forum.heinrichsweikamp.com

One of my dives today was a very shallow dive (5 meters maximum depth).
After the dive, in the logbook, I noticed that the sample of 14 minutes (840 seconds) was incorrect. Instead of around 2.7 meters (as the sample before and after this one) it showed 0.01 meters, or 1 centimeter.

Has anyone else seen anything like this?

I´ve attached the raw data and a screenshot of the dive.

FYI, this happened using a beta, so it is clearly possible that it does not happen with the release versions.

The reason I´m asking is simply because I would like to find out if it´s a software issue or maybe the sensor failed to deliver a value briefly, making it a hardware issue.

Which version did you use? All reported pressure sensor fails failed in the other direction -> showing max. depth instead of zero. So, I don't think this is a sensor issue here.

regards,
Matthias

Even though I feel slightly embarrassed, I have to admit that this was using the current repository code (as of yesterday).
The purpose was to do some live testing of the new German translation.

Got one dive in today with 1.80, no anomalies in the samples there, clean as a whistle. But this dive was a little deeper (approx. 20 meters).

Just a hunch.

Could it be that it has something to do with the current 1.83 CPU time issue. i.e. it skipped the sample and thus reported it as zero?

D

That does not sound far-fetched at all, could be the case I suppose.

I´ll stick to 1.80 for the time being to see if I get any more weird samples.

In case anyone sees any samples like that with 1.83, please do let the rest of us know.

It happened again, this time in the other direction. Max depth according to the logbook was 13,25 meters. Then there is one single (10 second) sample of 15.29 meters. Max depth at that location is at around 13-14 meters, so 15.29 is impossible. See the attached screenshots.

Hello Nakatomi,

This terribly looks like the CPU time issue, corrected by patch 257 two weeks ago. Since then, there have been 50 patches made to implement new features and finish things up for the next 1.87beta...

So, can you tell use exactly what version did you use, and how you did compiled it ?

Cheers,

Hi JeanDo,

this happened on the 14th consecutive dive running changeset 282 -compiled in release mode. All the other dives were fine, so it seems to be very sporadic.

I´ll run the official 1.87 now and stick to that for a while to see if this returns.

Oliver