Quote: (Originally Posted by decoweenie)
Dave,
IMHO, there is a basic principle difference between the "normal" HUD and the Smithers Code HUD.
The "normal" HUD (like the Vision, for example) is very close to the passive idiot-light concept in cars. When everything is fine, no flashes no alarms etc.
The Smithers Code HUD is a more active type system which communicates constantly to the diver. There is really no alarm, only information to relay to the diver the entire time.
I think of the Smithers Code HUD is like a "numeric" gauge sending me a value instead of an alarm gauge. So once you have change the mindset from what you expect from the HUD, I think you will like it better.
When I was diving the KISS-HH, the annoying thing was buddy kept coming to ask me if I am OK since they kept seeing the flashing LED infront of my face...
I think you've hit on the key point here.
It's all about what you want your HUD to be for you.
Do you want it to be your primary sensory "full range" input device, or a more secondary device that's easier to monitor continuously while in the "all is going pretty well" range.
Depending on what the implementation details are, therein lies whether you could loose digital readout, but still maintain HUD function, or if it's HUD function that could fail, but still leave digital readouts functional.
Personally, I'd rather have the digital readout be the more protected, (electronically and physically) so that if I snag the wire to the HUD or something, I have the digital still working.
To borrow your car idiot light analogy, I see the HUD as more than just an alarm light, Mine is a "numeric gage", as you describe, it's just limited to a more specific range, and don't forget that unlike the car anology, you also have the gages with the lights.
Darlene