forum.heinrichsweikamp.com

Hello Matthias,

Please see updated RUSSIAN version.
Next messages were translated:
## 183 - 185, 193 - 224, 227.

Thank you!

This is intended for Nakatomi - if HW doesn't want to revisit the safety stop discussion again, I can generate the firmware adjusted for a stop of 3-6 or 4-6m for you if this is helpful?

This is also intended for Nakatomi:

There seems to be a confusion here about safety stops the newest cf and then deco stops - the stops that have always been incooperated in the firmware.
AFAIK no technical agency are working with safety stops.

br: Michael

Still the same problem, updating from 2.21 stable to 2.27 (or 2.26) produces a black screen.

Updating from beta 2.25 to 2.27 works.

@Chris
Thanks a lot for the offer, I appreciate it! In the long run I would need it done for every new version, so actually I won´t bother. I´ll do it as I have always done, by activating the stop watch

@Michael
Well I don´t know about all technical agencies and for sure I do not want to argument about this. Nor would I want to argue about the usefulness of safety stops in general All I know is that the agencies I have trained with being IANTD and NSS-CDS absolutely recommend that safety stops are done on no decompression dives. Quite obviously this is not required nor useful on decompression dives.

Just to clarify, I´m not asking for anything to be changed. The point was simply to voice my opinion that the safety stop feature, as it is implemented now, will NOT allow the safety stop to be performed correctly as required or recommended by most agencies. This for the simple fact that hovering at 5m will most likely be below 5.00 m for at least 50% of the time, thus interrupting the safety stop of the OSTC that stops at a floor of 5 meters.

Oliver

I wouldn't worry about acquiring a modified firmware version. I will actually need to compile it for myself for every future version, as I agree with you on the boundary depth for the safety stop.

Adjusting the figures and compiling the firware hex-file is done in a matter of minutes so don't hesitate to ask if you want a customized firmware.

08-15 users like me don't have any idea about compiling... And maybe that's ok, otherwise the support about non-reacting units will increase...

I also think the safety stop sould be between 3-6m, as it's in every recreational computer on the market, bue I also undertand HW's way of thinking... That matter is beeing a pain in the ass, and we sould be thankful for including it after our petition. I understand they want to close the subject as fast as they can.

Try asking shearwater for a safety stop in predator computers, and wait for response...

@scubatinoo

If you happen to flash a non working firmware onto your computer you can always revert to the standard firmware as provided by HW of course.

How to do that has been discussed many times.

DiverM Wrote:
-------------------------------------------------------
> I wouldn't worry about acquiring a modified
> firmware version. I will actually need to compile
> it for myself for every future version, as I agree
> with you on the boundary depth for the safety
> stop.
>
> Adjusting the figures and compiling the firware
> hex-file is done in a matter of minutes so don't
> hesitate to ask if you want a customized firmware.


I may take you up on this offer. Many thanks.

Jerry.

@Smiler1968

Use at your own risk of course B)-

DiverM Wrote:
-------------------------------------------------------
> How to do that has been discussed many times.

What? How to compile a customized firmware or how to revert a standard firmware?

DiverM Wrote:
-------------------------------------------------------
> @Smiler1968
>
> Use at your own risk of course B)-


That goes without saying. Thanks.

[quote="Diver M"]
DiverM Wrote:
-------------------------------------------------------
> I wouldn't worry about acquiring a modified
> firmware version. I will actually need to compile
> it for myself for every future version, as I agree
> with you on the boundary depth for the safety
> stop.
>
> Adjusting the figures and compiling the firware
> hex-file is done in a matter of minutes so don't
> hesitate to ask if you want a customized firmware.
[/quote]

Thanks very much, I have taken you up on that kind offer.

scubatinoo Wrote:
-------------------------------------------------------
> DiverM Wrote:
> --------------------------------------------------
> -----
> > How to do that has been discussed many times.
>
> What? How to compile a customized firmware or how
> to revert a standard firmware?


Reverting to standard firmware

Compiling isn't hard either, it's explained in a document when you download the source code. The only thing which can be a puzzle is where to place the workspace an project file (they go in the "ostc2_code" directory). After that you start the MPLAB IDE v8.86 open the project file and hit 'F10'. If all goes well a hex-file appears

I was doing the first dive today with my repaired unit. I've missed to update the firmware to V2.27, but V2.26 was OK for checking the safety stop feature. My dive was with a light deco, which disappeared during ascent, because we've had some time arround 12 - 10 meters. The stopp came to display as i reached 5.0m and the countdown startet. Perfect - even though it was a deco dive. But as soon as i went a little deeper than 5.1m the stopp was hidden and only came back, when i reached 5.0m again. So this makes really no sense! Especially if we have CF's like CF16 (CF16: Estimated distance to decompression stop) with a default value of 1 meter... Why am i - as a technical diver - expected to stay below one meter of the required stop and a recreational diver only 10cm?

Safety stop between 6 and 3 meters like in the "community edition" firmware is a perfect solution.

If you guys are going to modify the firmware by yourself, can someone PLEASE compile a version without this shutdown at 130m!? Thx a lot!

Is someone of you compiling the firmware using a linux box?

@ Solodiver: Didn't Matthias mention some time ago, that this shutdown is hardware related and can't be disabled!?

Yes, he did...

As I have no death-wish, I will limit myself to change only that of which I can foresee the implications.

In short:

Want another deco algorithm? Learn to program and compile yourself, or buy another computer.

Want to dive beyond 130m? Buy another computer.

Want custom depths for the safety stop? I can do that.

Want the battery charging color changed? I can do that.

Want something changed and I think it unsafe? Ask someone else, learn to program and compile, or forget about it.

DiverM Wrote:
-------------------------------------------------------
> Want custom depths for the safety stop? I can do
> that.
>
> Want the battery charging color changed? I can do
> that.

That brings me to a pioneering idea:

Online Firmware Compiling
(c) 2012 by scubatinoo (:P)

Which is a webservice where you can register with username and password. After loging-in you can start with a standard profile and make your changes. The profile contains all stuff (CF's and more) who can be changed, but don't have to be changed for every dive. After saving the profile you can compile your firmware online and download it to your harddisk, from where you can install the hex-file in normal way using bootloader or other software like ostctools, ostc-planner etc.

This would keep or even increase all the flexibility of CF and other changeable values.
>:D<

No, the shutdown is coded in software. And yes, why not have an online compile service? Shouldn't be that tricky. If someone goes for rewriting the firmware, the for sure choose the Linux way would be choosen where one can configure what and how to compile. This would also save some CF for sure...

And most of the "Custom Functions" are more "Custom Settings"... But that's a detail... B)-

By the way: to which depth are the OSTC units tested? Doesn't make sense to override the 130m shutdown and the unit implodes at 135m...

AFAIK the problem is the pressure sensor of the ostc. It is only certified to 130m and very unreliable when you go deeper. Besides, the Bühlman-Decomodel should only be used for dives to 120m. I neither know if the sensor would survive deeper diving nor if it produces data at all below this depth. Only that matthias mentioned, that the shutdown is hardware related and can't be changed. As I'm not a programmer, I can't verify that but I believe him and since 120m is enough for me, I don't care. On the other hand: Diving to these depths is really expensive, so why not buy a computer (DR5) that is certified therefore?

tiefunten Wrote:
-------------------------------------------------------
> Besides, the
> Bühlman-Decomodel should only be used for dives
> to 120m.


This is the reason why Uwatec's Galileo turns in Gauge Mode at 120m...