A DTC1000 with a PT100 sensor communicated successfully over Modbus but returned a value alternating between 2 and 3. The evidence identifies H1000 as the temperature register. Because substituting another DTC1000 restored the temperature reading, isolate the original module or its configuration before changing PID or alarm settings.
Validate the Temperature Register and PLC Data Path
Read H1000 and inspect the PLC's unmodified receive value before applying scaling, conversion, byte swapping, or display formatting. If the PLC uses the MODRW command, inspect D1296 as part of that command's diagnostic path; D1296 is not established here as applicable to other PLC brands.
| Item | Evidence-supported use | Decision |
|---|---|---|
| H1000 | Temperature value to read | Confirm the request targets this address. |
| D1296 | Data to inspect when using MODRW | Use only on the applicable PLC and command path. |
| Value alternating between 2 and 3 | Observed PLC result | Units and scaling are unknown; do not infer temperature from this value alone. |
Separate Module Failure from PLC Interpretation
The replacement DTC1000 produced a valid temperature reading with the existing system. This comparison supports investigating the original module, although it does not by itself distinguish hardware failure from a configuration difference between modules. Record the raw H1000 response from each module under the same wiring, PT100 input, communications settings, and PLC logic, then compare their configurations in DTCom.
- Capture the raw H1000 value without PLC scaling.
- Install the replacement module without changing the PLC program or sensor wiring.
- Capture H1000 again and compare both module configurations in DTCom.
- If only the original module returns 2 or 3, keep the PLC conversion unchanged and investigate that module or its configuration.
Diagnose a 1–2 Degree Difference Correctly
First determine whether the reported 1–2 degree difference is oscillation around the target or a stable measurement offset. Auto tuning applies to control behavior: start it through DTCom or by turning bit address 813H ON. The evidence does not establish auto tuning as a correction for PT100 measurement bias, so do not use PID changes to mask a stable indication error.
Verify the result by trending the measured temperature and set value before and after tuning. A changing error indicates control variation; a persistent offset requires a measurement-path investigation, but no supported calibration parameter is provided in the evidence.
Configure OUT1, OUT2, and Alarm Modes
Configure the OUT1 and OUT2 operating modes at 1006H and 1023H, respectively. Configure Alarm 1 mode at 1020H and Alarm 2 mode at 1021H by writing the required mode code from the DTC documentation. The numeric mode codes are not supplied here and must not be inferred.
The process set value belongs at 1001H; a value such as 40 is the control setpoint, not the alarm-mode selector. Write the alarm-mode code to 1020H or 1021H, then configure the corresponding AL-H and AL-L temperature thresholds. Verify each output by creating a controlled condition that crosses the configured threshold and observing the associated output state.
FAQ
Which DTC1000 Modbus address contains the temperature?
Read H1000. Confirm the raw response before applying PLC scaling or data-format conversion.
How do I start DTC1000 auto tuning?
Start auto tuning through DTCom or turn bit address 813H ON. Use it for control oscillation, not as an unsupported correction for a stable PT100 measurement offset.
Which registers configure DTC1000 outputs and alarms?
Use 1006H and 1023H for the OUT1 and OUT2 operating modes, and 1020H and 1021H for Alarm 1 and Alarm 2 modes. Keep the process set value at 1001H and configure alarm thresholds through AL-H and AL-L.