Page 1 of 1

A few questions about the OSTC plus

Posted: 18 Oct 2019, 19:49
by julianp
Hi,

I recently bought an OSTC plus with hwOS sport and had the occasion to use it during a few test dives. So far I'm pretty happy with it.

I have however a few questions.

1. I've been using OSTConf on iOS to help me configure the OSTC and flash the most up to date firmware. I'm surprised because OSTConf reports the OS type as "hwOS Tech" even though the OSTC is running the Sport version. Is this a bug in OSTConf ? (or is it possible that I've been sold an OSTC plus "Tech" with a downgraded firmware ?)

2. What is the latest stable firmware revision of hwOS Sport ? 10.61 appears to be the latest at time of writing and is the one I've flashed, but there's no official communication about it on this forum and this version does not appear in the changelog on the firmware download page.

3. Where can I find the hwOS Sport source code ? I've found the git repository called hwos_code on bitbucket but I only find mentions of hwOS Tech firmware version numbers in the history. Are "tech" and "sport" sharing the same code, if so, why are they not sharing the same version numbers ?

4. I've installed a SAFT LS14500 battery in my OSTC. The manual indicates that the T1 option should be chosen in the "New battery" menu. However only T0, T2 and T4 actually appear in the menu. Both T0 and T2 actually work with this battery, but choosing T0 makes the OSTC wrongfully report a 100% battery level, and choosing T2 leaves the charging function on the OSTC enabled which does sound pretty dangerous.

5. I'm confused by the description of the ppO2 max and ppO2 deco settings in the manual. Is pp02 max used for computing MOD ? What's ppO2 deco used for ? Which one of these two is used for displaying a warning when the ppO2 is too high ? Thanks for clarifying this.

6. Another post from this forum discourages using batteries other that Sanyo UR14500P or Panasonic ICR14500 which both have a 800mAh capacity. But unfortunately they appear to be really hard to come by. I was able to find cheap ICR14500 batteries from china that claim to have a capacity of 2800mAh, and are equiped with a discharge protection circuit. Is this safe ?

Maybe I should mention that I'm using the french version of the firmware.

Thanks for helping.

Re: A few questions about the OSTC plus

Posted: 01 Nov 2019, 15:34
by UKG
Hi Julian,

to your #6: Don't know where you live, but here's two online shops who carry the Sanyo batteries

https://www.nkon.nl/de/sanyo-14500-3-7v-800mah.html

https://www.akkuteile.de/sanyo-14500-84 ... 00105_1122

As far as capacity is concerned, anything higher than 900-1000mAh for a rechargeable 3,6V 14500 battery is bogus (there's various posts in this forum on that).

Furthermore the Trustfire 14500 are a good option, too. Until recently the OSTC plus came equipped with these from the hw factory.

Re: A few questions about the OSTC plus

Posted: 01 Nov 2019, 19:24
by julianp
Thanks for your answer, I only found the posts about batteries in the forum after creating this thread. My mistake sorry about that.

It appears the cheap batteries I was about to order from china were indeed bogus. Some online customers reported measures of ~400mAh instead of the advertised 2800mAh capacity.

I must say that no rechargeable battery was provided when I bought the OSTC plus. However, I was able to find a 800mAh rechargeable battery of the "XTAR" brand from a serious local electronics components dealer. It's been working well so far.

That resolves question #6. Question #2 is now out of date because firmware 10.63 is now officially out. I'd appreciate if someone could help me answer the rest.

Thanks,

Re: A few questions about the OSTC plus

Posted: 02 Nov 2019, 07:29
by Ralph
Hi,

1) the latest Sport is derived from the Tech (by removing some functions, mainly Helium and CCR), thus it's "signature" may well be identified as a tech by 3rd party software. Just don't care about that...

2) check out the form, latest versions are always announced within the first entries.

3) You found it! The "old" sport was not open source, but the tech. This open repository will get updated from time to time.

4) battery type coding is: 0:1.5V, 1:3.6V Saft, 2:LiIon 3.7V/0.8Ah, 3:LiIon 3.7V/3.1Ah, 4: LiIon 3.7V/2.3Ah.

5) They are both used for generating warnings: while in the bottom phase and the Initial ascent, the ppo2max value is used, while during the deco stops the ...deco is uded. MOD is named "change depth" in the menu system and needs to be set by hand, as ppO2 is not the only factor determining MOD, but also ppN2. So it is left to the user to decide on personal choice of gas depth limits.

Ralph

Re: A few questions about the OSTC plus

Posted: 02 Nov 2019, 11:25
by julianp
Ralph Wrote:
-------------------------------------------------------
>
> 4) battery type coding is: 0:1.5V, 1:3.6V Saft,
> 2:LiIon 3.7V/0.8Ah, 3:LiIon 3.7V/3.1Ah, 4: LiIon
> 3.7V/2.3Ah.
>


Thanks Ralph, the problem is that on the OSTC plus, T1 cannot be selected because it is not in the list. Does this mean that we're not supposed to use SAFT batteries in the OSTC plus ?

Re: A few questions about the OSTC plus

Posted: 02 Nov 2019, 12:34
by Ralph
Yes, on purpose. The SAFT is not rechargeable, but this can not be detected by the OSTC plus hardware. So for safety reasons, we strongly request to only put rechargeable 3.6 Volt batteries into the plus model.

Re: A few questions about the OSTC plus

Posted: 16 Nov 2019, 08:55
by kuehnero
Hi Ralph

You wrote: "3) You found it! The "old" sport was not open source, but the tech. This open repository will get updated from time to time."

The code for hwOS_code on bitbucket.org/heinrichsweikamp is still from 19 Sep 2019. When will it include the 3.07 Release code?

Thank you,
Oskar

Re: A few questions about the OSTC plus

Posted: 16 Nov 2019, 09:46
by Ralph
There is still one point that needs improvement in the 3.07, it is the instability of the depth of the first deco stop. A rework of the respective code has been done already and is in HW internal testing at times. As soon as testing is finished without any findings, an update of the repository can be expected.

BR
Ralph