Jump to content

mjkuwp94

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by mjkuwp94

  1. follow up. yes, I found that if I do the routine of programming each MCE button twice then I get good results. As I mentioned above it's not so fun but maybe i am lazier than most! one issue I can think of is that with this routine some applications will not respond correctly to fast-forward commands. I recall that sometimes one press is 1X forward speed, 2 presses is 2X forward, etc. I didn't test it but I guess the end user (application) will not be able to respond correctly. btw, you can see in another thread that I am using a keypress application in Windows provided by user NJKA to do the testing.
  2. The HP and Rosewill remotes designed for WMC (Windows Media Center) both worked the same way. After matching commands to Flirc, they worked but - not really. I eventually figured out that approximately only every other keypress did anything. After further research, this thread included I figured out the issue seemed to be the toggle bit. At one point, I reached the maximum memory of the Flirc so I wasn't too thrilled with the idea of programming each button twice and so I never gave that a good try. I may try again if I find some time - no promises. Would I need to go through the entire button programming sequence twice? Like: Press play on Flirc GUI Press Play on MCE remote Press play on Flirc GUI Press Play on MCE remote ? I can see how that might work but it sure seems tedious and also would it take up double the normal memory? It would be much nicer if you could somehow use the desktop application (gui) to decode the remote protocol and assist with the Flirc programming. It could then recognize the RC6 protocol and prompt the user to press the key two additional times, for example. I admit after reading a few of the protocol specs, my head is totally spinning. I didn't anticipate these things would be so complicated. One more thing - I checked the modulation frequency on both my MCE remotes again. I came up with 36 kHz again. I used the DSO Nano - I have to set the timebase so that I just see the very beginning of the command and also scale and offset the voltage (essentially zooming way in) but then the ripple is extremely easy to see. It doesn't matter to me personally what priority you put on something like this. I am sure it will help the project in the long run but for me I want results very soon so I am trying a combination of Sony remotes and Harmony 300. I do like the Flirc concept a lot and that is why I was willing to abandon the MCE remotes in the short term.
  3. Just realized I was not complete or detailed enough in my earlier post - sorry! I also have a Tek 2235 Analog scope and a DSO Nano and a bare IR Receiver Diode. These parts are what I used to measure the modulation frequency. The DSO Nano waveforms can be captured and analyzed on the PC and I think the Nano just barely does have enough bandwidth to pick up the modulation. I get your point about the jitter and if I get some time I will re-measure the modulation frequency on my two 'Windows' remotes which are actually HP and Rosewill brand. My home theater components are Panasonic and Sony so it seems I will have good luck if I use some other remote controls. I think the biggest thing I was reacting to is that the front page of FLIRC makes it very clear in capital letters that ANY remote will work though this is not totally accurate. Leaving out all remotes designed for Windows MCE seems like a big hole. I had initially planned to do my remote integration with Arduino and the Ken Shirriff library but the deeper I get I see I don't have enough time for this. I am sticking with Flirc for now and will either use a Sony universal remote or pick up a Harmony remote since it seems those are highly endorsed by the community.
  4. I am guessing the issue isn't the 38kHz nominal. A Sony remote worked really well and is likely at 40kHz. The Media center remote is 36kHz. I *assume* Flirc uses a 38kHz receiver nominal so it would still have sensitivity for for the other modulation frequencies used. I have been testing the remotes with an Arduino board, an IR receiver breakout board from Sparkfun and a library by Ken Shirriff. I checked the modulation frequency with an oscilloscope. I am by no means an expert but unofficial information on the RC6 protocol seems to be readily available. For my solution, I am simply going to find a Sony universal remote and give up on the Windows media center remotes (or any Phillips RC6 protocol remote?). It will be far quicker and easier for me to solve the problem that way. It doesn't change my assertion that the Flirc product should support those remotes. Not to get too far off topic... but a big reason I am sticking with the Flirc is the fact it can wake up my HTPC from USB.
  5. eskro, I didn't see where MCE remotes were not suggested. Actually I find that suggestion a little unreasonable as this device is intended for "your PC media center" according to the front page of the Flirc website. I just tried an old Sony DVD remote; mapped the keys to FLIRC and it worked shockingly better. However, the Windows media center remotes should be supported because they will have close to the appropriate keys for a media center. Until then Flirc team, how about a more prominent warning about the type of remotes supported.
  6. The so-called strange issue seems to be part of the RC6 protocol (little bit of research on Google led right to it). The last transmitted bit is a toggle bit that allows the receiver to distinguish multiple key presses. I hope you can correct the firmware and/or the GUI soon - the workaround to program keys will be pretty tedious and will be hit and miss. I have been having good results except for this issue.
×
×
  • Create New...