New 1.92 beta available for the OSTC 2N/Mk.2

[heinrichsweikamp]

Hi,

We just uploaded the 1.92beta for everyone to test. As for the 1.91beta there are two important informations for everybody upgrading from 1.90 or lower to this version:

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

Important new Features/Bugfixes:
- The red warning color is now displayed correctly for ppO2>3,3bar
- The SetPoint logging now works even if you don't change the SetPoint during the dive (initial SetPoint is logged)
- A few minor display bugs were fixed in Apnea mode
- hypoxic Air (e.g. 19/0) is displayed in divemode
- the "change gas" indicator now blinks more eye-catching in yellow

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

[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

[Solodiver]

Sorry for coming up with 1.92 but I did not manage to update to 1.93 before my last dive. So here we go with a bug which reads like this:

Knowing that the my MK2 (which I use as backup to my hardwired predator on my CCR) shows similar values as my predator I've seen huge differences today. In fact it seems that a old bug from 1.8x is back concerning wrong deco calculations. While my preadator showd a NDL of more than 10min the MK2 showed 1min at 6m and a TTS of some Minutes. At the next look I had a NoDeco time similar to the predator. Shortly after I had deco again and so on. Is this something you can explain? Unfortunately I'm not able to able to get the log out of the unit as the new logbook format is not supported by JDiveLog yet. I remember we have seen these spikes in the deco calculation in 1.8x before. I'm wrong remembering this has been related to CPU usage?

HTH,
Jan