Table 2-11: Result Byte - Addi-Data APCI-8001 Option Manual

O
PTIONS MANUAL
Code Meaning
F416 hex IBU_init_timeout
F417 hex IBU_too_many_devices_config_valid
F420 hex IBU_ibs_loop_diag_no_loop
F421 hex IBU_ibs_loop_diag_not_stable

Table 2-11: Result byte

Coding
Meaning
(1 Byte)
00 hex No error
01 hex
CRC error
last path
02 hex CR error
04 hex SL error
08 hex NOISE error
10 hex STOP error
20 hex MAU error
40 hex Parity error
Service error -
80 hex
Explanation
System runs without errors.
Received and calculated CR check sums do not coincide. A fault
has occurred on the section monitored by IBS UART.
CR flag in the character header of the sent and received characters
do not coincide.
SL flag in the character header of the sent and received characters
do not coincide.
After the expected end of an FCS, a "follow-on telegram" was
detected by the IBS UART hardware.
STOP bit error. Instead of the expected "STOP bit" of an INTERBUS
telegram, a high signal was identified by the IBS UART hardware.
A static "high" signal with more than 64-bit times length was
identified at the INTERBUS input (connection DI).
This error occurs if no device is connected to the IBS UART.
A transmission error was detected by the IBS UART hardware via
the parity bit of the serial asynchronous communication.
Primitive not defined
- When sending the result byte, a further
error was identified
- Primitive not allowed in the current status
example
the IBS UART is still in the "reset" status
only the "ResetStop" or "Set" primitives are
allowed.
Explanation
IBU_IBS_Init() could not be completed
within the specified time
Possible causes:
• max_repeat too small
IBU_IAPI_Set_MaxRep()
• BusDelay too small
IBU_ML_Set_Bus_Delay ()
The previously set maximum number of
subscribers is valid.
No system with the "loop diagnosis"
function is connected
No stable state is achieved for subscriber-
oriented local bus diagnosis.
Possible cause: loose connection
45
if, for