Download 40 Profinet IO (RT/IRT)

PROFINET IO Implementation Details 25
3.5 Diagnostics
3.5.1 Standard Diagnostics
PROFINET IO 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.
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
Minor, recoverable
Minor, unrecoverable
Major, recoverable
Major, unrecoverable
Event code != network specific
Channel Diagnostic Alarm
Event code = network specific
Generic Diagnostic Alarm
(See “Extended Diagnostics” on page 25)
Anybus enters Exception state
Note: Process alarms can not be created.
See also...
•
“Diagnostic Object (02h)” on page 73.
3.5.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, and
can also contain additional network specific diagnostic data.
For more information, see “Details: Network Specific Data” on page 75.
Anybus CompactCom 40 PROFINET IO
Doc.Rev. 1.22
Doc.Id. HMSI-27-226