Suunto Eon Core not recognised running Mac OS Mojave 10.14.6

[Mark Jones]

Connecting a new Suunto Eon Core to my Mac running Subsurface 5.0.2 binary downloaded from subsurface website. DM5 works on the Mac and I have downloaded first two dives successfully using DM5. Subsurface won't connect to the Eon Core. Restarted the Mac and Subsurface still won't connect to the Eon Core. This is despite the Eon's screen showing "USB connected" and this terminal command giving the following result:

ioreg -p IOSUB

    +-o GURU2@14400000  <class AppleUSBDevice, id 0x10000098e, registered, matched, active, busy 0 (714 ms), retain 11>

The error shown in Subsurface is "unable to open Suunto (EON Core)". The logfile shows:

ERROR: Failed to open the usb device. [in /Users/hohndel/src/subsurface/libdivecomputer/src/usbhid.c:625 (dc_usbhid_open)]

I've tried different USB ports on the Mac and I'm not using a USB Hub.

Any ideas?

[Dirk Hohndel]

Is this compiled from source, or the official binary?

Can you share a log (starting the app executable in a Terminal window, redirecting stdout/stderr)?

/D

[Mark Jones]

Subsurface 5.0.2 binary was downloaded from subsurface website today, not built locally. 

This is all that has been written to file redirected from stderr:

QObject::connect(QQuickWindow, QDeclarativeGeoMap_QML_6): invalid nullptr parameter

Populating font family aliases took 511 ms. Replace uses of missing font family "Bookman URW" with one that exists to avoid this cost. 

[0.013842] ERROR: Failed to open the usb device. [in /Users/hohndel/src/subsurface/libdivecomputer/src/usbhid.c:625 (dc_usbhid_open)]

and from stdout:

Starting download from  "USBHID"

downloading only new dives

Finishing download thread: "Unable to open  Suunto (EON Core)"

[Dirk Hohndel]

Just tried to reproduce this.

Oddly took me about 10 tries (plus some vigorous cleaning of the the Suunto connector) before it worked.

Initially all the Suunto would show when being plugged in was "charging". After trying A LOT harder with a brush, it said "USB connected" when plugged in and Subsurface happily (and very very quickly) downloads dives from it.

So, err... works here?

/D

[Mark Jones]

Weird thing is that if I fire up Suunto DM5 straight after trying subsurface it syncs-up automatically and it's 'just there' connected. Restarting the mac, so that there's no chance DM5 is stealing the connection and somehow holding onto it, and trying again isn't any better.

[Mark Jones]

Asking if anyone knows what else I can do to fix this?

[Steve Strong]

So I recently updated to 5.0.4 on Mac OS 10.14.6 and I'm seeing a similar problem. Odd thing is it worked for a time then it stopped. I tried DM5 after it stopped working to confirm the physical connection and that worked fine. The DC says "USB connected". I tried Bluetooth BTW and that doesn't recognize the DC either. I have intermittent success with BT on my iPhone as well. I'll post that elsewhere if you'd like to avoid confusion, but essentially if I configure it on the iPhone fresh I can download dives for a little while but if I come back after a short period of time (not sure exactly how much) then I acts like every time I scan it tries to add it again, it won't recognize it without doing that, and either way it doesn't work unless I forget the DC in subsurface-mobile, forget the device in the OS, and start over from scratch every time.

Thanks!

[Dirk Hohndel]

Hi Steve,

Weirdly it seems that even though the Subsurface 10.13/10.14 binary does contain the HIDAPI drivers, it+ refuses to open HIDAPI devices - I can reproduce this here locally (not something I tested in who-knows-how-long -- this definitely used to work back when my main MBP was running 10.14...)

I can also verify that this works with the macOS 10.15 binary on macOS 10.15 or 11 - but I guess that's not much of a consolation for you given that that's not the OS you are using.

As of earlier this week Mojave is officially EOL from Apple and will stop receiving updates... but I'm sure you are aware of that and are running 10.14 for a reason... But given that 10.13 and 10.14 are no longer supported by Apple, I really do consider those binaries even more "best effort" than everything else we do in Subsurface... and unfortunately I can't promise you that I'll be able to fix this. I'll play with it some more, time permitting.

/D

[Steve Strong]

Hi Dirk,

Still getting caught up after my last dive trip. Thanks for the info though, I totally understand. My laptop is a 2015 model which is why I’ve not upgraded. It’s already running slow as it is. Guess it’s time for a new one!

For the time being, the iOS will be fine, I just need to figure out why that’s being problematic in a different way. I’ll put something in for that too.

Thanks for all you do,

Steve

[Henrik B A]

On Mon, Nov 1, 2021 at 6:26 PM Steve Strong <st...@strongus.net> wrote:

Still getting caught up after my last dive trip. Thanks for the info though, I totally understand. My laptop is a 2015 model which is why I’ve not upgraded. It’s already running slow as it is. Guess it’s time for a new one!

Your Mac won't get slower with a newer macOS.  If anything, it might be faster.  This ain't Windows :)

Henrik

 

[Steve Strong]

I may give it a try as soon as I clear up the few remaining 32 bit only apps I need to replace. However, while I agree this ain't windows, I have found in the past that after a point, they add so many new features, it ultimately does understandably slow things down. The underlying *nix no doubt is fine, but all the extras Apple puts in does seem to have an impact after a while. I started with the 32 bit app replacement a long while ago, but it was just taking too much time, and I was in no rush really. No more updates changes that calculus though. I haven't seen official notice of this, but I do know it's time if they follow their normal timeline. I'd probably hold off on Monterey as there have been more than a few reports of bricking machines. ;)

[Dirk Hohndel]

I am traveling this week so won't be able to look into this anymore. But I have a vague idea how this might be solved. I need to know create a VM with macOS 10.14 (which Apple makes excruciatingly hard to do - they want app developers to force users to upgrade). I unfortunately don't appear to have any of my old systems still running 10.14...
Once I have the ability to reproduce this here I should be able to get it back to work (given that this used to work). But it won't happen this week

/D

[Steve Strong]

Unless there is a big call for it from many people Dirk, don't go through all the work just for 1 of us (or even just a few IMHO). If it was real easy that'd be one thing but please don't knock yourself out. There are work arounds with the phone so not a huge deal.

[Robert C. Helling]

If that's any consolation, I am writing this on an MBP of early 2015 that is happily running Big Sur. What I had to do, though, is at some point install a bigger SSD as I was running out of disk space. And yes, you have to say goodbye to 32bit applications (which in my case included MS Office as I had to find a new license for the 64bit version). I think you won't regret  the update.

[Steve Strong]

Good to hear from someone who went through the same thing. MS Office is/was one of those things for me too, and I don't want to pay for their subscription. I've gone so long now being able to use the Apple equivalents exclusively I think it's safe to part with that. The other pain is, I know it's a multi-hour process to do and time is not on my side right now! I have just a few other minor apps that I just need to find replacements for and I'll be ready. My battery is starting to swell again, 2nd time, so at this point I really do just need to pull the trigger on a new one sooner or later.