log corrput, no data

[tdewilt2]

Hi,

the computer has worked for 200+ dives ok, now in 10 dives i have 2 dives that have "corrupt data" that i have problems downloading, i'm switching oc/cc now for a few times, thats the only change my side

teunn

[Thorsten]

Hi Teunn,

could you provide some more details regarding the corrupt data (peaks in log graph, not data at all etc.)? I assume the depth data is not visualized as graph (in OSTC log view) but the generic time / depth information are available?
The download of dives is still possible, meaning that the download process itself is not aborted? Just the interpretation of the downloaded for the coruppted dive files?

It should not matter if it is an OC or CC dive because the way data is written is the same way. I switch between the mode regulary and did not yet had a corrupted dive log.

A potential root cause for a failed write operation could be a very low battery voltage. Did you charge your OSTC during the last 10 dives? If not doing a full charging cycle could be a good first step to identify the root cause.

Kind regards,
Thorsten

[tdewilt2]

Hi thorsten,

i now have the same problem again, now i get a error in subsurface saying: DIVE1 : Error parsing the header : Data format error

i have 3 new dives on the computer, logbook in the computer is reading fine, but on subsurface mobile and on my laptop (mac) it does only download 2 dives

is there someting i can send you for mor information?

best regards
teun

[Thorsten]

Hello Teun,

if I understood correct then the log display at the OSTC is fine => no corrupted data graphs? In that case maybe something goes wrong during the data transfer to subsurface. Did you update the OSTC or subsurface SW before the problem showed up? What versions are you using?

Kind regards,
Thorsten

[tdewilt2]

Hi Thorsten,

using rte 3.4 with os 1.6.9
subsurface mac 6.0.5214-cicd-release
subsufrace ios 6.0.5365

after better inspection, the log on the OSTC has no depth or temperature data. so on the ostc there is a log entry but no graph data. there is however a max depth, avg, temperature , time and surface pressure (hPa)

i'm using the OSTC as a OC computer and as a 2nd monitor on my XCCR, but the last 3 dives where all OC, and the last dive is corrupt

no sw updates, 2 dives correctly downloaded, 1 error

best regards
teun

[Thorsten]

Hello Teun,

thank you for the version information. The missing graph data is pointing to a problem during storing the data. As posted last time a very low battery could be an issue.
Looking for different root causes: Was there a special situation / handling during the last dives? Did you, for example, store a bearing on the surface before dive or did you shortly return to surface after starting the dive? A gas switch shortly after descending? Other events (warnings) which could go into the log profile?

It is hard to identify the problem because it seems to show up very sporadic... I think it makes sence to add some diagnostic funtionality to the OSTC which will help us to identify root causes for such problems better.

Kind regards,
Thorsten

[tdewilt2]

no specifics this dive, no changes above water, no changes in the water, just (simple) diving

/teun

[tdewilt2]

Another incident, during the first dive computer was on CCR mode (but last dive was also OC) so switched to BO so the deco calculation works, during the surface interval switched to OC mode. Log of the 2nd dive has no data logged exept max depth and time (on the OSTC and on the computer/IOS)

in the meantime switched to latest FW versions

battery was at 85% after the 2nd dive (4.0V)

is the switching between CCR and OC related to the data loss?
is my battery going wrong?
is my memory going bad, or do i need to clear it?

[mikeller]

Hi Teun.

subsurface mac 6.0.5214-cicd-release

This is relatively old - try updating to the latest version of Subsurface from https://subsurface-divelog.org/latest-release/.

Ngā mihi
Michael Keller

[tdewilt2]

Already did, also to latest firmware

[swissdiving]

What FW version?

There is a bug in 1.7.0. I have the same problem. CCR dive details seem not to be recorded properly. I've provided some log details to HW.

OC logbook info seems ok.