forum.heinrichsweikamp.com

2h hours after the dive I had a no fly value of 65:34, what does this mean? I can't believe these are hours. I also had a smal vaulue for Desat, which is gone now. My saturation bar is complety empty now (80%) for N2 and HE, but I still have 63:something for no fly!? I did something like 20min@65m today using a light trimix in a CCR.

I'm currently running 1.81 but noticed this behaviour also some weeks ago (1.80 or the latest 1.7x release).

Check the desat cf.

CF12: 90% (Default 90%)

After 5 days off the water now it shows 216:something, looks like a bug to me.

Updating to 1.82 now...

Most likely also broken in 1.82, switching to the 1.82 thread now...

Mate,

Wrong cf

You should be looking at cf 13.

CF13: 60% (Default 60%)

As assumed by other guys as well in the 1.82 thread there seems to be some kind of problem. The no fly value shows now 68:13, seems correct in relation to the 70:xx before...

Try loading it from the pc software. it may well be 1060%

or from the pc reset all cf's and start all over again.

Hi,

There was a bug in the NoFly routine, please check the new beta (coming in the next days) about this issue.

Cheers,
Matthias

Just for the records: After doing a shallow dive some hours later the no fly value is now cleared....

Hallo,

habe letztes Wochenende die neue Version 1.83 ausprobiert. Während des Tauchgangs war alles bestens. Die Anzeigen nach dem Tauchgang haben aber ein paar Fragen aufgeworfen.
- noFly - es wurden ca. 65h angezeigt,bei desat von ca. 34h und CF13 mit 60%,der Fehler scheint also noch vorhanden zu sein
- desat - unmittelbar nach dem Tauchgang waren es 34h, 2h später noch 21h und weitere 6h säter nur noch 7h
In dieser Zeit habe ich mich von 600müNN auf 200müNN runter begeben. Das sich bei Verringerung der Höhe die Zeit verkürzt, habe ich erwartet, aber so gravierend dann doch nicht. Mein 2. TC war von der Höhenänderung dagegen völlig unbeeindruckt.

Grüße
Rüdiger

The topic starts in english
Can you continue in english please ?
Thank you

Rüdiger just stated again that there is something wrong. I think this topic is well known now and covered in the 1.83 Thread also, so we can stop discussing this in here...

Definitely a bug, high in my priority list (because sounds quiet easy to correct). In fact, the conjunctions of two:
- NoFly bad value just when you exit a dive.
- Doing a simulation (eg. just the default 1min@15m) reset the NoFly value to something correct (except it should not be reseted).

Thanks for the signaling.

the annoying blue led

beta V1.83

still the same "No Fly" bug......


Ekki

the same bug for me with 1.87 Beta

see PDF below

Bug No Fly v1.87 Beta