- Slave application
- Replacement
- Stand Alone application
- PROFINET V2.3
- IO-Link Gateway
- Development
- SPI Host
Protocol | Master | Link | Slave | Link |
---|---|---|---|---|
As-Interface | ![]() | AS-Interface Master | ![]() | - |
CANopen | ![]() | CANopen Master | ![]() | CANopen Slave |
CC-Link | ![]() | - | ![]() | CC-Link Slave |
DeviceNet | ![]() | DeviceNet Master | ![]() | DeviceNet Slave |
EtherCAT | ![]() | EtherCAT Master | ![]() | EtherCAT Slave |
Ethernet/IP | ![]() | EtherNet/IP Scanner | ![]() | EtherNet/IP Adapter |
OpenModbus TCP | ![]() | Open Modbus/TCP | ![]() | Open Modbus/TCP |
Powerlink | ![]() | - | POWERLINK Controlled Node | |
PROFIBUS | ![]() | PROFIBUS DP Master | ![]() | PROFIBUS DP Slave |
PROFINET | ![]() | PROFINET IO-Controller | ![]() | PROFINET IO-Device |
Sercos | ![]() | Sercos Master | ![]() | Sercos Slave |
Description | Link |
---|---|
Development Boards | NXHX 51-ETM |
Sales Information | |
Technical details | netX overview |
For processing the fast I/Os, the application is provided with a second RISC CPU. It works in parallel to ARM and significantly relieves the demands made on the ARM software via short bus cycle times. Typical applications are IO-Link Master Gateways. The xPIC takes over the IO-Link data transfer, leaving the ARM completely available for processing the transmission protocol to the master.
Some Real-Time Ethernet systems use the CANopen object models or the same communication services such as EtherNet/IP and DeviceNet. This results in the task of connecting CAN as the „legacy“ network to the Real-Time Ethernet system. Up to now, that entailed using an expensive netX 100 controller, with its three communication channels. As an alternative, a dedicated CAN controller is now available. With this possibility, the netX 6 / 51 / 52 is so much more than just a Real-Time Ethernet interface chip equipped with a dual-port memory.