LinHES Forums http://forum.linhes.org/ |
|
Iguana IR Blaster issues in R6 http://forum.linhes.org/viewtopic.php?f=21&t=20557 |
Page 1 of 1 |
Author: | falinskip [ Sun Nov 22, 2009 8:19 pm ] |
Post subject: | Iguana IR Blaster issues in R6 |
Hi there, I am running R6, (Myth version 21) the standard R6 install with updates (sudo pacman -Syuf). Issue: remote receives fine (I can move about in Myth just fine), but the blaster does not work, Hardware: Streamzap remote IguanaIR USB (I am using it for receiving IR singles and as a blaster to a Motorola VIP 1200). Processes followed In trouble shooting I did the following: chmod 777 /dev/ttyS0 gpasswd -a mythtv uucp Then I checked irsend with the following commands irsend LIST Streamzap_PC_Remote "" irsend LIST "" "" the results were as expected (the remote was there and working). I SSHed into the box and and ran the following commands: irsend send_once Streamzap_PC_Remote POWER irsend send_once Streamzap_PC_Remote MENU irsend send_once VIP1200 POWER /var/log/lircd Results from the log file are as follows: Nov 21 19:39:25 mythbe lircd: removed client Nov 21 19:40:03 mythbe lircd: accepted new client on /dev/lircd Nov 21 19:40:03 mythbe lircd: error processing command: send_once vip1200 POWER Nov 21 19:40:03 mythbe lircd: transmission failed Nov 21 19:40:03 mythbe lircd: removed client Nov 21 19:42:50 mythbe lircd: accepted new client on /dev/lircd Nov 21 19:42:50 mythbe lircd: error processing command: send_once vip1200 POWER Nov 21 19:42:50 mythbe lircd: transmission failed Nov 21 19:42:50 mythbe lircd: removed client Nov 21 19:43:09 mythbe lircd: accepted new client on /dev/lircd Nov 21 19:43:09 mythbe lircd: error processing command: send_once Streamzap_PC_Remote MENU Nov 21 19:43:09 mythbe lircd: transmission failed Nov 21 19:43:09 mythbe lircd: removed client Nov 21 19:43:17 mythbe lircd: accepted new client on /dev/lircd Nov 21 19:43:17 mythbe lircd: error processing command: send_once Streamzap_PC_Remote POWER Nov 21 19:43:17 mythbe lircd: transmission failed Nov 21 19:43:17 mythbe lircd: removed client Nov 21 19:48:30 mythbe lircd: accepted new client on /dev/lircd Nov 21 19:48:30 mythbe lircd: error processing command: send_once Streamzap_PC_Remote POWER If someone could point me in the right direction it would be much appreciated. Afterward I will post to flyspray so it can be included in the future. Thanks, Paul |
Author: | falinskip [ Wed Nov 25, 2009 8:15 pm ] |
Post subject: | I just needed to adjust some scripts |
This is what I did first chmod 777 /dev/ttyS0 gpasswd -a mythtv uucp Then I started trouble shooting the iguana IR USB blaster it's self, I was getting the following in the log file: Nov 21 08:51:35 mythbe lircd: WARNING: Failed to initialize hardware Nov 21 08:51:37 mythbe lircd: accepted new client on /dev/lircd Nov 21 08:52:19 mythbe lircd: accepted new client on /dev/lircd Nov 21 08:53:05 mythbe lircd: caught signal Nov 21 08:53:10 mythbe lircd: lircd(iguanaIR) ready Nov 21 08:53:17 mythbe lircd: accepted new client on /dev/lircd Nov 21 08:53:17 mythbe lircd: couldn't open connection to iguanaIR daemon: No such file or directory Nov 21 08:53:17 mythbe lircd: WARNING: Failed to initialize hardware Nov 21 08:53:22 mythbe lircd: removed client Nov 21 08:53:27 mythbe lircd: accepted new client on /dev/lircd Nov 21 08:53:27 mythbe lircd: couldn't open connection to iguanaIR daemon: No such file or directory Nov 21 08:53:27 mythbe lircd: WARNING: Failed to initialize hardware Nov 21 08:54:17 mythbe lircd: removed client Nov 21 09:04:13 mythbe lircd: caught signal Nov 21 09:04:53 mythbe lircd: lircd(iguanaIR) ready Nov 21 09:04:57 mythbe lircd: accepted new client on /dev/lircd Nov 21 09:04:59 mythbe lircd: accepted new client on /dev/lircd Nov 21 09:08:05 mythbe lircd: trigger Nov 21 09:08:06 mythbe lircd: trigger More Trouble shooting on the iguana IR USB igclient --get-version get version: success: version=0x0306 igclient --get-features get features: success: features=0x4 igclient --get-channels get channels: success: channels=0x00 I then set the channel to 1 igclient --set-channels=1 Tested it with the manual irsend command using the commands from my VIP1200 settopbox and it worked. irsend send_once VIP1200 POWER Next I modified the script below to incorperate the igclient set channel (also please note in this script is some extra wait time for my ATT VIP1200 box to "wake up" all the way). channel_change.sh script below #!/bin/sh REMOTE_NAME=VIP1200 cmd="$1" case $cmd in [0-9]*) for digit in $(echo $1 | sed -e 's/./& /g'); do irsend SEND_ONCE $REMOTE_NAME $digit sleep 0.5 # If things work OK with sleep 1, try this for faster channel changes: # sleep 0.3 done ;; *) irsend SEND_ONCE $REMOTE_NAME $cmd ;; esac irsend SEND_ONCE $REMOTE_NAME ENTER # line below is used to select the channel going to the iguana USB send # to either channel 1 or channel 3, channel 1 is for first blaster igclient --set-channels=1 # to either channel 1 or channel 3, channel 3 is for second blaster #igclient --set-channels=3 # /usr/bin/fix_audio.sh & # end of channel_change script I also have ran into some issues where from a vanilla install of R6 (myth 21) that the iguana driver stops working. Normally after midnight (I have not looked into commercial flagging, but I will soon). I then created the script below and setup a cron job to have it restart the damon at like 12:05 AM. Here it is in case anyone needs it. #!/bin/bash # Script for fixing lockup issue with iguana. Locking up at midnight every # night, run script at 5 min after midnight to fix # Paul Falinski version 1 - 11-25-2009 sudo sv stop igdaemon sleep 0.3 sudo sv start igdaemon |
Author: | falinskip [ Fri Nov 27, 2009 8:11 am ] |
Post subject: | |
I am still running into issues where the iguana stops working (blasting and receiving). It looks like it may have issues (possibly not running as root) igdamon.log file Nov 23 18:53:12 2009 ERROR: Failed to get version. Nov 23 21:08:08 2009 ERROR: failed to write control packet: Failed to write (in$ Nov 23 21:08:08 2009 ERROR: Failed to disable the receiver. Nov 23 21:26:51 2009 ERROR: Failed to get version. Nov 25 08:39:57 2009 ERROR: failed to write control packet: Failed to write (in$ Nov 25 08:39:57 2009 ERROR: Failed to disable the receiver. Nov 25 08:54:30 2009 ERROR: failed to write control packet: Failed to write (in$ Nov 25 08:54:30 2009 ERROR: Failed to disable the receiver. Nov 25 09:29:30 2009 ERROR: failed while reaping worker thread. Nov 25 15:06:23 2009 ERROR: select failed: Interrupted system call Nov 25 15:06:23 2009 ERROR: failed while reaping worker thread. Nov 25 19:16:50 2009 ERROR: failed to write control packet: Failed to write (in$ Nov 25 19:16:50 2009 ERROR: Failed to disable the receiver. Nov 25 20:19:47 2009 ERROR: failed to write control packet: Failed to write (in$ Nov 25 20:19:47 2009 ERROR: Failed to disable the receiver. Nov 26 20:57:42 2009 ERROR: Failed to get version. Nov 26 21:04:45 2009 ERROR: failed to write control packet: Failed to write (in$ Nov 26 21:04:45 2009 ERROR: Failed to disable the receiver. Nov 26 21:04:47 2009 ERROR: trying to claim usb:4:3 lircd logfile Nov 27 07:30:03 mythbe lircd: transmission failed Nov 27 07:30:03 mythbe lircd: removed client Nov 27 07:30:32 mythbe lircd: accepted new client on /dev/lircd Nov 27 07:30:32 mythbe lircd: error processing command: SEND_ONCE VIP1200 OK Nov 27 07:30:32 mythbe lircd: transmission failed Nov 27 07:30:32 mythbe lircd: removed client Nov 27 07:30:32 mythbe lircd: accepted new client on /dev/lircd Nov 27 07:30:32 mythbe lircd: error processing command: SEND_ONCE VIP1200 8 Nov 27 07:30:32 mythbe lircd: transmission failed Nov 27 07:30:33 mythbe lircd: removed client Nov 27 07:30:33 mythbe lircd: accepted new client on /dev/lircd Nov 27 07:30:33 mythbe lircd: error processing command: SEND_ONCE VIP1200 0 Nov 27 07:30:33 mythbe lircd: transmission failed Nov 27 07:30:33 mythbe lircd: removed client Nov 27 07:30:34 mythbe lircd: accepted new client on /dev/lircd Nov 27 07:30:34 mythbe lircd: error processing command: SEND_ONCE VIP1200 5 Nov 27 07:30:34 mythbe lircd: transmission failed Nov 27 07:30:34 mythbe lircd: removed client |
Author: | falinskip [ Sun Nov 29, 2009 6:04 pm ] |
Post subject: | Added a Powered USB hub |
Well after some searching, I noticed that the guy's using the commandIR product (another USB based receiver/blaster) had issues with some newer USB chipsets (in particular Nvidia). I am running a Asus M4A78-EM board with a Nvidia 8400 video card. The chip set is AMD708g / SB700 for this board. What they did to fix the issue was to put Powered USB hub between the commandIR and the motherboard. Well I gave this a try for the IguanaIR USB and it seems to have made a difference. For whatever reason, I have not had the IguanaIR USB fail to receive or blast for over 24 hours now. Before I could not go even 12 hours without the device (IguanaIR) would stop working. I am currently running the lirc version: lircd 0.8.5-CVS-pvr150 If I have more success I will post it here. |
Author: | cliffsjunk [ Tue Jan 05, 2010 11:52 am ] |
Post subject: | Don't give Iguanaworks your hard earned money! |
First of all, I am not a newby. I've been a systems programmer and hardware hacker for 30 years. I am very familiar with Linux in general and KM R5.5. Iguanaworks USB would not work for me on R5 or R5.5. They said they would look into it and get back. They never did get back. After a few encouraging emails, I emailed maybe 5 times over the course of a year, ALL IGNORED. Maybe a year ago, I helped my brother in law set up an R5.5 system and told him to get a serial Lirc/Blaster and stay away from the Iguanaworks USB device. What did he do? You guessed it. Following all the instructions on the Iguanaworks web site and Googling for help for days did not fix it. There are several ways of setting it up. None of them produced a 100% working system. I have a couple of their serial devices and they work, but I am not sending any more money to them, ever. Cliff |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |