Problems connecting CompuTrainer to GC

[SebpG]

Hi there!

I am a total newbie to GoldenCheetah, so I ask for some lenience for
my first post.
I am encountering some weird things trying to connect my CompuTrainer
to GC. To make matters worse,
I am also a newbie to CompuTrainer. I tried to make the CompuTrainer s/
w work under "wine", but all
I get is an immediate crash when I launch the "CompuTrainer 3D"
software.
But right now I couldn't care less about this since my main goal is to
use GC.

The technical data first:
- Ubuntu 8.04
- GoldenCheetah Version: 1.3 and "developer build" (built on the
lastest version on May 31, 2010)
- Racer Mate CompuTrainer (March 2009)

I tried to feed riding data from my CompuTrainer to GC. Here is how I
went about it:
First, I select a cyclist.
Then I select "Tools->Options->Devices" to add the CompuTrainer.
As device port I enter /dev/ttyUSB0.
A diff between "ls -rtl /dev/" before and after I connected the USB
plug gives me:
crw-rw---- 1 root root 254, 19 2010-07-25 13:30
usbdev5.35_ep00
crw-rw---- 1 root root 254, 20 2010-07-25 13:30
usbdev5.35_ep81
crw-rw---- 1 root root 254, 21 2010-07-25 13:30
usbdev5.35_ep02
crw-rw---- 1 root dialout 188, 0 2010-07-25 13:30 ttyUSB0
(the number 5.35 increases by 1 every time I plug in the USB cable)
Then, I change to "Train and Racing View".
Finally, I select "Ride->DownLoad from Device"
The pop-up window displays
Select port:
Serial: /dev/ttyUSB0
Select device type:
PowerTap
When I click "Download" I get the pop-up window "Download failed"
with the message "ERROR: open failed: open: No such file or directory"
Funny thing is that /dev/ttyUSB0 has disappeared. If I run a diff
between "ls -rtl /dev/"
before I connected the USB plug and after I clicked "Download" I get:
crw-rw---- 1 root root 254, 19 2010-07-25 13:30
usbdev5.35_ep00
crw-rw---- 1 root root 254, 20 2010-07-25 13:30
usbdev5.35_ep81
crw-rw---- 1 root root 254, 21 2010-07-25 13:30
usbdev5.35_ep02
Upon further investigation I found that /dev/ttyUSB0 disappears right
after I open the
"Ride->DownLoad from Device" dialog.

I know it's probably a really small or stupid mistake I am making
here, but nevertheless,
am stuck and need your help. Thank you in advance.

[Mark Liversedge]

Hi,

Cool, thanks for giving it a go.

To stsrt the ant+/computrainer stuff on the top left of the screen
there is a drop-down that says 'Ride Analysis View', if you change
that to 'Racing and Training View' you will then be able to start
rides etc. There should be a dropdown on the main screen (lots of
"LCD" number displays) that allows you to select your computrainer
and press start to ride.

The keys on the handlebar controller do lots of fancy things when you
are riding:
STOP/Reset = Stop
F1 = new lap/interval
F2 = change display size
+/- = increase/decrease load/gradient
F3 = shift key so...
F3 and + = fast forward through workout
F3 and - = rewind back in workout
F3 and F1 = fast forward to next Lap marker

Let me know if you need more info, the workout files
support .crs, .mrc and .erg. Racermate provide lots of these on the
install CD so you could pop them somewhere and reference the directory
in tools->options, and on the Settings page there is a 'Workout
Library Directory' which you can set to point at the directory with
all the racermate .erg/.mrc/.crs files.

Good luck!!!

Hope you have a nice big fan too :-))))

Cheers,
Mark

[SebpG]

Thank you, Mark, for the warm welcome and the quick reply.

My problem is that I cannot seem to connect my CompuTrainer via USB
port to GC.
Here is what I am doing: I change to 'Racing and Training View' (as
you told me). When I press start, the timer starts running OK, but
when I get on my bike and start pedaling all the zeros on the display
remain 0, I (except Avg Load Watts and Load Watts which were at 100
all the time). I may not be the strongest cyclist, but I would hope
that I can go faster than 0 km/h. By the way, the handlebar display
works fine, albeit in Miles.

My guess is that there are no data coming in through the USB port. The
port is recognized all right, because if I don't plug in CT I get an
error message "Cannot connect to Computrainer". Could it be a problem
with the FTDI driver?

Thanks a lot in advance

Sebp


PS: Luckily, I do have a strong fan. I put it behind the bike, gives
me much needed tail wind ;-)

[Mark Liversedge]

When you are connected and the timer is running what gets displayed on
the handlebar computer?

Do you know what kind of USB adaptor you are using? I am assuming it
is a Keyspan (usually kinda translucent browny/grey) rather than a
Sewell (usually blue) ?

Can you check that too?

Cheers,
Mark

[SebpG]

Wow, you're quick!

The adapter is translucent, about 12 cm long and connects to the audio-
stereo plug.

The handlebar display is pretty much unimpressed when I connect the
plug and start the timer. No change from its previous state. There are
3 fields, "MPH", "TIMER" and "PRGM" (which has value 5).

Is this useful?

Thx,

Sebp

[Mark Liversedge]

Ok. So we really do need to work out what that adaptor is - does it
have anything written on it?

Whilst GC has successfully opened /dev/ttyUSB0 it sure aint your CT
(or the usb stuff is all a bit wonky) - your display would change to
say 'Pro' if it was conencted at all.

Also, can you connect the CT and run 'sudo dmesg' - this will display
the diagnostic console messages from the Linux kernel, and will help
to validate we are using the right port. If you're concerned about
running that command cause someone on the internet asked you to it is
described here: http://en.wikipedia.org/wiki/Dmesg

Also, might be worth unplugging the USB connection from your PC.
turning the CT off for a few secs until the display disappears then
back on again and then reconnect the USB adapter to the PC (but I
suspect you may have already been though this a gazillion times)

Cheers,
Mark

[Mark Liversedge]

It might also be file permissions ... can you sudo chmod 666 /dev/
ttyUSB0 ? (makes it read/writable by everyone)

[SebpG]

On Jul 29, 4:11 pm, Mark Liversedge <liverse...@gmail.com> wrote:
> Ok. So we really do need to work out what that adaptor is - does it
> have anything written on it?

Nope, nothing written on it, merely a little graphic that looks like

^
| _
| [_]
O | |
| | /
\ |/
\|
O

>
> Whilst GC has successfully opened /dev/ttyUSB0 it sure aint your CT
> (or the usb stuff is all a bit wonky) - your display would change to
> say 'Pro' if it was conencted at all.
>
> Also, can you connect the CT and run 'sudo dmesg' - this will display
> the diagnostic console messages from the Linux kernel, and will help
> to validate we are using the right port. If you're concerned about
> running that command cause someone on the internet asked you to it is
> described here:http://en.wikipedia.org/wiki/Dmesg

Running 'sudo dmesg' gives me 1520 lines of output, the last 20 being
1501 [608704.923447] usb 5-2: configuration #1 chosen from 1 choice
1502 [608704.926371] ftdi_sio 5-2:1.0: FTDI USB Serial Device
converter detected
1503 [608704.926405] /build/buildd/linux-2.6.24/drivers/usb/serial/
ftdi_sio.c: Detected FT232RL
1504 [608704.926489] usb 5-2: FTDI USB Serial Device converter now
attached to ttyUSB2
1505 [608803.909650] usb 5-2: USB disconnect, address 84
1506 [608803.909988] ftdi_sio ttyUSB2: FTDI USB Serial Device
converter now disconnected from ttyUSB2
1507 [608803.910002] ftdi_sio 5-2:1.0: device disconnected
1508 [608820.877421] usb 5-2: new full speed USB device using
uhci_hcd and address 85
1509 [608821.078733] usb 5-2: configuration #1 chosen from 1 choice
1510 [608821.081652] ftdi_sio 5-2:1.0: FTDI USB Serial Device
converter detected
1511 [608821.081674] /build/buildd/linux-2.6.24/drivers/usb/serial/
ftdi_sio.c: Detected FT232RL
1512 [608821.081744] usb 5-2: FTDI USB Serial Device converter now
attached to ttyUSB2
1513 [608881.654408] usb 5-2: USB disconnect, address 85
1514 [608881.654809] ftdi_sio ttyUSB2: FTDI USB Serial Device
converter now disconnected from ttyUSB2
1515 [608881.654830] ftdi_sio 5-2:1.0: device disconnected
1516 [609100.829218] usb 5-2: new full speed USB device using
uhci_hcd and address 86
1517 [609101.029558] usb 5-2: configuration #1 chosen from 1 choice
1518 [609101.032474] ftdi_sio 5-2:1.0: FTDI USB Serial Device
converter detected
1519 [609101.032495] /build/buildd/linux-2.6.24/drivers/usb/serial/
ftdi_sio.c: Detected FT232RL
1520 [609101.032574] usb 5-2: FTDI USB Serial Device converter now
attached to ttyUSB2

>
> Also, might be worth unplugging the USB connection from your PC.
> turning the CT off for a few secs until the display disappears then
> back on again and then reconnect the USB adapter to the PC (but I
> suspect you may have already been though this a gazillion times)
>
> Cheers,
> Mark

Unplugging and reconnecting and turning off/on has no effect
whatsoever.

After seeing USB2 I created 3 devices in the options menu, one for
USB0, USB1, USB2.

When I connect and start the timer, I get the message "Cannot Connect
to Computrainer if I select the wrong device in the menu above the
start button. However, if I select the correct device, and I press
"start" a little red flash emerges from the translucent USB plug. When
I press "pause" or "stop" a huge green flash emerges from the plug
followed by a 0.5 second long red flash. It seems to me that GC at
least connects to the correct USB port. The CT handlebar display
changes to "0.00 lbs" on the top line and "U 200" on the bottom line.
When I start cycling, the top line displays mph and the bottom line
the word "UP". The displays in GC remain unimpressed by all of this.
When I press "stop" after cycling, the USB plug does not flash
anymore.

I've repeated these steps 3 times now, always with the same result,
i.e. the lights flash in the USB plug on "start/stop", but cease to
flash on "start/stop" once I actually hit the pedals.

If you're not confused yet, I for sure am.

Sebp

[SebpG]

I chmodded to 666, same depressing results.

[Justin Knotzke]

  Salut,

  There is no indication at all on this device of yours that converts serial to USB of who makes it or what the model number is ?

  Have you been able to convert any serial to USB successfully using this device ?

  J

[Mark Rages]

You are on Linux.

Show us the output of lsusb

Better yet, show us lsusb with the adapter unplugged, then plug it in
and show us lsusb after that.

Regards,
Mark
markrages@gmail

--
Mark Rages, Engineer
Midwest Telecine LLC
mark...@midwesttelecine.com

--
Mark Rages, Engineer
Midwest Telecine LLC
mark...@midwesttelecine.com

[SebpG]

On Jul 29, 5:18 pm, Justin Knotzke <jknot...@shampoo.ca> wrote:

> On Thu, Jul 29, 2010 at 17:14, SebpG <sebp.ge...@videotron.ca> wrote:
> > I chmodded to 666, same depressing results.
>
> > On Jul 29, 4:18 pm, Mark Liversedge <liverse...@gmail.com> wrote:
> > > It might also be file permissions ... can you sudo chmod 666 /dev/
> > > ttyUSB0 ? (makes it read/writable by everyone)
>
>   Salut,
>
>   There is no indication at all on this device of yours that converts serial
> to USB of who makes it or what the model number is ?

No, nothing at all. Maybe the manufacturer is ashamed of it. Wonder
why?

>
>   Have you been able to convert any serial to USB successfully using this
> device ?

I run linux (Ubuntu 8.04). I tried to run the CompuTrainer s/w under
wine. I can compile and create the applications, they crash however on
opening.
So, the answer is "No, I have never successfully used this device".

Sebp.

>
>   J

[SebpG]

On Jul 29, 5:27 pm, Mark Rages <markra...@gmail.com> wrote:
> On Thu, Jul 29, 2010 at 4:18 PM, Justin Knotzke <jknot...@shampoo.ca> wrote:

>
> > On Thu, Jul 29, 2010 at 17:14, SebpG <sebp.ge...@videotron.ca> wrote:
>
> >> I chmodded to 666, same depressing results.
>
> >> On Jul 29, 4:18 pm, Mark Liversedge <liverse...@gmail.com> wrote:
> >> > It might also be file permissions ... can you sudo chmod 666 /dev/
> >> > ttyUSB0 ? (makes it read/writable by everyone)
>
> >   Salut,
> >   There is no indication at all on this device of yours that converts serial
> > to USB of who makes it or what the model number is ?
> >   Have you been able to convert any serial to USB successfully using this
> > device ?
> >   J
>
> You are on Linux.
>
> Show us the output of lsusb
>
> Better yet, show us lsusb with the adapter unplugged, then plug it in
> and show us lsusb after that.
>

Before:
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 058f:6377 Alcor Micro Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000


After:
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 101: ID 0403:6001 Future Technology Devices
International, Ltd FT232 USB-Serial (UART) IC
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 058f:6377 Alcor Micro Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Thx,

Sebp

> Regards,
> Mark
> markrages@gmail
>
> --
> Mark Rages, Engineer
> Midwest Telecine LLC

> markra...@midwesttelecine.com

>
> --
> Mark Rages, Engineer
> Midwest Telecine LLC

> markra...@midwesttelecine.com

[Mark Liversedge]

I'm guessing this is the adaptor: http://www.computrainer.com/images/FTDIUSBstereosmall.jpg

Gonna try and work out what it is...

I had lots of problems with the adaptor racermate sent me with my own
CT and ended up getting a keyspan (and a friend of mine had a similar
problem with his Velotron too). But lets not be too hasty, maybe its
the drivers and we just need to get the right ones installed.

I'll get back when I've found out what it is!! (unless someone else
knows?)

[SebpG]

A million thanks, Mark!

Sebp

[Mark Liversedge]

More hints here: http://www.racermate.net/forum/viewtopic.php?f=4&t=2172

[SebpG]

It's the bugger in the upper left corner. 100%.

S

[Mark Liversedge]

Reading over on the Racermate site, this is a custom USB adaptor:

"FTDI-based adapter

Approved FTDI-based USB Drivers

Please Note: An FTDI-based adapter has been standard with
CompuTrainer for all Vista 64-bit sales beginning October 2008 and
then became standard on all CompuTrainers sales beginning in December
2008, at which point all in-house support for the Sewell adapter was
suspended - except as noted above. The first FTDI USB-to-Serial
adapter is recognized by the tan and blue housing with blue lights
flashing when in use. This driver is the same for all FTDI adapters
including our new custom FTDI-based USB-to-Stereo adapter, which now
ships with all new CompuTrainers as of January 2009.

This driver executable is the same for all operating systems and will
correctly detect and install the driver for the operating system you
have.

Approved Windows™ (including 7) FTDI Driver"

Not at all sure how 'custom' it is -- I would have hoped that the
stock FTDI VCP 1.5.0 drivers would be ok. I'm kinda stumped.

Since they haven't given you an audio jack to 9-pin serial converter
(its all built in to that custom adaptor) its going to be very tricky
to use another Serial/USB adaptor (i.e. the Keyspan).

Will sleep on it.

[Mark Liversedge]

Ah. You are on hardy heron, which is circa 2008, so *maybe* installing
the latest (2009) FTDI 1.5.0 drivers will fix this... worth a try.

You can download them here: http://www.ftdichip.com/Drivers/VCP.htm

Will catch up in the morning... (I'm in the UK).

Good luck,
Mark

[SebpG]

I have tried to install this driver, but the make command gives me an
error list a mile long.
I will have to work on that first. Thank you again for your time and
support.

Sebp

[Mark Liversedge]

No problem.

From what I can see the 2.6.24 kernel you are running included v1.4.3
of the ftdi_sio driver and there are a surpisingly high number of
fixes after 2.6.24 related to the ftdi_sio drivers... maybe it's time
to upgrade to the latest 10.04 Ubuntu ?

Cheers,
Mark

[SebpG]

I've upgraded to 10.04 (it was high time, anyway).

When I try to compile ftdi_sio I get an error list a mile long.
Most errors are missing include files from the kernel sources (/lib/
modules/2.6.32-24-generic/build/include/linux/) and missing #defines
because of those missing include files.

I've searched on the web if someone else had the same problem and
found a few posts where they say that the kernel is probably too old.
Sounds not right as I have version 2.6.32.

I don't like to touch the kernel (I've never done it). What should I
do?

Cheers,
Sebp

[Mark Liversedge]

I run 10.04 with keyspan drivers and it works a charm, of course that
option is not available to you since the cable from Racermate no
longer gives you a 9pin serial connection. I wonder if they can supply
one (audio->9pin) and then you can use a keyspan instead?

I guess you already tried with the stock ftdi drivers in 10.04?

Other than that, I am afraid I am out of ideas :-(

Justin and Mark R - any ideas?

Cheers,
Mark

[Justin Knotzke]

On Sun, Aug 1, 2010 at 14:22, Mark Liversedge <liver...@gmail.com> wrote:

I run 10.04 with keyspan drivers and it works a charm, of course that
option is not available to you since the cable from Racermate no
longer gives you a 9pin serial connection. I wonder if they can supply
one (audio->9pin) and then you can use a keyspan instead?

   How are you connecting Mark ? You are using a Keyspan and the standard cables from Racermate ?

   J 

[Mark Liversedge]

The cable from the headunit is an audio cable, it then goes into an
audio -> serial 9pin converter which I attach to the keyspan HS19-USA
(but previously connected to the sewell serial->usb adaptor that
didn't work very well).

Seb has an audio cable that goes directly into the 'custom' Racermate
adapter which converts from audio -> usb. This is the new standard
Racermate adaptor (as of late last year).

On Aug 1, 7:25 pm, Justin Knotzke <jknot...@shampoo.ca> wrote:

[Justin Knotzke]

On Sun, Aug 1, 2010 at 14:45, Mark Liversedge <liver...@gmail.com> wrote:

The cable from the headunit is an audio cable, it then goes into an
audio -> serial 9pin converter which I attach to the keyspan HS19-USA
(but previously connected to the sewell serial->usb adaptor that
didn't work very well).

   When you say Audio Cable, do you mean DIN 5 ?

   And the 9pin I assume you mean DB9 ?

   So all that has changed are the cables ? The interface on the Computrainer is still DIN 5 ?

   If so, it's just a question of finding a DIN5 to DB9 and then running that into a HS-19..

   Worst case, you can make your own..

   J 

[Mark Rages]

I am pretty sure your problem is not with Linux-builtin FTDI drivers.
I've used them with no problems on pretty much every Ubuntu version
from 7.10 on. I've found installing the drivers from FTDI / keyspan
to be a big hassle with no upside. So I think you would be wise to
look elsewhere for the problem before spending too much time with
this. A wiring problem perhaps?

If you want to test a serial connection, you can do a "loopback test".
Short TX and RX together. If the serial is on a stereo audio plug,
short the tip and ring together. Then open two terminals. In the
first, type "cat /dev/ttyUSB0". Now it is watching the RX line. In
the second terminal, type "echo hello world > /dev/ttyUSB0". This
will put some data out the TX line. If the serial is working you will
see "hello world" echoed back on the first terminal.

If the loopback test works, basic serial comms are working and it is
not likely to be driver problem.

Do you have access to an oscilloscope?

Regards,
Mark
markrages@gmail
--
Mark Rages, Engineer
Midwest Telecine LLC

mark...@midwesttelecine.com

[Mark Liversedge]

I had blindly assumed that the unit already worked with the Racermate
software on Windows?

It might be worth trying that out first to validate issues unrelated
to GC/Linux?

Cheers,
Mark

[Gareth]

Have you done a:
sudo apt-get update
sudo apt-get install libftdi1 libusb-0.1-4 libc6

This will put you at the latest ftdi drivers for Ubuntu.

There is a later version of libftdi out (http://www.intra2net.com/en/
developer/libftdi/index.php) you could try.

[SebpG]

Thanks for the tip,

but nothing's changed.

Sebp