Trouble downloading Atom to Mac

[Stuart Vernon]

Greetings,

 

I am using a Macbook Pro Retina (late-2013). macOS 10.13.6. I have been using this Mac for several years, but I am really a Windows guy, so I don’t pretend to really have a good handle on things like installing and configuring hardware drivers on a Mac.

 

Subsurface 4.8.1

 

Oceanic Atom 3.0 dive computer with a brand new battery in it.

 

I have downloaded successfully from my Atom many times on both Windows and Linux. But, I am, so far, completely failing at downloading on my Macbook. In all cases (below), when I have the cable plugged in (whether via USB port on my monitor, or directly into the left side USB port on the Macbook), and I clip it onto the Atom, the Atom does go into PC download mode and start its 2 minute countdown.

 

In Subsurface, when I select to download and choose Oceanic and Atom 3.0, the only “Device or mount point” it offers is: /dev/tty.Bluetooth-Incoming-Port

 

There are no other choices in the dropdown and clicking the “…” button does nothing. If I click Download, it gives some error that it couldn’t open the port. My suspicion is that tty.Bluetooth-Incoming-Port is not the port it should be using, so I’m not surprised by the error. I just can’t see how to get the correct port to show up there.

 

I found that the official Oceanic answer is to use Diverlog, so I installed Diverlog Lite and tried to download using that. It told me to install the USB driver and took me to a page on the PPS website. I downloaded and installed the indicated driver package and rebooted. Diverlog will not download, either. It recognizes that the Atom data cable is plugged in – there is a dialog where it tells you to plug it in and the Next button is greyed out until I do plug it in. But, when I click Next enough times and it starts trying to download, it just sits there forever at 0%.

 

I did some more searching and found the libdivecomputer website and its recommendation for drivers. There was an implication that the drivers there might be newer and work better, so I downloaded and installed that package also. And then rebooted. It made no difference to anything.

 

Does anybody have any suggestion for me on how to get this to work?

 

Thanks.

 

• Stuart

[Stuart Vernon]

One more try. I didn’t get any response the first time I sent this out.

 

Anyone?

 

Any idea what the USB download port should be?

[Dirk Hohndel]

The symptoms look like you are missing a driver for the download cable on your Mac.

The Oceanic Atom official cable is FTDI based, so you’ll need an FTDI driver. You said you installed it and rebooted. I wonder, is the FTDI driver actually loading correctly?

kextstat | grep FTDI

Are there any serial devices showing up?

ls -l /dev/tty.usb*

BTW: this has been discussed in this group many times, e.g. here: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/subsurface-divelog/3K2ztbJhiRw/4bTEMc5vAgAJ

Maybe that’s why no one responded?

/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 post to this group, send email to subsurfac...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/99C0A2EC-3B26-4CEF-9F98-69E1F0ADDBFE%40force2.net.
For more options, visit https://groups.google.com/d/optout.

[Dirk Hohndel]

We should really keep the conversation on the User Forum so the next person can find it….

Thanks for the help, Dirk.

 

When I attempt kexstat, I get this:

 

EHR1-DEV-MAC:~ svernon$ kexstat | grep FTDI

-bash: kexstat: command not found

That should be /usr/sbin/kextstat

That’s the tool that tells you what kernel drivers are loaded.

 

Also, this:

 

EHR1-DEV-MAC:~ svernon$ ls -l /dev/tty.*

crw-rw-rw-  1 root  wheel   21,   0 Aug 10 10:44 /dev/tty.Bluetooth-Incoming-Port

This is with your dive computer plugged in? You should see a port for it right there. Until you do, no software will be able to talk to your dive computer

 

I installed the driver from the PPS site and the driver from the libdivecomputer site.

 

The DMG from the PPS site is called 2002Design_Driver.dmg. The file it contains is called FTDI_Driver.pkg. I have installed that.

 

The DMG file from libdivecomputer.org is called FTDIUSBSerialDriver_v2_4_2.dmg. The file it contains is called FTDIUSBSerial.pkg. I have also installed that.

 

…at least, as far as I know. On a Mac, I don’t know how to check what drivers are installed.

See above. Clearly, the problem is that installation.

 

It also occurred to me that I should possibly uninstall the PPS driver (or both, and the reinstall just the driver from libdivecomputer). But, I don’t know how to uninstall a driver from the Mac, either.

Typically the installer pkg offers an uninstall option. Also, there’s always this: http://www.ftdichip.com/Support/Documents/InstallGuides/Mac_OS_X_Installation_Guide.pdf

 

I looked at the Subsurface website and manual for this info and didn’t see it. I didn’t think to search the Google Group. I will see if I can find help there.

We’re always happy to help. There have been many others before you who ran into problems with this particular driver

/D

[Linus Torvalds]

On Fri, Aug 10, 2018 at 9:52 AM Dirk Hohndel <di...@hohndel.org> wrote:
>
> This is with your dive computer plugged in? You should see a port for it right there.
> Until you do, no software will be able to talk to your dive computer

.. actually, that's not true.

I think we should just accept the fact that

(a) FTDI on OSX is a pain because clearly the driver situation is
very confusing. It's not like this is the first time the issue comes
up.

(b) we already use libusb for other dive computers.

which to me says "why don't we just enable the user-space FTDI support
on OSX too"?

What do you think? Wouldn't that work?

Linus

[Stuart Vernon]

I was only taking it “offline” because of concerns about posting my laptop name on a public forum. So, never mind…

 

Kexstat returns no results.

 

I uninstalled the PPS drivers and the libdivecomputer drivers (by finding the kext folders, right-clicking in Finder and choosing Send to Trash), rebooted (and verified the drivers were gone), installed the libdivecomputer drivers again (v2.4.2), rebooted again.

 

Still nothing. One time, when I plugged the cable in, VMware Fusion (which was running at that time) popped up and asked me if I wanted to connect the USB device to the Mac or Windows. I chose Mac and don’t ask me again. On subsequent tests, I didn’t even have VMware running.

 

So, it’s clear the Macbook recognizes that the cable is plugged in. It seems that it’s just not loading the FTDI driver. And I don’t know how to make it.

 

From: Subsurface Group <subsurfac...@googlegroups.com> on behalf of Dirk Hohndel <di...@hohndel.org>

Reply-To: Subsurface Group <subsurfac...@googlegroups.com>
Date: Friday, August 10, 2018 at 12:52 PM
To: Subsurface Group <subsurfac...@googlegroups.com>

--

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 post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/86B085D6-CDFA-4780-B338-9A2C65AFE7F9%40hohndel.org.

[Stuart Vernon]

I just wish I had the patience to distill this experience down into a short-ish document and then hand it to everyone who ever told me "Macs are better than Windows. They're so much simpler. You just plug stuff in and it works!"

--
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 post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/CA%2B55aFyu7P9_f%3DwwbnNoJ6SDU7N%3DY3isbUhOB%2B5iA6b7y4tLOw%40mail.gmail.com.

[Dirk Hohndel]

I have no idea if that would work. It certainly seems worth a try given
how many people run into problems with that.

/D

[Anton Lundin]

I haven't tried it, but the libftdi code works just fine in linux, and I'll guess it works on mac os x to. Its simple to just compile it in, and let the user have the option to test it out.

//Anton 

[Jef Driesen]

It should work fine. To workaround all those driver problems, Macdive also
switched to using a userspace driver, and I know Nick is very happy with that
solution.

Jef

[Stuart Vernon]

I’m happy to test anything you like. I had a working dev environment setup on my Linux laptop. But, I have retired that machine (which is why I’m now trying to download from my Atom on my Macbook). I have never attempted to do any kind of development work on my Macbook (other than my day job programming, which I do all in Windows VMs, some running on the Macbook). But, I am game to even go as far as setting something up on my Macbook so I can build it myself and try whatever you like.

 

Of course, if somebody else wants to just do the build and send me a download link, that is fine, too. 😊

 

From: Subsurface Group <subsurfac...@googlegroups.com> on behalf of Anton Lundin <an...@lundin.pp.se>

Reply-To: Subsurface Group <subsurfac...@googlegroups.com>
Date: Friday, August 10, 2018 at 3:57 PM
To: Subsurface Group <subsurfac...@googlegroups.com>

--

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 post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/ba34d8de-1a9c-481b-81c3-fcbc03026824%40googlegroups.com.

[Dirk Hohndel]

I’ll play with creating a build - but it may take a few days as I’ll want to make sure that this actually works with at least the one FTDI device that i have access to :-)

/D

[Linus Torvalds]

On Fri, Aug 10, 2018 at 1:06 PM Dirk Hohndel <di...@hohndel.org> wrote:
>
> I’ll play with creating a build - but it may take a few days as I’ll want to make sure that this actually works with at least the one FTDI device that i have access to :-)

Note that the one reason it _wouldn't_ work is if you have the ftdi
driver natively installed. I suspect then the user space driver could
easily fail simply because the kernel already claimed the device.

I definitely know the ftdi driver builds on Linux, because I did the
build testing when I switched over to the new IO world order. I would
assume OSX has no differences in this area, it's all just libusb, I
think.

Linus

[Dirk Hohndel]

On Aug 10, 2018, at 1:06 PM, Dirk Hohndel <di...@hohndel.org> wrote:

I’ll play with creating a build - but it may take a few days as I’ll want to make sure that this actually works with at least the one FTDI device that i have access to :-)

Umm. OK. This was embarrassingly simple. Why again didn’t we do this ages ago?

Stuart, please do the following:

First, make sure all FTDI kernel drivers are actually gone. Instructions how to do that are here:

https://apple.stackexchange.com/questions/166906/how-can-i-uninstall-the-ftdiusbserialdriver

that first answer appears to do the trick for me.

REBOOT. Very important.

Then, download the test build I just posted:

http://subsurface-divelog.org/downloads/test/Subsurface-4.8.1-151-gb9fcc9543dac.dmg

run the Subsurface on that DMG and try to download from your Atom. Make sure to overwrite the “Device or mount point” entry with “ftdi” (just the four letters, no quotes)

I tried this here and it seems to work just fine…

Please let us know how it goes.

/D

[Stuart Vernon]

Okay, that worked. Yaayy!!

 

One oddity, it downloaded (apparently) all the dives from my computer – including ones that were already downloaded from that computer and stored in my log. I unchecked all the extra ones and just imported the new ones. Seems to be all good.

 

Thank you!

 

From: Subsurface Group <subsurfac...@googlegroups.com> on behalf of Dirk Hohndel <di...@hohndel.org>
Reply-To: Subsurface Group <subsurfac...@googlegroups.com>
Date: Friday, August 10, 2018 at 5:24 PM
To: Subsurface Group <subsurfac...@googlegroups.com>
Subject: Re: Trouble downloading Atom to Mac

 

 

On Aug 10, 2018, at 1:06 PM, Dirk Hohndel <di...@hohndel.org> wrote:

--

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 post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/79F2E432-0508-4714-9F2C-DCEF093AA509%40hohndel.org.

[Dirk Hohndel]

On Aug 10, 2018, at 2:55 PM, Stuart Vernon <stu...@force2.net> wrote:

Okay, that worked. Yaayy!!

Yay indeed. We’ll switch to this by default for the next version, I guess.

One oddity, it downloaded (apparently) all the dives from my computer – including ones that were already downloaded from that computer and stored in my log. I unchecked all the extra ones and just imported the new ones. Seems to be all good.

I wonder why that happened - did the divecomputer id change for some reason?

Odd.

/D

[Stuart Vernon]

I can't think of how my dive computer id would have changed. The most invasive thing I've done to it is change the battery. 

-------- Original message --------

From: Dirk Hohndel <di...@hohndel.org>

Date: 8/10/18 8:54 PM (GMT-05:00)

To: subsurfac...@googlegroups.com

Subject: Re: Trouble downloading Atom to Mac

--
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 post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/54211B09-51EC-4571-893B-0E5D5AE1487B%40hohndel.org.

[Dirk Hohndel]

> On Aug 10, 2018, at 8:08 PM, Stuart Vernon <stu...@force2.net> wrote:
>
> I can't think of how my dive computer id would have changed. The most invasive thing I've done to it is change the battery.

I was wondering if this had something to do with using the user space FTDI connection.
Or something.
But mostly I'm interested if you look into your divelog if there's an obvious reason why it wouldn't have recognized the dives as having already been downloaded before.
Not sure how comfortable you are with doing things like that.

Maybe the easiest way to figure it out would be to export two dives to XML - your last one, and one much earlier one that was already in the dive log when you did that last download.
Simply select them both and then export the selected dives. In the XML you can see the divecomputer id stored in each of the dives...


/D

[Stuart Vernon]

I finally had a chance to look at my divelog for this.

From the top of the file. This seems odd because I have dives from these 3 computers in my log, but I also have dives from my Seabear H3 and the Shearwater Petrel 2 that I used to have. I looked (in the ssrf file) and I can see the dives logged from the Seabear, but, even more strange, I don't find any record at all of the Petrel 2 I used to have, even though my log goes all the way back to my very first dive after OW, where I was using the Atom that I am still using today. It's like all data from my Petrel 2 has been lost. Fortunately, I always dived with 2 computers when I had the Petrel 2, so the dives are in there, recorded by my Atom or Seabear. But I digress...

<settings>
<divecomputerid model='Hollis TX1' deviceid='4a0b8d14' serial='000674'/>
<divecomputerid model='Oceanic Atom 3.0' deviceid='4b1311a5' serial='001123'/>
<divecomputerid model='Shearwater Perdix AI' deviceid='e16fe0ac' serial='380765c9' firmware='53'/>
</settings>

On an early dive (downloaded under Windows):

<divecomputer model='Oceanic Atom 3.0' deviceid='4b1311a5' diveid='c2343091'>

From one of the dives downloaded using the new version of Subsurface that you baked for me:

<divecomputer model='Oceanic Atom 3.0' deviceid='4b1311a5' diveid='144e7ea6'>

I did a Find in the file, for Oceanic, and looked at a lot of the entries. They are all the same deviceid.

So, definitely not sure why this new version wanted to re-import all the dives from my Atom. The deviceid is still the same.

--
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 post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/C9F96B1F-F75B-49DD-B958-09FC614CA8AD%40hohndel.org.

[Dirk Hohndel]

> On Aug 13, 2018, at 8:12 AM, Stuart Vernon <stu...@force2.net> wrote:
>
> I finally had a chance to look at my divelog for this.
>
> From the top of the file. This seems odd because I have dives from these 3 computers in my log, but I also have dives from my Seabear H3 and the Shearwater Petrel 2 that I used to have. I looked (in the ssrf file) and I can see the dives logged from the Seabear, but, even more strange, I don't find any record at all of the Petrel 2 I used to have, even though my log goes all the way back to my very first dive after OW, where I was using the Atom that I am still using today. It's like all data from my Petrel 2 has been lost. Fortunately, I always dived with 2 computers when I had the Petrel 2, so the dives are in there, recorded by my Atom or Seabear. But I digress...

That's very concerning. Why would all the Petrel dives be lost? Has this always been stored in the cloud? If yes we should be able to recover the missing divecomputer entries.

> <settings>
> <divecomputerid model='Hollis TX1' deviceid='4a0b8d14' serial='000674'/>
> <divecomputerid model='Oceanic Atom 3.0' deviceid='4b1311a5' serial='001123'/>
> <divecomputerid model='Shearwater Perdix AI' deviceid='e16fe0ac' serial='380765c9' firmware='53'/>
> </settings>
>
> On an early dive (downloaded under Windows):
>
> <divecomputer model='Oceanic Atom 3.0' deviceid='4b1311a5' diveid='c2343091'>
>
> From one of the dives downloaded using the new version of Subsurface that you baked for me:
>
> <divecomputer model='Oceanic Atom 3.0' deviceid='4b1311a5' diveid='144e7ea6'>
>

> I did a Find in the file, for Oceanic, and looked at a lot of the entries. They are all the same device.

OK, so that theory is proven incorrect.

Thanks for looking into this. I have it when the software does things that I cannot explain :-(

/D

[Stuart Vernon]

Yes, always been in the cloud.

My log is under this same email address and you are welcome to delve into it however you like. But, no worries if you don't have time. At this point, I am very happy to have things sorted out and seeming to work (fully, for me) on the Mac.

--
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 post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/C2C24946-BB57-4C87-ACC1-99EB808B7377%40hohndel.org.