From: Bill Paxton <goawaypleaseus@ya...> - 2002-05-16 07:05:58
Yes, yes. That bare one, the 78k one in
.org/remotes/rc-5 and the 114k one in
.org/remotes/philips/RC-5 were my first attempts. No
Q: Is that .org/remotes/rc-5/RC-5 config really RC5?
Is it an older format issue? Can someone else verify?
Using a One-For-All Producer 8 remote and patching in
20+ known RC5 remote devices, that file doesn't detect
-any- of their button presses.
If this is the way inherited projects get updated then
I'm telling ya this file doesn't work for lirc_serial
sense=1 with 0.6.5 in any RC5 capacity. At all.
The .org/remotes/philips/RC-5 one detects every button
press from every remote - even a few (~10) codes that
aren't in the file but the remote generated. (reliable
and repeatable, I'll annotate an update).
Of course the bare protocol header one in
0.6.5/remotes/generic works perfectly fine - all
learned RC5 keys match the .org/philips/RC-5 exactly.
But this JBL remote can't be learned with either
header. As the original post - I know your file is RC5
protocol, but I have no idea what the remote is other
than the IR chip. JBL is less than helpful I actually
got a msg stating "The only thing I can tell you
technically about the remote is that it is an IR
remote" from custserv!!
Plus, it's broken.
I've been trying transmitting the power codes for all
RC5 devices and it will not turn the unit off - I
think it must be another protocol. It's time-consuming
Thanks though. (for everything!)
> Try "irrecord lirc-0.6.5/remotes/generic/RC-5.conf".
>> a Philips SAA3010 RC5 IR chip
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
Bill Paxton "goawaypleaseus@..." wrote:
> Plus, it's broken.
> I've been trying transmitting the power codes for all
> RC5 devices and it will not turn the unit off - I
> think it must be another protocol. It's time-consuming
> as hell.
SAA3010 uses RC-5. From the mode2 output I can actually see if it's really