Page 2 of 3

Re: 1.29 bug

Posted: 14 Mar 2009, 08:28
by corona_citron
after 3 days, the temperature of my ostc remains on -43.6 C.
Then it was impossible to turn it on.
I've tried with the ostc linked to the computer and it works BUT the battery was nearly empty after only ONE dive (and one week elapsed time)
Now my OSTC is resetting without any intervention of mine..... After the reset, I got the same temperature problem and he says that he has a very high N2 saturation
I think I have a serious problem :(

Re: 1.29 bug

Posted: 14 Mar 2009, 08:30
by corona_citron
furthermore, it's impossible to navigate through the menu. The ostc is switching between surface and dive mode when I push on the buttons....
I've made a secon manual reset. The temperature is now 98.7 C and the pressure is 4419mbar
I think he is dead...

Re: 1.29 bug

Posted: 14 Mar 2009, 08:32
by corona_citron
and when I push on the left button, the pressure goes shortly to 15000mbar..and the temperature is falling to -93 C

The battery is now fully charged after 3 minutes...

Re: 1.29 bug

Posted: 14 Mar 2009, 10:37
by Anonymous User
corona_citron Wrote:
-------------------------------------------------------
> and when I push on the left button, the pressure
> goes shortly to 15000mbar..and the temperature is
> falling to -93 C
>
> The battery is now fully charged after 3
> minutes...

I think the depth/temperature sensor is gone.

I had similar problems with 3 of my Vr3s. Due to a change in production (a switch from lead to lead free soldering) depth sensors were cooked and unpredictably failed thereafter.

This seems to be different though from the bug discussed earlier, UNLESS in all reported cases the OSTC dives itself deeper than it is same as happened to me on the Vr3 due to a bad depth/temperature sensor. This can happen at surface as well as during the dive causing the Deco time to shoot up unreasonably.

Re: 1.29 bug

Posted: 14 Mar 2009, 13:15
by corona_citron
yes, that can be a reason why....

Fortunately, Mathias has already solve the problem this morning.... great service !

Re: 1.29 bug

Posted: 14 Mar 2009, 15:44
by sailor
Hi,

i guess everybody here is very much interested how to solve this kind of problem.
I believe this was solved remotely?
So please tell us a little bit about it, that's what a forum is for.

Thanks, Reiner

Re: 1.29 bug

Posted: 14 Mar 2009, 15:46
by heinrichsweikamp
This is probably (I've not seen the unit yet) a hardware problem related to intermittent contacts to the pressure sensor. We'll replace these for free, of course.

regards,
Matthias

Re: 1.29 bug

Posted: 14 Mar 2009, 16:26
by corona_citron
oh sorry, I didn't mentioned the solution....
I though it was evident

Re: 1.29 bug

Posted: 14 Mar 2009, 17:23
by nicolas schreyer
4th dive with this version (2 only air, 1 Tx+ 2 Nx, 1 air+ Nx)

still stable, no problem...

Re: 1.29 bug

Posted: 14 Mar 2009, 22:10
by sailor
corona_citron Wrote:
-------------------------------------------------------
> oh sorry, I didn't mentioned the solution....
> I though it was evident


No, it is not.
Let us know.

Re: 1.29 bug

Posted: 14 Mar 2009, 23:09
by Anonymous User
OSTCfan Wrote:
-------------------------------------------------------
> corona_citron Wrote:
> --------------------------------------------------
> -----
> > and when I push on the left button, the
> pressure
> > goes shortly to 15000mbar..and the temperature
> is
> > falling to -93 C
> >
> > The battery is now fully charged after 3
> > minutes...
>
> I think the depth/temperature sensor is gone.
>
> I had similar problems with 3 of my Vr3s. Due to a
> change in production (a switch from lead to lead
> free soldering) depth sensors were cooked and
> unpredictably failed thereafter.
>
> This seems to be different though from the bug
> discussed earlier, UNLESS in all reported cases
> the OSTC dives itself deeper than it is same as
> happened to me on the Vr3 due to a bad
> depth/temperature sensor. This can happen at
> surface as well as during the dive causing the
> Deco time to shoot up unreasonably.

What was the problem with your unit?

Re: 1.29 bug

Posted: 16 Mar 2009, 07:28
by corona_citron
heinrichsweikamp Wrote:
-------------------------------------------------------
> This is probably (I've not seen the unit yet) a
> hardware problem related to intermittent contacts
> to the pressure sensor. We'll replace these for
> free, of course.
>
> regards,
> Matthias

Re: 1.29 bug

Posted: 17 Mar 2009, 19:29
by nicolas schreyer
So... I just come back from a little dive...
(déco mode Zh-16 OC)

as I didn't have anything special to do, I just went to have a look in the menus...
I just get in the O2 mode...
and gasp ! frozen !!
:-)

So, just some silly questions:
why does it have an access to this menu in OC mode ?

This problem of freezing should not already be solved ?
(or maybe it is "normal", when there is no O2 cells to reed)

Re: 1.29 bug

Posted: 17 Mar 2009, 21:26
by PeterT
I also have a similar problem, yesterday in the divesimulator-mode i tried to open 'O2 monitor' and then the menu went blank. It was still showing the little arrow wich i moved to the lowest position wich i asumed was 'exit'. I gues i was right because it returned to normal divescreen again.
For the record, i have a model with open bulkhead!

Re: 1.29 bug

Posted: 18 Mar 2009, 11:18
by heinrichsweikamp
Hello,

Thanks for the reports. We're working on the new version already and will look at this issue again.

regards,
Matthias

Re: 1.29 bug

Posted: 19 Mar 2009, 12:02
by PeterT
Hello Matthias,

are you aso working on the divesimulator for the next version?
Isn't easier to let it work like a kind of diveplanner where you just give bottomtime and max.depth and the computer calculates the decoprofile based on the active gases?
It's just a tought, I don't know how other users think about this? This way it would be easier to produce backup-tables!

Re: 1.29 bug

Posted: 19 Mar 2009, 12:33
by heinrichsweikamp
Hello,

Yes, this is exactly the way it's planed. But it won't be in the next version (Which is done but not online because the preliminary testing is not finished).

regards,
Matthias

Re: 1.29 bug

Posted: 19 Mar 2009, 20:05
by PeterT
Ok, I'll be looking forward to that. The next version and the coming diveplanner ;-)
Thanks

Re: 1.29 bug

Posted: 20 Mar 2009, 08:55
by champollion
Same problem when opening O2 monitor while diving freezes the stuff, had to reset with the interface, and the dive is not logged (did never end in fact I was in the last deco stops)

Re: 1.29 bug

Posted: 20 Mar 2009, 11:57
by heinrichsweikamp
Hello,

We've just uploaded a 1.30 with some improvements. A very clear error message is now displayed if any connection timeouts occur.

Regards,
Matthias

Re: 1.29 bug

Posted: 22 Mar 2009, 18:02
by corona_citron
Hello guys,

new OSTC, V1.30, TX14/34, deep 53m...
After 10 minutes, I get a Decocum of 96 min.... + unbeleavable deco stop....
30 minutes after the dive, the OSTC seems to be better, with a saturation time of abour 5 jours.
But, on the screen, you can see a peak for Helium, just one.
A friend of mine was with me. His OSTC (v1.29) had the same problem (decosum of 99 minutes).
He had the same peak of Helium BUT the gas selected was AIR.....
Strange thing...

What do we have to do ?

Re: 1.29 bug

Posted: 22 Mar 2009, 19:12
by Marou
I had the same problem today
OSTC V1.29, TX18/38 deep 36,6m, CC with GF30/70, SP 1.2, dive time 72min
After 40 min I had a decosum of 99 min and unbeleavable deco stop
On the same time on my shearwater I had 12min of decosum

After during the dive I didn't care to much the OSTC.

On surface it seems better, also a big peak of helium, after some minutes.

Re: 1.29 bug

Posted: 22 Mar 2009, 21:32
by Bech
I also had a small problem last week (first dive with my OSTC) a set it to GF 20/65 with a Tx 20/30 CCR dive.

At 13m after 2 minutes it gaves me 6 min at 3 meters stop !!!

I made 3 other dives since that moment with pure bulhman and had no problem.


Does someone know how to see de GF during the dive while going up in order to be able to follow it ?

Raph

Re: 1.29 bug

Posted: 23 Mar 2009, 09:48
by heinrichsweikamp
Hello,

We got a logbook file and replaying this dive in the simulator right now - thanks.

regards,
Matthias

Re: 1.29 bug

Posted: 23 Mar 2009, 10:19
by corona_citron
is that mine ?
Can tou reproduce the problem ?