MacDive Forums

I only need a memory dump of the dive computer (or the raw dive data if the dive computer does not support downloading a memory dump). There is absolutely no need to import any dives in Macdive! Macdive should have some kind of diagnostics feature for downloading a memory dump. But since I'm not a M...

Nick, I already added support for the i200 to libdivecomputer a few days ago. So no need to spend time on that anymore

It looks like the downloading itself is working fine. Maybe it's the parsing of the data that goes wrong. Can you email me the dctool.bin and dctool.log file?

@Nick: I have support for the i750tc almost ready
It's very similar to the vtx.

Has this been fixed, or is it not a libdivecomputer related problem? I haven't received any emails.

Have a look at this topic for instructions on how to collect the data that we need to fix such problems.

The newer Uwatec/Scubapro dive computers (e.g. Meridian, Mantis and Chromis) are no longer using IrDA communication, but standard usb-serial communication. That means compatibility with Mac OS X is no longer problematic. I suspect the Scubapro M2 (Mantis 2) is also on that list. So technically it's ...

If you don't mind using a command-line tool, you can always use libdivecomputer's dctool to upgrade the ostc firmware:

It's a command-line application. You first have to start the Windows Command Prompt, make sure the universal.exe is located the current directory (move it if that's not the case), and then type the command (I recommend copy-and-past to avoid typos).

[0.000855] ../../source/examples/universal.c:973: No matching device found. That's because you executed the application with the wrong options. Oops, I forgot to mention that. The correct options are: universal.exe -v -l vyper-dump.log -m vyper.bin -b vyper <COMx> universal.exe -v -l vyper-dives.lo...