Suunto D9 connection problems

[AndreyK]

Just got used Suunto D9. Computer works fine but has connection problems.
I could not connect with my cable (version 4.00/ device name /dev/tty.usbserial-ST000001). Tried reinstall drivers, used different version of driver from FTDI and Suunto, deinstall Apple FTDI embedded driver... no result.
At dive shop I took new cable (version 6.00/ device name /dev/tty.usbserial-STVCHW7O) and It worked fine with the same driver.
So problem with cable or driver. Computer D9 is fine.

Detailed information with my cable:

Dive computer - Suunto D9
OS - MacOS 10.10.5 Yosemite
Driver FTDI 2.2.18 (64 bit) or 2.3 (64 bit) - same result

Cable:
Product ID: 0xf680
Vendor ID: 0x0403 (Future Technology Devices International Limited)
Version: 4.00
Serial Number: ST000001
Speed: Up to 12 Mb/sec
Manufacturer: Suunto
Location ID: 0xfa130000 / 7
Current Available (mA): 500
Current Required (mA): 300

saturn:~ andrey$ ls -l /dev/cu.*
crw-rw-rw- 1 root wheel 34, 1 26 окт 20:01 /dev/cu.Bluetooth-Incoming-Port
crw-rw-rw- 1 root wheel 34, 3 26 окт 20:01 /dev/cu.Bluetooth-Modem
crw-rw-rw- 1 root wheel 34, 5 26 окт 20:01 /dev/cu.iPhone-WirelessiAP
crw-rw-rw- 1 root wheel 34, 7 26 окт 21:04 /dev/cu.usbserial-ST000001
saturn:~ andrey$ ls -l /dev/tty.*
crw-rw-rw- 1 root wheel 34, 0 26 окт 20:01 /dev/tty.Bluetooth-Incoming-Port
crw-rw-rw- 1 root wheel 34, 2 26 окт 20:01 /dev/tty.Bluetooth-Modem
crw-rw-rw- 1 root wheel 34, 4 26 окт 20:01 /dev/tty.iPhone-WirelessiAP
crw-rw-rw- 1 root wheel 34, 6 26 окт 21:04 /dev/tty.usbserial-ST000001

saturn:~ andrey$ kextstat |grep FTDI
161 0 0xffffff7f838fb000 0x8000 0x8000 com.FTDI.driver.FTDIUSBSerialDriver (2.2.18) <148 39 5 4 3 1>

saturn:~ andrey$ ~/Downloads/d9 /dev/tty.usbserial-ST000001
DATETIME 2015-10-26T18:06:33Z (1445882793)
VERSION 0.5.0-devel (61e9847196b4e7f4e2c80e47dd6cd7070c9c4418)
DEVICE=/dev/tty.usbserial-ST000001
suunto_d9_device_open
INFO: Open: name=/dev/tty.usbserial-ST000001
INFO: Configure: baudrate=9600, databits=8, parity=0, stopbits=1, flowcontrol=0
INFO: Timeout: value=3000
INFO: DTR: value=1
INFO: Sleep: value=100
INFO: Flush: queue=3, input=0, output=0
INFO: Configure: baudrate=9600, databits=8, parity=0, stopbits=1, flowcontrol=0
INFO: RTS: value=0
INFO: Write: size=4, data=0F00000F
INFO: Read: size=4, data=0F00000F
INFO: RTS: value=1
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../source/src/suunto_d9.c:268 (suunto_d9_device_packet)]
INFO: RTS: value=0
INFO: Write: size=4, data=0F00000F
INFO: Read: size=4, data=0F00000F
INFO: RTS: value=1
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../source/src/suunto_d9.c:268 (suunto_d9_device_packet)]

[nick]

Sounds like you already narrowed it down to the cable?

You can check and see if it's damaged in any way. I know mine got a bit loose, it's looking pretty dodgy these days and can take a bit to get connected.

The driver has been fine for me on various devices that use it.

[AndreyK]

My cable is absolutely in good condition. No damage.
When I connect it Suunto is changing mode to "Data transfer" and the drive create automatically devices in /dev folder.
Look like is OK but does not work.

[nick]

I am mainly going off the fact you said another cable works, and this one doesn't, combined with my own experience of the driver not having any issues.

The D9 is typically a very reliable device to download. Another cause of issues like this can be low battery.

[AndreyK]

Battery has been changed one week ago.

[AndreyK]

May be the cable v4.00 not compatible with D9?

[nick]

The cable that when plugged in reports itself as tty.usbserial-ST000001 is the correct/original cable for the D9. The other one you mention, I guess the "v6", is typically for the D4i, D6i, D9tx, etc.

Perhaps you can try another original D9 cable, it may just be faulty, particularly if you said you already tried a different cable and it works fine.

Sorry, I don't have many more suggestions right now - the D9 is reliable. You've said a different cable works, so, it seems like there is an issue with your cable.