Website News |
Campbell Scientific Datalogger Q&AQuestion: How can I calculate how fast the CR10 X memory fills up with readings Answer: The quickest way to assess memory usage for an Edlog programmed device (CR10(X), CR510, etc.) is to look at the fsl file. When you compile a program using the Edlog compiler it generates a number of other files along with the .dld. One has the extension .fsl and this stands for Final Storage Label. If you scroll all the way to the bottom of the file you will find an estimate of the amount of memory used in a single day. For example this is the estimate from one of my programs: “Estimated Total Final Storage Locations used per day 5976”. The CR10X has roughly 60000 locations so in this scenario data should be offloaded every 10 days to avoid data loss. Data can be stored as high or low resolution so one can’t simply
count the number of data points to estimate memory usage. The
compiler will allow for high and low resolution in its estimate so
it’s best to use the fsl file to estimate memory Question: How do I read VW sensors with a CR10 datalogger? Answer: We have a manual that explains the basics. There are also sample programs that you can use to get started. We do not provide support for the sample programs. Question: I want to place my CR10 and my AM416 multiplexer in different locations. How far apart can I place them? Answer: We usually recommend that the AM416 be placed close to the CR10, but if you must separate them, here are some points to consider: 1. Power: The CR10 must supply power to drive the relays on the AM416, so you must check for a voltage drop caused by the resistance of long cables. See the AM416 manual for power requirements. 2. Digital Ouput and Pulse: The CR10 sends a digital signal to reset and clock the relays. The duration and level of this signal can be degraded by long cables. See the AM416 manual for required voltages. 3. Signal Degradation: The signal from the sensor doesn't stop at the multiplexer. It continues, unamplified and unfiltered, through the multiplexer all the way to the CR10. Long cable lengths are subject to RF noise from the environment and resistance from the cable. Question: Is there a way to connect a CR1000 to my SCADA system? Answer: There are two ways to interface a CR1000 to a SCADA system.
Discussion of OPC on the Campbell Scientific website Discussion of SCADA on the Campbell Scientific website Question: How do I read Slope Indicator's RTD temperature sensor with a CR10X. What coefficients do I use? Answer: This information is in some, but not all of our manuals. Here is information taken from the VW Piezometer manual, but works for any of Slope Indicator's RTDs. 1. Use instruction P4 with the following settings to read the RTD sensor.
Question: How do I read (3K) thermistors with the CR10X? Answer: 1. Use instruction P4 to read the thermistor.
Question: I want to use CR10 data in Excel. How can I convert CR10 dates into Excel dates? Answer: We've placed the answer on a separate page: How to Convert CR10 Dates. Question: I need to enter some polynomial factors that have more decimal places than the p55 instructions allows. What's a good workaround? Answer: One workaround is to convert the factors to scientific notation and assign them to variables: this: A_01=-1.59950E-05 A_02=-1.38150E-05 Scientific notation allows the CR10X to maintain the required number of decimal places. Then you make a loop to grab relevant factors and apply them to the raw data in a simple polynomial equation: xmH2O = (((xA * xHz^2 + xB * xHz + xC) + BARO_psi + xTemp) * 0.7037) + xeleOS Then transfer the result into the final storage location, for example: 24: Beginning of Subroutine (P85) ; convert to mH2O 25: Beginning of Loop (P87) ; get a frequency & temperature 27: Z=X (P31) 28: Z=X (P31) ; get the elevation offset ; get the calibration factors 30: If (X<=>F) (P89) ; if the fequency is < 0 we have a bad
reading ; if we have a bad reading then set the value to zero 31: Else (P94) ; calculate temperature correction ; convert to mH2O 32: End (P95) ; put calculated reading into final storage 34: End (P95) ; loop 35: End (P95) ; subroutine
|