Small logbook issues

Legacy OSTC's
Post Reply
danou
Posts: 25
Joined: 15 Jan 2011, 17:18

Small logbook issues

Post by danou »

Hi all,

While working on Perl scripts to print my logbook with LaTeX, I stumbled upon strange things in OSTC.DMP files (produced by libdivecomputer). The files were provided by Jan (Solodiver).

The dives were done in CCR mode with firmware 1.95, but dumped after 1.96 was installed.

1) There is an alarm "Deco Stop missed" in the first sample of a dive, at depth 0.82m, which doesn't make sense.

Here are the raw data all in hexa) from file OSTC.DMP:

fa fa 21 08 03 0b 0e 13 (dive on 03/08/2011 ended at 14:19)
...
fb fb (end of header)
50 00 82 42 63 <= 1st sample: depth=0.82m, Alarm=2, Setpoint change, value=0.99
8d 00 00 <= 2nd sample (normal)
9d 00 00

The same type of false alarm seems to be visible on the snapshot provided by Matthias on August 03, 2011 08:28AM in thread "Vorschlag firmware update".

2) Setpoints changes (CCR mode) do not seem to be recorded properly in the logbook.

In the example above, the initial setpoint value is 0.99, instead of 1.0, 1.3 or 0.7 (the 3 SP values used by Jan on his OSTC).

OK, this could be a rounding error and mean 1.0... but the initial values of the SP for the next dives are even stranger: 1.23 (dive #373), 1.18 (dive #374), 1.16 (dive #375)...

First samples of dive#373:
47 01 82 40 7b
5c 01 00

First samples of dive#374:
0d 01 82 40 76
14 01 00

First samples of dive#375:
fc 00 82 40 74
15 01 00

3) As Jan already mentionned in thread "New 1.93 beta available for the OSTC 2N/Mk.2" on August 07, 2011 11:26PM, I also found an obviously wrong depth at the beginning of his dive#369 (done with firmware 1.93):

fa fa 21 07 0a 0b 0d 23 (dive on 10/07/2011 ended at 13:35)
...
fb fb
7d 01 00
82 91 01 00 <= strange sample
b3 01 00
d5 01 00

It occured only once, but I mention it here because it might be related to the false "Deco Stop missed" alarms.

Thanks for your remarkable work and best wishes,
--
Daniel Flipo
OSTC Mk2 1610
daniel.flipo.free.fr
heinrichsweikamp
Posts: 4469
Joined: 13 May 2007, 18:07

Re: Small logbook issues

Post by heinrichsweikamp »

Hello,

Thanks for the detailed report - the SetPoint issue should be fixed now :)

Cheers,
Matthias
wrobell
Posts: 105
Joined: 28 Jan 2009, 16:28

Re: Small logbook issues

Post by wrobell »

danou Wrote:
-------------------------------------------------------
[...]
> 3) As Jan already mentionned in thread "New 1.93
> beta available for the OSTC 2N/Mk.2" on August 07,
> 2011 11:26PM, I also found an obviously wrong
> depth at the beginning of his dive#369 (done with
> firmware 1.93):
>
> fa fa 21 07 0a 0b 0d 23 (dive on 10/07/2011 ended
> at 13:35)
> ...
> fb fb
> 7d 01 00
> 82 91 01 00 b3 01 00
> d5 01 00
>
> It occured only once, but I mention it here
> because it might be related to the false "Deco
> Stop missed" alarms.

First of all I would like to confirm above. Jan has sent me the same profile and I see the strange sample as well.

Beside above, I would like to present the following data dumped from OSTC a year ago

header: fafa2006050a0c332f0c3d002e77001104c50315002800220020001b00240001013ce20f0a2c26203090006400fbfb

profile: c70100750200e00200ea0200f502004d030200a0ef0300a00400500500de0500210600a00604a90000390407005407007f0700960700b30700d207020022040800290800610800ed08006e0900c0090491000011e80900170a004e0a00820a008d0a00a00a02000cb60a00d70a00110b005a0b001a0b00310b048500000a1c0b00040b00020b00fd0a00080b00300b0200093c0b006f0b00950b00ba0b00b30b00a40b047d000007b40b00bf0b00ef0b00f30b000c0c002e0c020601070c00060c00ef0b00d10b00b30b00b60b0479000005c00b00b70b00a70b007e0b00690b00250b020004ef0a00be0a007e0a005a0a00570a003c0a0477000005060a00e909009409003909003f090055090200065a09005609003c0900250900f90800ba080478000009880800570800330800fc0700c70700a3070200109407008007007f07003607001a0700830704790000129c0700d70700e3fafafa2009040a0e35cb063300239b0013043a0215002600220020001d002400040146650f0a2c26203090006400fbfb8c0100860200670300380400f2040032050200a0640500b30500ed0500e60500ea0500e10504b40000a0fa05000806002006002706001806001d060200821b0600160600110600fe0500120600080604a700008c1906000e06000e0600fd0500130600160602008c2a06001e0600210600280600190600140604a3000082140600190600130600080600fb0500f20502008cf20500fc0500f60500eb05001006001d0604a10000821f06001e06002806002306002a06001c060200820306000a0600d40500eb0500090600170604a00000822906003606001806001806001a060028060200823a06002806003606002406002906003a0604a00000782f06002a06002f060004060017060011060200782d06001506001a06001606001006000806049f000082fd0500e30500e705000806002206003c0602006e100600280600050600fd0500ea0500e905049f00008ce20500b20500950500940500ae0500a4050200a0950500d10500e205001b06003006004506049d00006e2b06002206001906001606003306004d0602006e7306007d06007e06008506009606009906049c000050a70600ae0600a80600b20600ae0600c206020046ad0600750600930600a90600a106008d06049c0000508706008906008506007c06005d0600650602005a7906007f06007806006606007106004e06049b00005a4f06005106006806003f06002c0600090602006efe0500000600fc0500f00500de0500e305049c000082c90500b90500a40500ba05009e05008b050200a0850500a10500af05009605008905006d05049c0000a04205006005005a05008a05009005004a050200a0130500030500f80400db0400c20400c604049d0000a0b804009204005a04004704004f040070040200a09504008f0400a10400b90400e50400f404049c0000a0f1040010050025050006050001050003050200a00a05002205003405006c05007005009a05049c0000a0c60500d60500ea05000c0600070600e405020078f10500ea0500ce0500d80500da0500e205049b000078d50500e30500e80500f5050019060066060200506d06006106002a06005806005206005706049c00005
05906005b06006106006306005f06006b060200506406004506005f06006206006106005e06049c00005a680600530600280600310600300600460602005a6106005206002f06002606002e06001506049c000064b70500860500760500990500b30500cd0502006e920500460500150500d704008204008404049b0000a0470400100400e10300b303005e030028030200a0fb0200cb0200d10200d80200c80200b602049b0000a0ce0200d90200e20200da0200ef020012030200a0120300f80200be0200d70200bd0200b902049c0000a0a402009602008e02006502003f020028020200a03c0200350200150200a501007b01008001049d0000a07c01007001006b010057010063010043010200a00a0100ca00008100002f00001400001300049e0000000300000a00000100000100000000000e000200000200000600000400001200000500001100049d0000001c00001400000300000100000200000100020000010000010000020000fdfd

sample 98 is at depth 20.07m: d7 07 00
sample 99 is at depth 642.27m: e3 fa fa fa ...
wrobell
Posts: 105
Joined: 28 Jan 2009, 16:28

Re: Small logbook issues

Post by wrobell »

danou Wrote:
-------------------------------------------------------
[...]
> 3) As Jan already mentionned in thread "New 1.93
> beta available for the OSTC 2N/Mk.2" on August 07,
> 2011 11:26PM, I also found an obviously wrong
> depth at the beginning of his dive#369 (done with
> firmware 1.93):
>
> fa fa 21 07 0a 0b 0d 23 (dive on 10/07/2011 ended
> at 13:35)
> ...
> fb fb
> 7d 01 00
> 82 91 01 00 b3 01 00
> d5 01 00

Just different view at above, maybe the first sample is the strange one having additional byte - then all samples have correct depth

fb fb
7d 01 00 82
91 01 00
b3 01 00
d5 01 00

Could be there a bug when saving ProfileFlagByte?

Regards,

w
heinrichsweikamp
Posts: 4469
Joined: 13 May 2007, 18:07

Re: Small logbook issues

Post by heinrichsweikamp »

wrobell Wrote:

[First depth sample]
> 7d 01 00 82

We have:
7d 01 = d'381' = 3,81m
00 = No Event, no additional bytes
82 = d'130' = SetPoint = 1,3bar

Error is in the second byte, which should be 0x81 followed by 0x40 in this example.

I just checked the code here, at least in the latest beta versions - this should work as advertised: In CC modes, the SetPoint is attached to the first sample.

regards,
Matthias
wrobell
Posts: 105
Joined: 28 Jan 2009, 16:28

Re: Small logbook issues

Post by wrobell »

heinrichsweikamp Wrote:
-------------------------------------------------------
> wrobell Wrote:
[...]
> I just checked the code here, at least in the
> latest beta versions - this should work as
> advertised: In CC modes, the SetPoint is attached
> to the first sample.

Sorry for pushing, but I wonder if this could be revisited somehow once again.

I am asking to do that because from time to time there are different reports on strange deco calculation behaviour (i.e. stuck at 9m or entering deco mode when quite long NDL is still expected) or logbook data corruption.

Above was attributed to one dive removal functionality in the past, but that's gone and the problems still are reported from time to time.

In my case, which is the deco mode for a minute or two when still long NDL is expected, the problem could be replicated with 15-20 dives in logbook and then a dive like go to 30m, then slowly go up till end of the dive. It is hard to replicate it with simulation (going up is too fast), but maybe simulating recreational Red Sea trip and reef diving would be possible with a testing chamber?

Best regards,

w
Post Reply