4/26/2023 3:52 PM | |
Joined: 4/20/2023 Last visit: 9/25/2023 Posts: 3 Rating:
|
Hello, I am trying to connect to a Beckhoff OPC UA Server using an S7-1500 OPC UA Client. I am using the sample PLC program with the S7 user block for OPC UA Client (S7 user block for the OPC UA client of a SIMATIC S7-1500 - ID: 109762770 - Industry Support Siemens). I can browse the PLC tags on the Beckhoff OPC UA Server from my TIA Portal project but when I enable the opcUaConnect bit on the opcUaClient block the outputs opcUaBusy and opcUaError bits are TRUE, the opcUaStatus = 16#8601 and opcUaDiagnostics subfunctionStatus = 16#800A_0000. The Beckhoff OPC UA Server and TIA Portal project are on the same Windows 10 VM. I can connect successfully to the Beckhoff OPC UA Server using the UaExpert Client software and read the status of the PLC tags, but I cannot connect successfully using the S7-1500 OPC UA Client. OPCUA Server: Beckhoff TwinCAT OPCUA Server running on Windows 10 VM (PC Name: DESKTOP_96BENPL, IP Address: 192.168.16.61) OPCUA Client: S7 1517F-3 PN/DP PLC, Firmware V2.8 (V2.9 online) (IP Address: 192.168.16.60) Using TIA Portal V16 sample PLC Program. I have attached a PDF doc with screenshots. Any assistance is much appreciated. Regards Danny AttachmentOPCUA_Errors.pdf (242 Downloads) |
Last edited by: Jen_Moderator at: 04/27/2023 11:45:20Text formatting optimized. Link optimized. |
|
5/4/2023 10:33 AM | |
Joined: 8/3/2009 Last visit: 6/27/2024 Posts: 13163 Rating:
|
Hello AutoGen_6354894 Check also this FAQ: https://support.industry.siemens.com/cs/ww/en/view/109766709 Bye Murof |
If this Information really helps, you could use the Rate function |
|
This contribution was helpful to
1 thankful Users |
5/19/2023 2:08 PM | |
Joined: 4/20/2023 Last visit: 9/25/2023 Posts: 3 Rating:
|
Hello, Managed to get this working with the help of Siemens and Beckhoff tech support. Had to use V17 of TIA Portal and upgrade PLC Firmware to V3.0. The issue seemed to be that the S7-1517 PLC was trying to connect to the Beckhoff OPC UA Server using its IP address, but the OPC UA Server was responding using its Fully Qualified Domain Name. I had to edit the OPC UA Server certificate to include the IP Address and also had to add it to the ServerUri field in the Client Interface Configuration DB in TIA Portal. Danny AttachmentOPCUA-SERVER.pdf (447 Downloads) |
Last edited by: AutoGen_6354894 at: 05/19/2023 14:09:45 |
|
This contribution was helpful to
2 thankful Users |
Follow us on