Hi Dirk, I'm sure that this problem will solved. It's clear that is anyway a Shearwater problem or an undocumented feature. The interim solution proposed by Anton is already a good step forward. BTW you will not find a patch: Anton just posted a "diff". You will find everything here:
https://github.com/Subsurface-divelog/subsurface/issues/971 As you see my report is dated back on december 2017. I cannot blame nobody except my self for being lenient checking my profiles after discovering that bug. On the other side I know well how open-source projects works. People write code or generally help (like me) for what is important for themselves and not so quickly for other things that are not so important for themselves. No one gets paid for the work, so one cannot force anybody. Hence this bug was thought provoking for me. I've been always a minority but with a divecan shearwater controller I thought I was mainstream but I was wrong. This bug hit me hard. I have over 60 ccr maniacally logged dives with completely wrong or missing pO2 samples. A CCR dive without pO2 samples is like a cake with no sugar. If I still have them on my Petrel (I never investigated how many profiles it stores) I should import everything from scratch into Subsurface and compile everything again. Not a nice perspective for the future. Right now I'm diving two/three times per week so the count will increase rapidly. I've tons of notes, wrecks positions, all dives have GPS locations... I think I will use Shearwater desktop for the time being and leave old dives in Subsurface. When a complete solution will be found I will evaluate how much effort is needed to realign everything because I do not see a real solution coming soon. Anton (and now Aaron) patches are blessed workarounds but don't solve the inner problem: for some mysterious reason, on some devices we cannot use/decode Shearwater data. Moreover other questions remained unanswered; In one year my unique Petrel was identified as 3 different devices with random number of sensors. My logbook is a mess and nobody knows the reason. Frankly speaking I think nobody with a shearwater petrel ccr controller knowing in advance this bug would use Subsurface as their logbook. My profiles shows 2,1 bar of pO2 at 80 meters. Nothing you would show to anybody. Months ago, given your good relationship with Shearwater, I warmly recommended to contact them privately asking info on this nasty behaviour of some devices. Bye -- Davide https://vimeo.com/bocio/videos _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
