Features - V2
Key Features
- cyclic Profinet Communication (RT_Class_1)
- support for FastStartUp IO-Devices
- interfaces for acyclic services
- interfaces for DCP services
- automatic or application controlled IOPS handling
Supported Protocols
- RTC – Real time Cyclic Protocol
- RTA – Real time Acyclic Protocol
- DCP – Discovery and Configuration Protocol
- CL-RPC – Connectionless Remote Procedure Call
- LLDP – Link Layer Discovery Protocol
- SNMP – Simply Network Management Protocol (SNMP v1)
Â
Technical Data
Feature | Description |
---|---|
Maximum number of total cyclic input data | 5712 bytes (including IOxS status bytes) Note: bitlists of IO-Device status information require the remaining bytes |
Maximum number of total cyclic output data | 5760 bytes (including IOxS status bytes) |
Maximum number of cyclic input data | 1440 bytes per device (= IOCR data length including IOxS status bytes) |
Maximum number of cyclic output data | 1440 bytes per device (= IOCR data length including IOxS status bytes) |
Maximum number of configured devices | 128 |
Acyclic communication | Read/Write Record Limited to 1392 bytes per telegram, Limited to 4096 bytes per request |
Alarm processing | yes but requires handling in application program |
DCP functions via API | Name Assignment IO-Devices (DCP SETNameOfStation) Set IO-Devices IP (DCP SET IP) Signal IO-Device (DCP SET SIGNAL) Reset IO-Device to factory settings (DCP Reset FactorySettings) Bus scan (DCP IDENTIFY ALL) DCP GET |
Minimum cycle time | 1ms (Different IO-Devices can be configured with different cycle times) |
Functions | Fast Startup of PROFINET IO Devices supported |
Data transport layer | Ethernet II, IEEE 802.3 |
Size of configuration file | Max. 1 MByte |
Profinet specification | implementation based on Profinet IO specification v2.2 |
Configuration
Two kinds of configuration are possible:
- Configuration by tool SYCON.net (Download or exported configuration of two files named config.nxd and nwid.nxd).
- Configuration by packets to transfer bus and device parameters
Diagnostic
Firmware supports common and extended diagnostic (of firmware itself) in the dual-port-memory for loadable firmware.
Profinet diagnosis needs to be handled by the application. Incoming Profinet diagnosis alarms are forwarded to application by packet interface.