Forum Replies Created
-
Posts
-
Hi,
You found the secret key in the right place.
The default agent’s password is also scada.
This video may be useful.> the “Encrypted Password String Bytes” are different each time
Yes. The protection algorithm encrypts password differently. Otherwise, someone can sniff packets and login.Check the ScadaClient and ClientBase source code.
Hi,
Thank you for the details.> As for why calculated channels always 0 is due to I enable the formula with 0. I disable the formula and problem solved.
There is also a general server option to disable channel formulas.> Looks like the “converting DAT files to PostgreSql database” is success.
That’s good!In the protocol, a string is encoded as
Bytes 0…1 – the string length in bytes
Bytes 2…N – the UTF-8 encoded charactersCould you specify what should be updated in the document?
You right. The Users table contains the password hash, while XML files contains encrypted passwords. Hash cannot be decrypted. Encrypted password can be decrypted. You can encrypt password with Administrator user interface.
If you run the HelloWorld project and use the default configuration of ScadaTestClient, can you successfully communicate between the client and the server?
You can try setting SecretKey to an empty string. If ScadaTestClient allowed that (I don’t remember), it would simplify the protocol packets.
Likely ScadaTestClient.xml contains invalid SecretKey property.
ScadaTestClient source code is here if need.The cause of the error is that there is no partition for old data. You should create it manually using pgAdmin. SQL example:
CREATE TABLE mod_arc_postgre_sql.min_historical_20240101_20240201 PARTITION OF mod_arc_postgre_sql.min_historical FOR VALUES FROM ('2024-01-01 03:00:00+03') TO ('2024-02-01 03:00:00+03')Set your own dates for the partitions. By default 1 partition covers 1 month.
