[mythtv-users] DirecTV D11-500 Control Issue

[John P Poet]

On 7/3/07, Rich West <Rich.West at wesmo.com> wrote:
> John P Poet wrote:
> > On 6/30/07, Rich West <Rich.West at wesmo.com> wrote:
> >
> >> John P Poet wrote:
> >>
> >>> On 6/25/07, Rich West <Rich.West at wesmo.com> wrote:
> >>>
> >>>
> >>>> John P Poet wrote:
> >>>>
> >>>>
> >>>>> On 6/23/07, jmk <jmk at foofus.net> wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> [1] The Wiki states that the adapters found at the URL below have been
> >>>>>> successfully tested. I am assuming that EMT is now shipping something
> >>>>>> other than what was tested. I received two "HL-340" adapters. They do
> >>>>>> not look like what is pictured and contain a FTDI-based chipset, which
> >>>>>> does not appear to have Linux support.
> >>>>>>
> >>>>>> http://www.emtcompany.com/products/adapters/dxubdb9-usb-to-serial-db9-adapter-cable.htm
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> Ug!  I ordered one of the EMTC adaptors on Thursday, for this purpose.
> >>>>>  Guess I will be sending it back.
> >>>>>
> >>>>> Thanks for the info.
> >>>>>
> >>>>>
> >>>> Ack.  Did you call/email them to point out the difference?
> >>>>
> >>>> I had bought the USB->Serial adapters from that link early on (I have 4
> >>>> of them), and they were as pictured on the site and the worked perfectly
> >>>> out of the box..
> >>>>
> >>>> -Rich
> >>>>
> >>>>
> >>> I emailed them, asking if there was a difference.  They have not
> >>> gotten back to me yet.
> >>>
> >>> Assuming they already shipped my order, I will try it before sending it back.
> >>>
> >> Any news?  I'm curious because I am looking to order another 2.
> >>
> >> -Rich
> >>
> >
> > The adaptor arrived today.  It does look different than the picture on
> > the EMTC website (for example, it is green instead of blue).  As far
> > as I can tell, it does not work.
> >
> > If I plug it into my Fedora Core 6 box, I get:
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > usb 2-1: new full speed USB device using uhci_hcd and address 3
> > usb 2-1: configuration #1 chosen from 1 choice
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > Which is not terribly helpful.
> >
> > If I plug it into my H20-100, and try to use the directv.pl script, I get:
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > # directv.pl baudrate 9600 verbose setup_channel 240
> > Initializing Serial Port...
> > SEND: 0xFA [�] 0x82 [�]
> > RECV: Timeout Error
> >
> >
> > Retry Mon Jul  2 20:33:50 2007
> > SEND: 0xFA [�] 0x82 [�]
> > RECV: Timeout Error
> >
> >
> > Retry Mon Jul  2 20:33:52 2007
> > SEND: 0xFA [�] 0x82 [�]
> > RECV: Timeout Error
> >
> >
> > Retry Mon Jul  2 20:33:54 2007
> > SEND: 0xFA [�] 0x82 [�]
> > RECV: Timeout Error
> >
> >
> > Retry Mon Jul  2 20:33:56 2007
> > Error excessive retries
> >         (in cleanup) Can't call method "opened" on an undefined value
> > at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Device/SerialPort.pm
> > line 2020 during global destruction.
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > I have tried both versions of the directv.pl script on the wiki.  I
> > have tried using every box_type.  I have tried 9600 and 19200 baud.
> >
> > Anything else I can try?
>
> Hrmm.. it looks like the system is able to recognize that there is a USB
> device there.. that's a start. :)
>
> What is the output from "lsusb" (from the "usbutils" package)?  For
> example, mine looks like:
> [root at mythtv1 ~]# lsusb
> Bus 003 Device 001: ID 0000:0000
> Bus 004 Device 001: ID 0000:0000
> Bus 002 Device 001: ID 0000:0000
> Bus 002 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
> Port
> Bus 001 Device 004: ID 0557:2008 ATEN International Co., Ltd UC-232A
> Serial Port [pl2303]
> Bus 001 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
> Port
> Bus 001 Device 001: ID 0000:0000
> Bus 005 Device 001: ID 0000:0000



The output of lsusb is the same whether the EMTC usb-serial adaptor is
installed, or not:

Bus 002 Device 004: ID 4348:5523
Bus 002 Device 001: ID 0000:0000
Bus 002 Device 002: ID 051d:0002 American Power Conversion Back-UPS
Pro 500/1000/1500
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 005: ID 0557:2205 ATEN International Co., Ltd
Bus 001 Device 004: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub

With:

usb 2-1: new full speed USB device using uhci_hcd and address 4
usb 2-1: configuration #1 chosen from 1 choice

Showing up in dmesg.   This Indicates to me, that it does not have a
proper driver for it, which probably means the H20 does not have a
driver for it.


> Also, and this is probably a dumb question, but is this a new set up or
> are you trying this in a configuration which had worked previously?  I
> ask because the timeout error is a common indicator of a mis-wired cable.

Brand new setup.  I am hooking up a null-modem 9pin rs232 cable from
my computer to the EMTC usb-serial adaptor, then plugging the
usb-serial adaptor into the back of my H20.

I have been using an old ir-blaster to control the H20.  Fortunately
it has worked flawlessly -- once I figured out the magic trick.  After
fighting with it for around an hour and a half (and getting about 15%
reliable channel changes), I finally figured out that I needed to
cover up the ir-receiver and ir-blaster, so *only* the ir light was in
play.  Stray light from the room seem to make the communication more
miss than hit.

I want to switch to the usb/serial control just because it is cleaner
and should be even more reliable.


John
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?