Small logbook issues
Posted: 09 Aug 2011, 12:47
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
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