Hi, Since my remoter is http://en.qi-hardware.com/wiki/File:Adam_remote_controller_2.jpg After took some waveforms on receiver's output pin, i did scopes below:
* my versions on m1: Flickernoise 1.0RC1 (built on Jun 3 2011) GUI toolkit: MTK1.2 OS: RTEMS 4.10.99.0 Platform: Milkymist SoC 1.0 CPU: LatticeMico32 Board: M1 (PCB rev. 1) *All presses is under using a quick and short period to push btn, and try not to let it repeated emit. 1482 remoter, btn 1, 1st press, gui shows: 0x1c, I visually read code must be: 11-1-00000-000001 (after inverted); http://en.qi-hardware.com/wiki/File:1482-btn1-1st_11-1-00000-000001.jpg 1482 remoter, btn 1, 2nd press, gui: 0x0c, 11-0-00000-000001; http://en.qi-hardware.com/wiki/File:1482-btn1-2nd_11-0-00000-000001.jpg 1482 remoter, btn 9, 1st press, gui: 0x0c, 11-0-0000-001001; http://en.qi-hardware.com/wiki/File:1482-btn9-1st_11-0-00000-001001.jpg 1482 remoter, btn 9, 2nd press, gui: 0x2c, 11-1-0000-001001; http://en.qi-hardware.com/wiki/File:1482-btn9-2nd_11-1-00000-001001.jpg from them above, 1) my remoter transmits very well and consistently on codes, 2) only need to notice the 3rd bit from left, it will be toggled when even i press the same key again. 3) the whole RC5 code transmit period is rough to 24.3ms, see http://en.wikipedia.org/wiki/RC-5 and also http://users.telenet.be/davshomepage/rc5.htm 4) gui shows wrong after went to http://www.jaecs.com.tw/Web/pdtype.asp?PdCate=1&PdType=2 , i got T003 24keys*4 pcs with RC5 protocol back, also got a code table(which i can't upload it); http://en.qi-hardware.com/wiki/File:T003_front.JPG so a system code 07 and a data code 01 provided is for its btn pause/play key. i did the same works for T003: btn play, 1st press, 11-0-00111-000001; http://en.qi-hardware.com/wiki/File:T003-btn1-1st_11-0-00111-000001.jpg btn play, 2nd press, 11-1-00111-000001; http://en.qi-hardware.com/wiki/File:T003-btn1-2nd_11-1-00111-000001.jpg home key, 1st press, 11-0-00111-001001; http://en.qi-hardware.com/wiki/File:T003-btn9-1st_11-0-00111-001001.JPG home key, 2nd press, 11-1-00111-001001; http://en.qi-hardware.com/wiki/File:T003-btn9-2nd_11-1-00111-001001.JPG from them four above, 1) gui can't read for all 2) T003 transmits well and consistently on code but its whole transmit is 23.5ms, i visually read IR receiver's signal which meets to its code emitted. Unfortunately this visit made on their site without available engineers there, so I didn't bring my 1482 remote to let them decode. :-) They have had a universal for R&D purpose which can show several format codes. But I only called on the phone to know few techs that how they decodes on receiver's main board side. Here's some info on s/w needed: 1, using falling edge or rising edge as a primary skeleton/rule to capture transmitting period on low to high or high to low to determine which bi-phase 2, 1) goes along with pulling & counting period time as a secondary rule to eliminate noise, etc. thus half of "T" time( 1.778ms / 2 = 889us ) needs to be taken consideration. Like 889us +/- 20%, some sort of they called threshold timing value well-defined firstly. 3, regards to if using/decoding repeat mode, depends on use case. Since I have no idea on fpga side, hopefully this can be as reference. I also brought another two models remoter with NEC protocols samples: T016 & T021. http://en.qi-hardware.com/wiki/File:T016_front.JPG http://en.qi-hardware.com/wiki/File:T016_rear.JPG http://en.qi-hardware.com/wiki/File:T021_front.JPG http://en.qi-hardware.com/wiki/File:T021_rear.JPG * They don't do COB process compared to China vendor, they insist on using TSOP or SOIC for some reasons: better price, good quality control, more strengthen case design, no protection on spilling liquids design now, MOQ-1K, Lead time for 4 weeks once approved on printing customized.* Usually all models can be programed for RC5, or NEC, etc. * Click material can be membrane or metal doom, T016 is a metal one phew, i just got gerbers so I need to interrupt remote stuff now until gerber-out. Thanks, adam
_______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode Twitter: www.twitter.com/milkymistvj Ideas? http://milkymist.uservoice.com
