Anzeige DEKO in Logbook

[heinrichsweikamp]

Hi Rob,

Attached is a dive I made today - unfortunately only a few minutes@3m but it may help for a first test.

Regards,
Matthias

[Iglooz]

Rob, I would have like to test it tomorrow too but here is what I'm getting at start-up after uploading a 2.52 (changeset 631:19c2773a1657).
Tissue already loaded even without dive (reseting the decodata/OSTC does not help either ...)

Not really sure to dive with this version even with a spare computer !!

[heinrichsweikamp]

Compile 632:41df16e18b2b p2_deco.o wasn't included in 631

Regards,
Matthias

[Iglooz]

No rest for the brave !!
Indeed, it works better this way.

Thanks for the fast update

[Iglooz]

Here is my today dive profile on the France in Annecy.
Difficulties with my new dry suit and not really proud of the profile, but if it can help ...

For info :
- beta 2.52 (changeset 632:41df16e18b2b)
- CF25 set to 6

[Rob]

Hi Matthias,

you are saving the decostep depth instead of the time :S

Have a look:

complete profile entry
Numeric: #1=238 #2=9 #3=20 #4=65 #5=0 #6=15 #7=1 #8=0 #9=4 #10=6 #11=9 #12=12 #13=15 #14=0 #15=0 #16=0 #17=0 #18=0 #19=0 #20=0 #21=0 #22=0 #23=0
Hex: #1=0xEE #2=0x09 #3=0x14 #4=0x41 #5=0x00 #6=0x0F #7=0x01 #8=0x00 #9=0x04 #10=0x06 #11=0x09 #12=0x0C #13=0x0F #14=0x00 #15=0x00 #16=0x00 #17=0x00 #18=0x00 #19=0x00 #20=0x00 #21=0x00 #22=0x00 #23=0x00
Binarie: #1=11101110 #2=00001001 #3=00010100 #4=01000001 #5=00000000 #6=00001111 #7=00000001 #8=00000000 #9=00000100 #10=00000110 #11=00001001 #12=00001100 #13=00001111 #14=00000000 #15=00000000 #16=00000000 #17=00000000 #18=00000000 #19=00000000 #20=00000000 #21=00000000 #22=00000000 #23=00000000

Decostop depth (m)
Value: 15
Numeric: ( 6) 15
Hex: ( 6) 0F
Binarie: ( 6) 00001111

Decostop duration (min)
Value: 1
Numeric: ( 7) 1
Hex: ( 7) 01
Binarie: ( 7) 00000001

Deco Debug
Value: 0
Numeric: ( 9) 4 ( 10) 6 ( 11) 9 ( 12) 12 ( 13) 15 ( 14) 0 ( 15) 0 ( 16) 0 ( 17) 0 ( 18) 0 ( 19) 0 ( 20) 0 ( 21) 0 ( 22) 0 ( 23) 0
Hex: ( 9) 04 ( 10) 06 ( 11) 09 ( 12) 0C ( 13) 0F ( 14) 00 ( 15) 00 ( 16) 00 ( 17) 00 ( 18) 00 ( 19) 00 ( 20) 00 ( 21) 00 ( 22) 00 ( 23) 00
Binarie: ( 9) 00000100 ( 10) 00000110 ( 11) 00001001 ( 12) 00001100 ( 13) 00001111 ( 14) 00000000 ( 15) 00000000 ( 16) 00000000 ( 17) 00000000 ( 18) 00000000 ( 19) 00000000 ( 20) 00000000 ( 21) 00000000 ( 22) 00000000 ( 23) 00000000


Regards
Rob

[heinrichsweikamp]

Rob Wrote:
-------------------------------------------------------
> Hi Matthias,
>
> you are saving the decostep depth instead of the
> time :S

Oops... Will be fixed soon.

Gruß,
Matthias

[Rob]

Huston ... äää Freiburg we have a problem.

CF29 is not saved in the dive-logfile data.
so i dont know at what depth the first decostep is.
See the profile of Iglooz he set cf29 to 4m.
it would be interesting to see what happens when the last step is set to 6m.

For example:
Normal: 3m 6m 9m 12m
Iglooz: 4m 6m 9m 12m

CF29=6: 6m 6m 9m 12m OR
6m 9m 12m 15m

Maybe we have to use the first byte for the depth of the first decostep and then we have 14 bytes for the decosteptime.
The rule for handling the examples is not the problem, but i have to know the depth of the last decostep.

Or any other idea Matthias?


Regards
Rob

[heinrichsweikamp]

> Or any other idea Matthias?

Yes, put CF29 into the header of the log (We have some bytes free here).

My proposal: save CF29 into header byte 52.

Regards,
Matthias

[Rob]

> My proposal: save CF29 into header byte 52.

Thats the best solution.
I didn't dare to ask

B52 will be fine.

Regards
Rob

[heinrichsweikamp]

Done.

Matthias

[Rob]

Done too.

but now i need a dive with cf29 < 6m and a dive with cf29 = 6m to work out the behaviour.
Matthias, can you tell me what is saved when cf29 =6m?

Byte 1: 0
Byte 2: 6m
Byte 3: 9m
Byte 4:12m

or (what i think is the reality)
Byte 1: 6m
Byte 2: 9m
Byte 3:12m

So in the first byte ist the decostep given in cf29 next step is the next regular step in the 3-6-9-12-... order.

Right?

best wishes
Rob

[heinrichsweikamp]

Here's one with quite a lot of deco (Last @3m)

Regards,
Matthias

[heinrichsweikamp]

Rob Wrote:
> or (what i think is the reality)
> Byte 1: 6m
> Byte 2: 9m
> Byte 3:12m

Correct. There's one very special case: If one stops exceeds 255min the next entry will have the remaining time for this stop. I don't think you need to implement this.

Matthias

[Rob]

That means whenever i got an 255 in one byte i have to add(?) the next byte.
When the Time is 255 the next byte will be 0 and belongs to the 255 step.

Am i right?

Rob

[Rob]

heinrichsweikamp Wrote:
-------------------------------------------------------
> Here's one with quite a lot of deco (Last @3m)

What a dive.

Should i change the order of the deco stops?

Regards
Rob

[scubatinoo]

Rob Wrote:
-------------------------------------------------------
> Should i change the order of the deco stops?

Yes, deepest first... but i guess that there are 50% others who like it this way (:P) But much nicer, IMHO, would be a table form...

[DTR.Diver66]

Hello Rob,

for me it would be also nice to see the deepest first.


Regards

[xymanuel]

Hi Rob,
i also vote for the deepest stop first (tu)
Regards
Manuel

[Gucky]

Warscheinlich wurde Abstand davon genommen weil für den TG relevante Daten im Vordergrund stehen sollten ...
Was nützt die max Deko Zeit im Logbuch wenn aufgrund eines Multi Level Profiles (90 % der TG) ein ganz anderes Profil ausgetaucht wurde?
Sollte das jemand z.B. nach einem Tauchunfall ernst nehmen und nicht das Profil anschauen wird u.U. eine falsche Schlußfolgerung gezogen.

Spannend ist doch nur das was wirklich war. Nicht das was vielleicht hätte sein könnnen ... oder sich im Laufe des TG geändert hat.
Also bitte im Logbuch das anzeigen was wirklich passiert ist!
Ansonsten ist es ein Lügenbuch.
Die Dekozeiten sind auch ganz prima aus der eigenen TG Planung ablesbar.

Gruß Gucky

[JMA]

Hallo zusammen

Lange ist es her, als ich das letzte mal im Forum gestöbert habe.....::o

Interessant zu sehen, dass man sich bei diesem Thema auch nicht einig ist.
Ich muss gestehen, mittlerweile sind mir die Deko-Angaben nach dem Tauchen auch nicht mehr soo wichtig.

Aber trotzdem wäre es evt. doch noch gut, zumindest die "gesammelte" TTS im Logbuch anzeigen zu lassen.

Grues, Jan