Table of Contents
Advertisement
Diagnostics and error behavior
Diagnostics via FB STATUS
Event class 14 (0Eh) "Loadable Driver - General Processing Errors <Processing of a BSEND Job>"
Event class / number Description
0E 47h
0E 48h
0E 49h
0E 4Ah
0E 4Fh
0E 50h
0E 51h
0E 52h
0E 53h
0E 54h
100
With Modbus master only
Function codes 15 or 16: The parameter LEN for SFB BSEND does not correspond to the
transferred parameters "Amount of Bits" and/or "Amount of Registers". Parameter LEN is too
small.
Remedy: Increase parameter LEN for SEND until a sufficient amount of user data is transferred
to the CP. A larger amount of user data must be transferred to the CP because of the "Amount
of Bits" and/or "Amount of Registers".
With Modbus master only
Function code 5: The code specified in SEND source DB for "Set Bit" (FF00h) or "Delete Bit"
(0000h) is wrong.
Remedy: The only permitted code is FF00h or 0000h.
With Modbus master only
Function code 08: The code specified in SEND source DB for "Diagnostic Code" is wrong.
Remedy: The only permitted code is "Diagnostic Code" 0000h.
With Modbus master ASCII only
Access to 32bit registers is only allowed with FC 03, 06, 16.
Here bit 6 of FC in source DB is set.
Remedy: Correct your source DB.
With Modbus master only
The R_TYP specified for SFB SEND RK is illegal with this driver.
Remedy: "X" has not to be entered as R_TYP.
With Modbus master only
Slave address incorrect: The received slave address is different from the sent slave address.
Remedy: The wrong slave has replied. Check if the transmission line is interrupted (interface
analyzer may be required).
With Modbus master only
Function code incorrect: The function code received in the reply message is different from the
sent function code.
Remedy: Check slave device.
With Modbus master only
Byte underflow: Amount of characters received is less than should have resulted from the byte
counter of the reply message or is less than expected with this function code.
Remedy: Check slave device.
With Modbus master only
Byte overflow: Amount of characters received is more than should have resulted from the byte
counter of the reply message or is more than expected with this function code.
Remedy: Check slave device.
With Modbus master only
Byte counter wrong: The byte counter received in the reply message is too small.
Remedy: Check slave device.
VIPA System 300S
HB130 | CP | 341-1CH01 | en | 18-40
Advertisement
Table of Contents
