Our distributor receive their Promoter demo and is trying to download a PLC project to ctrlX CORE, but they always get this message. The ctrlX WORKS and PLC app versions are the latest and match my demo which is working fine. I had him download to a virtual ctrlX CORE and this is wokring fine, it is only an issue wiht the demo unit. The actual device name and the name in the project are the same (icx-sn01234567) so I'm not sure why it says the name does not match. Maybe something to do with ctrlX-MOTION-Trial-033 that appears in the message. Any ideas how to resolve this?
Solved! Go to Solution.
"Encrypted communication not possible. Device name does not match the name of the certificate."
So you try to load an already used program to the new control?
Please try to start ctrlX PLC Engineering out of the web interface and import only the application part from your actual project.
This happens even when launching PLC Engineering from web browser, making a new default project etc. He isn't trying to load an older project.
I have the same thing occuring. I am opening from the web application. When the application is opened I am alerted that the application does not match the project settings. I have attached a video.
So it seems that the configuration running on your control was set up with another one.
The easiest way would to simply create a new configuration and set it to active but then all the data will be lost:
If you want to keep your data there are more steps to do:
1) Export PLC Application from the actual program if needed afterwards:
2) Download your configuration and delete the PLC part:
3) Create a new configuration upload the manipulated configuration and activated it (and perhaps reboot the control afterwards):
4) Create a new PLC program and import your exported code.
Now you should be able to normally login again.
I am currently using RM20.11(01V06).
The problem occurs even if I perform the same procedure as above.
Are there any other workarounds?
Please let me know.
Thank you in advance.
If the top ways do not work you could try to rename your controller via the web interface:
And if any name does not work please use the name in the error code: