...
| Column | ||
|---|---|---|
| ||
Key Features
|
| Column | ||
|---|---|---|
| ||
Supported Protocols
|
...
| width | 30% |
|---|
...
| title | On this page |
|---|
| Table of Contents |
|---|
...
Description
The PROFINET IO Device stack V4 has implemented the required state machines and services to build a PROFINET IO Device. It can be used to build a complete PROFINET IO Device 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. remanent storing of NameOfStation.
Configuration
The stack offers a mailbox interface for configuration. A basic configuration has to be set using a Set Configuration packet first. Afterwards at runtime it is possible to change the submodule configuration by using services to plug or pull submodules.
During connection establishment to an IO Controller the stack compares its current submodule configuration to the expected one of the IO Controller. Differences are indicated to a registered application so that the application is able to adjust the stacks submodule configuration, if the application model allows such a handling.
Cyclic data and I/O state
The stack offers an interface to access the cyclic data as well as a packet based interface for configuration, acyclic services and diagnostic.
The cyclic data is available in the dual-port memory which can be accessed by a host application.
The stack supports different ways of handling the submodul related IO status bytes IOPS (Input Output Object Provider State) and IOCS (Input Output Object Consumer State). Either they are completely handled by the stack or handled by the application. In case the stack handles these IO status bytes they are always set to "good".
This IOxS is part of the cyclic data and not set/get by packets but by the mechanisms for cyclic data.
Acyclic services
Acyclic services requested by an IO Controller with a Read Record or Write Record are indicated to a registered application via the mailbox interface. If no application is registered at the stack all acyclic requests for none-standardized datasets will be responded with an error by the stack automatically.
The stack offers automatic handling of I&M functionality (read and write). However it is possible for application to disable this automatic handling and handle I&M on its own if required.
Alarms and diagnosis
The stack offers a mailbox interface for the application to generate alarms and add diagnosis entries to the stack.
Key Features
- Cyclic communication
- Acyclic communication
- Shared Device
- Fast Startup
- Runtime adjustment of submodule configuration
- IRT (for most firmwares)
Detailed technical data
| Info | ||
|---|---|---|
| ||
For a detailed listing of the technical data, please refer to the data sheet of the individual firmware. You can find them in the "Resources" section on the specific firmware version page. Firmware data sheets are available for version V4.7.0.0 and higher. The technical data of the individual available firmwares differ slightly. Therefore, the below table only provides a rough overview of the supported features and/or quantity structures. The following technical data applies to the latest available Release version. Technical data of older Release versions may be different. |
| Feature | Description |
|---|---|
| Maximum number of total cyclic input data | 1440 bytes |
| Maximum number of total cyclic output data | 1440 bytes |
Maximum number of submodules 32 submodules in total(firmware dependent) | Up to 256 submodules |
Multiple Application Relations (AR) (firmware dependent) | The Stack can handle up Up to 4 IO-ARs and one 1 Supervisor-DA AR at the same time. |
| Acyclic communication | Read/Write Record, max. 1024 Bytes/Telegram for standard firmware. |
| Alarm Types | Process Alarm, Diagnostic Alarm, Return of Of Submodule Alarm (implicit), Plug Alarm (implicit), Pull Alarm (implicit), Update Alarm, Status Alarm, Upload and Retrieval Notification Alarm |
Diagnosis EntriesThe stack supports up (firmware dependent) | Up to 256 application diagnosis records of type Channel or Extended Channel Diagnosis |
| Identification & Maintenance | I&M0 -4 Read: Either built in for Slot 0 / Subslot 1 or pass through to application for any submodule. I&M1-5 Read/Write: Either built in for Slot 0 / Subslot 1 or pass through to application for any submodule. I&M4 and I&M5 are disabled by default. |
| Topology recognition | LLDP, SNMP V1, MIB2, physical device |
Minimum cycle time | 1 ms for RT 250µs for IRT Note: The network cycle time of 250 µs can be used with asynchroneous applications only, which do not update the dual-port memory on every network cycle. (Isochroneous) applications are not supported for 250 µs network cycle time, only for 500 µs, 1 ms, 2 ms and 4 ms. |
IRT Support (firmware dependent) | supported (RT_CLASS_3) |
Media Redundancy | MRP client is supported |
| Additional supported features | DCP, VLAN- and priority tagging, Shared Device |
| Baud rate | 100 MBit/s |
Data transport layer | Ethernet II, IEEE 802.3 |
| Profinet IO specification | V2.3 (advanced startup) is implemented V2.2 (legacy startup) is supported |
Restrictions
- RT over UDP not supported
- Multicast communication not supported
- Only one device instance is supported
- DHCP is not supported
...
Maximum supported GSDML Parameter PNIO_Version: 2.35 (when using newest available stack/firmware version)
Configuration
Configuration is done by sending packets to the stack or by using SYCON.net configuration database.
Diagnostic
...
- The amount of configured IO-data influences the minimum cycle time that can be reached.
Only 1 Input-CR and 1 Output-CR per AR are supported
- Fast Startup is implemented. However some additional hardware limitations apply to use it.
The amount of usable submodules is reduced by 1 for each used different API (in case more than 2 APIs are used in parallel).
Little endian byte order for cyclic process data is not supported
System Redundancy (SR-AR) and Dynamic Reconfiguration (formerly known as Configuration-in-Run, CiR) are not supported. (*)
- The usage of PROFINET CombinedObjectContainer
- is not supported at all (for standard firmware)
is not supported for user application parameters (for SystemRedundancy enabled firmware) (*)
- SharedInput is not supported
- MRPD is not supported
DFP and other HighPerformance-profile related features are not supported
- NXLOM is not available
- The stack does not support usage of PDEV submodules (InterfaceSubmodule or PortSubmodule) outside of slot 0. In addition the InterfaceSubmodule is only supported in subslot 0x8000 and the PortSubmodules are only supported in subslots 0x8001 and 0x8002.
In case of using a firmware including the feature System Redundancy, the combination of the features “System Redundancy” and “Shared Device” is not supported. Recommendation: Set “NumberOfAdditional IO ARs” in tag list to 1.x
(*) A separate PROFINET IO-Device firmware is available that support the features System Redundancy and Dynamic Reconfiguration. To use the firmware requires a separate license agreement.