The AXL_F_BK_ETH coupler allows management of the Axioline modules connected to it, via the Modbus/TCP protocol.

Axioline modules connected to the coupler are called remote and are managed up to 63 modules per coupler. For proper functioning, the Control and the Coupler must be in the same IP network.

Connections between Control and Coupler can be:

•connection via direct Ethernet cable (through a network device, switch or other)

•connection via Wi-Fi between Control and one or more Wi-Fi stations, plus an Ethernet connection via Wi-Fi station. In the case of using a control from the RP-2 family, the built-in Wi-Fi interface can be used.

Control and coupler must be in the same IP network to work properly. You can set the IP address of the coupler via rotary switch or via web server. Via the two rotary switches S1 and S2 on the front of the coupler, a static IP address between 192.168.0.1 and 192.168.0.50 can be configured. While via web server, any address can be imposed.

The coupler, to work properly, needs to know which modules are connected to it. If the configuration saved in memory does not match the actual configuration, the coupler will go into alarm and data exchange cannot be started. To save a module configuration on the coupler, rotary switches or the web server interface can be used.

To parameterize a module, then write "Application Objects" that change the module's behavior, you cannot use R3 functions or shell commands (axio_robj/axio_wobj). The only way is to use the "Startup+" program that Phoenix Contact provides.

To configure the Robox control to handle remote modules, you must flash-load the PCMBC.CFG file. Remote Axioline modules should not be entered in the Hardware configuration.