Hi,
In old data-loggers (eg CR10X), it was able to modify the datafile without any disturbance on data-logging: the only thing was that the code character displayed at the end of the last row should not be deleted.
Now, on the new data-loggers, when I change something in the file, the data-logger will systematically create a new file. It seems like the date and hour of file is important for the new data-files.
Is it so possible to do the same thing I did with the old dataloggers.
Regards,
Daniel
With "newer" dataloggers, such as the CR1000, the default output file format is TOA5. This format requires that a header be present that accurately describes the data that will follow. LoggerNet cannot append to this format of file without first checking the header of the existing file. If that header disagrees with what LoggerNet knows about the table, then it will back up the existing file and start a new one with the proper header.
You didn't mention what you were doing to modify the data file but it apparently affected the header of the file. If you don't want this checking to take place, you can modify the format of the file in LoggerNet by specifying the "Output Format" field for the table as "ASCII Table Data, No Header", or "Array Compatible CSV".
Ok, so if a change only data without changing header the same file will be append?
My example is the following: I added a new CR1000 on my network but the 100 first lines of the datafile are bad because sensors were not added at the same time.
I would like to delete these lines.
Daniel
UP !
* Last updated by: Otemohu on 9/14/2012 @ 2:27 AM *
You should be able to delete the 100 lines of bad data and leave the header intact with a "plain text editor".
Ok it works, thank you !