Skip to content
SunGeneAgricultural IoT
All comparisons

Farm equipment selection

Modbus RTU or TCP for Farm Sensors and Controllers?

Connect farm meters, sensors and controllers through documented Modbus registers. Compare serial wiring, Ethernet access and the gateway functions your system needs.

Choosing equipment for your farm?

Send your country, measurement points and existing equipment. We can quote an individual device or prepare the sensors, power and data connection for a farm monitoring point.

Hardware in this guide

Product-family illustrations. See each product page for specifications and options.

Plan the connection at your farm

Planning example: read irrigation meters on an existing serial bus and hand the agreed values to a farm system over Ethernet. Record each device address and register interpretation before selecting the gateway.

  1. 1

    Farm meter or controller

  2. 2

    Registers and data types

  3. 3

    Matching serial or Ethernet interface

  4. 4

    Receiving system and units

At your site

Start with the interface on the existing farm instrument. Serial Modbus RTU and Modbus TCP carry application data through different transports. A matching gateway can connect them, while the register map, data types, scaling and access rules still need to agree.

Decision table

Instrument interface

Modbus RTU
Modbus RTU over the documented serial interface
Modbus TCP
Modbus TCP over the selected IP network
Guidance
Match the physical connection and device settings to the instrument documents.

Register meaning

Modbus RTU
Address, function, data type, scaling and polling interval
Modbus TCP
Addressing, unit identifier and the receiving register requirements
Guidance
Transport conversion does not define the measurement units or register interpretation.

Gateway work

Modbus RTU
Read the existing serial instruments where local polling is required
Modbus TCP
Expose or read the agreed TCP interface
Guidance
Specify transparent transport, protocol conversion, polling and record creation as separate functions.

Equipment in the system

Example equipment arrangement. Check compatibility and agree who handles software, PLC/SCADA programming and site installation.

Existing field equipment

Confirm the device signals, electrical interface and register map before selecting the gateway.

Data destination

Customer platform or an agreed third-party service

Implementation checks before choosing RTU or TCP

Changing the transport does not settle the device-level details. Confirm these items before selecting a converter or gateway.

01

Media and topology

For RTU, confirm two-wire or four-wire RS485, cable length, termination, biasing and device count. For TCP, confirm the LAN, IP plan, routing and access to the required service port.

02

Device identity

Record every serial device address and decide how the gateway will map it to the upstream unit identifier. Do not assume the default mapping fits every SCADA driver.

03

Register semantics

Confirm function codes, address notation, data types, byte and word order, scaling and write permissions. A transport conversion does not correct an incomplete register map.

04

Serial timing

Match baud rate, parity and stop bits, then set turnaround delay, polling interval, timeout and retry limits for the slowest field device.

05

TCP connection model

Confirm how many upstream clients may connect, whether connections stay open and whether the gateway serves live polls or cached values.

06

Failure and stale-data handling

Define how timeouts, Modbus exception responses and stale values are exposed, including timestamp or quality information needed by the receiving system.

Existing farm equipment panel and a separate low-voltage measurement collection box

Application illustration. List the available instrument outputs and controller inputs before choosing the data connection.

Connect the existing farm instruments

Match the instrument outputs to the collector inputs and the interface used by the farm system. Include the existing equipment labels or register maps with the request.

Request farm equipment

Choose Modbus RTU when

  • Existing instruments expose the required serial Modbus registers
  • Serial settings, wiring and power can be matched
  • The collector performs the required local polling

Choose Modbus TCP when

  • The instrument or receiving system requires Modbus TCP
  • The selected equipment supports the required client or server role
  • Register meaning and network access are documented

Information needed for quotation

  • Instrument model and register map
  • Serial settings or Ethernet arrangement
  • Values, units and polling interval
  • Receiving-system protocol and access requirements
Farm monitoring plan with measurement points, mounting parts and equipment samples

Application illustration. Mark the measurement points, power and cable routes on a farm layout for an equipment request.

Record the interface and data requirements

Mark the measurement points, field power and receiving system on a farm layout. Include equipment already in use and the number of points to be added.

Request farm equipment

Official technical references

Related pages

FAQ

Will a serial-to-Ethernet converter create the farm data records?

A transparent converter transports serial data. Polling registers, interpreting values and creating records are additional functions. Specify which equipment performs those tasks and how the receiving system reads the result.

What should I send for an equipment quotation?

Send the country, measurements, equipment already on site, available power and the system receiving the data. Add a site sketch or instrument photo and the approximate point count.

Can I buy individual devices or request a complete farm monitoring point?

Yes. A device request can cover a missing measurement or connection. A complete point brings together the instruments, matching inputs, power, enclosure and agreed data connection, with local installation responsibilities set out in the proposal.

What should be checked before adding more farm sites?

Compare the field readings with the records received by the platform. Check units, timestamps, interruptions and recovery, then record the equipment configuration and the team responsible for service.

Does an RTU-to-TCP gateway change the register map?

Usually the gateway transports or maps requests; it does not make an incomplete register definition correct. Confirm unit identifiers, address offsets, data types, byte order and scaling. If remapping is required, state it before hardware selection.

What should I send before requesting an RS485 or Modbus gateway quote?

Send the device model, register map, function codes, serial settings, device count, bus layout, polling interval, upstream client count and network requirements. A sample readout is useful when available.