Hi, I have a problem with the new firmware version (2020.0.1) when I try to connect the PLCnext to the PLCnext Engineer. Project’s IP range is ok and the configured IP for the project is the same as the PLCnext. PLCnext Engineer and PLCnext both are in the same firmware version. I’ve just logged on the controller’s website, connect via ssh and received it’s ping. When I try to log in or to connect PLCnext, the software shows this message: “could not connect to the controller”. Also it shows a logging error: “connection failed, no response from the controller”. Francisco
Hi Francisco, It sounds like the PLCnext Runtime has not started. Without this process, PLCnext Engineer cannot connect to the PLC. Can you please check the contents of the Output.log file? (/opt/plcnext/logs/Output.log) This should give you some clues as to why the PLCnext Runtime has not started. ~ Martin. ======================= Edit: If you can see the controller’s web page, then perhaps the PLCnext runtime has started … in which case it may be a setting in PLCnext Engineer. Please let us know if you find anything in the log file.
I’ve been checking the Output.log file and I found some errors. This one called my attention: 07.04.20 15:02:01.664 Arp.Io.ProfinetStack.System.Internal.Adaption ERROR - Event Archive Entry, Module ID: 8b, Message: HW_ETH_SetAdapterInfo(): Could not change to the given gateway address! I’m attaching the Output.log file.
Hi Francisco, I will check the output log with my colleagues tomorrow. Can you tell me more about the network setup? Is there a Profinet controller somewhere else on the network that could be changing the IP address of this PLC? Or, are there other Profinet devices on the network? Any other information about the network that might be relevant? ~ Martin.
Hi Martin, First of all, thanks for your help. I have the controller at home to develop during the quarantine, I’m directly connected from the computer to the PLC. Francisco
Hi Martin, When I updated to FW 2020.0.1, I tried to change project’s controller from 2020.0.0 to 2020.0.1 . PLCnext Engineer 2020.0.1 did not have a 2020.0.1 firmware version controller, so I change th FW version of the controller back to the 2020.0.0 but even this way it did not connect. I tried using the other firmware versions both in the controller and in the software and the error persist. Using Netnames the IP address, subnet mask and default gateway may be modified without problem. I think the problem may be a PLCnex Engineer´s component that could be failing.
Can you tell me if I need to delete any file in my PC to make sure the software instalation will work correctly?
Hi Franciso, Here is the advice from the PLCnext Engineer support team:
* First, try to start PLCnext Engineer as Administrator. * If this does not work, please try deactivating the firewall and any antivirus programs.Please let us know if this makes any difference. ~ Martin.
moved to PLCnext Engineer category
