3/22/2024 2:31 PM | |
Joined: 2/1/2010 Last visit: 10/3/2024 Posts: 150 Rating: (71) |
There is an old post discussing this which gives hints: If you do the reverse engineering based on the @RedStateDispContainer.pdl you can assume the bits correlate to the bit mask definitions at the top and the usage later in the background color c-script. MASK_FLASH_ON 0x0001 - new bad redundancy state occured - flashing icon MASK_SOME_BAD 0x0002 - red fault state - red icon state MASK_POSTPONED_FAULT 0x0004 - postponed fault - yellow icon state MASK_ARCHIVE_SYNCRONIZATION 0x0008 - syncing state - show the sync arrows on icon According to this, should be bits 0-3 (one byte) and integer values 0-15, but of course all integer values are not possible. Integer 7 would mean new event, bad, and postponed fault: likely a non stable moment for your system, unless my quick bit math is wrong. |
If my post helped you, please rate. Thanks. |
|
3/22/2024 4:58 PM | |
Joined: 2/1/2010 Last visit: 10/3/2024 Posts: 150 Rating: (71) |
Sorry, agree I was looking at flags info not the server state itself you are talking about. The Global script "DisplayServerStates.fct" is not locked so you can see the source. That is the global script that gets called by the Display on change (of @RedundancyWatchPCStates) C-script on @ServerStates.pdl Similar masking data and reverse engineering capability exists inside the script. MASK_ONLINE 0x0000001 Looks like bit 3 is postponed fault. So now just missing a definition for bit 1. Maybe with more digging we can determine it, but it looks like Siemens themselves are not visualizating it anywhere directly that I can see.
|
If my post helped you, please rate. Thanks. |
|
Follow us on