There is no communication between the controller and the panel. OPC UA.

dmitry_izmodenov

Hello!
I followed the steps:
1. Made the settings for OPC UA on the controller;
2. Created a new project in the VISU 2.54 environment;
3. Launched the VISU project in RUNTIME mode (clicked Start Project);
4. In RUNTIME mode, the project is running, there is communication with the controller;
5. Uploaded the project to the panel;
6. The panel is working;
7. There is no communication between the controller and the panel.

What is the problem?

Starter kit provided by Phoenix Contact:
- controller: AXC F 2152;
- panel: TP3120W / P.

Martin - PLCnext Technology Team

In order to isolate the problem - are you able to successfully connect and exchange data with the OPC UA server in the PLC using a different OPC UA client, e.g. UaExpert from Unified Automation?

dmitry_izmodenov

Yes.Another client can connect.

Martin - PLCnext Technology Team

OK, thanks. I have passed this question to the Visu+ support team and I'll post their answer here.

Martin - PLCnext Technology Team

For PLCnext Engineer 2021.0 or greater, please check that the OPC UA Security settings are as follows:



... than save changes, send the project to the controller, and then restart the controller before testing again with Visu+.


.

dmitry_izmodenov

I checked the parameters. The controller was rebooting. The situation is not changing.

Martin - PLCnext Technology Team

Since this issue is probably related to Visu+, and not the PLC, do you mind if I ask someone from the Visu+ support team to contact you using the email you used to register for this forum?

dmitry_izmodenov

I don't mind. thanks

alitera

Since this issue is probably related to Visu+, and not the PLC, do you mind if I ask someone from the Visu+ support team to contact you using the email you used to register for this forum?

Sorry, I need to correct this.
This is not related to VISU+. The Plcnext Firmware was changed the OPC UA Namespaces Name Index. This is the reason that VISU+ is confused.

Please check that you are using the correct template in PLCnext Engineer.
You need to have 2021.0,x.
Then check also this document, which you can find on the Phoenix Contact Homepage

https://www.phoenixcontact.com/online/portal/us/?uri=pxc-oc-itemdetail:pid=2988544&library=usen&pcck=P-19-08-01&tab=1&selectedCategory=ALL

Article 2988544 --> Download Areas --> Application Node --> VISU+ OPC UA IMPORT Instructions on how to import OPC UA variables from PLCnext Engineer into Visu+ and Visu+ Express
--> ah_en_visu_opc_ua_import_109303_en_02.pdf

Please create for your test a complete new VISU+ 2.54 project with OPC UA client.

If this is not helping, then contact Support (OpMon Group). We will contact you fast as possible.

Thanks and good luck.

Alex L.

Martin - PLCnext Technology Team

And I need to correct this statement:

This is not related to VISU+.

This is true:

The Plcnext Firmware was changed the OPC UA Namespaces Name Index.

... however, as discussed in another thread, an OPC UA server is allowed to change the namespace index. If an OPC UA Client like Visu+ does not handle this correctly, then there is nothing that can be done in the OPC UA server to fix this. Here is the relevant section of the article from Unified Automation that is referenced in that other discussion:

In OPC UA service calls the namespace index is used instead of the longer namespace URI in NodeIds. The Client needs to take care of the correct mapping from namespace URI to namespace index. Servers are not allowed to change the namespace index for a specific namespace URI or delete entries from the namespace table as long as an active session exist, so that clients can cache the namespace table for a specific session. But a Server may change namespace indexes and remove entries from the namespace table if no Client is connected or if the server is restarted. For this reason, a Client should not persist the namespace index without storing the namespace URI as well, because a namespace URI represented by index “2” during one session could be represented by index “5” during the next session. Thus, when having established a session with a Server, a Client should always read the Server’s namespace table and update namespace indexes before calling services in which NodeIds are involved.

This issue - which might not even be related to the OPC UA namespace index - is currently being handled directly with Dmitry by the OpMon support group (ref: #220449).


.

alitera

Maybe. Fact is, that Visu+ worked over years without any issues regarding the OPC UA connection. Well, after a lot of PLCnext Firmware Updates Visu+ was not able to follow all this changes.
And by the way. With Version 2.54 Visu+ can also work with changed Namespace Index
The best way is to ready the enclosed document.
We have a lot of customers with OPC UA and TP3000 and TP6000. I would expect, that we should get this running.
Best regards
Alex L.

Frank Phoenix Contact Deutschland Support

This issue is now handled inside a support ticket.

Martin - PLCnext Technology Team

For others with a similar issue:
In this case the problem appears to have been due to an old firmware version on the display panel.
(ref: #220449)