From: Bogdan G. <bo...@bl...> - 2002-08-26 15:20:02
|
Hi, I want to use lirc to send/receive messages from the Zaurus PDA to my Lego robot (RCX brick). So far I was able to learn some codes (motor A/B/C forward/backward, beep) using irrecord -f and to reproduce them using omni-remote. The lego robot understands the codes and it's pretty cool :) Now I want to create a real lirc.conf file, without using the --force option but I have a problem. Here is the output of the recording session: ------------------------------------------------ Press RETURN now to start recording. ............................................................................ .... Found const length: 215942 Please keep on pressing buttons like described above. ............................................................................ .... RC-6 remote control found. 2No header data. No repeat code found. Signals are biphase encoded. Signal length is 59 Checking for toggle bit. Please press an arbitrary button repeatedly as fast as possible (don't hold it down!). irrecord: no data for 10 secs, aborting No toggle bit found. But I know for sure that RC6 has a toggle bit! ------------------------------------------------ irrecord was searching the toggle bit for more than 4-5 minutes so I gave up. I am not familiar with RC-6 protocol but here is the protocol used to communicate with the RCX (from http://www.crynwr.com/lego-robotics/) ------------------------------------------------ The IR protocol associated with sending a "message" to the RCX is pretty simple. Bit encoding is 2400 bps, NRZ, 1 start, 8 data, odd parity, 1 stop bit. A '0' is coded as a 417us pulse of 38kHz IR, a '1' bit is 417us of nothing. At the packet level, all packets look like this: 0x55 0xff 0x00 D1 ~D1 D2 ~D2 ... Dn ~Dn C ~C where D1...Dn are the message body, and C = D1 + D2 + ... Dn. The data for sending an IR message is F7 followed by the 8 bit "message". For example: 55 ff 00 f7 08 12 ed 09 f6 is a packet sending the message "0x12" to the RCX. ------------------------------------------------ Can someone help me to create a lirc.conf because I cannot find any documentation regarding the format of this file ? I am using lirc 0.6.6-CVS (08/24/2002) Have fun, Bogdan |
From: Karl B. <ka...@tu...> - 2002-08-27 04:51:39
|
I don't think irrecord & lircd are designed to work with the IR protocol you describe. They may work in this "raw" mode to a degree as you found out. You may want to consider using the LIRC driver and adding a custom application on top of this. I did this for an application that did not fit the common remote model(transmit only): http://www.turbobit.com/software/jvc_send-0.0.2.tgz Another alternative is to figure out how to write your own lircd.conf files based on the protocol and some raw recordings. (this could work around some limitations of irrecord). cheers, Karl. On Mon, Aug 26, 2002 at 06:20:02PM +0300, Bogdan Ghidireac wrote: > Hi, > > I want to use lirc to send/receive messages from the Zaurus PDA to my Lego > robot (RCX brick). So far I was able to learn some codes (motor A/B/C > forward/backward, beep) using irrecord -f and to reproduce them using > omni-remote. The lego robot understands the codes and it's pretty cool :) > > Now I want to create a real lirc.conf file, without using the --force option > but I have a problem. Here is the output of the recording session: > > ------------------------------------------------ > Press RETURN now to start recording. > ............................................................................ > .... > Found const length: 215942 > Please keep on pressing buttons like described above. > ............................................................................ > .... > RC-6 remote control found. > 2No header data. > No repeat code found. > Signals are biphase encoded. > Signal length is 59 > Checking for toggle bit. > Please press an arbitrary button repeatedly as fast as possible (don't hold > it down!). > irrecord: no data for 10 secs, aborting > > No toggle bit found. > But I know for sure that RC6 has a toggle bit! > ------------------------------------------------ > > irrecord was searching the toggle bit for more than 4-5 minutes so I gave > up. > > > I am not familiar with RC-6 protocol but here is the protocol used to > communicate with the RCX (from http://www.crynwr.com/lego-robotics/) > > ------------------------------------------------ > The IR protocol associated with sending a "message" to the RCX is pretty > simple. Bit encoding is 2400 bps, NRZ, 1 start, 8 data, odd parity, 1 stop > bit. A '0' is coded as a 417us pulse of 38kHz IR, a '1' bit is 417us of > nothing. > > At the packet level, all packets look like this: > > 0x55 0xff 0x00 D1 ~D1 D2 ~D2 ... Dn ~Dn C ~C > > where D1...Dn are the message body, and C = D1 + D2 + ... Dn. > The data for sending an IR message is F7 followed by the 8 bit "message". > For example: > > 55 ff 00 f7 08 12 ed 09 f6 > > is a packet sending the message "0x12" to the RCX. > ------------------------------------------------ > > > Can someone help me to create a lirc.conf because I cannot find any > documentation regarding the format of this file ? > > I am using lirc 0.6.6-CVS (08/24/2002) > > Have fun, > Bogdan > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > |