fix: hide live discovery protocol noise from Signal Selection - #188
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Field evidence
Real Siemens live discovery on ARSAS
2f2af7d29a4103030b76261a827cc0031d82f1d2/ ARIEC761fa0df9ca84fbe15352d2670f03fddbe8784bacorrectly preserved 58/58 static DataSet members, but Signal Selection still exposed discovery/service noise such asMod,Beh,Health,NamPlt, substitution attributes,origin.orCat,origin.orIdent,ctlVal,ctlNum, andd.stVal/LLN0.q.stValstyle points.The live scan reported 8,481 raw MMS variables, 7,776 FC points, 4,664 SCADA candidates, 2,382 publishable live signals and 213 control objects. The problem is therefore not DataSet parsing; it is the presentation boundary between broad live discovery authority and Signal Selection.
Root cause
SasOperationalSignalPolicyalready has operator-facing rules, but Signal Selection uses WPF's default collection view, which can be shared with another DataGrid. The global UI filter may be installed first and then replaced by the wizard constructor when it assigns its own search/filter predicate. Because the global policy remembers the shared view as already filtered, it can fail to re-wrap it when the wizard loads.Fix
LiveDiscoverySignalSelectionPolicyas a field-hardened selector boundary.Mod,Beh,Health,NamPlt,q,t,d,origin, control-service leaves, substitution/configuration/nameplate attributes, including nested forms such asd.stValandq.stVal.Loadedevent, after constructor search/column filters exist.device.Signalsfrom UI code.Regression coverage
Field-derived negative examples:
GAPC1.Mod.stValGAPC1.Beh.stValGAPC1.Health.stValGAPC1.NamPlt.dGGIO1.Mod.Oper.origin.orCatGGIO1.Mod.Oper.origin.orIdentctlVal,ctlNum,Check,ctlModeld.stValLLN0.q.stValPositive coverage keeps breaker position, MMXU measurements, protection trip, GGIO indications, valid CSWI position control, and object-level static DataSet members. A configured static DataSet member is also verified to remain visible even if its name resembles an engineering state.
Field acceptance
After this PR, Diagnostics can still describe the complete raw MMS/live model, but Signal Selection must not show the protocol/engineering noise above. Static DataSet completeness must remain 58/58. No field success is claimed until the real Siemens IED is re-tested.