forum.heinrichsweikamp.com

Teasy Wrote:
-------------------------------------------------------
> Seit der V2.70 ist das ausgelesene Tauch-Profil
> voll Fehler.(td)(td)
> Sowohl bei "MacDive 2" als auch bei "subsurface"

Which macdive and subsurface versions are you using? There are a few OSTC2 bugfixes in libdivecomputer related to the new bailout event, which are not yet included in the latest macdive and subsurface versions. So if you happen to have dives which contain the new bailout event, then parsing will fail. Should be fix in their next release, and I think I already saw some betas too.

If that's not the case, then please send me a memory dump from your ostc. You can do that by downloading the "universal" test tool from the libdivecomputer website, and run it with these arguments:

./universal -n "Heinrichs Weikamp OSTC" -v -l output.log -m output.bin

Then send the generated files to me.

Replace with the correct serial port (e.g. something like /dev/tty.xxx). On Mac you also need to mark the tool as executable with the command "chmod +x universal". You can find some more detailed explanation on the macdive forum.

Hi Teasy,

Teasy Wrote:
-------------------------------------------------------
> Seit der V2.70 ist das ausgelesene Tauch-Profil
> voll Fehler.(td)(td)

Aus deiner Beschreibung entnehme ich das du einen Mac nutzt.
Würdest du mir bitte den binarie Export (wie TnT beschrieben hat) auch zumailen, so das ich die Profile mit der anzeigen in den OSTCTools ausprobieren kann?
Ich habe zwar noch keine Probleme feststellen können, aber bislang nur wenige TG zur Auswertung hier.

Schon mal Danke.

Grüße
Rob

Ist kein Fehler der V 2.70
Das Profil wird im OSTC Tools einwandfrei angezeigt.
Danke an Robert Angermayr für die Telefonische Unterstützung (tu)

Somit kommt die fehlerhafte Anzeige bei MacDive V 2.2.3 & Subsurface 3.0.2 von den Programmen selber.

Von Zeit zu Zeit, vor allem auf Anwenderwünsche hin, müssen wir an der Datenstruktur der Tauchgänge Änderungen vornehmen.

Das dauert dann immer etwas bis die PC-Programmierer nachgezogen haben. Dafür ist das Software-Milieu des OSTC mittlerweile umfangreicher als für jeden anderen Tauchcomputer auf dem Markt.

Gruß,
Matthias

Teasy Wrote:
-------------------------------------------------------
> Ist kein Fehler der V 2.70
> Das Profil wird im OSTC Tools einwandfrei angezeigt.
>
> Somit kommt die fehlerhafte Anzeige bei MacDive V
> 2.2.3 & Subsurface 3.0.2 von den Programmen
> selber.

If you send me the memory dump of your ostc, I can double check whether parsing works using the latest libdivecomputer version. If not, we may still be able to fix before the next subsurface and macdive version.

@ Teasy,

I don't know if your problem is related to v2.70. I will check very soon. I had the same problem lately (v2.50) and I've talked to Nick and he corrected it and put out a beta that you can find on the forum under support.

Hope that helps.

I've just downloaded 5 new dives onto Mac Dive and everything is working well. Profile is good, temperature are back to normal.

Here is the beta you can use : http://www.mac-dive.com/forum/viewtopic.php?f=2&t=1433

Jean-François Wrote:
-------------------------------------------------------
> I've just downloaded 5 new dives onto Mac Dive and
> everything is working well. Profile is good,
> temperature are back to normal.
>
> Here is the beta you can use :
> http://www.mac-dive.com/forum/viewtopic.php?f=2&t=
> 1433

Die beta benutze ich hilft, aber nicht. (td)(td)

Wird der TG im internen Logbuch richtig angezeigt?

Gruß,
Matthias

heinrichsweikamp Wrote:
-------------------------------------------------------
> Wird der TG im internen Logbuch richtig
> angezeigt?
>
> Gruß,
> Matthias

Ja da ist alles OK

In OSTCTools wird es richtig angezeigt.(tu)

In Mac Dive 2.2.3.(letzte Beta) ist es falsch.(td)

Alles nach dem 1. und 2. Gaswechsel stimmt nicht.

NACHTRAG: Subsurface 3.1-11 läuft

Funktioniert es mit Diving Log oder muss ich da auch etwas anpassen?

Schöne Grüße,
Sven

divinglog Wrote:
-------------------------------------------------------
> Funktioniert es mit Diving Log oder muss ich da
> auch etwas anpassen?
>
> Schöne Grüße,
> Sven

Kann ich nicht sagen, verwende eigentlich nur noch meinen MAC, nur zum Test habe ich auf das alte Datengrab PC mit Win98 OSTCTools installiert.

hello
I already wrote another post.
After flashing 2.7, the color of active gaz stay as inactive except for the first gaz.
I compare with another OSTC 2N not flashed and this one works properly.

For simulator it is much more long.
Friend of mine has also trouble after flashing : its simulate only with the first active gaz and do not simulate with the 3 gaz setup.
The color also does not become as "active". (color inactive is pink on mine)

Can somebody check if problems of colors for all active gaz (fewer choice than ostc 2n)

thanks

Hi,

2N and 2C have the exact same firmware (If they are both on 2.7), so
- they compute at the same speed
- they have the same choice of colors
- deactivated gases are shown in the CF64 color

Please, reset your settings to default (Menu -> Reset Menu -> Reset Gas & CF & Deco) and have a look at it again...

Regards,
Matthias

Thanks for your answer.
I check again.
The depth by default was ok but not "changer" (the one just up)
now the colors are correct
and simulator also

Just a little try of the new firmware 2.7 in a 129mt 22' BT, Runtime 221min GF10/100 dive, on a new discovered wreck in Gorgona Island, Livorno, Italy.

Everything worked fine.. except that maybe 10/100 is too aggressive, i was expecting almost 15-20 min more deco.

And as a result, i got some pain in joints and head swinging for some hours after the dive..!!!

Good job with the firmware!

why did you choose GF10/100 instead of 10/75 for example ?
10/100 is very agressive for shallowest stops.
Firmware 2.7 does not require such a setting

Ciro1982811 Wrote:
-------------------------------------------------------
> Just a little try of the new firmware 2.7 in a
> 129mt 22' BT, Runtime 221min GF10/100 dive, on a

The OSTC2 is not intend to be used in this depth.

> Everything worked fine.. except that maybe 10/100
> is too aggressive, i was expecting almost 15-20
> min more deco.
>
> And as a result, i got some pain in joints and
> head swinging for some hours after the dive..!!!

You really should think about your dive plans. And: If you really dive that aggressive, I wouldn't tell anyone online.

There aren't any extra margins in the OSTC, the red CF warning you may have noticed is there for a reason.

Anyway: Have fun diving and add some more safety margin in the future.

Cheers,
Matthias

After a nice week end with a couple of longer and deeper dives using Trimix, air, and nitrox I've encountered no problems with FW 2.70. Everything worked just fine.

Did not download the profiles though.

heinrichsweikamp Wrote:
-------------------------------------------------------
> Ciro1982811 Wrote:
> --------------------------------------------------
> -----
> > Just a little try of the new firmware 2.7 in a
> > 129mt 22' BT, Runtime 221min GF10/100 dive, on
> a
>
> The OSTC2 is not intend to be used in this depth.
>
> > Everything worked fine.. except that maybe
> 10/100
> > is too aggressive, i was expecting almost
> 15-20
> > min more deco.
> >
> > And as a result, i got some pain in joints and
> > head swinging for some hours after the
> dive..!!!
>
> You really should think about your dive plans.
> And: If you really dive that aggressive, I
> wouldn't tell anyone online.
>
> There aren't any extra margins in the OSTC, the
> red CF warning you may have noticed is there for a
> reason.
>
> Anyway: Have fun diving and add some more safety
> margin in the future.
>
> Cheers,
> Matthias

Hi mathias. that was the first time I tried to set GF in that aggressive way, because when i did extremely deep and long dives with 10/90 and with previous firmware, it seemed me that the last oxygen stops at 6 and 3 mtrs was excessively too long compared to previous used softwares.

BUT that last one was the deeper and longest dive i ever made, and this time I had no reference with previous dives.

With 10/100 i think the 36 to 9 mtrs stops was a bit too much aggressive and the oxy stops instead was right (almost 80 minutes). I was feeling right and strong till the end of the dive, so i decided that i was ok and went out of water. Little pains and head swinging begun 10 minutes later and persisted till the night. _I think that this was really near the limit, so next time i'll go back to 10/90 and plan longer dives!! :D

Anyway, here is some photo shots of the dive, excellent visibility, more than 40 mtrs at the bottom!

Gorgona island deep wreck exploration -136 mtrs

Cheers, Ciro.

Ciro1982811 Wrote:

> Anyway, here is some photo shots of the dive,
> excellent visibility, more than 40 mtrs at the
> bottom!
>
> [url=https://www.facebook.com/ciro.osimo/media_set
> ?set=a.10201649879078251.1073741828.1517378023&typ
> e=1]Gorgona island deep wreck exploration -136
> mtrs[/url]
>
> Cheers, Ciro.

Fantastic Dive !!! Outstanding ...
Maybe you should ask Dr. Gardette at COMEX in Marseille for some "better" dive plan than ZHL-16. I think he would provide them on an individual basis.

Update: Just found the time to download the last dives, no problem with FW 2.70 and Diving Log 5.0

No issue U/W either, however max depth was only 55m (:D

Dear All,
well up two weeks I use V.2.7 all is okey ... but logbook... my OSTC switch only last three dive not more ....I don't see dive no 4/no 5/no 6 ... etc. in early version is okey but version 2.7 don't display this info.
Regards
adam

Nice one HW - great work, love the format.. Works for me

Adam Wrote:
-------------------------------------------------------
> Dear All,
> well up two weeks I use V.2.7 all is okey ... but
> logbook... my OSTC switch only last three dive not

As send in email this is related to your very detailed logbook recording settings you mailed us. Increase the sampling time from 2 to 10seconds again.

regards,
Matthias