forum.heinrichsweikamp.com

Hello,

Today, we released the 2.94 beta for the OSTC2 Series (2N/Mk.2/2C).

Compared to the 2.90:
NEW: On-Time counter for better battery information
NEW: Store useage timer in logbook header (Byte 54, see documentation)
NEW: CF74: Battery Timeout [min] - Battery symbol will blink if the OSTC was longer in active mode (since the last _full_ charge) then CF74. Default=1800 (30hours)
NEW: Show Gas change countdown if CF55>0
CHANGE: Graphical velocity on by default (CF60=1)
NEW: Ceiling display (GF_hi based) in divemode
CHANGE: No turkish language support anymore
BUGFIX: Gas volume computation when using several travel mixes
NEW: Show event "Bailout" in internal logbook

As usual, get the beta from here: http://www.heinrichsweikamp.com/?id=57&version=en

Regards,
Matthias

Thx!

Dass das Batterie-Symbol jetzt blinkt ist gewollt???


---> CF 74 war der Wert Current auf 0. Auf Default gesetzt, blinkt nicht mehr

Whats the purpose of cf74?

Hi !

In French ?

Thx

My guess from looking at it is that CF74 counts how many minutes the OSTC has been on since last fully charged and once it exceeds the setting in CF74, the battery charge indicator blinks. Quite a useful feature, you just need to decide what to put as CF74. I have just done about 35 hours without a full charge (on a trip) and still had good voltage, so I guess the default of 1800 (30 hours) is a reasonable figure to start with.

What about just plugging it in to charge? That would take out the guess work. Anyway Matthias implemented it and I am sure some people will find it useful to be reminded by the diving computer that they should plug it in to be charged.

Nice idea!

My guess is that this interval is probably good as a reminder to upload your dive data to you PC or whatever too, before you start overwriting dives.

Clearly the value of CF74 needs to be tuned to your type of diving and how bright you maintain the display.

I suppose that Matthias could also have caused the battery symbol to blink once the battery voltage falls to a configurable value given that the recommendation is that LiIon batteries should be recharged before the terminal voltage falls too much below 70% of full charge voltage.

Hi,

This is a remainder to recharge the OSTC from time to time. The current battery indicator only worked on the cell voltage. This caused some issues when diving in very warm waters where the cell voltage is higher just because the battery is warmer.

A full recharge after 30h is a recommended conservative figure to avoid power-loss during the dive.

Regards,
Matthias

Fair enough.

Thanks for yet another useful feature difficult to find in any other dive computer.

Why is my profilegraphic (Logbook) shwowing "Bailout" in the bottem right corner? I've done a trimix dive today, OC...

scubatinoo Wrote:
-------------------------------------------------------
> Why is my profilegraphic (Logbook) shwowing
> "Bailout" in the bottem right corner? I've done a
> trimix dive today, OC...


In the previous beta (2.93) already, all the previous trimix dives already in the memory of my OSTC show "Bailout" ... All OC trimix dives.

OK... I didn't check previous dives for this information. but anyway, what is this informationen (Bailout) telling me? It's color is somehow red - is this an error message or what?

New in 2.94:
BETA Version
BUGFIX: False bailout flag in logbook

... this should be fixed in the 2.94beta. When in CCR mode the depth line changes color so you can see the bailout parts of the dive.

regards,
Matthias

I'm diving with 2.94beta...

Hi


heinrichsweikamp Wrote:
-------------------------------------------------------
> NEW: Ceiling display (GF_hi based) in divemode


How is this new feature to be used? Where can i find the
ceiling display - in custom menu?

Hello,

Unfortunately this release is in english and I can't find the french HEX file.
Enjoy that this Beta version come a stable version...in french.

Regards

scubatinoo Wrote:
-------------------------------------------------------
> I'm diving with 2.94beta...

This is now (for sure) fixed. It will be part of the next beta/stable.

regards,
Matthias

P.S.: Yes, the last beta was only released in English, sorry.

heinrichsweikamp Wrote:
-------------------------------------------------------
> This is now (for sure) fixed. It will be part of
> the next beta/stable.

>:D< Thanks for your efforts!

Continue here: read.php?2,13906