When manufacturers design make sure platform can allow at least 2 software versions or at the very least allow what I call both newer version update (whole) and a older subset (portion of older version) to be used.
Why?
Makes testing easier if and when a newer version is designed and requires pre release testing in the field for validation. Would allow users after version!release to use different versions and gain first hand feedback of the benefits or lack thereof!of different versions or version subset(s). Case in point. Notice Minelab left old iron bias to be user selected when they released!newer version with iron bias F2 option.
So in a nutshell this allows the detector versions ( or version subset) to be compared to the themselves in the field by the user.
Xp should have done this too. They should have designed Deus imo where at least 2 complete version allowed to be uploaded to unit.
Notice the later released Ace Apex. Garrett should have allowed on it too.
Don’t know what added production cost this would cause. Hopefully not much.
Why?
Makes testing easier if and when a newer version is designed and requires pre release testing in the field for validation. Would allow users after version!release to use different versions and gain first hand feedback of the benefits or lack thereof!of different versions or version subset(s). Case in point. Notice Minelab left old iron bias to be user selected when they released!newer version with iron bias F2 option.
So in a nutshell this allows the detector versions ( or version subset) to be compared to the themselves in the field by the user.
Xp should have done this too. They should have designed Deus imo where at least 2 complete version allowed to be uploaded to unit.
Notice the later released Ace Apex. Garrett should have allowed on it too.
Don’t know what added production cost this would cause. Hopefully not much.
