forum.heinrichsweikamp.com

Second time I've got this with the previous version of 1.30(just seen there is a new one):
after a OC dive on air I want to take a look in the logbook, so far so good.
But after I enter the dive I want to have a look at(to see the graphic of the dive etc...), the dive profile opens up and starts writing the diveprofile for a few seconds and then the OSTC suddenly stops displaying anything, and won't start up again untill I do a full reset with the USB interface, but then I have the problem that my no fly time and saturation are resetted to zero.First time I had this I looked at the dive with Jdivelog: no probelem to get the dive out of the OSTC, but looking at the profile with the OSTC gives the same problem every time I've tried.

What should I do with this? just not look into the logbook or try with reloading the software again??

Could I help you with putting the debug on and try and see the debug code I get(hopefully I will see something since the OSTC shuts itselves down when looking into the logged diveprofile...

Hello,

You have probably one corrupted dive from a previous version in the memory.
- Download dives with JDivelog/Divinglog
- Open a dive that can be displayed fine (or create a new one with the simulator)
- Select "Delete all" to format the erroneous memory

Sorry, no better solution to this.

regards,
Matthias

Hello, deleted the dives,installed firmware 1.30, and made a computer dive(simulation) to 55m on air and followed the decostops.
Went to logbook on the OSTC, the problem still consists...
Opened JDivelog, no problem to get the Dive from my OSTC...
Tried again with installing firmware 1.22, same result...
What should I do????

Grtz, Alain.

Hello, problem seems to be solved by deleting all the dives, and installing V 1.30 and resetting to default(CF values back to default values).
Done a few test- dives with J-divelog and seems to be fine now.
After I've done that I've changed some CF values again to see if I could generate a bad dive again... No...
Will try some more but seems to be solved...

Hello,

Thanks for the feedback! We also did not notice these problems again with newer versions.

regards,
Matthias