Introduction
It is possible to communicate with Robox controls in EtherNET/IP mode.
The data exchange modes and the DNSn.CFG configuration file are the same as DeviceNET.
The DNSn.CFG file must be present in the CAN_DIR or FB_DIR folder alias.
Communication can be done as follows:
•In dual Europa rack controllers (RBXM, ...) using the EthIP/PNET communication board (AS5040.001) from version RTE34.13.4
The name of the configuration file must be DNS0.CFG. In this case, the board should be inserted immediately to the right of the CPU.
NOTE: The EthIP/PNET board occupies one can channel.
•In the other uRmc2/uRmc3 controls communication can be done using one of the available Ethernet channels
The name of the configuration file must be DNS-1.CFG.
NOTE: In this case it is not necessary to specify the ip address. If it is specified it must correspond to one of the addresses assigned to the Ethernet devices present.
The Robox control will appear as a SLAVE type device within the EtherNET/IP protocol.
NOTE: From RTE 34.28.0 the NOP service is managed (check if the board is still available on the network).
Related arguments
Keywords EtherNET/IP
sys_flag.20 (0x100000) enable entry of information regarding communication into the report |
sys_flag.25 (0x2000000) enable report of outgoing messages from Robox |
sys_flag.26 (0x40000) enable report of incoming messages to Robox |
sys_flag.31 (0x80000000) disables EtherNET/IP message data dump, leaving only received/sent message reports |
FB_SLAVE_CFG masks the configured slave fieldbus channels |
