|
Post by Lake Shore Ryan on Sept 23, 2022 13:26:53 GMT -5
|
|
|
Post by Lake Shore Ryan on Sept 23, 2022 12:57:44 GMT -5
I couldn't tell if our engineer was annoyed or impressed to be talking to me about the 805 temperature controller , but he found some information that might be helpful. It seems that there is a switch inside the instrument that is used to initialize the NOVRAM. If the NOVRAM is corrupt, the firmware stops and waits for switch 4 to be switched. Then it will initialize the NOVRAM and then stop until switch 4 is open again. This is his best guess from looking at the old code and schematics. Could you let us know if this works? He and I are now both very curious if you can get your instrument working again.
|
|
|
Post by Lake Shore Ryan on Sept 22, 2022 16:59:29 GMT -5
Hi, well I must say that I applaud your determination to keep this 805 controller running. I found a copy of the manual that looks to have been published in 1988 and I see the mention of initializing the NOVRAM. I don't have any experience with this unit, since I think I may have still been learning to ride a bike when these were made, but I will check if we have any documentation that might help. Do you have any way to determine whether the new DS1225Y you sourced is good?
|
|
|
Post by Lake Shore Ryan on Nov 2, 2021 9:50:33 GMT -5
|
|
|
Post by Lake Shore Ryan on Sept 14, 2021 13:25:45 GMT -5
Hi Tim, first of all, thank you for linking to that publication. I hadn't seen this one and it's nice to have this to point to for future questions about this topic.
As for your application with the SD packaged Cernox, we don't have any data on what would happen to the various material boundaries under that combination of temperature and pressure, but we're interested to learn.
It sounds like you've already built the experiment and will likely proceed. If this is the case and would like to find out how that particular sensor faired, we could perform an internal vapor analysis at the conclusion of your experiment and let you know what we find. Obviously this would destroy the sensor, so we could arrange for a replacement if needed.
If you have space for additional sensors, we could also send extras that could all be installed together and gradually removed one at a time to see if/when helium begins to be seen.
We're open to collaborating on research like this. We often get questions from researchers about high pressure scenarios, so this kind of research could be helpful to others doing similar work in the future.
|
|
|
Post by Lake Shore Ryan on Jun 28, 2021 8:13:38 GMT -5
And if it all just gets too frustrating, there is always our 240-8P temperature input module which has a native PROFIBUS DP-V0 interface and a GSD file to get it configured on your network.
|
|
|
Post by Lake Shore Ryan on Apr 7, 2021 11:01:38 GMT -5
Hi there, Sorry for the delayed response, had to dig a little deeper than usual to find the answers for some of these questions. Hope your experiences with the older Lake Shore instruments were positive. I have to admit I haven't heard of the CST-900 before. What kind of instrument is this? Model 224I couldn't find a good picture of the back of the 6-pin DIN connector for the sensor, and working from home means I can't easily get one. However, I can say that I've soldered wires to the back of these connectors before and they're quite easy to work with. We even solder 1/4W axial resistors directly to the pins, then bridge the leads using the resistor wires to make the 4-lead connections just like you're talking about. Here is a picture of the power cable, it's 7.5 ft long. Model 211SThankfully, the DB-25 plug for the 211S is easier to find. As you can see, these connections use solder cups, and they're also easy to solder to. Below you can see the dimensions of the power adapter. The length of cable provided is 1.5m long. Hope that's helpful in answering your question. And finally, yes, you're correct about the 4 to 20 mA out. If you set to range 3, it will scale linearly from 4 mA at 0 K to 20 mA at 325 K. Section 3.8 of the 211 manual has some tables and formulas that should help demonstrate this. Hope this helps with your questions. These are both great instruments, that I'm sure will last you as long as your DRC-80 .
|
|
|
Post by Lake Shore Ryan on Feb 11, 2021 9:46:29 GMT -5
If you're willing to share your findings, I'd be happy to look into it further. There are other temperature dependent properties too, like zero field offset. Is the gaussmeter in a temperature controlled area? Or would it be seeing temperature changes too?
|
|
|
Post by Lake Shore Ryan on Feb 10, 2021 17:21:06 GMT -5
It's continuous, as temperature changes, so does the gain factor.
Just curious, what sort of temperature ranges and field ranges are you experiencing? It sounds like you might be doing some interesting things if you're asking these sorts of questions.
|
|
|
Post by Lake Shore Ryan on Feb 10, 2021 15:02:29 GMT -5
I wish we were still on break! Can't believe it's been a whole month already. Sorry we didn't get back to you, this one must have slipped by.
The gaussmeter applies temperature compensation by calculating the difference between our calibration temperature and the current measured probe temperature and then applying a gain factor accordingly.
Gain factor = 1 + (temperature coefficient x temperature difference)
The temperature coefficient is unique depending on the sensor in the probe and will generally be somewhere in the range of +/- 0.1% per °C
So as an example, if the probe was calibrated at 24°C and your probe was measuring at 29°C you would expect a +5°C temperature difference to be used.
If that particular probe had a -0.02%/°C temperature coefficient, the the gain factor for that temperature would be 1 + (-0.0002 x 5) = 0.999
This gain value would then be applied to the calculated field value.
Unfortunately, the unique values stored on your probe are not accessible by the user, but you could try calculating using typical values:
Typical calibration temperature: 23°C Typical temperature coefficient of sensitivity: -0.04%/°C
If you are not having any luck using these numbers, then I would suggest sending a request to support@lakeshore.com for them to look up your probe serial number to see what values were programmed into its onboard memory.
Best of luck. Let me know if this was helpful.
|
|
|
Post by Lake Shore Ryan on Dec 21, 2020 10:30:24 GMT -5
And if you're looking for more options when it comes to the python scripts, the documentation is here: lake-shore-python-driver.readthedocs.io/en/latest/teslameter.htmlI think from your description, you're using the buffered streaming option, which is only setup to read DC values? myTeslameter.get_buffered_data_points(*args, **kwargs) Which field values in particular are you looking to record? Since you're wanting to record frequency readings, you probably don't need to record those values more often than once per second. Are you also wanting to record RMS and DC offset? The frequency and RMS requests are just: myTeslameter.get_frequency()
myTeslameter.get_rms_field() Maybe you could ask for one second of buffered data, then frequency, and RMS, then another second of buffered data? Keep looping through that until you have the amount of data you're looking for? As long as you can get the frequency and RMS data out of the instrument fast enough, you shouldn't loose any of the data being buffered. If you do notice you're not able to get the data out fast enough, you might extend the buffer to 100 ms intervals? Just depends on what you're trying to capture I guess. Feel free to respond with more information about what you're doing and we can make other suggestions. Glad to hear you're getting some use out of the python scripts we added to the teslameter.
|
|
|
Post by Lake Shore Ryan on Feb 19, 2020 1:19:56 GMT -5
Thanks gert, now I understand a little better what you're asking. The 240 as you're probably realizing now was designed to keep cost and complexity down for large scale deployments. So the 240 only has two communication methods: USB intended for instrument configuration using PC software, and PROFIBUS for PLC integration. In the past when customers have integrated with Beckhoff units, it was using a proxy or gateway of some kind that translates the PROFIBUS data to EtherCAT. Whether this makes sense for your installation will probably come down to how many modules you intend to integrate into the system. Was there a specific reason you wanted to shift from the 218 to 240 modules beyond form factor?
|
|
|
Post by Lake Shore Ryan on Feb 12, 2020 8:52:22 GMT -5
Hi gert, would you mind telling me a little more about what you're hoping to do? We might be able to suggest an alternative solution. Thanks.
|
|
|
Post by Lake Shore Ryan on Jan 6, 2020 10:09:29 GMT -5
OK, thank you. Hopefully this helps us replicate the issue.
|
|
|
Post by Lake Shore Ryan on Jan 3, 2020 14:37:36 GMT -5
Hi Chev, so I tried to replicate this problem today and now I can't get my units to demonstrate the same problem when using 2.0.1. Talk about frustrating. Could you let me know if the 240 module you have way purchased new and came directly from us, or was it part of an evaluation kit or from someone who may have already programmed it with something? Thanks.
|
|