FEC920: USER GUIDE
Page 19
A
September 18
FTP Primary Server Failure
This error occurs if the recorder fails to establish connection with the
primary server, after two attempts. After the second attempt fails, the
recorder attempts to establish connection with the secondary server
instead. Primary and secondary server details are entered in the
Network. Archiving area of configuration (Section 6.2.2).
FTP Secondary Server Failure
This error occurs if the recorder fails to establish connection with the
secondary server, after two attempts. Primary and secondary server
details are entered in the Network.Archiving area of configuration
(Section 6.2.2).
Maths channel failure
Appears if, for example, the divisor of a divide function is zero.
Media archiving file lost
A file has been deleted that had not yet been archived. Possible causes:
memory stick missing, full or write protected; archiving has been
disabled; archiving rate too slow.
Media archiving too slow
The archive rate is too slow to prevent the internal memory from
overflowing. The recorder effectively switches to ‘Automatic’ (Section
6.2.2) to ensure that data is not lost.
Media full
Archive storage device is full. The alarm becomes active only when an
archive is in progress.
Media missing
No archive storage device present when archive attempted.
Non-volatile memory failure
RAM copy of non-volatile parameters is corrupted.
Non-volatile Write Frequency warning
One or more parameters are being written frequently to non-volatile
memory. If this continues, it may lead to ‘memory depletion’ (i.e. the
memory will no longer be able to store values correctly). A common
cause of this problem is frequent writes over Modbus comms.
Recording failure (message)
Message explains reason for failure.
SNTP failure
Invalid data received from SNTP server, for example, the year received
from the server is <2001 or >2035, or the server cannot be accessed.
Time synchronization failure
Instrument time has failed to synchronize with SNTP server.
If more than 5 ‘Time change events’ occur within 24 hours a ‘Time
synchronization failure’ alarm is set. The alarm occurs 24 hours after
the first event. Once synchronization is re-established, the alarm self-
clears within 24 hours. A ‘Time change event’ occurs whenever the
recorder time is found to be more than two seconds different from the
server time. If the instrument time differs from the SNTP time by less
than two seconds, the instrument time is updated gradually (1ms, eight
times a second) to prevent time changes being recorded.
SNTP time is based on elapsed seconds since 00:00 hours on 1st
January 1900. The time is not affected by time zones or daylight saving
adjustments.
USB overcurrent
USB power fault - too much current (i.e. >100mA) is being drawn by a
USB device.
Wiring failure
The user wiring has failed to verify, i.e. one or more wires has been
detected that does not have both a source and a destination defined.
This may be the result, for example, of power loss during a download
from iTools.
A5E45696052A Rev-AA