New firmware 2.28beta

[Clownfish]

Upgraded successfully to the 2.2.8 beta prepared by DiverM. Will test on Wednesday night. Would love it to be 5 minutes as this is what is preferred by most agencies in Australia.

[heinrichsweikamp]

I though it was a yoke spending some CF's on the "safety" stop...

Cheers,
Matthias

[tiefunten]

Please no CF for this feature. I don't need it, but most people say the stop should be between 3-6m, so couldn't you just change that and this whole topic is solved?

[scubatinoo]

gosh, we have plenty of unused new CF's (:D

[DiverM]

heinrichsweikamp Wrote:
-------------------------------------------------------
> I though it was a yoke spending some CF's on the
> "safety" stop...
>
> Cheers,
> Matthias

Apparently not.....

I guess if you change the depth boundaries to 6-3 meters, only one extra CF would be needed to toggle between 3 and 5 minutes.

{Added thoughts:}

heinrichsweikamp Wrote:
-------------------------------------------------------
> You won't degas much at 6m (Assuming a single-gas,
> no-deco dive -> low tissue load). Difference
> between ambient pressure and the overpressure in
> your tissues is quite low.
> I think 3min between 3 and 5m is common sense in
> diving education.
>
> regards,
> Matthias

Degassing is not an issue when doing a safety stop, it is all about micro-bubbles in very much the same way as deep stops are about micro-bubbles. Doing one isolated dive within the NDL, the safety stop is superfluous, obviously. Not doing the safety stop every dive during a week long diving series of 2-3 dives a day (still all within the NDL), is asking for DCS.

As far as depth is concerned, anywhere between 6 to 3 meters is good enough, even a slow ascend from 6 to 3 meters during the stop time will give the micro-bubbles time to defuse (at least enough to surely reduce the risk of DCS significantly).

Then the time issue: In warm water 3 minutes is more than sufficient, but in cold water you might want to go for 5 minutes.

[DiverM]

Oliver Ritzmann Wrote:
-------------------------------------------------------
> Hello!
>
> @DiverM
> Could you be so kind and compile the 2.28beta with
> a safety stop between 3 and 6m in the german
> language? At the moment I'm in Mexico and the stop
> not under 5m is not practicable in this rough
> sea.
>
> Thanks in advance.
>
> CU Oliver

German V2.28 beta, don't forget to take a backup computer with you, I did not test this hexfile....

[scubatinoo]

DiverM Wrote:
-------------------------------------------------------
> I guess if you change the depth boundaries to 6-3
> meters, only one extra CF would be needed to
> toggle between 3 and 5 minutes.

I like!

[DiverM]

scubatinoo Wrote:
-------------------------------------------------------
> DiverM Wrote:
> --------------------------------------------------
> -----
> > I guess if you change the depth boundaries to
> 6-3
> > meters, only one extra CF would be needed to
> > toggle between 3 and 5 minutes.
>
> I like!

Comes to mind, that the existing CF could be adapted, to allow toggling between OFF, 3min and 5min....

[PeJo]

> Comes to mind, that the existing CF could be
> adapted, to allow toggling between OFF, 3min and
> 5min....

(tu)
Exactly, make CF65 a numeric where the recommended values are 0 - 10. (minutes)
Obviously 0 would be = disabled.
And set it default = 0 (not to upset all hardcore tech'ies!)

/Petter

[Oliver Ritzmann]

Hello!

@DiverM
Thank you so much for your perfect service.

CU Oliver

[Oliver Ritzmann]

Hello!

@DiverM
I've to correct me. The hex-file is not flashable. "Overwriting booloader denied" is the result.

CU Oliver

P.S.: For the next dive I'll have my Sol or my old D9 with me as a backup.

[DiverM]

Strange... Only thing I changed for compiling was the language....

Can you flash the HW supplied v2.28beta?

I have had a flashing issue myself, when I tried to flash the v2.27beta from stable v2.21 , had to upgrade to v2.25beta first before further upgrade was possible....

Can someone else test the german firmware I compiled? (will test it myself tomorrow, but you know, the more data the better )

Update: Just got home an compiled some more hexfiles, English works fine, all other languages seem borked somehow....

@Mathias: Compiling for other languages seems straight forward enough, in definitions.asm simply remove the semikolon for the language you want?

ie for German:
[pre]
; International extension. Selecting messages source:
;#DEFINE ENGLISH ; Use english_text.asm
;#DEFINE FRENCH ; Use french_text.asm
#DEFINE GERMAN ; Use german_text.asm
;#DEFINE SPANISH ; Use spanish_text.asm
;#DEFINE RUSSIAN ; Use russian_text.asm
;#DEFINE TURKISH ; Use turkish_text.asm
;#DEFINE ITALIAN ; Use italian_text.asm
[/pre]

[DiverM]

Oliver Ritzmann Wrote:
-------------------------------------------------------
> Hello!
>
> @DiverM
> I've to correct me. The hex-file is not flashable.
> "Overwriting booloader denied" is the result.
>
> CU Oliver
>
> P.S.: For the next dive I'll have my Sol or my old
> D9 with me as a backup.


For now I can only offer you an English firmware with adjusted safety stop depth

At least this one does work B)-

[Clownfish]

It uploaded first go for me. I second the change to 0=off, 1=1 min, 2=2 min etc. That will make all of us happy so long as is 6-3 metres.

[heinrichsweikamp]

DiverM Wrote:
> @Mathias: Compiling for other languages seems
> straight forward enough, in definitions.asm simply
> remove the semikolon for the language you want?


Yes, exactly like this. Try a clean+build (CTRL+F10).

regards,
Matthias

[DiverM]

heinrichsweikamp Wrote:
> Yes, exactly like this. Try a clean+build
> (CTRL+F10).
>
> regards,
> Matthias


same result...

[pre]
Connected to \\.\COM1 at 115200
HEX: 0 min old, INHX32,18Fcode+cfg, total=83188 bytes.
Searching for PIC ...
Found:18F 4685
Reading HEX file...
Overwriting bootloader denied
ERROR!
Overwriting bootloader denied

[/pre]

edit: I attached the definitions.asm file I use, only changed language, compiling English hex file is succesfull, compiling any other language gives above result....

[DiverM]

Found the problem!

Used the wrong linker apparently....

The slightly larger file was used by the compiler, despite that I had added the correct one.

[DiverM]

Oliver Ritzmann Wrote:
-------------------------------------------------------
> Hello!
>
> @DiverM
> I've to correct me. The hex-file is not flashable.
> "Overwriting booloader denied" is the result.
>
> CU Oliver
>
> P.S.: For the next dive I'll have my Sol or my old
> D9 with me as a backup.


This time, a flash-able version:

[scubatinoo]

Oh, you're already running 2.29 beta (:P)

[Clownfish]

Used the 2.29 beta tonight, the safety stop starts at 6 m. Much better.

[Oliver Ritzmann]

Hello!

@DiverM
Yeah, you got it and made my day. This file was flashable.

Thank you very much for your work.

CU Oliver

[cparsons]

Think I may have missed something? I have the 228 beta from HW and the safety stop starts at 6m?

How is your recompiled hex different? Does it have the CF to allow the time at the safety stop to be adjusted?

If so, are there any plans to merge these changes into the main code?

Thanks

[DiverM]

I think you have downloaded my v2.28 beta, since the v2.28beta from HW still had the safety-stop set fro 5-3 meters... as does the current dev version v2.29

Above you can find the modified v2.29beta, which I compiled from the very latest code out of the bit-bucket repository.

I have had a configuration issue with the compiler, and in search of a solution I updated my local code repository, thus arriving at v2.29betadev, as in development, since no official v2.29beta has been released bij HW yet.

[swissdiving]

Yep only 2.28 is from HW.

@Matthias,
Will you integrate DiverM's code into 2.28?

Actually I think its not very smart to post non HW compilations in a HW Beta. It confuses people

[DiverM]

@swissdiving: Code, code..... Let's call it an adjustment of an otherwise fixed CF

Also, I don't see where and why it confuses people.
The current development version is v2.29, I've even added "betadev" for clarity. If it confuses you, you probably shouldn't be loading beta's to your OSTC anyway. But that's just my two cents... -D