Author |
Message |
bruce_s01
|
Posted: Thu Apr 19, 2007 6:24 am |
|
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 561
Location:
UK
|
ej4176 wrote: I did not see lp2303 listed anywhere in the messages.log. Maybe its called something differnet on my system? I'm hoping the adapter is whole problem and will report back after trying it. On a bright note I think I fixed my lirc issues.
As you are connecting the device up to the serial port of the KM box, you won't see anything in /var/log/messages.
Bruce S.
_________________ Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P 16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD, SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080 Hauppauage Nova-T 500, Nova-T LinHes R8.6.1
|
|
Top |
|
|
ej4176
|
Posted: Thu Apr 19, 2007 10:37 am |
|
Joined: Sat Apr 07, 2007 8:20 am
Posts: 49
Location:
Mansfield, OH
|
Hmm. ok. My new adapter should be here today and I can work on this now that I have my lirc issues worked out for the most part.
I'll try the cutecom to see if I can get anything working and I'll use 9600 baud for the channel change script as long as it works. I don't think that speed is of the essence in this case.
Thanks!
|
|
Top |
|
|
JoeF
|
Posted: Thu Apr 19, 2007 3:45 pm |
|
Joined: Fri Mar 30, 2007 1:01 pm
Posts: 21
Location:
Santa Ana, CA
|
bruce_s01 wrote: ej4176 wrote: I did not see lp2303 listed anywhere in the messages.log. Maybe its called something differnet on my system? I'm hoping the adapter is whole problem and will report back after trying it. On a bright note I think I fixed my lirc issues. As you are connecting the device up to the serial port of the KM box, you won't see anything in /var/log/messages.
Yeah, you would only see these messages if you connect the USB side to your box. And you would only do that for testing purposes. Sorry if I wasn't clear enough about that.
|
|
Top |
|
|
ej4176
|
Posted: Fri Apr 20, 2007 7:11 pm |
|
Joined: Sat Apr 07, 2007 8:20 am
Posts: 49
Location:
Mansfield, OH
|
I have my new adapter hooked up and here is what I did:
sudo setserial /dev/ttyS0 * flow_on
..and here is teh response I got.
Invalid flag: d11
So the serial port is seeing the d11 but cannot do anything with it. I then tried:
sudo directv.pl off
and got:
Initializing Serial Port...
Retry Fri Apr 20 21:08:03 2007
Retry Fri Apr 20 21:08:05 2007
Retry Fri Apr 20 21:08:07 2007
Retry Fri Apr 20 21:08:09 2007
Error excessive retries
(in cleanup) Can't call method "opened" on an undefined value at /usr/lib/perl5/Device/SerialPort.pm line 2020 during global destruction.
Maybe its just settings in teh setserial command and once I get that right it will work... maybe...
|
|
Top |
|
|
JoeF
|
Posted: Sat Apr 21, 2007 4:29 pm |
|
Joined: Fri Mar 30, 2007 1:01 pm
Posts: 21
Location:
Santa Ana, CA
|
ej4176 wrote: I have my new adapter hooked up and here is what I did:
sudo setserial /dev/ttyS0 * flow_on
..and here is teh response I got.
Invalid flag: d11 Hmm, why is the * there? Do you have a file named d11 in your directory? That would explain the error. Also, forget the whole flow_on stuff. That only works for a Hayes serial board, according to man setserial: "Hayes ESP Configuration Setserial may also be used to configure ports on a Hayes ESP serial board. The following parameters when configuring ESP ports: ... flow_on" I think you can forget the whole setserial stuff. Quote: sudo directv.pl off
and got:
Initializing Serial Port... Retry Fri Apr 20 21:08:03 2007 Retry Fri Apr 20 21:08:05 2007 Retry Fri Apr 20 21:08:07 2007 Retry Fri Apr 20 21:08:09 2007 Error excessive retries (in cleanup) Can't call method "opened" on an undefined value at /usr/lib/perl5/Device/SerialPort.pm line 2020 during global destruction.
Yeah, got the same stuff originally. Check the baudrate, and the serial port.
|
|
Top |
|
|
ej4176
|
Posted: Sun Apr 22, 2007 7:15 am |
|
Joined: Sat Apr 07, 2007 8:20 am
Posts: 49
Location:
Mansfield, OH
|
It works! I think it was a simple as checking permissions and changing the baudrate in the script to 9600. Once I did that it works.
Thanks for the help!
|
|
Top |
|
|
jpitlick
|
Posted: Wed Apr 25, 2007 2:27 pm |
|
Joined: Wed Apr 25, 2007 1:13 pm
Posts: 21
|
I am having the same issue that ej4176 was having. I have made all of the changes outlined in this thread, but the problem persists. I have to try hard setting the port and irq in the BIOS for the serial port. Is there anything else I can check/change to make this work? Thanks.
|
|
Top |
|
|
jpitlick
|
Posted: Wed Apr 25, 2007 2:52 pm |
|
Joined: Wed Apr 25, 2007 1:13 pm
Posts: 21
|
I am having the same issue that ej4176 was having. I have made all of the changes outlined in this thread, but the problem persists. I have to try hard setting the port and irq in the BIOS for the serial port. Is there anything else I can check/change to make this work? Thanks.
|
|
Top |
|
|
bruce_s01
|
Posted: Wed Apr 25, 2007 4:55 pm |
|
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 561
Location:
UK
|
What error messages are you getting if you run the program from the command line?
If you su to root, does it work then?
Bruce S.
_________________ Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P 16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD, SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080 Hauppauage Nova-T 500, Nova-T LinHes R8.6.1
|
|
Top |
|
|
jpitlick
|
Posted: Thu Apr 26, 2007 6:35 am |
|
Joined: Wed Apr 25, 2007 1:13 pm
Posts: 21
|
Below is the output from the directv.pl script run as root. I get the same output regardless of whether or not the serial port is connected, so I know the issue isn't with the USB port on my DTV receiver.
root@mythtv:~# perl /usr/local/bin/directv.pl get_channel
Initializing Serial Port...
Retry Thu Apr 26 08:32:34 2007
Retry Thu Apr 26 08:32:36 2007
Retry Thu Apr 26 08:32:38 2007
Retry Thu Apr 26 08:32:40 2007
Error excessive retries
(in cleanup) Can't call method "opened" on an undefined value at /usr/local/lib/perl/5.8.8/Device/SerialPort.pm line 2020 during global destruction.
BTW I am using an H20 receiver not a D11, but I've read that they take the same commands. My KM box is a 1.6 GHz Dell Dimension, 512 MB RAM, 160 GB IDE HD, Hauppauge PVR-150 MCE.
|
|
Top |
|
|
ej4176
|
Posted: Mon Apr 30, 2007 5:32 am |
|
Joined: Sat Apr 07, 2007 8:20 am
Posts: 49
Location:
Mansfield, OH
|
That's what I was getting too. What USB->serial adapter are you using? Is it one of the ones that is known to work? That may have been my problem all along.
The other thing you can try is to do a :
sudo locate directv.pl
to see if you have more than one copy of the script and then check permissions on both of them.\
Hope that helps.
|
|
Top |
|
|
jpitlick
|
Posted: Mon Apr 30, 2007 7:34 am |
|
Joined: Wed Apr 25, 2007 1:13 pm
Posts: 21
|
I am using a known working USB to serial. It's the BAFO BF-810.
I only have one copy of directv.pl. It's in /usr/local/bin. I have checked all the of the permissions. This doesn't work for root user either.
I tried a test of connecting a null modem cable between my Myth box and a PC running Hyperterminal. When I ran directv.pl, Hyperterminal received the commands. I think the problem is with my DirecTV receiver's USB port, unless the commands are wrong in the directv.pl script.
|
|
Top |
|
|
ej4176
|
Posted: Tue May 08, 2007 7:12 am |
|
Joined: Sat Apr 07, 2007 8:20 am
Posts: 49
Location:
Mansfield, OH
|
Have you tried to change the baud rate in the script to 9600?
You can also try running the script from the command line and see if it works or not. Use something like:
sudo directv.pl off
to see if it working. Once I changed the baud rate it just worked for me.
|
|
Top |
|
|
jpitlick
|
Posted: Tue May 08, 2007 7:29 am |
|
Joined: Wed Apr 25, 2007 1:13 pm
Posts: 21
|
I have tried changing the baud. No go. The problem appears to be on the DirecTV receiver end. Any other ideas? Thanks.
|
|
Top |
|
|
jpitlick
|
Posted: Tue May 08, 2007 7:38 am |
|
Joined: Wed Apr 25, 2007 1:13 pm
Posts: 21
|
This is the output that I get when running the script in verbose mode as root from the command line:
root@mythtv:~# cd /usr/local/bin
root@mythtv:/usr/local/bin# perl directv.pl get_channel
Initializing Serial Port...
SEND: 0xFA [ú] 0x87 []
RECV: Timeout Error
Retry Tue May 8 09:36:57 2007
SEND: 0xFA [ú] 0x87 []
RECV: Timeout Error
Retry Tue May 8 09:36:59 2007
SEND: 0xFA [ú] 0x87 []
RECV: Timeout Error
Retry Tue May 8 09:37:01 2007
SEND: 0xFA [ú] 0x87 []
RECV: Timeout Error
Retry Tue May 8 09:37:03 2007
Error excessive retries
(in cleanup) Can't call method "opened" on an undefined value at /usr/local/lib/perl/5.8.8/Device/SerialPort.pm line 2020 during global destruction.
|
|
Top |
|
|