What is the safest HUD code?

O.C.Diver

Ditto; well said; have some green!

Ted

__________________
Consider this my opinion.......sometimes I'm even right, but remember.........YMMV.

Ted Green
Charter Boat "OC Diver"
http://www.ocdiver.com

decoweenie

It does (with small mod as Joe mentioned).

However, even if you did, it doesn't count as you obviously don't know how it works (i.e. your comment about red blink for 1.0+)

__________________
"...after a while you get bored offering advice to a bull that like to keep butting the fence with its head rather than walking through the open gate..."

- Rebreather World PM

Janos

It sounds like a system that's been developed for the Developer, not the Customer.

Janos

__________________
You can lead a horse to water but you can't climb a ladder with a large bell in both hands - Vic Reeves
www.hellfins.com/shed

Hanssing

Hi All,

I'll give this rather hot topic a go, since most people are discussing the existing solutions, instead what they would like.

Please note, that I'm a wannabe, and as such I write how I THINK I would like it..... I do however program industrial automation/machines for a living, and as such a have some first-hand knowledge of what works and what does not.

There is IMHO two thinks that the HUD should at most convey, PPO for cells and general alert for all of ADs other alarms (CO2, breathingrate, ascent-rate etc.). But the most important thing is to get rid of alarms that are triggered by normal operations. Never blink red if its not something immediately critical. Otherwise red will get ignored in the end. So first and foremost make sure red, really means something, and that it will never get ignored.

First up are some general thoughts about the HUD:
I would prefer it to be seperated into two defferent parts/hud/whatever so that they are not mixed, and theres less chance of misreading one segment for the other. So one section for PPO-info and one for General System OK/Waring/Error.

For the general systems-info, I would avoid using too many colors, and codes. Its possible to use fibre-optics and multiplex a lot of different leds, but ppl forget, and then the HUD has failed.
Generally a light can have 3 states if those states are not occuring frequently: OFF, ON, and blinking. So for the general info-sgment:
GREEN = OK (with a pulse if ppl, prefers that)
YELLOW = WARNING, BLINK-YELLOW=Multiple warnings/New warning
BLINK-RED=Critical (as in life-treatning) alarm
That is only if its needed at all in the HUD-segment.

-------------------

Now for the PPO-dispaly - Main-information to be displyed is for each cell:
Is the loop lifesupporting, ie. within alarm-range high and low.
If the loop is not lifesupporting is it HIGH (Yellow) or is it LOW (Blue)?
If the loop is OK, exactly what PPO is currently meassured?

Now RED=ON is BAD - RED means youre DEAD (or dying), or that the cell/unit is completely malfunctioning.

This is one configuration:
RED-BLINK/YELLOW-BLINK/GREEN-OFF = Critical: PPO above alarm-level.
YELLOW-blink/GREEN means RICH (one blink for 0.1 above setpoint etc.)
GREEN is good, means PPO is OK (at setpoint)
BLUE-blink/GREEN means lean (one blink for 0.1 below setpoint etc.)
RED-BLINK/BLUE-BLINK/GREEN-OFF = Critical: PPO below alarm-level.

So in summary:
RED -> Only used when critical alarms are active (not lifesupporting)
GREEN -> System is lifesupporting
If in green-zone, indication of setpoint-deviation.

Never trigger RED lights if its not actually critical!
Ex Never trigger alarms during setpoint-switch. Setpoint-switch is a normal operation, and is not critical. Alarm-levels should be filtered/ramped accordingly. So if switched from 0.7 to 1.2 and low alarm-delta is 0.2 (ie. switched from 0.5 to 1.0), then the low limit should be ramped up slowly, as to never cause RED lights during normal operations.

Just my input, and I'm looking from outside the Rebreather-box....

Regards
Nicolai

Mark Chase

Woooo Hoooo, I got one right

I was talking about the Sherewater Hud not the HH. I didn't realize the Sherewater had green flashes as i only ever saw Red on Janos HUD when doing the bubble check etc.

Every now and then id catch a glimpse of a red flash on his HUD and i wrongly assumed the LEDs we red only.

Bruce, I humbly apologise for my error

ATB

Mark Chase

__________________
Is it supposed to make that noise ?

I took my unit to the dive shop and demanded they bolt on every thing that would fit.

Join my elite diving teem and get a Tshirt

"Doing It Chasey"Hammerhead Eccr Advanced Diving System

divetheworld

Alex,

Here is an idea for you. Feel free to use it if you wish (with reference to me of course!).
How about an LED bar graph array with the centre being setpoint. The further you are away, the colour changes. Colour is not the only indication as the position of the light should be sufficient (for colour blind?).

Vertical for absolute readout or horizontal for "rich to the right" etc. I would suggest the green centre should slowly "wobble" to indicate the controller is not "stuck" as could be the case in a green=good/red=bad indicator.



With current developments of LED technology including the flexible array, there are a number of ways to innovate the idea.

Brent

__________________

jptaylor9

I think the Vision has it about right. Steady green = OK, flashing green & reds for warnings & serious problems. I dive with a Meg diver, so I'm aware of the alternative method of counting flashes.

The Vision has got my attention for a number of issue, cell errors, high ppO2, deco ceiling violation & others, so I feel it enhances my safety.

jradomski

I really have to disagree with this.. I would never want a Solid led (either on or orff) as a good indication.. CPUs do freeze.. A constant signal is a bad thing...

I soldi indication is ok for a failure or even maybe a power on indicator (useless in a hud), but otherwise solid=good is bad in my opinion..

__________________
Joe Radomski
CCR Trimix Instructor Trainer
ANDI Instructor Trainer Director #10

All posts are personal opinions and DO NOT reflect any affiliated agency unless specifically stated.

decoweenie

It is already difficult enough (for me) to see the different shades of light at depth (i.e. red, green) sometimes.

Personally, I wouldn't want to use light of close shade like red - orange - yellow at depth where the colors are not true anymore.

Just my opinion...

__________________
"...after a while you get bored offering advice to a bull that like to keep butting the fence with its head rather than walking through the open gate..."

- Rebreather World PM

Hanssing

Actually I meant YELLOW=ORANGE which shuld be selcted so it is clearly different from both red and green. If not then another color should be chosen - but wich?
The main piont was RED=Danger, and should only be activated if it really is Danger. Normal operation during predive, dive and deco should never trigger red-light.
This has the disadvantage that people cannot remeber the light-sequnces in red, since that color is not used often. I therefor suggested reducing the no. of light states to a minimum: OFF/ON/BLINK, with RED-blink as life-threatning.

Please note that the sugestion was also to seperate PPO-monitoring from everything else, so one cannot get confused between the two. Ie. set them physically apart.

BTW: I thought the color would be as true on the bottom, because the water-distance is the same (i.e. from HUD to mask), and the surrounding light has faded, which should make them lights even clearer?

Regards
Nicolai