Legacy Equipment Connectivity

The problem

Machines and instruments with RS-232 or RS-485 ports still run well but are invisible to modern systems, and replacing them only for connectivity is hard to justify.

Solution overview

MILESGO gateways collect data from legacy RS-232 / RS-485 instruments, machine HMIs and CNC controllers, HART field transmitters, run/stop and fault dry contacts over Modbus RTU / HART, and deliver it to SCADA, MES, a cloud platform (MQTT) as Modbus TCP / MQTT / OPC UA. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

legacy RS-232 / RS-485 instruments
machine HMIs and CNC controllers
HART field transmitters
run/stop and fault dry contacts

Protocol path

Modbus RTU / HART → Modbus TCP / MQTT / OPC UA

Implementation checklist for the project manager

Collect register maps and protocol documents from every equipment vendor early; a missing map is the most common delay.
HART instruments are read through the HART converter; list device addresses and variables for each loop.
RS-485: shielded twisted pair, daisy-chain topology, termination at both ends, up to 32 nodes per segment without a repeater.
For hard-wired signals, list each DI/DO/AI/AO with its type (dry contact, 4–20 mA, 0–10 V, PT1000) and choose I/O modules accordingly.
Commission in read-only mode first; enable write / control points only after the client approves each one.
Build and simulate the configuration off site (FAT) before installation to shorten time on site.

Project deliverables

Signed point table and protocol mapping
Gateway configuration files and backups
IP address plan and network drawing
FAT and SAT test records
As-built documentation and operator training

System architecture

Field layer: legacy RS-232 / RS-485 instruments, machine HMIs and CNC controllers, HART field transmitters, run/stop and fault dry contacts, connected over Modbus RTU / HART. Edge and integration layer: MILESGO protocol gateways and edge controllers, mounted on DIN rail in existing panels, polling each device, time-stamping values and buffering them locally. Upper layer: SCADA, MES, a cloud platform (MQTT), which receives the data as Modbus TCP / MQTT / OPC UA. Remote access for maintenance runs over VPN rather than open internet ports.

System composition

Field devices: legacy RS-232 / RS-485 instruments, machine HMIs and CNC controllers, HART field transmitters, run/stop and fault dry contacts
Edge / integration: MILESGO protocol gateways and edge controllers
Upper systems: SCADA, MES, a cloud platform (MQTT) (Modbus TCP / MQTT / OPC UA)
Tools and commissioning: Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

Software and AI capabilities

Point mapping assistance from uploaded register listsPilot

Delivery steps

1
Site survey and point list
Inventory devices, protocols, register maps, panel space, power and network paths.
2
Design and point table sign-off
Map every point to the target protocol and system; agree it with the client and the upper-system contractor.
3
Configuration and FAT
Build the gateway configuration off site, simulate it and test against the signed point table.
4
Installation and wiring
Mount gateways on DIN rail, wire RS-485 / I/O / Ethernet, apply the IP plan.
5
SAT and alarm tests
Verify values against local readings, test every alarm and command end to end.
6
Handover and support
Hand over configuration backups, point table and as-built documents; train operators.

Customer value

Monitoring added without changing existing control programs
Data ready for cloud platforms and analytics
Reliable trend data for optimisation and fault diagnosis
Open interfaces (BACnet, Modbus, OPC UA, MQTT, HTTP) avoid lock-in to one vendor

Tell us about your project

Send the protocols, point count and target system. A sales and engineering pair reviews every submission.

Discuss Your Project