hwOS for OSTC3, cR and OSTC 2: 1.85 beta
-
- Posts: 4446
- Joined: Sunday 13. May 2007, 18:07
hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Hello,
Attached to this post is the new 1.85 beta with some new features for testers:
New since the last stable:
CHANGE: change button sensitivity range and default (OSTC2)
NEW: MOD Warning (Can be disabled)
NEW: Depth dependent ascend speed (Can be disabled)
NEW: Graphical speed indicator (Can be disabled)
NEW: Option to always show the ppO2, shows ppO2 for Diluent in CC mode
NEW: Mode Auto SP: Automatically switches the SP during descent (CC Mode)
NEW: Deco planer computes gas consumption for all gases and can compute bailout plans for CC modes
New since the last beta:
BUGFIX: Rotate button sensitivity with screen (OSTC 2 and cR)
CHANGE: GF and aGF high range increased to 45-110%
NEW: New option to download "Compact Headers". Improved BLE support (OSTC 2 and OSTC 3+)
NEW: Quit Simulator automatically when starting a real dive
BUGFIX: Auto-Brightness clipped to lowest settings in bright sunlight on some devices
CHANGE: Auto SP now available on OSTC 2
Please use only in the simulator or when carrying a backup computer during diving.
Downgrading to the 1.81 is, as always, possible and will not corrupt any settings or logbook data.
regards,
Matthias
Attached to this post is the new 1.85 beta with some new features for testers:
New since the last stable:
CHANGE: change button sensitivity range and default (OSTC2)
NEW: MOD Warning (Can be disabled)
NEW: Depth dependent ascend speed (Can be disabled)
NEW: Graphical speed indicator (Can be disabled)
NEW: Option to always show the ppO2, shows ppO2 for Diluent in CC mode
NEW: Mode Auto SP: Automatically switches the SP during descent (CC Mode)
NEW: Deco planer computes gas consumption for all gases and can compute bailout plans for CC modes
New since the last beta:
BUGFIX: Rotate button sensitivity with screen (OSTC 2 and cR)
CHANGE: GF and aGF high range increased to 45-110%
NEW: New option to download "Compact Headers". Improved BLE support (OSTC 2 and OSTC 3+)
NEW: Quit Simulator automatically when starting a real dive
BUGFIX: Auto-Brightness clipped to lowest settings in bright sunlight on some devices
CHANGE: Auto SP now available on OSTC 2
Please use only in the simulator or when carrying a backup computer during diving.
Downgrading to the 1.81 is, as always, possible and will not corrupt any settings or logbook data.
regards,
Matthias
-
- Posts: 4446
- Joined: Sunday 13. May 2007, 18:07
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
P.S.:
The new stable (1.86, most likely) will be released beginning of next week.
Die neue Stable (voraussichtlich 1.86) wird Anfang nächster Woche veröffentlicht.
Gruß,
Matthias
The new stable (1.86, most likely) will be released beginning of next week.
Die neue Stable (voraussichtlich 1.86) wird Anfang nächster Woche veröffentlicht.
Gruß,
Matthias
- ClaudeDive
- Posts: 206
- Joined: Friday 27. September 2013, 12:50
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Matthias,
[left][/left]
Translation, English / French new parameters 1.85 beta
[left][/left]
Menu Déco >
[left][/left]
"Menu ppO2" = "Menu pO2"
[left][/left]
Simulateur > Réglages >
[left][/left]
"Bottom Gas" = "Gaz Fond"
[left][/left]
"Deco Gas" = "Gaz Déco"
[left][/left]
Simulateur > Start Simulateur >
[left][/left]
"Ceiling" = "Prof.Plafond" or "Plafond"
[left][/left]
"ppO2 = "pO2"
[left][/left]
Regards,
[left][/left]
[left][/left]
Translation, English / French new parameters 1.85 beta
[left][/left]
Menu Déco >
[left][/left]
"Menu ppO2" = "Menu pO2"
[left][/left]
Simulateur > Réglages >
[left][/left]
"Bottom Gas" = "Gaz Fond"
[left][/left]
"Deco Gas" = "Gaz Déco"
[left][/left]
Simulateur > Start Simulateur >
[left][/left]
"Ceiling" = "Prof.Plafond" or "Plafond"
[left][/left]
"ppO2 = "pO2"
[left][/left]
Regards,
[left][/left]
Cheers
ClaudeDive ><)))))°> OSTC3 #2430 <°(((((><

ClaudeDive ><)))))°> OSTC3 #2430 <°(((((><
-
- Posts: 4446
- Joined: Sunday 13. May 2007, 18:07
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Hi,
Thanks, I updated the texts. "Ceiling" wasn't translated for a reason.
Btw. We still need some Italian translations (See attached file)...
Regards,
Matthias
Thanks, I updated the texts. "Ceiling" wasn't translated for a reason.
Btw. We still need some Italian translations (See attached file)...
Regards,
Matthias
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
ClaudeDive Wrote:
-------------------------------------------------------
> Menu Déco >
> "Menu ppO2" = "Menu pO2"
>
> Simulateur > Start Simulateur >
> "ppO2 = "pO2"
Hi Claude,
One question : why do you want to change "pp02" by "p02" ? In French, we use as in the other language "pp02" for the oxygen partial pressure ( "pression partielle" ).
Thanks
Yoann
-------------------------------------------------------
> Menu Déco >
> "Menu ppO2" = "Menu pO2"
>
> Simulateur > Start Simulateur >
> "ppO2 = "pO2"
Hi Claude,
One question : why do you want to change "pp02" by "p02" ? In French, we use as in the other language "pp02" for the oxygen partial pressure ( "pression partielle" ).
Thanks
Yoann
- ClaudeDive
- Posts: 206
- Joined: Friday 27. September 2013, 12:50
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Hi,
[left][/left]
Simply because in sientific and medical documents the O2 pressure is noted pO2 and not ppO2,
[left][/left]
If O2 is a gas alone the oxygen pressure is noted : pO2,the oxygen pressure is necessarily equal to the total pressure, oxygen pressure can not be partial,
[left][/left]
If the O2 is included in a mixture, the oxygen pressure is necessarily part facing to the total pressure of the mixture, it is noted pO2
[left][/left]
Regards,
[left][/left]
[left][/left]
Simply because in sientific and medical documents the O2 pressure is noted pO2 and not ppO2,
[left][/left]
If O2 is a gas alone the oxygen pressure is noted : pO2,the oxygen pressure is necessarily equal to the total pressure, oxygen pressure can not be partial,
[left][/left]
If the O2 is included in a mixture, the oxygen pressure is necessarily part facing to the total pressure of the mixture, it is noted pO2
[left][/left]
Regards,
[left][/left]
Cheers
ClaudeDive ><)))))°> OSTC3 #2430 <°(((((><

ClaudeDive ><)))))°> OSTC3 #2430 <°(((((><
-
- Posts: 4446
- Joined: Sunday 13. May 2007, 18:07
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
I assume the French divers use ppO2 just as everyone else does (Even if this may be scientifically incorrect). My french is a bit rusty but I have this (very nice) book from Frank Vasseur here:
[img]file.php?6,file=739,filename=Resize_of_ ... .47.11.jpg[/img]
There's always "ppO2" as far as I can see.
regards,
Matthias
[img]file.php?6,file=739,filename=Resize_of_ ... .47.11.jpg[/img]
There's always "ppO2" as far as I can see.
regards,
Matthias
- ClaudeDive
- Posts: 206
- Joined: Friday 27. September 2013, 12:50
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
It's true the French divers use ppO2, but that does not make it true!
[left][/left]
The partial pressure pO2 is part of a naming convention of measuring units that is made for scientific, medical, and physiology and even for French and foreign divers to everyone speaks the same language ...
[left][/left]
It's to the diver to use the notations of physiology, but certainly not the physiologist to speak language of the diver to talk about physiology,
[left][/left]
One can continue to use an incorrect notation which does not promote communication between divers and physiologists ...
We can also attempt to change the language of the French diver and abroad to use conventional notation as pO2,
[left][/left]
http://www.smart-doc.org/modules.php?op ... 396d3fe4cb
[left][/left]
Regards,
[left][/left]
[left][/left]
The partial pressure pO2 is part of a naming convention of measuring units that is made for scientific, medical, and physiology and even for French and foreign divers to everyone speaks the same language ...
[left][/left]
It's to the diver to use the notations of physiology, but certainly not the physiologist to speak language of the diver to talk about physiology,
[left][/left]
One can continue to use an incorrect notation which does not promote communication between divers and physiologists ...
We can also attempt to change the language of the French diver and abroad to use conventional notation as pO2,
[left][/left]
http://www.smart-doc.org/modules.php?op ... 396d3fe4cb
[left][/left]
Regards,
[left][/left]
Cheers
ClaudeDive ><)))))°> OSTC3 #2430 <°(((((><

ClaudeDive ><)))))°> OSTC3 #2430 <°(((((><
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Hi Claude,
I understand your point of view and if you want to be absolutely precise, we should write "PO2" and not "p02".
Regards
Yoann.
I understand your point of view and if you want to be absolutely precise, we should write "PO2" and not "p02".
Regards
Yoann.
-
- Posts: 4446
- Joined: Sunday 13. May 2007, 18:07
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Hi,
Another (very recommended) book:
[img]file.php?6,file=740,filename=Resize_of_ ... .17.28.jpg[/img]
No PO2, always ppO2... Don't you think it's better to use the terms divers use? "ppO2" as the abbreviation for "partial pressure Oxygen" is not wrong.
Regards,
Matthias
Another (very recommended) book:
[img]file.php?6,file=740,filename=Resize_of_ ... .17.28.jpg[/img]
No PO2, always ppO2... Don't you think it's better to use the terms divers use? "ppO2" as the abbreviation for "partial pressure Oxygen" is not wrong.
Regards,
Matthias
- ClaudeDive
- Posts: 206
- Joined: Friday 27. September 2013, 12:50
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Hi,
[center][/center]
The partial pressure O2 breathed is a term from physics and used in physiology, it notes pO2 or PO2 following the standards of measurement units,
[center][/center]
Jean Claude Péchon world-renowned French scientific has already reported error diving literature using ppO2,
[center][/center]
http://www.ffessm78.fr/provisoire/Tout_ ... ession.pdf]
[center][/center]
The diving literature is not THE reference in terms of scoring utlisation units of measurement,
[center][/center]
But it's entirely possible to continue using an incorrect notation in the field of literature or dive computers,
[center][/center]
But the use of a single language for all is also a way of progress,
[center][/center]
Regards
[center][/center]
[center][/center]
The partial pressure O2 breathed is a term from physics and used in physiology, it notes pO2 or PO2 following the standards of measurement units,
[center][/center]
Jean Claude Péchon world-renowned French scientific has already reported error diving literature using ppO2,
[center][/center]
http://www.ffessm78.fr/provisoire/Tout_ ... ession.pdf]
[center][/center]
The diving literature is not THE reference in terms of scoring utlisation units of measurement,
[center][/center]
But it's entirely possible to continue using an incorrect notation in the field of literature or dive computers,
[center][/center]
But the use of a single language for all is also a way of progress,
[center][/center]
Regards
[center][/center]
Cheers
ClaudeDive ><)))))°> OSTC3 #2430 <°(((((><

ClaudeDive ><)))))°> OSTC3 #2430 <°(((((><
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Hi,
I don't know if OSTC would like to be a pioneer reforming the divers' language or to be more scientific than the what diving requires. I would expect this from the well-known, international diving associations and organizations.
...but - do these terms from the physics or other areas actually help? Wouldn't it be more confusing? What about using an acronym instead of abbreviation?
E.g. when you say "partial pressure of Oxygen" the abbreviation would be - based on your discussion - pO2 or PO2. Isn't it confusing? - like the PO2 is just P-O2 aka Phosphorus-Oxygen2? Wouldn't it be better to use the ppO2 acronym instead of the pO2/PO2 abbreviation? The acronym can't be mixed up with Phosphorus-Oxygen2.
If we accept to use ppO2, it will be - by accident (actually by the common core of the languages) - the same as in English which makes even easier for others to understand your display when really required.
If you check other national study books they also use ppO2 independently from how the local language would write it - intentionally as divers should speak the same diver's language.
The other example how the terms from diving differ from the scientific values is the Air. When we set Air on a diving computer we set 21% O2 and 79% N2, but in real it would be only 78% N2 and 1% others.
In short: I can accept pO2 as abbreviation (not PO2, it's confusing) but I think the ppO2 acronym is much better.
Regards, Janos. /neither a philologist nor a scientist/
I don't know if OSTC would like to be a pioneer reforming the divers' language or to be more scientific than the what diving requires. I would expect this from the well-known, international diving associations and organizations.
...but - do these terms from the physics or other areas actually help? Wouldn't it be more confusing? What about using an acronym instead of abbreviation?
E.g. when you say "partial pressure of Oxygen" the abbreviation would be - based on your discussion - pO2 or PO2. Isn't it confusing? - like the PO2 is just P-O2 aka Phosphorus-Oxygen2? Wouldn't it be better to use the ppO2 acronym instead of the pO2/PO2 abbreviation? The acronym can't be mixed up with Phosphorus-Oxygen2.
If we accept to use ppO2, it will be - by accident (actually by the common core of the languages) - the same as in English which makes even easier for others to understand your display when really required.
If you check other national study books they also use ppO2 independently from how the local language would write it - intentionally as divers should speak the same diver's language.
The other example how the terms from diving differ from the scientific values is the Air. When we set Air on a diving computer we set 21% O2 and 79% N2, but in real it would be only 78% N2 and 1% others.
In short: I can accept pO2 as abbreviation (not PO2, it's confusing) but I think the ppO2 acronym is much better.
Regards, Janos. /neither a philologist nor a scientist/
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Hi Matthias,
thanks for "CCR - Mode Auto SP" for OSTC 2 too.
Please, can You explain how does it works?
Regards,
Boris
thanks for "CCR - Mode Auto SP" for OSTC 2 too.
Please, can You explain how does it works?
Regards,
Boris
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Jak,
I totally agree with you : ppO2 is so much more convenient to use than p02/P02.
I think (but I could be wrong, my chemistry courses are so far behind me...), that Phosphorus-Oxygen 2 doesn't exist in that form. So it's impossible to confuse
I'll let Matthias choose what's better for us
Regards
Yoann
I totally agree with you : ppO2 is so much more convenient to use than p02/P02.
I think (but I could be wrong, my chemistry courses are so far behind me...), that Phosphorus-Oxygen 2 doesn't exist in that form. So it's impossible to confuse
I'll let Matthias choose what's better for us

Regards
Yoann
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Servus,
ich habe gerade mit der 1.85beta ein wenig gespielt.
Was mir aufgefallen ist.
Setpointeinstellungen
0.7 ab 7m
1.6 ab 20m
Ich starte den Simulator auf 12m (flachster möglicher Wert)
gehe tiefer, auf 20m schaltet der Setpoint um.
Starte ich den Simulator auf 30m bleibt der Setpoint auf 0.7.
Vielleicht sollte man beim Simulatorstart prüfen welcher Autosetpoint denn bis zum Erreichen der Starttiefe erreicht wird.
Beim Auftauchen lasse ich den Setpoint 1.6 stehen,
dieser bleibt auch bei 3m Wassertiefe stehen.
Ich hoffe doch das OSTC rechnet dann nicht mit mehr als 100% O2?
In meinem Fall Start bei 900mbar dann wäre auf 3m maximal 1.2 möglich.
Wäre es nicht sinnvoll hier den Setpoint automatisch zurückzunehmen?
Anregung: Es stehen 5 Setpoints zur Verfügung, ich denke man könnte z.B. die Letzten beiden Setpoints im Auto Mode nutzen das sie beim Auftauchen umschalten.
Bsp:
SP1 0.7
Sp2 1.0 10m beim Abtauchen
SP3 1.3 20m beim Abtauchen
SP4 1.0 10m beim Auftauchen
SP5 0.7 7m beim Auftauchen
Dann kann ich den OSTC als Backup im Automatikmodus immer mitlaufen lassen und muss nicht daran denken auch den Backup umzustellen.
Grüße
Rob
Now in English:
I played a bit with the 1.85beta.
Things i recognized:
Setpoint setup
0.7 7m
1.6 20m
I'm Starting the simulator at 12m (shallower not possible)
go deeper, at 20m is a automatic setpoint switch to 1.6. So far so good.
When i'm starting the dive at 30m the Setpoint is still at 0.7.
Maybe you should check at simulation start what setpoint is reached during the virtual descent.
I let the setpoint at 1.6 during ascent.
1.6 is still set at 3m.
I hope OSTC is not calculating with more than 100 percent O2 in this case.
Here, i startet the dive at 900mbar at 3m a maximum setpoint of 1.2 is possible.
Wäre es nicht sinnvoll hier den Setpoint automatisch zurückzunehmen?
Maybe it makes more sense if you reduce the setpoint automatically?
A suggestion: There are 5 setpoints availible, i thint we can use the last two setpoints (4 and 5) in auto mode to switch the setpoint during ascending.
Example:
SP1 0.7
Sp2 1.0 10m at descending
SP3 1.3 20m at descending
SP4 1.0 10m at ascending
SP5 0.7 7m at ascending
Than i can use the OSTC in automatic mode as Backup that runs automatically with my planned setup and i dont have to switch it manually.
Best regards
Rob
ich habe gerade mit der 1.85beta ein wenig gespielt.
Was mir aufgefallen ist.
Setpointeinstellungen
0.7 ab 7m
1.6 ab 20m
Ich starte den Simulator auf 12m (flachster möglicher Wert)
gehe tiefer, auf 20m schaltet der Setpoint um.
Starte ich den Simulator auf 30m bleibt der Setpoint auf 0.7.
Vielleicht sollte man beim Simulatorstart prüfen welcher Autosetpoint denn bis zum Erreichen der Starttiefe erreicht wird.
Beim Auftauchen lasse ich den Setpoint 1.6 stehen,
dieser bleibt auch bei 3m Wassertiefe stehen.
Ich hoffe doch das OSTC rechnet dann nicht mit mehr als 100% O2?
In meinem Fall Start bei 900mbar dann wäre auf 3m maximal 1.2 möglich.
Wäre es nicht sinnvoll hier den Setpoint automatisch zurückzunehmen?
Anregung: Es stehen 5 Setpoints zur Verfügung, ich denke man könnte z.B. die Letzten beiden Setpoints im Auto Mode nutzen das sie beim Auftauchen umschalten.
Bsp:
SP1 0.7
Sp2 1.0 10m beim Abtauchen
SP3 1.3 20m beim Abtauchen
SP4 1.0 10m beim Auftauchen
SP5 0.7 7m beim Auftauchen
Dann kann ich den OSTC als Backup im Automatikmodus immer mitlaufen lassen und muss nicht daran denken auch den Backup umzustellen.
Grüße
Rob
Now in English:
I played a bit with the 1.85beta.
Things i recognized:
Setpoint setup
0.7 7m
1.6 20m
I'm Starting the simulator at 12m (shallower not possible)
go deeper, at 20m is a automatic setpoint switch to 1.6. So far so good.
When i'm starting the dive at 30m the Setpoint is still at 0.7.
Maybe you should check at simulation start what setpoint is reached during the virtual descent.
I let the setpoint at 1.6 during ascent.
1.6 is still set at 3m.
I hope OSTC is not calculating with more than 100 percent O2 in this case.
Here, i startet the dive at 900mbar at 3m a maximum setpoint of 1.2 is possible.
Wäre es nicht sinnvoll hier den Setpoint automatisch zurückzunehmen?
Maybe it makes more sense if you reduce the setpoint automatically?
A suggestion: There are 5 setpoints availible, i thint we can use the last two setpoints (4 and 5) in auto mode to switch the setpoint during ascending.
Example:
SP1 0.7
Sp2 1.0 10m at descending
SP3 1.3 20m at descending
SP4 1.0 10m at ascending
SP5 0.7 7m at ascending
Than i can use the OSTC in automatic mode as Backup that runs automatically with my planned setup and i dont have to switch it manually.
Best regards
Rob
Home: http://www.angermayr.eu
email: ostctools@angermayr.eu
Home of OSTC Tools: http://ostctools.angermayr.eu
HWOSConfig for Android: https://play.google.com/store/apps/details?id=eu.angermayr.hwosconfig
email: ostctools@angermayr.eu
Home of OSTC Tools: http://ostctools.angermayr.eu
HWOSConfig for Android: https://play.google.com/store/apps/details?id=eu.angermayr.hwosconfig
-
- Posts: 4446
- Joined: Sunday 13. May 2007, 18:07
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
steficic Wrote:
-------------------------------------------------------
> Hi Matthias,
>
> thanks for "CCR - Mode Auto SP" for OSTC 2 too.
> Please, can You explain how does it works?
The OSTC switches to the SP2-5 (It starts with SP1) during descent. It switches on the configured depths and only during the descent.
regards,
Matthias
-------------------------------------------------------
> Hi Matthias,
>
> thanks for "CCR - Mode Auto SP" for OSTC 2 too.
> Please, can You explain how does it works?
The OSTC switches to the SP2-5 (It starts with SP1) during descent. It switches on the configured depths and only during the descent.
regards,
Matthias
-
- Posts: 4446
- Joined: Sunday 13. May 2007, 18:07
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Deep_Yo Wrote:
-------------------------------------------------------
> I'll let Matthias choose what's better for us
In the (just released) 1.86 it's pO2 for the French version - but this can be changed again to ppO2. I'm not sure about this yet.
regards,
Matthias
-------------------------------------------------------
> I'll let Matthias choose what's better for us

In the (just released) 1.86 it's pO2 for the French version - but this can be changed again to ppO2. I'm not sure about this yet.
regards,
Matthias
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
Ok. It doesn't really matters in fact.
I think the question was already asked but I didn't find the answer : can you tell us more about the depth dependent speed ?
Thanks.
Regards
I think the question was already asked but I didn't find the answer : can you tell us more about the depth dependent speed ?
Thanks.
Regards
-
- Posts: 4446
- Joined: Sunday 13. May 2007, 18:07
Re: hwOS for OSTC3, cR and OSTC 2: 1.85 beta
When enabled it works like this:
[pre]
; depth(ft): 20 >40 >60 >75 >88 >101 >115 >128 >144 >164
; speed(ft/min): 23 26 29 33 36 43 49 56 59 62 66
; depth(m): 6 >12 >18 >23 >27 >31 >35 >39 >44 >50
; speed(m/min): 7 8 9 10 11 13 15 17 18 19 20 (warning)
; speed(m/min): 5 6 7 8 8 10 12 13 14 15 15 (attention)
[/pre]
Hope that explains it.
regards,
Matthias
[pre]
; depth(ft): 20 >40 >60 >75 >88 >101 >115 >128 >144 >164
; speed(ft/min): 23 26 29 33 36 43 49 56 59 62 66
; depth(m): 6 >12 >18 >23 >27 >31 >35 >39 >44 >50
; speed(m/min): 7 8 9 10 11 13 15 17 18 19 20 (warning)
; speed(m/min): 5 6 7 8 8 10 12 13 14 15 15 (attention)
[/pre]
Hope that explains it.
regards,
Matthias