Need Help with downloading from UWATEC dive computer

[Oscar Steele]

Hi,

I am trying to switch to subsurface for my primary dive log software as it looks great.  However I am unable to download dives from my dive computer.

My Setup:

MacBook Pro (16-inch, 2019)

MacOS Big Sur 11.6.6

Uwatec Alladin Z Nitrox

Uwatec MemoMouse

I have two old USB to COM cables that I have successfully used in the past to upload to DiveTrack (running in a VM with windows) a long time ago

- An old IOGear (no idea the specific model #)

- SEWELL SW-1301

I have tried to download the appropriate drivers (no success with SEWELL) and attempted to import dive info from my comp with no success.  Both directly into subsurface running on mac os and into Windows 11 running in VirtualBox.  So I just bought a "USB C to RS232 DB9 Serial Port Adapter Cable(USB-C to Serial, USB C to DB9, USB C to RS232) with FTDI Chipset Supports Windows 10 8 7 and Mac Linux…" https://www.amazon.com/gp/product/B08B5M1KBZ/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&th=1

I installed both the VCP and D2XX drivers.  One at a time followed by a reboot.  Attempted to download using the FTDI mount point and the "/dev/tty.usbserial-4" and the "/dev/tty.usbserial-A9CF" mount points that show up in the subsurface download/mount point drop down.

In all cases, old and new cables, I get "Event: waiting for user action".  I put the computer in logbook mode, advance to the latest dive, and see the memomouse pulling all information, but the "Event: waiting for user action" never goes away.

I would appreciate any help in debugging this issue.

Note, while i have not (yet!) pulled the subsurface source code I am a software engineer with over 35 years experience (mostly in cybersecurity) don't be hesitant getting into the weeds with what is required to debug this.

Thanks

- Oscar

[Dirk Hohndel]

Hi Oscar,

I have no personal experience with the memomouse, so it's hard for me to help you - I had hoped that someone else who actually used that device might respond...

With your new cable and a recent Subsurface version on macOS you should be able to simply enter "FTDI" in the connection box, put the memomouse into PC mode (or whatever it is called when it is willing to talk to a computer) and then download.

One thing that often helps us understand what's going on is if you can select "save libdivecomputer logfile" in the download dialog, try the download, and then send us that file.

Thanks

/D

[Oscar Steele]

Thanks for the response.

The log file shows:

[1332.086612] INFO: Open: name=/dev/tty.usbserial-A9CFBQR1
[1332.095376] INFO: Configure: baudrate=19200, databits=8, parity=0, stopbits=0, flowcontrol=0
[1332.099836] INFO: Timeout: value=3000
[1332.099838] INFO: DTR: value=1
[1332.100387] INFO: RTS: value=0
[1332.120511] INFO: Read: size=1, data=00
[1332.120521] INFO: Read: size=1, data=E6
[1332.120524] INFO: Read: size=1, data=00
[1332.120526] INFO: Read: size=1, data=00
[1332.120529] INFO: Read: size=1, data=18
[1332.120532] INFO: Read: size=1, data=F8
[1332.120534] INFO: Read: size=1, data=18
[1332.120537] INFO: Read: size=1, data=7E
[1332.120539] INFO: Read: size=1, data=E6
[1332.120542] INFO: Read: size=1, data=7E
[1332.120545] INFO: Read: size=1, data=E0
[1332.120547] INFO: Read: size=1, data=60
[1332.120550] INFO: Read: size=1, data=7E
[1332.136664] INFO: Read: size=1, data=80
[1332.136682] INFO: Read: size=1, data=E0
[1332.136688] INFO: Read: size=1, data=80
[1332.136692] INFO: Read: size=1, data=18
[1332.136697] INFO: Read: size=1, data=00
[1332.136702] INFO: Read: size=1, data=E6
[1335.136728] INFO: Read: size=0, data=
[1335.136731] ERROR: Failed to receive the answer. [in src/uwatec_aladin.c:174 (uwatec_aladin_device_dump)]
[1338.137293] INFO: Read: size=0, data=

The last two lines repeat multiple times.

Im going to install subsurface on linux and windows VMs and see if that changes my luck.

[Dirk Hohndel]

Hi Oscar,

I have copied Jef, the maintainer of libdivecomputer who knows a lot more about the details of communication than I do... but looking at the source code for this driver... it seems that we are not getting the header data that we are expecting from the dive computer and are then giving up.

Jef, am I missing anything?

/D

-- 
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/f9765656-362d-4327-81c6-bd92b27f1022n%40googlegroups.com.

[Joe Friday]

You mention MemoMouse in your set up. Could that extra part be the problem? Have you tried a direct connection (or indirect?)  between your dive computer and your real Subsurface computer, not via the MemoMouse?

I have a slightly different custom setup that works reliably for Windows Subsurface. I have no knowledge of using a MemoMouse, but have been able to successfully "indirectly" download several models of the "old" DataTrak supported Aladins ( Aladin Pro, Aladin Sport, Aladin Pro Ultra, Aladin Pro Nitrox,  ) into Windows subsurface (but NOT Android!**) via a custom bluetooth hack Ardunio thingy***.

Regardless.. I am  very careful to initiate the download in Subsurface before I activate the Uwatec divelog on the dive computer. Sometimes it take several Uwatec finger pattern attempts to get Subsurface to recognize the download attempt. I am unsure if my problems are Subsurface issues of my bluetooth hack issues.  I believe most of my failed uploads are due to bad electrical contacts on the dive computer or my paper clip leads (feel free to spank me about paper clips, salt water and other things...).

**Android Subsurface denies an Uwatec Bluetooth connection. See *** below.

***I created a very simple Arduino based blob thing that watched for an Aladin download (the Aladin will ALWAYS push a download every time you pull up the dive log) and then spewed it over bluetooth. This approach has only worked with Windows Subsurface since Windows was dumb enough to present bluetooth as COM ports. Android Subsurface denied my direct Uwatec bluetooth connections since Subsurface claimed that Uwatec was not able to support bluetooth.

[Jef Driesen]

Oscar,

Are you trying to download directly from the Uwatec Aladin, or from the
Memomouse? Based on your explanation, it looks like you are downloading from the
Memomouse, but the log file clearly shows an attempt to download directly from
the dive computer. That's not going to work. If you want download from the
Memomouse, you should select the Uwatec Memomouse as the dive computer, and not
your Uwatec Aladin model.

Jef

On 28/05/2022 21:39, Dirk Hohndel wrote:
> Hi Oscar,
>

> I have copied Jef, the maintainer of libdivecomputer who knows a lot more about
> the details of communication than I do... but looking at the source code for
> this driver... it seems that we are not getting the header data that we are
> expecting from the dive computer and are then giving up.
>
> Jef, am I missing anything?
>
> /D
>
>> On May 28, 2022, at 5:29 AM, Oscar Steele <oscar.st...@gmail.com

>> email tosubsurface-div...@googlegroups.com
>> <mailto:subsurface-dive...@googlegroups.com>.

>> To view this discussion on the web
>> visithttps://groups.google.com/d/msgid/subsurface-divelog/f9765656-362d-4327-81c6-bd92b27f1022n%40googlegroups.com

>> <https://groups.google.com/d/msgid/subsurface-divelog/f9765656-362d-4327-81c6-bd92b27f1022n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>

[Oscar Steele]

Thanks Jef,

I totally did not notice memo mouse as an option for the dive computer type. That fixed my issue.  

- Oscar the inattentive