Modbus TCP

Revision as of 01:49, 29 November 2019 by Rehak (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The Modbus/TCP is a Modbus variant used for communications over TCP/IP networks, typically connecting over port 502. Modbus is a serial communications protocol originally published by Modicon (now Schneider Electric) in 1979 for use with its programmable logic controllers (PLCs).

Modbus has become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices.

Modbus/TCP is implemented in NETIO products as M2M API protocol.

  • NETIO device is Modbus/TCP server (slave) sharing output states and energy measured values on the Bit / Bytes registers.
  • NETIO power outputs can be controlled with the Modbus/TCP protocol.
  • Power Outputs can be relays, power sockets 230V (NETIO 4 / NETIO 4All) or power outlets IEC-320 110/230V for NETIO 4C.

Modbus/TCP is an open M2M protocol designed for communication among various devices. The communication takes place by exchanging data messages between a client and a server in a master-slave mode.

Standard NETIO Modbus/TCP API

Download the Protocol description in PDF: NETIO Modbus/TCP API

AN27: Modbus/TCP with NETIO 4x – Control and measure LAN power sockets

The AN27 Application Note demonstrates how to control NETIO 4x smart sockets and PowerCable Modbus devices using the Modbus/TCP protocol. Modbus/TCP is the de-facto industry standard for connecting sensors and devices to PLCs, SCADA systems and smart home systems. NETIO products can be controlled over Modbus/TCP as 1-bit outputs (“coils”). In addition, values can be measured and advanced control is possible using registers.

Supported devices: