Firmware >V1.91does not save more profile data

[brabbel]

Hi

I have made 9 dives with firmwares 1.93 and 1.97. Although the OSTC dumps more memory (64kb instead 32kb) the additional memory is not used for saving more profile data and more dives.
Today my logbook in the OSTC contains about 245 minutes of profile data with a sampling rate of 2s for depth and 10s (factor 5) for everything else. With these sampling rates there should be memory for about 500 minutes of profile data.
I have attached two memory dumps before and after my last dive. The older dump shows a lot of free memory (FF). In the newer dump the oldest dive has been erased although memory should be sufficient and a new dive was added.

Regards
Brabbel

[heinrichsweikamp]

Hi,

Thanks for the report, you have two end-of-memory marker in your OSTC memory resulting is unexpected behaviour when new dives are stored. This is most likely the result of a buggy conversion routine and can only be fixed with a Logbook-Reset (Deleting all dives...), sorry.

We have tested the new logbook with a flat memory and the OSTC actually is using the 64kB then but it should also work with the converted memory, of course.

I'll look for this issue...

regards,
Matthias

[brabbel]

Hi,

yes I already recognized these 2 end-of-memory marker with my profile parser but I thought they exists due to the firmware update. So, a correct logbook memory contains only one end-of-memory marker?
I have attached the memory dump before and after the firmware update, maybe it helps with bug-tracking.
I will do a logbook reset ( that's the faith of beta tester) and see whether more profile data is stored. But this will need some weeks to fill up the logbook again.

Regards,

Brabbel

[heinrichsweikamp]

Hi,

This is full-service bug reporting, thanks a lot

ostc-20110715.data has one marker
ostc-20110716.data has one marker
ostc-20110817.data has two markers <- Wrong!

Conclusion 1: Conversion went fine.
Conclusion 2: Then something went wrong...

Question: How many dives are between the last two?

Cheers,
Matthias

[brabbel]

Hi Matthias

I have tracked down the dive where something went wrong.
I have attached 2 dumps in between one dive was made. The first one has one end-marker, the latest two end-markers
I hope this helps you finding the reason.

Regards
Brabbel

[Solodiver]

Is there any news in here? Running 2.0 I've still only 7 dives in the logbook (some of then done with 1.9x). Is there any action needed in case the logbook got corrupted running a beta firmware? Is there a check done in the new firmware or will this be self adjusted when the last 1.9x dive is overwritten? I did not reset the logbook so far...

Thx,
Jan

[heinrichsweikamp]

This will solve automatically with your new dives overwriting the old ones.

Regards,
Matthias

[Solodiver]

Using a high sampling rate my unit is now showing 9 dives with around 730 minutes in total, old dives are not overwritten yet - so this issue seems to be solved, Thx.

Jan