lirc-list

Re: how to make remote more reliable

[Cory C. <cc...@gm...>]

Still looking for help if anyone is out there.

On 04/21/2012 11:14 AM, Cory Coager wrote:
> I'm using a URC MX-980 remote connected to commandIR via cable.  I'm
> using version lirc 0.9.0.
>
> The remote is intermittently missing IR commands on key presses.  If I
> watch with irw I can see sometimes when I press a key nothing displays
> on irw.  If I hold the button, still nothing.  However, the next key
> press may work fine.  I'd say there is about a 20% error rate which is
> enough to be annoying.
>
> How do I tweak my setup to be more reliable?
>
> Here is the top part of the remote config:
>
> begin remote
>   name  mx980
>   bits           16
>   flags SPACE_ENC|CONST_LENGTH
>   eps            30
>   aeps          100
>   header       8977  4433
>   one           606  1636
>   zero          606   501
>   ptrail        606
>   repeat       8976  2190
>   pre_data_bits   16
>   pre_data       0xA10C
>   gap          108320
>   toggle_bit_mask 0x0
>

Re: PVR-350 receiver supported under Kernel 3.2?

[Paul C. <pa...@th...>]

It looks like I was being a bit pessimistic.

I'm happy to report that with debian unstable, kernel 3.2.15, using
lirc-0.9.0-0ubuntu (nice configuation screen to give me some hints :)) I
was able to get my PVR-350 receiver and homebrew transmitter both working.

I didn't have to mess with any rc tables (besides what I had done
already), although I did have to change the driver for the PVR-350 to
devinput and use the correct lircd.conf file for that.

Finally!  -P

> Is the PVR-350 receiver/remote supported under Kernel 3.2? If so, is Zilog
> the right module to use?
>
> Something tells me my StreamZap is about to come out of the box...

PVR-350 receiver supported under Kernel 3.2?

[Paul C. <pa...@th...>]

Is the PVR-350 receiver/remote supported under Kernel 3.2? If so, is Zilog
the right module to use?

Something tells me my StreamZap is about to come out of the box...

Thx, P

Re: convert RMDU file to lirc remote config file?

[Tom M. <tme...@gm...>]

Bengt Martensson wrote:
>Brian J. Murrell wrote:
>> The only thing I found was the gap between duplicate key sends was
>> not quite long enough to defeat the STBs de-bouncing when doing
>> something like:
>> # irsend SEND_ONCE xmpff-1 3 3
>>
>> For the duplicate key press situation I can do:
>> # irsend SEND_ONCE xmpff-1 3; sleep .5; irsend SEND_ONCE xmpff-1 3
>>
>> and it works as expected.

I wrote about the same problem with a Thompson DTA in these threads:
http://sourceforge.net/mailarchive/forum.php?thread_name=4F94A895.6090500%40gmail.com&forum_name=lirc-list
http://sourceforge.net/mailarchive/forum.php?thread_name=4F809A16.9050904%40gmail.com&forum_name=lirc-list

No one had any suggestions.


> The used protocol XMP-1...

Is that the same as XMP (flags XMP) as used by:
http://lirc.sourceforge.net/remotes/motorola/DTA100
?


> ...with final frame is unfortunately quite
> complicated, containing both a long intro sequence, and long repeat
> sequence, AND a long ending sequence. LIRC cannot (as I recall) do
> anything near this. Be happy that it "almost" works!

Interesting. Any pointers you can provide for more information on this?
I'd like to understand the problem better, confirm if it applies to my
situation, and see what can be done to fix it.

If LIRC doesn't fully implement XMP, or the variation in use, then would
using raw codes be a workaround?

Thanks,
 -Tom

Re: irsend with raw codes?

[StephenG <st...@ph...>]

Glad you got a working one.  I got mine all up and running at around 2am
this morning (WHY do I stay up that late!?)
I confess I'm relatively new to LIRC setup and didn't know what an RMDU 
is used, and whether it had worked for you.  Some days, I just hit
the brute force button and attack things at the lowest level (maybe I've 
done to much assembly language programming).  It did help me nail the
carrier frequency though.
Can you do me a favour and test mine to see if it works on your box too?
Richard wants to give me a shot with his remote so he's planning on 
mailing it to me.   It would be nice to know that what I did is 
universally applicable.


Brian J. Murrell wrote:
> 
> 
> Did you notice that somebody else provided a similar config based on the
> RMDU file that I had dug up and sent to the list?  It's working
> wonderfully for me also.
> 

-- 
View this message in context: http://old.nabble.com/irsend-with-raw-codes--tp33690522p33760469.html
Sent from the LIRC mailing list archive at Nabble.com.

Re: irsend with raw codes?

[Brian J. M. <br...@in...>]

On 12-04-27 12:01 AM, StephenG wrote:
> 
> Hi Brian.  I was in the same situation as you.  My cable co went digital
> and sent me a dc730 which castrated my mythtv box.

If you are talking about the cableco that serviced you when you are/were
at queensu.ca, then we are talking about one and the same cableco.
Queens is "just down the street" (relatively speaking) from me here.  :-)

>     http://www.physics.queensu.ca/~steve/DC730_lirc.conf

Ahhh.  Great.  Thanks!

Did you notice that somebody else provided a similar config based on the
RMDU file that I had dug up and sent to the list?  It's working
wonderfully for me also.

>  NOTE that I was only interested in sending the numbers so that my mythtv 
> box could change the channels so it only has keys 0-9.  If you need the
> other 
> keys, let me know and I'll finish the job.

Indeed.  Mythtv is my use-case also.

Thanks so much for responding though, I do appreciate it.

Cheers,
b.

Can not match received code with Sony RM-U305A

[<ke...@gm...>]

Hi,

I'm trying to received remote code from the sony remote control
RM-U305A.
I'm using the confuguration file rm-u305.
I'm really close to get them but there are still some mistakes.
On 12 bit code, 12 bit are catched but lircd terminates by:
lircd: timeout: 100000
lircd: <p1276
lircd: space expected
lircd: failed on bit 12
lircd: failed on code

I've compiled lirc-0.9.0 and I'm using a ftdi based receiver.

In the following, I put the used conf file, lircd debug log (-D3) when
irw is launched and a mode2 trace for this remote code. 
If you need more or other informations, ask them to me !


Thx in advance,
Dal.

Conf File
---------
begin remote

  name  RM-U305_func
  bits           12
  flags CONST_LENGTH
  eps            30
  aeps          200

  header       2392   593
  one          1202   575
  zero          609   575
  gap          24000
  min_repeat      0
  toggle_bit      0


      begin codes
          SLEEP                    0x0000000000000061
          AV_i/o                   0x0000000000000A90
          VIDEO                    0x0000000000000441
          DVD                      0x0000000000000BE1
          TV/SAT                   0x0000000000000561
          AUX                      0x0000000000000B81
          CD                       0x0000000000000A41
#          CD                       0x0000000000000EEE
          TUNER                    0x0000000000000841
          ON/OFF                   0x0000000000000A81
      end codes

end remote

Lirc Debug Log
--------------

lircd/lirc-0.9.0/daemons/lircd -n -H ftdi -L log.t -D3 lirc_remote/rm_u305_modif
...
...
lircd: trying "RM-U305_func" remote
lircd: <p1276
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c2203912
lircd: trying "RM-U305_func" remote
lircd: <s2203912
lircd: sync
lircd: +p162
lircd: failed on header
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <p162
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c173561
lircd: trying "RM-U305_func" remote
lircd: <s173561
lircd: sync
lircd: +p2425
lircd: header
lircd: +s540
lircd: +p1259
lircd: 1
lircd: +s543
lircd: +p657
lircd: <p657
lircd: 0
lircd: +s520
lircd: +p1263
lircd: 1
lircd: +s537
lircd: +p644
lircd: <p644
lircd: 0
lircd: +s533
lircd: +p654
lircd: <p654
lircd: 0
lircd: +s498
lircd: +p1253
lircd: 1
lircd: +s546
lircd: +p644
lircd: <p644
lircd: 0
lircd: +s664
lircd: +p641
lircd: <p641
lircd: 0
lircd: +s517
lircd: +p657
lircd: <p657
lircd: 0
lircd: +s533
lircd: +p644
lircd: <p644
lircd: 0
lircd: +s507
lircd: +p1266
lircd: 1
lircd: +s23489
lircd: <s23489
lircd: failed on bit 12
lircd: failed on code
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <s23489
lircd: sync
lircd: +p2421
lircd: header
lircd: +s546
lircd: +p1240
lircd: 1
lircd: +s550
lircd: +p660
lircd: <p660
lircd: 0
lircd: +s533
lircd: +p1230
lircd: 1
lircd: +s540
lircd: +p644
lircd: <p644
lircd: 0
lircd: +s517
lircd: +p651
lircd: <p651
lircd: 0
lircd: +s533
lircd: +p172
lircd: <p172
lircd: failed on bit 6
lircd: failed on code
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <p172
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c543
lircd: trying "RM-U305_func" remote
lircd: <s543
lircd: sync
lircd: +p644
lircd: failed on header
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <p644
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c598
lircd: trying "RM-U305_func" remote
lircd: <s598
lircd: sync
lircd: +p634
lircd: failed on header
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <p634
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c546
lircd: trying "RM-U305_func" remote
lircd: <s546
lircd: sync
lircd: +p641
lircd: failed on header
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <p641
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c540
lircd: trying "RM-U305_func" remote
lircd: <s540
lircd: sync
lircd: +p647
lircd: failed on header
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <p647
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c520
lircd: trying "RM-U305_func" remote
lircd: <s520
lircd: sync
lircd: +p651
lircd: failed on header
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <p651
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c543
lircd: trying "RM-U305_func" remote
lircd: <s543
lircd: sync
lircd: +p1204
lircd: failed on header
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: trying "RM-U305_func" remote
lircd: <p1204
lircd: space expected
lircd: failed on sync
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes
lircd: c24029
lircd: trying "RM-U305_func" remote
lircd: <s24029
lircd: sync
lircd: +p2444
lircd: header
lircd: +s524
lircd: +p1266
lircd: 1
lircd: +s546
lircd: +p654
lircd: <p654
lircd: 0
lircd: +s533
lircd: +p1347
lircd: 1
lircd: +s530
lircd: +p641
lircd: <p641
lircd: 0
lircd: +s537
lircd: +p1227
lircd: 1
lircd: +s553
lircd: +p651
lircd: <p651
lircd: 0
lircd: +s598
lircd: +p644
lircd: <p644
lircd: 0
lircd: +s517
lircd: +p647
lircd: <p647
lircd: 0
lircd: +s514
lircd: +p638
lircd: <p638
lircd: 0
lircd: +s537
lircd: +p631
lircd: <p631
lircd: 0
lircd: +s537
lircd: +p1276
lircd: 1
lircd: timeout: 100000
lircd: <p1276
lircd: space expected
lircd: failed on bit 12
lircd: failed on code
lircd: failed "RM-U305_func" remote
lircd: decoding failed for all remotes


Mode2 Trace
-----------
mode2 -H ftdi
mode2: Initializing FTDI: 
mode2: opened FTDI device '' OK
pulse 3
space 2813697
pulse 2447
space 520
pulse 198
space 533
pulse 651
space 530
pulse 1256
space 514
pulse 651
space 537
pulse 638
space 546
pulse 1243
space 556
pulse 611
space 569
pulse 651
space 527
pulse 683
space 537
pulse 628
space 540
pulse 1328
space 24547
pulse 1412
space 569
pulse 1240
space 537
pulse 657
space 520
pulse 1263
space 524
pulse 641
space 517
pulse 644
space 543
pulse 1256
space 540
pulse 644
space 602
pulse 647
space 566
pulse 651
space 520
pulse 670
space 533
pulse 1256
space 23795
pulse 2460
space 530
pulse 1236
space 540
pulse 638
space 527
pulse 1263
space 527
pulse 647
space 524
pulse 628
space 533
pulse 1386
space 608
pulse 647
space 524
pulse 657
space 527
pulse 644
space 530
pulse 644
space 540
pulse 1243

Re: irsend with raw codes?

[StephenG <st...@ph...>]

Hi Brian.  I was in the same situation as you.  My cable co went digital
and sent me a dc730 which castrated my mythtv box.  I didn't have any
luck with "irrecord -f" either.  So, I took the remote into work and scoped
it up with an photodiode to get all the timings and carrier frequency.  Long 
story short, I now have a working lirc.conf file that I can use with irsend.   
I won't guarantee it'll work with your box but you're welcome to give it a
try.  

    http://www.physics.queensu.ca/~steve/DC730_lirc.conf

 NOTE that I was only interested in sending the numbers so that my mythtv 
box could change the channels so it only has keys 0-9.  If you need the
other 
keys, let me know and I'll finish the job.

 -steve


Brian J. Murrell wrote:
> 
> Hi,
> 
> I have a new set-top box I need to use irsend to control.  For the
> record, it's a HUAWEI DC730.  It comes with it's own remote.
> 
> --SNIP----
> 
> Any ideas?
> 
> Cheers,
> b.
> 
> 

-- 
View this message in context: http://old.nabble.com/irsend-with-raw-codes--tp33690522p33756843.html
Sent from the LIRC mailing list archive at Nabble.com.

Re: convert RMDU file to lirc remote config file?

[Bengt M. <bu...@be...>]

On 04/24/12 14:56, Brian J. Murrell wrote:

> 
>> I am almost finished (just documentation and web site setup remains) of
>> a tool that will do this semi-automatically (and much more). Try the
>> included "fragment": The first 10 commands should correspond to 0 to 9,
>> Command  d062f013s016 and d062f014s016 should be channel up and down
>> respectively, while d062f015s016  should be power, Does it work?
> 
> Woot!  It works great!

Nice to hear that. I enclose a file containing the commands 0-100, which
should be more than you need, according to the rmdu. Use the "hex"
attribute in the rmdu-file to associate them to command names.

>  The only thing I found was the gap between
> duplicate key sends was not quite long enough to defeat the STBs
> de-bouncing when doing something like:
> 
> # irsend SEND_ONCE xmpff-1 3 3
> 
> However
> 
> # irsend SEND_ONCE xmpff-1 3 2
> 
> works as expected.  For the duplicate key press situation I can do:
> 
> # irsend SEND_ONCE xmpff-1 3; sleep .5; irsend SEND_ONCE xmpff-1 3
> 
> and it works as expected.

The used protocol XMP-1 with final frame is unfortunately quite
complicated, containing both a long intro sequence, and long repeat
sequence, AND a long ending sequence. LIRC cannot (as I recall) do
anything near this. Be happy that it "almost" works!

> 
> Much, much thanks for this.  I truly appreciate it.

Glad to be of help. The program will be available next week, estimated.

Greetz,

Bengt

Vala code example

[Brian D. <br...@gm...>]

Does anyone have an example of integrating lirc with my vala application? I
have my remote working on my Fedora 16 box. IRW returns the proper codes
with the IRW program. I would like to be able to read the codes in my Vala
application without resorting to using irexec and/or dbus to get them.

thanks

Brian

-- 
Duff

unsubscribe

[<Gav...@st...>]

unsubscribe


Regards,

Gavin Whitehead


Technical Consultant (Messaging)
Steria (www.steria.com\uk)
Switchboard:0870 600 4466
Direct: 01442 884883
Mobile:07966 824883


Think before you print - Steria is committed to supporting a sustainable 
world



Think before you print - Steria is committed to supporting a sustainable 
world and is Certified Carbon Neutral for Flight and Fleet Travel

This email originates from Steria*. It, and any attachments, may contain confidential information and may be subject to copyright or other intellectual property rights. It is only for the use of the addressee(s). You may not copy, forward, disclose, save or otherwise use it in any way if you are not the addressee(s) or responsible for delivery.
If you receive this email by mistake, please advise the sender and cancel it immediately.
Steria may monitor the content of emails within its network to ensure compliance with its policies and procedures.
Any email is susceptible to alteration and its integrity cannot be assured. Steria shall not be liable if the message is altered, modified, falsified, or edited.
_____________________________________________________
* Steria Limited, number 4077975;
Steria Recruitment Limited, number 1437998.
Registered in England and Wales; registered office Three Cherry Trees Lane, Hemel Hempstead, Hertfordshire HP2 7AH

Re: convert RMDU file to lirc remote config file?

[Brian J. M. <br...@in...>]

On 12-04-23 05:16 PM, Bengt Martensson wrote:
> 
> Hi Brian,

Hi Bengt,

> a rmdu-file is for the use of the program RemoteMaster,

Indeed.

> It contains the name of an IR
> protocol used, here "XMP-1 with final frame",

Which I'm guessing is a protocol that LIRC doesn't know about, yes?

> I am almost finished (just documentation and web site setup remains) of
> a tool that will do this semi-automatically (and much more). Try the
> included "fragment": The first 10 commands should correspond to 0 to 9,
> Command  d062f013s016 and d062f014s016 should be channel up and down
> respectively, while d062f015s016  should be power, Does it work?

Woot!  It works great!  The only thing I found was the gap between
duplicate key sends was not quite long enough to defeat the STBs
de-bouncing when doing something like:

# irsend SEND_ONCE xmpff-1 3 3

However

# irsend SEND_ONCE xmpff-1 3 2

works as expected.  For the duplicate key press situation I can do:

# irsend SEND_ONCE xmpff-1 3; sleep .5; irsend SEND_ONCE xmpff-1 3

and it works as expected.

Much, much thanks for this.  I truly appreciate it.

Cheers,
b.

Re: convert RMDU file to lirc remote config file?

[Bengt M. <bu...@be...>]

On 04/23/12 08:01, Brian J. Murrell wrote:
> I have a device (Huawei DC730) which has a remote which LIRC can't seem
> to learn from (see the "irsend with raw codes?" thread for more
> information).  Using raw codes doesn't seem to be at all effective.
> 
> I have managed to find a configuration file for this device/remote in
> "RMDU" format?  Is there any way to convert that to an LIRC remote
> control configuration file?  The RMDU file can be found attached to this
> message if you are interested in seeing it.

Hi Brian,

a rmdu-file is for the use of the program RemoteMaster, see
http://www.hifi-remote.com/forums/. It contains the name of an IR
protocol used, here "XMP-1 with final frame", together with the
parameters "device" (62) and "subdevice" (16). These are shared by all
the command in the rmdzuu-file. In addition, every command has its own
command number, that is the "hex" parameter in the rmdu-file.

I am almost finished (just documentation and web site setup remains) of
a tool that will do this semi-automatically (and much more). Try the
included "fragment": The first 10 commands should correspond to 0 to 9,
Command  d062f013s016 and d062f014s016 should be channel up and down
respectively, while d062f015s016  should be power, Does it work?

Greetz,

Bengt

convert RMDU file to lirc remote config file?

[Brian J. M. <br...@in...>]

I have a device (Huawei DC730) which has a remote which LIRC can't seem
to learn from (see the "irsend with raw codes?" thread for more
information).  Using raw codes doesn't seem to be at all effective.

I have managed to find a configuration file for this device/remote in
"RMDU" format?  Is there any way to convert that to an LIRC remote
control configuration file?  The RMDU file can be found attached to this
message if you are interested in seeing it.

Cheers and much thanks,
b.

Re: irsend with raw codes?

[Richard F. <si...@bi...>]

Hi Brian,

I was in the same position as you, I ended up with two options, hack the hardware or change the STB.

Hacking the hardware would have been easy, spend $30 on a replacement remote and some time wiring and programming it up. However  in that scenario I was still stuck with the crappy provider STB which a max of S-Video out. Ended up replacing the STB which had component out, a remote I could record and HD video :D

HD-PVRs are a godsend.

-rF

On 23/04/2012, at 3:02 PM, Brian J. Murrell wrote:

> On 12-04-16 07:54 PM, Richard Ferrara wrote:
>> Hi Brian,
> 
> Hi Richard,
> 
>> 1. Minimise IR interference (try a dark room and make sure the transmitter is as close as possible to the receiver),
> 
> Recorded from the remote to raw in a very dark room.  Had the
> transmitter LED taped right to the front of the receiver and while the
> receiver's light blinks when I use irsend, irw is still not seeing a thing.
> 
>> 2. Do some research and check what protocol that remote is using, I had a hell of a time attempting to record my Austar Flinders Satellite STB... It uses the RC-MM protocol. You can tell irrecord to use a specific protocol by specifying from the examples.
> 
> Still haven't been able to determine this.  I don't think this device
> (manufacturer) is too popular/prevalent.  I've tried contacting Huawei
> directly but (to no surprise) they failed to respond.
> 
>> 3. The pronto remotes have an awesome database and you may be able to get the pronto hex codes and convert to lirc configuration using the python script.
> 
> Is this http://www.remotecentral.com/cgi-bin/codes/ you mean?  There was
> nothing at all there for Huawei.  I even did a site search for Huawei
> and it returned a few hits but nothing about my device.
> 
> Please?  Anyone?  Any ideas?
> 
> I mean other than hacking the hardware.  I don't own it, the cableco does.
> 
> b.
> 
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2

Re: irsend with raw codes?

[Brian J. M. <br...@in...>]

On 12-04-16 07:54 PM, Richard Ferrara wrote:
> Hi Brian,

Hi Richard,

> 1. Minimise IR interference (try a dark room and make sure the transmitter is as close as possible to the receiver),

Recorded from the remote to raw in a very dark room.  Had the
transmitter LED taped right to the front of the receiver and while the
receiver's light blinks when I use irsend, irw is still not seeing a thing.

> 2. Do some research and check what protocol that remote is using, I had a hell of a time attempting to record my Austar Flinders Satellite STB... It uses the RC-MM protocol. You can tell irrecord to use a specific protocol by specifying from the examples.

Still haven't been able to determine this.  I don't think this device
(manufacturer) is too popular/prevalent.  I've tried contacting Huawei
directly but (to no surprise) they failed to respond.

> 3. The pronto remotes have an awesome database and you may be able to get the pronto hex codes and convert to lirc configuration using the python script.

Is this http://www.remotecentral.com/cgi-bin/codes/ you mean?  There was
nothing at all there for Huawei.  I even did a site search for Huawei
and it returned a few hits but nothing about my device.

Please?  Anyone?  Any ideas?

I mean other than hacking the hardware.  I don't own it, the cableco does.

b.

irsend should atomically set the transmission channel and send IR codes

[Tom M. <tme...@gm...>]

Consider a scenario of a channel change script, lets say Perl, that
executes:

irsend set_transmitters $channel
irsend SEND_ONCE $remote $keys

and at the top of the hour the application wants to change channels on
two tuners. It may launch one instance of the channel change script,
wait for it to terminate, then launch a 2nd instance. It also may spawn
children for each and run them in parallel. In which case you might end
up with the following sequence of irsend commands, where the first
channel change child is PID=1000 and the 2nd is PID=2000:

irsend set_transmitters 1 (ran from PID=1000)
irsend set_transmitters 2 (ran from PID=2000)
irsend SEND_ONCE MotorolaDTA100-PaceDC50X KEY_2 KEY_5 KEY_ENTER (ran
from PID=1000)
irsend SEND_ONCE MotorolaDTA100-PaceDC50X KEY_3 KEY_2 KEY_ENTER (ran
from PID=2000)

The result of this is that both sets of IR sequences get sent to emitter
#2.

Most channel change scripts I've seen make no attempt to mitigate this
problem, but I have seen at least one that uses a lock file as a
semaphore to prevent overlapping sequences.

This raises the question: why was irsend designed such that
set_transmitters is a separate sub-command, mutually exclusive with
SEND_ONCE?

It would make more sense had the syntax been something like:

irsend --set_transmitters=$emitter SEND_ONCE $remote $keys


 -Tom

lirc.conf parameter to control space between codes

[Tom M. <tme...@gm...>]

When irsend is executed with parameters like:

% irsend SEND_ONCE remote KEY_1 KEY_2 KEY_3

what parameter in lirc.conf specifically controls the pause between the
transmission of KEY_1 and KEY_2?

'gap' seems like the obvious answer, but experimentally it doesn't seem
to do the trick. Some information I've seen suggests that 'gap' might
control the spacing between the initial code and the repeat code when a
code is being sent repeatedly, which is not necessarily the same thing
as the pause between different codes.

 -Tom

lirc / ir-keytable / in-kernel lirc confusion

[Michael S. <tcw...@gm...>]

Hi folks,

[  204.360019] usb 4-2: new low-speed USB device number 2 using uhci_hcd
[  204.540036] usb 4-2: New USB device found, idVendor=0471, idProduct=20cc
[  204.540041] usb 4-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  204.540044] usb 4-2: Product: MCE USB IR Receiver- Spinel plus
[  204.540047] usb 4-2: Manufacturer: PHILIPS
[  204.603640] input: PHILIPS MCE USB IR Receiver- Spinel plus as 
/devices/pci0000:00/0000:00:1d.3/usb4/4-2/4-2:1.0/input/input13
[  204.603895] generic-usb 0003:0471:20CC.0009: input,hiddev0,hidraw4: 
USB HID v1.00 Keyboard [PHILIPS MCE USB IR Receiver- Spinel plus] on 
usb-0000:00:1d.3-2/input0
mschmitt@adrastea:~$ ir-keytable -t
/sys/class/rc/: No such file or directory
mschmitt@adrastea:~$

basically I just want this device to be used with ir-keytable. Other 
remote receivers "just work". Regardless if built-in a machine or 
plugged in via USB, in generell they get recognized, a rc-keytable is 
assigned and ir-keytable works with them automatically (I know 
ir-keytable -t only works with root privs, but I already checked that, 
the paste was done afterwards and a missing /sys/class/rc is the issue 
not privs). So what do I need to do to get ir-keytable working?

Apart from that, if one would be so kind and point me in the right 
direction for a document explaining the "Linux and RCs today" topic a 
bit. I used to use plain old lirc but the whole situation has changed as 
it seems. In genereal I know enough to get things working again IF 
ir-keytable works and /sys/class/rc IS there, but as it is missing with 
this receiver and as said I know very little about the whole "new" 
approach with in-kernel lirc / rc-stuff I have no idea where to poke / 
look. Is it a kernel issue? At least I tried a fairly recent 3.3 kernel 
and a stable 3.2 kernel (I am on Debian sid and the 3.3 kernel I got 
from "experimental)

In addition I am quite confused when a RC is recognized as a keyboard 
and keypresses are interpreted as a normal dev-input-device. How do I 
prevent that from happening?

regards
Michael

mceusb on Debian Wheezy

[Josu L. <jos...@gm...>]

Hello all, I have a problem with the mceusb driver on Debian, I just
upgrade from Squeeze (2.6.32) to Wheezy (3.2) and I now there is not
the "lirc-modules-source" package.

On Debian I used to install this way:

apt-get install lirc-modules-source
dpkg-reconfigure lirc-modules-source
m-a prepare
m-a a-i lirc
modprobe lirc_mceusb2

The problem is that now I don't know how to install it.

I notice that there are some button working without any lirc configuration:

# cat /sys/class/rc/rc0/protocols
[rc-5] [nec] [rc-6] [jvc] [sony] [mce_kbd] [lirc]

This is my USB receiver:

# lsusb
Bus 004 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver

Which is the correct way to install it?

Thanks and best regards.

-- 
Josu Lazkano

how to make remote more reliable

[Cory C. <cc...@gm...>]

I'm using a URC MX-980 remote connected to commandIR via cable.  I'm
using version lirc 0.9.0.

The remote is intermittently missing IR commands on key presses.  If I
watch with irw I can see sometimes when I press a key nothing displays
on irw.  If I hold the button, still nothing.  However, the next key
press may work fine.  I'd say there is about a 20% error rate which is
enough to be annoying.

How do I tweak my setup to be more reliable?

Here is the top part of the remote config:

begin remote
  name  mx980
  bits           16
  flags SPACE_ENC|CONST_LENGTH
  eps            30
  aeps          100
  header       8977  4433
  one           606  1636
  zero          606   501
  ptrail        606
  repeat       8976  2190
  pre_data_bits   16
  pre_data       0xA10C
  gap          108320
  toggle_bit_mask 0x0

Re: irsend with raw codes?

[Richard F. <si...@bi...>]

Similar to this.

http://forums.oztivo.net/showthread.php?1977-Success-with-IR-translator-for-Austar-Flinders

On 18/04/2012, at 9:00 AM, Brian J. Murrell wrote:

> On 12-04-17 06:57 PM, Richard Ferrara wrote:
>> If you don't care about the remote you could wire up a hardware solution.
> 
> I'm not sure I'm following.
> 
>> Not as elegant but would be the path of least resistance.
> 
> Perhaps which is why I am showing interest.  :-)
> 
> b.
> 
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second 
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev

Re: irsend with raw codes?

[Richard F. <ri...@fe...>]

Similar to this..

http://forums.oztivo.net/showthread.php?1977-Success-with-IR-translator-for-Austar-Flinders

On 18/04/2012, at 9:00 AM, Brian J. Murrell wrote:

> On 12-04-17 06:57 PM, Richard Ferrara wrote:
>> If you don't care about the remote you could wire up a hardware solution.
> 
> I'm not sure I'm following.
> 
>> Not as elegant but would be the path of least resistance.
> 
> Perhaps which is why I am showing interest.  :-)
> 
> b.
> 
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second 
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev

Re: irsend with raw codes?

[Brian J. M. <br...@in...>]

On 12-04-17 06:57 PM, Richard Ferrara wrote:
> If you don't care about the remote you could wire up a hardware solution.

I'm not sure I'm following.

> Not as elegant but would be the path of least resistance.

Perhaps which is why I am showing interest.  :-)

b.

Re: irsend with raw codes?

[Richard F. <si...@bi...>]

If you don't care about the remote you could wire up a hardware solution. Not as elegant but would be the path of least resistance.

-rF

On 17/04/2012, at 11:45 PM, Brian J. Murrell wrote:

> As a followup, I took this remote apart and other than a couple of
> capacitors, this remote is being entirely driven from a chip with the
> following markings:
> 
> 54973
> 64133
> 1014 02
> 
> I couldn't manage to find anything out about it though.  :-(
> 
> b.
> 
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second 
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev