In many industrial projects, the field devices are not the problem.
They are already installed. They are already communicating. And in many cases, they have been doing their job reliably for years.
The problem usually appears later, when someone decides that all of this data now needs to be available through OPC UA.
That is when things start getting messy.
One device is using Modbus RTU. Another is on Modbus TCP. A power-related system may be using IEC104 or DL/T645. Building automation equipment may be communicating through BACnet/IP or BACnet MS/TP.
None of these protocols is necessarily a problem on its own.
The headache comes from having all of them in the same project.
Now the engineering team has to figure out how to bring data from different devices, different networks, and different communication methods into one upper-level OPC UA system — without turning the whole project into a collection of separate protocol-conversion jobs.
That is the kind of situation the BLIIOT BL121ML is designed for.
BL121ML can collect data from devices using Modbus RTU, Modbus TCP, IEC104, DL/T645, BACnet/IP, and BACnet MS/TP, while providing the collected data to the upper-level system through OPC UA.
That matters because real installations are rarely standardized from end to end.
A newer controller may already be connected over Ethernet, while older equipment is still working perfectly well on an RS485 network. Replacing those devices just to make the communication architecture look cleaner usually creates more work, not less.
BL121ML provides two Ethernet ports and two RS485/RS232 serial ports, so Ethernet and serial devices can be handled within the same gateway.
It supports data collection from up to 10 devices with 512 data points, which makes it a practical option when a project has several different field devices that all need to reach the same OPC UA platform.
And this is where integration projects often become more difficult than expected.
Connecting one device is easy.
Connecting one protocol is usually manageable.
But once you have several protocols, several devices, Ethernet and RS485 in the same cabinet, and one upper-level platform expecting a consistent interface, the complexity starts to grow very quickly.
The goal should not be to make every field device behave the same way.
The goal should be to make the integration layer simpler.
There is another issue that is easy to overlook during commissioning: what happens after the gateway has been installed?
A small configuration change months later should not automatically mean another site visit.
BL121ML supports remote configuration and remote firmware upgrades, and it also supports OpenVPN. For systems deployed across different buildings, factories, or customer sites, those capabilities can make ongoing maintenance much easier to manage.
The hardware itself is also built with cabinet installation in mind.
It supports 9–36VDC power input with reverse-polarity protection, hardware and software watchdogs, and an operating temperature range of -40°C to 85°C. The Ethernet and serial interfaces include ESD and EFT protection.
At only 30 × 83 × 110 mm, with DIN-rail or wall mounting, it does not take much space inside an existing control cabinet either.
But the real value of a gateway like this is not the number of ports or the size of the enclosure.
It is what happens when you stop treating every protocol as a separate integration problem.
If Modbus, IEC104, DL/T645, and BACnet devices are already doing their jobs, there may be no reason to redesign the field layer simply because the new platform wants OPC UA.
Sometimes the better approach is much simpler:
Keep the field devices.
Keep the existing communication networks.
And give all of that data one practical way to reach the OPC UA system.
That is exactly the role of the BLIIOT BL121ML.
