Msg_onl0166 -

Hello. I have seen this issue listed a few times on the forum but none of the answers are pointing me into the right direction, so I apologize for the repeat.
I was able to connect to the PLC with a direct ethernet, but now that it is on my network I am having issues. I am able to ping the PLC from my PC. My PC is at IP address 192.168.50.102
I do not have the correct Rev available in PLCnext Engineer, the PLC firmware is 2024.6.0 and only 2024.0.0 is available
Question 1: How can I update what firmware is available?
If I am able to ping the PLC, why can I not access it via PLCnext Engineer. As I said I was able, with the difference of firmware files, connect with a direct ethernet cable connection and using the default IP addresses of 192.168.1.10.
Any direction would be helfpul.

image.pngimage.pngimage.pngimage.pngimage.pngimage.png

Which version of PLCnext Engineer are you using ?

Hi JDPC_Engineer,
the answer to question 1 is: use a PLCnext Engineer 2024.6 and you’ll get the templates for 2024.6 PLCs.
But that does not matter in your case because (as you noticed already) it is entirely possible to have an older PLC template in your project and connect to a PLC having a newer firmware version.
The first thing I would do is to make sure it’s actually the PLC that answers your ping and not some other device with the same IP address. Maybe you can check your ARP table or scan the network via PLCnext Engineer.

Best Regards
DivisionByZero

Hi JDPC_Engineer,</p>the answer to question 1 is: use a PLCnext Engineer 2024.6 and you’ll get the templates for 2024.6 PLCs.</p>But that does not matter in your case because (as you noticed already) it is entirely possible to have an older PLC template in your project and connect to a PLC having a newer firmware version. </p>The first thing I would do is to make sure it’s actually the PLC that answers your ping and not some other device with the same IP address. Maybe you can check your ARP table or scan the network via PLCnext Engineer.</p>Best Regards</p>DivisionByZero</p>

Hello DivisionByZero,
Thank you for your response. I can confirm that I am able to ping the PLC and that there is not anything else on the network with the same IP address. I know this by two reasons, I am able to reach the HTTP config screen of the PLC from the IP address and when the PLC is unplugged from the network the ping returns back as unreachable.
I had assumed, and thank you for confirming, that a newer PLC would update with an older firmware on the PLCnext Engineer software.
I am going to go back to a direct connection and see if I can get that work again.
Please if you have any other suggestions, send them my way.

Can you check the Online-Protocol tab in the MESSAGES window? What exactly is the error message?

[https://forum.plcnext-community.net/discussion/comment/13742#Comment_13742</a></p>Hello DivisionByZero,</p>Thank you for your response. I can confirm that I am able to ping the PLC and that there is not anything else on the network with the same IP address. I know this by two reasons, I am able to reach the HTTP config screen of the PLC from the IP address and when the PLC is unplugged from the network the ping returns back as unreachable.</p>I had assumed, and thank you for confirming, that a newer PLC would update with an older firmware on the PLCnext Engineer software.</p>I am going to go back to a direct connection and see if I can get that work again. </p>Please if you have any other suggestions, send them my way.</p>

I have connected the PLC directly to my PC, and set back to the factory IP address. I have also updated the PC network IP address. I can ping the PLC and open the HTTPS page on the PLC. I get the ONL0166 error and an additional error, ONL0185 Profinet Stack error.

Which System Services are enabled/disabled, according to this WBM page on your device?

image.png

Can you provide a screenshot of the error messages. I haven’t memorized what they say :wink: