forum.heinrichsweikamp.com

Hello Matthias,

As I had a normal, OC and air only dive yesterday, I was coming back from the abyss with approximately 35mn of deco time and checked the decoplan on my ostc. No problem so long. Exit from decoplan, still OK. But suddenly, as I was not moving, the % of my GF became terrible: 110%, 150%, 250% and so on. I was at 9m or so, but my ostc send me back to 18 or 21m, with 30 or 40mn of deco time, and more than 99mn of total time. Beep beep during the rest of my dive. The gauge and timer were still OK. Back to the ship, the dive and datas on my logbook were strangely pretty ok...

Attached a screen capture of my dive, where you can see the big red alert since 33rd mn onwards. Tell me if I can send you more informations for debugging.

Regards

Olivier



OSTC v. 1.29, OC with GF (default).

hello,,

I had the same problem today during a CCR dive - TX14/33 - 52m
About 10 min at 52 then 6-7 min at 40.
I had a TTS of 18 min
A few seconds later, I had a TTS of 99 min.
I've made the deco stop at 15 m then at 6 en then I had 35 min at 3. Unbelievable for this kind of dive.
I went out without any problems on my backup...

Hi,

Can you post the Jdivelog or Divinlog log file here, please. So I will try to reproduce this...

regards,
Matthias

Here it is...

Regards

Olivier

Hello Olivier,

Thanks for the file!

Have you tried to replay the dive with Jdivelog? I've tried with GF OC mode and it passed fine. (Well, I noticed that the max. depth, temperature and current gas are displayed several seconds after the decoplan is quit -> fixed.)

regards,
Matthias

Hello Matthias,

Just done it after waking up this morning... Passed fine also, I can't get the bug repeating. I'll keep you aware if I have troubles more (I dived yesterday but was back on 1.26. I'll keep 1.29 now). Can it help you if I have debugging mode on ?

Regards

Olivier

No, the debugger runs in the background all the time and is intend to find out troubles when the output freezes or if the unit is reacting slow.

Regards,
Matthias

Hello,
Should one stop using version 1.29 pending the bug to be fixed ?
Thank you & regards
Bruno

here you have the log of my OSTC. The 3rd dive has the problem. The 2 first dive were run for testing purpose by you.

I hope it can help you

Regards

during the 'rerun', my ostc said that the temperature was -75?C en that the max deep 125m was.

After a reset, the temperature is -43 C

I decided to go back to version 1.22

after reset, the temperature remains on -43,6

Hello,

Again, temperature problem has _nothing_ to do with software. This is an intermittent contact to the pressure/temperature sensor.

regards,
Matthias

ok. I just wanted to mention it...

corona_citron Wrote:
> here you have the log of my OSTC. The 3rd dive has
> the problem. The 2 first dive were run for testing
> purpose by you.

A different question: Where did you make this dive?

Regards,
Matthias

where...? in a quary in Belgium...
I don't know why you ask this ?
Can that influence a deco ?

No, I'm just interested

Regards,
Matthias

Hello,
Is 1.29 safe for diving or not ?
Thank you
Bruno

Until today I was not able to reproduce the described behavior.

Regards,
Matthias

Hi,
i did a dive today with software 1.29 to 72 meters, bottom time 20 minutes, total time 85 minutes, on CCR with diluent 14/50 and GF 5/90.
Everything was fine during the dive and the deco was very close to my shearwater and vision as usual.
No bug, no hung-up, no funny deco-info or so, very smooth and i played a little with the PO2-setting aswell.

Now comes the funny thing. At home i jumped in the pool to flush my kit and played a little more with the UW-menue.
I also called up O2 Mon. ( without having a O2-board connected ) and now the OSTC got hung-up and was only resetable with the interface.
I thought this bug was cleared with 1.29?

So to sum it up, during the relativly extrem dive no issue at all with deco or so but when selecting O2 Mon. the OSTC still hung-up also with software 1.29.

Regards, Reiner

P.S.: I'm using divinglog and the logbook is to big to attach it here so if anybody is interested i can send it by email, your request to reinerklQyahooDOTde please ( file already sent to HeinrichWeikamp )

Hello Reiner,

Thanks for the report, maybe you can retry this again next time? And can you check the installed firmware (With the Divinglog-Firmware Hash check). It was an easy to fix bug and I was quite sure it has been fixed.

Regards,
Matthias

Hi Matthias,

Firmware ID:

SN 186: 011DCE6EE97DA95475FD91A52F4CBD9481F7
SN 36: 011DCE6EE97DA95475FD91A52F4CBD9481F7

So both the same.

Is it this what you where asking for?

I will check the bug for you again right away.

Thanks, Reiner

Looks like a correct 1.29.

Hi,

same same hung-up when selecting O2 Mon. in the UW-menue again, snapshot before resetting send by Email.

Another thing is my OSTC's wount start automatically in a 2 meter deep pool even after adjusting CF0 to 50 cm. I have to start them manually.

Reiner

Have you waited long enough? It can be up to 10s worst case until the OSTC wakes up.

Also, there are two thresholds (CF6(wake-up) and CF0(start dive)) where you can adjust this.

regards,
Matthias

Ah, ok, i changed only CF0 but i'll have to change CF6 to 1150 for a 2 meter deep pool, thanks.