Moeller XControl XC600, Hardware, Engineering And Function Description, Page: 56 / 78

Diagnostics for the local XI/
ON-BUS and the PROFIBUS-DP /
CANopen bus
07/04 AWB2700-1428GB
52
The diagnostic address (marker byte) from where the saved data
start, can be found in the configuration:
The first field starts at MB0, the second at MB142, the third at
MB284, etc.
An XC600 setup is shown as an example, together with the
resulting declaration:
Setup:
Declaration:
Structure of the inputs/outputs:
The input and output data are collected in the following structure,
to facilitate data access easier.
However, only the data for the (structure) output EXTENDEDINFO
is important for the user, since the individual bytes of the output
(ARRAY[0..129]) contain the diagnostic information for the
individual participants.
Evaluation of the GETBUSSTATE.EXTENDEDINFO array
The contents of the array depend on the bus system. Basically, the
array has the following structure:
Each byte contains the diagnostic information for one participant.
It is contained in three bits which you can query:
• Bit 0: 1 = a configuration is available
• Bit 1: 1 = data exchange is ok
1)
• Bit 2: 1 = new diagnostic data available
1) Bit 1 already indicates a “1” signal when the data exchange for
coupling of the slave was successful. This means: The connection is ok
and data exchange occurs.
Byte 129 is only used for interrogating PROFIBUS-DP participants.
In this case, it contains the number of participants that are
reporting diagnostic data.
Diagnostics of the local XI/ON bus
With local XI/ON modules there is only one participant, so that
Byte 0 shows the diagnostic information for all modules. Bits 0, 1
and 2 can be interrogated.
Diagnostics for PROFIBUS-DP bus
Byte 129 can be used for general diagnostics. It contains the
number of malfunctioning bus participants.
If the content of Byte 129 > 0 is, then the participant bytes can be
interrogated for error messages, starting with Byte 2 (participant
with address 2) and continuing to Byte 125.
Figure 68 : Controller configuration with diagnostic address
XC-... XC
-NET-C
AN
(Address CC000) XC
-NET-D
P-
M
(Address CE000) XC-PO
W
50-
XION-
UPS
XC-ADP-XION
VAR_GLOBAL
LXIONSTAT AT%MB0: GETBUSSTATE;
DPSTAT AT%MB142: GETBUSSTATE;
CANSTAT AT%MB284: GETBUSSTATE;
END_VAR
TYPE GETBUSSTATE;
STRUCT
BOLDENABLE: BOOL;
ENABLE: BOOL;
DRIVERNAME: POINTER TO STRING;
DEVICENUMBER: INT;
READY: BYTE;
STATE: INT;
EXTENDEDINFO: ARRAY[0..129] OF BYTE;
END_STRUCT
END_TYPE
Bit 7 6 5 4 3 2 1 0 Participant
Byte 0 x x x A
Byte 1 x x x B
Byte 2 x x x C
Byte 3 x x x d
...
Byte 128 x x x Z
Byte 129 x x x x x x x x
h If you connect the Gateway XN-GW... to the PROFIBUS-
DP module XC-NET-DP-M, then you must implement the
following settings in the controller configuration, in the
User Parameters register:
Diagnostics from modules: activate
Gateway diagnostics: device-related diagnostics