Bug report: fails to start

[Turtle]

My unit now had failed to start/turn-on.

v1.30 (battery fully charged). 2 months old (serial 11-165)

I deleted all the logbook (kept the button pressed in for the 9 seconds). The log book then showed only one spurious dive and after deleting that, the machine then fails to turn-on. No life at all.

Will leave it for a while and then if it continues to not start, will return it to the reseller (in the UK).

Any view?

[heinrichsweikamp]

Hello,

Have you tried to reset (With the interface) the unit already? Deleting the logbook completely takes some minutes.

Regards,
Matthias

[Turtle]

Interesting. The reset brings the machine back to life; however, there is one dive still in the memory.

When I access that dive, the machine tries to show the profile and dies. Reset brings it back to life.

And this repeats.

Dive is: 01 17/11 30.1m 58'

(not one of my dives).

[heinrichsweikamp]

Hello,

Add a new dive with the simulator - open this dive and select "delete all" from the logbook menu again. 1.34 (published soon) will have some more maintenance functions.

Regards,
Matthias

[Turtle]

Did this,however,the problem is still there.

Added a new dive via the simulator and then did a delete all; however, it only deleted the new simulated dive.

The persistant "error" dive that cuases the machine to die is still there and causes the machine to die when accessed.

?

[heinrichsweikamp]

Hello,

Strange indeed - all other functions work fine?

regards,
Matthias

[Turtle]

Yes all other functions seem to work fine.

Am happy to wait until v1.34, if you think it may fix things?

[Turtle]

It definitely looks like the logbook memory is corrupted and with the false (and unable to delete) dive.

Also annoying is that it is not allowing any of the real dives to be downloaded. The downloader (using the downloader with DiverLog4) just shows the corrupted dive. The logbook function on the OSTC shows the real dives as well, but the downloader application can only see the corrupted false dive.

Is there anything that I can do to clear the logbook memory, so I can use the download function with the logbook?

If there is nothing I can do, I am happy to return the machine for examination.

Out of interest, here is the corrupted dive loaded into DiverLog4 - it would be one hell of a dive, if it was real!

[img]http://myfo.to/kQ1o.jpg[/img]

[heinrichsweikamp]

Hello,

Can you send us your email address again? I'd like to send you a special firmware which tries to get rid of that...

Ours is info@heinrichsweikamp.com

regards,
Matthias

[heinrichsweikamp]

Never mind

You have mail....

regards,
Matthias

[divinglog]

It looks like this is one of these dives with the deco issue at the end of the dive discussed in another thread. From minute 31 the profile looks normal and when you look at the end of the profile you can see the exact same issue we've seen in another posting here in the forum. First a deco stop ignored warning is stored followed by the deco flag itself.

Kind regards,
Sven

[heinrichsweikamp]

Hello Sven,

This is not surprising since the Deco flag is a normal sample information (Extended Information), configured with "Divisor Deco/NDL". "Decostop missed" is an Event in the EventByte (Bit2) which can be attached to every depth sample.

We decided to check the logbook memory chip at our place.

regards,
Matthias

[Turtle]

Machine is on its way to you, should get there in the next day or so.

Thanks for the quick support on this.

- Turtle