Corrupted logbook with 2.09beta

[Iglooz]

Hello,

I had a really strange behavior yesterday eve with the 2.09beta release while I was teaching a beginner in a 20m diving pool pit (19.3m 28' : forgotten to reset the salinity ;o) ).

Everything went well during the dive but during the debriefing my 2N turns crazy when I tried to show my student the dive profile from the logbook:
• First the OSTC got stuck for more than 20min with a "wait …" message in the top right corner
• Then it has given me back the control but any action with the logbooks were really slow
• The last but also all the previous entries in my logbook were corrupted: the index list was ok but the profiles were showing use of all gas with crazy profiles.
• I have rebooted my OSTC and it has turned back to life all the previous entries in the logbook except the last one (see capture).
• Now, back home, when I try to download the profile into DivingLog 5.06, a message explains that an index is out of range (should be positive and lower thant the size of the "collection" ... ) and the download is blocked.

To get into this state, I had several dives with 2.01 and then 3 or 4 dives with 2.06beta and then the last dive with 2.09beta.

Any idea of :
• What went wrong ?
• How to correct it before the next official release?
• How can I recover my OSTC to be able again to download my diving profile to my PC?

Iglooz (OSTC 2N 2755)

[Solodiver]

Lucky Me is not having any of these issues running 2.09 so far...

[fishwithlungs]

Yep.

Should have looked in the forum on 31st. On that day after very shallow dive for 37min or so the computer did exactly the same.20min 'wait...'then unbelievable profile,on mine the 'deco green'goes all the way to the top of the screen,temp and depth similar graph as yours.
I didn't really bother connecting in the evening
Next day on first dive of the year the computer turned itself on 22 minutes into the dive after fast blinking red led stopped,same as with the logbook the previous day.
That has happened before,after upgrading to 2.03.Dive profile in logbook loaded in about 20 sec,instant descend to the depth then real profile from 20th minute onwards.Dive data stating correct depth and time.
Again i didn't try to connect to pc.
Today my MK2 died.
Dive time 2 min,depth 4.5m low battery then blank.Before the dive 3.97V.
About 15min after dive i got screen with :


Unexpected reset from
Divemode!Please help
and report the Debug
Information below!
1 ACOBpA. 36 15
32 72 104 16 128
0 0 32 64 64

Just after scribbling debug into wetnotes screen flickered and dimmed to blank.
On press of Menu button white screen with a lot of dead pixels for cca 5 sec then dimmed to black and that's how it is.
Connecting charger turns MK2 on(a few seconds white with dead pixels,then standby),battery 3.94V,gas correct,date 05.05.11 and flickering screen(like an analogue TV,vertical stripes running from right to left),orange led blinking irregularly.Disconnecting usb turns it black.

Interestingly with one update max temp was up to 88 degrees,this time with 2.09 min temp went down to -45!

Looks like it's shipping time,very sad.

Sorting the download is simple,downgrade to 2.00,download logbook,get back to whatever version you prefer.Had to do this with each beta since 2.00.

Anywhere else where I should post the Debug Info?



Cheers,

Richard

OSTC MK2 385

[Iglooz]

Hello,

Sometime knowing about the future is not that nice

I hope to find a solution before my "Precious" dies too …
At least, it is nice to see that I'm not alone !!

As you suggested, I've tried to get back to the last official release (2.01 as I can't find any trace of 2.00) but it is still the same: my 2N seems to work (at least in surface mode) and except for my last dive, the logbook is OK but the last one is still corrupted (same as on my first screen-dump).
As suggested by Matthias, I then try to test the last 2.10beta : still the same

If it can help, I shall admit that diving is just a hobby and my "shameful" main activity remains embedded software development. I'm more used to play with PPC but I'm a complete newbie with PIC and fill naked without a JTAG probe. .

I don't know if the last correction is supposed to avoid the corruption of logbook or if it is supposed to deal with already corrupted logbook : much about workaround of a timer issue but I have to learn more about this piece of code and I still can't see how it can help in the reading of the logbook.

I've pulled the last version of the source code from Bitbucket and then build and uploaded my own version of the current 2.11alpha : still the same ….

It just looks like the logbook-parser misses a datum and parses the rest of the EEPROM as if data were belonging to the current logbook ??? It would confirm the Divinglog error code when I try to upload logbooks : "The index is out of range : it shouldn't be negative and shall remain lower than the size of the array. Name of the parameter: index". -1 is often the default value of an EEPROM after erasing it. I don't know the structure of the logbook and can't see what could be this index but -1 could be a good start to explain this kind of behavior.

At least, on the OSTC side the behavior during the download looks ok with the classical succession of : "Start", "Data", "Header", "Profile", and then a fugitive "Done."

If I try to download my logbooks with Subsurface, I don't get any error. But my entire dives are downloaded except the last and corrupted one….

If I can be of any help, fill free to contact me: next dive Saturday the 14th, always in the same 20m pool pit…
I don’t' really need a dive computer for that but it remains a nice place for safe experimentation ;o)

Iglooz

[JeanDo]

@Iglooz

Did you try to reset your logbook ?

[Iglooz]

Not yet, in case my record could be of any help to sort this issue ...

But the experience of fishwithlungs is not that attractive and a logbook reset is probably what I will do before my next dive, assuming that this last entry in my logbook is definitely dead but it should not happen anymore with firmware >= 2.10.

[Iglooz]

Hello,

I'd just like to let you know that after resetting my logbooks and moved to v211_alpha_543_0def530863c2, I dived yesterday in the same pool pit (probably with a profile really similar to the previous dive) and this time no problem at all.

My 2N is working well and I can download my profile in DivingLog and Subsurface.

So, to people that are experiencing similar logbook issues with beta releases > 2.01, I might suggest the same workaround:
1) Reset your logbook
2) Move to a more recent firmware (at least >= 2.10).

I hope this could help !!