Anyone who’s worked on industrial integration knows that sending sensor data or equipment status from a production line to an MES or ERP system is rarely as simple as plugging in a PLC. Protocol mismatches, cybersecurity requirements, and the classic IT/OT communication gap keep coming up in real‑world projects.
A common scenario: a factory has a dozen Modbus RTU instruments scattered around. You need to collect all that data and make it available to an OPC UA client - a SCADA, an MES, or a cloud platform. The typical solution is to add an OPC UA gateway. But many gateways are either complicated to configure, expensive, or inflexible - the moment you need two more analog inputs, you’re looking at different hardware.
What the BL191 is: a configurable I/O box with a built-in OPC UA server
Hardware‑wise, the BL191 is a DIN-rail controller-compact, with the 3 slots version only 40mm wide. It runs Linux, has an embedded OPC UA server, supports Modbus RTU master mode, and accepts 1 to 3 Y series I/O boards.
You can choose the I/O mix you actually need: digital inputs/outputs, analog inputs/outputs, PT100 RTD inputs, thermocouple inputs, pulse counting, PWM output. Once you configure the parameters via the built‑in web page, the module automatically exposes the collected data as OPC UA nodes.
No coding, no extra client software - just a browser.
What the BL191 OPC UA EdgeIO Controller can do?
Turn legacy Modbus RTU data into OPC UA
Connect your RS485 devices - meters, drives, power monitors - to the BL191’s RS485 port. On the web configuration page, set up each device’s slave address, function code, and register start address. The BL191 then polls them automatically.
The collected data is mapped directly to OPC UA nodes. An OPC UA client like UaExpert - or any other client - can connect to the BL191’s IP address and port and read those values. Writing to a DO point works both ways as well.
Run simple local logic without relying on a PLC
The BL191 has built-in logic and conditional operations. Example: connect a temperature sensor to an analog input channel, then set up a rule on the web page: “when the temperature exceeds 50°C, close DO3 to start the fan.” This logic runs locally on the BL191 - even if the network goes down or the host system fails, the control action still happens.
You don’t need ladder logic or structured text; everything is configured through point-and-click on the web interface. For simple jobs like interlocking a packaging line’s start/stop or handling high/low level alarms on a storage tank, the BL191 works perfectly on its own.
How it compares to traditional solutions
Traditional chain: instrument → RS485 → serial server → industrial PC / gateway → protocol conversion → OPC UA server. Lots of components, many potential failure points, and an industrial PC running Windows - which means higher maintenance.
With the BL191 OPC UA EdgeIO Controller: instrument → RS485 → BL191 (built-in Modbus master + OPC UA server) → host system.
You skip the industrial PC or a dedicated protocol gateway. Configuration is done through a web page, so the person commissioning the system doesn’t need to know Linux commands or write any code.
When the BL191 makes sense - a cost-effective choice
What it’s not for
Of course, it’s not a universal cure. Complex motion control, high-speed interlocking, or heavy‑duty computation are still jobs for a PLC or an embedded computer. For those cases, consider BLIIOT ARMxy series embedded computers or EdgePLC.
The BL191’s role is clear: it’s the glue between OT and IT - reliably collecting field signals and sending them out as standard OPC UA, while handling simple local logic when needed.
For engineers working on digital transformation, equipment networking, or factory information integration, this module offers a clean, configurable, code‑free solution.
For more details, contact Beilai Technology for the BL191 OPC UA Edge I/O Controller datasheet.
