|
|
|
| Like for fieldbus systems, Ethernet based communication systems provides different
solutions and have their specific technically approaches. Device manufacturers need to make themselves familiar with the new technology, evaluate pros and cons of each
system and decide what can be used best for their application or product.
In some instances, the market makes the decision and the device manufacturer is forced
to create test scenarios with multiple network nodes in a real-world system.
The slave devices used in this network should be easy to use, inexpensive and flexible like the NXIO board. The NXIO is a digital IO board for all Ethernet based fieldbus system and utilizes networX on chip. It is easy configurable through an exchangeable MMC card.
|
|
|
|
|
|
|
| Facts at a glance: |
| One PC Card for all Real-time Ethernet Systems |
| One PC Card that runs Master and Slave Protocols |
| Data Exchange via Dual-Port Memory (DPM) or Direct Memory Access (DMA) |
| Unified User Interface for Various Protocols |
| PCI or PCI Express |
| Ten-year Commitment of Availability |
| SyCon.net Configuration Tool based on FDT/DTM Technology |
|
|
|
| Product
|
CIFX 90-RE\F
|
|
|
|
| EtherCAT Slave
|
|
|
|
| Cyclic Data
|
max. 400 Bytes
|
| Acyclic Data
|
SDO Master/Slave
|
| SDO Slave/Slave
|
| Functions
|
3 FMMUs and 4 SYNC-Manager
|
| COE (CANopen over Ethernet)
|
| Complex Slave
|
| Emergency
|
|
|
|
| EtherNet/IP Adapter
|
|
|
|
| Cyclic Data
|
max. 1008 Bytes
|
| Unscheduled Data
|
max. 1400 Bytes per Telegram
|
| Functions
|
Cyclic Connection
|
| DHCP, BOOTP
|
| one E/A Connection
|
| max. 8 Connections
|
| UCMM supported
|
| Server Services
|
Get_Attribute_All
|
| Get_Attribute_Single
|
| Set_Attribute_All
|
| Set_Attribute_Single
|
|
|
|
| PROFINET IO Device
|
|
|
|
| Cyclic Data
|
max. 2048 Bytes (IOCR)
|
| Acyclic Data
|
Read/Write Record, max 1024 Bytes/Telegram
|
| Functions
|
Context Management over CLRPC
|
| DCP
|
| Process- and Diagnostic Alarm
|
| 1 Submodul
|
| Diagnostic, max 200 Bytes/Telegram
|
| max. 244 modules
|
| variance comparison of the configuration
|
| VLAN- and Priority-Tagging
|
|
|
|
| Modbus TCP/IP Server
|
|
|
|
| Function code
|
1,2,3,4,5,6,15,16
|
| Register (16-Bit)
|
max. 120 or 125 Register per Telegram
|
| Coil (1-Bit)
|
max. 1968 or. 2000 Coils per Telegram
|
| Message Modus
|
In/Out-Data Image not used
|
| Server
|
| I/O-Modus Server
|
max. 11520 Byte E/A Data
|
|
|
|
| SERCOS III Slave
|
|
|
|
| Realtime Data
|
max. 2800 Bytes
|
| Acyclic Data
|
Service Channel Read/Write/Standard Kommands
|
| Functions
|
Max. 8 Subdevices
|
| Phase Run Up
|
| Ring and Line Topology
|
| Synchronization
|
| Version
|
V1.1
|
|
|
|
| EtherCAT Master
|
|
|
|
| Cyclic Data
|
max. 11520 Bytes
|
| Acyclic Data
|
CoE (CANopen over EtherCAT)Up-/Download
|
| Functions
|
Emergency
|
| Get OD List
|
| Topologie: Linie
|
|
|
|
| EtherNet/IP Scanner/Master
|
|
|
|
| Cyclic Data
|
max. 11520 Bytes
|
| Unscheduled Data
|
max. 504 Bytes per Telegram
|
| Functions
|
Cyclic Connection
|
| DHCP, BOOTP
|
| max. 64 Connections
|
| UCMM supported
|
| Client Services
|
Get_Attribute_Single/All
|
| Set_Attribute_Single/All
|
|
|
|
| PROFINET IO Controller
|
|
|
|
| Cyclic Data
|
max. 6144 Bytes
|
| acyclic data
|
Read/Write Record, max. 4096 Bytes/Request
|
| Functions
|
Alarm Handling
|
| Context Managment over CLRPC
|
| DCP
|
| max. 32 Devices
|
| minimum cycle time 1 ms
|
| Pro Device one Puffer available for Diagnostic Data
|
|
|
|
| PowerLink Controlled
|
| Node/Slave
|
|
|
|
| Cyclic Data
|
max. 2980 Bytes
|
| Acyclic Data
|
SDO Up-/Download
|
| Functions
|
SDO over ASND and UDP
|
| Poll Request/Response
|
Response Time 1?s
|
| Version
|
V2
|
|
|
|
| Technical Data
|
|
|
|
| Interface
|
PCI, 33 MHz DPM or DMA
|
| Operating Temperature
|
0..55°C
|
| Operating Voltage
|
3.3 V / max. 650 mA
|
| Dimensions (L x W x H)
|
60 x 45 x 4.5 mm
|
|
|
|
|
|
|
