IMDTouchKnowledge BaseShop main store

How-to

Connecting an HMI to a GE Fanuc PLC Over Ethernet SRTP

HMI and touchscreens Published 6 min read

Short answer

Yes. GE controllers speak SRTP, their native Ethernet protocol, on TCP port 18245, and the HMI editor's built-in GE Fanuc SRTP driver needs no Modbus TCP and no purchased add-on. VersaMax CPUs with integrated Ethernet serve SRTP only, and a Series 90-30 needs CPU firmware 8.xx before its IC693CMM321 Ethernet module will cooperate.

On this page
  1. Why SRTP is the native path
  2. What each controller supports
  3. Prepare the PLC side first
  4. Add the GE Fanuc SRTP driver in the HMI editor
  5. Addressing tags in GE memory areas
  6. Worked example: fault-delay budget for the default timeout with 3 retries
  7. When the link fails anyway
  8. Questions asked

Yes, and you need neither Modbus TCP nor a purchased driver. GE Fanuc controllers speak SRTP, GE's native Service Request Transport Protocol, over Ethernet on TCP port 18245, and nearly every GE controller with an Ethernet port serves it. HMI editors that list a GE Fanuc SRTP driver connect straight to it. Two facts decide how smooth the job is: a Series 90-30 must run CPU firmware 8.xx or later before its IC693CMM321 Ethernet module cooperates, and VersaMax CPUs with integrated Ethernet serve SRTP only — which is exactly why a Modbus-only attempt looks impossible on those machines. The steps below cover the PLC side, the driver settings, GE memory addressing, and the checks that find a dead link.

Why SRTP is the native path #

SRTP is the protocol GE built for its own Ethernet equipment: the PLC side runs an SRTP server, the panel acts as the client, and the service carries reads and writes of every GE memory area. The default TCP port is 18245. Because it is the vendor's own protocol, almost every GE controller with an Ethernet port speaks it — 90-30, 90-70, VersaMax and the PACSystems CPUs.

The GE Fanuc SRTP driver sits in the HMI editor's driver list and needs no license, dongle or separate download. It covers the 90-series PLCs, including the 90-70 and 90-30, and through its PLC-type setting it reaches VersaMax and the PACSystems racks.

Modbus TCP exists on these controls only where a module adds it: the IC693CMM321 at module firmware 2.30 or later, and the PACSystems Ethernet modules. VersaMax never gains it on the integrated CPU port. That asymmetry is the whole story behind "GE Fanuc doesn't support Modbus TCP" — true on VersaMax, optional elsewhere.

What each controller supports #

Controller Ethernet hardware SRTP Modbus TCP Condition to watch
Series 90-30 IC693CMM321 module Yes Yes, at module firmware 2.30 or later CPU firmware 8.xx minimum; CPU331 kit 44A731232-G16
VersaMax, integrated Ethernet IC200CPUE05 CPU Yes No CPU firmware 2.10 minimum for the port
VersaMax modular IC200ETM001 module Yes No For racks whose CPU has no Ethernet
PACSystems RX3i IC695ETM001 Yes Yes SRTP reads all memory areas without mapping
PACSystems RX7i IC698ETM001 Yes Yes Same trade as RX3i

The decision by controller: on a 90-30, use SRTP through the CMM321 once the CPU firmware floor is met. On any VersaMax, use SRTP and stop trying Modbus. On RX3i and RX7i, prefer SRTP and enable Modbus TCP only when a second, non-GE system needs port 502.

Prepare the PLC side first #

  1. Check the firmware floor. On a 90-30 the CPU must run 8.xx or later; a CPU331 gets there with upgrade kit 44A731232-G16 at its latest revision. On a VersaMax IC200CPUE05, firmware 2.10 is the minimum for the Ethernet port.
  2. In the hardware configuration of your GE programming software, open the Ethernet module or CPU and set the IP address, subnet mask and gateway. With mask 255.255.255.0, the panel and the PLC must share the first three address octets, such as 192.168.1.x.
  3. Leave the SRTP server enabled — it is on by default, listening at port 18245. Enable the Modbus TCP slave on port 502 only on a CMM321 at firmware 2.30 or later, and only if a second system needs it.
  4. Download the hardware configuration, then power-cycle the module; the IP settings apply at that power cycle. Do this with the machine stopped or in a safe state, because every HMI and SCADA session on that module drops when it reboots.

Add the GE Fanuc SRTP driver in the HMI editor #

  1. In the project's I/O manager, add a new driver and pick the GE Fanuc SRTP Ethernet driver from the built-in list.
  2. Enter the PLC's IP address — for the example configuration, 192.168.1.10 — and leave the port at 18245.
  3. Leave the timeout at the driver default of 3000 ms and the retry count at 3. Move the timeout to 5000 ms only on a slow path; the worked example below shows what that costs you.
  4. Add an equipment node under the driver and set its PLC type to 90-30, VersaMax or RX3i to match the rack.
  5. Create the tags with GE memory references; the panel reaches %I, %Q, %M, %AI, %AQ and %R directly, with no register map to build.
  6. Build, download the project to the panel over Ethernet or USB, and confirm the driver's connection status before you build screens.

Addressing tags in GE memory areas #

Memory area Carries Example address
%I Discrete inputs %I00001
%Q Discrete outputs %Q00001
%M Internal coils %M00001
%AI Analog input registers %AI00001
%AQ Analog output registers %AQ00001
%R Internal register words %R00001
%SA, %SB, %SC System status bits %SA00001

The reference table in the PLC program is the authority for how many references of each area the CPU actually owns; the driver can only reach references the CPU has configured.

Worked example: fault-delay budget for the default timeout with 3 retries #

The case: a panel on the same switch as a Series 90-30 whose IC693CMM321 carries the link, with the driver at its default settings.

Inputs, each with its unit and origin: the timeout, the driver default stated above; retry count 3, the driver default; 5000 ms, the timeout the slow-network guidance suggests; panel and PLC share one switch, which is the connection this article builds.

The rule in words: the driver reports a communication fault only after the first attempt and every retry have timed out, so the worst-case delay before the operator sees the fault is the timeout multiplied by the number of retries plus one.

The arithmetic: at the default, 3 s per attempt × (3 + 1) = 12 s. On the slow-network setting: 5000 ms × (3 + 1) = 20,000 ms = 20 s.

Result: raising the timeout from the default to 5000 ms adds 8 s of dead time between a pulled cable and the alarm on the panel.

Decision: keep the default with 3 retries on any same-switch link — 12 s worst case is the number to quote when someone asks how fast the panel reports a dead PLC. Take the 5000 ms setting only on a link that genuinely drops packets, and if the requirement is an operator alarm within 15 s of losing the PLC, the 5000 ms setting fails it and the default passes.

  • Every tag faults right after download: wrong IP, wrong mask, or a port other than 18245. Ping the PLC address, confirm the panel sits in the same subnet, and read the port back from the driver properties.
  • Ping succeeds but tags still fault: the CPU is in STOP — a VersaMax refuses SRTP sessions until it runs — or, on a 90-30, the CPU sits below the 8.xx floor and leaves the module faulted. Check the module's LEDs.
  • Module fault LED solid: CPU firmware below the floor, or the hardware configuration never downloaded. Reflash the CPU, redownload, power-cycle.
  • Tags read but return zeros: wrong memory area. %AI and %R are not interchangeable; check the area letter and the reference number against the PLC program.
  • Timeouts that come and go with several clients attached: the module serves a limited number of simultaneous sessions; drop the HMI poll rate or disconnect the programming laptop.

For hangs that appear and recover rather than hard-failing, the sequence in diagnosing intermittent HMI to PLC Ethernet comms hangs applies to SRTP links the same as to any other Ethernet protocol.

Questions asked

Can a VersaMax CPU with built-in Ethernet speak Modbus TCP at all?

No. Integrated-Ethernet VersaMax CPUs such as the IC200CPUE05 serve SRTP only, and port 502 never opens on them, so a Modbus TCP driver just times out. Point the GE Fanuc SRTP driver at the CPU's address on port 18245 instead. On a modular VersaMax rack, the IC200ETM001 Ethernet module also speaks SRTP, so SRTP is the path there too.

Which firmware does a Series 90-30 need before the IC693CMM321 will work?

The CPU must run firmware 8.xx or later; on a CPU331 that means upgrade kit 44A731232-G16 at its latest revision. Below that floor the module faults and sessions fail. The CMM321 itself needs firmware 2.30 or later only if you also want its Modbus TCP slave on port 502 — plain SRTP does not require it.

Is the SRTP port fixed at 18245, or can it be changed?

18245 is the default on both the PLC side and the panel driver, and network monitors identify GE SRTP traffic by that port number. You can change it where the panel reaches the PLC through a NAT firewall, but the number you pick must then match in the module configuration, in the driver, and in the router rule.

The panel pings the PLC but every tag faults. Where do I look first?

Ping only proves the address and mask are sane. Next confirm the driver uses the PLC's actual address with port 18245 and that the CPU is in RUN rather than STOP — a VersaMax refuses sessions until it runs. On a 90-30, a CPU below the 8.xx firmware floor leaves the module faulted, so check its LEDs before touching the panel.

Keep reading

  • Selection guide

    Selecting a Modbus TCP HMI Panel for an Existing Controller

    A replacement HMI qualifies when its Modbus TCP client driver reproduces the working panel's tag map exactly: data area, raw address, word order and write behavior. A connection that polls proves reachability, not correctness — prove one known tag and one supervised write before rebuilding the screens.

    HMI and touchscreens

  • How-to

    Connecting an HMI Panel to an S7-1500 PLC

    Confirm the HMI's documented driver covers the S7-1500 for your exact panel model and software revision, put the panel and CPU on the same subnet, permit the connection in the CPU protection settings, then validate one known PLC tag before building screens. A working Ethernet link alone proves nothing about tag access.

    HMI and touchscreens

  • Troubleshooting

    Connecting a CompactLogix PLC to an HMI over EtherNet/IP

    A CIP transport unsupported fault on a Generic Ethernet/IP module in a CompactLogix project means the connection was built the wrong way around. For HMI tag access, delete the module, select the panel's Rockwell PLC driver, point it at the controller IP, and rebuild the tags — no assembly instances, I/O sizes, or EDS file.

    HMI and touchscreens