IMDTouchKnowledge BaseShop main store

How-to

Building and Verifying an HMI RJ-45 Programming Cable

HMI and touchscreens Published 5 min read

Short answer

Your computer reaches a Fuji HMI through a USB-to-RS-232 converter, a female DB9 and an RJ-45 plug, but the conductor map between DB9 and RJ-45 is fixed by the exact HMI model, not by the connectors. Get the wiring diagram for your model from the Fuji connection documentation, terminate to it, and prove every conductor and every unused pin with an ohmmeter before anything is powered; with no documented pinout, the answer is the vendor's own cable, not a guess.

On this page
  1. What each part does
  2. The RJ-45 side has no universal map
  3. Build the cable
  4. Verify with a meter before anything is powered
  5. Bring the link up
  6. The decision in each case
  7. Questions asked

The link is four parts in a row: a USB-to-RS-232 converter in the computer, a female DB9 carrying the RS-232 signals, the cable conductors, and an RJ-45 plug in the HMI's programming port. What decides whether that link works or damages a port is the conductor mapping between DB9 and RJ-45, and that mapping belongs to the exact Fuji or Hakko HMI model, never to the connector shapes. Build in this order: obtain the wiring diagram for your model and port, terminate to it, then prove every conductor and every unused pin with an ohmmeter before anything is powered. If no diagram exists for your model, you stop and use the vendor's own cable.

What each part does #

Part Position Role
USB-to-RS-232 converter computer USB port gives the computer an RS-232 DTE port on a male DB9
Female DB9 mates with the converter lands the RS-232 signals for solder or screw termination
Cable conductors between the connectors carries only the signals your model's map assigns
RJ-45 (8P8C) plug HMI programming port lands those signals on HMI port pins 1 through 8

On the DB9 side the positions are fixed by the 9-pin RS-232 convention (TIA/EIA-574): RD on pin 2, TD on pin 3, SG on pin 5, with DCD on 1, DTR on 4, DSR on 6, RTS on 7, CTS on 8 and RI on 9. A three-wire link runs TD, RD and SG; hardware handshaking, if your diagram wires it, adds RTS/CTS and DTR/DSR. These are the same positions used when building an RS-232 Modbus cable between an HMI and a controller, because a DTE serial port is a DTE serial port.

The RJ-45 side has no universal map #

An 8P8C socket accepts any RJ-45 plug, and the HMI does not care that Ethernet usually lives on that connector. Serial over RJ-45 exists in several industry conventions, EIA/TIA-561 among them, and each manufacturer assigns the signals its own way. Fuji's connection documentation publishes wiring diagrams and pin-assignment tables per model and per communication port, listing COM 1, COM 2 and COM 3 with their 9-pin D-sub assignments in the POD manuals, so the map for your unit is a lookup, not a deduction.

Other equipment families show how different those maps are. An SLC 500 DTAM RJ-45 to DB9 cable pinout guide documents one full conductor table for exactly this connector pair. A DB9-to-RJ-45 interface cable pinout for the SVX 9000 drive family documents a different one. Same connectors, different maps: the RJ-45 side is whatever your model's diagram says, and a pinout found for a different model stays untested until your own manual confirms it. This page prints no Fuji pinout because there is no single one to print.

Build the cable #

  1. Record the exact HMI model and the port you will use, then pull the wiring diagram for that model and port from the Fuji or Hakko connection manual. No diagram, no build.
  2. Plug the USB-to-RS-232 converter into the computer, let its driver install, and write down the COM number the operating system assigns it.
  3. Terminate the DB9 female end first: each used conductor goes to its documented DB9 pin, at minimum RD on 2, TD on 3 and SG on 5, plus whatever handshake pins the diagram assigns.
  4. Terminate the RJ-45 end on the documented pins, 1 through 8. To prove a mapping before committing crimps, land the conductors on RJ-45 female to screw terminal block adapters, get the link working, then crimp a plug to the proven arrangement.
  5. Use the conductor colors as labels and write the color-to-pin table on the cable tag; the colors carry no signal meaning of their own.
  6. Set the cable aside for meter verification with both ends disconnected.

Verify with a meter before anything is powered #

Measure only with the cable off both the converter and the HMI: an ohmmeter across a live port reads the port instead of your crimps and can damage the meter's input.

  1. Touch the probe tips together, note the lead reading (typically 0.2 to 0.4 Ω), and subtract it from every measurement that follows.
  2. Check each mapped conductor from DB9 pin to RJ-45 pin against your written table. A 2.0 m run of 24 AWG copper is 2.0 m × 0.084 Ω/m = 0.17 Ω, so after lead-nulling a sound conductor reads near zero; above roughly 0.5 Ω, unstable, or open (OL) means re-terminate.
  3. Check for shorts: between any two points the diagram does not join, the meter must show OL. Any finite reading is a short, so re-terminate or replace the plug.
  4. Count the work and finish it: a five-signal map (TD, RD, SG, RTS, CTS) needs 5 end-to-end checks plus every pin pair on the 8-position end, 8 × 7 ÷ 2 = 28 pairs, 33 measurements, about 11 minutes at 20 seconds each. That is the full cost of not guessing.
  1. Connect the converter and the cable, power the HMI, and put its port into the transfer or communication state the manual describes.
  2. In the programming software's communication dialog, select the converter's COM number and the serial parameters shown on the HMI's transfer setup screen; those values are model-specific, so read them off the screen rather than assume a default.
  3. Start the transfer. Progress proves cable, mapping and settings in one shot. A timeout puts the fault in the serial path: meter the cable again, confirm the COM number, confirm the HMI is in transfer mode, in that order — fixing RS-232 cable disconnected errors on a replacement HMI walks that fault class end to end.
  4. If you are working with no supported cable at all, uploading an HMI program without the right cable pinout follows the same rule this page does: the documented pinout is the entry ticket.

The decision in each case #

  • Diagram in hand for your exact model: build it, complete every check in the count above (33 measurements in the five-signal example), then connect and transfer.
  • No diagram found for the model: stop building. Use the vendor's cable — Fuji's POD hardware manual states to use Fuji Electric's cables when connecting the display to a PLC at the MJ port, and a programming port earns the same discipline. A homemade cable without its map is a gamble on the HMI's port, not a shortcut.
  • Diagram only for a similar model: treat it as untested until your own model's manual confirms it, because ports on sibling models are not interchangeable evidence.
  • Meter shows an open, a short or an unstable reading: re-terminate that conductor before the cable goes near either port.

Questions asked

Can I use a standard Ethernet patch cable or its T568B color order?

The plug fits and all eight conductors work, but T568A and T568B fix only the color order of the pairs, not which signal lands on which pin. Use the color order to keep conductors identified while you terminate, and let your model's wiring diagram decide where each one ends. A straight-through Ethernet cable does not become a programming cable by shape alone.

How many conductors does the programming link actually need?

Three at minimum: TD, RD and signal ground. If the model's diagram includes hardware handshaking, the count grows to as many as seven, adding RTS, CTS, DTR, DSR and possibly DCD. Unused positions on the RJ-45 stay unconnected and must be verified short-free, never bridged or folded back.

What resistance reading says the crimp is good?

Null your leads first by touching the probe tips together and subtracting that reading, typically 0.2 to 0.4 Ω. A 2.0 m run of 24 AWG copper is about 0.17 Ω, so a sound conductor reads near zero after lead-nulling. Anything above roughly 0.5 Ω, unstable, or open gets re-terminated before the cable touches a port.

The converter is recognized but the HMI stays silent. Cable, mapping or settings?

Check in order: the COM number selected in the software, the HMI sitting in its transfer state, then the cable back on the meter. To isolate the converter, jumper DB9 pins 2 and 3 on a spare adapter and open a terminal program; what you type should echo back. Echo works but the HMI stays silent, and the fault is your mapping or the transfer state.

Keep reading

  • How-to

    How to Build the HMI Cable for an A1S Programming Port

    Build the GP2301S-to-A1SCPU-S1 programming-port cable from three documents — the HMI connector table, the driver's connection diagram and the CPU port drawing — reconciled into one wiring sheet by pin number, signal name and viewing direction. Ring out every path before power, then prove one read-only value before any operator command. A connector that fits is not compatibility.

    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

  • Troubleshooting

    FX3G front port RS-422 HMI connection that reports PLC off

    The FX3G-40M front port is an 8-pin MiniDIN, four-wire RS-422 interface that runs CH0 on the Mitsubishi programming protocol only. An HMI set to RS-232 or to an MC Protocol driver shows cable disconnected or PLC off even with the PLC powered. Match the electrical interface, the driver connection variant and the documented cable diagram, and the link comes up without expansion modules or added resistors.

    HMI and touchscreens