Command failed
Symptom:
Sometimes an error appears when a (pre-)Midlife instrument was configured with an older version of software that appears when connecting to a newer software. The error will state it is unable to read back the old configuration settings and informs the user to use the default configuration.
Solution:
This is normal behavior and an extra security to avoid firmware/software incompatibility problems. It only applies to reading back the configuration from the instrument with a different version than was used to program it. You can use the new software to retrieve and convert your data files without problems. Information about the deployment configuration settings used is available in the converted header file (*.hdr).
Checksum error
A checksum error means there was a problem with the serial communications. The checksum is at it's simplest the sum of all of the bytes from the start of a data string to the end. This is generally encoded at the end of the data string and used to check for communication errors. A checksum error occurs when the computed checksum on the receiving end does not match the transmitted value.
Generally, this means there is some noise on the communications line and one of the bits was mis transmitted or something similar, although in this case it could be due to the data buffer overflow and the data strings getting a little out of sync. For example, a data string could start and then the buffer overflow error occurs, so a portion of that data string is lost.
Flash corrupt
The message "Error: Flash Corrupt (I)" may appear in the Terminal Emulator. It can also be identified by looking at the dual LED on the main PCB blinking red once per second.
The flash corrupt message indicates a problem with the part of the recorder flash where internal parameters are stored such as baud rate, instrument mode etc. The corrective action is to try to erase the recorder and see if the problem disappears. The cause of this error is typically extensive "recorder wear" which can cause flash failure. We have seen this in cases where instruments have been used with a high rate of measurement start/stop sequencing usually only done by system integrators. If you see this error and use a controller to operate the instrument autonomously you may have to change the way you operate the instrument. For example using the commands that measure and output single samples from command mode or controlling the data flow by controlling the power to the instrument.
Another solution to this is to replace the flash which is a relatively simple operation. Nortek Support will send a short document describing the procedure when it is necessary along with the ready programmed flash and a special tool.
Updated