Modbus Exception 02: Check the Register Map Before Changing the Wiring
A Modbus client reports “illegal data address”, yet a technician is asked to replace the communications cable. Before touching the installation, preserve the request and response. A properly identified exception response gives a different starting point from a timeout: investigate what was requested and which device answered. This guide proposes a read-only diagnostic record for an authorised integrator; it is not permission to change a live control system.
Recognise the response before choosing the repair
The Modbus application specification defines exception 02 as an invalid combination of address and transfer length. An exception response sets the function code’s high bit; for a function 03 request, the exception function is 0x83. The following exception byte 0x02 is distinct from function 02, which reads discrete inputs. Do not diagnose the message from an isolated “02” in a screenshot.
Ask for a timestamped transaction capture that identifies the responding device, requested function, starting address, quantity and returned exception. Keep the original capture alongside a readable interpretation. If software displays only a general communications warning, obtain its diagnostic log before assigning a cause. Redact credentials, public network details and unrelated plant information from support copies.
Put the register map beside the client configuration
Use the instrument manufacturer’s map for the installed model, firmware and enabled options. Record the document revision and the exact row being requested. A spreadsheet copied from a similar instrument is a lead to investigate, not an approved mapping. Ask the integration owner whether the point was ever accepted successfully, and preserve that earlier configuration if available.
Check the selected register table and client address convention. Function 03 reads holding registers; function 04 reads input registers. Protocol register addresses start at zero. A client’s displayed reference notation may need translation before transmission, so check its documentation rather than applying a universal “subtract one” rule. Record both the displayed setting and actual transmitted address.
A hypothetical block-read boundary
Suppose a hypothetical device documents readable addresses 200–207. Starting at 206 with quantity two stays within that range; quantity three includes 208. An acceptable starting address does not make the whole request valid. This example illustrates boundary checking, not a register map or command for any ProSense product.
Write the proposed range out explicitly before changing a polling block. Include documented gaps and complete multi-register values. Have the responsible integrator choose the smallest documented read that still contains a complete value; do not split a value arbitrarily just to make an error disappear. Never scan unknown addresses or try write commands as a discovery method on operating equipment.
Separate the field transaction from the wireless uplink
A converter adds another place to collect evidence. Dragino documents its RS485-LB/LS as sending configured requests, processing returned data according to user-defined rules and uploading a LoRaWAN payload. A received uplink alone therefore does not prove that the intended field register was read successfully. Preserve the local transaction separately from the network payload and dashboard value.
The pictured converter is an example of this integration architecture, not a claim that it caused the fault. Confirm the supplied hardware, firmware, regional radio variant and connected instrument before using its manual. Do not copy another installation’s serial commands, payload slicing or decoder assumptions. This guide does not establish direct compatibility with ProSight or any particular customer instrument.
Run a controlled comparison and retain both outcomes
Agree a test window and monitoring contingency with the site owner. Save the current polling configuration and identify who can restore it. Compare one documented read with the failing request, changing only the address-related setting supported by your evidence. Retain the exact before-and-after requests, responses and times, including unsuccessful attempts. Avoid presenting an expected result as an observed result.
If an exception becomes a normal response, verify the point’s identity, units and plausible value against an independent permitted observation. A successful transaction is a separate acceptance check from correct engineering interpretation. If the exception remains, escalate the model, firmware, map revision and paired capture. If the symptom becomes a timeout, record that change rather than continuing to describe every failure as exception 02.
Common mistakes and a useful handover
Avoid increasing timeouts to conceal a consistently rejected address, changing wiring while evidence points to a request mismatch, or expanding block reads across undocumented gaps. Do not permanently substitute a zero or stale “last good” value for a failed point without the application owner’s approved treatment. A tidy dashboard must not hide unresolved data quality.
Close the investigation with the accepted mapping, the evidence supporting it, the restoration method and any unresolved limitation. Where electrical access, process interruption or safety functions are involved, leave application-specific assessment and work to competent people under current site requirements. For supplier assistance, send the concise transaction record and exact product details; that is more useful than a photograph of a generic error banner.
References and pictured equipment
Need help with your application?
For instrument enquiries, visit ProSense Instruments, email sales@prosenseinstruments.com.au or call 1800 560 854. Include the exact model and a concise fault record.
For complete monitoring and automation projects, visit ProSense Solutions or email sales@prosense.com.au.
For software enquiries, visit ProSight Software or email info@prosightsoftware.com. Confirm device and protocol integration for your application.
Comments