I'm running LoggerNet 4.3. In rare cases with loggers with marginal radio links I noticed the following behaviour:
Sometimes an array is not transferred completely (I guess due to some transmission issues). LoggerNet writes the incomplete array to the specified file:
--- Appended at 2015-09-09T01:36:05.088928 ---
100,140,121,2015,252,2,6.11,6.9,255,4.516,100,6999,6999,6999,0,25,50,100,6999,6999,6999,6999,6999
401,140,121,2015,252,2,1.59,4548,13.87,13.66,7.16,0,0,3079,0,0,1.099,0
403,140,121,2015,252,2,100,100,17.31,13.9,21.5,17.86,14.7,21.9
100,140
So far so good. But on the next data collection, LoggerNet continues exactly where it stopped the last time:
--- Appended at 2015-09-09T01:46:43.338868 ---
,121,2015,252,32,6.45,7.4,254.8,4.531,99,6999,6999,6999,0,25,50,100,6999,6999,6999,6999,6999
401,140,121,2015,252,32,1.59,4548,13.89,13.88,7.15,0,0,3079,0,0,1.018,0
403,140,121,2015,252,32,100,100,17.55,13.9,21.1,17.87,13.8,21.9
This is unwanted as I process the files just after each data collection. I then miss the partly transferred array therefore.
Is there an option to let LoggerNet retransfer incomplete arrays?
Kind regards,
Marcel
There is not a method available for array based dataloggers. Loggernet keeps track of what data to collect based on memory addresses on the datalogger. There is no mechanism for Loggernet to know if the line of array based data is complete or not.
All current models of Campbell Scientific dataloggers store data in tables. In the case of a datalogger running a table based or Pakbus OS, each line of data has a record number. Loggernet will automatically retry collection of incomplete records.
Some of the retired dataloggers have table based or Pakbus operating systems available. Some changes would need to be made to your datalogger programs and data processing. Also, the compatibility of your communication hardware would need to be checked.