Modbus Function 16 Succeeded? Verify a Fresh Register Read-Back
A commissioning tool reports that a Modbus write succeeded, but the handover record contains no independently read value. That leaves an avoidable gap. A normal Function 16 response identifies the register block written; it does not return the contents of that block. Use the response to check the transaction, then obtain a fresh read-back where the device supports it.
This distinction is useful when configuring instruments through a serial adapter, PLC or communications converter. Keep three questions separate: did the server report a successful write, what value can now be read, and has the application behaved as intended? Each needs its own evidence.
Read the response according to its function
Section 6.12 of the Modbus Application Protocol Specification V1.1b3 defines Function 16, hexadecimal 0x10, for writing contiguous registers. The normal response contains the function code, starting address and quantity of registers written. Unlike the request, it contains no register-value field. A displayed quantity of two therefore means two registers, not a returned process value of two.
For a supported holding-register read, Function 03 is the separate operation to consider. Check the exact instrument manual before choosing addresses, decoding values or assuming that a written parameter has the same readable representation. The protocol format does not supply a manufacturer’s register map or parameter meaning.
A converter adds another boundary to verify
Dragino documents the RS485-LN as a converter that issues user-defined serial commands and processes returned bytes for its LoRaWAN payload. Its documentation also distinguishes one-off device configuration using AT+CFGDEV from commands used during sampling. That makes the serial instrument’s response an important boundary: a wireless message or a successful command submission should not be substituted for the actual device evidence.

Confirm the installed hardware, firmware and applicable manual before using a configuration method. The photograph illustrates the communications device, not a tested installation. This guide does not establish that every connected instrument supports Function 16 or that a proposed ProSight integration is already available.
Recognise an acknowledgement without treating it as data
Hypothetical simulator example: a write starts at protocol address 0x0020 and covers two registers. A normal response PDU is 10 00 20 00 02. Read it as function 0x10, starting address 0x0020 and quantity 0x0002. Those final bytes are not the two values that were requested. This is a protocol illustration, not a command to send to a field instrument; no device-specific parameter is assigned to that address.
Build a test record with separate columns for requested values, write response and fresh read-back. Leave the read-back column unverified until a new read actually supplies the expected values. Copying the request into that column would only show what the software intended to send.
Plan an authorised acceptance test
1. Choose a safe test target. Use a simulator or an isolated spare with an approved configuration procedure. Do not experiment with production setpoints, motor commands, protection settings or outputs. Application-specific design and validation remain the responsibility of competent people.
2. Preserve the starting state. Record the exact model, firmware, register-map revision, device identity and original readable values. Identify the approved writable block and its permitted range. Check whether the manufacturer requires an unlock, commit operation or other procedure; leave that question open if the manual does not resolve it.
3. Capture the complete exchange. Retain the request and matched response with timestamps. Check the returned starting address and quantity against the intended operation. Preserve exceptions and timeouts as distinct outcomes. A tool’s green success badge is useful only when its definition of success is understood.
4. Request fresh evidence. Where supported, read the relevant holding registers after the documented processing interval. Confirm the response belongs to the intended device and decode it using the applicable map. Avoid a cached display or a local copy of the requested value.
5. Check the application requirement separately. If the purpose is a display configuration, verify the display. If persistence matters, follow an approved manufacturer procedure to test it. An immediate read does not by itself prove retention through a restart. Restore temporary settings and document any untested requirement.
Make failures useful for support
Common mistakes include interpreting the echoed register count as data, reading the wrong address basis, accepting a cached dashboard value and repeatedly sending writes when the outcome is uncertain. Stop and reconcile the evidence before another authorised change; a retry policy needs to account for the meaning of the target parameter.
Send ProSense a sanitised request/response trace, exact instrument and converter models, register-map reference, expected values and observed read-back. Exclude credentials and device keys. State which requirement remains unverified so support can distinguish a protocol interpretation problem from a device configuration or application problem.
Need help with your application?
ProSense Instruments - discuss instruments and communications hardware: sales@prosenseinstruments.com.au or 1800 560 854.
ProSense Solutions - discuss system integration: sales@prosense.com.au. ProSight Software - discuss software requirements: info@prosightsoftware.com. Device integration must be confirmed for your application.



Comments