OSTC Planner - version 350 for Mac & PC :)

[JeanDo]

Hello,

Just a word: version 350 of OSTC Planner is available on the website.

New features:
* Upgraded to firmware 2.22 (beta), with room for the new CF (CFIII, still unused).
* Embebed the screen copy feature, so you can save images of the computer's screen.
* Added re-sizeable button window, to allow for Mac users with big fonts to view all buttons.
* Plus a few minor improvments and bug fixes.

On PC, the automatic update feature will propose the newest version on the next (connected) run. Mac users have to upgrade by manually downloading the package, and double-click to install.

Enjoy,

[Bardass]

thank you !

[scubatinoo]

Thanks mate!

[Jean-François]

Thanks a lot.

[JeanDo]

There is a new beta version available for Mac users here. Mainly this is a repackage for 10.7 (Lion). It also provides checking for upgrades, and various small bugfixes:

Gas at 0m should not go red when not used.
CF Editor should open on page CFI.
Quit should quit, not just close the main window.
Typos in german translations.
Upgraded to LLVM, Qt 4.8.1, and Qwt 6.0.1. Supports Intel based machines, from MaxOSX 10.5 (Leopard).

Enjoy (:P)

[scubatinoo]

cool, i will try it tonight (:D

[Bardass]

merci, elle fonctionne mieux que la précédente qui plantait

thanks !

[Jean-François]

I'd like to know if there is an iOS or android version in the work or if there ever would be one ?

Sadly I cannot help because I have no programming knowledge

Et merci beaucoup pour la nouvelle version.

[JeanDo]

A new version 371 is online HERE.
- Identical on Mac and PC.
- Upgraded for the latest firmware beta (2.23).
- Includes support for CF64 (inactive gas color).
- Includes automatic check of new version (was missing on Mac).
- Plus minor bug fixes from the 370-mac-only beta.

@Jean-François: yes, I do have an iOS version in mind (tailored for the iPad screen)... It will be done iff I can reuse most of the interface inside iOS.
I plan to start dev this summer.

Also somewhere in the pipeline: firmware upgrades, and dive-profile editor along with the replay-dive feature.


Enjoy.

[scubatinoo]

It becomes an even more exciting peace of software

Just one idea: Rob is doing a very good job in programming OSTC-Software too! Why don't you guys stick together and create "the ultimative OSTC-Software-Suit"? Maybe there are others who can join, not only programmers but designers too...

[Jean-François]

JeanDo Wrote:
-------------------------------------------------------
> @Jean-François: yes, I do have an iOS version in
> mind (tailored for the iPad screen)... It will be
> done iff I can reuse most of the interface inside
> iOS.
> I plan to start dev this summer.
Lovely, Thank you very much.

[swissdiving]

Please Windows8 für Tablet.

[scubatinoo]

Feature Request:

OSTC Planner is using Patm for dive planning. The only Patm i know "out of my head" is 1013 mbar at 0 Meter (=sealevel). So it would be nice to add a "calculation field" where i can enter 933 Meters (above sealevel) and OSTC Planner then calculates the Patm using the barometric formula (see http://en.wikipedia.org/wiki/Barometric_formula).

[JeanDo]

@scubatino:
So it would be nice to add a "calculation field" where i can enter 933 Meters (above sealevel)

Interesting. I added the altimeter, so I should be able to reuse the same formula...

[Vortax]

I have a question: Planning a dive (For example, 60mx30min, Tx 18/40 + EAN50 + O2, GF 30% / 85%), when I hit the "simulate" button, I get this runtime:

0:00 60.0m DESCENT DONE
...
30:04 60.0m Deco:
33 m : 2 ' 35 '
30 m : 2 ' 37 '
27 m : 2 ' 39 '
24 m : 3 ' 43 '
21 m : 3 ' 46 ' (SWITCH Gas#1 -> Gas#2)
18 m : 3 ' 49 '
15 m : 4 ' 54 '
12 m : 7 ' 61 '
9 m : 10 ' 71 '
6 m : 13 ' 84 ' (SWITCH Gas#2 -> Gas#3)
3 m : 27 ' 112 '
0 m : --- ' 113 '
TTS = 83 '
CNS = 44%

Then, I hit the "Gas volume" button, to see the gas needed, Runtime changes to:

30:18 60.0m Deco:
33 m : 2 ' 35 '
30 m : 2 ' 37 '
27 m : 3 ' 40 '
24 m : 3 ' 44 '
21 m : 2 ' 46 ' (SWITCH Gas#1 -> Gas#2)
18 m : 4 ' 50 '
15 m : 4 ' 54 '
12 m : 7 ' 62 '
9 m : 11 ' 73 '
6 m : 13 ' 86 ' (SWITCH Gas#2 -> Gas#3)
3 m : 28 ' 115 '
0 m : --- ' 115 '
TTS = 86 '
CNS = 45%
Depth = 60 m
Bottom time = 30 min
Bottom gas consomation (CF56) = 20 l/min
Ascent gas consomation (CF57) = 20 l/min
Gas#1 ( 18/40) = 5428
Gas#2 ( 50/00) = 1349
Gas#3 (100/00) = 1161


Now, both runtimes have slight differences, as seen:

27m stop changes from 2' to 3'
21m stop changes from 3' to 2'
18m stop changes from 3' to 4'
9m stop changes from 10' to 11'
3m stop changes from 27' to 28'

so, the second runtime is 2' longer, with some variations in deep stops... why? I know 1 minute is not big deal, but I can't understand the reason for this behavior.

Another question: If we take the first runtime, we can see this:
27 m : 3 ' 40 '
24 m : 3 ' 44 '

As far as I know, 40+3=43', not 44'.

Same here:
18 m : 3 ' 49 '
15 m : 4 ' 54 '

49+4=53', not 54'

where this "extra" minutes added came from?

And finally, I think there is a Typo : "gas consomation" shouldn't be "gas consumption"? (OSTC Planner V.3.71 for Mac)

Regards.

[JeanDo]

Hi Vortax,

OSTC Planner is not just a dive planner. It runs the OSTC code and simulate the OSTC underwater behaviour as much as possible.

If you look closely, you will see the first runtime is computed at 30:04, the second at 30:18.
Meaning:

• * The OSTC continuously recompute your decompression. The gas accumulation/off-gasing is done very second. Computing the new runtime takes a little longer, and is dispatched in several cycles. The For small dives it is done every 6 seconds. For bigger ones, it takes longer, and in your example it takes 14 seconds to recmpute a 115' runtime.
  * Everytime you hit the Gas Volume button, OSTC Planner get the new gas configuration, and recompute a new runtime. So you can quickly optimize complex deco configuration.
  * Because it is a new simulation, it adds up the 14 seconds you > at 60m playing with your gas list...

This is a drawback of the strict OSTC simulation approach, and clearly a (minor) bug.

About the runtimes difference, this is a rounding approximation that propagate between stops. At 10m/min, you take 18 seconds between stops. They accumulate, and give a round extra minute every ~ 3 stops.

Regards,

[Vortax]

Thanks JeanDo, I didn't noticed the botton time variation between both runtimes.

It's pretty clear now. Thanks again.
Regards.