Introduction

A common issue in industrial systems is when the SCR power controller is connected to a PLC, but communication fails—no control signals are sent, and no status data is returned.

In most cases, this problem is not complex. Around 90% of communication failures are caused by protocol mismatch, wiring issues, or signal interference.

This guide shows a simple 3-step method to quickly identify and fix the problem.

Key Concept

Communication only works when both devices “speak the same language.”

• Protocol mismatch → no communication
• Wiring issue → broken connection
• Interference → unstable signal

Step 1: Check Communication Parameters (Protocol)

Start with the protocol settings. This is the most critical step.

Ensure the following parameters match between PLC and controller:

• Protocol type: e.g., Modbus RTU, PROFINET
• Slave address: must match and be unique
• Baud rate: e.g., 9600 / 19200
• Data format: typically 8N1 (data bits, stop bits, parity)

📍 Any mismatch can cause complete communication failure.

Step 2: Check Wiring (Physical Connection)

If parameters are correct, check the wiring.

Key points:

• RS485 connection:
  A → A (+), B → B (−), do not reverse
• Grounding:
  Connect GND between PLC and controller
• Connection quality:
  Ensure terminals are tight and not oxidized
• Cable integrity:
  Use a multimeter to check continuity

📍 Wrong or loose wiring is one of the most common causes.

Step 3: Check Interference (Signal Stability)

If communication is unstable, interference is likely the cause.

Solutions:

• Keep communication cables away from power lines (≥30 cm)
• Use shielded cables
• Ground the shield at one end only
• Add a 120Ω termination resistor for long distances (>100m)
• Avoid routing near inverters or welding equipment

📍 Strong electromagnetic interference can disrupt communication signals.

Quick Test Method

To identify whether the issue is from PLC or controller:

1. Disconnect communication cable
2. Short A and B terminals on the controller
3. Test communication from PLC

• Timeout → PLC or software issue
• Abnormal data → controller communication fault

Conclusion

Most PLC communication failures with SCR power controllers are caused by:

• Incorrect protocol settings
• Wiring problems
• External interference

By following the sequence:
Protocol → Wiring → Interference,
you can quickly locate and resolve the issue without complex tools.

👉 Need help with PLC communication setup? Contact us for support.