Only Archive on “Status change”

[Mikhail]

1. Is there a chance that they are written when Server restarts? What can be the cause of writing?
2. If the channel value changes, is it written to the archive?
3. Tick “Log enabled” checkbox. What would be in the archive log file?

[TroyV23]

1. Is there a chance that they are written when Server restarts? What can be the cause of writing?

I tested restarting the server but it did not trigger any new entries.

2. If the channel value changes, is it written to the archive

Yes, the when the value of a bit goes from OFF/ON or ON/OFF it does write to archive, but there are also additional writes in between, and I’m getting multiple ON writes in a row.

3. Tick “Log enabled” checkbox. What would be in the archive log file?

The log looks like this:
2026-08-20 10:41:02 Data queue has become empty
2026-08-20 10:41:02 Enqueueing of 1 data points completed successfully in 0 ms
2026-08-20 10:41:02 Data queue has become empty
2026-08-20 10:41:03 Enqueueing of 1 data points completed successfully in 0 ms
2026-08-20 10:41:03 Data queue has become empty
2026-08-20 10:41:03 Enqueueing of 2 data points completed successfully in 0 ms
2026-08-20 10:41:03 Data queue has become empty
2026-08-20 10:41:03 Enqueueing of 3 data points completed successfully in 0 ms
2026-08-20 10:41:03 Data queue has become empty
2026-08-20 10:41:03 Enqueueing of 1 data points completed successfully in 0 ms
2026-08-20 10:41:03 Data queue has become empty
2026-08-20 10:41:03 Enqueueing of 1 data points completed successfully in 0 ms
2026-08-20 10:41:04 Data queue has become empty
2026-08-20 10:41:04 Enqueueing of 1 data points completed successfully in 0 ms
2026-08-20 10:41:04 Data queue has become empty
2026-08-20 10:41:04 Enqueueing of 1 data points completed successfully in 0 ms
2026-08-20 10:41:04 Data queue has become empty
2026-08-20 10:41:04 Enqueueing of 2 data points completed successfully in 0 ms

• This reply was modified 1 month, 1 week ago by TroyV23.

[Mikhail]

I’ll check the source code for the additional details, and write here.

[Mikhail]

Hi,

I’m trying to reproduce the issue. But it works correctly on my side.
Test scenario:
1. Open the HelloWorld project.
2. Update the archive properties as shown https://ibb.co/G4bkbWQP
3. Unset the default checkbox for the archive https://ibb.co/1pbGTYn
4. Configure the channel 104 archives https://ibb.co/HLTsfbG7
5. Stop Rapid SCADA.
6. Clear data in the PostgreSQL database.
7. Upload the project.
8. Change channel 104 values via the web interface multiple times.
9. Check data in the database https://ibb.co/cc8s4Pzh
Data is written in the archive only on change.

Please perform the same test on your side.

[TroyV23]

This is with the same settings you’ve shown above:
https://www.imghippo.com/i/nKU4907dgo.png

Should I update my version of rapidscada maybe? Currently running v6.2.2

[Mikhail]

Update to the latest version Rapid SCADA 6.4.7

[TroyV23]

I have updated to latest version and I’ve found the source of the issue.

The value of the bit is not changing but the status of the bit is changing which causes a “write” entry even when the value of the bit has not changed. I get many of these status changes which causes this issue.

Is there a way to ignore status, and only write on “value” change?

[Mikhail]

Is there a way to ignore status, and only write on “value” change?

Talking about writing to archive, there is no such an option.
To solve the issue, let’s find why the status changes and avoid that.

[Author]

Posts