forum.heinrichsweikamp.com

The OSTC does not directly report if it is a 2, Plus, Sport, cR, ... Instead, it reports its hardware features and from this "fingerprint" the 3rd party software guesses what kind of model it is. But there are so many models out meanwhile, that guessing sometimes is inaccurate. Furthermore...

Hi,

that's why the hwos provides the dive simulator mode - endless opportunity now to try out all the settings, do dive & deco violations etc. etc. and observe how the OSTC reacts, what it shows on the display and so on! :-)

Ralph

Hi Jay, sorry for the delay in answering. Before sending the OSTC to HW, there is one thing you may try out before: there is a chance that the button recovers after a reboot. If menu operation is not possible, there is one to two other ways: if your OSTC is an old 2 (big housing) it can be rebooted ...

Ahm, with re-installing 3.09 beta 3 you are back to your original problem... So for installing the beta 4 once it is out, you have to repeat the recovery procedure. Using the recovery procedure should not be done too often, as it is a "no frills" way of loading firmware onto the OSTC, i.e....

Well, that pretty much looks like a defective pressure sensor (depth = pressure and temperature are corrupted). It's factory repairable, please contact HW by direct email to arrange the details.

Hello Michael, then your OSTC is likely to be affected by the hardware anomaly. Please contact HW by direct email to receive tooling and instruction for doing a recovery load. The new firmware will also have a readout of the CPU revision which we're keen to know about to get an idea how many of thes...

Well, I have the honor to forward a big deal of the thanks to Jef from libdivecomputer, as he owns such a 'troublemaker' OSTC and had to try dozens of debugging code enhanced firmware versions for us before we could pin-point the root of the problem. As part of these efforts, there will be an update...

Hi all, here's some news on the next (and hopefull final) beta: Yesterday we were able to fix the last and really nasty bug in the firmware update procedure. Really nasty because it only showed up on older OSTC models, and also not on all of them but just individual ones, heaviliy depending on the p...

Hi Edward, sorry for the delays in answering. I am very busy in the moment with debugging the last issue with the comm mode of the upcomming hwos V3.08 beta 4 firmware which works perfectly despite in one single case that up to now refuses to uncover its root point of failure. Will come back on you ...

Hi, wasn't able to understand in-depth your way of calculation, but maybe some hints help: - the OSTC calculates ppN2 a depth using the gravity constant of 0.9... instead of the 1 bar/10m - also the ppWaterVapor (a constant value) is subtracted, ==> both of this measures reduce the ppN2 a bit, reduc...

Hi, thanks for having such an in-depth look into our code. It's true, there are two warnings that are triggered beyond the M-line, it is the microbubbles warning and the "outside model" warning. Both of these warnings, once triggered, are latched for the remainder of the dive. Basically, H...

HI, thanks for sharing your observations! I'll try to answer / explain... Regarding the stuck in dive mode: actually hard to tell what happened. The OSTC sensed being at depth although it was at surface, so it may have operated on a wrong surface pressure reference. The surface pressure reference ca...

Well, so on the OSTC everything is fine, but the dive data download failed!? I am close to providing a debugging firmware download solution, to narrow in on the "problem maker". Update (copy from above): A lot of time has went into debugging and testing this week, on OSTC side, but also on...

What does the OSTC built-in logbook show?

Hello Hervé,

documentation is always a little bit behind software production, but for the latest Sport firmware you can relate to the hows Tech manuals, as the Sport is based on the Tech. Just ignore CCR, Helium and gauge mode...

BR
Ralph

Thanks for sharing these probing data! I also saw the BT entry in the menu disappearing from time to time. Every time the OSTC restarts into the surface mode, it makes a new auto-discovery of its hardware features. In general, this features some "auto-healing" in case some subsystem didn't...

Hi Michi, the dive data downloading protocol has not changed, but maybe Diving Log also uses an updated library that may cause problems, as i showed in my last post with an older version of Subsurface working fine whereas the latest one is bumpy at least to say. Does it already fail at establishing ...

Hi, sorry to hear you are experiencing problems with firmware uploading. Pretty sure there hasn't been intoduced a bug in the firmare loading code, but indeed the code has changed a bit. The timing while firmware transfer is a little bit picky, with newer (faster) computers and especially smartphone...

sorry, it said ...await... ;-) ......... Now it's available! :-))

Bugfixing Information: NDL always showing zero: that was a simple but stupid bug in the output routine that came in on fixing another bug, annoyingly. Garbage in depth output after crossing 100m: the mechanism for such ghost outputs is a known one, though the individual trigger always a little bit h...

There hasn't been changed anything in the firmware that relates close with the BT transmission. But i also observed "lock-ups" of the BT module, such that it disapperas from the menu. Leving and re-entering the menu fixed that always. But there may also be hangs by something that happens b...

Hi Alex, thanks! Meanwhile i've figured out that the logbook storage bug is due to two different memory chips used throughout the OSTC models - the code works fine with one of them, but not with the other one... Just to underline: all safety relevant functionality (deco, etc.) is ok in the beta 1, o...

Hi Michael,

thanks for that Information! The sensor and the NDL display bug has already been understood from analysing the code and fixed. The root cause for the logbook storage thing seems to be a little bit tricky to find, but we're on the hunt...

cheers
Ralph

Hi all, just discovered three bugs in this beta 1: - using external sensors in CCR or pSCR mode doesn't work, - the NDL time is not shown in the big layout, - there is a propability that there will be garbage written into the dive log when taking this beta under water. --> please do not use 3.09 bet...

Hi,

thanks a lot - could reproduce & will fix that!

BR
Ralph