From: Eric B. <eri...@gm...> - 2005-08-01 02:57:21
|
i think i tried this. the problem i ran into was the amount of shit. i=20 actually only needed to shift half a bit. (whaa!?!) by half a bit, i mean= =20 the order of pulse-space/space-pulse. the page i found describing the=20 robosapien protocol said: If the data bit is 0: signal goes high for 1/1200 sec, and low for 1/1200 sec. If the data bit is 1: signal goes high for 4/1200 sec, and low for 1/1200 sec. although lirc.conf wants 0s and 1s in this format: - *one <pone> <sone>* The pulse and space lengths representing a one.=20 - *zero <pzero> <szero>* The pulse and space lengths representing a zero.=20 unless ptrail shifts everything, i'm not sure it will work. as far as the= =20 eps value goes, that was probably left over from when i was frantically=20 changing any value i could in order to make things line up :)=20 -eric On 31 Jul 2005 14:38:00 +0200, Christoph Bartelmus <li...@ba...>=20 wrote: >=20 > Hi! >=20 > Eric Buehl "eri...@gm..." wrote: >=20 > > I built a simple LIRC configuration file that implements all the remote > [...] > > http://www.andrew.cmu.edu/user/ebuehl/robosapien-lirc/ >=20 > Only one remark: I think the device in fact uses 7 bits. The last bit is > not always 0 (just as the first is not always 1), but instead you should > add a "ptrail 833" to the config file and shift right all codes one bit. > This would be consistent with common IR protocols. >=20 > > begin remote > > > > name Robosapien > > > > frequency 39200 > > header 6666 3333 > > bits 8 > > eps 500 >=20 > The eps value usually should be around 30. 500 doesn't make much sense. >=20 > Christoph >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic= k > |