forum.heinrichsweikamp.com

Hallo,

Die neue 1.22 stable ist jetzt verf?gbar - damit kommen nach 2 Monaten auch die Benutzer der Stable versionen in den Genuss der neuen Funktionen.

http://www.heinrichsweikamp.net/ostc/de ... 750ABB.htm

The new 1.22 stable is now available - users of the stable releases waited two months to have access to the new functions.

http://www.heinrichsweikamp.net/ostc/en ... 750ABB.htm


Regards,
Matthias Heinrichs

I saw something strange tonight...

for the 5 last minutes (after the deco-stops end)in 3-4m of water,4 or 5 times, the no-deco indcation get from 160 to 0 and finish to stay on 0...until the surface mode...

did I forget to set something after to last update (from 1.21 to 1.22) ?

actual setting are:
L16-GF (30-80)
last stop on 6m

the other parameters are on default values

Hello,

I will test this during a dive today. I think the leading tissue changed several times during the ascend.

Regards,
Matthias

nur eine kleine Frage:

ist es normal dass die "Desat" Zeit ist k?rzer als die "no-Fly" Zeit ist??

Hallo Nicolas,

Kannst Du mal schreiben was f?r Tauchg?nge mit welchen Gasen Du da gemacht hast?

Gruss,
Matthias

Tief. 70
Dauern. 47
Gas:Tx 19/30, Nx 32 Nx 70
[IMG]http://img219.imageshack.us/img219/5263/profil689mp3.th.jpg[/IMG][IMG]http://img219.imageshack.us/images/thpix.gif[/IMG]

Hi Matthias,

Wenn I open the ostc_part2 workspace, a file named p2_deco_main_c_v105.c is included in the workspace althought the file in the source is p2_deco_main_c_v104.c, if i replace the 105 by the 104 it works fine but i just wanted to make sure that by doing that i really have version 1.22 and not an intermediary release.
Best Regards

Sebastien Kister

Hello,

p2_deco_main_c_v104.c is the latest stable. I will update the sourcecode package. 105 is a beta.

Regards,
Matthias

Hello Nicolas,

nicolas schreyer Wrote:
> Gas:Tx 19/30, Nx 32 Nx 70

We run hundreds of such dives in the simulator, Are you really sure that the NoFly-Time was bigger then the total Desat. time? I'm afraid I can't see any issue causing this effect.

Regards,
Matthias

- Running the computer with the simulator I get strange results when I try "Reset Deco data" the computer is logging 96m.

- Is it normal that the deco display (sum) only shows up to 99 minutes? Tried a dive to 100m for 15 minutes

- The behaviour of the Deco table in the OSTC is strange, a random number of stops shows 0 minutes while stops mor deep or more shallow shows the real numbers... I will try to get a profile to You and some photos asap.

andersnasman Wrote:
> - Running the computer with the simulator I get
> strange results when I try "Reset Deco data" the
> computer is logging 96m.

Deco data can only be reseted in surface mode, not during the (simulated) dive.

> - Is it normal that the deco display (sum) only
> shows up to 99 minutes? Tried a dive to 100m for
> 15 minutes
Yes.

> - The behaviour of the Deco table in the OSTC is
> strange, a random number of stops shows 0 minutes
> while stops mor deep or more shallow shows the

Right now, the GF deco model calculates the actual deep stops based on the current saturation situation and so specific stops may not be required in terms of tissue saturation but are displayed with 0 minutes as a recommended deep stop.

regards,
Matthias

Hello,

I still have problem with my logbook. I can't see the profile of the last dive... With the others ther is no problem.

And I can't see them with Jdivelog. But no problem with divinglog...

Yesterday no problem.
Today the battery led is blinking without the USB plug.
And now the profile is out...

Regards

Servan

Hello,

Blinking battery symbol in surface or divemode means weak battery.

Regards,
Matthias

heinrichsweikamp Wrote:
-------------------------------------------------------
>Blinking battery symbol in surface or divemode
> means weak battery.

Hello Matthias,

Thanks for your answer, but the battery symbol is full and the voltage is 4.18V

Regards
Servan

Hello,

1.18 does not blink and still show the profile without troubles?

regards,
Matthias

Hello,

1.18 is not bugging, but shows profile with problem

[img]http://nsa03.casimages.com/img/2008/12/18/mini_081218101407699717.jpg[/img]

I'll say later if the battery Led is blinking.

Thank you

Regards
Servan

servan Wrote:
-------------------------------------------------------
> I'll say later if the battery Led is blinking.

I confirm, the led is not blinking with 1.18

Servan

servan Wrote:
> I confirm, the led is not blinking with 1.18

Really strange. Is anybody experiencing this problem, too?

Maybe you can test again with the 1.23 (Just released)? As for your logbook problem: Best think you can do is a "Delete all", this will re-format the entire profile memory area.

regards,
Matthias

Hello,

heinrichsweikamp Wrote:
-------------------------------------------------------
> Maybe you can test again with the 1.23 (Just
> released)? As for your logbook problem: Best think
> you can do is a "Delete all", this will re-format
> the entire profile memory area.

With 1.22 : the Led blink twice for 4.14V and more
With 1.18 : no blink for the same voltage


OK I delete all the logbook. The problem appears after using the JDIVELOG transfert protocol ...

Regards
Servan

Hello,

JDiveLog does not have direct access to the profile memory, so this is most likely not the problem.

Regards,
Matthias

Hello,

I remember settings I've changed before the problem appears.

I've changed CF20 ; CF21 ; CF22
My values :
* CF20 = 1
* CF21 = 60
* CF22 = 10

Can it be the source of the problem ?

Regards
Servan