TheWaterboy
Lifetime Supporting Member + Moderator
While I'm waiting for the IT dept to wake up and examine the FW logs...
I have a MSG configured to read an N12 register from a PLC5 over a cell modem. This is the first of this particular combination of controllers and I figured it would be problematic, just not like this. The MSG errors with error 16#0001 extended error code 16#0000_0204. Connection Failure
I can also use Logix 5 from my desktop through the cell modem with no issue.
I can't see it's webpage, but even though this PLC is Series E rev J there is no dialog to enable the webpage. I think this might have had a firmware update many years ago and might not be capable of a web page. So its suspicious but may not be related.
My desktop and the Polling PLC are on different vlans so its possible that the FW is blocking MSG protocol on the controller vlan but not on my desktops vlan so when IT wakes up that's my question but until then I need to gather info. However . . .
Using RSlinx over the cell modem I can use data monitor and see all the registers in real time and I can ping the device at will with a 300 to 400 ms return time from both Vlans
So that brings the question: Is there anything different about a MSG instruction and using RSLinx Data Monitor that the Firewall might be blocking? Wouldn't Data monitor use port 2222 as well as the MSG?
I have a MSG configured to read an N12 register from a PLC5 over a cell modem. This is the first of this particular combination of controllers and I figured it would be problematic, just not like this. The MSG errors with error 16#0001 extended error code 16#0000_0204. Connection Failure
I can also use Logix 5 from my desktop through the cell modem with no issue.
I can't see it's webpage, but even though this PLC is Series E rev J there is no dialog to enable the webpage. I think this might have had a firmware update many years ago and might not be capable of a web page. So its suspicious but may not be related.
My desktop and the Polling PLC are on different vlans so its possible that the FW is blocking MSG protocol on the controller vlan but not on my desktops vlan so when IT wakes up that's my question but until then I need to gather info. However . . .
Using RSlinx over the cell modem I can use data monitor and see all the registers in real time and I can ping the device at will with a 300 to 400 ms return time from both Vlans
So that brings the question: Is there anything different about a MSG instruction and using RSLinx Data Monitor that the Firewall might be blocking? Wouldn't Data monitor use port 2222 as well as the MSG?