Skip Menu |

This queue is for tickets about the Audio-Radio-Sirius CPAN distribution.

Report information
The Basics
Id: 47470
Status: open
Priority: 0/
Queue: Audio-Radio-Sirius

People
Owner: jtatum [...] gmail.com
Requestors: cpan [...] dusty.hey.nu
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.03
Fixed in: (no value)



Subject: Does not power on (lag and then fail)
Using Ubuntu Jaunty with this kernel: Linux kairi 2.6.28-13-generic #44-Ubuntu SMP Tue Jun 2 07:55:09 UTC 2009 x86_64 GNU/Linux. I'm using SCHDOC1 (SIRIUS Connect Home Kit) with the SC-H1 USB Interface cable from MJS (rush2112.net). The radio is a Stratus (SV3). When all is powered and plugged in, the radio displays "Sirius Connect". When I connect to the serial port (via this module or even using "cat"), the screen goes blank and the backlight shuts off. I'm using the "ftdi_sio" kernel module (libftdi1 package version 0.13-2). The device shows up as /dev/ttyUSB0. I have changed the ownership of that device to my current user. I had to create the "/etc/modprobe.d/ftdi.conf" file with these contents: "options ftdi_sio vendor=0x0403 product=0xca81". Running the code as root makes no difference in the result. Here is the code that I'm using: ================== #!/usr/bin/perl $| = 1; use Audio::Radio::Sirius; use Device::SerialPort; my $serial = Device::SerialPort->new('/dev/ttyUSB0'); my $tuner = Audio::Radio::Sirius->new; print("Connect... "); print(($tuner->connect($serial) ? 'okay' : 'fail').".\n"); print("Power... "); print(($tuner->power(1) ? 'okay' : 'fail').".\n"); print("Channel... "); print(($tuner->channel(184) ? 'okay' : 'fail').".\n"); ================== Here is the output: ================== Connect... okay. Power... fail. Channel... okay. ================== I'm not sure why power fails but channel claims to succeed. It sits that the "power..." for several minutes before it finishes trying. It stays on "channel..." for what seems to be about 15 seconds. When I dig into the code, I see that the radio is sending between 3 and 5 bytes, but the code is expecting 6.
That's a good one. I have not tried that particular setup but it's my understanding that when controlling the tuner via serial, the display will not activate. You can think of the display as having a similar function to this perl module: Built in display/controls <==> Tuner or Audio::Radio::Sirius <==> Tuner From what I've gathered, the built in controls use the same protocol for communicating with the tuner as are exposed via the serial interface. More than likely, there has been some change to the protocol. Hopefully it isn't too bad. Have you tried setting debug? $tuner->debug=1; should do it. Looks like I forgot to document that setting. Apply that and update this bug with the output. That will hopefully give me something I can take to the kind folks at rush2112.