lirc-list

Re: Lirc Compilation problem.

[endeavor j. <jen...@gm...>]

Hi Team,
I am able to compile LIRC,
on our board IR reciever is connected to UART via MCU.
So i built lirc with --with driver=serial option and did
 setserial /dev/ttyS1 uart none
But still it gives
 insmod lirc_serial.ko
lirc_serial: port 03f8 already in use
lirc_serial: use 'setserial /dev/ttySX uart none'
lirc_serial: or compile the serial port driver as module and
lirc_serial: make sure this module is loaded first
insmod: can't insert 'lirc_serial.ko': Device or resource busy

Please help me how to configure LIRC for this

Thanks,
John



On Fri, Nov 9, 2012 at 6:39 PM, Jonathan Isom <je...@gm...> wrote:

>
>
> On Friday, November 9, 2012, endeavor john wrote:
>
>> Hi Team ,
>> I am cross compiling the LIRC for CE4100 target.
>> I am using following config options :
>> export CONFIG_SITE=./canmore.config
>>
>> ./configure $DEBUG_OPTIONS --prefix=/opt/canmore/local
>> --host=i686-cm-linux
>> --with-kerneldir=/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35
>> --with-moduledir=/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/root/lib/modules
>> --without-x --with-driver=mceusb
>> When i try to compile i get the following error:
>>
>> make -f scripts/Makefile.build obj=/root/lirc/lirc-0.8.7/drivers/lirc_dev
>>   gcc -Wp,-MD,/root/lirc/lirc-0.8.7/drivers/lirc_dev/.lirc_dev.o.d
>>  -nostdinc -isystem /usr/lib/gcc/i686-linux-gnu/4.6/include
>> -I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35/arch/x86/include
>> -Iinclude  -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef
>> -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
>> -Werror-implicit-function-declaration -Wno-format-security
>> -fno-delete-null-pointer-checks -O2 -m64 -mno-red-zone -mcmodel=kernel
>> -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI_SIGNAL_FRAME=1
>> -DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare
>> -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
>> -fno-stack-protector -fomit-frame-pointer -Wdeclaration-after-statement
>> -Wno-pointer-sign -fno-strict-overflow -fconserve-stack
>> -DIRCTL_DEV_MAJOR=61 -DEXPORT_SYMTAB -DHAVE_CONFIG_H -I. -I../..
>> -I/root/lirc/lirc-0.8.7/drivers/lirc_dev/.
>> -I/root/lirc/lirc-0.8.7/drivers/lirc_dev/.
>> -I/root/lirc/lirc-0.8.7/drivers/lirc_dev/../..
>> -I/root/lirc/lirc-0.8.7/drivers/lirc_dev/../..
>> -I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35//include/
>> -I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35//drivers/media/video/
>>  -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(lirc_dev)"
>>  -D"KBUILD_MODNAME=KBUILD_STR(lirc_dev)"  -c -o
>> /root/lirc/lirc-0.8.7/drivers/lirc_dev/lirc_dev.o
>> /root/lirc/lirc-0.8.7/drivers/lirc_dev/lirc_dev.c
>> *cc1: fatal error: include/generated/autoconf.h: No such file or
>> directorythe same.*
>>
>>  Hi. It is looking for a configured linux kernel. You'll need the same
> as the ce4100 has installed or will have installed. Newer kernels have mce
> device in tree. Are you replacing the kernel? It appears that you have
> 2.6.35 you are working with. I think it wasn't in tree until 2.6.39.
>
> HTH
>
> Jonathan
>
>
>> *Please let me know how to fix *
>> *Thanks,*
>> *John*
>>
>>

Re: LIRC mode2 could not open /dev/lirc

[endeavor j. <jen...@gm...>]

Hello Team,
 our Remote receiver is connected to mcu. and mcu connect ce4100 with a
uart.
Please let me know how to configure the LIRC to recognize my remote.
Thanks,
John

On Thu, Nov 29, 2012 at 5:52 PM, endeavor john <jen...@gm...> wrote:

> Hi All,
> I have build LIRC using following options
> /configure $DEBUG_OPTIONS ----without-x --with-driver=mceusb
> when i tried to run mode2:
> mode2: could not open /dev/lirc
> mode2: default_init(): No such device
> # ls -l /dev/lirc
> crwxrwxrwx    1 root     0          61,   0 Jan  1  2000 /dev/lirc
> #
> This means that lirc is not configured proparly, I am not running LIRCD
> daemon while running mode2?
> Can you please help me fix this?
> Thanks,
> John
>
>
>

LIRC mode2 could not open /dev/lirc

[endeavor j. <jen...@gm...>]

Hi All,
I have build LIRC using following options
/configure $DEBUG_OPTIONS ----without-x --with-driver=mceusb
when i tried to run mode2:
mode2: could not open /dev/lirc
mode2: default_init(): No such device
# ls -l /dev/lirc
crwxrwxrwx    1 root     0          61,   0 Jan  1  2000 /dev/lirc
#
This means that lirc is not configured proparly, I am not running LIRCD
daemon while running mode2?
Can you please help me fix this?
Thanks,
John

Need help with LIRC and HVR-2250

[Luc G. <luc...@gm...>]

Hi everyone,

I've got a mythtv setup and am using an ATI Remote Wonder II to
control the MythTV box, so am not using LIRC for that.

What I want to use LIRC for is sending channel change commands for my
DCT700 STB.

I have an HVR-2250 as my main input source and I have a IR Blaster
connected to it.

I read around that for most HVR cards, using the lirc_zilog module is
a way of getting it working. I have not seen any 100% confirmation of
this, so I have assumed it will work and am following the process that
others have to get it working.

I posted on the Mythbuntu forum but have not received any replies. No
point rephrasing here, here's what I posted
(http://ubuntuforums.org/showthread.php?t=2088142):

****
I'm running Mythbuntu 12.04, kernel version 3.2.0-32, and I am trying
to get the IRBlaster working on my Hauppauge HVR-2250. I installed
LIRC from the Mythbuntu Software Center and I deduced that I need to
load the lirc_zilog module.... I followed the instructions located
here:

http://jaysdesktop.blogspot.ca/2012/06/configuring-lirc-for-hvr-1600-in-ubuntu.html

As that post states, the lirc-modules-source package is not available
for 12.04, so I took the lirc_zilog.ko from my staging directory
(/lib/modules/3.2.0-32-generic/kernel/drivers/staging/media/lirc) and
placed it in here:
/lib/modules/3.2.0-32-generic/kernel/drivers/staging/media/lirc/lirc_zilog.ko

When I try to modprobe lirc_zilog I get

[ 1419.291447] lirc_zilog: disagrees about version of symbol
lirc_register_driver
[ 1419.291458] lirc_zilog: Unknown symbol lirc_register_driver (err -22)

I'd like some help in resolving this conflict.

I also tried doing what the post suggests and downloading the .deb
file and extracting the lirc_zilog.ko file, but it has the same
results.

****

I can kind of deduce the module is not of the proper version, but if I
don't have access to the lirc-modules-source, I can't do a
reconfigure, so I just don't see how I am supposed to get modules of
the proper version? Anyway, any help I could get would be awesome as
I'm really almost there with this box, only missing this piece.
Thanks,

Luc

Getting LIRC working

[endeavor j. <jen...@gm...>]

Hello Team,
I am able to install LIRC drivers on to board.
*lirc_dev: IR Remote Control driver registered, major 61*
*lirc_mceusb: Windows Media Center Edition USB IR Transceiver driver for
LIRC 1.90*
*But i tried starting lirc service*
*
 /opt/canmore/local/sbin/lircd /etc/lircd.conf

But remote control does'nt seem to work at all, we find no logs ub
/var/log/messages.
Please do help with this,
Thanks,
Rashmi
*


On Fri, Nov 9, 2012 at 12:32 PM, endeavor john <jen...@gm...> wrote:

> Hi Team ,
> I am cross compiling the LIRC for CE4100 target.
> I am using following config options :
> export CONFIG_SITE=./canmore.config
>
> ./configure $DEBUG_OPTIONS --prefix=/opt/canmore/local
> --host=i686-cm-linux
> --with-kerneldir=/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35
> --with-moduledir=/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/root/lib/modules
> --without-x --with-driver=mceusb
> When i try to compile i get the following error:
>
> make -f scripts/Makefile.build obj=/root/lirc/lirc-0.8.7/drivers/lirc_dev
>   gcc -Wp,-MD,/root/lirc/lirc-0.8.7/drivers/lirc_dev/.lirc_dev.o.d
>  -nostdinc -isystem /usr/lib/gcc/i686-linux-gnu/4.6/include
> -I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35/arch/x86/include
> -Iinclude  -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef
> -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
> -Werror-implicit-function-declaration -Wno-format-security
> -fno-delete-null-pointer-checks -O2 -m64 -mno-red-zone -mcmodel=kernel
> -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI_SIGNAL_FRAME=1
> -DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare
> -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
> -fno-stack-protector -fomit-frame-pointer -Wdeclaration-after-statement
> -Wno-pointer-sign -fno-strict-overflow -fconserve-stack
> -DIRCTL_DEV_MAJOR=61 -DEXPORT_SYMTAB -DHAVE_CONFIG_H -I. -I../..
> -I/root/lirc/lirc-0.8.7/drivers/lirc_dev/.
> -I/root/lirc/lirc-0.8.7/drivers/lirc_dev/.
> -I/root/lirc/lirc-0.8.7/drivers/lirc_dev/../..
> -I/root/lirc/lirc-0.8.7/drivers/lirc_dev/../..
> -I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35//include/
> -I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35//drivers/media/video/
>  -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(lirc_dev)"
>  -D"KBUILD_MODNAME=KBUILD_STR(lirc_dev)"  -c -o
> /root/lirc/lirc-0.8.7/drivers/lirc_dev/lirc_dev.o
> /root/lirc/lirc-0.8.7/drivers/lirc_dev/lirc_dev.c
> *cc1: fatal error: include/generated/autoconf.h: No such file or
> directorythe same.*
>
> *Please let me know how to fix *
> *Thanks,*
> *John*
>
>

Re: Lirc and long keypresses.

[Anders T. <aer...@gm...>]

On 2012-11-15 03:44, Mark DM wrote:
> I see that there seems to be some issues with getting LIRC to
> recognize long keypresses , however this seems to also baffle me as to
> why .  see http://forum.xbmc.org/showthread.php?tid=115023
>
> I have a Creative Labs Sound Blaster Audigy 2 NX . I only use the IR
> functionality.
>
> When I launch irw and hit a key I see this
> 000000000000001f 00 ok RM-1500
> with "ok" corresponding to the key pressed.
>
> Now with irw if I press and hold a key for about 3 seconds I see this
> 000000000000001f 00 ok RM-1500
> 000000000000001f 01 ok RM-1500
> 000000000000001f 02 ok RM-1500
> 000000000000001f 03 ok RM-1500
> 000000000000001f 04 ok RM-1500
> 000000000000001f 05 ok RM-1500
> 000000000000001f 06 ok RM-1500
> 000000000000001f 07 ok RM-1500
> 000000000000001f 08 ok RM-1500
> 000000000000001f 09 ok RM-1500
> 000000000000001f 0a ok RM-1500
> 000000000000001f 0b ok RM-1500
> Clearly the entry before "ok" corresponds to the time the button was pressed.
>
> My question is therefore very simple.....
>
> Since we can now use simply "ok" to identify that the "ok" button was
> pressed, why can we not identify a duration by saying instead of "ok"
> we say , "0b ok" meaning a three second button press would yield a
> specific behavior? I see no issue in making this an option ,
> especially when the button does not conflict with another use. An
> example would be when XBMC is not running and I want to long press
> "ok" or "0b ok" to start XBMC, but that does not mean I want to launch
> XBMC when the remote falls on the floor and that button gets pressed,
> or when the cat steps on it while chasing a fly. In fact it coul;d
> probably be implemented while leaving compatibility with older
> configuration files as only those needing long keypresses would
> require the additional "0b"
>
>
Each non- "00" event generates a "REP" style repeat event when fed into 
the input subsystem. I've configured mouse emulation using this to make 
the mouse accelerate when I press and hold a direction button. X's mouse 
stuff require repeats to be distinguished from a batch of single events. 
I guess you can write an input listener which does something if the 
repeats are 11 or so..

/Anders

Lirc and long keypresses.

[Mark DM <mar...@gm...>]

I see that there seems to be some issues with getting LIRC to
recognize long keypresses , however this seems to also baffle me as to
why .  see http://forum.xbmc.org/showthread.php?tid=115023

I have a Creative Labs Sound Blaster Audigy 2 NX . I only use the IR
functionality.

When I launch irw and hit a key I see this
000000000000001f 00 ok RM-1500
with "ok" corresponding to the key pressed.

Now with irw if I press and hold a key for about 3 seconds I see this
000000000000001f 00 ok RM-1500
000000000000001f 01 ok RM-1500
000000000000001f 02 ok RM-1500
000000000000001f 03 ok RM-1500
000000000000001f 04 ok RM-1500
000000000000001f 05 ok RM-1500
000000000000001f 06 ok RM-1500
000000000000001f 07 ok RM-1500
000000000000001f 08 ok RM-1500
000000000000001f 09 ok RM-1500
000000000000001f 0a ok RM-1500
000000000000001f 0b ok RM-1500
Clearly the entry before "ok" corresponds to the time the button was pressed.

My question is therefore very simple.....

Since we can now use simply "ok" to identify that the "ok" button was
pressed, why can we not identify a duration by saying instead of "ok"
we say , "0b ok" meaning a three second button press would yield a
specific behavior? I see no issue in making this an option ,
especially when the button does not conflict with another use. An
example would be when XBMC is not running and I want to long press
"ok" or "0b ok" to start XBMC, but that does not mean I want to launch
XBMC when the remote falls on the floor and that button gets pressed,
or when the cat steps on it while chasing a fly. In fact it coul;d
probably be implemented while leaving compatibility with older
configuration files as only those needing long keypresses would
require the additional "0b"

I understand that the idea above is not what they were looking for in
the apple thread, but a step in the right direction.

As I recall the apple remote seems to have a very fast repeat rate,
and maybe much faster than my creative remote and in relation to the
apple thread if the repeat rate was twice the rate of the creative
well 1/8 of a second is not too much of a lag to wait to see if there
is a long keypress or not. Also recognizing that only certain buttons
would have dual function for long or short press this lag would not
even have to apply to all buttons

Maybe there is something I am missing and it can already be done?

Just my two cents from someone trying to use this stuff!

 Mark

Question on using irexec with virtual remote

[Aurelien B. <aur...@gm...>]

Hi,

I have setting up a lirc configuration with receiver/transmitter module on
a raspberrypi card.
It's seems to work nice (exept maybe to record ir codes, I made the config
on my main pc).
I'm using a software on my android phone to send codes through network. It
works to send real ir codes to my devices.

Now, I would launch a specific software/script from a received network code
(based on remotes stored in lirc).
Is there a way to do this with irexec?

When I try from command line with irsend (from another computer) nothing
works with irexec.

Regards.
Aurelien

Re: Can I transmit the serial signal over 50 feet of CAT5 cable

[VDR U. <use...@gm...>]

On Sun, Nov 11, 2012 at 6:27 AM, Jim Bojan <boj...@gm...> wrote:
> I have successfully constructed an IR receiver to RS232 and controlled my
> XBMC box with that.  I would like to place the HTPC out of site, and run the
> serial cable through the wall with the IR receiver placed under the wall
> mounted TV.  I tried extending my wire (about 50 feet of CAT5 by the time I
> routed down through the basement and back up behind the TV) and did not get
> a signal.  I assume this is due to the length of wire.  Obviously I can get
> an IR repeater, but that seems inefficient.  I would rather have a powered
> IR receiver that would push the RS232 signal through the wire to the serial
> port on the computer.  Is there such a thing, or can I hack an IR repeater
> to act like this?

I'm actually doing this with one of my htpcs. I built a homebrew
serial IR which is @ the tv, then it runs over cat5 to the box which
is roughly 60ft. away. In total it signal goes through: tv -> 3ft to
wallplate connector -> about 60ft run outside -> wallplate connector
-> 4ft to serial port. It works here just fine with only the wire. The
only problem I had was making sure the HDMI cable from the box to the
tv didn't run along side it. I'm guessing the reason it's not working
for you is cable quality. I don't think it makes any difference which
wires I used in the cat5 but I can check if you like.

Can I transmit the serial signal over 50 feet of CAT5 cable

[Jim B. <boj...@gm...>]

I have successfully constructed an IR receiver to RS232 and controlled my
XBMC box with that.  I would like to place the HTPC out of site, and run
the serial cable through the wall with the IR receiver placed under the
wall mounted TV.  I tried extending my wire (about 50 feet of CAT5 by the
time I routed down through the basement and back up behind the TV) and did
not get a signal.  I assume this is due to the length of wire.  Obviously I
can get an IR repeater, but that seems inefficient.  I would rather have a
powered IR receiver that would push the RS232 signal through the wire to
the serial port on the computer.  Is there such a thing, or can I hack an
IR repeater to act like this?

Thanks

-- 
Jim Bojan
boj...@gm...
-------------------------------------------------------------------------------------------------------
*Praying for a blessing through adoption*
View our profile for
adoption<http://www.angeladoptioninc.com/component/option,com_family/Itemid,137/id,283/view,detail/>

Lirc Compilation problem.

[endeavor j. <jen...@gm...>]

Hi Team ,
I am cross compiling the LIRC for CE4100 target.
I am using following config options :
export CONFIG_SITE=./canmore.config

./configure $DEBUG_OPTIONS --prefix=/opt/canmore/local --host=i686-cm-linux
--with-kerneldir=/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35
--with-moduledir=/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/root/lib/modules
--without-x --with-driver=mceusb
When i try to compile i get the following error:

make -f scripts/Makefile.build obj=/root/lirc/lirc-0.8.7/drivers/lirc_dev
  gcc -Wp,-MD,/root/lirc/lirc-0.8.7/drivers/lirc_dev/.lirc_dev.o.d
 -nostdinc -isystem /usr/lib/gcc/i686-linux-gnu/4.6/include
-I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35/arch/x86/include
-Iinclude  -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration -Wno-format-security
-fno-delete-null-pointer-checks -O2 -m64 -mno-red-zone -mcmodel=kernel
-funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI_SIGNAL_FRAME=1
-DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare
-fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
-fno-stack-protector -fomit-frame-pointer -Wdeclaration-after-statement
-Wno-pointer-sign -fno-strict-overflow -fconserve-stack
-DIRCTL_DEV_MAJOR=61 -DEXPORT_SYMTAB -DHAVE_CONFIG_H -I. -I../..
-I/root/lirc/lirc-0.8.7/drivers/lirc_dev/.
-I/root/lirc/lirc-0.8.7/drivers/lirc_dev/.
-I/root/lirc/lirc-0.8.7/drivers/lirc_dev/../..
-I/root/lirc/lirc-0.8.7/drivers/lirc_dev/../..
-I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35//include/
-I/usr/local/Intel/IntelCE-21.4.11332.291760/project_build_i686/IntelCE/kernel-21.5.11393.297315/linux-2.6.35//drivers/media/video/
 -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(lirc_dev)"
 -D"KBUILD_MODNAME=KBUILD_STR(lirc_dev)"  -c -o
/root/lirc/lirc-0.8.7/drivers/lirc_dev/lirc_dev.o
/root/lirc/lirc-0.8.7/drivers/lirc_dev/lirc_dev.c
*cc1: fatal error: include/generated/autoconf.h: No such file or
directorythe same.*

*Please let me know how to fix *
*Thanks,*
*John*

Re: [PATCH] Driver for USB Infrared Toy

[Christ S. <aa...@gm...>]

I'm not saying it's not supported...  but I've been on this list and using
lirc for a decade, and never noticed it.
What I am saying is this:  if you stick to well tested and supported
hardware, you'll have an easier time with blasting.
On Nov 5, 2012 6:56 AM, "stuart" <st...@xn...> wrote:

>
> That's to bad.  I like the USB Infrared Toy as I have PIC knowledge and
> thought to share a HW project where the USB Infrared Toy was the center for
> all types of Mythtv features.  It strikes me that this 1 device could be
> used to receive & send IR signals as well as control any number of Liquid
> Crystal or Vacuum Florescent Displays.  I don't see the microsoft product
> doing that.
>
> So, to be clear ... Are you saying that the lirc command "irsend" is
> believed not to work with the USB Infrared Toy?
>
> -thanks
>
> On 11/04/2012 10:21 AM, Christ Schlacta wrote:
>
>> Usbuirt2 is a good option, as is mce based transceiver. It's usually
>> best to stick to well used and known-to-work hardware.
>>
>> On Nov 4, 2012 7:38 AM, "stuart" <st...@xn...
>> <mailto:st...@xn...>> wrote:
>>
>>     It's a year later....
>>
>>     Hi, I was rebuilding my mythtv box which has been using lirc and the
>> USB
>>     Infrared Toy from dagerousprototypes.com
>>     <http://dagerousprototypes.com**> to control mythtv very
>>     successfully for quite some time.
>>
>>     But this go around I wanted to also control my TV from the USB
>> Infrared
>>     Toy.  (For those who may not know, the USB Infrared Toy is a PIC
>>     (microchip.com <http://microchip.com>) based IR receiver and
>>     transmitter which uses the PIC's
>>     USB peripheral hardware to connect to your computer.)
>>
>>     To do this I have been chasing down what support there might already
>> be
>>     to help in the transmission of IR signals from the USB Infrared Toy to
>>     my Sony TV.  I have connected the dots to this (i.e. this particular
>>     thread I'm typing into now).  That is, to this lirc patch submission
>> by
>>     Peter Kooiman.
>>
>>     I've downloaded the Peter's patch and looked for the associated files
>> in
>>     the lirc GIT repository.  Specifically I looked for
>>     "daemons/hw_usbirtoy.c" but did not find it.
>>
>>     I looked here:
>>      >
>>     http://lirc.git.sourceforge.**net/git/gitweb.cgi?p=lirc/**
>> lirc;a=tree;f=daemons;h=**3a413ac0244dd6afa550aa17ff6a0f**
>> 5c2da27e57;hb=HEAD<http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=tree;f=daemons;h=3a413ac0244dd6afa550aa17ff6a0f5c2da27e57;hb=HEAD>
>>
>>     So, I assume the support to transmit IR signals using the USB Infrared
>>     Toy PIC based dongle from dagerousprototypes.com
>>     <http://dagerousprototypes.com**> does not exist for
>>     Linux based Mythtv users as it is not part of the lirc.org
>>     <http://lirc.org> effort?
>>
>>     If true, do any have an alternate suggestion?
>>
>>     -thanks
>>
>>
>>     On 09/02/2011 03:08 AM, Peter Kooiman wrote:
>>      > [As plain text this time, sorry!]
>>      > Hello,
>>      >
>>      >
>>      > Attached two patches that add support for the Dangerous
>>     Prototypes USB Remote Toy receiver/transmitter, for review and
>>     possible inclusion.
>>      > Patches are against git HEAD.
>>      >
>>      > Peter
>>      >
>>      >
>>      >
>>      >
>>     ------------------------------**------------------------------**
>> ------------------
>>      > Special Offer -- Download ArcSight Logger for FREE!
>>      > Finally, a world-class log management solution at an even better
>>      > price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>>      > download Logger. Secure your free ArcSight Logger TODAY!
>>      > http://p.sf.net/sfu/**arcsisghtdev2dev<http://p.sf.net/sfu/arcsisghtdev2dev>
>>      >
>>
>>
>>     ------------------------------**------------------------------**
>> ------------------
>>     LogMeIn Central: Instant, anywhere, Remote PC access and management.
>>     Stay in control, update software, and manage PCs from one command
>> center
>>     Diagnose problems and improve visibility into emerging IT issues
>>     Automate, monitor and manage. Do more in less time with Central
>>     http://p.sf.net/sfu/**logmein12331_d2d<http://p.sf.net/sfu/logmein12331_d2d>
>>
>>
>

Re: [PATCH] Driver for USB Infrared Toy

[stuart <st...@xn...>]

That's to bad.  I like the USB Infrared Toy as I have PIC knowledge and 
thought to share a HW project where the USB Infrared Toy was the center 
for all types of Mythtv features.  It strikes me that this 1 device 
could be used to receive & send IR signals as well as control any number 
of Liquid Crystal or Vacuum Florescent Displays.  I don't see the 
microsoft product doing that.

So, to be clear ... Are you saying that the lirc command "irsend" is 
believed not to work with the USB Infrared Toy?

-thanks

On 11/04/2012 10:21 AM, Christ Schlacta wrote:
> Usbuirt2 is a good option, as is mce based transceiver. It's usually
> best to stick to well used and known-to-work hardware.
>
> On Nov 4, 2012 7:38 AM, "stuart" <st...@xn...
> <mailto:st...@xn...>> wrote:
>
>     It's a year later....
>
>     Hi, I was rebuilding my mythtv box which has been using lirc and the USB
>     Infrared Toy from dagerousprototypes.com
>     <http://dagerousprototypes.com> to control mythtv very
>     successfully for quite some time.
>
>     But this go around I wanted to also control my TV from the USB Infrared
>     Toy.  (For those who may not know, the USB Infrared Toy is a PIC
>     (microchip.com <http://microchip.com>) based IR receiver and
>     transmitter which uses the PIC's
>     USB peripheral hardware to connect to your computer.)
>
>     To do this I have been chasing down what support there might already be
>     to help in the transmission of IR signals from the USB Infrared Toy to
>     my Sony TV.  I have connected the dots to this (i.e. this particular
>     thread I'm typing into now).  That is, to this lirc patch submission by
>     Peter Kooiman.
>
>     I've downloaded the Peter's patch and looked for the associated files in
>     the lirc GIT repository.  Specifically I looked for
>     "daemons/hw_usbirtoy.c" but did not find it.
>
>     I looked here:
>      >
>     http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=tree;f=daemons;h=3a413ac0244dd6afa550aa17ff6a0f5c2da27e57;hb=HEAD
>
>     So, I assume the support to transmit IR signals using the USB Infrared
>     Toy PIC based dongle from dagerousprototypes.com
>     <http://dagerousprototypes.com> does not exist for
>     Linux based Mythtv users as it is not part of the lirc.org
>     <http://lirc.org> effort?
>
>     If true, do any have an alternate suggestion?
>
>     -thanks
>
>
>     On 09/02/2011 03:08 AM, Peter Kooiman wrote:
>      > [As plain text this time, sorry!]
>      > Hello,
>      >
>      >
>      > Attached two patches that add support for the Dangerous
>     Prototypes USB Remote Toy receiver/transmitter, for review and
>     possible inclusion.
>      > Patches are against git HEAD.
>      >
>      > Peter
>      >
>      >
>      >
>      >
>     ------------------------------------------------------------------------------
>      > Special Offer -- Download ArcSight Logger for FREE!
>      > Finally, a world-class log management solution at an even better
>      > price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>      > download Logger. Secure your free ArcSight Logger TODAY!
>      > http://p.sf.net/sfu/arcsisghtdev2dev
>      >
>
>
>     ------------------------------------------------------------------------------
>     LogMeIn Central: Instant, anywhere, Remote PC access and management.
>     Stay in control, update software, and manage PCs from one command center
>     Diagnose problems and improve visibility into emerging IT issues
>     Automate, monitor and manage. Do more in less time with Central
>     http://p.sf.net/sfu/logmein12331_d2d
>

irsend - lirc 0.9.0 - RCMM

[John O'B. <jo...@te...>]

hi
I has the same issue with my remote that uses the RCMM protocol, and 
using lirc 0.9.0.
Would always get irsend:timeout error , even though it worked flawlessly 
in previous versions of lirc.
The solution for me was to modify the /gap /in my lircd.conf file.
Mine was about 100000, i kept reducing it down , I now have it at 18000 
and and my transmitter works flawlessly when blasting, with no 
irsend:timeout errors.
Hope this helps
John

Re: [PATCH] Driver for USB Infrared Toy

[Christ S. <aa...@gm...>]

Usbuirt2 is a good option, as is mce based transceiver. It's usually best
to stick to well used and known-to-work hardware.
On Nov 4, 2012 7:38 AM, "stuart" <st...@xn...> wrote:

> It's a year later....
>
> Hi, I was rebuilding my mythtv box which has been using lirc and the USB
> Infrared Toy from dagerousprototypes.com to control mythtv very
> successfully for quite some time.
>
> But this go around I wanted to also control my TV from the USB Infrared
> Toy.  (For those who may not know, the USB Infrared Toy is a PIC
> (microchip.com) based IR receiver and transmitter which uses the PIC's
> USB peripheral hardware to connect to your computer.)
>
> To do this I have been chasing down what support there might already be
> to help in the transmission of IR signals from the USB Infrared Toy to
> my Sony TV.  I have connected the dots to this (i.e. this particular
> thread I'm typing into now).  That is, to this lirc patch submission by
> Peter Kooiman.
>
> I've downloaded the Peter's patch and looked for the associated files in
> the lirc GIT repository.  Specifically I looked for
> "daemons/hw_usbirtoy.c" but did not find it.
>
> I looked here:
> >
> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=tree;f=daemons;h=3a413ac0244dd6afa550aa17ff6a0f5c2da27e57;hb=HEAD
>
> So, I assume the support to transmit IR signals using the USB Infrared
> Toy PIC based dongle from dagerousprototypes.com does not exist for
> Linux based Mythtv users as it is not part of the lirc.org effort?
>
> If true, do any have an alternate suggestion?
>
> -thanks
>
>
> On 09/02/2011 03:08 AM, Peter Kooiman wrote:
> > [As plain text this time, sorry!]
> > Hello,
> >
> >
> > Attached two patches that add support for the Dangerous Prototypes USB
> Remote Toy receiver/transmitter, for review and possible inclusion.
> > Patches are against git HEAD.
> >
> > Peter
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Special Offer -- Download ArcSight Logger for FREE!
> > Finally, a world-class log management solution at an even better
> > price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> > download Logger. Secure your free ArcSight Logger TODAY!
> > http://p.sf.net/sfu/arcsisghtdev2dev
> >
>
>
>
> ------------------------------------------------------------------------------
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
>

Re: [PATCH] Driver for USB Infrared Toy

[stuart <st...@xn...>]

It's a year later....

Hi, I was rebuilding my mythtv box which has been using lirc and the USB 
Infrared Toy from dagerousprototypes.com to control mythtv very 
successfully for quite some time.

But this go around I wanted to also control my TV from the USB Infrared 
Toy.  (For those who may not know, the USB Infrared Toy is a PIC 
(microchip.com) based IR receiver and transmitter which uses the PIC's 
USB peripheral hardware to connect to your computer.)

To do this I have been chasing down what support there might already be 
to help in the transmission of IR signals from the USB Infrared Toy to 
my Sony TV.  I have connected the dots to this (i.e. this particular 
thread I'm typing into now).  That is, to this lirc patch submission by 
Peter Kooiman.

I've downloaded the Peter's patch and looked for the associated files in 
the lirc GIT repository.  Specifically I looked for 
"daemons/hw_usbirtoy.c" but did not find it.

I looked here:
> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=tree;f=daemons;h=3a413ac0244dd6afa550aa17ff6a0f5c2da27e57;hb=HEAD

So, I assume the support to transmit IR signals using the USB Infrared 
Toy PIC based dongle from dagerousprototypes.com does not exist for 
Linux based Mythtv users as it is not part of the lirc.org effort?

If true, do any have an alternate suggestion?

-thanks


On 09/02/2011 03:08 AM, Peter Kooiman wrote:
> [As plain text this time, sorry!]
> Hello,
>
>
> Attached two patches that add support for the Dangerous Prototypes USB Remote Toy receiver/transmitter, for review and possible inclusion.
> Patches are against git HEAD.
>
> Peter
>
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
>