Has anyone had any experience connecting Ignition via the MODBUS TCP driver to an SEL3530 RTAC? Any problems?
Thanks.
crickets
Maybe nobody has ever done this. Why don’t you hook it up and let us know how it went? If you get stuck feel free to call in or post back here and we can help you out.
I have hooked it up to a SEL-3354 running SubStationServer.net.
This is basically the same equipment as a new GE D25
Great, seems promising then. Thanks.
Works well, very simple setup.
Hi, seems that you were able to connect to a SEL rtac, could you share how you did that.
I can connect to the RTAC with the user name/pwd and also the RTAC is collecting modbus data into its own database, but how did you managed to get that data into ignition?
You have to configure a Modbus server in the RTAC and map the data to it using the RTAC Tag Processor. Then the data will be available to any Modbus master, such as Ignition.
Exactly what my thinking was and did it as soon as I saw your reply.
Tried too many things, this one was easy.
Thanks again
I also have the SEL-3530 RTAC and connection issues. I have set up my Tab Browser to store Modbus TCP registers. We also have an instance of SkySpark communicating to the SEL-3530 with no issues. Under the OPC UA -> Device Connections, the device keeps connecting/disconnecting. Using the SEL-3530 onboard packet capture, it shows that the Ignition server sends a handshake request with [SYN, ECE, CWR], but then the Ignition gateway does an immediate TC Retransmission. Through some research, the [SYN, ECE, CWR] both ends need to be ECN enabled. Does anyone know if Ignition gateways are ECN enabled? Or, does anyone know of additional troubleshooting to resolve the connection issue?
Generally, yes, via the operating system they run on. Are you sure that handshake isn't being disturbed by some router in the middle?
(See if a wireshark capture from the Ignition side show the same thing.)
No, both the Ignition server and SkySpark server are on the same subnet. If there was an issue with the router, SkySpark would not work either. I have shared the packet capture with my IT group and they have verified no issues with the router or firewall.
Based on the Wireshark screenshot you deleted, the TCP Retransmission is after three seconds of no reply from the RTAC. That's not "immediate", that's appropriate for an initial handshake that the target has dropped.
On a LAN, there should have been a response from the RTAC in a fraction of a millisecond.
Your problem is on the RTAC.
Checking the RTAC now. SkySpark and Ignition are set up almost identically with Modbus TCP configurations. Very shocking that it can't keep the socket open with Ignition but can with SkySpark.
The more I'm exposed to SEL products with various clients the less impressed I am. That they have near-total lockout of anyone else in the power industry is what is shocking to me.
From my experience, this is one of the best products for being a substation electrical engineer. The RTAC lineup is so powerful, but does have their nuances.
@pturmel you wer correct sir! The SEL RTAC-3530 has an on-board firewall network configuration that requires a server, Ignition, to be bound to a "Server Client" relationship within the Tag Processor. As soon as I created a Server for the Ignition IP address, everthing connected. My Tag Processor was already set up with Modbus registers. Once it connected, I have good data.
1 Like