New 1.95beta available for the Mk.2/2N

[heinrichsweikamp]

Hi,

The new 1.95beta for the 2N/Mk.2 was just uploaded.

1) When downgrading again from 1.95 to 1.90 you may loose your dive profiles!
2) After installation of 1.95 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 or higher installed no conversion is required)

Important new Features/Bugfixes:
BUGFIX: "Reset all" works again
CHANGE: 0.98bar equal 10m depths with salinity set to 1.00kg/l

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

[O2diver]

Why 0.98bar equal 10m depths with salinity set to 1.00kg/l?? Why not 1.00 bar?

[O2diver]

During the dive computer indicated a maximum depth of 46.6 m. However after downloading the data to the logbook showed 45.72 m. Why?

[Solodiver]

O2diver - how did you download and display the data? Most likely an issue with your diving log app.

I did some (real) dives with 1.95 and love to see the depth is now equal to the one displayed by the Predator. I think we can now bury this endlessly topic!

Thx a lot,
Jan

[tiefunten]

@O2diver: 0.98bar/10m is necessary, because it is the physically correct calculation. You have to take into account the gravity acceleration of 9.81 m/s2.

But there seems to be something wrong if this correct measurement is not shown in the logbook. The difference between 46.6m and your 45.72 is almost exactly the 2% that the 0.98-factor increased the depth.
Can someone else reproduce that, Solodiver perhaps? Unfortunately I can't test this at the moment...

[tiefunten]

@O2diver: you can find an explanation for the 0.98 thing here: http://en.wikipedia.org/wiki/Centimetre_of_water - the german page is much better and includes all the necessary calculations (which are easy to understand as SI-Units are the same in english and german): http://de.wikipedia.org/wiki/Wassers%C3%A4ule

Cheers,

Jörn

[Peter_O]

Hi!

I have just made a couple of dives with this version..
Very nice with the new functions.. future TTS and the other stuff when pressing the right button... ( I haven't upgrade for a while so some of the stuff have probably been around for a while..)

But I didn't like that the bail-out option in rebreather mode is moved to the "submeny setpoint".

So is it possibly to move it to "head meny" in rebreather mode and have it as the first selection?

Best regards from a happy customer..

/Peter

[heinrichsweikamp]

O2diver Wrote:
> of 46.6 m. However after downloading the data to
> the logbook showed 45.72 m. Why?

Good point, the logbook stores pressure not depth. The factor of 0.98 (and the used salinity) were not taken into account for the display.

This has just been fixed.

Regards,
Matthias

[Solodiver]

Today I did a longer and deeper dive using 1.95. In the past (previous firmwares) I was used to see same/very similar values on the MK2 and my predator concerning TTS, GF% and Deco. This time there has been huge differences in all of the mentioned values. I always had lower readings on the MK2 than on the predator differing more than 10min on TTS and 10% on GF%. I did not do double check, but the units shall be configured the same and if not, at least the GF% should not vary that much. I've no prove what is wrong and I can not do some more tests as I've to keep dry for the next weeks . Anyway, I just wanted to let you know there might be something wrong...

HTH,
Jan

PS: As I said before, I love to see the same depth on both units now. Really cool that this is fixed, Thx!

[JeanDo]

@Solodiver

It might also be a different in Setpoint on both units, no ? Can you have a look into the logbooks to make sure ?

Regards,

[Solodiver]

Thx JD, yes a higher set point could result in this effect. As long I'm the only one reporting this issue I would not give too much on it. Indeed, there might be some misconfiguration on either of my units. I just can report again, that I saw quite a different behavior than with previous firmware releases.

Usually I do not switch set point in my MK2 but beside that, the highest configured set point on my unit is 1.3 which is the main set point on my predator also. Any other set point on my MK2 is lower and should result in longer TTS/deco and higher GF%. At this dive I set my SP to 1.3 at the beginning of the dive as it might have been set to 1.0 or 0.7 from playing around with them at the last dive (for testing purposes for Daniel). Unfortunately I'm not able to see the set points in the internal graphical log view (do I?) nor in JDiveLog. Checking the report done by Daniel with his new diving log software I can see a switch after around 12min at around 80m depth from 1.04 to 1.37. I doubt that any of these values are correct but as I said above, even if they are correct they should have a opposite effect as I'm running 1.3 on the predator.

BTW: It should not have any effect to this, but is'nt the GF low and high als stored in the log book? I've not seen this in JDivelog nor Daniel's software (which is at least reporting the deco model).

For now please ignore this. Maybe there is someone else reporting a similar issue, so you could come back to this. I just wrote it down as long it is in my mind...

HTH,
Jan

[JeanDo]

@Jan

GF is indeed stored inside the logbook (at least with the defaults divisors). To my knowledge, no external software exploit this yet... It is a highly technical curve, but gives deep insight about the chosen GF factors or the decompression margin used by the implementation.

Cheers,