Communication via SIKONETZ5
AG05
Date: 15.06.2016 Art. No. 85677 Mod. status 139/16 Page 50 of 64
10.5.1 SIKONETZ5 error codes
no further information available
no further information available
Value rage exceeded /
inadequate
no further information available
no further information available
no further information available
write attempt to read only
read attempt to write only
Error due to device status
no further information available
EEPROM write access active
Table 18: SIKONETZ5 error codes
10.6 Errors
If a slave is in the error state the slave signals this state with SW.7 = 1.
Errors must be acknowledged by CW.5 = 0/1. If the cause of the error has not ben resolved at
the time of acknowledgement, the error will not be reset.
After acknowledgement of an error, the slave is in the switch-lock state. The switch-lock can
be released via a negative flank on CW.0 or CW.1 or CW.2.
Errors are stored in the error memory and can be read out.
In order to receive the last error occurring the number of errors must first be read in
parameter address 0x80.
With 0x80 + number of errors the parameter address with the latest error is received. Under
this address the error code is found (see chapter 7.2.1: Error codes).
10.7 Communication monitoring
10.7.1 Bus Timeout
The first telegram received by the slave starts time monitoring.
Every new telegram recognized as valid by the slave (correct check sum) triggers time
monitoring.
If timeout occurs during an active travel job, this will result in the Timeout error, i. e. the
current travel job is cancelled. Thus, a broken cable can be detected for instance and the
actuator set into a defined state.
To Next Page
Loading...