Active
Real-Time Ethernet systems are successfully used and further developed in many applications. Thus, the demands on the resources and functionalities of network controllers are increasing. netX 51/52 network controllers are based on the further developed netX 50 communication architecture which features considerably more internal storage capacity and additional function units. The hardware of netX 51 and netX 50 is compatible. netX 52 consists of the same silicon, but dispenses with an external memory bus and is more cost-effective due to its smaller housing. These three components are thus optimized for designing modular or compact slaves, or as a Real-Time Ethernet controller of a high-performance CPU. The communication channels meet all actual and future requirements of the PROFINET Specification V2.3, as e.g. ”Dynamic Frame Packing“. Moreover, the application of the new PHYs manufactured by Renesas ensures faster throughput times and expanded diagnosis properties.
In connection with a small QSPI Flash the internal memory of more than 670 KByte enables very compact solutions doubling the performance of the netX 50. For processing fast IOs, the application is provided with a second RISC CPU. It works in parallel to the ARM and significantly reduces the demands on the ARM software in case of short bus cycle times. Typical applications are IO-Link Master Gateways. When using gateways, the xPIC carries out the IO-Link data transfer so that the ARM is fully available for processing the transmission protocol to the master. A third Ethernet interface for connecting a PC for diagnosis and configuration purposes is implemented. Alternatively, it can also be used for connecting the netX to a host CPU. On this MII interface the netX will behave like a PHY.
Some Real-Time Ethernet systems use the CANopen object models or the same communication services as with Ethernet/IP and DeviceNet. This makes it necessary to connect CAN to the Real-Time Ethernet system as a “legacy network”. So far, this task required the use of the expensive netX 100 controller with its three communication channels. As an alternative, a dedicated CAN controller is available now.
Owing to these possibilities, the netX 51/52 is significantly more than just a Real-Time Ethernet interface chip equipped with a dual-port memory.
Product name | Part number | Brief description |
---|---|---|
NETX 51 | 2231.001 | Network controller for fieldbus and Real-Time Ethernet slaves with memory controller |
Product name | Part number | Brief description | |
---|---|---|---|
NXHX 51-ETM | 7763.200 | Development board | Show product |
NXLFW-COS | 7427.540 | Loadable Firmware CANopen Slave | Show product |
NXLFW-CCS | 7428.740 | Loadable Firmware CC-Link Slave | Show product |
NXLFW-DNS | 7427.520 | Loadable Firmware DeviceNet Slave | Show product |
NXLFW-DPS | 7427.420 | Loadable Firmware PROFIBUS DP Slave | Show product |
NXLFW-EIS | 7427.830 | Loadable Firmware EtherNet/IP Adapter | Show product |
NXLFW-OMB | 7427.860 | Loadable Firmware Open Modbus/TCP | Show product |
NXLFW-ECS | 7427.120 | Loadable Firmware EtherCAT Slave | Show product |
NXLFW-PNS | 7427.850 | Loadable Firmware PROFINET IO Device | Show product |
NXLFW-S3S | 7427.160 | Loadable Firmware Sercos Slave | Show product |
NXLFW-VRS | 7428.810 | Loadable Firmware VARAN Client | Show product |
NXLFW-PNS-IOT | 7427.853 | Loadable Firmware PROFINET IO-Device + OPC UA Server + MQTT Client | |
NXLFW-EIS-IOT | 7427.833 | Loadable Firmware EtherNet/IP Adapter + OPC UA Server + MQTT Client |
Product name | Part number | Brief description | |
---|---|---|---|
NETX 90 | 2270.000 | Smallest Multiprotocol SoC | Show product |
The right ASIC for every application. The Hilscher netX product family ranges from highly integrated and energy-efficent multiprotocol applications (netX 51/52/90) to high performance master applications (netX 100/500/4000), with the support of all common Real-Time Ethernet and fieldbus protocols.
Find all our current Media to Network Controller at our Media Archive.