Troubleshooting
Fixing PLC not responding between an HMI and a CQM1
Short answer
The alarm means the panel's request never returned from the CQM1. Set the panel port to RS-232C, verify the 2-2, 3-3, 5-9 cable with pin 1 open, match the CQM1's Host Link defaults of 9600 baud, 7 data bits, 2 stop bits and even parity, and reserve the panel's system start address from the PLC program.
On this page
- What does the PLC NOT RESPONDING 02:FE:00 alarm mean?
- Should the panel port be set to RS-232C or RS-422?
- How should the cable pins be wired between the panel and the CQM1?
- What baud rate and framing does the CQM1 use by default?
- How long should one Host Link exchange take at 9600 baud?
- Why must the HMI system start address be reserved?
- What order should you test the link in?
- Questions asked
The PLC NOT RESPONDING alarm with code 02:FE:00 on a Pro-face ST403 means the panel sent a request to the Omron CQM1 and no valid response came back inside the timeout. The panel is the master on this link and initiates every exchange, so the fault lies somewhere on the path between its serial driver and PLC memory: interface mode, cable conductors, framing and protocol, then addressing. A successful screen download to the panel proves nothing about this path, because it travels the engineering link, not the PLC link.
What does the PLC NOT RESPONDING 02:FE:00 alarm mean? #
It means the panel sent a request and no valid response came back inside the timeout: one incomplete request-response cycle, with nothing in the code that says which layer failed, so you work inward from the electrical interface.
The panel raises the code from its driver when the cycle does not complete; it does not distinguish an electrical fault from a framing fault or a protocol mismatch. Clear each layer before moving to the next:
| Layer | What you confirm | What a failure looks like |
|---|---|---|
| Interface | Panel port set to RS-232C | No readable signal levels at the connector |
| Conductors | 2-2, 3-3, 5-9 continuity, pin 1 open | The request never arrives, or the answer never returns |
| Framing | Baud, data bits, stop bits, parity identical at both ends | Characters arrive corrupted or flagged as errors |
| Protocol | Host Link selected on both ends | Clean characters, but no valid request to answer |
| Addressing | System start address reserved | The link runs, then corrupts data or drops back into alarm |
The same incomplete-cycle logic behind fixing an HMI PLC communication timeout over serial applies to other panel-PLC pairs, so the method travels even though the pinout does not.
Should the panel port be set to RS-232C or RS-422? #
Set the panel to RS-232C: the CQM1's CPU-mounted port is an RS-232C port, this panel model offers a choice of RS-232 or RS-422 on its communications port, and the two interfaces cannot pass each other's signals through any adapter.
The ST403 documentation lists both RS-232 and RS-422 on its communications port, and the port takes its mode from the panel project's interface configuration, not from the connector shell. The CQM1's built-in port is RS-232C: single-ended marks and spaces measured against signal ground. RS-422 is a differential-pair interface, so wiring it to an RS-232C receiver produces levels that receiver cannot interpret, and no adapter converts one into the other.
One caution from this panel family: variants differ in interface — the ST401-AG41-24V variant carries an RS-232C connector while others in the family are RS-422. Confirm the exact unit from its nameplate and documentation, then set the project to match.
Decision: RS-422 at the panel against an RS-232C PLC is wrong before anything else matters. Correct the mode first and retest before touching a single protocol setting.
How should the cable pins be wired between the panel and the CQM1? #
Three conductors plus one bridge: panel pin 2 to PLC pin 2, panel pin 3 to PLC pin 3, panel pin 5 to PLC pin 9, a bridge between pins 4 and 5, and pin 1 left unconnected, because the Omron nine-pin port does not follow the IBM PC pinout.
| Conductor or pin | Reading with both ends disconnected |
|---|---|
| Panel pin 2 to CQM1 pin 2 | Continuity |
| Panel pin 3 to CQM1 pin 3 | Continuity |
| Panel pin 5 to CQM1 pin 9 | Continuity |
| Pin 1 at either connector | Open |
| Every other pair, before the bridge is fitted | Open |
Measure with power off and both cable ends removed from the devices, and sweep every pin against every other pin. That one habit catches open conductors, mirrored connector numbering, solder bridges and shield-to-pin mistakes — the failures a visual inspection misses. It is the same conductor-by-conductor discipline as building the RS-232 Modbus cable between an HMI and a controller, and it applies to every hand-made serial link.
Pin maps are pair-specific in general: the TD200 to S7-200 cable pinout runs 2-2, 3-3, 7-7 and 8-8 on its DB9 connectors, so a cable that worked on a different link proves nothing on this one.
The wiring note for this link adds a bridge between pins 4 and 5, listed among the panel-side lines, so solder it at the panel connector. After assembly an ohmmeter shows panel pin 4 common with panel pin 5 and with the line out to CQM1 pin 9 — that common reading is the bridge at work, not a short. If the three data conductors later verify good and the alarm stands, move the bridge to the PLC connector and retest once: the bridge satisfies one port's handshake, and one retest tells you which end wants it.
What baud rate and framing does the CQM1 use by default? #
The CQM1's documented default is 9600 baud, 7 data bits, 2 stop bits, even parity, with Host Link as the protocol; enter those values at the panel once you have confirmed the PLC port still carries its defaults.
| Setting | CQM1 documented default | Panel value |
|---|---|---|
| Protocol | Host Link | Host Link |
| Baud rate | 9600 | 9600 |
| Data bits | 7 | 7 |
| Stop bits | 2 | 2 |
| Parity | Even | Even |
Read the PLC side before trusting the defaults column. The CQM1 port can be reconfigured from the programming software or a handheld programmer, and a CPU-mounted DIP switch can hold the nine-pin port at fixed settings — pin 5 in the documented Omron Host Link setup — so read the switch block and the port settings back rather than assuming either.
A baud mismatch corrupts every character, because the receiver samples the line at the wrong instants and assembles garbage it discards. A parity or stop-bit mismatch lets most bits through but makes the receiving UART flag errors and drop frames. A protocol mismatch is quieter still: clean characters arrive, but the PLC finds no valid request to answer. No cable change fixes any of the three.
Decision: with the CQM1 confirmed at its defaults, the panel gets 9600 baud, 7 data bits, 2 stop bits, even parity and Host Link — all five fields, or none of it works.
How long should one Host Link exchange take at 9600 baud? #
About 23 ms of line time each way for an illustrative 20-character frame: at 9600 baud the default framing loads 11 bits onto every character, which is 1.146 ms per character, so 20 characters occupy 22.9 ms.
The arithmetic, with the default framing:
- Bits per character: 1 start + 7 data + 1 even parity + 2 stop = 11 bits
- Time per character: 11 bits ÷ 9600 bits/s = 1.146 ms
- Illustrative 20-character request: 20 × 1.146 ms = 22.9 ms of line time
- Same-size response: another 22.9 ms, so the round trip is 2 × 22.9 ms = 45.8 ms
The 20-character frame is an illustrative size — real Host Link commands vary — but the order of magnitude is the point: a whole exchange clears in tens of milliseconds. The panel's response timeout is sized accordingly, so when this alarm appears the response is not late, it never existed. Lengthening the timeout chases the wrong fault.
The same arithmetic shows why a baud mismatch never reads as slow. Drop the PLC to 4800 baud and each character takes 11 ÷ 4800 = 2.292 ms; a panel still sampling at 9600 baud reads each bit at half its true width and assembles corrupted bytes, not delayed ones.
Decision: leave the timeout at its normal value and find the layer. A correct link at these settings answers essentially instantly.
Why must the HMI system start address be reserved? #
Reserve it completely: the system start address places the panel's own status words in PLC memory, and any ladder instruction that touches that span competes with the panel, which can stop the exchange even after cable, framing and protocol are all correct.
Read the address from the panel's communication setup — it is a project setting, not a fixed number — and reserve the whole span it occupies: last word = start word + (length − 1), with the length taken from the driver's documented requirement. The PLC program then avoids that range entirely for its own data.
The overlap symptom is distinctive: the link comes up, screens display, and then data corrupts or the alarm returns as ladder rungs overwrite the panel's status words. That behavior after a working download is the tell that sends you back to addressing, not back to the cable.
Decision: if the configured span overlaps any PLC data area in use, move the system start address to free memory or relocate the program's data. The panel and the ladder never share words.
What order should you test the link in? #
Test in signal order — interface mode, then conductors, then framing, then protocol, then addressing — because every layer depends silently on the one before it, and a meter reading costs less than a second hand-made cable.
- Confirm the exact panel variant and set its project port to RS-232C.
- Power down, disconnect both cable ends, and log the readings: 2-2, 3-3 and 5-9 continuous, pin 1 open, every other pair open before the bridge goes in; then fit the 4-5 bridge at the panel end.
- Read back the CQM1 port's framing values and protocol, and confirm no CPU DIP switch is holding fixed settings.
- Enter 9600, 7 data bits, 2 stop bits, even parity and Host Link at the panel — or the PLC's actual values if they differ from the defaults.
- Read the system start address and fence its full span off from the ladder program.
- Put one live read on the test screen — a PLC input word or a timer current value — and watch it update. A button alone proves nothing, because it only writes when pressed.
When all six pass, the alarm clears on the next poll. If steps 1 through 5 verify and step 6 still fails, the remaining suspects are the panel driver selected for the exact CQM1 model and the port hardware itself: test the panel against another serial device, and the PLC against another master, and whichever half still fails carries the hardware fault.
Questions asked
The project downloaded to the panel without errors, so why does the PLC link still fail?
The download travels over the engineering link between your PC and the panel; it exercises none of the conductors, framing or protocol the panel uses to reach the PLC. Treat a successful transfer as proof about the panel only, then prove the PLC link separately with a live tag on screen.
What is Host Link protocol on the Omron side?
Host Link is Omron's ASCII-based serial protocol, arranged as 1:N so one master can address up to 32 PLCs and devices on a single link. On this installation it runs point to point: the panel issues every request, and the CQM1 answers the ones it recognizes. Both ends must select Host Link by name.
Should pin 1 be connected as a ground between the two connectors?
No. The documented arrangement for this link leaves pin 1 unconnected and carries the signal reference on the panel pin 5 to CQM1 pin 9 conductor instead. A closed reading on pin 1 is exactly the kind of undocumented extra the continuity sweep is meant to find and remove.
Two different cables show the same alarm, so is the cable ruled out?
No. Two untested cables can share the same open conductor or the same wrong map, and a cable fault is only one of the layers behind this alarm. Only a logged continuity check closes the cable question; agreement between two cables that were never measured closes nothing.
Why did the Omron panel-to-panel cable not work either?
Because that cable follows Omron's own connector convention between Omron devices. This link must follow the panel maker's RS-232 pin map against the CQM1 port, and the two maps are not the same even though both ends are nine-pin connectors. Any cable on this link earns its place through measurement, not through its origin.