Comprehensive Manual106
© 2018 Nortek AS
Figure: Fuse on circuit board
5.1.12 Check LED Indications
The midlife hardware has a dual LED consisting of one green and one red LED. The firmware uses
the LEDs to indicate the state it is in. The following combinations are used:
A short red flash occurs when the board boots. This means that reception of a break will also
cause a red flash as well as start of a new measurement based on an alarm from the real time
clock and when power is applied to the board.
Continuous green and red indicates that the board is in firmware upgrade mode.
Continuous green only indicates command mode.
In measurement mode, the green LED will flash when either of the beams pings.
5.1.13 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 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 that 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. The Vectrino software picks up the stream from the buffer but is missing a little
bit so the checksums do not match.
5.1.14 Flash corrupt
The message "Error: Flash Corrupt (I)" may appear in a couple of scenarios in the Terminal
Emulator.
Vector: 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.
To Next Page
Loading...
