Controller: AXC F 2152, FW 2020.0 LTS (20.0.0.24752): I’ve configured a static IP address: 10.2.3.213 / 255.255.255.0 / 10.2.3.1 but couldn’t reach PROFICLOUD or any other external IP address. I logged on to the controller via ssh to check the /etc/network/interfaces file. The device address and mask were correct but the gateway address said 0.0.0.0 and had obviously not been transferred from PLCNext to the controller. After I corrected the interfaces file manually and restarted the system everything worked as expected. Funny thing? Regards, Wolfram
Hi Wolfram, I create several new PLCnext Engineer v 2020.0 projects every week, all with a non-default Gateway address, and I have never had this problem, but that’s not to say that it’s not possible. Can you please confirm that this is reproducible behaviour, if so then I will pass this to the PLCnext Engineer team, and they will let you know what additional information they need from you to investigate further. ~ Martin.
Yes, it seems to be a reproducible behaviour. I just configured a new gateway address like this address 10.2.3.213 subnetmask 255.255.255.0 gateway 10.2.3.2 and uploaded it to the controller. Logged on with SSH and using ip r I’ve got this: root@axcf2152:/opt/plcnext/# ip r
default via 10.2.3.1 dev eth0
10.2.3.0/24 dev eth0 scope link src 10.2.3.213 root@axcf2152:/opt/plcnext/# The gateway address did not change from 10.2.3.1 to 10.2.3.2. Where am I wrong? Regards, Wolfram
Hi Wolfram, OK, I have reproduced what you are seeing, and this was my misunderstanding. Using PLCnext Engineer, it is only possible to change the IP parameters of the PLC using the Project → Online Devices window: This is way I have been setting the Default Gateway in my projects, so I misunderstood the problem (sorry!). It is not currently possible to change the default gateway by downloading a new PLCnext Engineer project to the PLC. From PLCnext Engineer, this can only be done from the Online Devices window. ~ Martin.