• State Verified Answer
  • Replies 2 replies
  • Subscribers 586 subscribers
  • Views 152 views
  • Users 0 members are here
Options
Related

Problem with OPCUA in Citect Scada 2018

Jaime Derecho

Hi all,

I have Citect Scada 2018 installed in a server with an OPCUA IO Device. It was working well but I had to reinstall all the server and the SCADA. Now I am facing a problem when I try to read the OPCUA device. When I see the IOServer Syslog I have the following message:

Error: Disconnected unit UINIT    000c     PORT_OPC       tcuopc                 Error_in_CMD-3   16   Generic 000012 Driver 00000023 (0x00000017)

I have installed the SCADA and OPCUA client driver. When I use the configurator to configure the OPCUA I can connect the server and with the Device Communication Wizard I can read the Tags. I have in the citect.ini the SecuritySettingsName configured with the configurator name. But when I open the SCADA all the tags apper as BAD or 0 and in the log appears the message I told before. From the same server I tried to connect with a comercial client and I can see all the values from the OPCUA server.

I have search in the manual but I had no solution with what is in it.

Could anyone help me?

Thank you in advance.

Parents
  • +1

     Hi  ,

    It looks like a connection related issue.

    You mentioned that you could browse tags with Device Communication Wizard. Did you use any security setting in Browse as shown in the screenshot below? The reason I am asking is that some of OPC UA servers can support both secure and unsecure connections. It could end up that Browse Session used the unsecure endpoint with Anonymous and Runtime used the security settings. 

    OPC UA Client Driver of Plant SCADA supports the following security policies

    • None
    • Basic256 and Basic128Rsa15
    • Basic256Sha256
    • Aes128Sha256RsaOaep
    • Aes256Sha256RsaPss

    Make sure that you select a correct one. You check if the OPC UA server has any logged message when the error occurred on the driver side. Below is from the Troubleshooting section in the driver help  (accessible from top-right corner in Configurator)

    If the connection cannot be established, the specific error will help to identify the cause of the problem.

    Points to consider include:

    • The user credentials are stored in ArchestraATm Data Store and the ArchestraATm Data Store service must be running on the machine for the plug-in to store the data and for the driver to read it. The ArchestraATm Data Store service should be installed and running after the driver installation.
    • When the user credentials are configured for the first time, the plug-in adds the currently logged-in user to the Citect.User.Drivers Windows group so that the I/O Server running under the same user account can read the data. When a user is added to that group for the first time, you will need either to restart the computer or to log in / log out.
    • The client and server certificates must be present in the Windows certificate store. The client certificate must have a private key and its "Subject Alternative Name" field should be in the format "urn:HostMachineName:Citect.OPCUA.Client.Driver", where the HostMachineName is the host name of the computer running the driver.

    You may also try the following driver settings and more info will be logged. Hopefully, some info could reveal the root cause.

    [OPCUA]
    DebugLevel=ALL
    DebugCategory=ALL

    Regards,

    Jacky

  • 0 in reply to Jacky Lang

    Hi Jacky,

    Thank you very much for your help. What you told me was very helpful. The security part was correct. But we didn't notice that the user that runs the SCADA wasn't on the Citect.User.Drivers.

    Once we added it, the SCADA started to show the data and now the problem is solved.

    Once again, thank you very much for your help.

    Best regards,

    Jaime

Reply Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.