How-to
How to Upload an E200 HMI Project Over CAB5
Short answer
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.
On this page
- How do I see the hardware and software version on an E200?
- Does the E200 have to be put into a transfer menu first?
- How is the CAB5 cable wired for the E200?
- Why does the 2-3, 3-2 null-modem cable fail on the E200?
- How do I connect when the PC has no COM port?
- What are the steps to upload the project from the E200?
- How long can the CAB5 cable be?
- What should I check if the upload still times out?
- Questions asked
Start the upload from E-Designer itself — the Upload function, which the tool and its users also call Receive — because the Mitsubishi E200 switches itself into transfer mode the moment the PC calls. The one thing that routinely breaks this job is the cable: the CAB5 between the PC and the E200 is straight-through, pin 2 to 2, pin 3 to 3 and pin 5 to 5, and the 2-3/3-2 null-modem cable that looks correct on paper is exactly what produces the timeout. Power-cycle the panel first, photograph the HW and SW versions on the splash screen, then work through the steps below.
How do I see the hardware and software version on an E200? #
Power the terminal off and back on and watch the startup screen: the E200 shows its hardware (HW) and software (SW) revision strings there during boot, which is the pair of numbers that decides which E-Designer build can open the project you upload. Cycle the 24 VDC supply and photograph the splash as it appears, because the strings sit on screen for only a few seconds. Record both numbers: an HW mismatch can demand a different editor build, while an SW mismatch is usually handled by opening and re-saving the project in a newer editor. If the splash scrolls past too fast or the backlight is weak, the terminal's system menu carries the same version information. The same discipline applies after any panel swap — it is the check behind verifying the HMI project version running on a panel, and it costs you one power cycle.
One safety note: confirm supply voltage and polarity at the connector before repowering a terminal that has come off a machine.
Does the E200 have to be put into a transfer menu first? #
No: the E200 changes into transfer mode by itself when you start an Upload or a Download in E-Designer, so the entire recovery runs from the PC with the terminal sitting at its normal startup state. The documentation for this terminal family puts it plainly: the operator terminal automatically changes to transfer mode and receives the project once the transfer starts from the PC. Leave the panel powered at its startup screen and stay off its menus. Manual entry into transfer mode is only for the dead cases — a crashed runtime, a project password, or a menu the original developer hid — and even then it is one selection in the terminal's own system menu before you click Upload on the PC. Upload and Download behave the same way; the panel answers whichever direction E-Designer initiates.
How is the CAB5 cable wired for the E200? #
Straight through on all three lines: DB9 pin 2 to pin 2, pin 3 to pin 3 and pin 5 to pin 5, with a female DB9 at each end of the CAB5 that plugs into the PC and the E200.
| CAB5 pin at the PC end | Signal on the PC port | Lands on at the E200 end |
|---|---|---|
| 2 | RXD — the PC receives | Pin 2 |
| 3 | TXD — the PC transmits | Pin 3 |
| 5 | Signal ground | Pin 5 |
TIA-232-F governs the electrical side of this link, and on the 9-pin connector the PC convention is pin 2 receive, pin 3 transmit, pin 5 ground. The E200's port presents the complementary assignment, so the cable carries no crossover at all — the two pinouts do the crossing for you. If one cable has to serve several terminals, the CAB5 pinout compatibility between the E200 and E1000 family maps which terminal takes which wiring, because the straight map above is settled for the E200, not for every panel that shares the connector.
Why does the 2-3, 3-2 null-modem cable fail on the E200? #
Because the crossover sends the PC's transmit pin onto the E200's transmit pin, so both devices talk and neither listens, and E-Designer reports a timeout instead of a completed upload. A null modem exists for two ports wired identically — two PCs, both transmitting on pin 3. The E200 already mirrors the PC's pinout, so adding the crossover puts transmit against transmit and receive against receive: the panel never sees the connect request, the PC never sees an answer, and the transfer dies waiting. The signature is a clean timeout or a no-response error, not garbage characters. If a store-bought null-modem or file-transfer cable is what is on the bench, the fix is a re-pin to the straight map, not a settings change.
How do I connect when the PC has no COM port? #
Use a USB-to-serial adapter with a signed driver — adapters built on FTDI, Prolific or Silicon Labs chipsets are the usual industrial choices — then read the COM number Windows assigns and type that number into E-Designer's communication settings. Open Device Manager, look under Ports (COM & LPT) for the number the adapter took — COM3, COM4 or COM7, whatever your machine shows — and select that exact port before starting the transfer. Prefer an adapter on a rear port rather than one sharing a hub with high-bandwidth devices, because enumeration hiccups drop bytes mid-transfer. Adapters on older Prolific chips sometimes need their specific driver generation before Windows will hand out a COM number at all.
What are the steps to upload the project from the E200? #
Ring out the cable, note the versions, connect the adapter, set the port, start Upload in E-Designer and save the arriving project immediately — six steps in the order you meet them.
- Power-cycle the E200 and photograph the HW and SW versions from the boot splash.
- Ring out the CAB5 end to end with a continuity meter: 2 to 2, 3 to 3, 5 to 5. Re-pin anything that crosses.
- Connect the USB-to-serial adapter and note the COM number Windows assigns in Device Manager.
- Open E-Designer's communication settings and select that COM port.
- Start the Upload (Receive). Leave the panel's menus alone — it switches to transfer mode on its own.
- Save the arriving project under a new name straight away and treat that file as the master copy.
On a machine with no archived project anywhere, that saved file becomes the only copy in existence — the same starting point as replacing an old HMI when no project files exist. If this job landed on you because an earlier supplied file turned out to be a GOT project rather than an E-Designer one, E200 recovery when the supplied file is a GOT project is the separate path for that mismatch. And when the terminal itself is the reason for the work, the saved project is what you rebuild from on industrial panel PCs once the old panel comes off the door.
How long can the CAB5 cable be? #
The TIA-232-F guideline is 15 m (about 50 ft) at bit rates up to 19,200 bps, and most bench uploads run a tenth of that, so cable length is rarely the reason an E200 transfer fails. Keep the run short anyway near drive cabinets, where the noise floor is high. An illustrative time check shows the length is not a throughput problem: at 19,200 bps with a 10-bit frame — 1 start, 8 data, 1 stop — the line carries 19,200 ÷ 10 = 1,920 bytes per second, so a 200,000-byte project takes 200,000 ÷ 1,920 ≈ 104 seconds. Call that a two-minute floor, since the transfer protocol adds overhead on top. An upload that times out in the first half-minute is telling you the cable map or the COM setting is wrong, not that the line is slow.
What should I check if the upload still times out? #
Work through three checks in this order — confirm the cable map with a meter, confirm the COM number in Device Manager, and confirm the terminal is sitting alive at its startup screen — before you suspect the panel itself.
- Ring the cable again with both ends free and confirm nothing crosses between pins 2, 3 and 5.
- Match the COM number exactly between Device Manager and E-Designer, and close any other program that may be holding the port.
- Watch the panel while the PC calls: if a crashed runtime or a password screen holds it, put the terminal in transfer mode from its own system menu, then retry.
- Re-cycle power and confirm the splash still shows both version strings — that proves the terminal is alive and booting.
If every check holds and the PC still gets silence, the fault is in hardware at one end of the cable — the adapter or the panel's serial port. That is the point to stop debugging the transfer and start deciding whether the terminal is worth repairing.
Questions asked
How can I test a CAB5 cable without a panel connected?
Set a multimeter to continuity and ring it end to end with both connectors free. Pin 2 should beep only against pin 2, pin 3 only against pin 3, and pin 5 only against pin 5. If pin 2 beeps against pin 3, you are holding a null-modem cable, and it will time out on the E200 even though it works fine on other equipment.
Does the upload also back up the panel's firmware?
No. The upload reads the project — screens, tags and alarms — out of the terminal's memory. Firmware is a separate image tied to the SW revision on the boot splash, and it stays on the panel. If firmware is ever needed, it comes from the manufacturer's official download for that exact terminal, never from this transfer.
Can the E200 transfer over the network instead of serial?
Terminals in this family that carry a network option can be switched to it with the "Use TCP/IP transfer" setting in their settings menu before you start from E-Designer. A basic E200 on a CAB5 link has no network path in play, so plan on the serial upload. The automatic transfer-mode switch behaves the same either way.
Can I download the uploaded project straight into a spare E200?
Yes, provided the spare's hardware revision matches what the project targets and its software revision is not older than the project. Read both versions from each panel's boot splash before you transfer. A mismatch is why a download refuses or arrives with conversion warnings. Keep the original upload untouched and download from a saved working copy.