forum.heinrichsweikamp.com

Hi Rob, This device was used before mith OSTCTools and it was working? The device was used with HWOS Config only (the android app). I'm pretty sure I did upgrade all my DCs to the latest firmware versions (both OSTC3+, OSTC plus, OSTC4) around 1 october (to 3.12 for the small OSTCs and 1.5.5 for the...

I'm having a problem with HWOS Config for Android. Running Android 10 device (that I used before successfully with HWOS Config). First, I got an error message cannot create directory /storage/emulated/0/HWOSConfig. Obviously, the app was installed allowing storage permission. Ok, then I make that di...

Hi Ralph, nice, makes live a little more easy to simulate dives. Not sure how familiar you are with the OSTC4 code and its simulator. There is another nice feature called "follow decostops on ascent". This let you automatically do the ascent in the simulator, without user interaction, to t...

Thanks for your explanations Ralph. ad 2) I somehow expected the the ascend speed from the deco parameters was used, but I understand the rationale here. ad 3) My bad. I had a proper OC B/O gas defined for the given depth but it had type "disabled". Interestingly, you can switch (manually,...

Installed this on an OSTC Plus, and ran the simulator: 1) Something nice to have: when doing increase or decrease depth in the sim, the menu says at the same point. So, you can click multiple times with the right button to increase/decrease depth. However, when you to sim+5' the menu resets, so when...

Last week I did 5 proper deco dives (using fw 1.4.8, including some things that I was testing, so not the official 1.4.8 from HW), and I see the deco both on the OSTC4 internal logbook, and when interfaced to Subsurface I see it there as well. I believe that Divinglog (as is Subsurface) is libdiveco...

1.4.8 is likely to be released soon. Way more stable than 1.4.7, and I've not seen any spike test diving the very latest beta code.

> after updating to 1.4.7 the battery indicator is > always red and empty, but it indicates 4.0V > (battery full). Yes, when the RTE part is installed (and rebooted), this is normal behavior. You might try to go to the SYS2 menu, Reset Menu, Maintenance, and there you likely see "Reset last kno...

> Wie konntest du ihn den resetten? Einfach gewartet
> bis der Akku leer ist?
> Und wo hast du die 1.3.0 gefunden? Hast du mir
> hierzu evtl. einen Link?

Put it on the charger, and swipe a good strong magnet on the left side of the unit. This will reboot the firmware.

--jan

I think I just answered my own question :) I just re-implemented the OSTC4's ceiling algorithm. While the old algorithm does work, and gives results that I did understand, it seems not efficient ... and my new algorithm gives very similar results to hwOS. That was not my intention, so it was a bit o...

Question for Ralph. I have problems understanding the value hwOS (current 3.01 version) displays for the ceiling during the deco phase of a dive. Obviously, I find these things while working on the OSTC4 code. While on deco, I expect the ceiling to be smaller than the current stop depth, but when th...

Ralph wrote: ... During the transition from NDL to deco this can be shown for several minutes, whereas at the end of the deco this display normally comes up for just a few seconds and then "NDL 240" is shown. ... I tried to simulate the issue at hand using GF 80/80, 42m depth, air. Yes, th...

Hmm, I dive a lot in caves, and not only for fun, but also for exploration, and up to now, I never missed an inclinometer on a dive computer. For surveying purposes, a proper depth gauge and any distance measurement tool between between survey stations will do. And for a post-siphon survey of a dry ...

Hi Ralph, > I changed the step size from initially 10% down to 5% as 10% makes quite an impact, anyhow given the residual uncertaincies that are in any deco model, adjustments finer than 5% will probably have limited practical value. I agree fully on the limited practical value part from a deco pers...

Hi Matthias, see both attaches pictures (of my beaten up OSTC3 :-) ). One with firmware 2.99 and one with 3.00. The 2.99 shows the percentage in the logbook, and the 3.00 does not. Notice that it was the first dive with 3.00 but it would surprise me very much is that makes any difference. And, yes, ...

Yes, that is even better. Conservatism also sounds too much like the conservatism
factor from VPM.

Does this also imply that the ZH-L16 algorithm is planned to go away? Including the sat/desat pairs?

--jan

When setting saturation/desaturation settings on hwOS tech, the step size is 5%. However, when running hwOS sport, and choosing for example, conservatism +1 these values are 88/112 (verified this in the manual of the OSTC Sport, and by pulling the data info Subsurface). So, now assume that I'm divin...

So, just to be clear. The OSTC Logbook also shows the strange 75% values on the mentioned dives?

As you mention Subsurface ... did you verify the data in the logbook on the device itself?

--jan

Just noticed that since hwOS 3.00, the battery percentage data is not printed on the info page (subpage 1 of the dive details) in the logbook on the device. It is correctly interfaced externally to Subsurface, so it seems a display only issue.

--jan

Hi Ralph, indeed a tricky one, and nice that you found the code path that exposed this behavior. Somehow, I had a feeling that it was related to the 99m MOD case, so that is why I tried to reproduce it on a shallow gas (and failed), and that is also why I wrote down as much as possible relevant deta...

I think I found a firmware bug (HWos tech). Navigate to Diluent Setup. I have 1 enabled diluent setup with gas 10/70 and try to set the depth of that gas to 99m. I do this not by using the depth +/- menu items, but with the Reset to MOD menu option. So far so good. Now navigate out of the menu with ...

Let say I want to use a bailout OC gas 8/92 and max bottom po2 of 1.2 bar. This gas has a MOD of 140m, but hwOS uses a maximum MOD of 99m. Is there a reason to limit this to 99m? There seems to be room in the UI for 1 extra digit.

--jan

But now I'm getting a little confused. A beta is something completely different in my book, than a true bug-fix release that is marked "Stable". Both the beta and SP versions are published at the HW website, so there is nothing internal to it. A beta is even meant for more testing from adv...

> if only the version number from the website will > be checked, it will be easy to write it as e.g. > x.ySPz to make parsing easier. This is just a text > file. Then write it as x.y.SPz. That said, imho, the SP text does not add anything relevant, so then x.y.z is as good. > But if this version num...