Observed Failure Pattern
The Z031 and SMH4 establish RS-485 communication only while a USB-to-RS-485 converter is connected in parallel. Removing the converter stops communication. Adding or removing the line terminator does not correct the fault, and both devices use the same power supply.
This pattern points to an RS-485 physical-layer compatibility problem rather than a Modbus addressing or command problem. The converter changes the electrical state of the bus, most plausibly by providing bias, but the evidence also identifies an idle-time synchronization mechanism that must be tested separately.
| Observation | Engineering implication |
|---|---|
| Communication works with the converter connected | The converter supplies an electrical condition missing from the two-device network. |
| Termination changes do not restore communication | Do not treat termination as the primary corrective action. |
| Z031 has no internal bias resistors | The network may require one external bias network when the peer does not provide bias. |
| Z031 has no internal terminator | Any required termination must be installed externally. |
Separate Bias Failure from Timing Failure
Two mechanisms are supported by the evidence and must remain separate during diagnosis.
Bias hypothesis: During bus idle, receivers continuously monitor the differential pair. Without pull-up and pull-down resistors, noise or an undefined idle voltage can prevent some receiver generations from recognizing silence. The evidence states that older receivers may require more than 200 mV of bias. It also identifies the Z031 transceiver as ST485EBDR and states that the Z031 omits bias because Zentec controllers normally provide it.
Timing hypothesis: The Z031 transmitter may need to hold the inactive level for 3 character times so the receiving UART can synchronize. The corresponding pre-response delay is disabled by default according to the evidence. The required time depends on baud rate and cable length, so no fixed millisecond value can be selected from the available information.
Diagnostic Decision Path
- Confirm the baseline symptom: record whether valid traffic stops only when the parallel converter is removed.
- In the template's main properties, open the Device tab and enable a delay before the response. Select a value appropriate to the configured baud rate and line length; the evidence does not provide an exact value.
- Retest without the USB-to-RS-485 converter. If communication becomes stable, retain the delay and verify it over repeated requests.
- If the delay does not restore communication, treat missing bus bias as the leading hypothesis. Install one purpose-built RS-485 biasing module or an RS-485-to-RS-485 repeater that provides a defined idle state.
- Retest termination independently. Use termination only where required by the actual network layout; its installation or removal did not solve the reported case.
Implement External Bias Safely
Install only one intentional bias network on the bus. Multiple universal bias networks can load or oppose each other. Confirm the required polarity from the device terminal definitions before wiring; the evidence warns that one proposed circuit had its polarity reversed and states that the correct idle condition requires A to be more positive than B.
Do not derive resistor values from the available evidence. Correct sizing must account for supply voltage, installed termination, receiver loading, and the differential idle voltage required by the least tolerant receiver. The discussion references a design case with at least two terminators and 32 unit loads of 12 kΩ, but it does not provide a complete circuit or validated resistor pair for this installation.
A USB-to-RS-485 converter powered from the SMH4 USB port can preserve the demonstrated workaround when its USB connection supplies only 5 V power. Treat this as a diagnostic or temporary measure. A dedicated bias module or RS-485 repeater provides a clearer permanent implementation.
Verification and Acceptance
Verify the correction with the converter removed unless it is the selected permanent bias device. Run repeated request-response exchanges and confirm that communication remains stable during idle-to-active transitions. Repeat the test after power cycling both devices.
If the timing change succeeds, document the configured baud rate, cable length, and response-delay setting. If external bias succeeds, document the bias module, polarity, termination state, and measured idle differential voltage. Compare that measurement with the receiver requirements in the device documentation; do not assume that an unverified bias voltage is sufficient.
If neither correction works, capture the differential pair during idle and at the beginning of a response. Determine whether the failure is an undefined idle state, reversed polarity, missing inactive interval, or another wiring-level condition before changing Modbus configuration.
FAQ
Why does SMH4 communicate with Z031 only when a USB-RS485 converter is connected?
The converter changes the RS-485 bus electrically and may provide the missing idle-state bias. Test the Z031 response delay first, then add one external biasing device if the timing change does not restore communication.
Where do I configure the Z031 delay before a response?
Open the template's main properties, select the Device tab, and set the delay before response. The target mechanism is an inactive interval of 3 character times, while the actual configured time depends on baud rate and cable length.
Will adding an RS-485 terminator fix Z031 and SMH4 communication?
Not in the reported configuration: installing or removing the terminator did not solve the fault. Diagnose response timing and idle-state bias separately, then apply termination according to the physical network layout.