Problem with s7-1500 and NAT

Industrial
1

Hello all,

Been working on setting up a large network of s7 machines, and then using NR to retrieve some signals, turn those signals into count and then sending periodically to maintain x.

Most of my stufff is working as intended, but I have run into a problem while using a NAT device on one of our machines.

It is a s7-1500, and I’ve used the NAT to translate from 192.168.1.10 on the lan to 192.168.11.10 on the wan port.

I am using node-red-contrib-s7 and I’ve basically opened all the ports in the nat, and tried multiple devices and yet to achieve sustainable functionality. There’s been a few instances where I’ve gotten it to work for a period of time, but if I restart either NR or the machine it won’t reconnect without physically disconnecting adapters and reconnecting.

Just wondering if anyone else has run into issues with this or can propose a solution.

Have a handful of machines which will require a NAT device, I purchased this one Wall IE by system Helmholz because in years past we had good luck with their devices but at the moment struggling.

I am able to connect to the PLC through the NAT device using my programming software, so not sure what the obstacle is for NR

Thanks in advance

2

Think I got it sorted now. Networking noob challenges I think. See how it does after a few days and report back.

1 Like
3

System has been working fine since last report.

I think the root of my problem was not understanding subnet masks. I altered my approach and everything all of a sudden worked.

I thought if I changed my subnet mask to 16 from 24 it would allow me to reach all devices in the 192.168.###.### range, and although it worked a handful of times. If I broke the link say by restarting the rpi that was running NR it would not establish without doing a bunch of physical disconnecting of devices.

solution was to assign multiple static IP addresses each with a 24 mask from my NR device.

4

192.168 addresses are in the class C range so are expected to only have a 24 size subnet. So devices would default to that and not route beyond it by default. Eg see IPv4 Addresses Classes Explained: A Comprehensive Guide to Class A, B, C, D and E

1 Like