Page tree
Skip to end of metadata
Go to start of metadata
Use Case
  • Slave application
netX51 is designed for slave application
  • Replacement
Pin Compatible to netX 50 -> direkt replacement
  • Stand Alone application
Has external memory controller for large applications
Supports PROFINET V2.3 with FSU, DFP, FFWD
  • IO-Link Gateway
Has internal IO-Link Controller and needs external manual
  • Development
netX 51 has a ETM trace interface, netX 52 not
  • SPI Host
netX 51 and 52 are able to be connected to a Host over SPI
More Information about netX 51
Development BoardsNXHX 51-ETM
Sales Information

Technical detailsOverview netX 51 / 52 and netX 90

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.

Block diagram