Warning: Revision does not match!

image.pngHello.
The installed firmware on the controller is 2022.0.4 LTS. This should work with PLCnext Engineer 2021.9 but when I try to get the controller online the PLCnext Engineer doesn’t seem to detect the controller revision.

What can I do? I have tried the same settings many times and a few times the Engineer detected the correct revision and got online but now I have the same problem.

Toggle flashing on the same page shows that the controller is connected to PLCnext Engineer.

Thank you.

The problem started after I changed the controller IP in a new location to match the Internet connection’s Default Gateway subnet. I got it to work suddenly after the same problems. Now I am at the original location and changing the IP addresses caused this same problem. The detection of the controller revision seems to be totally random. I might have pushed these buttons below in a correct order and set the same settings again. But now nothing seems to work.
image.png

Now the controller and Project Settings pages went completely blank. This has not happened before.
image.png

But these original settings finally worked with a new project. I think I tried these earlier and the controller revision was not detected.
image.png

If I use this exact IP address for the controller with a new project the revision on the controller is detected. Does this mean I should not change the IP address of the controller at all or what is the cause of the issue?
image.png

The problems start if I change the controller’s IP address to 10.67.8.2.
image.png

And when I change the settings back nothing happens. I have to start I new project to establish the connection again.

The Internet connection (10.67.8.1) has one Ethernet cable and the controller Ethernet cable goes to a second Ethernet port in the PC. This is probably the reason I can’t get these settings to work? I also can’t change the Internet connection’s IP address. I tried to have them in the same subnet so that Proficloud.io connection would work. It does work with a 4G router at least.

So this looks like it could be a problem with the overall network configuration.
Can you please give a description or diagram of:

                                          * Every device on the network.
                                          * Every Ethernet adapter on every device (both wired and wireless), with the IP address of that adapter.
                                          * The physical connections (wired or wireless) between every Ethernet adapter on the network.

This is a know problem with NPCAP driver that I have seen many times. you can un-install the NPCAP driver from the network adaptor and re-install the service again. That has solved my issues before in 98% of the cases.
This is especially the problem when you have some Siemens software on the PC as well. The versions for the Siemens software (TIA) and PLCNext Engineer are not the same and can generated this issue.

Peter Paul

Hello,
is there any update on this. I am using PLC Next Engineer 2024 and I have the latest version of npcap driver installed. Is there anything I can do to fix this problem.
I have multiple PLC Next devices on the network, they are all visible and from some of them the PLC Next Engineer can read the revision on from some devices can’t.

This is the crucial problem because the PLC Next Engineer is unusable and I can’t reach my devices with it.

Hello,</p>is there any update on this. I am using PLC Next Engineer 2024 and I have the latest version of npcap driver installed. Is there anything I can do to fix this problem. </p>I have multiple PLC Next devices on the network, they are all visible and from some of them the PLC Next Engineer can read the revision on from some devices can’t.</p>This is the crucial problem because the PLC Next Engineer is unusable and I can’t reach my devices with it.</p>

Afaik the latest npcap driver is 1.79?
Did you try using the npcap that’s delivered with the setup (1.78) of PLCnext Engineer?

Hello,
shutting down the CODESYS Gateway service resolved the problem.