• Replies 2 replies
  • Subscribers 586 subscribers
  • Views 206 views
  • Users 0 members are here
Options
Related

Troubleshoot OPC Unit offline

Jonathan Bellavance

Hi,

When I start my SCADA application I obtained an error for every OPC device in project in the IO server syslog.

Error: Unit offline   UINIT    000c     PORT_OPC  V2918_OPC_A                 Error_in_CMD-3   16   Generic 000012 Driver 00000259 (0x00000103)

I can't find any interesting documentation. Maybe you can point me where to look for documentation on the error code or provide me with a solution.

So far I found in the driver reference help that this error should probably reference to this:

But I don't have the knowledged nor the documentation to help me with a solution for this.

Running on Aveva Plant SCADA 2020 (8.3) in process of updating to R2 soon. It's full developper licensed running server and client on same pc.

Using Matrikon Explorer I'm able to see all my data.

Thanks.

Parents

  • When searching for opc error 259 (0x0103) on the Internet I get "Failed to connect to server".

    I would start looking at the Address field of the I/O device. Provide a valid OPC server ProgID, most often in the form of "Vendor.Application" (for example: Citect's ProgID is "Citect.OPC".

    You might also want to look into the protocol version that your device supports. The OPC driver defaults to OPC v1.0a. If your device supports OPC v2 then you might want to set Citect.ini parameter [OPC]UseOPC2=1, or specifically for one I/O device, using [OPC]<your I/O Server name>.<your I/O device name>.UseOPC2=1

    Furthermore, you can enable debugging (logging) by setting Citect.ini parameters [OPC]DebugLevel=ERROR and [OPC]DebugCategory=ALL

Reply

  • When searching for opc error 259 (0x0103) on the Internet I get "Failed to connect to server".

    I would start looking at the Address field of the I/O device. Provide a valid OPC server ProgID, most often in the form of "Vendor.Application" (for example: Citect's ProgID is "Citect.OPC".

    You might also want to look into the protocol version that your device supports. The OPC driver defaults to OPC v1.0a. If your device supports OPC v2 then you might want to set Citect.ini parameter [OPC]UseOPC2=1, or specifically for one I/O device, using [OPC]<your I/O Server name>.<your I/O device name>.UseOPC2=1

    Furthermore, you can enable debugging (logging) by setting Citect.ini parameters [OPC]DebugLevel=ERROR and [OPC]DebugCategory=ALL

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