forum.heinrichsweikamp.com

Hum, this never happened to me (about 1000 dives with an OSTC).

Kind regards.

What gas was the dive on, i.e. what gas was selected on the OSTC?
Can you post a screenshot from the dive profile from the logbook?

OK, that makes it harder to tell what happened...

When the logbook itself (list of dives, time & depth per dive, CNS before & after, batt level, ...) is avail, put not the profile, thisis most likely that the profile storage is full and new dives overwrite the oldest ones. That because the statistical data have fixed size and one can pompute now many dives can be stored before the oldest one gets overwritten. The profile data go into a separate storage space and the amount of memory used for a dive depends on the length of the dive and how many parameters are recorded (e.g. CCR mode produces more data than OC). So both memory areas start overwriting (replacing) oldest dives at different times.

What i was after, is to see which gas was selected on that dive. Going up to 97% CNS on such shallow depth smells like (accidentially) O2 (or a very rich Nitrox) was selected. Anyhow, the calculation works, has been proven on thousands of dives done with the code. The calculation is also full independent of any logbook issues that may exist, as during dive mode, logbook is write-only, no data from the logbook go into any part of teh dive calculations.

Maybe there is a pressure sensor issue and the OSTC stayed in dive mode, clocking up CNS %. There are many possibilities, so i can only recomment to go though all settings and check them. Ah, and i assume the was no battery issue during the dive (batt drained), as this may corrupt data.

Well then, honestly, give the computer a full reset (Erase Logbook, Tissues and then Reboot). Maybe your unit captured a neutrino (= once in a billon bit flip somethwere in RAM), i don't know.