forum.heinrichsweikamp.com

It looks like there is one logbook entry that contains invalid data: 0F000000000000000000000000FFFF00 This is the dive that should have number 710 at index 197. This particular entry does mess up the logic to find your most recent dive. It has number 65535 (0xFFFF), so it gets selected as your most ...

The error in the Subsurface 4.9.3 (16 dives) log file is a bug in subsurface. There is an error parsing the dive data. Subsurface handles that as a fatal error, and aborts the download. I believe this has already been fixed. This is already visible in the Subsurface 4.9.3-1331. (18 dives), because t...

Can you download again, but this time with the "libdivecomputer-Protokolldatei speichern" checkbox enabled? Email the logfile to jef@libdivecomputer.org, or attach it to the forum topic.

@Goose_66: You shouldn't get an "unsupported operation" error. Can you try to download your dives again with the "enable libdivecomputer logfile" checkbox enabled? Afterwards, send the log file, so I can see what is going wrong. @divemasterjaap: Enable the "Log Errors" ...

Both subsurface and macdive use libdivecomputer for downloading dives. So it's not unexpected you see the same problem in both applications. This particular issue has already been fixed in libdivecomputer, but the latest subsurface release (v4.9.3) is older and doesn't have this fix. If you can't wa...

I can certainly have a look a the download code. But for that, I need the libdivecomputer log file from a download with an OSTC4 computer that shows the problem. Both Diving Log and Subsurface have an option to create such a log file.

I can always use some extra data to test the workaround. To download the raw data from your OSTC, you can use the libdivecomputer command-line tool: https://libdivecomputer.org/builds/stable/windows/dctool.exe Download two times, using these options: dctool.exe -vv -l ostc3-download.log -f ostc3 dow...

Mutley Wrote: ------------------------------------------------------- > I have com > 12,13 for incoming connections and com 14 for > outgoing connections, but each time I attempt to > connect or download, i get the following response. > DC_STATUS_NOACCESS. The OSTC screen only shows > Starting.....d...

If you try again, do you get the same behaviour every time? The strange part is that it fails with a timeout, but when you look closer at the timestamps, there is no sign of a 3 second timeout. The entire session lasts only about 1.5 seconds. Are you able to download a full memory dump? dctool.exe -...

Libdivecomputer reports a gaschange on the first sample to indicate the initial gas mix. So if you join two dives in subsurface, that switch is probably the initial mix of the second half. If you join two dives with the same initial mix (e.g. Air), then the switch is basically a no-op (e.g. air to a...

tanomogi Wrote: ------------------------------------------------------- > * via dctool[dctool --family ostc3 --model 0x3B > --verbose --logfile dctool.log fwupdate --firmware > OSTC4_update_160919_V1_1_2__RTE_0_90.bin ] // > can't connect well > [pre] > [0.000373] DATETIME 2016-09-27T15:10:46Z > (14...

You can't. The OSTC4 protocol doesn't support memory dumps. What you can do is dump the individual dives:

dctool -v -l dctool.log -f ostc3 download -f raw -o dive.%n.bin

(The ostc3 option is NOT a mistake. The correct model is autodetected during the download.)

@tanomogi: Can you download the raw dives again, after you have upgraded to the new firmware? Just to confirm everything is working now.

tanomogi Wrote: ------------------------------------------------------- > dctool --family ostc3 --model 0x3B --verbose --logfile dctool.log download --output dctool.raw --format RAW /dev/tty.OSTC4-00051-SPP Can you retry again after changing "dctool.raw" to "dctool.%n.raw"? Witho...

tanomogi Wrote: ------------------------------------------------------- > * Subsurface import log time/date problem.(Win/MAC, OSTC4 v1.02 ~ 1.05) > - Subsurface doesn't show actual Date/Time field. > It subtracts duration. > E.G) 08 H 45 dive starts with duration 59 min , > subsurface date field sho...

AMM2T Wrote: ------------------------------------------------------- > tried Subsurface, which worked > once, but now reports 'error parsing date/time' > and the OSTC2 drops the bluetooth connection. If you enable the libdivecomputer logfile option in subsurface and send me the log file, then I'll h...

The OSTC4 is already supported in the latest version of subsurface. Changing settings may not work yet (because it works different compared to the OSTC3), but downloading your dives and upgrading the firmware should work fine.

The dctool application doesn't support changing settings. Maybe it will in the future, but not right now.

FYI, the command-line dctool application is also available for Mac OS X and Linux. Builds can be downloaded from the libdivecomputer website.

In theory, the lastest version of subsurface should support updating the OSTC4 firmware too, although I haven't confirmed that yet.

The available gas mixes in the dive data are configured as follows: O2%, Change depth, Type 21%, 0m, deco 51%, 15m, deco 21%, 0m, disabled 21%, 0m, travel 21%, 0m, disabled The problem is that none of them is marked as the first gas, and that causes the parsing to fail. In the latest libdivecomputer...

I support this feature! It might even be possible to implement this without having to modify the existing data format. We can discuss the technical details at the boot show this weekend.

Enable the "save libdivecomputer logfile" option, and attach (or email me) the logfile.

ChristofM Wrote:
-------------------------------------------------------
> I´m able to update the OSTC 2 with the companion,

On the exact same Windows 10 system? Or another one?

This appears to be the same problem as in this topic. Allthough we have configured a timeout of 20 seconds, the read operation already returns after less than a millisecond: [0.001389] INFO: Timeout: value=20000 ... [0.415721] INFO: Write: size=1, data=6D [0.512096] INFO: Read: size=1, data=6D [0.51...

When you start the Command Prompt, you are probably in a different directory then the one where the exe is located. Either you move the exe to the same directory, or you change the current directory of the Command Prompt.