I have a Philips RCAU013 remote with different modes controlled by a switch on the side; there are two positions labelled "TV" and one labelled "DVD". The buttons are split into buttons which transmit in TV mode and buttons which transmit in DVD mode. I've successfully recorded both types using a serial dongle with lirc_serial and LIRC 0.9.0 on Trisquel. Apparently TV mode transmits RC-5 and DVD mode transmits RC-6.
I've tried the same lircd.conf I created on the serial dongle (attached) with my irtoy2. It detects the RC-5 buttons fine but unfortunately, the irtoy2 doesn't seem to be able to detect the RC-6 button presses properly. Some are detected but then there is a massive, five-or-so second delay between button-push detection. It is unusable.
I thought it might be something specific to the irtoy2 so I tried irrecord from LIRC 0.9.3a compiled from source. Unfortunately, it segfaulted at the end of the second batch of dots at the start of the recording process, so I tried the latest git master. With this, I get the following error from irrecord:
It is very important that you press many different buttons randomly and hold them down for approximately one second. Each button should generate at least one dot but never more than ten dots of output. Don't stop pressing buttons until two lines of dots (2x80) have been generated. Press RETURN now to start recording. .......................................................................Cannot find any gap, using an arbitrary 50 ms one. If you have a regular remote for e. g., a TV or such this is probably a point where you hit control-C. However, technical hardware like air condition gear often works without any gap. If you think it's reasonable that your remote lacks gap you can proceed. Press RETURN to continue.
I'm wondering whether this is a problem with LIRC, or with the irtoy2? The firmware for the irtoy2 seems a bit flakey and it's odd that it will work OK with the serial dongle.
Does your IrToy work with IrScrutinizer? Can you generate a configuration file with it instead of irrecord?
Main problem with the 'toy is that it takes almost two seconds to deliver the final silence, by design of the firmware.
Your configuration file looks fine.
Apparently not:
Huh? To me, it looks like a large number of successfull captures, before one that went wrong. Why don't you just press "OK" and capture the last one again? Then export as Lirc.
hm... I have been away too long. Are you still interested in resolving this issue (I certainly am, but not without your help...)
Ping? Any news here?
Closing bug for lack of input. Thanks for reporting, though.