|
<< Click to Display Table of Contents >>
Reference of Errors in Log |
The next table lists some possible errors that may appear in this Driver's log, with the respective tips for solving them.
Errors in this Driver's log
Error |
Description or Solution |
|---|---|
LinkLayer104: Wrong frame sequence (received #XXX, expected #YYY), disconnecting... |
Master and Slave modes. This message reports receiving a message out of order in IEC 870-5-104 protocol. When this Driver detects that situation, forces a reconnection. Its cause is probably a message lost in the network. To solve it, investigate the physical connection or the network between this Driver and a device |
ERROR: Failed to send command 'XXX', application layer is locked |
Only in Master mode. This message occurs when this Driver tries to send a Command at application level while another Command is already executing. For example, trying to send a Select or Execute Command while a General Interrogation Command is executing. This Driver only generates that message and quits sending that Command after waiting for the time specified by an application's time-out. The cause is that the Application Layer of this Driver is locked for a long time. To solve it, increase that application's time-out |
GeneralInterrogation: received actterm with no GI active, retrying last GI |
Only in Master mode. This message occurs when this Driver receives a confirmation of finishing a General Interrogation Command and there is no active general interrogation process. Causes can be a General Interrogation Command started previously by this Driver which was interrupted due to a problem with a device's connection or this Driver is configured to not wait for a notification of finishing a General Interrogation Command and a Slave is sending that finishing notification. Possible solution are increase application's time-out of this Driver, investigate what caused the problem with a device's connection, or configure this Driver to wait for the finishing of the General Interrogation Command, and also possibly consider increasing application's time-out of this Driver |