forum.heinrichsweikamp.com

And this troll-boy is working in the belgian train company, so he knows what pretending to work is ;)

I cannot answer in name of Matthias, but I THINK it's just a matter of time and update.
The wiki is "meant" to be of the last firmware and "should" be updated with each update to explain the last modifications.

The versions are following so quickly that it's difficult to keep everything up to date ...

Sorry for the many posts ...

Again, yesterday evening second dive of the day, everything went fine ...

I checked the decodata. dT of Sunday morning is 40s, afternoon 30s, and this morning 60s, while I didn't change any setting in the meanwhile ... ???

From the last dive, the problem is easy to find minute 27 12m:1', minute 28 12m:69' ... bad boy !

Forgot to mention, again a peak of Helium in only 1 compartment.

I dive again this evening, do you want me to try some settings while I'm still not desaturated ?

Well well ... Like Corona Sunday morning had the bug "99 decosum" but can't say really when things began to go wrong.
Second dive everything went fine, nothing to understand ...

I did nothing in the meanwhile, upgrade or nothing, I'm still in 1.29

This morning, Fixed PpO2 1.2, GF 50/90, dil 19/10 ...

Same problem when opening O2 monitor while diving freezes the stuff, had to reset with the interface, and the dive is not logged (did never end in fact I was in the last deco stops)

Yep, that's the way of working of the shearwater pursuit, you still can refuse to change.

Like here the TTS is calculated "as if" all gasses will be used.

Only because you don't stay enough at the bottom ;)
With so little decostops you won't see any difference.

Simulating with MVplan 15minutes at 50meter :

GF 80/80 (I use with air dil) : 1min at 9, 2at6,4at3
GF 30/85 (most used with He dil) : deco starts at 18meter.
If you still want deepers stops ...

Indeed, I found that out it's busy in the meanwhile ...

So, Jdivelog with rx/tx on WinXP did work, I hope this helps for others ?

Do you recommand the use of jdivelog to upgrade, or still the tiny ? Of course the most important is it just works ...

Thanks for the quick answer !
Thierry.

Just the same problem here. Did someone find a solution ?

Tried it on Vista or Xp, restarted several times, tried the original tiny or the "hw powered", standard 9600 baud or 19200 ...

In jdivelog 2.10 I have no port displayed at all ?