To completely enable the Modbus Connection on the TX Box 2, some things need to be connected as they are needed for a fluent communication between the TX Box and the Clients System.
In the following article, you'll find details on how to change the parameters to your own likening.
First, the system that wants to read the registers needs to be connected to X18 on the TX Box 2.
Inside the TX Box 2, you'll see that the Modbus Connection has been guided to a terminal block for easier connection access.
Make sure that the connections are correct, L1 = A+ and L2 = B-.
After the TX Box 2 is physically connected to the System, it needs to be configured onto the TX Cyberconsole.
To get access of the Cyberconsole first follow point 1.3 Connectivity with the Metacentre Cyber Console in the Software Manual.
With this you can access the Cyberconsole and adjust the parameters.
To adjust the parameters you need to be logged in as an Admin account.
The details to this account can be found under point 2.3 Default Accounts.
This guide explains how to enable and configure Modbus communication on the TX Box 2 so it can exchange data between your client system (Modbus Master) and devices on the Airbus485 network.
To fully activate the Modbus functionality on the TX Box 2, both hardware connections and software configurations must be completed.
Once connected and configured, the TX Box 2 acts as a Modbus Gateway, translating data between a Modbus RTU Master and the connected Airmaster or Metacentre devices.
Hardware Connection
- Connect your Modbus Master system to terminal X18 on the TX Box 2. Inside the TX Box 2, you’ll find a terminal block for convenient Modbus access.
- Wire the terminals as follows:
- L1 → A (+)
- L2 → B (−)

Ensure correct polarity (A+ / B−) to prevent communication faults.
Accessing the TX CyberConsole
To configure Modbus parameters, you’ll need access to the TX CyberConsole.
- Follow the steps in the Software Manual – section 1.3 “Connectivity with the Metacentre CyberConsole” to connect.
- Once connected, log in using an Admin account (credentials found under section 2.3 “Default Accounts”).
Configuring Modbus Parameters
After logging in as an Admin:
- Go to Settings.
- Open the Diagnostic menu.
- In the X0 tab, select Modbus.
You’ll now see the Modbus configuration screen.
Set the Port Function
If you want your system to connect to the TX Box 2, set the Modbus Port Function to: MODBUS Slave
This ensures the TX Box 2 listens for requests from your client system (the Modbus Master).
Adjust Communication Parameters
You can now modify other Modbus settings — such as baud rate, parity, and timeout — to match your system’s configuration requirements.
When finished, press the green Save button at the bottom of the page to apply the settings.
Once saved, Modbus communication on your TX Box 2 is active.
Understanding the TX Box 2’s Role
The TX Box 2 is not a Modbus Slave.
Instead, it acts as a Modbus Gateway that:
- Translates communication between a Modbus RTU Master and one or more Airbus485 slave devices.
- Cannot be polled directly by a Modbus Master.
- Simply forwards read/write requests to the correct device on the Airbus485 network.
Supported Devices
Devices on the Airbus485 network can include:
- Airmaster controllers
- Metacentre products
- Or a combination of both
Configuring Airbus485 Addresses
Airmaster products:
You can configure the Airbus485 address via the product’s own interface.
Refer to the individual Airmaster product manual for detailed instructions.
Metacentre Master Controllers & IO Boxes:
These units have fixed Airbus485 addresses that cannot be changed.
For a full list of Metacentre Airbus485 addresses, download the Modbus RTU Airmaster Metacentre Technical Manual and refer to:
- Page 17 – Section 2. “Metacentre System Network Addresses.”
You can find a link to the manual below.
You’ve now successfully set up and enabled Modbus communication on your TX Box 2.
It’s ready to act as a gateway between your Modbus Master and devices on the Airbus485 network.