Page 1 of 1

Oceanic DataMask temperature still incorrect in 2.0.2

Posted: Mon Aug 30, 2010 6:44 am
by ArcticMoose
I deleted the offending dives, installed 2.0.2, restarted the (Mac) computer, and reimported the dives. A few of the dives still show highly incorrect temperature data.
Oceanic DataMask temperature incorrectly imported into 2.0.2.
Oceanic DataMask temperature incorrectly imported into 2.0.2.

Re: Oceanic DataMask temperature still incorrect in 2.0.2

Posted: Mon Aug 30, 2010 6:49 am
by nick
Have you sent me a dump of your device?

I just loaded up the only datamask dump I seem to have, and it all parses correctly. I may have fixed that recently though :) I could do with a memory dump from you, to verify everything looks ok.

But otherwise, the next release should fix it up.

Re: Oceanic DataMask temperature still incorrect in 2.0.2

Posted: Mon Sep 20, 2010 6:06 pm
by ArcticMoose
Sorry for the delay, I have been busy moving from Australia to Sweden.

I updated to 2.0.3 and reimported the last 25 dives, but am still seeing the same issue.

I just uploaded a dump here, but as far as I could tell DataMask was not available, so I used the Atom2 backend:
https://files.me.com/breneman/yq20k4

Re: Oceanic DataMask temperature still incorrect in 2.0.2

Posted: Mon Sep 20, 2010 9:35 pm
by nick
Ah. Cheers for the dump - yes, I see the problem. Fixed for the next patch. All looks good vs Oceanlog now.

Re: Oceanic DataMask temperature still incorrect in 2.0.2

Posted: Sat Sep 25, 2010 5:15 am
by ArcticMoose
Excellent, thanks!

Re: Oceanic DataMask temperature still incorrect in 2.0.4

Posted: Sat Nov 06, 2010 11:35 pm
by ArcticMoose
I have just had a chance to re-import into 2.0.4. It is almost there, but a few of the low temperatures look wrong to me. I do not currently have access to Windows, so I haven't compared to Oceanic's software, so there is always the possibility that the data is wrong.

Re: Oceanic DataMask temperature still incorrect in 2.0.2

Posted: Sat Mar 05, 2011 11:49 am
by nick
I was just taking another look at this, and the data is correct as per Oceanlog, even though it looks like it might be wrong in reality. So it could just be bogus readings, or there could be something else going on that Oceanlog isn't aware of either.