Hollis DG03 data import error

Gobbledegeek gobbledegeek at gmail.com
Fri May 23 03:07:11 PDT 2014


Ok, since I checked that my DC is correct, its not that critical for
post-dive accident  analysis
 Except in the case  the investigators import the entire dive data history
using subsurface and the error is not noticed. This one example is a
glaring obvious error. What if the error is marginal varying only by a
small percentage but the reading shows 32mtr instead of 30. The diver is
comatose or in a chamber or dead and the DC isnt physically handed over,
but the dive data is exported and emailed to the DAN or an insurance
company. This will lead to a problem with the insurance claim as the diver
has exceeded his certified depth, and so it is still important IMHO to get
to the bottom (no pun intended) of this.

Thanks


On Fri, May 23, 2014 at 3:27 PM, Gobbledegeek <gobbledegeek at gmail.com>wrote:

> My apologies, I read dive number as Date 5 Jan, instead of 5, Jan 3rd,
> ignore the date part.
>
> G0bble
>
>
> On Fri, May 23, 2014 at 3:25 PM, Gobbledegeek <gobbledegeek at gmail.com>wrote:
>
>> Sorry I thought rag00l.xml would contain an exported list of  my settings
>> and preferences it didnt.
>> In any case attaching the subsurface.log of the successful import in case
>> you need it to debug what went wrong.
>>
>> Also listing how my Hollis DG03 reads which is quiet at variance with
>> what subsurface imported. (date is wrong as well as depth).
>>
>> Dive 1 - 2nd Jan, time: 14:09 Temp: 27 Duration: 0:49 Max Depth: 23.6
>> Dive 2 - 2nd Jan, time: 17:29 Temp: 26 Duration: 0:56 Max Depth: 24.8
>> Dive 3 - 3rd Jan, time: 07:08 Temp: 26 Duration: 0:39, Max Depth: 24.8
>> *** shows 53.6 in subsurface
>> Dive 4 - 3rd Jan. Time, 10:46, Temp: 27 Duration: 0:51 Max Depth: 26 ***
>> Dive 5 - 3rd Jan, Time, 13:45, Temp: 27, Duration:0:47, Max Depth: 25 ***
>> wrong dates
>>
>>
>> HTH
>> Rahul
>>
>>
>>
>>
>> On Fri, May 23, 2014 at 2:53 PM, Gobbledegeek <gobbledegeek at gmail.com>wrote:
>>
>>> Thanks for the tip. I complied the latest subsurface, and it works now -
>>> partially.
>>>
>>> I have 32 dives logged in my new DC, but it only takes the last 5 from
>>> 2014 even when I select force download of all dives.
>>>
>>> Then dive 3 in the list shows a depth of 53.6!! This is a serious issue
>>> as it can mislead investigators in a post-dive accident analysis.
>>>
>>> ~/subsurface$ cat DiveHist.csv | awk -F"," '$5~"53.6"'
>>> "3","2014-01-03","07:08:00","34:00","53.645",,"88.253"
>>> "3","2014-01-03","07:08:00","34:56","53.645",,"88.253"
>>>
>>>
>>> Attaching the exported csv and my settings xml.  Please take a look.
>>>
>>> Thanks again.
>>> G0bble
>>>
>>>
>>> On Fri, May 23, 2014 at 1:22 AM, Tomaz Canabrava <tcanabrava at kde.org>wrote:
>>>
>>>> On Thu, May 22, 2014 at 4:41 PM, Gobbledegeek <gobbledegeek at gmail.com>
>>>> wrote:
>>>> > Ok so I got the latest snapshot of libdive computer and ran the
>>>> instructions
>>>> > to install it.
>>>> > Then I tried to get the latest subsurface from git and tried to build
>>>> it.
>>>> > But I get
>>>> >
>>>> > $/usr/src/subsurface$ sudo qmake
>>>> > Project ERROR: Package libgit2 not found
>>>> >
>>>> > So I am stuck here now.  Looking at libgit2 on the web I see a lot of
>>>> win32
>>>> > files. Not sure if this is a broken dependecy spec somewhere and If
>>>> this
>>>> > package is really needed on Ubuntu.
>>>> >
>>>> > what next? How do I fix the build error?
>>>> > Thanks
>>>>
>>>> it is needed for subsurface.
>>>> please, do not run qmake as sudo.
>>>> you can install libgit2-dev from the apt-repositories?
>>>>
>>>> > On Thu, May 22, 2014 at 6:48 PM, Gobbledegeek <gobbledegeek at gmail.com
>>>> >
>>>> > wrote:
>>>> >>
>>>> >> Thanks. I will try that tonight. Can you pointe to the CR that fixed
>>>> it?
>>>> >> I'd like to understand the specific background to this problem.
>>>> >>
>>>> >> G0bble
>>>> >>
>>>> >> On May 22, 2014 12:28 PM, "Jef Driesen" <jefdriesen at telenet.be>
>>>> wrote:
>>>> >>>
>>>> >>> On 2014-05-22 08:12, Gobbledegeek wrote:
>>>> >>>>
>>>> >>>> This issue is still pending resolution. I left on a dive vacation
>>>> and
>>>> >>>> forgot about sync'ing my DC after that. So far I've just been
>>>> using my
>>>> >>>> DC
>>>> >>>> for dives without logging.
>>>> >>>>
>>>> >>>> Now I am trying again on a fresh install of Ubuntu 14.0.4LTE.
>>>> >>>>
>>>> >>>> Here are the things I tried:
>>>> >>>>
>>>> >>>> $ ls -l /dev/ttyU*
>>>> >>>> crw-rw---- 1 root dialout 188, 0 May 22 11:24 /dev/ttyUSB0
>>>> >>>>
>>>> >>>> $ sudo chmod 0666 /dev/ttyUSB0
>>>> >>>> $ ls -l /dev/ttyU*
>>>> >>>> crw-rw-rw- 1 root dialout 188, 0 May 22 11:25 /dev/ttyUSB0
>>>> >>>>
>>>> >>>>
>>>> >>>> I tried making the above permanent on reboot with a
>>>> >>>> /etc/udev/rules.d/50-usbtty-rules file that read:
>>>> >>>> KERNEL=="ttyUSB*", MODE="0666"
>>>> >>>> but this resulted in my usb mouse and keyboard becoming
>>>> unresponsive on
>>>> >>>> reboot, so I removed it.
>>>> >>>>
>>>> >>>> Then I tried the instructions by Jef given earlier when this
>>>> thread was
>>>> >>>> active:
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>> it seems modem-manager thinks you just connected a modem and takes
>>>> the
>>>> >>>> device. you could create an udev rule to blacklist some usb serial
>>>> >>>> devices. look at (something like, probably /usr/lib)
>>>> >>>> /lib/udev/rules.d/77-mm-usb-de
>>>> >>>> vice-blacklist.rules
>>>> >>>> then create a similar file in /etc/udev/rules.d containing the
>>>> pid/vid
>>>> >>>> of your divecomputer
>>>> >>>> <<<
>>>> >>>> $ lsusb
>>>> >>>> Bus 001 Device 014: ID 0403:f460 Future Technology Devices
>>>> >>>> International,
>>>> >>>> Ltd
>>>> >>>>
>>>> >>>> with  /etc/udev/rules.d$ cat 50-divecomputer-blacklist.rules
>>>> >>>> ATTRS{idVendor}=="0403", ATTRS{idProduct}=="f460",
>>>> >>>> ENV{ID_MM_DEVICE_IGNORE}="1"
>>>> >>>>
>>>> >>>> and
>>>> >>>> $ sudo stop modemmanager
>>>> >>>>
>>>> >>>> No luck.
>>>> >>>>
>>>> >>>> So to summarize:
>>>> >>>> 1. Adding my user to dialout group did not work
>>>> >>>> 2. stopping  modemmanager did not work
>>>> >>>> 3. Adding a blacklist rule for my device did not work.
>>>> >>>>
>>>> >>>> Any other ideas to fix this? I tested with windows using the hollis
>>>> >>>> software and it works.
>>>> >>>
>>>> >>>
>>>> >>> You are referring to solutions for the access permissions on the
>>>> >>> /dev/ttyUSB0 device node, but at the same time you attach a logfile
>>>> that
>>>> >>> indicates you are able to open the device successfully. So that
>>>> means
>>>> >>> whatever you did to the /dev/ttyUSB0, it already worked!
>>>> >>>
>>>> >>> To fix the high number of timeouts and NAK's during the
>>>> communication,
>>>> >>> you'll need something completely different. The libdivecomputer
>>>> master
>>>> >>> branch (v0.5.0-devel) already contains a fix for this issue. I
>>>> don't see any
>>>> >>> evidence of this fix in your log, so I assume you are using an older
>>>> >>> version. Upgrade and downloading should work again.
>>>> >>>
>>>> >>> Jef
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > --G0bbleDeGeek
>>>> >
>>>> > _______________________________________________
>>>> > subsurface mailing list
>>>> > subsurface at hohndel.org
>>>> > http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
>>>> >
>>>>
>>>
>>>
>>>
>>> --
>>> --G0bbleDeGeek
>>>
>>
>>
>>
>> --
>> --G0bbleDeGeek
>>
>
>
>
> --
> --G0bbleDeGeek
>



-- 
--G0bbleDeGeek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20140523/ea1d3ff4/attachment-0001.html>


More information about the subsurface mailing list