"Scan Project for TEDS" erasing alarms is undesirable

[mnugent]

Clicking "Scan Project for TEDS" erases prior defined alarms. This is frustrating.

We have a FlexLogger based test stand with 100 input channels, a mix of bridge and voltage. All transducers have TEDS chips.

Unexpected behavior: I plug in 60 sensors, scan for TEDS, then spend a good bit of time defining additional alarm criteria. If I later add a 20 additional sensors and click "Scan Project for TEDS", all of the existing sensor channels have their alarms deleted.

What I would expect to happen: If I click "Scan Project for TEDS" and the TEDS chip data matches what's already in the FlexLogger channel definition, then DON'T delete the alarms for that channel. If the TEDS chip data doesn't match what's already in the FlexLogger channel definition, we are dealing with a new sensor, so delete the alarms for that channel. If the TEDS chip data is now empty, the sensor was removed so delete the entire channel definition including alarms. Functionally, the button would be "Scan Project for TEDS Changes".

[mnugent]

The same undesirable behavior exists for Channel Name. When clicking "Scan Project for new TEDS", all of the prior defined Channel Names get erased. This should not happen if the TEDS chip data matches the configured sensor channel data. It means the sensor did not change.