Menu
▾
▴
lirc-list
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(14) |
Jun
(29) |
Jul
(51) |
Aug
(40) |
Sep
(35) |
Oct
(58) |
Nov
(64) |
Dec
(70) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(111) |
Feb
(75) |
Mar
(85) |
Apr
(62) |
May
(56) |
Jun
(65) |
Jul
(67) |
Aug
(73) |
Sep
(46) |
Oct
(64) |
Nov
(55) |
Dec
(76) |
| 2002 |
Jan
(119) |
Feb
(74) |
Mar
(101) |
Apr
(128) |
May
(124) |
Jun
(138) |
Jul
(114) |
Aug
(63) |
Sep
(54) |
Oct
(135) |
Nov
(92) |
Dec
(127) |
| 2003 |
Jan
(129) |
Feb
(164) |
Mar
(129) |
Apr
(131) |
May
(181) |
Jun
(136) |
Jul
(118) |
Aug
(220) |
Sep
(116) |
Oct
(177) |
Nov
(206) |
Dec
(114) |
| 2004 |
Jan
(175) |
Feb
(222) |
Mar
(245) |
Apr
(209) |
May
(112) |
Jun
(104) |
Jul
(77) |
Aug
(115) |
Sep
(175) |
Oct
(141) |
Nov
(154) |
Dec
(190) |
| 2005 |
Jan
(198) |
Feb
(171) |
Mar
(164) |
Apr
(113) |
May
(104) |
Jun
(151) |
Jul
(107) |
Aug
(190) |
Sep
(142) |
Oct
(116) |
Nov
(113) |
Dec
(111) |
| 2006 |
Jan
(147) |
Feb
(103) |
Mar
(102) |
Apr
(75) |
May
(110) |
Jun
(82) |
Jul
(119) |
Aug
(77) |
Sep
(103) |
Oct
(188) |
Nov
(132) |
Dec
(155) |
| 2007 |
Jan
(169) |
Feb
(110) |
Mar
(113) |
Apr
(162) |
May
(107) |
Jun
(116) |
Jul
(159) |
Aug
(135) |
Sep
(135) |
Oct
(105) |
Nov
(96) |
Dec
(100) |
| 2008 |
Jan
(122) |
Feb
(93) |
Mar
(57) |
Apr
(80) |
May
(119) |
Jun
(85) |
Jul
(59) |
Aug
(73) |
Sep
(250) |
Oct
(146) |
Nov
(121) |
Dec
(72) |
| 2009 |
Jan
(193) |
Feb
(96) |
Mar
(102) |
Apr
(66) |
May
(99) |
Jun
(130) |
Jul
(206) |
Aug
(308) |
Sep
(117) |
Oct
(99) |
Nov
(170) |
Dec
(232) |
| 2010 |
Jan
(104) |
Feb
(127) |
Mar
(86) |
Apr
(111) |
May
(66) |
Jun
(44) |
Jul
(253) |
Aug
(120) |
Sep
(178) |
Oct
(220) |
Nov
(153) |
Dec
(157) |
| 2011 |
Jan
(80) |
Feb
(85) |
Mar
(129) |
Apr
(232) |
May
(236) |
Jun
(73) |
Jul
(53) |
Aug
(38) |
Sep
(23) |
Oct
(32) |
Nov
(25) |
Dec
(24) |
| 2012 |
Jan
(23) |
Feb
(43) |
Mar
(29) |
Apr
(50) |
May
(25) |
Jun
(15) |
Jul
(26) |
Aug
(26) |
Sep
(4) |
Oct
(10) |
Nov
(17) |
Dec
(18) |
| 2013 |
Jan
(12) |
Feb
(17) |
Mar
(15) |
Apr
(22) |
May
(29) |
Jun
(16) |
Jul
(15) |
Aug
(9) |
Sep
(45) |
Oct
(18) |
Nov
(21) |
Dec
(11) |
| 2014 |
Jan
(35) |
Feb
(34) |
Mar
(13) |
Apr
(14) |
May
(86) |
Jun
(23) |
Jul
(6) |
Aug
(18) |
Sep
(16) |
Oct
(36) |
Nov
(98) |
Dec
(62) |
| 2015 |
Jan
(27) |
Feb
(14) |
Mar
(5) |
Apr
(49) |
May
(27) |
Jun
(9) |
Jul
(11) |
Aug
(20) |
Sep
(26) |
Oct
(71) |
Nov
(2) |
Dec
(7) |
| 2016 |
Jan
(42) |
Feb
(3) |
Mar
(15) |
Apr
(34) |
May
(25) |
Jun
(39) |
Jul
(20) |
Aug
(85) |
Sep
(14) |
Oct
(82) |
Nov
(10) |
Dec
(34) |
| 2017 |
Jan
(29) |
Feb
(88) |
Mar
(78) |
Apr
(4) |
May
(7) |
Jun
(30) |
Jul
(4) |
Aug
(47) |
Sep
(14) |
Oct
(47) |
Nov
(5) |
Dec
(3) |
| 2018 |
Jan
(18) |
Feb
(13) |
Mar
(6) |
Apr
(8) |
May
(11) |
Jun
(1) |
Jul
(11) |
Aug
(1) |
Sep
(4) |
Oct
|
Nov
|
Dec
(23) |
| 2019 |
Jan
(5) |
Feb
(15) |
Mar
(11) |
Apr
(4) |
May
(15) |
Jun
(12) |
Jul
(4) |
Aug
(5) |
Sep
(14) |
Oct
(3) |
Nov
(10) |
Dec
|
| 2020 |
Jan
|
Feb
(5) |
Mar
(23) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2021 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
(8) |
May
|
Jun
|
Jul
(4) |
Aug
(5) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
(2) |
Dec
(13) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2024 |
Jan
|
Feb
|
Mar
(4) |
Apr
(3) |
May
(2) |
Jun
(4) |
Jul
(3) |
Aug
|
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
(2) |
Jun
(5) |
Jul
|
Aug
|
Sep
(12) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
|
2
|
3
|
4
|
5
|
6
(1) |
|
7
(3) |
8
(1) |
9
(2) |
10
|
11
|
12
(1) |
13
(2) |
|
14
(2) |
15
(2) |
16
(4) |
17
(1) |
18
|
19
|
20
|
|
21
|
22
|
23
|
24
|
25
|
26
(1) |
27
|
|
28
|
29
(2) |
30
|
|
|
|
|
|
From: Matrix200 <mat...@gm...> - 2013-04-29 22:53:22
|
<html><head><title>Re: Odd air condition codes not working with irrecord / manual configuration</title> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> </head> <body> <span style=" font-family:'Arial'; font-size: 10pt;">Hi Omer,<br> <br> I tried to make the same remote work with some limited success.<br> With commandir it works about 30% of the time for some of the keys.<br> If you want I can send you some codes I had generated.<br> <br> <br> Monday, April 29, 2013, 11:39:31 PM, you wrote:<br> <br> </span><table> <tr> <td width=2 bgcolor= #0000ff><br> </td> <td width=1><br> </td> </tr> </table> <span style=" font-family:'arial'; font-size: 10pt;">Hey,<br> <br> I've been trying for some while now to get lirc working with my air condition unit (remote control RC-4(HL)) without success.<br> The remote does not repeat the codes, so every key press only sends one burst of information.<br> (Another TV remote I have works perfectly with irrecord)<br> <br> Here is what I tried:<br> <b>irrecord</b> (with and without --force), does not find gap, and does not register most of my clicks.<br> I assume this is because the key does not repeat.<br> <br> mode2 works with this output:<br> mode2: uirt2_raw: checksum error<br> mode2: uirt2_raw: UIRT version 0905 ok<br> 1526500<br> <br> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:3250">3250</a><span style=" font-family:'arial'; font-size: 10pt;"> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:3800">3800</a><span style=" font-family:'arial'; font-size: 10pt;"> 1950 800 1050 1750<br> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:2000">2000</a><span style=" font-family:'arial'; font-size: 10pt;"> 800 1050 800 1000 900<br> 950 900 1000 800 1050 850<br> 1050 1800 1950 900 1050 1800<br> 1950 900 950 900 1000 850<br> 1000 900 1000 800 1050 850<br> 1000 900 1000 850 1050 850<br> 1050 800 1050 850 1050 800<br> 1050 850 1000 900 1000 800<br> 1000 900 950 1850 1900 900<br> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:2900">2900</a><span style=" font-family:'arial'; font-size: 10pt;"> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:3800">3800</a><span style=" font-family:'arial'; font-size: 10pt;"> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:2000">2000</a><span style=" font-family:'arial'; font-size: 10pt;"> 850 1000 1850<br> 1950 800 1050 800 1050 800<br> 1050 800 1000 900 1050 800<br> 1050 1750 </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:2000">2000</a><span style=" font-family:'arial'; font-size: 10pt;"> 800 1050 1800<br> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:2000">2000</a><span style=" font-family:'arial'; font-size: 10pt;"> 800 1050 850 1000 900<br> 1050 800 1050 800 1000 900<br> 1000 800 1050 850 1050 800<br> 1050 800 1100 800 1050 800<br> 1000 900 1050 800 1000 900<br> 950 900 1000 1750 </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:2000">2000</a><span style=" font-family:'arial'; font-size: 10pt;"> 850<br> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:2950">2950</a><span style=" font-family:'arial'; font-size: 10pt;"> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:3850">3850</a><span style=" font-family:'arial'; font-size: 10pt;"> 1950 850 1050 1750<br> 1950 900 1050 850 1000 900<br> 950 900 1000 850 1000 900<br> 950 1850 1950 850 1050 1800<br> 1950 900 1050 800 1050 850<br> 1050 800 1050 850 1050 800<br> 1050 800 1050 800 1050 800<br> 1050 800 1050 800 1050 850<br> 1050 850 1050 850 1000 900<br> 950 900 1000 1800 1950 900<br> </span><a style=" font-family:'arial'; font-size: 10pt;" href="tel:3950">3950</a><br> <br> <span style=" font-family:'arial'; font-size: 10pt;">trying to use this output in the config file:<br> <br> <i>begin remote<br> name test<br> flags RAW_CODES<br> eps 30<br> aeps 100<br> <br> ptrail 0<br> repeat 0 0<br> begin raw_codes<br> <br> name power<br> [...] CODES as shown above [...]<br> end raw_codes<br> end remote<br> <br> </i>This does not work properly.<br> irw identifies the key "power", but I cannot send the key with irsend.<br> Here is the output:<br> <br> lircd: registering local client<br> lircd: accepted new client on /var/run/lirc/lircd<br> lircd: writing command 23<br> lircd: 23 dd <br> lircd: wrote 2<br> lircd: cmd res 3:<br> lircd: 09 05 01 <br> lircd: <br> lircd: uirt2_raw: checksum error<br> lircd: uirt2: detection of uirt2 failed<br> lircd: uirt2: trying to detect newer uirt firmware<br> lircd: writing command 23<br> lircd: 23 dd <br> lircd: wrote 2<br> lircd: cmd res 8:<br> lircd: 09 05 01 01 1a 03 04 cf <br> lircd: <br> lircd: uirt2_raw: UIRT version 0905 ok<br> lircd: writing command 21<br> lircd: 21 df <br> lircd: wrote 2<br> lircd: cmd res 1:<br> lircd: 21 <br> lircd: <br> lircd: tty_setdtr: 1->0<br> lircd: received command: "send_start ct power"<br> lircd: clearing transmit buffer<br> lircd: transmit buffer ready<br> lircd: Trying REMSTRUC1 transmission<br> lircd: uirt2_raw: UIRT version 0905<br> lircd: hw_uirt2_raw.c:477<br> lircd: table[0] = 38<br> <br> lircd: hw_uirt2_raw.c:496 - signal 2000, tunit 52, bit: 0<br> lircd: table[0] = 16<br> <br> [...]<br> <br> lircd: hw_uirt2_raw.c:496 - signal 1950, tunit 52, bit: 0<br> lircd: expect 17, table[0] = 16<br> <br> lircd: hw_uirt2_raw.c:496 - signal 900, tunit 52, bit: 0<br> lircd: Couldn't find 57<br> <br> lircd: hw_uirt2_raw.c:496 - signal 3000, tunit 52, bit: -1<br> lircd: hw_uirt2_raw.c:508<br> lircd: uirt2_send: remote not supported<br> lircd: error processing command: send_start ct power<br> lircd: transmission failed<br> lircd: removed client<br> lircd: tty_setdtr: 0->1<br> <br> <br> I added some debugging info (shown in lines with __FILE__:__LINE__)<br> <br> Can anyone help with this? If code needs to be changed I can do it with a little guidance.<br> <br> Regards,<br> Omer.<br> <br> <br> <br> <br> <br> <br> <br> <span style=" font-size: 8pt; color: #c0c0c0;"><i>-- <br> Best regards,<br> Matrix200 </i></span></span><a style=" font-family:'arial';" href="mailto:mat...@gm...">mailto:mat...@gm...</a></body></html> |
|
From: Omer E. <om...@gm...> - 2013-04-29 20:39:57
|
Hey,
I've been trying for some while now to get lirc working with my air
condition unit (remote control RC-4(HL)) without success.
The remote does not repeat the codes, so every key press only sends one
burst of information.
(Another TV remote I have works perfectly with irrecord)
Here is what I tried:
*irrecord* (with and without --force), does not find gap, and does not
register most of my clicks.
I assume this is because the key does not repeat.
mode2 works with this output:
mode2: uirt2_raw: checksum error
mode2: uirt2_raw: UIRT version 0905 ok
1526500
3250 3800 1950 800 1050 1750
2000 800 1050 800 1000 900
950 900 1000 800 1050 850
1050 1800 1950 900 1050 1800
1950 900 950 900 1000 850
1000 900 1000 800 1050 850
1000 900 1000 850 1050 850
1050 800 1050 850 1050 800
1050 850 1000 900 1000 800
1000 900 950 1850 1900 900
2900 3800 2000 850 1000 1850
1950 800 1050 800 1050 800
1050 800 1000 900 1050 800
1050 1750 2000 800 1050 1800
2000 800 1050 850 1000 900
1050 800 1050 800 1000 900
1000 800 1050 850 1050 800
1050 800 1100 800 1050 800
1000 900 1050 800 1000 900
950 900 1000 1750 2000 850
2950 3850 1950 850 1050 1750
1950 900 1050 850 1000 900
950 900 1000 850 1000 900
950 1850 1950 850 1050 1800
1950 900 1050 800 1050 850
1050 800 1050 850 1050 800
1050 800 1050 800 1050 800
1050 800 1050 800 1050 850
1050 850 1050 850 1000 900
950 900 1000 1800 1950 900
3950
trying to use this output in the config file:
*begin remote*
* name test*
* flags RAW_CODES*
* eps 30*
* aeps 100*
*
*
* ptrail 0*
* repeat 0 0*
* begin raw_codes*
*
*
* name power*
* [...] CODES as shown above [...]*
* end raw_codes*
*end remote*
*
*
This does not work properly.
irw identifies the key "power", but I cannot send the key with irsend.
Here is the output:
lircd: registering local client
lircd: accepted new client on /var/run/lirc/lircd
lircd: writing command 23
lircd: 23 dd
lircd: wrote 2
lircd: cmd res 3:
lircd: 09 05 01
lircd:
lircd: uirt2_raw: checksum error
lircd: uirt2: detection of uirt2 failed
lircd: uirt2: trying to detect newer uirt firmware
lircd: writing command 23
lircd: 23 dd
lircd: wrote 2
lircd: cmd res 8:
lircd: 09 05 01 01 1a 03 04 cf
lircd:
lircd: uirt2_raw: UIRT version 0905 ok
lircd: writing command 21
lircd: 21 df
lircd: wrote 2
lircd: cmd res 1:
lircd: 21
lircd:
lircd: tty_setdtr: 1->0
lircd: received command: "send_start ct power"
lircd: clearing transmit buffer
lircd: transmit buffer ready
lircd: Trying REMSTRUC1 transmission
lircd: uirt2_raw: UIRT version 0905
lircd: hw_uirt2_raw.c:477
lircd: table[0] = 38
lircd: hw_uirt2_raw.c:496 - signal 2000, tunit 52, bit: 0
lircd: table[0] = 16
[...]
lircd: hw_uirt2_raw.c:496 - signal 1950, tunit 52, bit: 0
lircd: expect 17, table[0] = 16
lircd: hw_uirt2_raw.c:496 - signal 900, tunit 52, bit: 0
lircd: Couldn't find 57
lircd: hw_uirt2_raw.c:496 - signal 3000, tunit 52, bit: -1
lircd: hw_uirt2_raw.c:508
lircd: uirt2_send: remote not supported
lircd: error processing command: send_start ct power
lircd: transmission failed
lircd: removed client
lircd: tty_setdtr: 0->1
I added some debugging info (shown in lines with __FILE__:__LINE__)
Can anyone help with this? If code needs to be changed I can do it with a
little guidance.
Regards,
Omer.
*
*
|
|
From: praet0ri4n <fil...@gm...> - 2013-04-26 14:27:17
|
Hi all, I'm struggling with an old TV capture card Asus MyCinema Analog P7131, which has a IR receiver plug. I'm not using it's tv functions, just the IR receiver to controll my custom HTPC. Generally, when running /irrecord -d /dev/lirc0 test.conf/ I make it always to the first part, where I am asked to press as many buttons as possible to fill the two lines with dots. I tried with all remotes I have and it just works with mostly RC-6 and Pulse-Space protocols discovered. Remotes are of different origin, one for MAGIO set-top-box, one for a TVAnywhere Plus TV-card and one cheapo chinese remote <http://wiki.xbmc.org/index.php?title=Remote_control_reviews#IRF_Media_W-01RN> . After recognizing the protocol it asks for the first key assignment. I start with KEY_MUTE, then I press the appropriate button on the remote and get /"Something went wrong"/ According to the recommendations I start irrecord with force raw /irrecord *-f* -d /dev/lirc0 test.conf/ just to come to the same point. This time the error is slighly different, I assume it comes from another part of the lirc code. /"Sorry, something went wrong"/ I read somewhere, that with -f it is impossible to get this error message.. *The only remote, that leads to a proper assignment is a RC-5 remote originally shipped with USB tuner Pinnacle PCTV Nano Stick 73e. Protocol and key assignments are registered flawlessly.* //sys/class/rc/rc0/protocols/ contains RC-5, RC-6, SONY, SANYO, JVC, LIRC, MCEUSB protocols. mode2 returns all kind of pulses and spaces with all remotes, it is responding to IR signals well. I tried with /ir-keytable -t -s rc0/ and I am getting output from almost all remotes there. I also managed to get it to work by assigning those codes to keystrokes. But I would prefer LIRC instead.. Does it have to do with the Asus MyCInema card? Could it be somehow restricted? Shall I use any special driver when running irrecord? I used only default and devinput. devinput did not work at all. Are there any kernel modules needed for this to work? lirc_dev, lirc_i2c, etc? Pls let me know, I am ready to paste logs and outputs here, just need to know which were relevant. I didn't want to spam all at once. Thanks in advance! -- View this message in context: http://lirc.10951.n7.nabble.com/Asus-MyCinema-Analog-P7131-irrecord-fails-to-learn-another-remotes-tp9838.html Sent from the LIRC mailing list archive at Nabble.com. |
|
From: Bengt M. <bu...@be...> - 2013-04-16 20:58:28
|
On 04/16/13 20:07, XXXXXXXXXXXXXXXX wrote: >> On 04/09/13 13:16, XXXXXXXXXXXXXXXX wrote: >> I'm trying to run multiple >> LIRC instances (one for each device) in a >>> systemd service. ... >> >> Two processes are trying to bind to the same port. >> Change one "8765" to something else (8766?) or just leave out one of the >> --listen arguments. >> >> > > > Thanks for your message. > > If I understand this correctly. 8765 is the default listening port and > connection port. So --listen=8765 always defaults to --listen. I tried > both --listen and --listen=8765 but it still didn't work > No, you did not understand correctly. Read again, carefully. Or simply put, start the first instance with --listen=8765 and the second with --listen=8766 Greetz, Bengt |
|
From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - 2013-04-16 19:11:31
|
>> Is there some issue with "EnvironmentFile=..." in systemd service file? >> >> The "EnvionmentFile=/etc/conf.d/lircd.conf" contains: >> >> LIRC_DEVICE = "/dev/lirc0" >> LIRC_DRIVER = "devinput" >> LIRC_CONFIGFILE = /etc/lirc/lircd.conf >> > > Try the Environment file *without* spaces on either side of the '=' > signs. Your Env file is not actually making the variables. > > > [root@tor5 uls]# LIRC_DEVICE = "/dev/lirc0" > bash: LIRC_DEVICE: command not found > > [root@tor5 uls]# LIRC_DEVICE="/dev/lirc0" > > [root@tor5 uls]# echo $LIRC_DEVICE > /dev/lirc0 > > > Geoff > > Hi Geoff Thanks but actually there are no white-spaces in the Env-file. I retyped the above with spaces on either side of '=' but actually in my real file there are no such spaces. If I look up status: # systemctl status lircd.service I get: >> lircd: invalid argument count |
|
From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - 2013-04-16 18:15:24
|
Is there some issue with "EnvironmentFile=..." in systemd service file? I'm trying to use this type of service file: [Unit] Description=LIRC Daemon After=network.target [Service] Type=forking EnvironmentFile=/etc/conf.d/lircd.conf PIDFile=/run/lirc/lircd.pid ExecStartPre=/bin/mkdir -p /run/lirc ExecStartPre=/bin/rm -f /dev/lircd /run/lirc/lircd ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd ExecStart=/usr/sbin/lircd -d $LIRC_DEVICE -H $LIRC_DRIVER -P /run/lirc/lircd.pid $LIRC_CONFIGFILE ExecStopPost=/bin/rm -fR /dev/lircd /run/lirc [Install] WantedBy=multi-user.target But this is what I have to do to make it work: I have to pass the arguments explicitly to /usr/sbin/lircd. ... [Service] Type=forking EnvironmentFile=/etc/conf.d/lircd.conf PIDFile=/run/lirc/lircd.pid ExecStartPre=/bin/mkdir -p /run/lirc ExecStartPre=/bin/rm -f /dev/lircd /run/lirc/lircd ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd ExecStart=/usr/sbin/lircd -d "/dev/lirc0" -H "devinput" -P /run/lirc/lircd.pid /etc/lirc/lircd.conf ExecStopPost=/bin/rm -fR /dev/lircd /run/lirc ... The "EnvionmentFile=/etc/conf.d/lircd.conf" contains: LIRC_DEVICE = "/dev/lirc0" LIRC_DRIVER = "devinput" LIRC_CONFIGFILE = /etc/lirc/lircd.conf |
|
From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - 2013-04-16 18:07:45
|
> On 04/09/13 13:16, XXXXXXXXXXXXXXXX wrote: > I'm trying to run multiple > LIRC instances (one for each device) in a >> systemd service. >> >> This is the error I'm getting: >> >> lircd: could not assign address to socket >> lircd: Permission denied >> > .... >> >> This is what my service file looks like: >> >> [Unit] >> Description=LIRC Daemon >> After=network.target >> >> [Service] >> Type=oneshot >> EnvironmentFile=/etc/sysconfig/lirc >> ExecStartPre=/bin/mkdir -p /run/lirc >> ExecStartPre=/bin/rm -f /dev/lircd /dev/lircd1 >> ExecStartPre=/bin/rm -f /run/lirc/lircd /run/lirc/lircd1 >> ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd >> ExecStartPre=/bin/ln -s /run/lirc/lircd1 /dev/lircd1 >> ExecStart=/usr/sbin/lircd --device=/dev/input/event12 >> --output=/run/lirc/lircd1 --pidfile=/run/lirc/lircd1.pid >> --driver=devinput --listen=8765 /etc/lirc/lircd.conf >> ExecStart=/usr/sbin/lircd --device=/dev/input/event10 >> --output=/run/lirc/lircd --pidfile=/run/lirc/lircd.pid --driver=devinput >> --connect=localhost:8765 /etc/lirc/lircd.conf > > Two processes are trying to bind to the same port. > Change one "8765" to something else (8766?) or just leave out one of the > --listen arguments. > > Thanks for your message. If I understand this correctly. 8765 is the default listening port and connection port. So --listen=8765 always defaults to --listen. I tried both --listen and --listen=8765 but it still didn't work http://www.lirc.org/html/configure.html |
|
From: stuart <st...@xn...> - 2013-04-15 18:43:21
|
Just a guess, but are not most computer's IR ports actually IRDA ports? That is, they are meant to connect over distances of feet to printers and what not. And the formats are not even close. On the other hand, I have heard people turning their old Palm Pilots into IR (ASK) transmitters using software (as the IRDA ports do not support the ASK signal natively). But the range was bad. I always thought it funny since once you are close enough to use the IRDA transmitter you could just reach out and change the TV station with your hand. On 04/13/2013 10:03 PM, Jim Van Wie wrote: > Hi, 1st post here. I am wanting to control my Echostar(2700) receiver > with my computer(IBM600e). This computer has a built in IR. Will this > software LIRC lirc-0.9.0.tar.bz2 > <http://sourceforge.net/projects/lirc/files/LIRC/0.9.0/lirc-0.9.0.tar.bz2/download>, > 838 kB work with this computer with its built in IR? I just what the > computer to change the channel at a given time. > > Thanks Jim > KJ4BNH > > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > |
|
From: Daniel S. <dan...@gm...> - 2013-04-15 16:23:58
|
Dear LIRC-community, i finally found a solution for my problem! I posted my solution at: https://forum.openwrt.org/viewtopic.php?pid=198081#p198081 One may wants to change the sourcecode of LIRC, as it could save time for people having the same problems i had. First, the lirc/configure check of installed programs and libraries is not significant for cross-compiling. So i guess, there should be a separate configure-file for cross compiling. Second, a new dependency should be added. Instead of libusb, the dependency for all libusb-driver should be libusb-1.0 and libusb-compat. Cheers, Daniel > > Dear LIRC-Community, > > i want to use lirc on openwrt, but since a half a year or so, i do have > serious problems while compiling it. > > I opened a thread here: > https://forum.openwrt.org/viewtopic.php?pid=198193#p198193 and i would > be glad if you could help me. I also tried to email the developer of the > atilibusb-driver, but it seems that his email, which is given at the > header of his sourcecode is not valid anymore. > > For me it seems that it is not working since the libusb version switched > from 0.1 to 1.0. > I guess (but actually have no idea if its true) that lirc cannot find > the file, because it is now provided by libusb-compat and not libusb. > > Many thanks in advance, > > Daniel. |
|
From: Jim V. W. <kj...@gm...> - 2013-04-14 03:03:54
|
Hi, 1st post here. I am wanting to control my Echostar(2700) receiver with my computer(IBM600e). This computer has a built in IR. Will this software LIRC lirc-0.9.0.tar.bz2<http://sourceforge.net/projects/lirc/files/LIRC/0.9.0/lirc-0.9.0.tar.bz2/download>, 838 kB work with this computer with its built in IR? I just what the computer to change the channel at a given time. Thanks Jim KJ4BNH |
|
From: Rainer G. <ya...@rg...> - 2013-04-13 16:50:13
|
Hello, I developed a new hardware IR receiver and added it to Lirc. (Description is currently in German only) http://www.htpc-news.de/y-r-d-entwicklerforum-95/y-r-d-2-usb-status-16502/ Is it possible to add it directly to the Lirc repository ? Currently my Lirc source/patch is located @ https://www.assembla.com/code/yard2srvd/git/nodes/master/lirc Thanks for help, Rainer -- Mit freundlichen Grüßen Rainer Geigenberger mailto:ya...@rg... |
|
From: <oth...@gm...> - 2013-04-13 11:14:55
|
Dear LIRC-Community, i want to use lirc on openwrt, but since a half a year or so, i do have serious problems while compiling it. I opened a thread here: https://forum.openwrt.org/viewtopic.php?pid=198193#p198193 and i would be glad if you could help me. I also tried to email the developer of the atilibusb-driver, but it seems that his email, which is given at the header of his sourcecode is not valid anymore. For me it seems that it is not working since the libusb version switched from 0.1 to 1.0. I guess (but actually have no idea if its true) that lirc cannot find the file, because it is now provided by libusb-compat and not libusb. Many thanks in advance, Daniel. |
|
From: <oth...@gm...> - 2013-04-12 20:51:09
|
Dear LIRC-Community, i want to use lirc on openwrt, but since a half a year or so, i do have serious problems while compiling it. I opened a thread here: https://forum.openwrt.org/viewtopic.php?pid=198193#p198193 and i would be glad if you could help me. I also tried to email the developer of the atilibusb-driver, but it seems that his email, which is given at the header of his sourcecode is not valid anymore. For me it seems that it is not working since the libusb version switched from 0.1 to 1.0. I guess (but actually have no idea if its true) that lirc cannot find the file, because it is now provided by libusb-compat and not libusb. Many thanks in advance, Daniel. |
|
From: Bengt M. <no...@be...> - 2013-04-09 20:10:31
|
On 04/09/13 13:16, XXXXXXXXXXXXXXXX wrote:> I'm trying to run multiple LIRC instances (one for each device) in a > systemd service. > > This is the error I'm getting: > > lircd: could not assign address to socket > lircd: Permission denied > .... > > This is what my service file looks like: > > [Unit] > Description=LIRC Daemon > After=network.target > > [Service] > Type=oneshot > EnvironmentFile=/etc/sysconfig/lirc > ExecStartPre=/bin/mkdir -p /run/lirc > ExecStartPre=/bin/rm -f /dev/lircd /dev/lircd1 > ExecStartPre=/bin/rm -f /run/lirc/lircd /run/lirc/lircd1 > ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd > ExecStartPre=/bin/ln -s /run/lirc/lircd1 /dev/lircd1 > ExecStart=/usr/sbin/lircd --device=/dev/input/event12 > --output=/run/lirc/lircd1 --pidfile=/run/lirc/lircd1.pid > --driver=devinput --listen=8765 /etc/lirc/lircd.conf > ExecStart=/usr/sbin/lircd --device=/dev/input/event10 > --output=/run/lirc/lircd --pidfile=/run/lirc/lircd.pid --driver=devinput > --connect=localhost:8765 /etc/lirc/lircd.conf Two processes are trying to bind to the same port. Change one "8765" to something else (8766?) or just leave out one of the --listen arguments. |
|
From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - 2013-04-09 11:16:56
|
I'm trying to run multiple LIRC instances (one for each device) in a
systemd service.
This is the error I'm getting:
lircd: could not assign address to socket
lircd: Permission denied
lircd.service - LIRC Daemon
Loaded: loaded (/etc/systemd/system/lircd.service; enabled)
Active: failed (Result: exit-code) since Tue 2013-04-09 11:58:16
BST; 16s ago
Process: 27249 ExecStart=/usr/sbin/lircd
--device=/dev/input/event12 --output=/run/lirc/lircd1
--pidfile=/run/lirc/lircd1.pid --driver=devinput --listen=8765
/etc/lirc/lircd.conf (code=exited, status=1/FAILURE)
Process: 27246 ExecStartPre=/bin/ln -s /run/lirc/lircd1
/dev/lircd1 (code=exited, status=0/SUCCESS)
Process: 27242 ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd
(code=exited, status=0/SUCCESS)
Process: 27239 ExecStartPre=/bin/rm -f /run/lirc/lircd
/run/lirc/lircd1 (code=exited, status=0/SUCCESS)
Process: 27235 ExecStartPre=/bin/rm -f /dev/lircd /dev/lircd1
(code=exited, status=0/SUCCESS)
Process: 27231 ExecStartPre=/bin/mkdir -p /run/lirc (code=exited,
status=0/SUCCESS)
This is what my service file looks like:
[Unit]
Description=LIRC Daemon
After=network.target
[Service]
Type=oneshot
EnvironmentFile=/etc/sysconfig/lirc
ExecStartPre=/bin/mkdir -p /run/lirc
ExecStartPre=/bin/rm -f /dev/lircd /dev/lircd1
ExecStartPre=/bin/rm -f /run/lirc/lircd /run/lirc/lircd1
ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd
ExecStartPre=/bin/ln -s /run/lirc/lircd1 /dev/lircd1
ExecStart=/usr/sbin/lircd --device=/dev/input/event12
--output=/run/lirc/lircd1 --pidfile=/run/lirc/lircd1.pid
--driver=devinput --listen=8765 /etc/lirc/lircd.conf
ExecStart=/usr/sbin/lircd --device=/dev/input/event10
--output=/run/lirc/lircd --pidfile=/run/lirc/lircd.pid --driver=devinput
--connect=localhost:8765 /etc/lirc/lircd.conf
ExecStopPost=/bin/rm -f /dev/lircd /dev/lircd1
ExecStopPost=/bin/rm -fR /run/lirc
[Install]
WantedBy=multi-user.target
Either one of these two lircd commands run fine in a sudo terminal.
|
|
From: Steve Z. <qwa...@qw...> - 2013-04-08 01:38:34
|
Hey Ben, I am going to try this later tonight when I get home. This really looks like it is it. Yea I am using a Mororola DC50X STB. This really sounds like it since the Serial version works and USB is't able to communicate... though... the light activates. I attached my lircd.conf that I am using. This looks GREAT! from steveZ On Sun, Apr 07, 2013 at 01:05:13PM -0400, Benjamin Kraus wrote: > What brand STB are you using? What configuration file are you using? I > was having trouble getting a FTDI USB IR-Blaster (purchased from > irblaster.info) working with my Motorola cable box, and I discovered a > bug in 'daemons/hw_ftdi.c' that was keeping it from working properly. > > I just sent a message to the list detailing the bug, so I won't repeat > it here, but if you aren't subscribed to the list, let me know and I'll > send it to you directly. > > - Ben > > On Fri, Apr 5, 2013 at 3:34 PM, Steve Zawadzski <qwa...@qw...> > wrote: > > > > Hey Guys, > > > > I bought a USB IRBLASTER from irblaster.info > > <http://irblaster.info>. It uses the > > FT232RL chip. I was abe to get ir working with the ftdi > > driver accessing it with > > lircd --driver=nameofblaster --output=/dev/lircd /etc/lircd.conf > > > > with the above and using irsend I was able to see the blaster > > flash. So I am getting information through LIRC and out through > > the actual blaster. The output in the LIRCD is > > > > hwftdi_send() carrier=38000Hz f_sample=524288Hz > > > > I see the flash... but the channel does not change on the STB. > > > > I also have a serial blaster that uses lirc_serial to work. It > > works fine and I am using the same lircd.conf file for both. > > > > Are there any parameters such as baud rate or anything else that > > I can use to make this work? The output parameter is set to 2 > > by default. Is that the correct one? > > > > I saw there was a different note that mentioned the use of the > > mplay2 driver. I tried that one but LIRCD locked up and there > > was no flashing on the IRBLASTER. > > > > It would be great to be able to nail this down since I very few > > of my systems actually have serial ports now a days. > > > > Any help would be greatly appreciated as this is pretty cool > > software and I would love to get the USB versions running! > > > > from > > steveZ > > -- > Benjamin Kraus > be...@be... |
|
From: Benjamin K. <be...@be...> - 2013-04-07 17:30:37
|
What brand STB are you using? What configuration file are you using? I was having trouble getting a FTDI USB IR-Blaster (purchased from irblaster.info) working with my Motorola cable box, and I discovered a bug in 'daemons/hw_ftdi.c' that was keeping it from working properly. I just sent a message to the list detailing the bug, so I won't repeat it here, but if you aren't subscribed to the list, let me know and I'll send it to you directly. - Ben On Fri, Apr 5, 2013 at 3:34 PM, Steve Zawadzski <qwa...@qw...> wrote: > > Hey Guys, > > I bought a USB IRBLASTER from irblaster.info > <http://irblaster.info>. It uses the > FT232RL chip. I was abe to get ir working with the ftdi > driver accessing it with > lircd --driver=nameofblaster --output=/dev/lircd /etc/lircd.conf > > with the above and using irsend I was able to see the blaster > flash. So I am getting information through LIRC and out through > the actual blaster. The output in the LIRCD is > > hwftdi_send() carrier=38000Hz f_sample=524288Hz > > I see the flash... but the channel does not change on the STB. > > I also have a serial blaster that uses lirc_serial to work. It > works fine and I am using the same lircd.conf file for both. > > Are there any parameters such as baud rate or anything else that > I can use to make this work? The output parameter is set to 2 > by default. Is that the correct one? > > I saw there was a different note that mentioned the use of the > mplay2 driver. I tried that one but LIRCD locked up and there > was no flashing on the IRBLASTER. > > It would be great to be able to nail this down since I very few > of my systems actually have serial ports now a days. > > Any help would be greatly appreciated as this is pretty cool > software and I would love to get the USB versions running! > > from > steveZ -- Benjamin Kraus be...@be... |
|
From: Benjamin K. <be...@kr...> - 2013-04-07 16:35:35
|
I believe I have found a bug in 'daemons/hw_ftdi.c'. Line 440 should read: pulsewidth = f_sample * ((__u64) (pulse & PULSE_MASK)) / 1000000ul; Instead of what it currently reads: pulsewidth = f_sample * ((__u32) (pulse & PULSE_MASK)) / 1000000ul; I've attached a patch file with this change. I discovered this bug while using this configuration file: http://lirc.sourceforge.net/remotes/motorola/DCT2000 (included in the Ubuntu distribution of LIRC as: /usr/share/lirc/extras/transmitters/motorola/dctxxxx.conf) In that file, the header is specified as: header 9036 4424 The relevant pieces of code in 'daemons/hw_ftdi.c' are: static int tx_baud_rate = 65536; /* Default transmit baud rate */ __u32 f_sample = tx_baud_rate * 8; /* Default sampling rate 524288 Hz */ int pulsewidth = f_sample * ((__u32) (pulse & PULSE_MASK)) / 1000000ul; The largest pulse from the configuration file has a duration of 9036us. pulse = 9036; Given that pulse: 9036 * 524288 = 4737466368 However, 2^32 = 4294967296 Difference = 442499072 The result (verified using xmode2) was that the first header pulse was lasting ~844us instead of 9036us. Changing '__u32' to '__u64' resolved the issue. This was tested on a machine running the 64bit version of Ubuntu 12.10. This bug impacts the Motorola set-top-boxes, which from my experience are the majority of the set-top-boxes distributed by cable providers in my area (Boston, MA). I recently switched from Comcast to RCN as my cable provider, and both use Motorola cable boxes which use this same configuration file. This bug prevents the home-brew FTDI based transmitters (using Albert's design from http://www.huitsing.nl/irftdi/) from communicating with these set-top-boxes. - Ben -- Benjamin Kraus be...@kr... |
|
From: Jeff S. <jef...@gm...> - 2013-04-07 16:14:42
|
I have had similar problems with my iguana usb ir transceiver on an older tv. I had to use a usb repeater on that tv or hold the device really close. Maybe its just not strong enough? Not all IR LED's have the same frequency range, a repeater could fix this problem as well. Kind of a stupid solution but it had worked for me in the past. On Fri, Apr 5, 2013 at 3:34 PM, Steve Zawadzski <qwa...@qw...>wrote: > > > Hey Guys, > > I bought a USB IRBLASTER from irblaster.info. It uses the > FT232RL chip. I was abe to get ir working with the ftdi > driver accessing it with > lircd --driver=nameofblaster --output=/dev/lircd /etc/lircd.conf > > with the above and using irsend I was able to see the blaster > flash. So I am getting information through LIRC and out through > the actual blaster. The output in the LIRCD is > > hwftdi_send() carrier=38000Hz f_sample=524288Hz > > I see the flash... but the channel does not change on the STB. > > I also have a serial blaster that uses lirc_serial to work. It > works fine and I am using the same lircd.conf file for both. > > Are there any parameters such as baud rate or anything else that > I can use to make this work? The output parameter is set to 2 > by default. Is that the correct one? > > I saw there was a different note that mentioned the use of the > mplay2 driver. I tried that one but LIRCD locked up and there > was no flashing on the IRBLASTER. > > It would be great to be able to nail this down since I very few > of my systems actually have serial ports now a days. > > Any help would be greatly appreciated as this is pretty cool > software and I would love to get the USB versions running! > > from > steveZ > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > |
|
From: Steve Z. <qwa...@qw...> - 2013-04-06 04:54:25
|
Hey Guys, I bought a USB IRBLASTER from irblaster.info. It uses the FT232RL chip. I was abe to get ir working with the ftdi driver accessing it with lircd --driver=nameofblaster --output=/dev/lircd /etc/lircd.conf with the above and using irsend I was able to see the blaster flash. So I am getting information through LIRC and out through the actual blaster. The output in the LIRCD is hwftdi_send() carrier=38000Hz f_sample=524288Hz I see the flash... but the channel does not change on the STB. I also have a serial blaster that uses lirc_serial to work. It works fine and I am using the same lircd.conf file for both. Are there any parameters such as baud rate or anything else that I can use to make this work? The output parameter is set to 2 by default. Is that the correct one? I saw there was a different note that mentioned the use of the mplay2 driver. I tried that one but LIRCD locked up and there was no flashing on the IRBLASTER. It would be great to be able to nail this down since I very few of my systems actually have serial ports now a days. Any help would be greatly appreciated as this is pretty cool software and I would love to get the USB versions running! from steveZ |
2 messages has been excluded from this view by a project administrator.
