IMDTouchKnowledge BaseShop main store

Troubleshooting

Reaching an Inaccessible NS Touchscreen From CX-Designer

HMI and touchscreens Published 6 min read

Short answer

Neither a straight-through nor a crossover female-to-female adapter can make the installed PLC-to-NS cable serve a PC, because the PC's signal ground sits on pin 5 while the NS expects it on pin 9. Transfer through the PLC — with the NS on the CPU serial port, not an SCU — is the route that needs no rear access; USB (lot 0325, or system software 6.0 and later) or a cable wired 2-2, 3-3, 5-9, 7-5, 8-4 covers the one-visit cases.

On this page
  1. Why no adapter can rescue the existing cable
  2. Three routes that reach the panel
  3. Setting up the transfer through the PLC
  4. Wiring a service cable that works
  5. The decision for each case
  6. Questions asked

The straight-through-versus-crossover question has a hard answer: neither one works, and no female-to-female bridge of either kind can turn the installed PLC-to-NS cable into a PC transfer path. The PC's serial interface and the Omron endpoints put signal ground on different pins, so the conductors a PC needs do not exist in a cable wired for PLC-to-NS traffic. Three routes do work, and the best one needs no access to the rear of the touchscreen at all: CX-Designer can transfer through the PLC while the NS stays on the CPU serial port it already occupies. The other two — the NS USB port on late units, and a serial cable wired to the Omron programming map — each need one visit to the panel.

Why no adapter can rescue the existing cable #

The installed run is about 50 ft of RS-232 with male 9-pin plugs at both ends, because the PLC port and the NS port are both female. The USB-to-RS-232 converter on the PC also ends in a male plug, which is where the female-to-female bridge idea comes from. Mating the connectors is not the problem; the wiring behind them is. A PC COM port puts signal ground on pin 5. The Omron side expects ground on pin 9, with its handshake pair on pins 4 and 5. The documented PC-to-NS (or PLC) programming map is:

PC-side pin NS-side pin Role
2 2 data
3 3 data
5 9 signal ground
7 5 handshake
8 4 handshake

Score both adapter types against that map, assuming a straight-through gender changer and a null modem that swaps the 2/3 data pair:

PC pin Required at the NS Straight-through delivers Crossover delivers
2 2 2 — correct 3 — wrong
3 3 3 — correct 2 — wrong
5 9 5 — wrong 5 — wrong
7 5 7 — wrong 7 — wrong
8 4 8 — wrong 8 — wrong

The straight-through bridge lands 2 of 5 conductors correctly, and both are useless because ground never arrives on pin 9. TIA-232 requires a driver to swing at least 5 V and lets a receiver trigger on 3 V, both referenced to common signal ground; with no conductor reaching the NS ground pin, the receiver measures the data lines against a floating reference. The crossover scores 0 of 5, because it also breaks the one pair that was already correct. Neither topology contains the pin-5-to-pin-9 move, so the decision is to build neither. The same straight-versus-crossover decision governs other platforms' converter cables — wiring a DH-485 adapter cable for an SLC 5/02 is one case where it matters.

The only way to reuse the installed run is to cut it at the PLC end and reterminate to the map above, and the price of that is spelled out further down.

Three routes that reach the panel #

  • Transfer through the PLC — no rear access. The PLC acts as a bridge: the PC talks to the PLC over the programming connection you already use, and the PLC forwards the transfer down the CPU serial port the NS already occupies. One hard limit: the NS must hang directly on the CPU's serial port. Through a separate SCU module the bridge does not work, so trace the cable before counting on this route.
  • The NS USB port — one visit. USB transfer is supported on units from lot 0325 onward, and V1 hardware gained it with system software 6.0 or later: one NS12-V1, lot 2825, transferred only after its system software moved from version 5 to 6.0, and later ran 6.61. If you can reach the panel once, this is the simplest link.
  • A wired PC-to-NS serial cable — one visit. Omron's CS1W-CIF31 USB-serial conversion cable is the documented PC-side interface for connecting an Omron PLC or PT to a PC's USB port; pair it with a cable wired to the five-conductor map in the table above.

Setting up the transfer through the PLC #

  1. Trace the installed cable at the cabinet to its PLC end — with the cabinet locked out if the layout puts hands near exposed terminals. A CPU serial port means continue; a separate SCU module means this route is out and the one-visit options apply.
  2. Connect the PC to the PLC with the programming connection that controller already uses.
  3. In CX-Designer, open the transfer settings — the documented path is PT → Transfer Program → Comms Setting, where the destination and its communication settings are chosen — and define the connection so the route runs through the PLC. The introduction manual counts six ways to transfer a project, serial cable, modem, Ethernet and Controller Link among them, so the connection settings carry the route you intend.
  4. In the PLC's routing table, give the CPU serial port a network address of its own, different from the network the PC rides. In the documented field case the ETN21 sat on network 1 and the serial port took a different number before the transfer would route.
  5. Run the transfer. A working PC-to-PLC session proves only the first leg; the serial leg to the NS has to be configured and answering before anything moves.

Keep the installed cable exactly as found throughout — the value of this route is that nothing at the panel changes.

Wiring a service cable that works #

When you do get one visit to the panel, spend it on more than the transfer:

  • Wire any service lead to the five-conductor map above and verify it against the connector drawing for the installed NS model before soldering; the published map is labelled for NS or PLC endpoints generally, not one model. Read pin numbers from the mating face — the solder-side view is a mirror image.
  • If the pinout in hand is incomplete, the discipline is the same one behind uploading an HMI program without the right cable pinout: establish both endpoint pinouts first, then cut wire.
  • Leave the finished service connector somewhere reachable, and while the link is live, upload the program from the old touchscreen so the next outage does not depend on this access again.
  • Length is not the blocker. Fifty feet sits at the conventional TIA-232 reach of about 15 m at rates up to 20 kb/s, and the installed run already carries the PLC session at the installed speed. What has never been tested is a substituted converter-and-adapter chain — one more reason to drop the adapter idea.

The decision for each case #

  • NS on the CPU serial port, no rear access: transfer through the PLC. Set the routing-table entry, transfer, leave the cable untouched.
  • NS behind an SCU module: no bridge. Take one visit: USB if the unit is lot 0325 or later and runs system software 6.0 or above, otherwise fit a serial service lead wired to the map.
  • Older NS with no USB support: the wired serial service cable is the one-visit option; budget the visit to include a project backup.
  • Panel at end of life: if none of the routes is clean, weigh replacement. The same CX-Designer project runs on a PC under NS-Runtime, a destination in the same transfer dialog, which makes industrial panel PCs the natural landing when this terminal is retired.
  • Adapter already on the bench: shelve it. Neither straight-through nor crossover contains the pin-5-to-pin-9 move, and stacking them cannot create it.

Questions asked

Can I cut the 50-foot cable and reterminate it for the PC?

Electrically you can: reterminate the PLC end to the 2-2, 3-3, 5-9, 7-5, 8-4 map and the converter will reach the NS. But the machine loses its PLC-to-HMI link while you work, and you must restore the original pinout before the panel talks to the PLC again. A service lead fitted on one visit is cheaper than a cable you keep converting back and forth.

Why does one cable design serve both Omron PLCs and NS panels?

The published map is written for an NS or PLC endpoint because Omron's 9-pin serial ports share one signal assignment across PLCs and operator interfaces — ground on pin 9, handshake pair on pins 4 and 5. That is why the same hand-wired programming cable serves NS, NT and PLC serial ports.

Is 50 ft too long once the PC drives the cable?

TIA-232 sizes a link for a total load of about 2500 pF. At a typical 50 pF per foot of cable, 50 ft × 50 pF/ft = 2500 pF, right at the limit, with lower baud rates buying margin. The installed run already carries the PLC session at the installed speed, so distance is proven; the untested element is any substituted converter-and-adapter chain.

Do the handshake pins have to be wired?

Not always. The documented alternative ties pin 7 to pin 8 at the PC end and pin 4 to pin 5 at the NS end, which drops the link to three conductors: 2-2, 3-3 and 5-9. Wire the full five-conductor map when the transfer settings or the panel request hardware handshaking.

How do I know if my NS supports USB transfer?

Check the lot number marked on the unit. USB transfer is supported from lot 0325 onward; a unit built before that needs system software 6.0 or later before the port will transfer — one NS12-V1, lot 2825, only worked after moving from version 5 to 6.0. If both conditions look doubtful, plan the serial route.

Keep reading

  • Troubleshooting

    Fixing RS-232 Cable Disconnected Errors on a Replacement HMI

    Jumper RTS to CTS and DTR to DSR at the HMI end of the RS-232 cable before touching communication settings — that pair cleared 'cable is disconnected' and 'response timed out' on a replacement panel polling a Host Link PLC. The different first command, @00MS5E versus @00MM40, is not the fault: both are valid reads and the PLC answers either one passively.

    HMI and touchscreens

  • How-to

    How to Upload an E200 HMI Project Over CAB5

    Start the upload from E-Designer's Upload (Receive) function — the E200 switches itself into transfer mode — but only over a straight-through CAB5 wired pin 2 to 2, 3 to 3 and 5 to 5. The 2-3/3-2 null-modem cable is what produces the timeout. Read the HW and SW revisions off the boot splash first.

    HMI and touchscreens

  • Troubleshooting

    Fixing PLC not responding between an HMI and a CQM1

    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.

    HMI and touchscreens