Forum Home › Forums › Understanding the Software › SCADA Client API Command not Working
Tagged: SCADA Client API
- This topic has 18 replies, 2 voices, and was last updated 6 hours, 7 minutes ago by
Mikhail.
-
AuthorPosts
-
August 5, 2026 at 1:33 pm #18241
prabhu.natarajan.n@gmail.com
ParticipantNot Update
2026-08-05 18:51:32 [ENGINEERING][ENGINEERING$][ACT] Communicator 6.2.1.0 started
2026-08-05 18:51:32 [ENGINEERING][ENGINEERING$][ACT] Storage FileStorage 6.4.0.0 loaded from file C:\Program Files\SCADA\ScadaComm\FileStorage.dll
2026-08-05 18:51:32 [ENGINEERING][ENGINEERING$][ACT] Start logic processing
2026-08-05 18:51:32 [ENGINEERING][ENGINEERING$][ACT] Driver DrvDsScadaServer 6.0.1.1 loaded from file C:\Program Files\SCADA\ScadaComm\Drv\DrvDsScadaServer.Logic.dll
2026-08-05 18:51:32 [ENGINEERING][ENGINEERING$][ACT] Driver DrvSimulator 6.0.0.0 loaded from file C:\Program Files\SCADA\ScadaComm\Drv\DrvSimulator.Logic.dll
2026-08-05 18:51:32 [ENGINEERING][ENGINEERING$][ACT] Data source ScadaServer initialized successfully
2026-08-05 18:51:32 [ENGINEERING][ENGINEERING$][ACT] Data source ScadaServer: Receive the configuration database
2026-08-05 18:51:34 [ENGINEERING][ENGINEERING$][ACT] Data source ScadaServer: The configuration database has been received successfully
2026-08-05 18:51:35 [ENGINEERING][ENGINEERING$][ACT] Start communication lines
2026-08-05 18:51:35 [ENGINEERING][ENGINEERING$][ACT] Start reading commands from files
2026-08-05 18:51:37 [ENGINEERING][ENGINEERING$][ACT] Data source ScadaServer: Connection state is Logged In2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] The source code of scripts and formulas has been compiled successfully
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Module ModArcBasic 6.2.1.0 loaded from file C:\Program Files\SCADA\ScadaServer\Mod\ModArcBasic.Logic.dll
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Module ModArcPostgreSql 6.2.2.0 loaded from file C:\Program Files\SCADA\ScadaServer\Mod\ModArcPostgreSql.Logic.dll
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Archive Cur initialized successfully
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Archive Min initialized successfully
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Archive Hour initialized successfully
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Archive Events initialized successfully
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Start listener on port 10000
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][INF] Archive in DAT format: C:\Program Files\SCADA\Archive
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][INF] Archive copy in DAT format: C:\Program Files\SCADA\ArchiveCopy
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Archive Min: Update channel numbers of the page C:\Program Files\SCADA\Archive\Min\Min20260805\min20260805_0014.dat
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Archive Hour: Update channel numbers of the page C:\Program Files\SCADA\Archive\Hour\Hour20260805\hour20260805_0001.dat
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Delete outdated data from the Min archive older than 05/08/2025
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Delete outdated data from the Hour archive older than 05/08/2025
2026-08-05 18:51:31 [ENGINEERING][ENGINEERING$][ACT] Delete outdated data from the Events archive older than 05/08/2025
2026-08-05 18:51:34 [ENGINEERING][ENGINEERING$][ACT] Session with ID 4657788858686719484 created
2026-08-05 18:51:34 [ENGINEERING][ENGINEERING$][ACT] Client 127.0.0.1 connected
2026-08-05 18:51:34 [ENGINEERING][ENGINEERING$][ACT] User ScadaComm is successfully authenticated
2026-08-05 18:51:36 [ENGINEERING][ENGINEERING$][ACT] Client 127.0.0.1 disconnected
2026-08-05 18:51:37 [ENGINEERING][ENGINEERING$][ACT] Session with ID 766818876841368238 created
2026-08-05 18:51:37 [ENGINEERING][ENGINEERING$][ACT] Client 127.0.0.1 connected
2026-08-05 18:51:37 [ENGINEERING][ENGINEERING$][ACT] User ScadaComm is successfully authenticated
2026-08-05 18:59:22 [ENGINEERING][ENGINEERING$][ACT] Session with ID -5416493400788669943 created
2026-08-05 18:59:22 [ENGINEERING][ENGINEERING$][ACT] Client 127.0.0.1 connected
2026-08-05 18:59:22 [ENGINEERING][ENGINEERING$][ACT] User ScadaComm is successfully authenticated
2026-08-05 18:59:22 [ENGINEERING][ENGINEERING$][ACT] Command to channel 104 from user with ID 2
2026-08-05 18:59:22 [ENGINEERING][ENGINEERING$][ACT] Command is queued to be sent to clients
2026-08-05 18:59:25 [ENGINEERING][ENGINEERING$][ACT] Command to channel 104 from user with ID 2
2026-08-05 18:59:25 [ENGINEERING][ENGINEERING$][ACT] Command is queued to be sent to clientsAugust 5, 2026 at 1:34 pm #18242prabhu.natarajan.n@gmail.com
ParticipantAugust 6, 2026 at 10:57 am #18243
MikhailModeratorHello,
In ScadaServer.log
2026-08-05 18:59:22 [ENGINEERING][ENGINEERING$][ACT] Command to channel 104 from user with ID 2 2026-08-05 18:59:22 [ENGINEERING][ENGINEERING$][ACT] Command is queued to be sent to clients
That’s good.
I guess that Communicator does not receive commands, because both the ScadaGenerator app and the ScadaComm service are logged-in as the ScadaComm user. There is a protection to avoid infinite command loop. Try using the ScadaWeb user in ScadaGenerator.August 6, 2026 at 11:00 am #18244
MikhailModeratorPlease let me know about the result.
-
AuthorPosts
- You must be logged in to reply to this topic.