netRAPID 51 / 52

Owned by Christof Hunger
Last updated: 2023-08-04 by Simon Fischer
1 min read
Releases

The netX chip carrier netRAPID runs through a periodical system test. Usually this will be done with the release of a new product download package, which contains firmware, device driver, configuration tool, auxiliary tools and documentation. The comprehensive tests will ensure an optimal interaction between all components and results in a fixed assignment between latest hardware, firmware, device driver, bootloader and configuration tool.

If you are using a different combination and you are facing problems, please contact your local distributor or Hilscher support.


Current release:

For previous versions see version history.



Supported Hardware and Protocols

CC-Link IE Field Basic

Slave

EtherCAT

Slave

EtherNet/IP

Adapter

Modbus/TCP

Client/Server

POWERLINK

Controlled Node

PROFINET IO

Device

Sercos

Slave

NRP 52-RE(tick)(tick)(tick)(tick)(tick)(tick)(tick)
NRP 51-RE(tick)(tick)(tick)(tick)(tick)(tick)(tick)
Product Features


Host interfaceDiagnostic interface

SYNC0/1


Integrated
Webserver


Raw Ethernet (NDIS)6) 


TCP socket
interface 6)

Integrated
OPC UA Server
& MQTT Client 7)		Memory OptionsIntegrated
magnetics


SPM

DPM

USBUART
FLASHSDRAM














CC-Link IE Field Basic SlaveNRP 52-RE(tick)(tick)(tick)(error) 1)(tick) 1)(error)(error)(error)(error)4 MByte(error)(tick)
EtherCAT SlaveNRP 52-RE(tick)(tick)(tick)(error) 1)(tick) 1)(error)(error)(error)(error)4 MByte(error)(tick)
EtherNet/IP AdapterNRP 52-RE(tick)(tick)(tick)(error) 1)(tick) 1)(error)(error)(tick) 4)(error)4 MByte(error)(tick)

Modbus/TCP Client/Server

NRP 52-RE(tick)(tick)(tick)(error) 1)(error) 1)(error)(error)(error)(error)4 MByte(error)(tick)

POWERLINK Controlled Node

NRP 52-RE(tick)(tick)(tick)(error) 1)(tick) 1)(error)(error)(tick) 4)(error)4 MByte(error)(tick)

PROFINET IO Device

NRP 52-RE(tick)(tick)(tick)(error) 1)(tick) 1)(error)(error)(tick) 4)(error)4 MByte(error)(tick)

Sercos Slave

NRP 52-RE(tick)(tick)(tick)(error) 1)(tick) 1)(error)(error)(error)(error)4 MByte(error)(tick)














CC-Link IE Field Basic SlaveNRP 51-RE(tick)(tick)(tick)(error) 1)(tick) 1)(error)(error)(error)(error)4 MByte8 MByte(error)
EtherCAT SlaveNRP 51-RE(tick)(tick)(tick)(error) 1)(tick) 1)(error)(error)(error)(error)4 MByte8 MByte(error)
EtherNet/IP AdapterNRP 51-RE(tick)(tick)(tick)(error) 1)(tick) 1)(tick) 2)(tick) 3)(tick) 5)
(tick)7)4 MByte8 MByte(error)
Modbus/TCP Client/ServerNRP 51-RE(tick)(tick)(tick)(error) 1)(error) 1)(tick) 2)(error)(error)(error)4 MByte8 MByte(error)
POWERLINK Controlled NodeNRP 51-RE(tick)(tick)(tick)(error) 1)(tick) 1)(tick) 2)(error)(error)(error)4 MByte8 MByte(error)
PROFINET IO DeviceNRP 51-RE(tick)(tick)(tick)(error) 1)(tick) 1)(tick) 2)(tick) 3)(tick) 5)
(tick)7)4 MByte8 MByte(error)
Sercos SlaveNRP 51-RE(tick)(tick)(tick)(error) 1)(tick) 1)(tick) 2)(tick) 3)(tick) 5)
(error)4 MByte8 MByte(error)


Legend

1) Shared pins, means either SYNC 0/1 or Diagnostic UART can be used. SYNC 0/1 is activated as default. Can be changed via SSBL TAG-List.

2) The integrated WebServer is activated as default, but can be deactivated via Firmware TAG-List.

3) The NDIS functionality is deactivated as default, but can be activated via Firmware TAG-List.
   Real-Time Ethernet will be offered to the host in Channel 0, NDIS and TCP socket in channel 1 and in IoT communication in channel 2.
   Channel 1 (NDIS and TCP socket interface) and Channel 2 (IOT communication) can only be accessed in SPM host interface mode. In DPM host interface mode only Channel 0 (RTE) can physically be adressed

4) LWIP TCP stack is used, which has a different API (socket API) than the Hilscher  TCP stack.

5) Hilscher  TCP stack is used, which has a different API (HIL TCP API) than LWIP TCP stack.

6) NDIS and TCP socket interface can only be accessed in SPM host interface mode, because only Channel 0 can be physically adressed in DPM mode.

7) OPC UA Server and MQTT Client can only be accessed in SPM host interface mode, because only Channel 0 can be physically adressed in DPM mode. The firmware is obsolte and not recommended for new projects. New generation: netRAPID 90

To meet the different requirements of an embedded Design, two versions of netRAPID for Real-Time Ethernet will be offered

NRP 51-RE

 Extended Memory

  • Optimized for maximum functional possibilities
  • Without magnetics; need to be placed on the customer design
  • With SDRAM
  • DPM and SPM host interface mode

Enhanced communication & IOT-Ready

  • Real-Time Ethernet Slave communication
  • USB diagnostic
  • Integrated WebServer for firmware update (PNS, EIS, OMB, S3S, PLS)
  • In SPM mode:
    • TCP socket interface to the host
      (EIS, PNS, S3S)
    • Raw Ethernet (NDIS) interface to the host
      (EIS, PNS, S3S)
    • Integrated OPC UA server and MQTT client
      (PNS, EIS)

NRP 52-RE

 Minimum space

  • Optimized for minimum space requirements
  • With magnetics
  • Without SDRAM; sole usage of the netX 52 internal RAM
  • DPM and SPM host interface mode

Pure communication

  • Real-Time Ethernet Slave communication
  • USB diagnostic
Host interface channel structure of NRP 51-RE


Note1: Real-Time Ethernet will be offered to the host in Channel 0, NDIS and TCP socket in channel 1 and in future IoT communication in channel 2.

            Channel 1 (NDIS and TCP socket interface) and Channel 2 (IoT communication) can only be accessed in SPM host interface mode.

     In DPM host interface mode only Channel 0 can physically be adressed. There is no access to Channel 1 and Channel 2.


Note2:  netRAPID 51-RE owns 4 MAC addresses (MAC0 to MAC3), which will be provided per default from the Hilscher MAC address pool.

            MAC0 will be used for RTE communication in channel 0. MAC1 and MAC2 are reserved for Real-Time Ethernet. MAC3 will be used for Raw Ethernet.

            TCP socket in channel 1 and future IoT communication in channel 2 will use the same MAC0 and IP as the RTE communication.

            Raw Ethernet in channel 1 will use MAC3. IP address will be provided from the host application.



Documentation

Documentation about the products and tools can be found at:

More information on www.hilscher.com


News

Blog stream

Create a blog post to share news and announcements with your team and company.

FAQs

More FAQs ...