Unable to access cloud storage and unable to download data from Suunto Zoop Novo

[Matt Ruglys]

Hi, I am using Subsurface 5.0.1 on a MacBook Air running macOS 11.2.3. Both are recent updates. Having used Subsurface quite satisfactorily for years today I was not able to access my cloud storage data (however the app on my iPhone can access the cloud data). Then when I went to download my dive from my Suunto Zoop Novo I got an error message (see attachment).

Any thoughts?

Thanks,

Matt

[Dirk Hohndel]

The cloud storage issue should be fixed.

The issue with your serial device is of course completely unrelated... macOS 11 disabled a lot of kernel drivers. I wonder if that includes the Suunto driver / actually likely an FTDI driver that you were using.

Has this ever worked since you updated to macOS 11?

/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/2cb66b36-e17c-4bb9-b804-41b1ce3b279dn%40googlegroups.com.

[Matt Ruglys]

The cloud storage is good now, thanks. This was the first time I had tried to connect the Zoop Novo to Subsurface since updating to macOS 11

[Matt Ruglys]

The data download problem with Suunto DCs seems to have happened before, ( https://groups.google.com/g/subsurface-divelog/c/RZV5OuBu_FE ) but Subsurface updates seem to have fixed it. I am now running macOS 11.3, nothing else has changed. From what I read there is an enduring problem with Big Sur and FTDI drivers. Is anyone else having this problem, and if they have got it to work - how did you do it? Thanks, Matt

[Linus Torvalds]

On Tue, Apr 27, 2021 at 6:39 PM Matt Ruglys <mattr...@gmail.com> wrote:
>
> From what I read there is an enduring problem with Big Sur and FTDI drivers.

Have you tried using just "FTDI" as the device node (instead of the
/dev/tty* ones)? That skips the OS serial driver, and uses libusb to
talk directly to the FTDI chip.

That seems to work for some people.

Linus

[Matt Ruglys]

Linus

Sorry but I have no idea how to do that! :)

Matt

--
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/CAHk-%3Dwh_jjS%2Bdak%2B_0FqyCWB42eKXw61rgZ0G35io0TJAJRV_A%40mail.gmail.com.

[Linus Torvalds]

On Tue, Apr 27, 2021 at 7:15 PM Matt Ruglys <mattr...@gmail.com> wrote:
>
> Sorry but I have no idea how to do that! :)

When you've selected "Suunto" and "Zoop Novo" as your dive computers,
just type in "FTDI" in the "Device or Mountpoint" box (instead of the
default /dev/tty.usbserial.. that shows up)

Linus

[Matt Ruglys]

Awesome, that worked perfectly, thank you Linus!

Matt

--
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/CAHk-%3DwhL5zmk18LXw7MaRUTpTMbEh4ugzxxvNaqT0qOp7RAdnQ%40mail.gmail.com.