At a loss

[ilya]

Hi Nick et all,

I am at a terrible loss. I have tried everything and am desperate.

I have been using macdive for a long time with no problems. Ever since I upgraded to the latest version I haven't been able to get it to work.
I followed all the steps, but no serial port shows up, so I can't even create a test report...

Here is my setup:
OS: 10.7.5
Cable: Smart-Interface cable.
Driver software: 2.2.16 from here: http://www.smartinterface.de/downloads.php
Also tried deinstalling the 2.2.16 and trying this one: 2.2.18 from here: http://www.ftdichip.com/Drivers/VCP.htm
I have a new battery in my suunto Vyper, i tried cleaning the connector and jiggling...
Have tried both USB ports (not using a hub). When I plug it in the light on the cable flickers.

Please help. I don't want to go back to manual importing...

desperate

[ilya]

In the mean time I have done the following;

deleted the 2.2.16 driver and reinstalled the 2.2.18 driver as it is more recent.

I then thoroughly read this page:
http://www.divesoftware.org/libdc/drivers.html

When I plug in the device and turn it into transfer mode nothing extra appears in /dev/
Only three things show up when doing an ls in /dev/tty.* and the serial driver is not one of them...

I then followed the instructions in this document:
http://www.ftdichip.com/Support/Documen ... Driver.pdf

I tried all the values for PID: 6001 (24577), 6010 (24592) and 6011 (24593) in the section for the Suunto sports instruments section.
The original value was 63104.. BTW.

Each time removing the extension and copying the edited one over it doing sudo cp -R ./FTDIUSBSerialDriver.kext /System/Library/Extensions/FTDIUSBSerialDriver.kext

And then restarting my macbook.

Nothing happens with any of the three settings.

If I understand this page at libdc/drivers.html correctly, it is no use to try the sillicon labs and/or prolific drivers because I use the Smart-Interface Cable...

If anybody has an idea, please let me know... Desperate...

Sincerely,
ilya

[ilya]

hmm, I sent a mail to: info@smartinterface.de
and got the mail right back.

Does it make sense to try the other datacable (from customidea)?

[nick]

Hi,

Wow ok. First, I would start by making sure you remove all traces of all of these drivers, and starting from scratch. It looks like (as you discovered) the SmartInterface driver is just an FTDI driver with a modified vid/pid, which is fine. If you want to edit the official FTDI driver you must be very careful that the permissions are correct afterwards, or it will not function. You can try using kextload/kextunload (with sudo) to see if you can load it manually. Check the system logs and see if there are any errors reported loading it - maybe the permissions are not correct.

But upgrading MacDive itself would not have caused this. I would imagine if you can get the device to show up in /dev again things will return to working. That's an interesting problem. Did you upgrade from 10.x to 10.8 while this stopped working? It could be that the SmartInterface driver doesn't work properly on ML, but 2.2.18 definitely does. You'd need to modify that one though.

And no, there's probably no need to try another cable. Don't install the prolific or silabs drivers or anything else, they are not correct.

[ilya]

ok, thanks!! I'm sure we'll get there...

I think it the broken functionality happened when I updated OS and macdive... not 10.8 though.. Still on 10.7.5

Do you know if I can safely add multiple entries in the plist?
Or should I assume the original value in the 2.2.16 version is correct?

How do I remove all traces? I only remove the file in /System/Library/Extensions/
is that ok or are there other areas to check/purge?

[nick]

That should probably be fine.

You would be fine replacing the Suunto entry in the official FTDI driver with the correct pid/vid from the SmartInterface version - you shouldn't need multiple (unless you have another device with an official cable).

But again - you have to be very careful that the permissions are intact, that would be the main thing to ensure you get correct. I'm surprised the 2.2.16 one doesn't work though. I might have to double check the release notes and see what they say about ML. If you're still on 10.7.5 then it may not be an issue, though.

[ilya]

Ok, deleted everything that looked like FTDI from extensions.

Installed the FTDI driver from the smartinterface site again. (version 2.2.14)

No errors in console after installing:
18-11-12 21:59:49,593 Installer: IFDInstallController FBE34910 state = 5
18-11-12 21:59:49,593 Installer: Displaying 'Install Succeeded' UI.

sudokextload gives no error neither. Not on commandline, or in console:
18-11-12 22:01:18,124 sudo: ilya : TTY=ttys000 ; PWD=/System/Library/Extensions ; USER=root ; COMMAND=/sbin/kextload FTDIUSBSerialDriver.kext

Permissions are similar:
drwxr-xr-x 3 root wheel 102 28 feb 2011

So I did not change the PID...
<key>idProduct</key>
<integer>63104</integer>
<key>idVendor</key>
<integer>1027</integer>

in hex that would be:
pid: f680
vid: 403

plugging in the device and turning it onto TRPC mode gives no entry in /dev/

[nick]

You don't even need to plug in the device - the entry in /dev is from the chip in the cable itself.

Do you have access to Windows? It would be worth trying to install the windows driver and Suunto software to test that the cable is not faulty. Ruling that out would be good.

[ilya]

Ah, there is something going on:

I found this when I plugged in the device (when it was in TRPC mode)

18-11-12 22:15:57,000 kernel: USBF: 16809. 67 [0xffffff8012448200] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x4000000)
18-11-12 22:16:00,000 kernel: USBF: 16812. 82 [0xffffff8012448200] The IOUSBFamily was not able to enumerate a device.

[ilya]

I have a VMWARE but have bad experiences using windows this way with USB devices.