forum.heinrichsweikamp.com

Hi,

A new 1.94beta was just uploaded for testing.

1) When downgrading again from 1.94 to 1.90 you may loose your dive profiles!
2) After installation of 1.94 the internal logbook will be converted into the new format. This takes about eight minutes and can't be interrupted. (If you already have 1.91, 1.92 or 1.93 installed no conversion is required)

Important new Features/Bugfixes:
BUGFIX: CNS was not cleared with a "Reset Deco"
BUGFIX: Ascend threshold in high altitude mode
CHANGE: Max. depth for simulator now 120m
+Small display changes, typo corrections and power optimizations


Details about the upgrade process: http://www.heinrichsweikamp.com/read.php?2,4071
The link to the firmware: http://www.heinrichsweikamp.com/en/ostc_2n/firmware/

If there are any questions and/or comments, please post them here.

regards,
Matthias

Superb. Thanks guys. Will download later.

Just a note re the CNS calculations in Simulator. The calculation does indeed seem to be made on the bottom time phase of the dive only. I really don't see the point in this. I look for the following info from a dive plan in order of priority:

- total runtime (actually more useful than TTS)
- total CNS%
- detailed stops
- total OTUS

Here's a plan generated by v-planner:

V-Planner 3.89 by Ross Hemingway,
VPM code by Erik C. Baker.

Decompression model: VPM - B

DIVE PLAN
Surface interval = 1 day 0 hr 0 min.
Elevation = 0m
Conservatism = + 2

Dec to 60m (4) Diluent 10/70 0.70 SetPoint, 15m/min descent.
Dec to 99m (6) Diluent 10/70 0.70 SetPoint, 18m/min descent.
Level 99m 24:50 (31) Diluent 10/70 1.30 SetPoint, 17m ead, 24m end
Asc to 78m (33) Diluent 10/70 1.30 SetPoint, -9m/min ascent.
Stop at 78m 0:40 (34) Diluent 10/70 1.30 SetPoint, 11m ead, 20m end
Stop at 75m 1:00 (35) Diluent 10/70 1.30 SetPoint, 10m ead, 19m end
Stop at 72m 1:00 (36) Diluent 10/70 1.30 SetPoint, 9m ead, 18m end
Stop at 69m 1:00 (37) Diluent 10/70 1.30 SetPoint, 9m ead, 18m end
Stop at 66m 1:00 (38) Diluent 10/70 1.30 SetPoint, 8m ead, 17m end
Stop at 63m 1:00 (39) Diluent 10/70 1.30 SetPoint, 7m ead, 16m end
Stop at 60m 1:00 (40) Diluent 10/70 1.30 SetPoint, 6m ead, 16m end
Stop at 57m 2:00 (42) Diluent 10/70 1.30 SetPoint, 5m ead, 15m end
Stop at 54m 1:00 (43) Diluent 10/70 1.30 SetPoint, 4m ead, 14m end
Stop at 51m 2:00 (45) Diluent 10/70 1.30 SetPoint, 3m ead, 14m end
Stop at 48m 3:00 (48) Diluent 10/70 1.30 SetPoint, 3m ead, 13m end
Stop at 45m 2:00 (50) Diluent 10/70 1.30 SetPoint, 2m ead, 12m end
Stop at 42m 3:00 (53) Diluent 10/70 1.30 SetPoint, 1m ead, 12m end
Stop at 39m 3:00 (56) Diluent 10/70 1.30 SetPoint, 0m ead, 11m end
Stop at 36m 4:00 (60) Diluent 10/70 1.30 SetPoint, 0m ead, 10m end
Stop at 33m 4:00 (64) Diluent 10/70 1.30 SetPoint, 0m ead, 10m end
Stop at 30m 5:00 (69) Diluent 10/70 1.30 SetPoint, 0m ead, 9m end
Stop at 27m 6:00 (75) Diluent 10/70 1.30 SetPoint, 0m ead, 8m end
Stop at 24m 6:00 (81) Diluent 10/70 1.30 SetPoint, 0m ead, 8m end
Stop at 21m 8:00 (89) Diluent 10/70 1.30 SetPoint, 0m ead, 7m end
Stop at 18m 9:00 (98) Diluent 10/70 1.30 SetPoint, 0m ead, 6m end
Stop at 15m 13:00 (111) Diluent 10/70 1.30 SetPoint, 0m ead, 6m end
Stop at 12m 14:00 (125) Diluent 10/70 1.30 SetPoint, 0m ead, 5m end
Stop at 9m 20:00 (145) Diluent 10/70 1.30 SetPoint, 0m ead, 4m end
Stop at 6m 73:00 (218) Diluent 10/70 1.30 SetPoint, 0m ead, 4m end
Surface (218) Diluent 10/70 -9m/min ascent.

Off gassing starts at 83.3m

OTU's this dive: 317
CNS Total: 120.1%

DIVE PLAN COMPLETE



I've also attached the output of the same plan from APD Projection. Again total runtime, CNS% and OTUs feature

Hi Matthias,

maybe you can have a quick look at this thread: http://www.heinrichsweikamp.com/read.php?2,5400 !?

I am quite sure there is still a bug regarding the displayed depth. With a salinity setting of 1kg/l, the depth should not be 10m per 1 bar (like it is currently used for calculation within the ostc as you mentioned in the thread above) but 10,2m because you have to take the "Ortsfaktor" of 9,8 (gravity acceleration) into account. As F=m*g that means p=F/A=m*g/A. With a salinity setting of 1.00kg/l that means in a depth of 10m: p=10m*1000kg/m3*9,8m/s2=98000 N/m2= 0.98 bar. This is a 2% error and in my opinion worth correcting it...

Cheers,

Jörn

Hi,

No problem, it's easy to fix. Anyway, his will increase complaints about the OSTC is showing to little depths...

Cheers,
Matthias

"No problem, it's easy to fix. Anyway, his will increase complaints about the OSTC is showing to little depths... "

Why too little depths!? Right now, the OSTC shows for example 30m when measuring 4bar. If you make a correction according to the things I mentioned above, it will show 30.6m when measuring 4bar. You have 0.98bar per 10m fresh water which results in 1.00bar per 10.2m of fresh water. In my opinion, this will at least slightly reduce complaints abot the OSTC showing too little depths
Of course you can feed the OSTC with more exact numbers for the "Ortsfaktor"...

Sure. See this changeset: https://bitbucket.org/heinrichsweikamp/ ... 71d2018e0f

Regards,
Matthias

I noticed a couple of possible issues with the 1.94 beta on my Mk2

1. the unit does not stay in standby for more than a couple of seconds before it pops back into surface mode. It then cycles in and out of standby forever. A reset of all CF´s does not seem to help.

2. after upgrading from 1.92 to 1.94, a red box with CF43 is displayed in the upper right corner, even after a reset of all CF´s. CF 43 is however set to the default value of 13000. When reverting to the default value by selecting the default (which does not change the 13000 value of course) the red box disappears

3. issue #1 still occurs after downgrading to 1.92, which was the previous firmware I used that did not display this error. Another reset of all CF´s within 1.92 fixes the issue and the unit is able to stay in standby mode

4. issue number 4 happens within the simulator using Jdivelog to simulate a dive.
In the specific test the model was OC/GF set to 20/80, all gases air, only one active gas (air of course). All other relevant CF´s at default, no previous saturation and everything was reset.

After a direct descent to 40 meters, the "No stop" counter dropped to 0 minutes quickly, as was to be expected with GF 20/80.
However, the "No stop" seemed stuck at "0" for a duration of at least another 5 minutes, when in fact it should have changed to deco mode quite quickly, obviously in less than a minute.
Once I began the ascent, the display changed to decomode quickly showing stops. However I cannot really tell if the stops made sense or not.

Maybe someone else who still has 1.94 on their Mk2 can try to reproduce #4?

@Matthias: Ich verstehe jetzt irgendwie nicht, was du mit deinem "Sure" meinst!? Das Changeset interpretiere ich so, dass du meinen Vorschlag für die 1.95 beta übernommen hast?

Gruß,

Jörn

"Sure" meinte nur: Sicher, Du hast Recht. bei 0.98bar/10m wird natürlich 2% mehr angezeigt -> weniger Emails

Gruß,
Matthias

nakatomi Wrote:
> 1. the unit does not stay in standby for more than
> a couple of seconds before it pops back into
> surface mode. It then cycles in and out of standby
> forever. A reset of all CF´s does not seem to
> help.

I wonder if something with the update went wrong here. We have installed the 1.94 on about a dozen units for testing and I can't see why the unit don't want to stay in sleepmode. This routine is in use for quite a while now.

regards,
Matthias

smcmullan Wrote:
-------------------------------------------------------
> - total runtime (actually more useful than TTS)

RT=TTS+Bottom time -> TTS is there for historical reasons and I'm not sure if we should change this. Maybe configurable with a CF but personally, I like the TTS more.

> - total CNS%

Sure, this must be fixed.

> - detailed stops

Already there.

> - total OTUS

Not planed, sorry.

regards,
Matthias

heinrichsweikamp Wrote:

> I wonder if something with the update went wrong
> here. We have installed the 1.94 on about a dozen
> units for testing and I can't see why the unit
> don't want to stay in sleepmode. This routine is
> in use for quite a while now.

I flashed the Mk2 twice back and forth for testing, but am not entirely sure if I used your .hex file or one that I compiled myself. I will try it again this evening making sure to use your original file. Also I´ll check if the simulator issue can be reproduced.

Hi Oliver,

I added (Changeset 421) a SAFE_2BYTE_COPY for compatibility after the initial pressure sample but I'm quite sure (Now that I looked into this again) that this is not really necessary.

regards,
Matthias

Hi Matthias,

I installed the original 1.94 beta and the standby issue does not happen today. Also the red CF 43 warning did not appear after updating from 1.92. Maybe it was something else that triggered this yesterday?

However, issue #4 (the simulator "no stop" issue) is definitely happening again. Not every single time, but it does happen.

Right now the OSTC is at 40m, 10 minutes into the dive and shows no deco but still a "No stop" time of 0 (see attached screenshot).

Hi Matthias,

On my OSTC there is strange temperature reading after upgrading to 1.94.
In Battery info Tmax 88.1* (20.07.11)appeared .What could have caused this change?Before the upgrade Tmax was half of the one displayed now.On 20.07. done 2 dives,there the temp is in 27-29* range,and although it's summer in Egypt still the temp is not that high,and I take care not to expose DC to the sun .Flashed 1.94 yesterday night.

Thanks,
Richard

OSTC 385

@ nakatomi:

going to the water,will try air @ 40m to see if your simulator issue will happen there,my GF 10/70.
Cheers,will post later

Richard

OSTC Mk.2 385

Update: in real diving all no stop time went o.k.,after zeroing it went to deco mode without hang,starting with 1min@9m.

nakatomi :

I had noticed once or twice the same #4 issue on the simulator (not using Jdive but directly on the ostc). It remained on 0 for at least 4 or 5 minutes and then showed immediately stopped à 9 meters.

I dived today 43 meters (real dive). It went to deco mode (4m - 4') a short time after 0, as expected.

Guillaume

Hallo,

Ich wusste nicht wo es hinschreiben lol

Vor zwei Tagen habe ich ein Tauchgang in 6m tiefe gemacht, 70 minuten, mein Mk2 war in ZH-L16 CC.

Beim Aufstig hatte ich ein Alarm in Rot >2.55

Déco war naturlich keine da.

Erklärung ?

MFG

Mike

MK mit 1.90 Version

Hi!

Ich hätte einen kleinen Bug-Report für die Version 1.94:

Offensichtlich wird die Entsättigungszeit im Logbuch oder am Startscreen falsch angezeigt/berechnet:

Nach dem gestrigen Tauchgang stehen 28:05 Stunden Entsättigungszeit, Auftauchzeit: 20:29 Uhr. Ich habe dann gestern und noch den Startscreen kontrolliert:

29.7.11 22:40 Uhr:
Flugverbot: 14:43h
Entsättigung: 19:43h

30.7.11 7:49 Uhr (direkt nach dem einschalten):
Flugverbot: 5:32h
Entsättigung: 19:41h

30.7.11 7:50 Uhr:
Flugverbot: 5:32h
Entsättigung: 12:17h

30.7.11 7:51 Uhr:
Flugverbot: 5:31h
Entsättigung: 12:16h

30.7.11 8:06 Uhr:
Flugverbot: 5:21h
Entsättigung: 12:06h

Offensichtlich wird direkt nach dem Einschalten nur das Flugverbot richtig aktualisiert. Die Entsättigungszeit erst nach dem ersten Minutendurchgang.
Weiters sollte ich laut Logbuch erst am 31.7. um 0:34 Uhr entsättigt sein, laut Startscreen aber schon am 30.7. am Nachmittag...

Klaus

Hi Mathias, I've upgrade to 1.94 and I had the same problem as Nakatomi describes.
The unit doesn't stay in sleep mode.

Is there something I can do? or I must downgrade to 1.90?

Thanks

Fulvio

Fulvio Wrote:
-------------------------------------------------------
> Hi Mathias, I've upgrade to 1.94 and I had the
> same problem as Nakatomi describes.
> The unit doesn't stay in sleep mode.

I have just uploaded 1.95beta, do you have the same issue here?

regards,
Matthias

Just uploaded and everything works fine.

Thanks Mathias!