forum.heinrichsweikamp.com

A FAQ won't solve anything, people just don't know how to read or use the search function of the forum....

All we can do is just patiently answer the same question over and over again, or just ignore it.

On low brightness I have found battery life to be around 6 months having done some 50 dives avaraging 50 minutes per dive during that period. This still excludes the hours spent toying and demonstrating the OSTC on the surface....

In other words: Battery life is more than sufficient (tu):)-D

If I recall correctly you can only choose from a number of preset GF factors with the Frog.

I guess that's the subtle difference between an advanced recreational dive computer and a technical dive computer.

Flexible design is proving it's value as it appears. (tu)

You could call it a feature B)-

You better send an email to HW.

Any random 5V power-source with the right connector can be used to charge the OSTC....

swissdiving Wrote:
-------------------------------------------------------
> But then other people are complaining about the OC
> Bühlmann algorithm...
> ...you just can't win.


A most peculiar thing happened recently: Shearwater released a new dive-computer with ZH-L16-C algorithm and GF's :)-D ...

scubatinoo Wrote:
-------------------------------------------------------
> I guess the spikes are more a mathematical then a
> life threatening issue...


Excactly my point.

I have seen this behaviour with other software, which use Bühlmann.

Common sense indicates that you stop worrying about this, as you can't reach the jumping ceiling within ascent speed limits anyway?

A digital compass properly implemented is most certainly an asset. I may even considder buying a ostc3 if the compass proves to bee good, and degrade my 2N to backup-computer

I must agree with tiefunten, the 2N is an exceptionally good diving computer.

From the user's point of view, the 2N and 3 are in essence identical. The wet connector is as I read it, only used to display the O[sub]2[/sub] sensor values on screen, the software does not calculate with these values ...

heinrichsweikamp Wrote:
-------------------------------------------------------
> Hi,
>
> It's a 8bit custom function (max. 255) and it's
> limit is set to 250s currently.
>
> Cheers,
> Matthias


As a quick workaround to the limitation, multiply by 10 ?

Still storing the CF in 8bits, and a 10s ...

For CCR divers a minimum of 0.19Bar[sub]ppO2[/sub] makes perfect sense. There is an inherent delay in the measurement with chemical oxygen sensors, so levels can change quite a bit before the measurement becomes correct and stable.
So you really want a good safety margin when using a CCR, both with ...

heinrichsweikamp Wrote:
-------------------------------------------------------
> Smiler1968 Wrote:
> --------------------------------------------------
> -----
> > This is the latest Beta with the safety stop
> > adjusted to 6m. If anyone is interested.
>
> Before this starts again, there will be ...

I see the same Li-Ion cells being used in industrial applications, where they are being used in a much harsher fashion, and cell failures usually occur after about 6-7 years.

Treating the cell nicely like HW does, I expect >10years of use before mass failures start occurring.

I'd be more worried ...

Strictly speaking, when you have the GF displayed on screen, you can make a "linear-GF ascend" keeping the GF between 90 and 95 for example. And thus allowing for the of-gassing factor to be at a maximum at all times during ascend.

In an emergency you would then only have to take a few parameters ...

PeJo Wrote:
-------------------------------------------------------
> (tu)
>
> ...even though I still (from a esthetic viewpoint)
> think the main display should be reworked with:
> "41.0" and "Max." swapping places.
> All other data have the header above the data, so
> I don't understand why not ...

Yet another thing I need to do some tweaking on. This February the water in the Grevelingenmeer reached -3°C.

The gas-switch stop will clear, when you ascend. ie: With a switch set at 21m, it clears when I have ascended to 18m.

With CF55 set to 1 minute. Using V2.50

Gassetup:
G1: NX28 (travel)
G2: TX21/28 (bottom)
G3: NX49 (deco)

Bardass Wrote:
-------------------------------------------------------
> So use stopwatch
> Because, without sound, countdouwn is useless
>
> QED (quod erat demonstrandum)


Same can be said of the deco stop countdown..... useless, because there is no sound.
And countless other parameters and ...

Aquazone Wrote:
-------------------------------------------------------
> Hi HW
>
> I have noticed the new Safety stop will only
> activate shallower than 5m. So a stop at say 5.5m
> the stop will not start or continue to count. Can
> this be made to start at 6m and shallower. It's a
> great ...

milkyway Wrote:
-------------------------------------------------------
> Hello!
>
> And I have to ask DiverM once more for a compiled
> modified file with a stop between 6m and 3m (in
> the German version). :-)
>
> It's only a small thing, but with it the new 2.50
> would be perfect.
>
> DiverM ...

swissdiving Wrote:
-------------------------------------------------------
> I pose my question again. Has the Safety Stop now
> been implemented to everyones satisfaction?


No.

But that's why I adjusted the stop to start @6m depth and subsequently compiled my own.

Still need to read in on the ...

On a more serious note: Storing the max TTS should be feasible. As this only requires comparing the current value with the previously stored value, and storing it when the current value exceeds the stored value.

As requested before, maybe drop the profile graph from page 3 of the logbook display ...