COM_ERR DPM_COM_ERR_TYPE¶
Communication errors can be located more detailed using COM_ERR. COM_ERR outputs a structure of the type DPM_COM_ERR_TYPE. This data type is declared as follows within the PROFIBUS DP library:
TYPE DPM_COM_ERR_TYPE:
STRUCT
ADDRESS: BYTE;
EVENT: BYTE;
END_STRUCT
END_TYPE
Note
COM ERR is not supported by Communication Module CM592-DP. ADDRESS and EVENT are always set to 0.
ADDRESS
Data type: BYTE
If an error occurs, ADDRESS contains the bus address of the faulty device (0 to 125). If ADDRESS has the value 255, the error is located in the Communication Module itself.
EVENT
Data type; BYTE
EVENT displays the cause of an error.
The following tables show the encoding of the various errors.
Event | Meaning | Error source | Remedy |
---|---|---|---|
50 | USR_INTF task not found | Communication Module | Contact ABB |
51 | No global data field | Communication Module | Contact ABB |
52 | FDL task not found | Communication Module | Contact ABB |
53 | PLC task not found | Communication Module | Contact ABB |
54 | No master parameter record | Configuration | Generate configuration in the project and reload program to controller |
55 | Faulty value in master parameter record | Configuration | Check configuration data for Communication Module in the project and/or reload program to controller |
56 | No slave parameter records | Configuration | Add DP slaves to configuration data and reload program to controller |
57 | Faulty value in a slave parameter record | Configuration | Check configuration data of subordinate DP slaves in the project and/or reload program to controller |
58 | Doubled slave address | Configuration | Check configuration data of subordinate DP slaves in the project for doubled bus addresses and/or reload program to controller |
59 | Invalid offset address output data | Configuration | Check configuration data of subordinate DP slaves in the project for invalid IEC addresses and/or reload program to controller |
60 | Invalid offset address input data | Configuration | Check configuration data of subordinate DP slaves in the project for invalid IEC addresses and/or reload program to controller |
61 | Range overlapping in output data | Configuration | Check configuration data of subordinate DP slaves in the project for overlapping IEC address ranges and/or reload program to controller |
62 | Range overlapping in input data | Configuration | Check configuration data of subordinate DP slaves in the project for overlapping IEC address ranges and/or reload program to controller |
63 | Unknown process data handshake | Controller | Supply voltage OFF/ON, otherwise contact ABB |
64 | Insufficient memory | Communication Module | Contact ABB |
65 | Faulty slave parameter record | Configuration | Check configuration data of subordinate DP slaves in the project and/or reload program to controller |
202 | No segment available | Communication Module | Contact ABB |
212 | Error while reading database | Configuration/ Communication Module | Reload program with configuration data to controller |
213 | Faulty transfer structure operating system | Communication Module | Contact ABB |
Event | Meaning | Error source | Remedy |
---|---|---|---|
2 | Subscriber reports overflow | DP master telegram | Check configuration data of subordinate DP slave in the project and/or reload program to controller |
3 | Subscriber does not support requested function | DP master telegram | Check DP slave for conformity according to PROFIBUS DP standard |
9 | No data in response telegram | DP slave | Compare configuration data of subordinate DP slave in the project with actual configuration and reload program to controller if necessary |
17 | Subscriber does not response | DP slave | Check bus line and DP slave bus address |
18 | DP master not in logical token ring | DP master | Check the configured DP master bus address, the highest station address (HSA) in the other system DP masters and/or bus line for short circuits |
21 | Faulty parameter in request telegram | DP master telegram | Contact ABB |