IMDTouchKnowledge BaseShop main store

Troubleshooting

Why a C-more Micro Will Not Power From an H2-SERIO Port

HMI and touchscreens Published 6 min read

Short answer

The H2-SERIO's three RS-232 ports supply no +5 V, so a C-more Micro panel that powered from the CPU's serial port goes dark on any of them. Feed the panel external DC power — the EA-MG-P1 option does that while Port 1's RJ12 keeps handling TX and RX — and leave the panel on its built-in Com Port 1 with Do-more Serial. Port 1 and Port 2 in the HMI name the panel's ports; A, B and C name the module's.

On this page
  1. Separate the power fault from the serial fault
  2. Why no SERIO port can power the panel
  3. Port 1 and Port 2 belong to the panel, A, B and C to the module
  4. Power the panel from an external DC source
  5. Power budget for two EA1 panels on one H2-SERIO
  6. Set the module port in Module Configuration
  7. Verify each panel and record what passed
  8. When the panel is past a power retrofit
  9. Questions asked

A C-more Micro that lights up on the Do-more CPU's serial port and goes dark on the H2-SERIO is not misconfigured — it is unplugged from power. The H2-SERIO's three ports carry RS-232 data only and source no +5 V, so an EA1 panel drawing power through the cable has nothing to run on at A, B or C. Power the panel from an external DC source — the EA-MG-P1 option does that while Port 1's RJ12 keeps carrying TX and RX — leave each panel on its built-in Com Port 1 with the Do-more Serial protocol, and set the matching module port in Module Configuration. Port 1 and Port 2 in the panel software name the HMI's own ports, never the module's.

Separate the power fault from the serial fault #

Read the display before touching a protocol. On this machine the panel communicated through the Do-more CPU's serial port and only went dark on the H2-SERIO — that pattern names the fault as power. Work the list in order:

  • Dark on a SERIO port but powered and talking on the CPU port: power fault. The module's ports source no supply voltage, and no port setting changes that.
  • Lights from an external supply but exchanges no data: power is solved; the fault is port selection, serial settings or the cable.
  • Dark everywhere, including the CPU port: check the external supply and its wiring before suspecting the serial side.
  • One panel runs, the second does not: each panel-to-port pair is an individual path; test the second on its own.

Why no SERIO port can power the panel #

The H2-SERIO and H2-SERIO-4 are three-port serial I/O modules that plug into the base to add ports to a Do-more H2 system, and the H2-SERIO's three ports are RS-232. The module information lists its own consumption at 80 mA @ 5 VDC, drawn from the base for its electronics, and its port connectors give nothing back: no +5 V output exists on A, B or C. The EA1 panel on this machine drew its operating power through the RJ12 while it sat on the CPU's serial port, which is why the same panel ran there and died on the SERIO. Same plug, no power behind it.

Port 1 and Port 2 belong to the panel, A, B and C to the module #

Two numbering systems meet in the panel software, and they have nothing to do with each other. Com Port 1 is the C-more Micro's built-in port; Com Port 2 exists only after the EA-MG-P1 option is fitted, and the EA1-S3ML catalog entry lists exactly one serial port. Ports A, B and C are the H2-SERIO's connectors. Selecting Port 1 in the HMI never points at a SERIO port, and no A, B or C choice appears on the panel side.

For two panels the working arrangement is the simple one: each EA1 uses its own built-in Port 1 with the Do-more Serial protocol, wired to its own module port. RS-232 on this module is point-to-point — one port, one panel — so two panels occupy two of the three ports and one stays spare.

Power the panel from an external DC source #

The fix used on this machine is the EA-MG-P1 option: it brings external DC power to the panel while Port 1's RJ12 keeps working for transmit and receive, so the serial path already proven on the CPU port carries over unchanged. Each panel that needs cable power gets its own arrangement.

If you feed the panel another way, use the input its own documentation names: the EA1-S6ML specification sheet documents a 5.0 VDC input with a 4.75–5.25 VDC window alongside a 12/24 VDC input. One safety note: confirm the voltage and pinout against the panel's documentation before applying power — an RJ12 that carries both power and data punishes guessed wiring.

Power budget for two EA1 panels on one H2-SERIO #

Inputs, each with its source:

  • Panels: 2 × C-more Micro EA1-S3MLW, the machine at hand.
  • H2-SERIO own consumption: 80 mA @ 5 VDC, per the module information.
  • +5 V available at ports A, B and C: 0 mA — the finding on this failure, no +5 V on the SERIO.
  • Documented EA1 supply inputs, per the EA1-S6ML specification sheet: a 5.0 VDC input allowed 4.75–5.25 VDC, and a 12/24 VDC input.

Rule in words: watts equal volts times amps, and a supply's allowed error is the window's width divided by the nominal voltage.

The arithmetic:

  • Module draw from the base: 0.080 A × 5 V = 0.40 W.
  • Power deliverable to a panel through any port: 0 A, so 0 W.
  • 5 V input window: 5.25 V − 5.00 V = 0.25 V, and 0.25 ÷ 5.00 × 100 = 5% high; 5.00 V − 4.75 V = 0.25 V, the same 5% low.

Result: the module takes 0.40 W from the base and delivers 0 W at its connectors; a 5 V feed is in spec only between 4.75 and 5.25 VDC under load.

Decision: any panel expecting more than 0 mA from its cable — every EA1 here — needs an external source. Fit EA-MG-P1 to each panel, or feed the documented 12/24 VDC input where the panel documents one; two panels means two power arrangements, and no Module Configuration setting moves that 0 W.

Set the module port in Module Configuration #

On the Do-more side, a SERIO port's function is selected in Module Configuration of the Do-more software. Copy what already worked: on this machine the module ports were configured the same way as the CPU's local port, and the CPU-port link talked — so baud rate, parity, data bits and stop bits match the panel end, and the protocol choice was never the fault. Confirm the endpoint you configure is the physical port the cable actually reaches; a correctly configured port B never carries a panel plugged into A.

Verify each panel and record what passed #

  1. Power one panel through the EA-MG-P1 or its documented external supply, and confirm it starts before connecting serial data.
  2. Wire that panel's built-in Com Port 1 to its module port, with the HMI still set to Do-more Serial on Port 1.
  3. Read a known PLC value at the panel, then write one value chosen to be safe to change.
  4. Repeat all three steps on the second panel over its own port — one panel's pass does not certify the second cable or port.
  5. Record the port labels, protocol, the four serial settings and the power arrangement that passed.

If the panel powers but the link times out, work the checks in HMI PLC communication timeout over serial next.

When the panel is past a power retrofit #

The EA1 series is listed among retired products, so a failing panel eventually stops being worth new power hardware. When that point comes, industrial panel PCs are the replacement path for a machine-mounted HMI terminal.

Questions asked

Why did the panel power up on the Do-more CPU's serial port but not on the H2-SERIO?

The CPU's serial port supplies the +5 V the EA1 panel draws through the RJ12, so it lit and communicated there. The H2-SERIO ports carry RS-232 data only — the module takes 80 mA at 5 VDC from the base for its own electronics and sources nothing at A, B or C. Moving the panel back to the CPU port is the quick confirmation: if it lights there again, the power gap is the module, not the panel.

Does fitting the EA-MG-P1 change the protocol or the PLC program?

No. EA-MG-P1 is a power and port accessory: it feeds the panel external DC power while the built-in Port 1 RJ12 keeps handling transmit and receive. The panel stays on Do-more Serial over Port 1, and the Do-more side needs only the module port configured in Module Configuration with the same serial settings that worked on the CPU port. Nothing in the module documentation calls for added ladder logic for the HMI link.

Which of the H2-SERIO ports should the two panels use?

Any two of A, B and C — the choice is wiring convenience, not configuration. All three are RS-232 and each is configured the same way in Module Configuration. Give each panel its own port, because RS-232 on this module is point-to-point: one port, one panel, one cable. The third port stays spare for a future device.

The panel powers now but still will not communicate. What next?

Match baud rate, parity, data bits and stop bits at both ends, and confirm the configured Do-more endpoint is the physical module port the panel is actually wired to. Then check the cable's transmit, receive and signal-ground assignments against the documented pinout. Change one item at a time and retest, and keep the CPU-port values that worked so you can restore a known-good setup.

Is selecting Com Port 2 in the panel software a way to reach the H2-SERIO?

No. The Port 1 and Port 2 choices in the C-more Micro software name the panel's own ports: Port 1 is built in, Port 2 exists only after the EA-MG-P1 option is fitted. Selecting Port 2 without that hardware selects a port the panel does not have. The module's A, B and C never appear in the panel software at all — the panel only cares that its own Port 1 carries Do-more Serial.

Keep reading

  • How-to

    Connecting Multiple HMIs to One PLC Over 200 ft Serial

    RS-232 on good cable can reach 200 ft at 9600 baud, but RS-232 connects exactly two devices, so three HMIs cannot share one PLC port. Put an RS-232-to-RS-485 adapter at the PLC and at each panel, daisy-chain one twisted pair, and terminate only the two ends. Confirm the PLC port's protocol accepts more than one master before ordering adapters.

    Industrial networks

  • Troubleshooting

    Why an HMI Freezes or Updates Slowly Over Serial

    A panel-wide freeze or slow updates over serial is a link fault — driver, PLC port, wiring, or startup timing — not a screen-object fault. Test the two field-proven fixes first: a 10-second startup delay before the first poll, and a port set to four-wire RS-422 at 19,200 baud. Fix an isolated stale tag separately, by address and data type.

    HMI and touchscreens

  • Troubleshooting

    Fixing HMI Modbus Device No Response Over RS-485

    Device no Response means the slave never returned a valid frame to that request. When a PC polling tool reads the same scanner, the bus is probably carrying two masters: run one master at a time, then copy the known-good read's serial settings, station address, and register offset into the HMI.

    HMI and touchscreens