How-to
How to Upload an HMI Program Without the Right Cable Pinout
Short answer
Upload an HG3F with the documented programming cable HG9Z-XCM1A, which runs from a 9-pin RS-232 port on the PC to Serial Interface 2 on the panel. Do not fabricate a pinout, and confirm the installed WindOI-NV2 version permits upload before you connect.
On this page
The HG3F does not need a reverse-engineered pinout. The documented programming cable is the HG9Z-XCM1A, listed for the HG2F, HG3F and HG4F series, running from a 9-pin RS-232 port on the PC to Serial Interface 2 on the panel. Obtain that cable, confirm the installed WindOI-NV2 version lets you upload this panel before you connect anything, then work the procedure below in order. What you should not do is wire a lead from a guessed pin map: the documentation available for this cable publishes the part number and its two endpoints, not the pin assignments, and a cable that mates but crosses signals is the quickest way to leave the panel unreachable.
What the documented upload connection is #
The upload path for this family is a vendor accessory, not a homemade lead. The HG9Z-XCM1A is listed as the programming cable for the HG2F, HG3F and HG4F series, and it connects a PC's 9-pin RS-232 port to Serial Interface 2 on the panel. Listings for USB variants of this cable show the panel end as a mini-DIN 8-pin connector, which already rules out mating a standard 9-pin serial lead to the panel.
Three part numbers get confused on this panel, so separate them by their documented use:
| Part number | Documented use | Serves the HG3F upload? |
|---|---|---|
| HG9Z-XCM1A | Programming cable, PC to HG2F, HG3F and HG4F; PC side 9-pin RS-232, panel side Serial Interface 2 | Yes |
| HG9Z-XCM2A | USB programming cable for HG1G, HG2G, HG3G and HG4G touchscreens | No, G series, not F series |
| HG9Z-3C115A | Listed as a cable between IDEC Micro3 and MicroSmart (FC4A-PC2) equipment and the panel | No, PLC link, not a PC programming cable |
Generation matters more than connector shape. The WindO/I-NV4 manual for later panels directs models such as the HG2G-5T to a local area network when project data is downloaded, uploaded or monitored over the Ethernet port; the HG3F's documented path in the material here is the RS-232 cable above.
Why a guessed pinout is the wrong first move #
The request for pinouts has a short answer: the assignments are not published in the documentation available for this cable, so there is nothing trustworthy to wire from. A connector that fits proves nothing about signal assignment. Swap transmit and receive, or land a ground differently, and the port never communicates while you spend hours believing the panel is faulty.
Treat transmit and receive swaps and loopback jumpers as out of bounds here: without the official assignments you cannot predict what those tests do to the port, and a miswired port can look exactly like a software fault during troubleshooting. Where a manufacturer does publish a pin map, building or verifying against it is the right move, and the RS-232 pin map for DH-485 HMI wiring is an example of that documented case. This cable is not that case.
Upload procedure, in order #
- Read the nameplate and write down the exact model. HG3F and HG3G differ by one letter and by cable family: the F series takes the HG9Z-XCM1A, the G series takes the USB cable HG9Z-XCM2A.
- Identify the cable by its marking, HG9Z-XCM1A. If the marking is gone, do not use that cable on this panel until its identity is confirmed.
- Check the PC side before the panel side: the cable needs one 9-pin RS-232 COM port. Confirm the port exists and appears in the PC's device list.
- Check the software before connecting. Open WindOI-NV2, confirm the HG3F can be selected as the target model and that the upload function is available in this installation. A demo or unlicensed installation can block transfers, and the demo's limits are not documented in the material available here. If the function is unavailable, the blocker is the license, so resolve that with the vendor rather than experimenting with hardware.
- With the machine stopped and in a safe state, connect the cable between the PC port and Serial Interface 2 on the panel. One safety note, once: a transfer rewrites what the operator sees, so never start one on a machine mid-cycle, because a blank or half-written project on a running machine is an operational hazard.
- Use the software's documented transfer function to upload the project out of the panel into a new file, and save that file untouched. It is your only copy of what the machine actually runs.
- Edit a copy, reselect the exact panel model, then download. Record the project version, the date and the transfer result so the next shift can tell the original from the edited program.
- Verify before restart: the software reports a completed transfer, and the intended project on the intended panel passes the machine's commissioning checks.
Worked example: uploading from an HG3F when the PC has no 9-pin RS-232 port #
The case: an HG3F on the machine, WindOI-NV2 on a modern laptop, and the cable question already answered.
Inputs:
- Panel: HG3F, read from the nameplate.
- Cable: HG9Z-XCM1A from the vendor accessory listing; PC side one 9-pin RS-232 connector, panel side Serial Interface 2 with a mini-DIN 8-pin connector.
- PC: laptop with zero native 9-pin RS-232 ports, USB only, from your own bench.
- Software: WindOI-NV2 installed, with version and license status still to check.
Rule in words: the cable needs one working 9-pin RS-232 port. Count what the PC has and subtract. The connection is ready only when the shortfall is zero.
Arithmetic: ports required = 1; ports available = 0; shortfall = 1 - 0 = 1 port. Substitute check: the USB alternative HG9Z-XCM2A is documented for four series, the HG1G, HG2G, HG3G and HG4G; F-series panels among them = 0; 0 is less than the 1 needed, so it is not a fix for this panel.
Result: a shortfall of 1 port. The connection is not ready, and no communication setting changes that.
Decision, with its threshold: any shortfall above zero ports stops the job. Close it one of two ways, a PC with a native 9-pin COM port, or a USB path the vendor documents for this cable and software. A generic USB-to-serial adapter is acceptable only with that vendor documentation; without it, the committed answer is the native port.
Separating cable faults from software limits #
A failed transfer has four possible parents, and the error text alone does not name the guilty one: the cable identity, the PC port, the software's model support, and the software's enabled functions. Sort them in that order.
| What you see | Check first | Why |
|---|---|---|
| WindOI-NV2 does not list the HG3F | Software version and model support | No cable adds a model to the list |
| Upload or transfer function unavailable | License status of the installation | Demo or unlicensed installs can block operations |
| No COM port appears on the PC | Port, and the cable part-number marking | The path does not exist yet |
| Transfer starts, then stops | Communication settings and connector seating | The path exists; settings or continuity are suspect |
If it still fails, record five things before touching anything else: the panel model from the nameplate, the cable part number, the WindOI-NV2 version, the exact on-screen message, and the step where communication stopped. Recheck the cable marking and the model list once, then escalate with that record instead of repeating transfers. Leave the panel's existing program alone: never download over it to test the link.
After the transfer #
A completed transfer message is the start of verification, not the end. Confirm the intended project is on the intended panel, walk the edited screens through the machine's commissioning checks, and only then release the machine to operation. Keep the untouched upload file from step 6 archived with the transfer record.
When the panel goes back onto its serial link to the PLC, distance and loading limits come back into play, and the guide to connecting multiple HMIs to one PLC over 200 ft of serial covers those trade-offs.
The decision for each case #
- HG3F with the HG9Z-XCM1A, a 9-pin COM port and a licensed WindOI-NV2: run the eight steps above. This is the supported path.
- No published pinout in hand: buy the cable, do not build it. The assignments are not in the available documentation, and an unverified lead risks the port.
- PC without a 9-pin port: the shortfall is 1, so close it with a native port or a vendor-documented USB path before connecting.
- Demo installation blocks the upload: the fix is a license from the vendor. Cable work will not unlock it.
- Nameplate reads HG1G, HG2G, HG3G or HG4G: different generation, so use the USB cable HG9Z-XCM2A instead.
Questions asked
Can I upload from the HG3F with the WindOI-NV2 demo version?
The demo's transfer limits are not documented in the material available here, so treat capability as unverified: open the installed version, confirm the HG3F is selectable and the upload function runs, and read the licensing screen before connecting the panel. A failure under a demo installation proves nothing about your cable. If the operation is blocked, the fix is a license from the vendor, not a hardware change.
Is the pinout of the HG9Z-XCM1A published so I can build one?
The documentation found for this cable gives the part number, the PC-side 9-pin RS-232 connector and the panel-side Serial Interface 2, but no pin assignments. Without assignments you cannot verify a hand-wired lead before it is connected, so the decision is to obtain the vendor cable rather than fabricate one.
Will the USB programming cable HG9Z-XCM2A work on an HG3F?
No. HG9Z-XCM2A is documented for the HG1G, HG2G, HG3G and HG4G touchscreens, a different generation from the HG2F, HG3F and HG4F family that HG9Z-XCM1A serves. Match the cable to the nameplate model, not to the connector shape.
Does the upload go through any serial port on the panel?
Use Serial Interface 2, the port the HG9Z-XCM1A documentation names for the PC connection. The material available here documents no other programming port on the HG3F, so treat any unnamed port as unverified rather than trying it to see.
What should I record if the upload fails partway?
The five-item record described in the fault-sorting section is what you hand over: the panel model from the nameplate, the cable part number, the WindOI-NV2 version, the exact on-screen message, and the step where communication stopped. Do not repeat transfers or rewire the cable to force it through.