100m and OSTC behaviour
100m and OSTC behaviour
Hi,
A friend (Corona) was 100 m deeper with the OSTC (102 m). From his description of the OSTC behaviour, I am a bit surprised how the OSTC was programmed. At 100 m the computer stop everything with a message like: you are too deep I stop. He had to reset it after the dive, to make the computer alive.
Ok, we know that the computer is not made to go under 100 m and we were aware when we bought it. But why makes it crash under 100 m? Most of the computer display at least the depth and some still continue to make deco calculation with a message of alert.
Would it not be possible to modify the behaviour of the OSTC under 100 m?
Regards,
Antoine
A friend (Corona) was 100 m deeper with the OSTC (102 m). From his description of the OSTC behaviour, I am a bit surprised how the OSTC was programmed. At 100 m the computer stop everything with a message like: you are too deep I stop. He had to reset it after the dive, to make the computer alive.
Ok, we know that the computer is not made to go under 100 m and we were aware when we bought it. But why makes it crash under 100 m? Most of the computer display at least the depth and some still continue to make deco calculation with a message of alert.
Would it not be possible to modify the behaviour of the OSTC under 100 m?
Regards,
Antoine
Re: 100m and OSTC behaviour
I agree on that.
certainly when only 2m are exceeded the maximum limit
Just show a warning and for the rest, let the ostc work normaly untill the housing breaks :p
it would also be nice to come up with a new housing and buttons to raise the max depth.
certainly when only 2m are exceeded the maximum limit
Just show a warning and for the rest, let the ostc work normaly untill the housing breaks :p
it would also be nice to come up with a new housing and buttons to raise the max depth.
Steve
CMAS 2* Instructor
CMAS Advanced Nitrox Instructor
Belgium
CMAS 2* Instructor
CMAS Advanced Nitrox Instructor
Belgium
-
- Posts: 4383
- Joined: Sunday 13. May 2007, 18:07
Re: 100m and OSTC behaviour
Hello,
With the new depth font the OSTC can not display depths>100m. We've written this quite often: Do not use the OSTC for such dives! It was never intend to be used below 100m! Maybe, there will be an OSTC for deeper dives somedays.
Regards,
Matthias
With the new depth font the OSTC can not display depths>100m. We've written this quite often: Do not use the OSTC for such dives! It was never intend to be used below 100m! Maybe, there will be an OSTC for deeper dives somedays.
Regards,
Matthias
Re: 100m and OSTC behaviour
heinrichsweikamp Wrote:
-------------------------------------------------------
> Hello,
>
> With the new depth font the OSTC can not display
> depths>100m. We've written this quite often: Do
> not use the OSTC for such dives! It was never
> intend to be used below 100m! Maybe, there will be
> an OSTC for deeper dives somedays.
>
> Regards,
> Matthias
Matthias,
I full understand that it should not be used under 100 m but I do not understand why it should freeze.
-------------------------------------------------------
> Hello,
>
> With the new depth font the OSTC can not display
> depths>100m. We've written this quite often: Do
> not use the OSTC for such dives! It was never
> intend to be used below 100m! Maybe, there will be
> an OSTC for deeper dives somedays.
>
> Regards,
> Matthias
Matthias,
I full understand that it should not be used under 100 m but I do not understand why it should freeze.
Re: 100m and OSTC behaviour
That must be a new software feature what i really dislike a lot ! ! !
With an older software version i used to dive to 115 meter with no such a behaviour at all.
If this is tru i will switch back to an older software-version.
There should be at least a 10% tolerance margin!
With an older software version i used to dive to 115 meter with no such a behaviour at all.
If this is tru i will switch back to an older software-version.
There should be at least a 10% tolerance margin!
Re: 100m and OSTC behaviour
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.
Re: 100m and OSTC behaviour
heinrichsweikamp Wrote:
-------------------------------------------------------
> Hello,
>
> With the new depth font the OSTC can not display
> depths>100m. We've written this quite often: Do
> not use the OSTC for such dives! It was never
> intend to be used below 100m! Maybe, there will be
> an OSTC for deeper dives somedays.
>
> Regards,
> Matthias
It is not safe to implement a feature which locks out a diver from its electronics while in use, possibly at the worst possible time (i.e. when max. depth is exceeded which could happen if BCD fails or helping a buddy...).
It is not safe to do so without informing clearly the diver beforehand of the existence of this feature.
May I aks for this feature to be removed and what other similar features have been implemented without warning or prior information to the user?
-------------------------------------------------------
> Hello,
>
> With the new depth font the OSTC can not display
> depths>100m. We've written this quite often: Do
> not use the OSTC for such dives! It was never
> intend to be used below 100m! Maybe, there will be
> an OSTC for deeper dives somedays.
>
> Regards,
> Matthias
It is not safe to implement a feature which locks out a diver from its electronics while in use, possibly at the worst possible time (i.e. when max. depth is exceeded which could happen if BCD fails or helping a buddy...).
It is not safe to do so without informing clearly the diver beforehand of the existence of this feature.
May I aks for this feature to be removed and what other similar features have been implemented without warning or prior information to the user?
Re: 100m and OSTC behaviour
I do not always agree with the fan but this time i completly agree ! ! !
-
- Posts: 18
- Joined: Tuesday 14. April 2009, 14:53
Re: 100m and OSTC behaviour
I also fully agree with OSTCfan.
If the only issue is about the font then for gods sake just omit
the 1 (display depth % 100).
Regards,
Vincent
If the only issue is about the font then for gods sake just omit
the 1 (display depth % 100).
Regards,
Vincent
-
- Posts: 4383
- Joined: Sunday 13. May 2007, 18:07
Re: 100m and OSTC behaviour
Hi all,
Unfortunately, we still do not know if there was an error code or if it was an undocumented error (a.k.a. bug) during this dive. So please calm down a bit, thanks.
So we can only guess and I think the error routine took over (by mistake) because it though the contact to the pressure sensor was lost. There is no intend lock-out for any mode in the OSTC, so for all of you warranty breakers I've attached a 1.42beta which will work fine up to 120m and I'll make sure that this will be in the future releases, as well.
Cheers,
Matthias
Unfortunately, we still do not know if there was an error code or if it was an undocumented error (a.k.a. bug) during this dive. So please calm down a bit, thanks.
So we can only guess and I think the error routine took over (by mistake) because it though the contact to the pressure sensor was lost. There is no intend lock-out for any mode in the OSTC, so for all of you warranty breakers I've attached a 1.42beta which will work fine up to 120m and I'll make sure that this will be in the future releases, as well.
Cheers,
Matthias
Re: 100m and OSTC behaviour
Is the OSTC now stable below 100m +- some percent in the latest firmware 1.40 or was there just a part time solution?
-
- Posts: 4383
- Joined: Sunday 13. May 2007, 18:07
Re: 100m and OSTC behaviour
Hello Markus,
The OSTC does not display depth below 100m and additionally the 1.40 will not even work below 100m! If want to go deeper I strongly recommend the 1.44beta. We also recommend not to use the OSTC for such dives...
regards,
Matthias
The OSTC does not display depth below 100m and additionally the 1.40 will not even work below 100m! If want to go deeper I strongly recommend the 1.44beta. We also recommend not to use the OSTC for such dives...
regards,
Matthias