Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Trouble connecting Drivesmart 55 EX to Garmin Express Windows 10

2141508
over 2 years ago

I have a long history of success updating older Nuvi devices connecting via USB to older versions of Garmin Express on Windows 7 and 10 running in VMware Workstation Pro. This combination no longer works - Windows does not recognize the USB device, thus Garmin Express cannot connect to the device.  In contrast, I frequently use USB connected scanners and various storage devices in the same way, connecting to Windows 7/10 applications running in VMware Workstation Pro virtual computers.

Currently using Garmin Express v7.16.1.0 for Windows 10 running in VMware Workstation v17.0.1 virtual computer running on a Ubuntu 20.04 Linux host.

My only Windows installations are within VMware virtual computers. Is there any way to connect my Drivesmart 55 to Garmin Express in this configuration or natively on Ubuntu Linux?

  • 0 over 2 years ago

    I'm not familiar with VMware Workstation v17.0.1 or Ubuntu, but have to wonder if there is some form of a setting within the VMware Workstation that allows specific programs to be accessed?

  • 0 over 2 years ago in reply to JohnfromPA

    I believe it’s a lower level problem, ie outdated Windows MTS drivers such as those distributed via the Garmin web site.  

    I am continuing to research and found many references to getting an MTS driver load failure error when Windows detects the Garmin USB connecting to the computer.  That fits my earliest symptoms.

    I also confirmed that the Garmin device USB connection is being passed though the VMware host to the virtual machine, as is done for other devices. So, nothing strange about that.

    Given that Garmin Express does not support Linux and connecting to Garmin Express running in a virtual machine running Windows no longer works, how about a platform independent web/browser-based solution? Does that exist, yet?

  • 0 over 2 years ago

    While I do not have a Drivesmart anymore (its firmware was disproportionately riddled with issues for my taste, however the same applies for most of my Garmin devices), it should show up in your Ubuntu host as MTP and it may fail to connect in the event you try to mount it, however you might verify that is properly connected by issuing lsbusb command from the shell which should return (amongst all the USB devices connected) its Bus/Device/ID/Descriptor (the latter being Drivesmart MTP or something, from memory); in the event that does not happen, you might want to inquire what went wrong, i.e. by issuing sudo journalctl -b | grep -e ‘not accepting address’ -e ‘couldn’t allocate usb_device’ as the culprit could be the cable, the USB port and – most possibly (that happened in my case) the device itself. If all is well on the host side, let’s move on to the Windows 10 guest: since you mentioned that your scanners and/or USB storage is working properly, we can exclude issues with the VMware USB passthrough, therefore your EX – although it could show as unrecognized under Universal Serial Bus Controllers – should be enumerated in the Device Manager. Now, I would avoid the Garmin MTS drivers  if I were you (latest, outstandingly buggy, version is – again from memory – from 2015) and use Garmin Express instead, which in its current release 7.16.1.0 has some issues related to the way it connects to the Garmin infrastructure worldwide (short version: it may work fine for, for example, a Jon from West Sussex, however it may return a “We’re unable to add this device” to a Bruce from Melbourne): in the event you’re affected by the latter, downgrade Express to 7.15.x.0. Finally, if all else fails, you may want to experiment by changing VMware USB controller’s USB Compatibility to “USB 1.1” and see what happens.

    As for your last - interesting - question, you’re probably referring to the current W3C’s (et al.) attempt to push a functional and cross-platform WebUSB API: while it is technically within the realm of feasibility, vendors’ implementations will turn it into an effort like herding cats. So… no, not happening soon, IMO.