PROFIBus Master Diagnostics
Operator Menu Location: Generic Hardware Operators -> Networking -> PROFIBus
Operator Bitmap
Functional Description*:*
The operator issues a diagnostic check from the master.
Output pins indicate whether the master has a configured slave and whether the master is communicating with its slave.
[0] -> true if master has configured slave
[1] -> true if master is exchanging data with slave
[2] -> state output (see DPM_State below)
[3] -> remote error address (see Err_Rem_addr below)
[4] -> error event code (see page 25-26 of master document for error code interpretation)
[5] -> global error byte (see below)
[6] -> hard bus error count
The following error numbers are valid for Err_event, if Err_rem_adr is
255. Their format is;
CODE & EXPLANATION |
ERROR SOURCE |
REMEDY |
---|---|---|
0 |
 |
no mistakes appear |
50 USR_INTF-Task not found |
DEVICE |
contact technical support |
51 no global data-field |
DEVICE |
contact technical support |
52 FDL-Task not found |
DEVICE |
contact technical support |
53 PLC-Task not found |
DEVICE |
contact technical support |
54 non existing master parameters |
DEVICE |
execute download of data base again |
55 faulty parameter-value in the master parameters |
project planning |
contact technical support |
56 non existing slave parameters |
project planning |
execute download of data base again |
57 faulty parameter-value in a slave parameters datafile |
project planning |
contact technical support |
58 double slave address |
project planning |
check projected addresses |
59 projected send process data offset address of a participant outside the allowable border of 0- 255 |
project planning |
check projected addresses |
60 projected receive process data offset address of a participant outside the allowable border of 0- 255 |
project planning |
check projected addresses |
61 data-areas of slaves are overlapping in the send process data |
project planning |
check projected addresses |
62 data-areas of slaves overlapping in the receive process data |
project planning |
check projected addresses |
63 unknown process data handshake |
warmstart |
check warmstart parameters |
64 free RAM exeeded |
DEVICE |
contact technical support |
65 faulty slave parameter data sets |
project planning |
contact technical support |
202 no segment for the treatment free |
DEVICE |
contact technical support |
212 faulty reading of a data base |
DEVICE |
execute download of data base again |
213 structure-surrender to operating system faulty |
DEVICE |
contact technical support |
220 Software Watchdog error |
HOST |
check HOST program Controlled Start and Stop of I/O Connection 25 |
221 No Data Acknowlegde in process data handshake mode 0 |
HOST |
program hasn't acknowledged the last handshake in time |
222 Master in Auto_Clear |
Slave Device |
the auto_clear mode was activated, because one slave is missing during runtime |
225 No further Segments |
DEVICE |
contact technical support |
The following error numbers are valid for Err_event, if Err_rem_adr is unequal 255:
CODE & EXPLANATION |
ERROR SOURCE |
REMEDY |
---|---|---|
2 station reports overflow master |
telegram |
check length of configured slave configuration or parameter data. |
3 request function of master is not activated in the station master |
telegram |
check slave if PROFIBUS-DP norm compatible |
9 no answer-data, although the slave must reponse with data |
slave |
check configuration data of the station and compare it with the physical I/O data length |
17 no response of the station |
slave |
check bus cable, check bus address of slave |
18 master not into the logical token ring |
DEVICE |
check FDL-Address of master or highest-station-Address of other master systems. examine bus cableing to bus short circuits. |
21 faulty parameter in request master |
telegram |
contact hotline |
User-Defined Properties:
Name. A string label that identifies the operator
Comments: None.
See Also: