forum.heinrichsweikamp.com

The pressure sensor of my OSTC 2N 2133 seems to be a little unreliable the last week. I'm using firmware version 2.21. I'll try to describe the problem as good as possible :).

Whenever the pressure is increased, the reading seems to be ok. The depth seems to be right, and the OSTC reacts 'fast ...

Hi,

I got something rather 'unexpected' going on with the desaturation time: it's dropping faster than 'real time'. If I do my last dive in the evening, ending with a desat time of about 25-30 hours, the next day, when I wake up, desat time is decreased to 0 - and I don't sleep 25 hours/night ...

Did you check the other thread:
http://www.heinrichsweikamp.com/read.php?2,1674
It might be an issue because your dive is >100m deep, I suppose, dunno?

Well, I agree on that, but remember, if you have a tolerance of 10%, somebody one day may dive to 112m, and say: I exceeded the tolerance margin by only 2m, we should have a tolerance of 15% etc etc :p. But yes, I agree it would be better if the OSTC doesn't 'break' when you go >100m.

I use MV-plan too, and recently I asked them to implement the factor for faster compression and slower decompression too (as it is with the ostc). It seems Guy Wittig is willingly to add that feature, which would match the model used in the ostc... Only one question: for ascending and descending ...

Hey Steve,
Thanks for the reply, but I suppose temperture measurement should be right, no matter if you're diving in salt water or not :p. Anyway, the temperature thing remains a small issue, but I don't bother that much.
Greetz, ks

Reading the forum again, I realize that the time issue might be solved in next firmware versions (1.30 or higher)?
Well, in that case, the temperature issue is the remaining one...

If you're still waiting for others in favor of the ostc: me!
I've had a few computers so far (not that many, but still), and the ostc is still my favourite by far:
1/ free and resent software on the ostc as well as on your pc (also freeware, if you want, like jdivelog) at anytime
2/ possibility for ...

I have some small issues with the ostc, which now I'm very sure they the wrong values:
1/ The temperature given is always too high, about 3-5 degrees. I'm very sure about this, since all other computers give lower temperatures, and also biologically it doesn't fit - every year, there are sepia's in ...

Hey all, just wondering, and this question is probably already asked some time ago, but are there plans to capture tank pressure data in any way (probably wireless)? And if so, is this a long- or short-term plan...?
Kurt

Hey Peter,
Ik woon in Brugge en heb een ostc (en ben daar uiterst tevreden van) en gebruik jdivelog als electronisch logboek. Je mag het gerust eens komen bekijken... of als ik in de komende maanden nog eens ga duiken (zeker eens in Nemo33), dan kun je't ook onder water zien.
Kurt

Very quick, simple question: has the protocol for the dive profiles changed? Since I upgraded to v1.15, I can't import the dives into jdivelog (I can, however, read and save the settings).
thx, Kurt

Hey Matthias,

I suppose adding a note to say not to switch on during flight (or during landing) will solve the problem. It is logic that it happens, since pressure increases quite fast from about 750 mbar to about 1000 mbar during landing. The minimum CF0 treshold to avoid this would be more than ...

Hey,

Returning from work/holiday, I was bored and playing a little with the ostc (checking logbook etc). The plane started to land, and the ostc went in dive mode. Now, since I couldn't ask the pilot to go up and depressurize the cabin a little bit for a few minutes, the ostc is in dive mode ever ...

This has something to do with upgrading and wrong place of end of dive pointers... See forum jdivelog for more information

I thought the problem was solved by deleting all the dives, but this is not true :). I have problems to read the dives from the computer. Current firmware version is 1.08 - according to jdivelog, it can read the protocol up to v1.08. I simulated some dives with jdivelog, which works perfectly with ...

see 'import/clear memory?'-thread.
Kurt

Hey Matthias,
Well, it seems that indeed, the old format of the test dives was the problem. I can read the new (simulated) dives without any problem, using firmware v1.14 or v1.08. Doesn't matter, it works now, I'm happy :p.
Logbook in general - not only the delete option - is rather slow to my ...

Hey all,
well, just in case it is important to someone: I was working with v1.08 (since I was diving with the computer). There was no way of clearing the memory, at least to my knowledge :), so I upgraded to v1.14. I started deleting the simulated dives, since I thought there might have been an ...

Hi all,
When I check my logbook in the ostc, I see the five dives done so far: 2 tests performed by HeinrichsWeikamp, 1 simulated dive with jdivelog and 2 'real' dives. However, when I import the dives on my computer (in jdivelog), only the first two dives are recognized. Apparently, there is ...

Hi,
I tested the computer this weekend. When I want to import the data in jdivelog, it doesn't seem to work. On the ostc, I can see 5 dives (2 test dives from HeinrichsWeikamp, 1 simulated dive in jdivelog and 2 real dives). When I put 'import' in jdivelog, only the two test dives from ...

Hey,
I recieved the OSTC this week and I've been testing some basic stuff right now. So far, I like it :) although I have two questions... I use jdivelog and I'm running the stable version of the firmware (v1.08) on the OSTC.
For some reason, I can load the settings of the computer in JDiveLog, but ...

Hi,
I was wondering, does the computer go in errormode in some cases? I'm refering to things like skipping a decostop, surfacing without the necessary stops etc. How does the computer react on this? Error mode, longer stops, or just all kinds of alarm until you go back to the decostop you have to ...

Hey,

That clears that bit up... And I agree about the deep stop-priority. There might be a lot of questions about deep stops, but that's for another thread, another time .

Thanks,
Kurt

Hi all,
The ostc firmware doesn't inlude (the possibility) to add a safety stop (which can be skipped), as far as I know. Would it make sense to add this to the firmware? It would probably need 2 more custom functions (depth and time of the safety stop), so I wonder if it makes sense to 'sacrifice ...