HMS Networks Anybus CompactCom 40 Network Manual page 27

Diagnostics
4.6. Diagnostics
4.6.1. Standard Diagnostics
PROFINET IO devices uses alarms when informing the IO Controller of diagnostic entries. In the Anybus
implementation, it is possible for the application to create alarms via diagnostic entries by means of the
Diagnostic Object (02h).
Up to 5 diagnostic instances can be created by the host application. An additional 6th instance can always be
created in event of a major unrecoverable fault.
In addition to the maximum number of diagnostic entries related to the host application, the Anybus
CompactCom is able to handle two diagnostic entries related to the safety module. One of the entries is reserved
for the FatalErrorEntry message and the other for the SendChannelDiagAlarm message, both messages are sent
by the safety module.
Creating a diagnostic instance is done by issuing the command Create. If the module is in state IDLE or
PROCESS_ACTIVE, the created instance will be communicated on the network as an "appear"-alarm. If the
module is in another state, the PLC will be notified in the connect response by a module diff block.
Deleting a diagnostic instance is done by issuing the command Delete. This will trigger a "disappear"-alarm on
the network. Supply the instance ID that was returned by the create-command.
Every diagnostic instance has a severity level and an event code associated to it. Major unrecoverable events will
cause the module to disconnect itself from the network, thus preventing network participation. Other severity
levels either produce a Channel Diagnostic alarm or a Generic Diagnostic alarm, depending on the Event Code,
according to the table below.
Severity Event code != network specific
Minor, recoverable Channel Diagnostic Alarm
Minor, unrecoverable
Major, recoverable
Major, unrecoverable Anybus enters Exception state
NOTE
Process alarms can not be created.
See also..
• Diagnostic Object (02h) (page 41)
4.6.2. Extended Diagnostics
Using the network specific event code (FFh) creates a Generic Diagnostic Alarm on the network. This type of
alarm can carry extended diagnostic information and more details about the source of the problem.
Generic Diagnostic Alarm instances can be tagged with a source API and slot- and subslot number. It can also
contain additional network specific diagnostic data like:
• Standard channel diagnosis with manufacturer extension
• Manufacturer specific channel diagnosis
• Manufacturer specific channel diagnosis with manufacturer specific extension that also provide network
specific diagnostic data
For more information, see Details: Network Specific Data (page
SCM-1202-021 Version 2.6
®
Anybus CompactCom
Event code = network specific
Generic Diagnostic Alarm (See Extended Diagnostics (page
42).
™
40 - PROFINET IRT Transparent
Ethernet
19))
Page 19 of 177