Suunto Stinger problem with importing dives to Macdive

[nick]

Hi Nick
Last login: Tue Sep 8 23:20:30 on console
MacBook-Pro:~ iMarco$ cd Desktop
MacBook-Pro:Desktop iMarco$ chmod u+x vyper
MacBook-Pro:Desktop iMarco$ ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port /dev/tty.usbserial
/dev/tty.Bluetooth-Modem
MacBook-Pro:Desktop iMarco$

You have to follow all of the instructions. You have not completed them. You are missing the final command, which performs the test itself.

You must now paste the final command:

./vyper /dev/tty.usbserial

As for the missing dive after have imported an xml file well I don't really know what to say. I am sorry to say but I have actually lost one dive. As you may see in the attached screenshot my dive count now begins with 2 (rather than 1).

The only way this would have happened is if you deleted it manually.

Yours Sincerely
MacDive Support

[marcogiornetti]

All rightNick, hope this time I did it correctly. Please find below what I got

Last login: Wed Sep 9 10:37:09 on ttys000
MacBook-Pro:~ iMarco$ cd Desktop
MacBook-Pro:Desktop iMarco$ chmod u+x vyper
MacBook-Pro:Desktop iMarco$ ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port /dev/tty.usbserial
/dev/tty.Bluetooth-Modem
MacBook-Pro:Desktop iMarco$ ./vyper /dev/tty.usbserial
DATETIME 2015-09-09T08:41:23Z (1441788083)
VERSION 0.5.0-devel (61e9847196b4e7f4e2c80e47dd6cd7070c9c4418)
DEVICE=/dev/tty.usbserial
suunto_vyper_device_open
INFO: Open: name=/dev/tty.usbserial
INFO: Configure: baudrate=2400, databits=8, parity=2, stopbits=1, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=1
INFO: Sleep: value=100
INFO: Flush: queue=3, input=0, output=0
dc_device_foreach
INFO: Sleep: value=500
INFO: RTS: value=1
INFO: Write: size=5, data=0500161407
INFO: Sleep: value=200
INFO: Flush: queue=1, input=0, output=0
INFO: RTS: value=0
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../source/src/suunto_vyper.c:231 (suunto_vyper_transfer)]
../../source/examples/suunto_vyper_test.c:51: Cannot read dives.
suunto_vyper_device_open
INFO: Open: name=/dev/tty.usbserial
INFO: Configure: baudrate=2400, databits=8, parity=2, stopbits=1, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=1
INFO: Sleep: value=100
INFO: Flush: queue=3, input=0, output=0
dc_device_dump
INFO: Sleep: value=500
INFO: RTS: value=1
INFO: Write: size=5, data=0500002025
INFO: Sleep: value=200
INFO: Flush: queue=1, input=0, output=0
INFO: RTS: value=0
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../source/src/suunto_vyper.c:231 (suunto_vyper_transfer)]
../../source/examples/suunto_vyper_test.c:94: Cannot read memory.

SUMMARY
-------
test_dump_sdm: Timeout
test_dump_memory: Timeout


Does it make any sense? Did I follow the procedure correctly?

As for the missing dive: I managed to uninstall and reinstall Mac dive 2.3.8. I imported again my dives from a backup I had. Now the missing dive is there although I only imported 5 dives as Mac dive is in trial mode. How do I get the full version?

Thanks for help + sorry for the problems I am causing...
Marco

[nick]

All rightNick, hope this time I did it correctly.

Yes this is correct. It appears your device is not responding to communication. Did you install the latest Prolific USB driver that I linked you to?

There is also a third-party USB driver that some people have success with:

http://www.xbsd.nl/2011/07/pl2303-seria ... -lion.html

There are manual install instructions, or if you read the comments there is a graphical installer somewhere (from memory). It would be worth trying this. You will see a different serial port to test (not /dev/tty.usbserial, it will be different). Perhaps it is worth trying. I have had good reports of this with other prolific based devices. I would also try the latest official one, which I linked you to already, as it looks to have been updated for current releases of OS X.

As for the missing dive: I managed to uninstall and reinstall Mac dive 2.3.8. I imported again my dives from a backup I had. Now the missing dive is there although I only imported 5 dives as Mac dive is in trial mode. How do I get the full version?

It sounds like you need to register your license, by double-clicking on it or drag/dropping it on to MacDive.


Yours Sincerely,
MacDive Support

[marcogiornetti]

Yes this is correct. It appears your device is not responding to communication. Did you install the latest Prolific USB driver that I linked you to?

Yes I did as you may see from the system profile below reported

USB-Serial Controller:

Product ID: 0x2303
Vendor ID: 0x067b (Prolific Technology, Inc.)
Version: 3.00
Speed: Up to 12 Mb/sec
Manufacturer: Prolific Technology Inc.
Location ID: 0x04100000 / 4
Current Available (mA): 500
Current Required (mA): 100

I have run again the test and this is what I got

Last login: Wed Sep 9 12:23:32 on ttys000
MacBook-Pro:~ iMarco$ cd Desktop
MacBook-Pro:Desktop iMarco$ chmod u+x vyper
MacBook-Pro:Desktop iMarco$ ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port /dev/tty.usbserial
/dev/tty.Bluetooth-Modem
MacBook-Pro:Desktop iMarco$ ./vyper /dev/tty.usbserial
DATETIME 2015-09-09T10:32:43Z (1441794763)
VERSION 0.5.0-devel (61e9847196b4e7f4e2c80e47dd6cd7070c9c4418)
DEVICE=/dev/tty.usbserial
suunto_vyper_device_open
INFO: Open: name=/dev/tty.usbserial
INFO: Configure: baudrate=2400, databits=8, parity=2, stopbits=1, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=1
INFO: Sleep: value=100
INFO: Flush: queue=3, input=0, output=0
dc_device_foreach
INFO: Sleep: value=500
INFO: RTS: value=1
INFO: Write: size=5, data=0500161407
INFO: Sleep: value=200
INFO: Flush: queue=1, input=0, output=0
INFO: RTS: value=0
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../source/src/suunto_vyper.c:231 (suunto_vyper_transfer)]
../../source/examples/suunto_vyper_test.c:51: Cannot read dives.
suunto_vyper_device_open
INFO: Open: name=/dev/tty.usbserial
INFO: Configure: baudrate=2400, databits=8, parity=2, stopbits=1, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=1
INFO: Sleep: value=100
INFO: Flush: queue=3, input=0, output=0
dc_device_dump
INFO: Sleep: value=500
INFO: RTS: value=1
INFO: Write: size=5, data=0500002025
INFO: Sleep: value=200
INFO: Flush: queue=1, input=0, output=0
INFO: RTS: value=0
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../source/src/suunto_vyper.c:231 (suunto_vyper_transfer)]
../../source/examples/suunto_vyper_test.c:94: Cannot read memory.

SUMMARY
-------
test_dump_sdm: Timeout
test_dump_memory: Timeout
MacBook-Pro:Desktop iMarco$


It looks like the same as before, isn't it? where am I mistaking?

With the third party USB driver no luck at all. Every time I try to install, after rebooting I have a message saying that the file is corrupt and can not be used (maybe because I am on Yosemite and that driver was for Lion?).

It sounds like you need to register your license, by double-clicking on it or drag/dropping it on to MacDive.

Success!! I managed to register it. All dives previously saved are not correctly imported and shown on macdive

Thanks for help!

[nick]

Product ID: 0x2303
Vendor ID: 0x067b (Prolific Technology, Inc.)
Version: 3.00
Speed: Up to 12 Mb/sec
Manufacturer: Prolific Technology Inc.
Location ID: 0x04100000 / 4
Current Available (mA): 500
Current Required (mA): 100

This doesn't actually mean that a driver is installed. It just shows you what the connected hardware is.

With the third party USB driver no luck at all. Every time I try to install, after rebooting I have a message saying that the file is corrupt and can not be used (maybe because I am on Yosemite and that driver was for Lion?).

What is the exact error?

The comments from people on that site indicate success on Yosemite.

[marcogiornetti]

This doesn't actually mean that a driver is installed. It just shows you what the connected hardware is.

I run the set up process as instructed by the Manual and at the end I got the pop -up window confirming that the installation was succesful. thus I (tend to) assume the Prolific driver is correctly installed.

Then i rebooted. Then I also installed the third party driver. Then rebooted.

The interesting thing is that now there is an additional port indicated by /dev/tty.PL2303-00001004 and also Macdive "sees" this new port. If I go to Preferences-> Advanced now the available serial ports are the following two:

/dev/tty.usbserial
/dev/tty.PL2303-00001004

Therefore I performed the vyper test again and I got this (you may wish to notice that differently from before now the /dev/tty.PL2303-00001004 port is listed)


Last login: Wed Sep 9 14:08:01 on ttys000
MacBook-Pro:~ iMarco$ cd Desktop
MacBook-Pro:Desktop iMarco$ chmod u+x vyper
MacBook-Pro:Desktop iMarco$ ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port /dev/tty.PL2303-00001004
/dev/tty.Bluetooth-Modem /dev/tty.usbserial
MacBook-Pro:Desktop iMarco$ ./vyper /dev/tty.PL2303-00001004
DATETIME 2015-09-09T12:15:59Z (1441800959)
VERSION 0.5.0-devel (61e9847196b4e7f4e2c80e47dd6cd7070c9c4418)
DEVICE=/dev/tty.PL2303-00001004
suunto_vyper_device_open
INFO: Open: name=/dev/tty.PL2303-00001004
INFO: Configure: baudrate=2400, databits=8, parity=2, stopbits=1, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=1
INFO: Sleep: value=100
INFO: Flush: queue=3, input=0, output=0
dc_device_foreach
INFO: Sleep: value=500
INFO: RTS: value=1
INFO: Write: size=5, data=0500161407
INFO: Sleep: value=200
INFO: Flush: queue=1, input=0, output=0
INFO: RTS: value=0
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../source/src/suunto_vyper.c:231 (suunto_vyper_transfer)]
../../source/examples/suunto_vyper_test.c:51: Cannot read dives.
suunto_vyper_device_open
INFO: Open: name=/dev/tty.PL2303-00001004
INFO: Configure: baudrate=2400, databits=8, parity=2, stopbits=1, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=1
INFO: Sleep: value=100
INFO: Flush: queue=3, input=0, output=0
dc_device_dump
INFO: Sleep: value=500
INFO: RTS: value=1
INFO: Write: size=5, data=0500002025
INFO: Sleep: value=200
INFO: Flush: queue=1, input=0, output=0
INFO: RTS: value=0
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../source/src/suunto_vyper.c:231 (suunto_vyper_transfer)]
../../source/examples/suunto_vyper_test.c:94: Cannot read memory.

SUMMARY
-------
test_dump_sdm: Timeout
test_dump_memory: Timeout
MacBook-Pro:Desktop iMarco$


Does it mean anything?
Thanks for help,
m

[marcogiornetti]

Hi all I tried to make other attempts but no luck still.
However I add some more info hope they are helpful.
From System Information I got this (referred to the serial port that now I can see):

USB-Serial Controller (PL2303-00002006):
Type: PPP
IPv4:
Configuration Method: PPP
IPv6:
Configuration Method: Automatic
Proxies:
FTP Passive Mode: Yes
PPP:
ACSP Enabled: No
Display Terminal Window: No
Redial Count: 1
Redial Enabled: Yes
Redial Interval: 5
Use Terminal Script: No
Dial on Demand: No
Disconnect on Fast User Switch: Yes
Disconnect on Idle: Yes
Disconnect on Idle Timer: 600
Disconnect on Logout: Yes
Disconnect on Sleep: Yes
Idle Reminder: No
Idle Reminder Time: 1800
IPCP Compression VJ: Yes
LCP Echo Enabled: Yes
LCP Echo Failure: 4
LCP Echo Interval: 10
Log File: /var/log/ppp.log
Verbose Logging: No

When I try to configure by system preferences -> network I got these two (see attached screenshots):

[TnT]

Let's start by summarizing what we know already so far: On a Windows PC downloading works, so we can rule out problems with the cable and the device. On your mac, downloading fails. That means the problem must be in the Mac Prolific driver, or in the application.

In order to find out where the problem is located, I suggest you first try the Windows version of our test application on the same system where the Suunto software works. If that works, then we can confirm the problem is the Mac driver. If it doesn't work, then it must be on the application side.

[marcogiornetti]

Let's start by summarizing what we know already so far: On a Windows PC downloading works, so we can rule out problems with the cable and the device. On your mac, downloading fails. That means the problem must be in the Mac Prolific driver, or in the application.

Correct: it worked perfectly on windows and Suunto DM 3.1.

In order to find out where the problem is located, I suggest you first try the Windows version of our test application on the same system where the Suunto software works. If that works, then we can confirm the problem is the Mac driver. If it doesn't work, then it must be on the application side.

Ok I will do that on the week end and then I will post the results here and alert you via email.
Thanks for help, cheers
Marco

[marcogiornetti]

Hi all I performed the self test on the Windows-running pc where the trasfer works correctly.
More in detail:

1) I plugged the connection cable + docking station;
2) I put the diving computer in PC Mode-Transfer
3) I connected the diving computer in the docking station and waited until the signal ACW showed up;
4) I performed the self test

This is what I got:

[0.000021] DATETIME 2015-09-14T21:10:33Z (1442265033)
[0.000556] VERSION 0.5.0-devel (c72bdfe4e4175cb7ad2eb3dc4caa0e9fd9c12962)
[0.000855] ../../source/examples/universal.c:973: No matching device found.

Please note that with Suunto manager when i run steps 1) to 3) above the Suunto DM Assistant sees the device corectly in paraller to usb port 8. In fact as a matter of fact I managed to download all the dives in did this week end.


Does this makes any sense?
Cheers
Marco