Each slave communicates reliably when configured alone. The strongest configuration-level clue is that TP001 timeouts also occur when disconnected MVU-8 and MDVV devices remain in the PLC configuration through device-specific templates.
Separate confirmed behavior from suspected causes
| Observation | Engineering implication |
|---|---|
| The initial setup uses 9600 baud and a 500 ms polling time for each slave. | Do not assume polling frequency alone causes the timeout. |
| MVU-8 and TP001 operate reliably when tested separately. | The fault appears only in the combined configuration. |
| In a separate test at 19200 baud, TP001 sometimes reports error 81 when disconnected MDVV and MVU-8 entries remain configured. | Configured device templates can affect operation even when those devices are not physically connected. |
Prioritize the device-template configuration
The leading evidence-supported hypothesis is a problem in the dedicated MVU-8 or MDVV templates, not a confirmed electrical failure. The reported corrective direction is to remove those template-based submodules and represent every slave with a UniversalModbusDevice entry. The evidence describes the templates as old and potentially containing software errors, but it does not identify an affected software version or a specific defect.
Apply an isolation procedure
- Save the current PLC configuration so the original arrangement can be restored.
- Remove the MVU-8 submodule and any MDVV template entry from the active test configuration.
- Add each required slave as a separate UniversalModbusDevice, retaining the documented slave addresses and serial settings for the actual installation.
- If error 81 remains, inspect the communication statistics and recorded cycle time. Check the physical end of the RS-485 segment for the suggested termination resistor, but treat termination as an unverified diagnostic because the evidence does not provide resistor specifications or a successful result.
Verify the correction
Run the combined configuration long enough to cover repeated polling of both connected slaves and watch specifically for error 81 on each device. Then repeat the configuration-only isolation test: leave only TP001 physically connected while the required UniversalModbusDevice entries remain configured. The correction is supported if TP001 remains stable in that test and both slaves remain stable when reconnected. If timeouts continue, record which slave timed out, the active baud rate, polling time, measured cycle time, and whether the device was physically present; the available evidence does not establish a further root cause.
FAQ
The supplied evidence identifies error 81 as a timeout during polling. It occurs intermittently on both TP001 and MVU-8 in the combined configuration.
How do I stop intermittent error 81 with MVU-8 and TP001?
Remove the dedicated MVU-8 and MDVV template entries, configure each slave as a separate UniversalModbusDevice, download the configuration, and retest both slaves together.
Not in the reported case.