Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by jason

  1. @mjkuwp94

    As mentioned by everyone, your concerns are extremely valid. I'm using if not the same, but an extremely similar IR receiver you mentioned on sparkfun.

    You actually won't be able to tell the modulation frequency with that specific part. The output of this part is a noise free, demodulated signal from the received IR signal. If you point your remote at this part, and shoot, you will be able to receive the output on your scope because 56kHz is still within the wide frequency band of the on part filter. However, when passing through the AGC, it could have unpredicted results on the output which will show up as jitter, or worse. You can try this experiment by looking at the output and comparing your scope shot next to the IR receiver, and again when emitting a signal from the other side of the room, where the frequency effects would be more exaggerated.

    My algorithm will be fine tuned in the future for this, and eliminate the need for double recording (is that your primary concern?). But overall, I have to play a lot of tricks in order for this RC6 protocol to work which is outside the specified 38kHz center frequency of my receiver.

    All this being said, there are some RC6 protocols which are 38kHz, in which the only problem would be the double presses issue, in which you would need to record your button twice. If this truly what you are seeing, how is the performance of your flirc when you have done so? I've often found RC6, regardless, doesn't seem as solid.

    Thanks so much mjkuwp94.

  2. What an amazing story and it humbles me to hear your gratitude. I'm so grateful the product has solved your problem, and it's personal stories like this that make all the hard work worth it. Thank you so much for sharing, and please don't hesitate to post, email, or shout out should you have any questions or feedback. Happy Holidays and a healthy new year to you.

    Very Sincerely,


  3. I'm not sure you could. You can get a harmony remote and program the specific buttons on the remote just for flirc, while volume up/down could control your receiver. That's what I do, I was never fond of changing devices on the remote if I had to do this often. The cheapest harmony is about 20 bucks, but you get what you pay for: http://www.amazon.com/Logitech-Harmony-300i-Remote-Control/dp/B003IZFCFW/ref=sr_1_1?ie=UTF8&qid=1323539773&sr=8-1

  4. I'm not entirely convinced it's flirc, but let's try to get to the bottom of it.

    Do you have any logs you can check? Does XBMC have a log in windows you could look at immediately after a reboot from a crash?

    How about installing a different version of XBMC?

    Let me know.

  5. You can try a piece of electrical tape, although I'm not sure that would work as the sensor on the inside is a wide angle.

    Interesting problem, maybe there could be something in flirc which would say, 'if this button is received, ignore all signals until it is received again'.

    Would be tricky and I'd have to leave it as a super advanced option as I could see a lot of trouble coming from this.

  6. Yes, I agree, sounds like two different problems. Certainly create a different thread for that one, but gfxmonk is most likely right, this is probably noise due to ambient light.

    @gfxmonk, there isn't really a log because flirc uses the generic HID driver that comes with the OS.

    How USB keyboards work is this. When you press a key, the keyboard sends the key, followed by a null. The null says, "I'm not pressing the key anymore". Otherwise, the host thinks you are holding it down. One thing that could be happening is the null is sent too

    quickly to the host, and the host misses this. But this really shouldn't be the case since I wait for the host to be ready.

    One thing we can try is the interkey_delay. Changing this value will actually also adversely change the delay this termination signal gets sent to the computer.

    You can change this with the command line:

    flirc interkey_delay 0-7

    Try increasing this.

    Doing flirc interkey_delay by itself shows the current value set.

    Let me know.

    -- Jason

  7. This definitely sounds like an OS problem, and the first of I've heard of something like this. Interkey delay is for something a bit different.

    I'm sure linux has a GUI for configuring the keyboard. Maybe there is something in there.

    When the key get's stuck, could you switch to a terminal and do a:

    dmesg | tail

    perhaps that would show us something.

    Thanks gfxmonk

  8. Pseudo is exactly right. I did experiment with black plastic, which is transparent for the infrared spectrum. I was extremely disappointed in the quality. It's a plastic that looks extremely cheap and I was not happy with the effect on the sensitivity. Maybe one day I will look at this again.

  9. curently we can erase the IR codes one at a time, given that with certain remotes we have to program each button twice it'd be nice to click erase and then click a key on the virtual keyboad and have that erase all IR code associated with it.

    so if you had a problem with the behaviour with the up arrow, for example, you could click erase, then the up arrow on the virtual keyboard and every IR code associated with it would be deleted so you could just remap that key again without it undoing anything else. i guess its more of an issue for those with things like the xbox remote which need each button programming twice because you have to erase each button twice and things start to go horribly horribly wrong if you only erase one of the two IR codes.


    Will add this one for sure.

  10. Not really, Flirc doesn't really have hex codes for your remote. I use a proprietary way to link your remote with flirc and that information that would otherwise be useless to a machine, os, or software.

    Don't have any intentions to document the config files. The wrong bit set, could potentially brick your device if you didn't know what you were doing.


  11. Eskrow, Jason did mention in the xbmc forums that long presses was in the process of being worked on. I did see your post eskro about a work around with repeated keys for certain harmony remotes. The reason i purchased a flirc is to get other remotes such as a users samsung remote, or any remote for that matter to work with xbmc / mediacenter . And not be tied down to just harmony remotes in media center mode which would be able to handle most of my needs or any users needs.

    Pseudo 7, I appreciate the welcome!! Since i came from an appletv2 with xbmc eden, all the buttons were there and i could do more with the long press buttons such as fast forwarding a bit more or scrolling through the list to skip items. Other than that, the up down left right enter back and play pause works perfectly.

    I wonder if i can get openelec debugging remote program to see the codes and have the built lirc that is in openelec take the information instead. I understand the flirc usb itself presents itself to the system as a keyboard so it might not be possible without a firmware upgrade. We will see how this goes as im planning stages to start reselling some media boxes with some custom aluminum cases that matches well wtih the aluminum appleremote. The feedback i've always gotten from some of my older customers is simplicity, something easy enough for grandma and kids thats intuitive.

    Sounds like flirc is a good match, but what do I know, I'm biased. = )

    Something that you can do is pre-load configuration files. If you sell apple remotes paired with flirc, then you can pre-load the apple remote configuration. If you talk to me beforehand, I can load this while I bring them up before packaging.

    Long keypresses will be supported, I'm currently working on another firmware feature which is waking your computer up from sleep. You can follow the blog for beta release announcements or follow the forums themselves:


  • Create New...