In this article, we will use Phoenix Contact’s Ethernet Coupler AXL F BK ETH EF to connect to Mitsubishi’s FX5U via ModbusTCP.

Let’s get started.

AXL F BK ETH?

The AXL F BK ETH bus coupler can be used within a Modbus/TCP (UDP) network. The bus coupler creates a link to the Axioline F I/O system and the industrial I/O signals connected to it.Up to 63 Axioline F devices can be connected to the bus coupler.

Two Ethernet ports (built-in switch)
10 Mbps and 100 Mbps transmission speeds
Rotary coding switch for configuring IP address assignment and other features
Firmware updates available
Axioline F local bus cycle time is approximately 10 μs.
Web-based management

Internal Circuit

Here is an internal view of AXL F BK ETH.

Power Supply

This is the AXL F BK EIP EF power supply.

Wiring Exmaple

Here is an example of AXL F BK EIP EF wiring.

Rotary encoding switches

Rotary encoding switches can be used to set address assignment and other functions.Note that the bus coupler must be restarted after changing the switch position, since the switch position change is not reflected during operation.

Plug and Play mode

The Plug and Play switch for the AXL F BK EIP EF is located below the marking field at the top of the bus coupler.

Switch position 1A: Enables plug-and-play mode
- Process data write is denied, read is allowed.
Switch position 1B: Deactivates plug-and-play mode
- The bus will only start if the configuration of the connected bus matches the saved configuration.

In Plug and Play mode, local bus modules connected in the field can be activated using the bus coupler without a host computer (engineering system).

The reset button has two functions:

Reboot bus coupler
Reset default settings

Service Interface

The AXL F BK EIP EF service interface is located below the top marking field of the bus coupler.Using its service interface, a USB connection can be made between the bus coupler and a PC running the startup/diagnostic tool with Startup+ software.

Startup+ includes the following features

Station I/O Module Parameterization
I/O Checks
Module Diagnostics

Modbus protocols and registers

The AXL F BK ETH supports Modbus/TCP and Modbus/UDP servers.

Modbus connections

The bus coupler supports up to 8 simultaneous Modbus/TCP connections and can access different addresses simultaneously. 8 connections are supported, allowing connections to be restored quickly.

Modbus function codes

AXL F BK The following function codes are supported:

Mapping

This is a Mapping of AXL F BK ETH.

Implementation

STARTUP+

Download

Startup+ allows you to quickly and easily establish a connection to an Axioline F station, configure the connected modules, and check the wiring (I/O check).

You can download Start+ from the Phoenix Contact website (free of charge).

https://www.phoenixcontact.com/en-pc/products/software-startup-2700636

Also, include the DMT Catalog Update File in the Download.

Installation

Launch the Setup File downloaded earlier, select the installation language, and press OK to proceed.

Proceed with Next.

Accept the license and proceed with Next.

Proceed with Next.

Start installation.

Please wait a moment…

Done!

Launch Startup+

Launch Startup+.

The User Login screen will appear, and if you use the “Use Windows login for this user” option, you do not need to register as a user.

Create new Project

Create a new project with Create new project.

Select AXL F BK ETH for use in this article.Select the AXL F BK ETH to be used in this article.

In this case, the rotary switch for AXL F BK ETH has been set to 00, so the IP address has been reconfigured.

Click on the IP Address item in the AXL F BK ETH Coupler displayed on the search screen to change the IP, etc.

When IP configuration is complete, click the Send button to transfer the settings to Coupler.

Done!

Proceed with Next>.

Next, the Topology Scan screen appears, automatically searching for modules installed in the AXL F BK EIP.

Done!

Project creation is now complete.

Finish to complete.

Done!

DTM-Catalog Update

In some cases, you may need to update the DTM, so click Tools>DTM-Catalog Management.

Click on Search for installed DMTs.

The DTMs now installed are listed and the All button is clicked.

Finally, update the DTM Catalog with Update Catalog and close.

Configure IOL4

Change Operation Mode to IO-Link and set the number of PO IN and PO OUT bits to match the actual IO-Link device connected.

Download

Connect the tool and AXL F BK EIP with Device>Connect.

Click on Parameter Download to download your project to AXL F BK EIP.

Some Information About IOL4

The following example shows how to wire AXL SE IOL4 to INPUT/OUTPUT/IOLINK Port.

Process data

Process data is in Big Endian Format, up to 64 Bytes of Process data in cycle communication.Within those 64 Bytes, 6 Bytes of IO-LINK Master data are included, meaning that up to 58 Bytes of Process data can be exchanged with IO-LINK.

IN Process Data

This is the Mapping of the input Process data 64Bytes.

Byte0 Status of the IO-Link Connection For each IO-Link Port

This data indicates the status of each IOL Port in Bits.

True=Port is operating as IO-LINK Mode and IO-LINK Device is detecting it.

False=IO-LINK communication is not established.

Byte1 Status of the IO-LINK input process data for each port

The data can be used to check if the process data between the corresponding IO-LINK Port and IO-Device is valid or not.

True=Input Process data of the corresponding IO-Link Port is valid and available.

False=Input Process data for the corresponding IO-Link Port is invalid and cannot be used.

Byte2 Status(Level) of the C/Q Cable for each IO-Link Port

The meaning of that data changes depending on whether the Mode in which the Port is running is Input or IO-Link.

DI (Input) True: Input is ON.(>13V)
IOL(IO-LINK) True:Port has 13V or more, but communication has not been established with IO-Link devices.

Byte3-5 Reserved

That data is not used.

Byte6-63 Input Process data

Here is the input data from the IO-LINK Devie for each of the upcoming 58 Bytes Ports.If the IO-LINK Devie you are connecting to has less proecss data than 58 Bytes, all the extra Bytes will be 00h.

Out Process Data

This is the Mapping of the output Process data 64 Bytes.

Byte0-1 Reserved

That data is not used.

Byte2 Set point(level) of the C/Q Cable for each IO−Link Port

If the corresponding Port operates as Digital output mode, Output=1 when True.

Byte3-5 Reserved

That data is not used.

Byte6-63 Output Process Data(User data) of IO-Link Ports

This is the output data from the IO-LINK Devie for each 58 Bytes Port.If the IO-LINK Devie you are connecting to has less proecss data than 58 Bytes, all the extra Bytes will be 00h.

Web Server

Next, let’s access the AXL F BK ETH web server.

Modbus Register Overview

ModbusTCP(UDP)>Modbus Register Overview for a list of Coupler’s registers.

Modbus I/O Table

ModbusTCP(UDP)>Modbus I/O TableLists the modules installed in each Slot.

Startup Behaviour

Configuration>Startup Behaviour to configure Coupler to start.

First, disable Plug and Play Mode.

Set the Watchdog time in Process Data Watchdog according to your application.

FX5U Side

Now set the Mitsubishi FX5U side.

Configure Ethernet Port

Open FX5UCPU>Module Parameter>Ethernet Port.

IP Address

Base Settings>IP Address>Match the IP address of the FX5U to the application.

Simple CPU Communication

Since we will start Modbus TCP Client on the FX5U CPU, open the Simplate CPU Communication Settings.

Then, set “To Use or Not to Use Simple CPU Communication” to Use, open the Detailed Setting, and configure the detailed settings.

Configure access settings for Modbus TCP Server.

The Communication Pattern should be set to Read or Write.

For Socure, you can set the Modbus TCP Server you wish to access.

Set Device Type to “MODBUS/TCP-compatible device”.

Next, set the memory address, Input Register, and Output Register to be associated with FX5U in Word Device.

In the figure below, this is how it was set up.

Transfers 32 Word data from D5000 to Modbus TCP Server to access Input Register from 8000 to 8031.
Write 32 Word data from D5100 to Holding Register 9000 to 9031 of Modbus TCP Server.

Program

Here is a simple program to control Nass magnet’s IO-Link device.

X100:=D5000.0; //Status of the IO-Link Connection,port0
X101:=D5000.1; //Status of the IO-Link Connection,port1
X102:=D5000.2; //Status of the IO-Link Connection,port2
X103:=D5000.3; //Status of the IO-Link Connection,port3
X104:=D5000.8; //Status of the IO-LINK input process data,port0
X105:=D5000.9; //Status of the IO-LINK input process data,port1
X106:=D5000.A; //Status of the IO-LINK input process data,port2
X107:=D5000.B; //Status of the IO-LINK input process data,port3

X110:=D5001.0; //Status(Level) of the C/Q Cable,port0
X111:=D5001.1; //Status(Level) of the C/Q Cable,port1
X112:=D5001.2; //Status(Level) of the C/Q Cable,port2
X113:=D5001.3; //Status(Level) of the C/Q Cable,port3

X114:=D5004.8; //Valve State
X115:=D5004.9; //Short-Circuit Detection
X116:=D5004.A; //Open-Circuit Detection
X117:=D5004.B; //Overheat alert
X120:=D5004.C; //Overcurrent alert
X121:=D5004.D; //Counter1 overun
X122:=D5004.E; //Counter2 overrun

X123:=D5011.8;
X124:=D5011.9;

IF SM402 THEN
D5051.0:=FALSE;
END_IF;

D5103.8:=Y100;
D5103.9:=D5052.0;
D5103.A:=D5052.1;
D5103.B:=D5052.2;
D5103.C:=D5052.3;
D5103.D:=D5052.4;
D5103.E:=D5052.5;
D5103.F:=D5052.6;