I don't have any serial controlled devices, but that sound like either: 1. You do not have your serial port configured correctly in the kernel, or
2. The pin-out on the cable is wrong. It appears to not be communicating at all from the messages. On Sun, 2005-12-18 at 16:53 -0700, Chris wrote: > I've tried that previously, here's what I get: > > sudo ./channel -vv > Attempting to initialize DCT > SENT: type 0x70, len 2, id 0x04, seq 0x03 > Serial timeout > No response to packet > No response to init_1; trying to continue > SENT: type 0x78, len 3, id 0x04, seq 0x03 > data 0x00 > Serial timeout > No response to packet > No response to initialize_2 > Initialization failed > Attempting to initialize DCT > SENT: type 0x70, len 2, id 0x04, seq 0x03 > Serial timeout > No response to packet > No response to init_1; trying to continue > SENT: type 0x78, len 3, id 0x04, seq 0x03 > data 0x00 > Serial timeout > No response to packet > No response to initialize_2 > Initialization failed > Attempting to initialize DCT > SENT: type 0x70, len 2, id 0x04, seq 0x03 > Serial timeout > No response to packet > No response to init_1; trying to continue > SENT: type 0x78, len 3, id 0x04, seq 0x03 > data 0x00 > Serial timeout > No response to packet > No response to initialize_2 > Initialization failed > Attempting to initialize DCT > SENT: type 0x70, len 2, id 0x04, seq 0x03 > Serial timeout > No response to packet > No response to init_1; trying to continue > SENT: type 0x78, len 3, id 0x04, seq 0x03 > data 0x00 > Serial timeout > No response to packet > No response to initialize_2 > Initialization failed > Attempting to initialize DCT > SENT: type 0x70, len 2, id 0x04, seq 0x03 > Serial timeout > No response to packet > No response to init_1; trying to continue > SENT: type 0x78, len 3, id 0x04, seq 0x03 > data 0x00 > Serial timeout > No response to packet > No response to initialize_2 > Initialization failed > Communication failed after 5 tries > 0 > [EMAIL PROTECTED] dct-channel]$ > > > > On Sun, 2005-12-18 at 15:40 -0800, Ian Forde wrote: > > On Sun, 2005-12-18 at 16:31 -0700, Chris wrote: > > > Can you be more specific please? > > > > > > /usr/share/doc/mythtv-0.18.1/contrib > > > [EMAIL PROTECTED] contrib]$ ls > > > 6200ch.c myth_archive_job.pl > > > 6200ch-README mythencode.pl > > > change-channel-lirc.pl mythlink.sh > > > change-channel-lirc.sh mythmail > > > dct2000serial.tar.gz mythmaillog.pl > > > dct-channel mythname.pl > > > etc.init.d.mythbackend.lsb mythnotify > > > etc.rc.d.init.d.mythbackend myth.rebuilddatabase.pl > > > etc.security.msec.perm.local README.for.mythencode.and.mythname > > > etc.sysconfig.mythbackend temp > > > mandrake91.etc.sysconfig.lircd trailer.pl > > > master_iconmap.xml trailer.pl.README > > > mkiconmap.pl trailer.pl.svnfixes > > > mplayernetwork.pl tsc-calibrate.c > > > > dct-channel > > > > -I > > > > > > On Sun, 2005-12-18 at 15:27 -0800, Ian Forde wrote: > > > > On Sun, 2005-12-18 at 15:45 -0700, Chris wrote: > > > > > I've been trying for some time now to get serial channel changing > > > > > working, hopefully someone here can provide me with some insight into > > > > > the whole problem. > > > > > > > > > > I've got the following: > > > > > 2x Motorola DCT-2224, firmware version: 7.93 > > > > > 1x Motorola DCT-2524, firmware version: 2.54 > > > > > > > > > > I've tried a few different scripts to just try and change the channel > > > > > for now, none of which seem to work. When I connect the serial port > > > > > of a > > > > > windows box to these DCTs, hitting enter results in gibberish coming > > > > > back from the DCT, followed by the f/w version. I assume this is some > > > > > sort of menu prompt (VxWorks?), the reason I assume this is because > > > > > when > > > > > I go through the alphabet on the 2524, different keys produce > > > > > different > > > > > outputs. Seeing as I get gibberish from all three is it safe to assume > > > > > that their serial ports are enabled? > > > > > > > > > > When I run the serial cable from the FC4 box to the windows box and > > > > > run > > > > > the python scripts, I do get output over in Hyperterm, so it looks > > > > > like > > > > > I'm sending the data out. > > > > > > > > > > I remember reading in one of the python scripts that it wanted v2.2, > > > > > but > > > > > on my new FC4 box, I have python 2.4 installed, should this be an > > > > > issue? > > > > > > > > Mmm... Just took a look at it - I haven't used (or even looked at) the > > > > code in a while. Python 2.4 is definitely going to be a problem, IMHO. > > > > I remember having issues with Python 2.3 as well... Best bet is to use > > > > the C code in contrib/ instead... > > > > > > > > > I seem to be able to get everything else working except serial channel > > > > > changing, so hopefully someone will be able to help me out. > > > > > > > > > > Thanks, > > > > > -Chris > > > > > > > > > > _______________________________________________ > > > > > mythtv-users mailing list > > > > > [email protected] > > > > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > > > > > _______________________________________________ > > > > mythtv-users mailing list > > > > [email protected] > > > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > > > _______________________________________________ > > > mythtv-users mailing list > > > [email protected] > > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > _______________________________________________ > > mythtv-users mailing list > > [email protected] > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > _______________________________________________ > mythtv-users mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
