1.29 bug

[heinrichsweikamp]

Yes, it's your file. Simulation is still running....

Regards,
Matthias

[heinrichsweikamp]

Ok, Simulation passed fine. I used TX14/34.

Did anybody with this issue had this problem with the same firmware on two dives (Without upgrading/downgrading/resetting in between)?

regards,
Matthias

[Olivier]

heinrichsweikamp Wrote:
-------------------------------------------------------
> Did anybody with this issue had this problem with
> the same firmware on two dives (Without
> upgrading/downgrading/resetting in between)?

Not me. And more, I thought - maybe like you - that the bug could appear at the first dive after upgrading. So I tried downgrading, diving, upgrading and diving again... but wasn't successful in repeating the bug (which obviously exist). Sorry !

Since my first dive, I dived sometimes with 1.26, 1.29 and 1.30, every times ok.

[corona_citron]

heinrichsweikamp Wrote:
-------------------------------------------------------
> Ok, Simulation passed fine. I used TX14/34.
>
> Did anybody with this issue had this problem with
> the same firmware on two dives (Without
> upgrading/downgrading/resetting in between)?
>
> regards,
> Matthias


oh oh, I think that Mathias is on the track to find this bad bug...
Yeah, kill it my dear

[champollion]

Well well ... Like Corona Sunday morning had the bug "99 decosum" but can't say really when things began to go wrong.
Second dive everything went fine, nothing to understand ...

I did nothing in the meanwhile, upgrade or nothing, I'm still in 1.29

This morning, Fixed PpO2 1.2, GF 50/90, dil 19/10 (don't laugh, was just emptying bottles )
43m going up after some 25 minutes, 1min at 12m looks like normal.

Going up very slowly, at some 25 meter yellow warning light went on, GF was shown 51% (maybe THAT is the trick ?? if GF was really 51 I should have had a stop there) , something like 68 minutes at 12meter (never went to 15 meter), 99min decosum.

I did go down a bit to test, indeed GF went back to 43%, yellow light off, but still the same deco. Up again, at 50% yellow light back on, didn't really look at it the rest of the dive (you can bet ...)

Another question follows about decodata in another post.

[champollion]

Forgot to mention, again a peak of Helium in only 1 compartment.

I dive again this evening, do you want me to try some settings while I'm still not desaturated ?

[champollion]

I checked the decodata. dT of Sunday morning is 40s, afternoon 30s, and this morning 60s, while I didn't change any setting in the meanwhile ... ???

From the last dive, the problem is easy to find minute 27 12m:1', minute 28 12m:69' ... bad boy !

[champollion]

Sorry for the many posts ...

Again, yesterday evening second dive of the day, everything went fine ...

[Bruno]

Hello,
I do not know if I missed something but as far as I can see the solution to this problems has apparently not been found yet.
I wonder which is the last "bugfree" version (I'm thingking of major bugs..) available ?
Is it 1.22 ?
Thank you and happy Eastern to All of you.

[Anonymous User]

Bit concerend here too as it seems a lot of attention has gone to the OC side of the computer, but the CCR side is possibly a bit dodgy.

Can we have some extensive (or at least some more attention given to) the CCR side of the deco functionality?

[sailor]

Hello,

what i understood sofar is that the bug with increasing TTS is only active for the first dive after upgrading.
All subsequent dives are eventless.
This is at least the case for my two units and i believe some other users mentioned the same.
Also i'm quite happy with the CCR-features.

Reiner

[Anonymous User]

sailor Wrote:
-------------------------------------------------------
> Hello,
>
> what i understood sofar is that the bug with
> increasing TTS is only active for the first dive
> after upgrading.
> All subsequent dives are eventless.
> This is at least the case for my two units and i
> believe some other users mentioned the same.
> Also i'm quite happy with the CCR-features.
>
> Reiner

Well, bugs that come and go without knowing how they got there and how they went is not really the safest approach to safe diving. Bugs have to be debugged and the cause understood before contentment (otherwise the OSTC cannot be ever considered reliable for the purpose of primary or backup deco).

[heinrichsweikamp]

Hello,

Your 100% right! Unfortunately this bug did not show up at our place until today. For example I've updated a few OSTC from our rental stock recently and put them with different mixes in the pressure chamber - they all came out fine. Maybe some combination of actions underwater will cause it. Two of us are diving the entire next week, we'll do some more underwater tests again.

regards,
Matthias

[sailor]

OSTCfan Wrote:
-------------------------------------------------------
> Bit concerend here too as it seems a lot of
> attention has gone to the OC side of the computer,
> but the CCR side is possibly a bit dodgy.
>
> Can we have some extensive (or at least some more
> attention given to) the CCR side of the deco
> functionality?


Hi, let's know what in particular you are missing for the CCR side of deco functionality?

[corona_citron]

Today, CCR cave dive.
V1.30, TX 15/25, Depth 35, Time 50'.

No bugs.... great

[sailor]

Hi,

i had the TTS and deco bug now also on a CCR Nitrox decopmpression dive to max 44 meters and 38 minutes and there was no update just before that dive.
On 6 meter the OSTC first cleared almost together with my Shearwater and then after some time staying a little longer on around 6 meter the OSTC suddenly displayed the deepest stop to be on 21 Meter and the TTS to be 45 minutes.
The funny thing is that after the dive the OSTC showed some Helium-load but i used only air as diluent and bailout. No Helium-mixes where selected active gas and no bailout was selected during the dive.

This OSTC is on version 1.30.
Hopefully this issue will be solved with the next stable version.

Here a snapshot of my divinglog screen, the file itself is to big for this forum.
If someone is interested in the divinglog-file i can send it by email.

[IMG]http://img98.imageshack.us/img98/7802/ostc.jpg[/IMG]

Reiner

[divinglog]

Hi Reiner

It's interesting that the OSTC stored first a "Deco stop ignored" waring before it stored the "Deco Flag" itself (the red waring line is starting before the yellow deco line). Normally it should be the other way around.

Sven

[heinrichsweikamp]

Thanks Reiner,

This will be quite helpful!

Regards,
Matthias

[Anonymous User]

error (no way in the forum interface to delete a post entered in error).

[Anonymous User]

sailor Wrote:
-------------------------------------------------------
> Hi,
>
> i had the TTS and deco bug now also on a CCR
> Nitrox decopmpression dive to max 44 meters and 38
> minutes and there was no update just before that
> dive.
> On 6 meter the OSTC first cleared almost together
> with my Shearwater and then after some time
> staying a little longer on around 6 meter the OSTC
> suddenly displayed the deepest stop to be on 21
> Meter and the TTS to be 45 minutes.
> The funny thing is that after the dive the OSTC
> showed some Helium-load but i used only air as
> diluent and bailout. No Helium-mixes where
> selected active gas and no bailout was selected
> during the dive.
>
> This OSTC is on version 1.30.
> Hopefully this issue will be solved with the next
> stable version.
>
> Here a snapshot of my divinglog screen, the file
> itself is to big for this forum.
> If someone is interested in the divinglog-file i
> can send it by email.
>
> http://img98.imageshack.us/img98/7802/ostc.jpg
>
> Reiner

Scary stuff for a dive computer.

May I suggest the whole deco portion of the software be scrapped and rewritten from start?