Hello everyone,
I’m facing some technical issues related to my PLC project and Node.js installation. I’d appreciate any insights or suggestions to help me resolve these.
1st Problem: PLC Connectivity Issue
When I ping my PLC at 192.168.1.10, the response is inconsistent. Sometimes it works, but other times I get:
* _Host Unreachable_
* _Request Timed Out_
* **2nd Problem: PLC Synchronization and Revision Mismatch(PLCnext engineer)**
I can’t synchronize the online project on my PLC with my offline project. It throws a revision mismatch error.(I want to fetch the project from the PLC itself to import locally on my machine)
* 3rd Problem: Node.js Installation Issue
Despite installing Node.js multiple times, I get the following error when trying to use it:
* node: command not found
Troubleshooting Attempts :
Installed Node.js via the official installer.
* Verified the installation path and added it to my system’s PATH variable.
* Checked node -v in the terminal, but the command doesn’t work.
1st Problem: PLC Connectivity Issue
This is most likely related to the network setup, rather than anything related to the PLCnext Control device.
2nd Problem: PLC Synchronization and Revision Mismatch(PLCnext engineer)
Are the project sources stored on the PLCnext Control device? If so, what happens when you try this procedure?
Reading Project Sources from the Controller ');\n mywindow.document.close(); \n mywindow.focus();\n setTimeout(function () {\n mywindow.print();\n mywindow.close();\n }, 1000)\n return true;\n}\r\n\r\n\r\n 3rd Problem: Node.js Installation Issue
What commands are you using to install Node.js on the PLCnext Control device?
Verified the installation path and added it to my system’s PATH variable.What model of PLCnext Control device are you using, e.g. AXC F 2152, AXC F 3152?
If it’s an AXC F 3152, then the problem might be similar to this one:
Forum - PLCnext Community PLCnext Technology from Phoenix Contact is a unique, open ecosystem for modern automation that is capable of meeting all the challenges of the IoT world.
First, I’d like to thank you for your help and insights so far.
I am currently working with a PLC Next (AXC F 2152, 2019) and am facing several issues. My goal is to fetch the project from the PLC to download it to my local laptop. However, each time I try to synchronize or connect via PLC Next Engineer (Cockpit), it gives me a „connection failed“ error.
Interestingly, I can ping the PLC, and the ping works fine. However, the old HMI that was set up also shows „connection failed.“
I’m thinking that I might need to reset the PLC, but I wanted to check here first to see if there’s anything I might be overlooking or other steps I can try before going that route.
Thanks again for your time and advice!
It sounds like the PLCnext Runtime may not be running on the device - that’s the process that loads and executes both the PLCnext Engineer project, and the OPC UA Server (which I’m guessing your old HMI might use to connect to the controller).
To check if the PLCnext Runtime is running, you can open an ssh session on the device (which should be possible if you can ping it) and check the contents of the Output.log file. The most recent entries in that file should give a clue if the Runtime is running and, if not, what is causing a problem. If you need help interpreting that file, you can send it to your local Phoenix Contact office, where the technical experts there can look at it.
As you mentioned, a type 1 reset will probably solve the problem, although that will delete the PLCnext Engineer project from the device and so will scupper any chance of retrieving that project.
If the PLCnext Engineer project was not sent to the controller „with sources“, then unfortunately you will have no chance of recovering the project to your laptop. The PLCnext Engineer project itself is compiled before being sent to the device, and it cannot be reverse-compiled into source code.
Thanks for the reply! I’ve tried multiple solutions and fixed a few bugs, but I’m still running into this error in the output.log file. I would greatly appreciate any insights you may have on the possible root cause:
09.02.25 10:13:20.540 Arp.System.Acf.Internal.Sm.ComponentsController ERROR - Exception occurs while setting up config of component ‚Arp.Plc.Eclr‘: Could not load eCLR image file: ‚/opt/plcnext/projects/PCWE/Plc/Eclr/eCLR.img‘
Exception of type ‚Arp::System::Commons::InvalidOperationException‘ was thrown
at: Arp::Plc::Eclr::EclrComponent::LoadPlc(bool)
at: Arp::Plc::Eclr::EclrComponent::LoadConfig()
at: Arp::System::Acf::Internal::Pm::ProcessManager::LoadComponentConfig(Arp::BasicString<char, std::allocator > const&)
at: Arp::System::Acf::Services::Internal::ProcessManagerServiceImpl::LoadComponentConfig(Arp::System::Rsc::Services::RscString<512> const&)
at: Arp::System::Acf::Internal::Sm::ComponentsController::SetupComponentConfig(Arp::System::Acf::Internal::Sm::Data::ComponentExecutionData&)
at: Arp::System::Acf::Internal::Sm::ComponentsController::SetupComponentsConfig()
at: Arp::System::Acf::Internal::Sm::SystemManager::SetupSystem()
at: Arp::System::Acf::Internal::ApplicationBase::SetupSystem()
at: Arp::System::Acf::Internal::MainApplicationBase::SetupInternal()
at: Arp::System::Acf::Internal::ApplicationBase::Setup(Arp::System::Commons::Diagnostics::Logging::LogLevel, char const*)
at: Arp::System::Acf::Internal::ApplicationBase::Main(int, char**, Arp::System::Commons::Diagnostics::Logging::LogLevel)
at: Arp.System.Application() [0x1a600]
It looks like there’s a problem with the PLCnext Engineer project.
Did you do a Type 1 reset on the device?
Can you connect to the device using PLCnext Engineer, and send a project to the device?
Apologies for the delayed response.
I have not performed a Type 1 reset yet, as I want to ensure that all possible solutions have been explored.
Please correct me if I’m mistaken—if I send a project to the PLCnext, will it overwrite the existing project on the device?.
I don’t have the original project on my laptop, but it is stored on the PLCnext. Every time I try to synchronize and fetch it from the PLC, it detects the project but fails to retrieve it. It keeps showing an error stating that my revision is incorrect, even though I’ve tried all available revisions, but it still doesn’t work.
Keep in mind the PLC next engineer version I use is the newest one, back then when the project was working in 2020 it was a different version. Will the different software version be the cause of the problem ? .
if I send a project to the PLCnext, will it overwrite the existing project on the device?Correct.
I don’t have the original project on my laptop, but it is stored on the PLCnext. Are you 100% sure that the current project on the device was sent with sources?
Will the different [PLCnext Engineer] software version be the cause of the problem ?No, but differences in the firmware version of the PLCnext Control device in the PLCnext Engineer project vs. the firmware version on the controller may cause problems. But again, this won’t matter if the project sources are not stored on the PLCnext Control device. If the sources are stored on the controller, then you don’t need PLCnext Engineer to retrieve them. You can use WinSCP (or another scp client) to copy the project sources from the directory /opt/plcnext/projects/PCWE/Src. If that directory is empty, or does not exist, then I’m afraid there’s nothing you can do to retrieve the source code from the device.
Thank you very much for all your responses—I truly appreciate them. Unfortunately, the src directory does not exist, so we will need to start a new project.
Will the different [PLCnext Engineer] software version be the cause of the problem ?No, but differences in the firmware version of the PLCnext Control device in the PLCnext Engineer project vs. the firmware version on the controller may cause problems. But again, this won’t matter if the project sources are not stored on the PLCnext Control device. If the sources are stored on the controller, then you don’t need PLCnext Engineer to retrieve them. You can use WinSCP (or another scp client) to copy the project sources from the directory