Name: Anybus CompactCom 40
Brand: Anybus
Rating: 4 (1 reviews)

To Next Page

To Previous Page

PROFINET Implementation Details 23 (258)

4.5 Diagnostics

4.5.1 Standard Diagnostics

PROFINET IO uses alarms when informing the IO Controller of diagnostic entries. In the Any-

bus 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 re-

sponse by a module diff block.

Deleting a diagnostic instance is done by issuing the command Delete. This will trigger a “disap-

pear”-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 unre-

coverable 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 Ge-

neric 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, p.

23)

Minor, unrecoverable

Major, recoverable

Major, unrecoverable Anybus enters Exception state

Process alarms can not be created.

Anybus CompactCom 40 User Manual

Questions and Answers: