Hi,
with cr10x it was possible to have besides the program a configuration file with calibration factors. Is it possible with CR1000? I haven't found it on the documentation.
Thxs,
LGS
I use the Fileopen Fileread instructions to access configuration files on the USR drive. The files themselves I create in Excel saved as CSV format then upload to the logger.
For the CR1000/CR800/850/CR3000 you can use the CalFile instruction, or for on-site/in-field calibration you can use the FieldCal Instruction. After a FieldCal instruction has been put in place in the datalogger program, a calibration wizard can be activated from the Connect Screen of LoggerNet.
From the CRBasic Help:
The CalFile instruction provides a way to store sensor calibration data from a program into a file located on the PC card drive (CRD) or the CPU: drive.
--
The FieldCal instruction sets up the datalogger to perform a calibration on one or more variables in an array.
---
For more on FieldCal, take a look at the RTDAQ Manual, section 9:
http://s.campbellsci.com/documents/us/manuals/rtdaq.pdf
I have never used CalFile or FieldCal as my understanding is that CalFile is a one way program to CPU process which requires the calibration factors to be hard coded into the program. Hard coding of calibration factors is what I do not want to do. Also I have never used field calibration as my instruments are factory calibrated and certified and I apply offsets manually.
BUT having read this thread and the CRBASIC manual I can see me using FieldCal in the future.
So thanks GT.
LGS, Can you explain a bit more how your CR10X uses a calibration file? Maybe post some of the Edlog code. We should be able to figure out how to do something close to, or better than, what it did. I don't recall Edlog being able to access separate files.
In fact i never used any calibration file in Edlog: i was confused with the Table 4 possibility.
Thanks to all for the information received.
Take a look at the ConstTable/EndConstTable instructions. That is easy to set up and is close to *4 functionality. One note: making changes via the ConstTable does cause the program to recompile. Collect your data first.