Maybe 2025 is the year for GE drivers?
Not real likely, sorry. No client/sponsor has raised its priority for me.
I've just always used the built in OPC server.
My driver would likely target devices that use the earlier version of the protocol, and have no OPC Server option. 90-30 and various Fanuc robots ("HMI protocol") would be the target market.
2 Likes
That's exactly what we are waiting for! 
2 Likes
Hi Miguel, if %M variables are Discrete internal registers I don't understand why they have to be transferred to %R which are Word holding registers? Wouldn't %Q or %I make more sense
I recently had a project where we were using Ignition 8.1 and the PLCs were Rx3i PLCs. Looking up how to do it, I kept being brought to this thread, so I wanted to reply with my situation and what worked.
The PLC does have an OPC-UA option (OPC UA Access Level), but to turn that on, it requires a download to the PLC. This PLC didnât have that turned on and I try to avoid downloads any time I can. The second option is to have the tags in the PLC being Published External Read/Write. All the tags in the PLC were set to private, so AVEVA (and other HMI options) wouldnât be able to read the tags.
We used Kepware with a licensed GE Ethernet driver. That allowed us to connect to the PLC without having to download to the PLC to change the tags to be OPC UA or published externally. Inside the Ignition Gateway, we made an OPC connection to Kepware. You can use a tag export from PACMachine (.snf) to build your tags in Kepware when youâre building the Kepware - GE connection. Remember that in Ignition you will reference the tag names in Kepware.
1 Like