Protocol connectivity
Modbus TCP SCADA Software and 3D Visualization
Kingfisher 3D SCADA connects industrial controllers over Modbus TCP so operators can build browser-based dashboards and 3D scenes without writing custom driver code.
* Representative project visualization
Protocol overview and design intent
Modbus TCP extends the classic Modbus register model onto Ethernet. Controllers expose holding registers, input registers, coils and discrete inputs through a well-known function-code interface. Plants choose Modbus TCP when they need predictable polling, vendor interoperability and low integration cost across PLCs, power meters, VFDs and remote I/O.
Search demand for “Modbus TCP SCADA software”, “Modbus TCP dashboard” and “Modbus TCP visualization” usually comes from teams that already own Modbus devices and need a modern HMI/SCADA layer. Kingfisher targets that gap: Ethernet discovery, register mapping and 3D binding in one no-code workflow.
Unlike proprietary Ethernet protocols that lock you into a single vendor toolchain, Modbus TCP is intentionally simple. That simplicity is why it remains the default “get data out of the machine” path for many OEMs and system integrators.
How Kingfisher connects
In Kingfisher you create a Modbus TCP channel, point it at the PLC or gateway IP and port (typically 502), then map registers into tags. Tags bind to 2D widgets or 3D model properties so live values drive color, motion and alarms.
- Add a Modbus TCP driver channel and enter the device IP, port and unit ID.
- Choose poll interval and timeout based on plant network load.
- Map holding/input registers and coils to project tags with scaling and engineering units.
- Bind tags to 3D components or chart widgets and validate online quality bits.
- Publish the scene to the browser runtime for operator access without installing a thick client.
Data types and addressing
Modbus addressing is register-centric. Holding registers (4xxxx style) commonly carry analogs and setpoints; input registers provide read-only process values; coils and discrete inputs cover boolean status. Word order and byte order matter when a 32-bit float spans two registers.
Kingfisher stores the mapping as first-class tags so the same Modbus point can feed a trend, an alarm rule and a 3D animation without duplicate polling.
- Function codes for read/write coils and registers
- Unit ID / slave ID selection for gateway topologies
- Scaling, offset and float/int interpretation per tag
- Quality and timeout handling for offline devices
Industries that rely on this protocol
Factories use Modbus TCP for line controllers and energy meters. Water plants poll pump VFDs and analyzers. District-energy sites gather heat-meter totals. Anywhere Ethernet reaches the cabinet, Modbus TCP is often the fastest path to a live dashboard.
- Discrete manufacturing lines and packaging machines
- Pump stations and treatment skids
- Building energy meters and secondary plant equipment
Known limits and engineering notes
Size poll rates per channel to your OT network design. Modbus TCP has no built-in security layer—place devices on controlled OT networks and use firewalls or secure gateways when exposing data beyond the plant.
Large contiguous register blocks are efficient; scattered single-register polls increase overhead. Plan map layout with your controls vendor when possible.
- No native encryption on classic Modbus TCP
- Register endianness must match device documentation
- Gateway unit-ID mistakes cause silent wrong-device reads