garmin 310xt

[tigge]

garmin 310xt

[Tigge]

Yeah, unfortunately this happens sometimes on startup (it's a known bug), but should only show up once in while.. Does it ever work or does this constantly pop up?

[agiofws]

Tigge constantly.... it never worked is there anything i should do or try ? .....
thankyou... :)

[agiofws]

maybe this helps ?

Dec 7 00:18:30 ixus kernel: [27003.596141] usb 6-2: new full speed USB device using uhci_hcd and address 4
Dec 7 00:18:30 ixus kernel: [27003.758470] usb 6-2: New USB device found, idVendor=0fcf, idProduct=1004
Dec 7 00:18:30 ixus kernel: [27003.758476] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 7 00:18:30 ixus kernel: [27003.758480] usb 6-2: Product: Dynastream ANT2USB
Dec 7 00:18:30 ixus kernel: [27003.758483] usb 6-2: Manufacturer: Silicon Labs
Dec 7 00:18:30 ixus kernel: [27003.758487] usb 6-2: SerialNumber: 10046
Dec 7 00:18:30 ixus kernel: [27003.758644] usb 6-2: configuration #1 chosen from 1 choice
Dec 7 00:18:30 ixus kernel: [27003.763515] cp210x 6-2:1.0: cp210x converter detected
Dec 7 00:18:30 ixus kernel: [27003.876112] usb 6-2: reset full speed USB device using uhci_hcd and address 4
Dec 7 00:18:30 ixus kernel: [27004.023704] usb 6-2: cp210x converter now attached to ttyUSB0
Dec 7 00:18:58 ixus kernel: [27031.615831] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Dec 7 00:18:58 ixus kernel: [27031.615848] cp210x 6-2:1.0: device disconnected
Dec 7 00:18:58 ixus kernel: [27031.728124] usb 6-2: reset full speed USB device using uhci_hcd and address 4
Dec 7 00:18:58 ixus kernel: [27031.876695] usb 6-2: usbfs: process 7577 (python) did not claim interface 0 before use

[Tigge]

We do have people running this with the 310 (see for example #35), not sure what kind of ant stick was involved there. I've opened issue #47 to deal with support for the 1004 stick. Not all ANT chips support the ANT version command (which is what we never get an answer to here), such as the nRF24AP1 (whatever that is).

You could try to comment out the following lines in ant/fs/manager.py line 85:

    m = self._node.request_message(Message.ID.RESPONSE_VERSION)
    print "  ANT version:  ", struct.unpack("<10sx", m[2])[0]

I.e. change them to:

    #m = self._node.request_message(Message.ID.RESPONSE_VERSION)
    #print "  ANT version:  ", struct.unpack("<10sx", m[2])[0]

To see if we can get any further with this.

[Tigge]

That looks quite similar to mine. I should look into that 'did not claim interface' thing though:

[1296124.460053] usb 1-1.2.4: new full-speed USB device number 124 using ehci_hcd
[1296124.555648] usb 1-1.2.4: New USB device found, idVendor=0fcf, idProduct=1008
[1296124.555653] usb 1-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1296124.555656] usb 1-1.2.4: Product: ANT USBStick2
[1296124.555658] usb 1-1.2.4: Manufacturer: Dynastream Innovations
[1296124.555660] usb 1-1.2.4: SerialNumber: 139
[1296133.394595] usb 1-1.2.4: reset full-speed USB device number 124 using ehci_hcd
[1296133.488128] usb 1-1.2.4: usbfs: process 21441 (python) did not claim interface 0 before use

[agiofws]

i don't think that anything chnaged

look @ www.imagebin.org/238378

http://codepad.org/EihaO2zT

[agiofws]

It is a Garmin USB1 wireless ANT+ stick if this is usefull to you... IC:3797A-USBA

[Tigge]

It looks like it is still "requesting message 0x3e", that should not happen now, weird.

[agiofws]

agiofws@ixus:~/garmin-extractor/Garmin-Forerunner-610-Extractor-master$ gdb python
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
---Type to continue, or q to quit---
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/python...(no debugging symbols found)...done.
(gdb) run garmin.py
Starting program: /usr/bin/python garmin.py
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff5d83700 (LWP 7924)]
[New Thread 0x7ffff5582700 (LWP 7925)]
Request basic information...
Traceback (most recent call last):
File "garmin.py", line 205, in main
g = Garmin()
File "garmin.py", line 56, in init
Application.init(self)
File "/home/agiofws/garmin-extractor/Garmin-Forerunner-610-Extractor-master/ant/fs/manager.py", line 69, in init
m = self._node.request_message(Message.ID.RESPONSE_CAPABILITIES)
File "/home/agiofws/garmin-extractor/Garmin-Forerunner-610-Extractor-master/ant/easy/node.py", line 65, in request_message
return self.wait_for_special(messageId)
File "/home/agiofws/garmin-extractor/Garmin-Forerunner-610-Extractor-master/ant/easy/node.py", line 82, in wait_for_special
return wait_for_special(event_id, self._responses, self._responses_cond)
File "/home/agiofws/garmin-extractor/Garmin-Forerunner-610-Extractor-master/ant/easy/filter.py", line 91, in wait_for_special
return wait_for_message(match, process, queue, condition)
File "/home/agiofws/garmin-extractor/Garmin-Forerunner-610-Extractor-master/ant/easy/filter.py", line 58, in wait_for_message
raise AntException("Timed out while waiting for message")
AntException: Timed out while waiting for message
Interrupted
Traceback (most recent call last):
File "garmin.py", line 214, in
sys.exit(main())
File "garmin.py", line 210, in main
g.stop()
UnboundLocalError: local variable 'g' referenced before assignment
^C
Program received signal SIGINT, Interrupt.
0x00007ffff7bd03c0 in sem_wait () from /lib/libpthread.so.0
(gdb) backtrace
#0 0x00007ffff7bd03c0 in sem_wait () from /lib/libpthread.so.0
#1 0x00000000004d44e8 in PyThread_acquire_lock ()
#2 0x00000000004d8982 in ?? ()
#3 0x00000000004a7ba5 in PyEval_EvalFrameEx ()
#4 0x00000000004a95c1 in PyEval_EvalCodeEx ()
#5 0x00000000004a7752 in PyEval_EvalFrameEx ()
#6 0x00000000004a95c1 in PyEval_EvalCodeEx ()
#7 0x00000000004a7752 in PyEval_EvalFrameEx ()
---Type to continue, or q to quit---

[Tigge]

Looks like it is just waiting for the next capabilities message instead then.. hm. So either this stick is a bit different, there is something wrong with the usb connection, or something else. Could be worth trying to temporarily disable the cp210x-thingy, check to see if usb logs from a windows machine/vm reveal anything different. I'll sleep on it and see if I come up with something else.

Might be worth to get some system info as well, such as 'python --version', 'uname -a', etc. I should probably do a short guide on how to do this.

[agiofws]

/home/agiofws# python --version
Python 2.6.6

/home/agiofws# uname -a
Linux ixus 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux

[agiofws]

i even removed the cpx210 module but still the same symptoms anyway thanks i'll see to it tommorow Thank you for your spare time :)

[lcorbet]

Only to add, I have a USB2 ANT stick that worked (#35) with my 310xt.

[Tigge]

Handled in #47