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

[heinrichsweikamp]

Hi,

Diesmal nur in Englisch, dafür etwas ausführlicher. Ich denke, es ist aber für alle Verständlich.

Today, the new 1.91 beta has been released.

Most important:
1) When downgrading again from 1.91 to 1.90 you may loose your dive profiles!
2) After installation of 1.91 the internal logbook will be converted into the new format. This takes about eight minutes and can't be interrupted.
3) Right now, only the newest alpha from Diving Log supports the new format, so as a Diving Log user you'll need to update. Most likely, the link to the update will be published on the Diving Log Blog soon: http://www.divinglog.de/blog/

Important new Features/Bugfixes:
- The spurious stops when CF55 was >0 and diving with more then two gases were fixed
- The OSTC now records some extra data during the dive and you can see them in the logbook (Average depth, GF and Deco Settings, CNS)
- We have doubled the logbook capacity. Yes, with the default settings for sampling rate and divisors you can now have ~40 instead of ~20 dives (1h) in the internal logbook! As usual, you don't have to pay for the extra memory
- The clock is now accurate - as discussed here intensively, this turned out to be a bug and not an inaccurate oscillator.
- For our Nordic friends, the OSTC now records all negative water temperatures correctly.

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/

The new bootloader PC application (That downloads the firmware and installs it with two mouse clicks) will be available for the next stable. Due to the "CF55 Bug" we may publish the new stable 2.0 faster this time.

If there are any questions and/or comments, please post them here.

regards,
Matthias

[nakatomi]

After updating to 1.91 beta, I noticed that the loading of the logbooks main screen now takes almost 6 seconds. That is when entering the logbook page for the first time, and every time after leaving a dive or scrolling the page.
Does anyone else have the same issue?

FWIW, I emptied the logbook before updating to 1.91 and have made three dives today with 1.91.

[JeanDo]

Hello Oliver,

Yes this annoyance is >: you have an empty logbook, and is such situations the OSTC parse the full memory to find the next dive. And because there is twice as much memory, it is now twice slower... It will be better again after more dives.
But we should probably improve on that.

Thanks,

[nakatomi]

No problem, it will once again be very full in the near future. I hope

[divinglog]

The update for Diving Log with firmware 1.91 compatibility is now available.

• OSTC Firmware 1.91 beta support
• 64 KB logbook memory instead of 32 KB
• CNS profile gets imported
• Max CNS gets imported
• Screenshot function for OSTC

[img]http://www.divinglog.de/blog/wp-content ... /OSTC2.png[/img]

[Solodiver]

Screenshot looks very cool! So there is a way to read the current content of the screen? When did you say you are going to release your app on a proper operating system? Would be really cool....

Back to 1.91 - after upgrading I did not recognize a huge delay in displaying dive logs, slower than before but acceptable. After doing a real dive and having a new log inside the speed felt much slower but still far from 6sec as described above.

Things I've seen under water:

- reading my Future TTS configured for 5min I've seen a TTS 6min less than the real TTS while hanging on a deco stop which should not be possible, not critical just a note
- after "violating" a deco stop by some cm I had this red display quite a long time after going back to the limit, also just a note
- what I did realize in previous releases also is that the unit shows my current gas blinking in shallow areas which means there is a better gas available - diving a CCR this makes no sense but maybe for pSCR or similar, on the shearwater one can define a gas for OC or CC, maybe this would an idea for further development, one could also think about a seeting for CCR or pSCR - just some ideas...

[heinrichsweikamp]

Thanks for your comments:

Solodiver Wrote:
> - reading my Future TTS configured for 5min I've
> seen a TTS 6min less than the real TTS while
> hanging on a deco stop which should not be
> possible, not critical just a note

While doing your deco, future TTS @+5 should be lower then the real TTS, of course. The extra minute is probably due to rounding issues. Only full minutes of deco time were displayed.

Regards,
Matthias

[JeanDo]

Furthermore, if you hang up doing deco at 6m:
* deco is computed at 7m (default security factor CF16),
* Future TTS is computed at current depth, 6m.
So the (small) difference adds up to the rounding, too.