I am using 3.16 to connect to an RSLinx OPC Server running on a remote machine. Two things appear to happen, Configuration Panel indicates connected, browsing via Items shows all available topics, but clicking into the tree does not show any tags, it just repeats Offline/Online.
The log shows the following:
WCCOAopc (1), 2019.05.06 10:33:31.260, IMPL, WARNING, 54, Unexpected state, OPCServer, initialize, No connection monitoring via callback for RSLinx OPC Server
WCCOAopc (1), 2019.05.06 10:33:31.260, SYS, INFO, 0, , OPCServer, workproc, Reconnected to server RSLinxOPCServer
WCCOAopc (1), 2019.05.06 10:33:31.260, SYS, INFO, 0, , OPC DA Server (RSLinxOPCServer): Startup complete!
WCCOAopc1:Could not connect shutdown interface!: [RSLinx OPC Server]: COM Invalid argument has been passed to a function. (0x80070057)
The config file is:
[opc]
server = "RSLinxOPCServer" "192.168.168.115/RSLinx OPC Server"
RSLinx OPC Server Connection
- chood
- Posts:4
- Joined: Fri Oct 13, 2017 7:02 pm
RSLinx OPC Server Connection
- Attachments
-
- oa_opc.PNG (1.86 KiB) Viewed 2359 times
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: RSLinx OPC Server Connection
In your configuration DCOM is used for the communication between the OPC client and the OPC server.
If possible the usage of DCOM shall be avoided.
The error code 0x80070057 given in the log message is an error code returned by the OPC server and/or the operating system. This error is not generated by WinCC OA.
If an error is received from the OPC server the WinCC OA OPC client writes the error code to the log message.
To avoid using DCOM you can choose 2 options:
-- Install the OPC server at the machine where WinCC OA is running
-- Start a remote WinCC OA OPC client on the machine where the OPC server is running
Can you use one of these options?
Best Regards
Leopold Knipp
Senior Support Specialist
If possible the usage of DCOM shall be avoided.
The error code 0x80070057 given in the log message is an error code returned by the OPC server and/or the operating system. This error is not generated by WinCC OA.
If an error is received from the OPC server the WinCC OA OPC client writes the error code to the log message.
To avoid using DCOM you can choose 2 options:
-- Install the OPC server at the machine where WinCC OA is running
-- Start a remote WinCC OA OPC client on the machine where the OPC server is running
Can you use one of these options?
Best Regards
Leopold Knipp
Senior Support Specialist