image.pngimage.pngimage.pngimage.pngimage.pngimage.pngimage.pngevery time i start and write the simulation the uarexpert goes into shutdown „error bad communication“ and the factory io does not recognize the device please help this are the errors i get.
In this earlier conversation:
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. … you were able to get a connection from UaExpert to the AXC F 1152 simulation.
What are the exact steps after that, that causes UaExpert to lose communications?
If it involves sending a new PLCnext Engineer project to the device (simulation), what changes were made to the PLCnext Engineer project?
Note that when PLCnext Engineer is shut down, the simulation also shuts down. Could that explain what you’re seeing?
I put all algorithms to no
Set the ip address on the server settings to 192.168.1.10
Pit visibility of variables to marked
As I start and write the project uaexpert goes unto error mode
The IP address doesn’t make a difference for the simulation.
Disabling all the security policies would explain the behaviour.
What is the reason for disabling all the security policies?
If the Factory IO client does not support any of the available security policies, then you will need to contact the vendors of Factory IO to get their recommendation for how to deal with OPC UA servers that require at least some type of security policy.
Iam currently running the Sofware without changing anything, as soon i start and write the project it goes into error bad certificate invalid
I can reproduce this behaviour using the following steps:
* Create a new PLCnext Engineer project for AXC F 1152 FW 2023.0
* Send the project to the device (simulation)
* Connect the UaExpert OPC UA Client. During the connection, accept the server certificate.
* Change something in the PLCnext Engineer project that causes the OPC UA server certificate to be regenerated. In my case, I changed the Endpoint name in the OPC UA Server settings.
* Send the project to the device (simulation).
This causes the OPC UA Server to restart and use the new server certificate. UaExpert disconnects from the Server when the server restarts, and UaExpert then attempts to reconnect to the server automatically. When it reconnects, it finds that the Server certificate that was accepted during the initial connection is no longer valid, so it refuses to connect.
The solution in this case is to manually disconnect and reconnect to the server in UaExpert, so that it will ask you to accept the Server certificate again. In a real-world application, the server certificate is unlikely to change very often, and if it does then it makes sense that OPC UA Clients should not accept the new certificate until it is confirmed to be the correct one.
This is not a problem with the OPC UA Server, it’s just the way this particular client behaves. If you have suggestions for how UaExpert could be improved in situations like this, please contact Unified Automation.