From: Paul M. <pmi...@us...> - 2005-07-19 00:50:08
|
Hi Chris, I believe the aux keys are only emitted after another key is pressed. For this reason, we chose not to use them. There is an option to enable them in various different ways. -Paul On Monday 18 July 2005 07:59 am, Chris Ward wrote: > Hi, > > > > Saw a couple of list items about it but haven't really found the > resolution. I have the remote and see that the lirc_atiusb driver > (I'm using ver 1.49) see's the aux buttons as the 1st byte and it > goes: > > > > 00 = aux1 > > 01 = aux2 > > 02 = aux3 > > 03 = aux4 > > 04 = pc (aux 5) > > > > The driver debug output is: > > > > Jul 17 13:00:16 avcon kernel: lirc_atiusb[3]: data received 03 00 > 78 (ep=0x82 length=3) === something pressed when aux4 was > active (1st byte 03) > > Jul 17 13:00:16 avcon kernel: lirc_atiusb[3]: data received 02 01 > 3f (ep=0x82 length=3) === something pressed when aux3 was > active (1st byte 02) > > Jul 17 13:00:16 avcon kernel: lirc_atiusb[3]: data received 01 02 > 3f (ep=0x82 length=3) === something pressed when aux2 was > active (1st byte 01) > > > > I have lircd working and am using the lircd.conf that's stripped > down and only has the remote that starts like this which matches > the PN on my remote: > > > > begin remote > > name 5000024400 > > bits 16 > > eps 30 > > aeps 100 > > > > one 0 0 > > zero 0 0 > > pre_data_bits 8 > > pre_data 0x0 > > post_data_bits 16 > > post_data 0x0 > > gap 299851 > > toggle_bit 0 > > > > > > begin codes > > leftmouse 0x02A9 > > rightmouse 0x02AA > > a 0x0278 > > b 0x0279 > > power 0x020C > > > > but I'm looking to use the AUX buttons. How would I add the first > byte to the config. I assume I would have to basically quadruple > the config file adding 01 to everything , then 02 , 03 , 04 etc so > I could tell when "aux1-a or play or stop" or "aux2-a or play or > stop" were pressed.. > > > > Thanks, > > Chris. |