How-to
Relaying serial PLC data through a C-more HMI to SCADA
Short answer
The C-more EA9 is a communications client: it polls the PLCs it is configured for and exposes nothing for Ignition or KepServer to browse. Make the panel the relay instead — add a Modbus TCP server as a second PLC device and copy FX3 tags into it with Tag Copy events triggered from the system clock tags, since scheduled copies run at best once per minute.
On this page
- Why the panel cannot be the poll target
- Choose the protocol the panel will speak
- Stand up the server-side target
- Add the second device in the C-more editor
- Drive the copies from the clock, not the schedule
- Worked example: FX3 status into Ignition on the slowest clock tag
- Verify the relay end to end
- When to retire the relay
- Questions asked
Point an Ignition or KepServer driver at a C-more EA9-T8CL's IP address and browse for tags, and you get nothing usable — the panel is a communications client. It polls the PLCs it is configured for and publishes no tag database of its own. The arrangement that works with the hardware already on the machine makes the panel the relay: leave the FX3 on its serial link, add a second, Ethernet-side PLC device that is actually a Modbus TCP server in your SCADA software, and copy tags across with Tag Copy events. Trigger those copies from the panel's internal system clock tags, because a scheduled event runs at best once per minute. The path — FX3 to panel to server to Ignition — is a proven pattern for controllers with no Ethernet of their own.
Why the panel cannot be the poll target #
The EA9 series supports EtherNet/IP, Modbus TCP, Modbus RTU and ControlLogix EtherNet/IP tag messaging — but on protocols where a client exists, the panel is the client. Ignition and KepServer drivers connect as clients too, and they expect a server with an addressable database at the far end. The panel has none to offer: its tags are screen objects bound to PLC addresses, read on the panel's initiative. It is the same direction rule that settles an HMI OPC UA server vs client link: whoever initiates owns the conversation, and this panel only initiates.
One condition before you build anything: if the FX3 values on the panel are already stale or intermittent — the fault class behind HMI indicators staying off over Modbus RTU polling — fix the serial side first. Every relayed value inherits the faults of the poll it came from.
Choose the protocol the panel will speak #
Three Ethernet options on the EA9 do this job. Pick one before opening the editor, because everything downstream depends on it.
| Protocol on the panel | Panel role | SCADA side runs | Data moves | Use it for |
|---|---|---|---|---|
| Modbus TCP | Client | A Modbus server, such as a server driver on the Ignition gateway | Tag Copy events | Monitoring; fastest to commission |
| AB Logix tag protocol | Client | A virtual Logix-style target | Tag Copy events | Sites already using Logix tag names |
| EtherNet/IP I/O | Adapter | An EtherNet/IP scanner opening a cyclic connection | Cyclic, at the connection interval | Commands, including momentary buttons |
The momentary-button row is the one that bites. Copy events move data in discrete writes, so a press-and-release on the touchscreen can fall entirely between two copies and never reach the destination. The EtherNet/IP I/O adapter connection is cyclic: the scanner exchanges the whole data set every connection interval, so a button held even briefly is seen. Decision: monitoring only, run Modbus TCP on port 502; if operators command the process through this path, run EtherNet/IP I/O.
Stand up the server-side target #
- Enable the receiver: a Modbus server driver on the Ignition gateway. Any Modbus TCP server works the same way, including one that KepServer reads from.
- Lay out one contiguous holding-register range and one coil range, sized for the tags you will relay. Do not interleave data types.
- Write the register map before touching the HMI editor: FX3 address, HMI source tag, destination register, data type, scaling. Fix 32-bit word order in the map now — when values arrive scrambled, the method for swapping words on a C-more 32-bit Modbus tag is the fix, and it belongs in the map, not in a live scramble.
- Open the server host's firewall for TCP 502.
- Prove the server first: from a laptop with a generic Modbus client, write a value into a register and watch the matching Ignition tag move. If this fails, stop — no panel setting repairs a server that refuses writes.
Add the second device in the C-more editor #
- Open the project and add a new PLC device on the Ethernet port with the protocol you chose, the server's IP address, and 502 as the PLC port in the Panel Manager PLC connection settings. The PLC IP address must match the server. Leave the FX3 serial device exactly as it is.
- Confirm the panel's own IP and subnet reach the server, and make sure the panel IP settings are stored in the project so a later download does not undo them.
- Create destination tags from the map, with a prefix that keeps FX3 source tags and relay tags from ever being confused.
- Download, then watch the panel's communication status for the new device. A timeout here is one of three things: a wrong IP or subnet on the panel, a blocked port 502, or a unit ID mismatch on the server.
Drive the copies from the clock, not the schedule #
The Event Manager's Tag Copy action copies the value of one tag to another tag, and each Tag Copy is its own event and action — there is no block copy of a range. Event conditions can combine up to four tags when a copy should run only under some logic.
On a schedule, the fastest these events run is once per minute. That is fine for production counts and shift totals and useless for live status. The panel's internal system tags toggle at 250 ms, 500 ms and one second, and a tag-change event on one of them fires your copy actions at that rate.
Start on the slowest of the three. The processor that runs clock-driven copies also runs the screens and the FX3 serial poll, and overload announces itself as sluggish touch response, slow screen changes, or stale FX3 values on the panel itself. Any of those: back off the trigger rate before you touch anything else.
Worked example: FX3 status into Ignition on the slowest clock tag #
Inputs, each with its source:
- Scheduled-event floor: 1 copy per 60 s, the panel's fastest scheduled rate.
- The three internal system tags from the panel's system tag set, toggling at 250 ms, 500 ms and one second.
- Path: FX3 register, then the panel's serial poll, then a Tag Copy, then a Modbus TCP write, then the Ignition tag.
Rule in words: a relayed value is no fresher than one trigger period at the copy step, and copies per minute equal 60 s divided by the trigger period.
Arithmetic:
- Scheduled: 1 copy per 60 s, which is 1 copy per minute.
- Slowest tag: 60 s ÷ 1 s = 60 copies per minute, 60 times the scheduled rate.
- 500 ms = 0.5 s: 60 s ÷ 0.5 s = 120 copies per minute.
- 250 ms = 0.25 s: 60 s ÷ 0.25 s = 240 copies per minute — and, for the same tag count, 240 ÷ 60 = 4 times the copy work of the slowest setup.
Worst-case age of an FX3 change when it appears in Ignition: one FX3 poll period on the panel, which is the same staleness the screen already shows, plus one trigger period. On the slowest tag that is at most the screen's own delay plus one second.
Decision: anything that tolerates 60 s — counters, totals, shift data — stays on the schedule. Anything an operator would call status goes on the slowest clock tag. Drop to 500 ms or 250 ms only if the panel stays responsive under normal screen use. Anything that must be seen faster than 250 ms, or any momentary command, does not belong on copies at all: put it on the EtherNet/IP I/O connection or give the controller its own Ethernet path.
Verify the relay end to end #
Walk one point of each type the whole way — FX3 register, HMI source tag, HMI relay tag, Ignition tag — checking value, sign and word order on 32-bit data.
Pull the panel's Ethernet cable: the Ignition tags must flag bad or stale quality, not hold the last value. Add a heartbeat, a counter incremented on every copy, and alarm on it in Ignition so a silent stall pages someone.
Cycle power on the panel: both devices reconnect and the copies resume with no one touching anything.
Then run a full shift with operators using the screens normally, and watch touch response and screen-change speed. Those are the first symptoms of copy overload, and they show up on the floor before they show up in the data.
When to retire the relay #
The relay buys monitoring without new hardware on the machine, and that is all it buys. When the FX3 gets an Ethernet connection of its own, point Ignition at the controller directly, read the source registers, and delete the Tag Copy events. The panel goes back to the job it is built for: a client with screens.
Questions asked
Does the C-more EA9 support Modbus TCP and EtherNet/IP?
Yes. The EA9 series supports EtherNet/IP, Modbus TCP and Modbus RTU, along with ControlLogix EtherNet/IP tag messaging. For this relay the panel is the Modbus TCP client, so the SCADA side runs the server: enter 502 as the PLC port in the Panel Manager PLC connection settings and point the PLC IP address at the server.
Can Ignition or KepServer browse the tags already in the panel?
No. The panel is a client to the PLCs it polls and does not publish its tag database for browsing. Client drivers in Ignition and KepServer expect a server at the far end. That is why the working pattern is PLC to panel to server: the panel writes outward into a Modbus TCP server, and the SCADA software reads its own server.
How fast can a Tag Copy event run?
On a schedule, once per minute is the fastest. Fired from a tag-change event on the internal system clock tags, copies run at 250 ms, 500 ms or one copy per second. Start at the slowest rate: sluggish touch response, slow screen changes or stale FX3 values on the panel mean the copy rate is loading the processor, so back off before adding tags.
Why do momentary pushbuttons need the EtherNet/IP I/O path?
Because a press and release can fall entirely between two Tag Copy events, so the pulse never reaches the destination; the cyclic EtherNet/IP I/O connection described above is what catches it. Use that path whenever operators command the process through the relay, and keep copies for monitoring.