[Imported] Duty Mode and a custom driver

[sbeadle]

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: geoffpatton, originally posted: 2019-02-01 00:37:27 Id:357
I have a customer that encountered a Main - Main situation and their servers are in two locations so they lost the data from one when they synced.
So they enable Duty Mode and it worked fine for everything but a custom driver that we created. The object that we are using contains Tag Out information in it and that information was still lost. I am suspecting that since it is a custom driver ClearSCADA doesn't know what to do with it.

Just curious if anyone has encountered this before?

[sbeadle · Accepted solution]

>>Responses imported from previous forum

Reply From User: adamwoodland, posted: 2019-02-01 04:03:04
What is this Tag Out info? Duty-Duty only cross-syncs a subset of the database data, what it doesn't cross sync is sourced from the Main only (i.e. like normal Main-Standby). Some advanced drivers can do current data if enabled but the DDK is using the simple driver architecture.

I couldn't find any information in the help, but I'm sure it'll be there somewhere. From internal dev notes, so may not be 100% accurate in the latest versions, the following are merged following a Main-Main with Duty-Duty enabled:

* Raw data
* Modified data
* Annotation
* Suppression
* Event journal
* Alarm summary
* Configuration changes

Current data for advanced driver points can optionally be merged (must be enabled on outstation).

Historic files (Crystal Reports etc.) are merged.

No other data is merged.

Reply From User: geoffpatton, posted: 2019-02-01 11:51:15
The Tag Out is Tagging Electrical Utility Circuit Breakers that are being worked on.
They do have a log of Tag Outs so they can rebuild it. Just not ideal.
Thanks For the info Adam.