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 | Event code != network specific | Event code = network specific |
|---|---|---|
Minor, recoverable | Channel Diagnostic Alarm | Generic Diagnostic Alarm (See Extended Diagnostics) |
Minor, unrecoverable | ||
Major, recoverable | ||
Major, unrecoverable | Anybus enters Exception state | |
Note
Process alarms can not be created.
See also..