Hi all
I have to CR6 dataloggers running with similar programs.
From one of them I recently missed data because my data collecting PC had a crash and the table fill time was shorter than expected.
Now I observed that one of these two loggers has a table fill time of only 2 days and 4 hours (approx 19 000 records in two tables) while the other logger has 7628 days (183 076 records).
The size of all data tables was allocated automatically (-1).
So far I always allocated table size automatically in different applications and never run into trouble.
Any tips what went wrong and how I can identify the reason for the short table fill time?
Best regards
Uta
instrumentengineeer
NIVA, Norway
One of the CR6s has the extended memory for data storage. This was added to the CR6 after the initial release. This is the reason for the difference in fill times between the two dataloggers.
This extended storage is only accessible when using the auto-allocate (-1 in the size parameter), so for most applications, this would be the recommended default (an exception would be if the DataTable were being written to at a high rate as the extended memory is flash and will wear out).
To determine if the CR6 has the extended memory, if the size of a formatted CPU: drive is ~30M, this is the newer version. If the CPU: drive is ~4M, this is the older version which does not use the extended memory for data storage.