SCADAPack 474 / Trio QR Ethernet Networking

[RianL]

Hello,

I can't seem to get our SCADAPack 474 to communicate with a Trio QR radio network via the ETH1 port. Another Trio is connected to ETH2 and communicates just fine with its point-to-point network. Both ETH ports are on the same respective subnets as their connected Trio radios. The wider network connected to the ETH1 Trio uses IP routing and includes one repeater. I suspect I am missing an IP route or have an incorrectly configured gateway but nothing I try seems to work. I have included an abbreviated network map (addresses modified for security). Any assistance would be appreciated.

[BevanWeiss]

You're likely going to have to work through your route tables here.

Your remote sites will likely need to at least send 'default' stuff to the repeater WAN IP.

The repeater would then need to know each LAN subnet, and what the WAN IP of the radio for it is.

You can probably do some tracert/traceroute type of checks to see where in the pathway there's a lack of knowledge for which direction to send things (or the wrong knowledge).

[Nathan]

Hi, I am going to start with the xxx.x7x. address of the first trio might be incorrect.

The entry trio radio is 192.178.... and the repeater radio and radio A is 192.168... and you dont have the correct subnet to allow communications between these two addresses.

This also goes for the repeater and radio A of having different subnets and a subnet mask not allowing different subnet communications. I would set all gateways to the same being the internet router/server.

As long as the trios are on the same subnet they don't require the data being transmitted to be on the same subnet. As long as they can see each other they will transmit and receive data packets and act as a switch so don't care about the source/destination IP addresses. 

IE: the three radios have to be on the same subnet with a mask of 255.255.255.0. But the SCADAPack ethernet can be on a different subnet as long as it matches the SCADAServer can access it which must be 192.168.43.x due to the subnet mask of the SCADAPack474 being 255.255.255.0

Is the repeater radio set up as a single or dual antenna. Can be a single with omni directional antenna but I have usually used yagi directional antennas from each port.

Also have had issues with transmission speeds and too many errors when set too fast. The repeater will also require slower speeds due to the way they work. 

I'm not sure on your WAN addressing as mine I have just set the Default Gateway internet gateway device IP.

I have a complex setup I did 10 years ago and haven't returned to change anything. We don't remote manage the radios or upgrade the firmware. Set and forget has worked fine here.

Access Trio then has 4 repeaters with ethernet connectivity at repeaters 1 and 2 and 3 + 4 are for straight repeaters for the last radio device. Using SCADAPack 535 and Moxa modbus.

Sorry if I jumped around a bit as I did go back and amend some areas.

Hope this helps,

Nathan

[RianL]

Thank you for your reply. The remote site and repeater communicate well with Remote Radio A connected to the SCADAPack serial port 4 and Radio B and its remote network communicate well via both serial and ethernet connections to the SCADApack. It's only when I try to connect Remote Radio A to ETH1 that communications quit working. I'm not trying to link Remote Radio A to Radio B, just send back the Modbus data on the SCADApack over ETH1. Would this be an application for a Modbus Store and Forward route? I am mostly confused as to why the communication between the SCADApack and Radio A works well over serial but not over ethernet when ETH 1 and Radio A are on the same subnet.

[BevanWeiss]

Provide a screenshot of your test that shows that it's "not working", as per "I can't seem to get our SCADAPack 474 to communicate with a Trio QR radio network via the ETH1 port."

You can Telnet / SSH into the SCADAPack, at which point you should be able to use ping to test the IP connectivity.  Ditto for the radios.
So.
1. Show us a ping from the SCADAPack that doesn't work.

2. Show us a ping from the Trio radio on that SCADAPacks ETH1 port that does work (since you've said the issue is with the SCADAPack ETH1...)