The fastest message board... ever.
 
Pages: Previous123Next
Current Page: 2 of 3
Re: New firmware 2.27beta
Posted by: DiverM ()
Date: July 09, 2012 11:52PM

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.

Attachments: mk2 6 to 3m safetystop v227beta.hex (227.5 KB)  
Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: scubatinoo ()
Date: July 10, 2012 08:40AM

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... grinning smiley

regards,
scubatinoo

><((((º> OSTC 2N 3705 <º)))><

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: Vortax ()
Date: July 10, 2012 10:46AM

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... ;-)

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: DiverM ()
Date: July 10, 2012 11:14AM

@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.

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: Smiler1968 ()
Date: July 10, 2012 11:40AM

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.

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: DiverM ()
Date: July 10, 2012 11:54AM

@Smiler1968

Use at your own risk of course smoking smiley

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: scubatinoo ()
Date: July 10, 2012 12:52PM

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?

regards,
scubatinoo

><((((º> OSTC 2N 3705 <º)))><

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: Smiler1968 ()
Date: July 10, 2012 08:18PM

DiverM Wrote:
-------------------------------------------------------
> @Smiler1968
>
> Use at your own risk of course smoking smiley


That goes without saying. Thanks.

Options: ReplyQuote
Re: New firmware 2.27beta
Date: July 10, 2012 10:08PM

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.

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

Best Regards,
Stu
(Blackpool - UK)

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: DiverM ()
Date: July 10, 2012 10:42PM

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 winking smiley

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 tongue sticking out smiley

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: scubatinoo ()
Date: July 11, 2012 12:27AM

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? tongue sticking out smiley

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

regards,
scubatinoo

><((((º> OSTC 2N 3705 <º)))><

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: Solodiver ()
Date: July 11, 2012 12:48AM

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?

~~~
MK2 1076

my wish list: [heinrichsweikamp.net]

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: tiefunten ()
Date: July 11, 2012 09:32AM

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

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: Vortax ()
Date: July 11, 2012 10:59AM

Yes, he did...

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: DiverM ()
Date: July 11, 2012 01:18PM

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.

OSTC 2N #4807

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: scubatinoo ()
Date: July 11, 2012 02:17PM

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 spinning smiley sticking its tongue out

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.
the finger smiley

regards,
scubatinoo

><((((º> OSTC 2N 3705 <º)))><



Edited 1 time(s). Last edit at 07/11/2012 05:34PM by scubatinoo.

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: Solodiver ()
Date: July 11, 2012 04:16PM

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...

~~~
MK2 1076

my wish list: [heinrichsweikamp.net]

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: scubatinoo ()
Date: July 12, 2012 10:33AM

And most of the "Custom Functions" are more "Custom Settings"... But that's a detail... smoking smiley

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... grinning smiley

regards,
scubatinoo

><((((º> OSTC 2N 3705 <º)))><



Edited 2 time(s). Last edit at 07/12/2012 10:43AM by scubatinoo.

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: tiefunten ()
Date: July 12, 2012 11:02AM

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?

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: scubatinoo ()
Date: July 12, 2012 11:24AM

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...

regards,
scubatinoo

><((((º> OSTC 2N 3705 <º)))><

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: heinrichsweikamp ()
Date: July 13, 2012 12:26PM

Hi,

Again:
- Don't use the OSTC for depths >120m
- As a warning the depth will be red (Default setting) at 120m
- The pressure sensor works up to 14bar absolute
- We can't change the sensor using a firmware update

Sorry if this is not the answer you want to read.

Cheers,
Matthias

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: milkyway ()
Date: July 13, 2012 01:30PM

Hello!

@DiverM
Thanks for your work. Is it possibe to get a file for the German language?

Thx in advance.

CU Oliver

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: DiverM ()
Date: July 13, 2012 03:33PM

milkyway Wrote:
-------------------------------------------------------
> Hello!
>
> @DiverM
> Thanks for your work. Is it possibe to get a file
> for the German language?
>
> Thx in advance.
>
> CU Oliver


Yes, it is possible to compile a version in German. But as it is, v2.21 stable is already available in german, and with the v2.27 beta you shouldn't dive. And as far as testing goes, you might as well test it with the english version as the language does not alter the behaviour of the software.

When the next stable is realeased I can compile it in all available languages with the safety stop depth and or time changed for 6-3m.

OSTC 2N #4807

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: milkyway ()
Date: July 13, 2012 03:56PM

Hello!

@DiverM
Thx for your reply. With the beta-software I shouldn't dive, that's clear - but I'll do this (with a backup TC - Sol) just to test the new features.

Of course, it's not a problem to do this with the english version (I speak a famoust accent without the slighest english), but only to increase my own comfort it would be nice to have it in the German language.

So if it's not a hard work for you......... :-)

CU Oliver

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: heinrichsweikamp ()
Date: July 13, 2012 08:50PM

Hi,

The beta zip: [www.heinrichsweikamp.com] contains a version in German (mk2_v227-beta_deutsch.hex)

Edit: Never mind. I think you referenced to the custom build...
Regards,
Matthias



Edited 1 time(s). Last edit at 07/13/2012 08:54PM by heinrichsweikamp.

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: milkyway ()
Date: July 13, 2012 10:21PM

Hello!

@Matthias
Yepp, you're right.

A safety stop from 6 to 3m is nearly perfect for me.

CU Oliver

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: Solodiver ()
Date: July 15, 2012 01:05AM

heinrichsweikamp Wrote:
-------------------------------------------------------
> Hi,
>
> Again:
> - Don't use the OSTC for depths >120m
> - As a warning the depth will be red (Default
> setting) at 120m
> - The pressure sensor works up to
> 14bar absolute

> - We can't change the sensor using a firmware
> update
>
> Sorry if this is not the answer you want to read.

I'm pretty sure we've discussed this and have for sure seen a copy of the part of the source code which shuts down the unit. The question is still why is this there? I and others only ask to remove this part of the software, not to change/update the hardware specifications.

And to make it clear (again, also discussed before): The DR5 is not an alternative (for me)! Know to much guys which have too much trouble with these units and I also tested it myself and found it not comparable to the OSTC, Sorry. The OSTC is advertised as a technical dive computer and at least in these advertisements there is nothing found about this limit. 130m is not out of reach for nowadays divers and will be normal as CCR diving will become even more popular. I'm pretty sure I've discussed this question before I bought the unit (and the DR5 also has been an option) and have been told, that the only issue is the deco model which is not made for dives deeper than 120m. As this is also true for Shearwater and any other unit not having these depth limitations it is fine for me knowing this when using the unit deeper (intended or accidentally), especially as it is my backup unit. But a dead unit is not acceptable at all, so I ask again to remove this limitaion, thx.

Lets try it this way: Is there any difference if the unit is switched off or running at a depth of 150m?

Update: As it may not be clear for others not following the discussions before: We've been told that the depth sensor is not working _accurately_ for more than 14 bar, meaning the shown depth (and used for deco calculations if applicable) could (will) drift away from the real depth. This is an different statement from "working up to 14bar" as seen above. As I understood, the same sensor is also built in to the DR5 accompanied by an 2nd sensor for reading greater depth (but not reliable at shallow areas).

Thx,
Jan

~~~
MK2 1076

my wish list: [heinrichsweikamp.net]



Edited 1 time(s). Last edit at 07/15/2012 01:53AM by Solodiver.

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: heinrichsweikamp ()
Date: July 15, 2012 12:27PM

Hi Jan,

Please look at the facts (See datasheet DA5541C_005) again, the sensor (MS5541C) is guaranteed to work up to 14bar (Which is about 130m). In other computers other sensors may be in use (There are sensors for more then 14bar).

Will the ADC in the sensor clip or overflow at 140001mbar? Will it work up to 15bar? Even with all Cx-values at it's max. or min. allowed value (See AN518)?

If you are sure about the consequences just remove the error-routine by yourself or find someone doing it for you. We won't do that, sorry. This lock-out is intend to catch sensor errors - a non-working computer may be safer then a unit showing wrong information.


> diving will become even more popular. I'm pretty
> sure I've discussed this question before I bought
> the unit (and the DR5 also has been an option) and
> have been told, that the only issue is the deco
> model which is not made for dives deeper than
> 120m.

Definitely not. It's stated very clear in the OSTC manual or in our Flyers and if you have have asked us you've had been told that the unit is workable for dives up to 120m and shows depths until 130m.

As this is also true for Shearwater and any
> other unit not having these depth limitations it

Which sensor is used in the Shearwater?

regards,
Matthias

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: Chilihead ()
Date: July 15, 2012 01:40PM

Pursuit V68 Manual

• Transducer depth range: 14ATA
• Transducer depth accuracy: +/-2.5%

Predator Manual v2.3.3 (English)

Transducer Depth Range: 14ATA
Transducer Depth Accuracy: +/- 2.5%

The OSTC Pressure Sensor - MS5541C
• Pressure range 0 - 14 bar

May be the Same Sensor??

ok... the Shearwater Pursuit @ 500m works...

Options: ReplyQuote
Re: New firmware 2.27beta
Posted by: tiefunten ()
Date: July 15, 2012 02:33PM

The datasheet of the OSTC Sensor only states, that it can withstand an absolute pressure of 30 bar in salt water - but it is written nowhere, how it behaves at higher pressures than 14bar.

Matthias, did you check this behavior (of the sensor) below 130m in your pressure pot? For me, the depth range of the OSTC is absolutely sufficient, but it would be interesting to know...

Options: ReplyQuote
Pages: Previous123Next
Current Page: 2 of 3


Sorry, you can't reply to this topic. It has been closed.
This forum powered by Phorum.