Troubleshooting
Commissioning CP1L Host Link serial reads to SCADA
Short answer
CX-Programmer going online proves only the programming path, not the SCADA read. Set the CP1L serial port to Host Link, enter its unit number (0 to 31) as the driver's device address, match baud, data bits, parity and stop bits, prove the cable end to end, and free the computer port of other software. Read one known word before adding tags: a timeout means no valid reply arrived; a PLC protocol error proves the link works.
On this page
- Why does CX-Programmer go online but the SCADA screen shows nothing?
- Which driver does a CP1L use in Citect SCADA?
- What serial settings must match between the CP1L and the SCADA driver?
- How do I prove the RS-232 cable is right?
- Is another program holding the computer's serial port?
- Which PLC word should the first SCADA read test?
- What does a timeout versus a PLC error reply tell me?
- How many reads per second can one serial port carry?
- When should I add the rest of the SCADA tags?
- Questions asked
If CX-Programmer goes online to the CP1L but the SCADA screen stays empty, the PLC is almost never the fault. The programming connection and the SCADA read are two different paths, and only one of them has been commissioned. Commission the serial Host Link path on its own: set the port's mode to Host Link in the PLC Setup, enter the unit number (any value from 0 to 31) as the driver's device address, and make four serial-format fields agree — 9600 baud, 7 data bits, even parity, 2 stop bits is the classic starting set to read out of the PLC Setup and copy field by field into the driver. Then prove the cable end to end, free the computer port of other software, and read one known word such as D100 before adding any more tags. Read the diagnostics the way they divide: a timeout means no valid reply arrived, while a Host Link error reply proves the link works and points at the tag.
Why does CX-Programmer go online but the SCADA screen shows nothing? #
Because a programming connection and a SCADA read are two different paths: CX-Programmer going online proves only that the USB programming link works, while the SCADA runtime polls the RS-232 Host Link port through its own driver, so the SCADA path has to be proven on its own.
A programming session rides the controller's USB port under its own protocol; the runtime rides the serial port with Host Link commands. The healthy online indicator in CX-Programmer says nothing about the second path, and what going online to a PLC actually means and changes is worth a minute of reading before you treat an online session as proof of anything — what going online to a PLC means, and what it changes.
Decision: treat the SCADA path as unproven until one word reads back, no matter how healthy the programming session looks.
Which driver does a CP1L use in Citect SCADA? #
The Omron Host Link serial driver is the one to configure: it speaks the C-mode Host Link commands the CP1L serial port answers, so the board, port and I/O device chain in the SCADA project must reference that driver and the physical COM port the cable lands on.
Before building a single tag, open the driver help that ships with your installed Citect version, confirm the CP1L appears in the supported PLC list, and note the memory-area notation and address syntax that version documents. Settings copied from an example written for a different PLC family or protocol will not apply. The driver sits on a chain of three objects — a board that loads it, a port bound to that board, and an I/O device bound to the port — and the installed help spells out exactly what each object needs.
Decision: build the configuration from your installed driver help and compile it clean before the first runtime start.
What serial settings must match between the CP1L and the SCADA driver? #
Four serial-format fields plus the unit number must agree: the baud rate, data bits, parity and stop bits shown in the CP1L's PLC Setup for that port, and the Host Link unit number — settable from 0 to 31, unique per network — entered as the driver's device address.
The CP1L's side lives in the PLC Setup for the serial port, read and edited through CX-Programmer: the port mode must be Host Link, and the same screen holds the format fields and the unit number, which may be set anywhere from 0 to 31 and must be unique on the network it serves. The driver holds the same fields plus the device address, and that address is where the unit number goes. Two rules decide this section. First, read every field out of the PLC Setup and type it into the driver; never carry an address over from an unrelated example. Second, a value sitting in an offline project proves nothing: use the documented transfer and activation procedure so the physical port actually runs it, then re-read the Setup from the PLC to confirm what it took.
Decision: put the CX-Programmer serial screen and the driver screen side by side and make them agree field by field.
How do I prove the RS-232 cable is right? #
Prove it end to end against the drawings: compare the CP1L connector's documented signal names and pins with the cable's and the computer's, confirming that send meets receive, that signal ground is common, and that any handshake lines the setup needs are actually wired, because connector shape alone proves nothing.
The port side is drawn in the CP1L CPU unit operation manual's serial connection chapter; the cable and the computer side are whatever the supplier built, so all three drawings get compared. Adapters cause most of the trouble: a null modem or a gender changer turns a cable that looks right into one that carries nothing. Models also differ in fitted serial hardware, so identify the port you are actually cabling before building or buying anything.
Decision: when the first read times out, the cable is suspect number one — ahead of the driver timeout, which cannot repair a crossed pair.
Is another program holding the computer's serial port? #
One program at a time owns a COM port, so close every other application that opens it — a terminal emulator, an OPC server, a second SCADA project, or CX-Programmer when it drives that same serial interface — then confirm the runtime opens the port without a resource error.
USB serial adapters make this worse, because the operating system may hand the adapter a different COM number after a reboot or a move to another socket. Check which port the adapter holds right now and point the driver at exactly that one. Contention announces itself as a failure to open the port, not as a timeout after the port opens.
Decision: a driver that cannot open the port points at the computer; a driver that opens it and then times out points downstream, at the cable or the PLC.
Which PLC word should the first SCADA read test? #
One word you can watch from CX-Programmer at the same time — a noncritical data memory word such as D100 forced to a known value like 1234 — read through a single SCADA tag built with the driver's own memory-area notation, with every write kept out of this first test.
Set the value from the CX-Programmer watch window, watch the SCADA tag follow, then change the value again: a single matching number cannot tell a live read from a display that kept its first result. A word that changes on its own, such as a clock or counter, is the best witness. The write ban has a hard reason behind it — a write sent to the wrong address, or decoded with the wrong data type, can move an output the machine is depending on.
Decision: one tag, one known word, read-only, proven against the watch window before anything else is configured.
What does a timeout versus a PLC error reply tell me? #
They mean different things: a timeout says no valid reply arrived at all, so the cable, port mode or serial format is suspect, while a Host Link error reply says the PLC heard the request and rejected it, proving the link and pointing at the tag's address or command.
A timeout is only ever the statement that nothing valid arrived inside the driver's window — a rule that holds on any serial protocol, laid out in why a Modbus RTU read timeout means no valid reply arrived. An error reply, by contrast, is a message from the PLC itself, so capture the exact diagnostic before changing any setting:
- Driver cannot open the port — the computer owns the fault: check which program holds the interface and which COM number the adapter currently has.
- Every read times out — work the physical layer: cable, port mode, serial format, unit number, in that order.
- The PLC returns an error reply — the link is proven; check the requested memory area, the address format and whether the command is supported, using the exact error the driver reports.
- Quality good but the value wrong — check the address, word versus bit selection, and the data type the driver applies.
- Reads work, then stop — check connectors, adapter stability, and whether the polling load outran the port.
The same timeouts are what leave an operator staring at question marks where HMI values should be.
Decision: a timeout sends you to the physical layer; an error reply sends you to the tag.
How many reads per second can one serial port carry? #
At 9600 baud with an 11-bit character, one port carries about 873 characters per second, so a one-word exchange of roughly 30 characters costs about 34 ms of line time — plan on the order of ten to twenty one-word reads per second, and let block reads do the heavy lifting.
Worked example — assume the PLC Setup shows 9600 baud with 7 data bits, even parity and 2 stop bits:
- Character length: 1 start + 7 data + 1 parity + 2 stop = 11 bits per character.
- Line rate: 9600 baud ÷ 11 bits per character ≈ 873 characters per second.
- One-word exchange: request plus reply, two frames of header, unit number, command, operands and frame check, is on the order of 30 ASCII characters — an estimate, not a constant.
- Line time per exchange: 30 characters ÷ 873 characters per second ≈ 34 ms.
- With the PLC's turnaround at 20 to 50 ms: 34 + 20 = 54 ms per exchange ≈ 18 reads per second; 34 + 50 = 84 ms ≈ 12 reads per second.
So one port at 9600 baud carries roughly 10 to 20 one-word reads per second, before any other traffic, and lengthening the driver's timeout does not raise that ceiling — line time and turnaround set it. Grouping tags pays immediately: a ten-word reply carries 40 data characters, so the exchange grows to about 66 characters, and 66 ÷ 873 ≈ 76 ms works out to 7.6 ms per word — about 4.5 times cheaper per word than one-word polls (34 ÷ 7.6 ≈ 4.5). These are illustrative inputs, so redo the arithmetic with your own baud rate and character format, because the result moves with both. It is the same arithmetic that makes Modbus RTU drive polling slow on one serial port.
Decision: group tags into block reads per memory area, and never set a scan group period shorter than one exchange can complete, because stacked timeouts read like a broken link.
When should I add the rest of the SCADA tags? #
Only after one known word reads correctly and tracks a changing value: add tags in small groups by memory area and data type, checking quality and diagnostics after each group, and alarm the serial link itself so a loose cable announces itself instead of silently freezing numbers.
Group by memory area and data type so each group can ride one block read, then check quality and diagnostics under live polling and confirm the values against the PLC before the next group goes in. Build the link-loss alarm into the project now rather than after the first failure, following how to create a SCADA PLC communication alarm for link loss.
Decision: add the next group only after the last one has polled clean, and keep the sequence reversible — one word first, one alarm second, then the rest.
Questions asked
Do I configure anything in Citect besides the driver itself?
Yes. A Host Link serial project is a chain of three objects: a board that loads the driver, a port tied to that board, and an I/O device tied to the port, with the PLC's unit number as the device's address. The whole chain must compile clean, and after a configuration change restart the runtime components the installed version requires, because a running project keeps its old settings until it does.
The link works but the number looks wrong — what should I check first?
The data type. A word the PLC program stored as BCD shows 1234 when the driver decodes BCD and 4660 when it decodes the same bits as binary — the value 0x1234 is 4660 in decimal. Match the driver's data-type setting to how the program wrote the word, then check whether the tag points at a word or a bit and whether the address notation is the one the installed driver documents.
Can CX-Programmer and the SCADA runtime use the CP1L at the same time?
Usually yes, because they ride different physical paths: CX-Programmer programs over the PLC's USB port and the runtime polls the RS-232 Host Link port, so a programming session can stay connected for watching values while the SCADA polls the serial link. What can never be shared is a single COM port on the computer: if CX-Programmer or any other program holds the same serial interface the driver wants, close it before starting the runtime.
The machine came without Omron software — how do I get CX-Programmer?
CX-Programmer is part of Omron's licensed CX-One package: obtain a license and the software from Omron or an authorized distributor. Before installing or upgrading, read the PLC's unit version from the nameplate, where it sits to the right of the lot number, and match the software version to it, because an old install may not recognize a newer unit version.
Should I test writes from the SCADA as soon as one read works?
Not on a running machine. Reads prove the address, notation and data type; a write sent to the wrong word, or the right word decoded wrongly, can move an output the machine is depending on. Prove the first write with the machine stopped or on a bench, keep anything safety-relevant interlocked in the PLC program rather than in the screen, and give each writable tag a written purpose before it goes live.