Description

The PROFINET IO Controller stack V3 has implemented the required state machines and services to build a PROFINET IO Controller. It can be used to build a complete PROFINET IO Controller which requires a correctly behaving application.
The stack on its own just provides services that neet to be handled correctly by an application for certification and correct behaviour in the field, e. g. handling of IOxS and alarms.

The stack offers an interface to access the cyclic data as well as a packet based interface for configuration, acyclic services and diagnostic.

Configuration

The stack offers a mailox interface for configuration. In addition Sycon.net can be used to configure the stack by a database download.

At runtime it is not possible to change the configuration of the stack (e.g. adding/removing od IO-Devices or submodules is not possible).

Cyclic data and I/O state

The cyclic data is available in the dual-port memory which can be accessed by a host application.

The submodul related IO status bytes IOPS (Input Output Object Provider State) must be handled by host application.

The submodul related IO status bytes IOCS (Input Output Object Consumer State) must be handled by host application.

Acyclic services

Acyclic services (Read Record or Write Record) can be requested by the application to the stack via the mailbox interface. They are forwarded to an IO Device. The response of IO Device is sent back to IO Controller application via mailbox interface.

DCP Services (e.g. DCP Identify All for lifelist) are available via the mailbox interface.

Alarms and diagnosis

The PROFINET IO Controller stack V3 can be configured to perform automatic alarm handling. For each alarm type it can be configured if the alarm is to be handled by the PROFINET IO Controller firmware itself or if the alarm shall be passed to the application for further processing. Using automatic alarm handling reduces the amount of indications passed to the application and can simplify application implementation.

On this page