What causes some of the data points on the charts to be non-validated? What is non-validated data?
LogTag uses a very sophisticated method to automatically insert error detection codes during recordings. This assists in detecting corruption and/or manipulation of data. These error detection codes are saved with the file so any attempts to manipulate data in a saved file are also detected. Non-validated readings occur when a block of readings fails a data integrity check; these readings are displayed differently on the chart and data list. The most common cause for non-validated readings is when the LogTag has been configured to do continuous recording (i.e. the new recordings ‘wrap around’ over previous recorded values). As new data is over-written on a block of protected recordings, the data integrity error check for the original block of recordings will indicate an error, thereby technically putting the block of data into doubt. The same mechanism is also responsible if the logger is not configured for continuous recording, but has been configured for pre-start readings. Once the
