Phoenix AXC F 1152 as OPC UA Server
Hi,
currently, I am working on a project where I want to connect a Phoenix AXC F 1152 (OPC UA Server) to Siemens Tia WinCC Professional (OPC UA Client).
I didn't manage to get this working yet but I did manage to get UaExpert (another OPC UA Client working with the Phoenix Server).
I think that my OPC UA Certificates are not placed correctly or is it possible that I should use the GSD-File from the Phoenix AXC F 1152 PLCNext controller in Siemens Tia portal?
Could someone please help me with this problem.
Thanks in advance!
Kind regards,
Joost Merks
currently, I am working on a project where I want to connect a Phoenix AXC F 1152 (OPC UA Server) to Siemens Tia WinCC Professional (OPC UA Client).
I didn't manage to get this working yet but I did manage to get UaExpert (another OPC UA Client working with the Phoenix Server).
I think that my OPC UA Certificates are not placed correctly or is it possible that I should use the GSD-File from the Phoenix AXC F 1152 PLCNext controller in Siemens Tia portal?
Could someone please help me with this problem.
Thanks in advance!
Kind regards,
Joost Merks
Comments
this sounds familiar for me.
Another user of the forum reported a similar issue a few month ago OPC UA with Siemens 1522.
It seems that the UA Client have some problems using the self-signed certificates, unfurtonatly we've received newer a feedback.
We know also that some Clients have some problems with some additional security checks.
Please try to disable the following options.
As another option (but more or less only for testing) would be to deactivate the user authentification.
BR,
Frank
I have an update for the OPC_UA communication between Siemens PLCs (Client) and Phoenix AXC F 2152 / 3152.
There have been some issues when running FW 2021.6 on the AXC devices. It was not possible to establish a OPC_UA communication between the two systems - even with the changes Frank has posted here. The FW 2021.0 did work before.
At the moment I'm running tests on the FW 2021.9 to see if the issues have been resolved.
For the Siemens controllers it is important to use the latest FW here too. There have been some issues here as well. WinCC pro uses the same connection parameters as the controllers so please update the runtime here too.
Since I'm using normally Visu+ as SCADA application, I use a Phoenix Contact controller to handle the communication between sub systems. This means I keep my session count in the OPC_UA server to a minimum. Something you need to keep an eye on. Not all SCADA applications permit multiple controller connections. And it is not always clear what the max number is.
I will run a test with the WinCC pro v16.1 and v17 in the coming week and give you my feedback.
Currently I have an application where I need to collect data from multiple controllers from different suppliers. As a cheap and easy way I will use an EPC 1522 as a kind of hub to handle the communication between controllers. The EPC1522 will then be gateway to the SCADA application - in my case Visu+. But I will run a WinCC pro application parallel to Visu+ for testing. Will not be much work, since I always build dual applications - Frank, I did learn my lessons from the past!
You will find an update here in the middle of the coming week.
Peter Paul
thank you for sharing your experience with us here.
This is much appreciated!
Frank
Thanks for your reply, it's is really helpful!
I am also using the FW 2021.0. so that should not be the problem. At the client side I am using Siemens WinCC Professional V16 Update 4 so I am looking forward to your findings!
The amount of connections won't cause me a problem yet, but it's a good tip for the future.
Thanks a lot for sharing your experience!
Kind regards,
Joost Merks.
Info about my project:
This is the project that I am trying to get working, but I am not sure anymore if this is possible with OPC UA. So now I'm looking at other solutions as well.
as it seems you're dealing with a different problem than Peter has described.
Let's go back a step and see if the client does at least connect and authenticate to the server.
By checking the Output.log you can see if a client succeeded or failed the connection.
Here a positive and a negative example:
Positive authentification:
Arp.Services.OpcUAServer.Internal.Security.UserAuthenticationCallback INFO - Successful authentication for name='admin': client.address=192.168.2.100:55104, securityToken=F96B8C27, initialTimeoutMillis=1200000
Negative authentification:
05.11.21 13:01:13.701 Arp.Services.OpcUAServer.Internal.Security.UserAuthenticationCallback WARN - Failed authentication: client.address=192.168.2.100:55163, ua.status='BadUserAccessDenied', um.error=InvalidCredentials, um.penaltyDelayMillis=0, um.initialTimeOutMillis=1200000
In case of an invalid authentification you might have run in the situation that the user were blocked for security reasons.
Please find more details on that here.
To just exclude this as a cause you could just disable the user authentification on the PLC.
If all this does not give any clue, or if it seems that the certificate is not accepted, I would expect somekind of a warning or error in the UA Client log.
Is there anything available, or did you've contacted the Siemens support?
BR,
Frank