Automation Direct DL06 PLC Common Troubleshooting and Maintenance Guide

5.2 Modbus RTU or DirectNET communication failure

Station address conflict: Each slave station address must be unique. The station address of Port 2 can be set to 1-247 (Modbus) or 1-90 (DirectNET) in DirectSOFT.

Baud rate and parity mismatch: Port 2 supports 300-38400 baud. All network nodes must be consistent.

Terminal resistance: For RS-422/485 networks, 100-500 Ω terminal resistors need to be connected at both ends.

Modbus address calculation: DL06 uses octal addresses, while Modbus hosts typically require decimal addresses. For example, output Y20 (octal 20=decimal 16) corresponds to Modbus address 2049 (if using 584/984 mode, the address needs to be offset). The manual provides a detailed conversion table.

MRX/MWX instruction execution unsuccessful: Check special relays SP116 (Port 2 busy) and SP117 (communication error). Multiple network instructions need to be interlocked with each other to avoid simultaneous execution. Use interlock bits (such as C100) to ensure that only one MRX/MWX is activated at a time.

5.3 Non sequential protocol (ASCII input/output) issues

Port 2 can be configured in "non sequential" mode for communication with ASCII devices such as serial printers and barcode scanners.

PRIMT instruction no output: Confirm that Port 2 has been configured as a "non sequential" protocol through DirectSOFT or AUX 56, and that the correct V-memory buffer address (occupying 66 consecutive words) has been specified.

Garbled or misplaced data: Check if the data bits (7 or 8), stop bits, and parity check match the terminal device.

The message created by VPRINT has not been sent: first write the ASCII string to V-memory using VPRINT, and then send it using the PRIMTV instruction. Pay attention to using SP116 to ensure that the port is idle.

Programming and software malfunctions

6.1 Program cannot be downloaded or compiled incorrectly

Syntax Error: DirectSOFT will indicate incorrect lines during compilation. Common errors include instruction parameter out of range, operand type mismatch, missing END statement, etc.

Duplicate Reference Error (dEST): If two or more output or assignment instructions are written to the same coil at the same time, although it will not prevent the download, it will cause logical uncertainty. Use the duplicate reference check function (AUX 21 or DirectSOFT) to quickly locate.

Subroutine or interrupt program location error: Subroutines, interrupt programs, and data labels (DLBL) must be placed after the END instruction in the main program.

6.2 Run Mode Edits

DL06 supports online program modification during runtime. But please note:

When editing at runtime, the output will remain in its original state until the new program accepts and enters the next scanning cycle. If the new program has serious errors, the CPU will enter Program mode and shut down all outputs.

It is recommended to validate the logic through testing mode before making modifications.

6.3 Mandatory I/O and Bit Overcover

Conventional forcing: temporarily changing the status of inputs, outputs, intermediate relays, etc. for debugging purposes. The mandatory value is only valid for the current scan, and the actual signal will be restored during the next I/O update.

Bit Override: When enabled using AUX 59 or DirectSOFT, the CPU will ignore the actual input changes and fix it to the forced state. Commonly used for simulating signals or locking outputs. Note: Bit coverage does not affect the mandatory function, and both can be used simultaneously.

6.4 Memory Mapping Confusion

Many beginners are confused about the octal address of DL06. For example, the output point numbers are Y0, Y1,..., Y7, Y10, Y11,..., Y17 (without Y8, Y9). Similarly, V-memory addresses such as V2000 are valid, but V2008 is invalid (because 8 is not an octal number). When using pointers or Load Address (LDA) instructions, the address needs to be converted to hexadecimal.

Preventive maintenance recommendations

Regular backup: Save programs, V-memory, and system parameters to the computer through DirectSOFT.

Battery replacement cycle: Even if the power is not frequently cut off, it is recommended to replace the battery every 2-3 years to avoid data loss.

Cleaning dust: Clean the interior of the PLC, especially the heat dissipation holes and terminal areas, with low-pressure compressed air at least once a year.

Check grounding and shielding: Confirm that the grounding resistance is less than 100 Ω, and that the shielding layer of the communication cable is grounded at one end.

Transient suppression check: For newly added inductive loads, it is necessary to install suppressors and regularly check whether the suppression components have failed.

Regular restart testing: For systems that have been running continuously for a long time, they can be powered back on regularly during planned shutdowns to verify whether the startup logic and data retention are normal.