Equipment selection guide
Modbus Data Acquisition Gateway for Farm Sensors
Collect farm sensor and controller readings through Modbus. Plan register mapping, polling, MQTT delivery, timestamps and the storage needed during an outage.
Equipment and connection diagrams.
Compare individual equipment specifications ↓1. Purpose
Turn documented farm instrument registers into named readings in the receiving application.
2. Suitable sites
Irrigation panels, greenhouse controllers and several wired measurement points.
3. What to send
Send the device list, register maps, serial settings, update interval and the receiving application.
Choose equipment for your farm
Send the country, measurements, existing instruments, power and network, and where your team needs the readings.
When to use this guide
Choose the collector for the farm’s point list and receiving system. Distinguish the instrument measurement, polling, transmission and stored record.
Individual equipment specifications
Match the acquisition path to your existing equipment
A gateway can reuse the instruments already installed. Choose the field interface and receiving system before selecting the gateway version.

01
Existing RS485 instruments
Meters or sensors share a documented serial bus at a powered site.
- RS485 instruments
- Polling / protocol gateway
- Ethernet network
- SCADA or agreed endpoint
Equipment to compare
Before quotation: Provide device count, register maps, baud/parity groups, cable layout and the required upstream protocol. Check the selected gateway’s supported conversion and polling functions.
02
Contacts and analog measurements
The panel exposes mixed signals rather than one common register map.
- Digital / analog signals
- Matching remote I/O
- Gateway or controller
- Named and scaled data points
Equipment to compare
Before quotation: List the DI, DO and analog channels, signal ranges, isolation needs, panel power and any command authority. The module combination is selected from that point list.
03
A remote site without Ethernet
A pump station, well or field cabinet needs a cellular data path.
- Field devices / registers
- Compatible cellular RTU
- Operator network
- Your platform and offline rules
Equipment to compare
Before quotation: Confirm country, operator bands, SIM/APN, input count, supply and antenna location. Ask for model-specific recording and restart behaviour when data continuity matters.
These are configuration starting points. The quotation confirms the ordered models, versions, accessories, documentation and delivery terms. Send an equipment list or site photo if some details are still unknown.
Application interface example
A repeated rain report should not increase the rainfall total twice
A rain-station reporting request called for short-interval measurements, ten-minute summaries and retransmission after a lost connection. The receiving system needed to retain the original observation time and recognize the same measurement when it arrived again.
- 1
Rain measurement
Identify the observation interval and whether the value is an interval amount or a total.
- 2
Collection + delivery
Keep the measurement identity and observation time when a supported retry is sent.
- 3
Receiving check
Recognize a repeated observation before creating another historical record.
- 4
Rainfall history
Place the observation in its original interval; keep delayed delivery visible.
Four questions that change the integration
- Which time belongs on the chart?
- Use the original measurement time for the observation interval when the station supplies it. Keep reception time separately so a delayed upload is visible. A newly received report can contain an older measurement.
- Is this a new observation or a retry?
- Use the agreed stable observation identifier and station identity to recognize retransmission. Confirm whether the identifier survives a restart and how a new measurement is distinguished. Do not assume a delivery acknowledgement prevents duplicate database rows.
- What does the rain value mean?
- Keep short-interval amounts, ten-minute summaries and cumulative totals distinct. Summing overlapping summaries and interval values can count the same rainfall again. The agreed field definitions determine how the receiving system calculates and displays totals.
- What remains after power is lost?
- Ask which readings, timestamps and identifiers persist through a restart and how gaps are reported. A rechargeable supply or an online connection does not establish that unsent observations survive power loss.
Fields to review in the receiving record
This is a field checklist for the integration discussion. Use the selected station’s actual protocol for payload names and formats.
- Station + observation identity
- Which station measured it, and which observation is being delivered?
- Observation + reception time
- When was it measured, and when did the receiving system get it?
- Interval + value meaning
- Which period does the value cover, and is it an amount, summary or cumulative total?
- Unit + delivery state
- How is the value interpreted, and can a delayed or missing report be identified?
Use the same report to test a retry
The connection returns. What happens to the missing measurements?
A remote station keeps measuring while its cellular connection is unavailable. When the link returns, the dashboard receives a new value. That alone does not show whether readings collected during the outage were retained or delivered.
For Modbus-to-MQTT monitoring, select and test the field collection, local buffering and receiving database together. MQTT delivery settings describe message exchange; they do not create a local measurement archive. Confirm the selected gateway’s queue capacity, overflow behaviour and power-loss retention, then check how the receiver identifies delayed records and retries.
- Read Modbus point
- Local queue, if fitted
- MQTT delivery
- Receiving database
Compare the connection and the test
- Network unavailable; power remains
- Gateway question: Are measurements collected and queued?
- Receiver question: Can late records use their original observation time?
- Gateway loses power
- Gateway question: Is the queue persistent or only in RAM?
- Receiver question: How is the resulting gap represented?
- Queue fills
- Gateway question: Which records are removed or rejected?
- Receiver question: Is data loss visible to the operator?
- A delivery is retried
- Gateway question: Is there a stable observation identifier?
- Receiver question: Can the database recognize the repeated record?
Before choosing hardware: four connection checks

Product photograph
Pictured: SG-RTU-145 — Water Level Telemetry Terminal.
Collect the readings the farm team uses
Map documented registers from soil, water, weather instruments or controllers into named values with units and point identities. The selected gateway polls the required points and delivers them through its documented interface to the farm’s receiving system.
Choose the acquisition role
Use the existing sensor, meter or controller data when it supplies the required measurement. An RS485-to-Ethernet serial server transports serial traffic or performs its documented Modbus bridge role. A polling gateway collects and maps the points at the field end. Assign polling, scaling and record storage explicitly.
Register-map readiness
The most important preparation is a clean register map: device address, function code, register address, scale, unit and polling interval. This reduces commissioning time and avoids data interpretation errors.
Define the receiving interface
Keep the queue and its power-loss limit clear
Size storage from the collection schedule

Keep measurement, collection and delivery separate
Send the existing instruments’ register maps, serial settings and required update interval. Identify whether the farm system will poll the devices or whether the field gateway must collect, scale and publish the readings. Storage and recovery requirements are part of that choice.
Request a farm data-acquisition configurationSelection worksheet
Information that changes the gateway selection
Field devices
- What to provide
- Device list, quantity, Modbus RTU or TCP role and available register maps
- Why it matters
- Determines compatibility checks and how many device profiles must be mapped
- Confirm before quotation
- Supported device roles, data types, byte order and scaling
RS485 network
- What to provide
- Baud rate, parity, cable length, topology, device addresses and isolation needs
- Why it matters
- Determines serial-port count, segmentation, termination and isolation
- Confirm before quotation
- Port layout, electrical isolation and wiring constraints
Polling workload
- What to provide
- Registers per device, function codes, refresh interval, timeout and retry target
- Why it matters
- Determines whether the required scan cycle is practical
- Confirm before quotation
- Calculated polling cycle under the stated workload
Show the remaining worksheet rows
Key points
- Modbus RTU / TCP data collection
- RS485 gateway mapping for sensors, meters, PLCs and remote I/O
- Documented data handoff to customer-owned SCADA, BMS, MQTT or API endpoints
- Configuration and documentation support
Technologies
- Modbus RTU
- Modbus TCP
- RS485
- RS-485
- Ethernet
- BACnet
- MQTT
Related pages
Official technical references
Protocol specifications for the connections described in this guide.
FAQ
What does a farm data acquisition gateway collect?
It reads documented sensor, meter or controller points, maps them to names and units, and delivers them through the selected interface. The point list defines the instruments, polling and receiving-system requirements.
How is an RS485 instrument connected?
Match its electrical interface, protocol, address, serial settings and register map to the receiving port and polling function. Use the documented data path of the chosen gateway or serial server.
What is needed before Modbus gateway configuration?
A register map is the key input: slave address, function code, register address, data type, scale, unit and polling interval.
What is needed when a project uses Modbus RTU and TCP?
Specify both client/server roles, serial-port groups, polling workload and the receiving interface. Select the gateway or separate protocol bridge for that defined arrangement.
Is an RS485 serial server the same as a data acquisition gateway?
Not always. A serial server is the simpler choice for transparent serial transport or Modbus RTU-to-TCP bridging when the upstream system already handles polling and data interpretation. A data acquisition or edge gateway is required when the hardware must poll registers, scale values, publish structured payloads, use cellular backhaul or manage outage recovery.
Does every gateway support MQTT, BACnet, HTTP and CSV export?
No. Those are possible project requirements, not standard features of every model. Share the exact upstream protocol, role, authentication and data-format requirements so the selected gateway and firmware can be verified before quotation.
How many Modbus devices can one data acquisition gateway read?
There is no reliable answer from device count alone. Capacity depends on baud rate, points per device, function calls, response time, retries and the required refresh interval. Share the register maps and timing target so the polling cycle and serial-port layout can be checked before quotation.
What is the edge gateway’s MQTT queue limit?
The documented native-format MQTT queue holds up to 100,000 points in RAM. Power loss or restart clears the queue. Set the retention and recovery acceptance requirements for the selected arrangement.
What should I send for a data acquisition gateway quotation?
Send the device list, register maps, RS485 settings, required refresh interval, upstream protocol and role, backhaul, power, enclosure, target country, quantity and project timing. These inputs allow the polling workload and exact hardware configuration to be checked.
Can SunGene support distributor or integrator gateway programs?
Yes. SunGene supports distributors and system integrators with product selection, gateway configuration notes, documentation and delivery-ready project files.
Does MQTT QoS 1 prevent duplicate database rows?
No. QoS 1 permits redelivery. Use an agreed observation identifier and receiving-system deduplication where the application requires one stored row per observation.
Does a retained MQTT message provide historical logging?
No. A retained message holds the latest retained value for a topic. A measurement history needs a separate collection and storage arrangement.
Does a gateway keep queued records after power loss?
Use persistent storage when records must survive power loss. A RAM queue clears on loss of power or restart. Specify the required retention and verify it with a controlled restart and receiving-record export.
Get selection help
Tell us what you want to measure and where. Send a model number or site photo if you have one.

