Cressi Leonardo Import

[Philip Youdale]

I have two laptops - a Macbook Pro, and a Macbook Air - the Macbook Pro is running OSX 10.11.6 (because it is a little long in the tooth now) and the Macbook Air is running the latest OSX 10.12.3 update. Both are running with the latest Subsurface v 4.6.3 installed.

I also have two dive computers - a Mares Smart and a Cressi Leonardo (one mine, one belongs to my partner). We have the proprietory interface for both dive computers.
Both the computers also have the latest Silicon Labs driver installed.

The Mares Smart will download without a problem on either computer.

The Cressi Leonardo will download on the Macbook Pro, but not on the Macbook Air. On the Pro, the Cressi device or mount point option pops up (along with a choice of others of no relevance) as soon as I choose the dive computer on the import dialogue - but on the Air I get two "device or mount points" options - neither of which is relevant (one a bluetooth option, and one a wifi option to wifi on my iphone)

The USB on the Air is recognising the Cressi interface -

CRESSI PC INTERFACE:

  Product ID:    0x87d0
  Vendor ID:    0x0403  (Future Technology Devices International Limited)
  Version:    6.00
  Serial Number:    00002629
  Speed:    Up to 12 Mb/sec
  Manufacturer:    CRESSI
  Location ID:    0x14100000 / 9
  Current Available (mA):    500
  Current Required (mA):    90
  Extra Operating Current (mA):    0

It is in fact identical information to that shown on the Macbook Pro. On the Macbook Pro, the device or mount point option is given as /dev/tty.Cressi-port-00002629, but that is not even close to the two options on the Air.

While it is true that we can get the information, and it is not the end of the world, we travel with the Macbook Air, which means that the log files cannot be downloaded until we get home - which means that all the editting must take place at home (where time is at a premium), and not while on the dive trip (where we have a little bit more time on our hands).

So, does anyone know what I might be able to do to be able to download to the Macbook Air? Any suggestions appreciated.

[Jef Driesen]

On 26-03-17 04:23, Philip Youdale wrote:
> I also have two dive computers - a Mares Smart and a Cressi Leonardo (one mine,
> one belongs to my partner). We have the proprietory interface for both dive
> computers.
> Both the computers also have the latest Silicon Labs driver installed.

For the Leonardo you need the FTDI driver, not the Silicon Labs driver. You usb
log already show that:

> The USB on the Air is recognising the Cressi interface -
>
> CRESSI PC INTERFACE:
>
> Product ID: 0x87d0
> Vendor ID: 0x0403 (Future Technology Devices International Limited)

> [...]

That's an FTDI chip.

> It is in fact identical information to that shown on the Macbook Pro. On the
> Macbook Pro, the device or mount point option is given as
> /dev/tty.Cressi-port-00002629, but that is not even close to the two options on
> the Air.

This indicates the FTDI driver is missing. The above is the USB device
enumeration info. That is available as soon as you connect the PC interface. But
the /dev/tty.* device node only appears when the driver gets loaded. So just
install the FTDI driver, and it will probably work

Jef

[Philip Youdale]

Finally got this sorted. I tried and tried, without success, to install the FTDI driver, but could not get it to work. Then I had an epiphany - and installed the Cressi Leonardo interface from the Cressi support website (not that I wanted to use the Cressi interface, but my logic was that it must also contain the required driver). A few minutes later, i was downloading the Leonardo with Subsurface! Problem solved effortlessly. Thanks for your help in solving the problem for me, Jef

[Jef Driesen]

On 2017-06-03 10:02, Philip Youdale wrote:
> Finally got this sorted. I tried and tried, without success, to install
> the
> FTDI driver, but could not get it to work. Then I had an epiphany - and
> installed the Cressi Leonardo interface from the Cressi support website
> (not that I wanted to use the Cressi interface, but my logic was that
> it
> must also contain the required driver). A few minutes later, i was
> downloading the Leonardo with Subsurface! Problem solved effortlessly.
> Thanks for your help in solving the problem for me, Jef

Oops, I forgot to mention that. The Cressi Leonardo uses an FTDI chip
with a custom USB VID/PID, and hence the standard FTDI driver won't
recognize it. You need a modified version with the Cressi VID/PID added,
like the one shipped with the Cressi application.

Jef