Which features provides the module?

• Profinet stack, Conformance Class B, Real Time Class 1

• EtherNet/IP stack

• EtherCAT stack

• Modbus TCP

• OPC-UA stack

• Web server

• TCP channels (maximum throughput of 32kBit/s)

• UDP channels (maximum throughput of 32kBit/s)

• Cyclic communication channel for real time data (Profinet process data, EtherNet/IP process data) with at least 64 byes input/output data and up to 73 byte input and 73 byte output data (depending on the protocol stack) and a cycle time of 1 ms

• RPC interface for management, application setup and non realtime data

Profinet

What are the capabilities of the device?

• Configurable number of modules and slots

• Up to 73 byte of process data* per direction when Datamapper is chosen

  • input data, output data, ioxs, status information (optional generic data provider, optional apdu status)

  • direction of output data is limited to 69 byte when optional generic data provider is used

  • up to 1 ms cycle time

• Up to 1434 byte of process data per direction when RPC transport is chosen

  • cycle time must not be less then 100ms

• Support for process alarms

• Support for record data (read, write), where a maximum of 1116 byte can be accessed in each direction

• Support for Redundancy (MRP) (FW Rev. 2.1)

• Dynamic module configuration (provided by connection request from PLC) for modules mapped to the cyclic channel (FW Rev. 2.1)

What functionality is not supported?

• Queue for sequential process alarm sending

EtherNet/IP

• Redundancy (DLR) - Beacon Based Ring Node

• 73 byte of process data in each direction

  • 69 byte in output direction, if the generic data provider is used

  • the generic data provider is required for LED status of EtherNet/IP devices

• Virtual CIP classes

• Exceeding process data over the size of the cyclic channel (73 byte) by using RPC service

EtherCAT

• EtherCAT

• Dynamic PDO assignment and dynamic PDO mapping

• SDO Info service

• SDO service

• Distributed Clocks

• Up to 69 Byte of process data in each direction with an cycle time up to 1 ms

  • the generic data provider is required for LED status of EtherCAT devices

• Up to 1408 Byte of process data while using RPC transport

  • cycle time must not be less then 100ms

Modbus TCP

More Information at the Modbus TCP Documentation. Please see Features & Known Restrictions, too.

• User programmable data regions for coils, discrete inputs and registers

• Supported Function Codes:

  • 0x01 - read coils

  • 0x02 - read discrete inputs

  • 0x03 - read holding registers

  • 0x04 - read input registers

  • 0x05 - write coil

  • 0x06 - write register

  • 0x0F - write multiple coils

  • 0x10 - write multiple registers

OPC-UA

What are the capabilities of the device?

Please refer here for a full list of supported Profiles and Conformance Units.

Known Restrictions

• Objects with following Data Types can not created by Application:

  • Extension Objects (application specific data type container).

  • Data Values with associated status code and timestamps.

  • Variants (generic data container).

  • Diagnostic Information with associated status code and timestamps.

• SoM is not 100% compliant with Specification - OPC Unified Architecture Compliance Test Tool raise Errors at Subscriptions and Monitoring due to delayed communication between SoM and Application Controller.