PROFINET IO IRT Device

Drag and click to vote!

Supported Protocols:

Subject	Data
Technical Data	Maximum number of total cyclic input data: 1440 bytes Maximum number of total cyclic output data: 1440 bytes Acyclic communication: Read/Write Record, max. 1024 Bytes/Telegram Alarm Types: Process Alarm, Diagnostic Alarm, Return of Submodule Alarm, Plug Alarm (implicit), Pull Alarm (implicit) DCP Topology recognition: LLDP, SNMP V1, MIB2, physical device VLAN- and priority tagging Context Management by CL-RPC Minimum cycle time: 1ms for RTC1 & RTC2; 250µs for RTC3 with netX100/netx500 and 1ms for RTC3 with netX50 Baud rate: 100 MBit/s Data transport layer: Ethernet II, IEEE 802.3
Limitations	RT over UDP not supported Multicast communication not supported Only one device instance is supported DHCP is not supported IRT “flex” (synchronized RT Class 2) is not supported Media Redundancy (except MRP client) is not supported Access to the submodule granular status bytes (IOCS) is currently not supported if the application accesses the stack using the INX image interface. The amount of configured IO-data influences the minimum cycle time that can be reached. Supervisor-AR is not supported. DeviceAccess-AR is not supported. Only 1 Input-CR and 1 Output-CR are supported Using little endian byte order for cyclic process data instead of default big endian byte order may have an negative impact on minimum reachable cycle time
Version	Revision: Date: 19.11.2010 Status: Beta

Subject

Data

Technical Data

Maximum number of total cyclic input data:
1440 bytes

Maximum number of total cyclic output data:
1440 bytes

Acyclic communication:
Read/Write Record, max. 1024 Bytes/Telegram

Alarm Types:
Process Alarm, Diagnostic Alarm, Return of Submodule Alarm, Plug Alarm (implicit), Pull Alarm
(implicit)

DCP

Topology recognition:
LLDP, SNMP V1, MIB2, physical device

VLAN- and priority tagging

Context Management by CL-RPC

Minimum cycle time:
1ms for RTC1 & RTC2;
250µs for RTC3 with netX100/netx500 and
1ms for RTC3 with netX50

Baud rate:
100 MBit/s

Data transport layer:
Ethernet II, IEEE 802.3

Limitations

DHCP is not supported
IRT “flex” (synchronized RT Class 2) is not supported
Media Redundancy (except MRP client) is not supported
Access to the submodule granular status bytes (IOCS) is currently not supported if the
application accesses the stack using the INX image interface.
The amount of configured IO-data influences the minimum cycle time that can be
reached.
Supervisor-AR is not supported. DeviceAccess-AR is not supported.
Only 1 Input-CR and 1 Output-CR are supported
Using little endian byte order for cyclic process data instead of default big endian byte
order may have an negative impact on minimum reachable cycle time

Version

Revision:

Date: 19.11.2010

Status: Beta

Issue Tracker Blog Wiki

To download software on industrialNETworX.com you need to fill out the following fields in your profile:

industrialNETworX