[william]

Maybe I didn’t describe the problem clearly, I’ll rephrase the problem.

There are 2 DCS devices (OPC DA server) and 1 computer here. The Rapid Scada Admin runs on this computer. The OPC Core Components has also been installed. I use Rapid Scada Admin to connect to DCS and configure OPC. DCS A succeeded, while DCS B reported an error during the connection. The error message was mentioned earlier.
The OPC Core Components on the computer(OPC client) should be functioning properly as DCS A can be configured normally.

I have run another OPC client app on this computer, which can connect to DCS A and DCS B normally and read back data. This indicates that DCS is also working normally.

The OPC versions of DCS A and DCS B may not be the same, and I suspect it may still be a compatibility issue. This OPC client app uses a lower version of the API, which is compatible with DCS B. Rapid Scada uses a higher version of the API, so it is not compatible with DCS B.

[william]

Thanks for your reply.
Is the OPC Core Components installed on the OPC client or server?
The customer does not allow me to install anything on their DCS device (OPC server).
I am trying to read the source code. I would like to try replacing the unsupported functions (lOPCServerList2) with older versions. Is this the right way?

[william]

OPC Core Components has already been installed. Because I can connect and read back the data using other OPC Client tools.

[william]

Follow the solution 1 and 2 described in the article you provided.

[william]

It’s working! Thank you very much!

[william]

line000.log ：
——————————————————————————–
——————————————————————————–
2023-09-27 12:29:18 Start communication line [0] int0

2023-09-27 12:29:18 Connect to OPCServer.WinCC/{75d00bbb-dda5-11d1-b944-9e614d000000}
2023-09-27 12:29:19 Error connecting OPC server:
E_NETWORK_ERROR
Could not connect to server.

2023-09-27 12:29:19 Delay before connecting 4.4 sec
2023-09-27 12:29:23 Connect to OPCServer.WinCC/{75d00bbb-dda5-11d1-b944-9e614d000000}
2023-09-27 12:29:23 Error connecting OPC server:
E_NETWORK_ERROR
Could not connect to server.

*********************************************
device000.txt ：
[0] dcsda1
———-
Driver : DrvOpcClassic 6.0.0.0
Status : Error
Session time : Undefined
Command time : Undefined

Sessions (total / errors) : 0 / 0
Commands (total / errors) : 0 / 0
Requests (total / errors) : 0 / 0

Current Data
+—+——+——+——-+———+
| # | Code | Name | Value | Channel |
+—+——+——+——-+———+
| ************* opcda ************* |
+—+——+——+——-+———+
| 1 | a1 | a1 | — | |
+—+——+——+——-+———+

***********************************************
ScadaComm.log
——————————————————————————–
2023-09-27 12:29:15 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Communicator 6.1.1.1 started
2023-09-27 12:29:15 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Storage FileStorage 6.1.0.0 loaded from file C:\Program Files\SCADA\ScadaComm\FileStorage.dll
2023-09-27 12:29:15 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Start logic processing
2023-09-27 12:29:15 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Driver DrvDsScadaServer 6.0.1.1 loaded from file C:\Program Files\SCADA\ScadaComm\Drv\DrvDsScadaServer.Logic.dll
2023-09-27 12:29:15 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Driver DrvOpcClassic 6.0.0.0 loaded from file C:\Program Files\SCADA\ScadaComm\Drv\DrvOpcClassic.Logic.dll
2023-09-27 12:29:15 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Data source ScadaServer initialized successfully
2023-09-27 12:29:15 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Data source ScadaServer: Receive the configuration database
2023-09-27 12:29:18 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Data source ScadaServer: The configuration database has been received successfully
2023-09-27 12:29:18 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Start communication lines
2023-09-27 12:29:18 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Start reading commands from files
2023-09-27 12:29:20 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Data source ScadaServer: Connection state is Logged In
2023-09-27 12:35:09 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Stop communication lines
2023-09-27 12:35:14 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] All communication lines are stopped
2023-09-27 12:35:14 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Logic processing is stopped
2023-09-27 12:35:14 [DESKTOP-KJ7BBFJ][DESKTOP-KJ7BBFJ$][ACT] Communicator is stopped
——————————————————————————–

[william]

Setting username, password and domain does not work.
The Communicator still cannot read value. The error in the log is E_NETWORK_ERROR.
But connecting in the device properties page can be successful. Perhaps the device properties page like a desktop application and the Communicator is a service.
Are there any other configurations that I can try?

[william]

Thanks for your reply.
The OPC DA specification version is 2.0
The OPC server is a DCS device.
I will go to the factory and give it a try. I will report the results after trying.

[Author]

Posts