Jump to content
Flirc Forums

cortex

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cortex

  • Rank
    Curious Flirc-er
  1. Ok so I seemed to have fixed it for now. If anyone else runs into this issue they can try this. I jury-rigged a "tunnel" made out of some paper that separates the FLIRC module from the IR blaster by about 8 inches, taped to the FLIRC at one end, and the IR blaster at the other end. This seemed to solve (most of) the issues with some of the poor registrations and delays. I had to crank up the strength of the IR blaster Just wanted to say thanks to you Jason for helping to walk me thru this process. I realize my solution is unconventional, but hey, it works.
  2. The room is a dark, dedicated media closet. No light in there unfortunately. Any idea on the "too many edges issue"? Also the FLIRC device gets quite warm when I'm using it - is this normal?
  3. Here are the debug files, using the "up" button; single press and sustained press. The other file is demonstrates a rapid repeat press of the "up" button. debug double press.txt debug single and 2 second press.txt
  4. Still getting the same issues even with the remap. Delayed recognition of button presses, ignoring double presses etc. The issue persists when using just the remote without the IR blaster. "too many edges" error is also seen with any double presses.
  5. Does it matter which model I choose?
  6. I didn't have the FLIRC before I got the shield, so it's new to me. As far as the profiles, I'm using the "Shield" profile within the FLIRC device for the programming. As far as the URC remote goes, I'm still using the microsoft windows media center profile - AUX.252. I had been using it with my HTPC and it had seemed to work really well.
  7. I recently switched from a HTPC to an nVidia shield, and purchased a FLIRC for controlling it with my URC Mx-780. The remote had worked flawlessly on my HTPC, which had a separate RF module. With the new system the remote input is very sluggish, to the point of being unusable. Additionally, any quick presses (e.g. doing a double press of one of the direction keys, etc) will not register at all. The debug window gives the constant error of "too many edges" with any quick key press. I have turned down the strength of the IR blaster to its lowest setting, but it still seems to occur. I have wrapped the blaster and the FLIRC window in opaque tape, and that hasn't helped. I have tried to put distance b/w the rf blaster and FLIRC device, but that hasn't helped either. I have tried programming the directional keys etc in multiple ways, including mapping both single and rapid clicks to the same button, but nothing has seemed to help. And when the device is plugged in, even single taps are very sluggish, or don't register at all (though they register when the device is plugged into a laptop). I can post some logs if that would be helpful. Any help would be great. I'm getting to be a bit frustrated with the whole process.
  8. I recently switched from a HTPC to an nVidia shield, and purchased a FLIRC for controlling it with my URC Mx-780. The remote had worked flawlessly on my HTPC, which had a separate RF module. With the new system the remote input is very sluggish, to the point of being unusable. Additionally, any quick presses (e.g. doing a double press of one of the direction keys, etc) will not register at all. The debug window gives the constant error of "too many edges" with any quick key press. I have turned down the strength of the IR blaster to its lowest setting, but it still seems to occur. I have wrapped the blaster and the FLIRC window in opaque tape, and that hasn't helped. I have tried to put distance b/w the rf blaster and FLIRC device, but that hasn't helped either. I have tried programming the directional keys etc in multiple ways, including mapping both single and rapid clicks to the same button, but nothing has seemed to help. And when the device is plugged in, even single taps are very sluggish, or don't register at all (though they register when the device is plugged into a laptop). I can post some logs if that would be helpful. Any help would be great. I'm getting to be a bit frustrated with the whole process.
×