Search the Community

In the flirc gui, go to 'controllers' menu and choose 'full keyboard'. You can add any key from there, for example, you would just click on F4 and then press the button on the remote that you want to send the F4 command.

If I could get to the GUI I would do as you suggest. When I said the program does not launch I meant the GUI. I click on Flirc in Accessories and nothing happens. I don't mind using command line if I knew how to find the firmware version. fw_1.0.bin is no longer available (404 error). mike

I'm trying to install my new Flirc on a Zotac AD03 running Mythbuntu 12.04. I got the sources list modified and the apt-get-update and apt-get install flirc work fine and the program shows up in Applications -> Accessoreis -> Flirc. When I click on it it does not launch. The wait icon is present for a few seconds before the normal mouse pointer returns. Just on a chance I installed ia32-libs, nothing. I found a command line approach but I can't find a firmware version that doesn't return a 404 when I attempt a wget http://downloads.flirc.tv/fw/fw_x.x.bin. How do I get firmware into the device? mike

yes, I need to update my command utility so you can delete them by index, they don't show up, however, you can do flirc_util delete, and then hit the button on your remote, that should do it. Yes, sounds like harmony is ignoring it. It wouldn't be the first time. On my harmony, If I press the button twice in 20ms, it will insert a delay of 1s in between them, always. So if I hit the key 10 times, it takes ten f&*$@#'n seconds to get to my tv.

yeah still working on it, but just open up a command prompt, and type: sudo Flirc It runs as super user, I just can't figure out why it wont run without elevated privileges

hi, i've got a harmony 700. i'm seeing repeated keypresses being emitted at the slightest touch of (especially) the red/green/yellow/blue buttons. i've programmed these particular keys to be alt+z, alt+x, alt+c, alt+v. even after setting repeats to zero (in harmony), setting inter-key delay to 1000ms on the harmony, and setting inter-key delay to 7 on the flirc, i am still having this issue. what is very odd to me is that holding a key will emit about 10 repeats a second. if i understand what inter-key delay is supposed to do, a setting of 1000ms should only emit 1 keypress a second at a maximum. but i'm still seeing about 10/s emitted. so it seems like this setting is being ignored. does that sound right? strangely, although regular keys also repeat quickly, as if they ignore inter-key delay, they don't emit multiple keypress events at the slightest touch like the ones configured with record_api do. another thing i've noticed is that since recording them with flirc_util record_api, i can't delete them (they don't appear in the output of 'settings'), and i can't re-record them using the standard 'record' command (it says key already in use). so i'm unable to test if the hair-trigger nature of the red/green/yellow/red keys is a result of using record_api, or there is something else going on (at least without formatting and losing *all* of my settings). in conclusion, either i'm misunderstanding inter-key delay in thinking that it will rate-limit key repeats proportional to the specified delay, or inter-key delay is horribly broken somewhere. and, i am unable to re-record keys as non-modifier keys that were previously recorded with record_api, nor am i able to delete them using flirc_util. p.s. this is on firmware 3.0 / flirc_util 1.2.7

Hi, thanks for the info. OK, when I save it using the command line, it automatically saves it with the correct extension ie if I type in flirc_util saveconfig ~/Desktop/my_flirc_config it saves the config file as "my_flirc_config.fcfg" The good news is that this file is now automatically listed by the GUI, & by manually renaming the other backup configs that I've done, they now show up too. I haven't actually loaded one of the files though, as my flirc is doing nearly everything that I need it to currently.

Hey guys, finally got time to test RC2 myself. My findings, all on Windows: 1.) Installed Gui 1.3, started Gui, plugged in Flirc, gets recognised as FW 3.1, Guis asks to upgrade to 3.3, Gui upgrades, recognises Flirc as FW 3.3, down in the middel of the GUI it says "Unsupported firmware, try upgrading". Tried closing Gui, unpluggins Flirc and redo the process multiple times. Asks me for the eighth time now after reopeneing the Gui to upgrade firmware. Flirc_Util says on status: Last upgrade attempt: Error Ignoring the upgrade message and just clear config and go ahead learning some keys works flawless for me. Some more testing needed though. 2.) Forcing FW upgrade through the menus says "Your firmware version is: 3,3 The latest firmware version is: 3.2" Sound like a typo. After doing the force upgrade, flirc_util still says error on last upgrade attempt. GUI says "Firmware successfully upgraded". 3.) While trying to use the 334kb sized flirc_util.exe from the extracted zip (release/windows), it cries about missing libusb-1.0.dll. Using flirc_util.exe (505kb) that gets installed by the installer works fine. Still, typing flirc_util without its .exe extension in a command prompt just does not work, you HAVE to write "flirc_util.exe". Not an expetected behavior. So yeah, learning keys obviously works, but some messages are very confusing. That's all for now. Cheers guys and thanks to Jason for fighting bugs for us. :-D

Just to followup and confirm. I just tried the media play/pause/FF/RW buttons on my flirc using this chart and the record_api command to set the keys. Rewind puts the Nexus player to sleep Fast forward did nothing Play toggled play and pause Pause did nothing Stop did nothing I tried all the keys while playing back media just to verify. I'm going to update my post in the other thread just so no one gets confused.

What exactly do you need help with? The Harmony profile provided from Flirc includes a Poweroff command that sends the XBMC the keyboard command Ctrl-F12. Since that keyboard command does absolutely nothing I'm simply telling the XMBC to respond to that keyboard command by suspending through a custom keymap profile. This is how to ssh into openelec: http://wiki.openelec.tv/index.php/OpenELEC_FAQ#SSH This tells you everything you need to know about keymapping in xbmc: http://kodi.wiki/view/Keymap

Hello, I have the same "Keys stuck" problem that many others seem to have recently. As in this thread: I'm using openelec on an x86 computer and I'm using a Samsung TV remote to control it. I am a firmware programmer with experience in USB HID devices and I've studied this problem with my USB analyzer. I believe I understand the problem. First a bit of background: The Flirc firmware enumerates as a USB HID keyboard which sends keypresses. It also detects IR signals from remotes. IR remotes use codes that repeat when a button is held down, so filtering is necessary to prevent unwanted repetition of a keypress. Keyboards also have key repeat rates, but it is implemented differently than IR remotes. USB Keyboards use key on and key off messages. It is up to the OS or application to fascilitate key repeat. The problem is that this key repeat delay varies from O/S to O/S, and in some cases from program to program, which is why the inter-key delay settings don't work the same for everyone. If you press and hold down a key on your keyboard you'll see the keypress immediately register, then a short delay, then it will begin to repeat that key. Another thing that complicates things is that IR signals takes some time to actually be received and the IR remote repeat rate varies from remote to remote.. I'm assuming that the vast majority of remotes should take less than 50mS to send a key press, hence my default InterButtonDelay value below. I've captured the USB traffic with several different inter-key delay settings in the Flirc v3.1 firmware. It appears that the inter-key delay setting is actually changing 2 separate things with one delay. I think this is where the trouble lies. Both the IR command ignore delay AND the key down time seem to be modified by this one setting. If the delay is set too low, then the IR repeat rate becomes the dominant factor and you get multiple key presses because of the IR remote sending too quickly (which is unavoidable). If the delay is set high, then the key down time starts becoming long enough that the O/S thinks the key is being held down, so it starts repeating the key. The key down time shouldn't be increased simply because the IR button delay time is increased. When changing both of these, it becomes a balancing act between the two indpendent problems. Most people don't realize that setting the delay to 6 isn't actually the safest choice and 0 doesn't work well either. It isn't obvious why this would be the case though. You really have to find the happy medium that works best. I found a setting of 5 worked best for me, but it still wasn't working completely perfectly. I propose a different implementation of the inter-key delay that works by detecting how long the button has been released and sending the key up message as soon as it has been detected as released. Expected behavior: *If the button is pressed rapidly, as long as there is at least a 50mS pause between presses (button press 20 times per second should be a reasonable limit), then all presses should be recognized as individual presses and releases. *If the button is held down, as long as it is not released for more than 50mS, then the key released event will not be fired and the OS will eventually start repeating the key as expected. *If two different buttons are pressed within 50mS of each other, then the first will be pressed briefly and released as the next is pressed. (This should yield expected behavior) I implemented the keyboard sending code as a queue to guarantee that if 2 commands are needed back to back before the next USB EP1 IN request, then both are guaranteed to be done. This could be implemented a few different ways. A queue is just the mechanism I used. Initialization: ButtonPressed = false; ButtonReleasedTime = 0; InterButtonDelay = 50; //default value in milliseconds.. should be configurable. (this is the time the button is RELEASED, not held...) Upon receiving a recognized IR command (ReceivedKeyCode): if (!ButtonPressed) { QueueSendKeyboardCode(ReceivedKeyCode); //new button pressed: ButtonReleasedTime = 0; //Keep track of how long the button has been released ButtonPressed = true; ButtonPressKeyCode = ReceivedKeyCode; } else { //a button was pressed and we are waiting the minimum release time of that button: if (ButtonPressKeyCode == ReceivedKeyCode) { //Same button was pressed: ButtonReleasedTime = 0; //restart the release timer } else { //different button pressed before the release timeout. Switch buttons QueueSendRelease(); //release previously held button QueueSendKeyboardCode(ReceivedKeyCode); //send new button //new button pressed: ButtonReleasedTime = 0; ButtonPressed = true; ButtonPressKeyCode = ReceivedKeyCode; } } Timer routine (every millisecond - should be thread safe... should be non-interrupt context: same as above code): if (ButtonPressed) { ButtonReleasedTime++; if (ButtonReleasedTime > InterButtonDelay) { QueueSendReleased(); ButtonPressed = false; } } By the way, I understand that this is a closed source project, but if you'd allow me access to the source I'd be happy to work on the project. I don't have direct experience with Atmel chips, but I have worked with Microchip and ST, and to be honest it doesn't make all that much difference once you have the basic framework in place. I've attached one of the USB captures I made that I exported to excel format to analyze what was going on. Joe flic brief presses several repeats interkeydelay is 3.zip

Alt+esc got the home button!! Although I'm on a mac right now and the command+esc and command+space didn't do home/search. I can try again later from a windows machine but I assume they send the same keys.

You should not be able to record the same key again without deleting it before recording again. My last suggestion is for you to try all codes from 1 to 255 (second number still 102). I know that this may take some time. Maybe save your current config from the GUI or command line, then erase Flirc and start recording starting from code 1 102 and increment for all available buttons on the remote (remember which code for which button). Then try all the buttons with Android TV and if you don't find the Home button then erase again and start from next code after the one you recorded in previous round.

Normally the record_api command in flirc_util.exe allows you to record a key with a modifier. The first number is a combination of modifiers (left/right shift/control/alt/windows) and the second is a USB HID key code of the key. There is a special case when the second number is 102. This tells Flirc to send a key code defined by a first number from different HID usage table. The code 154 then means a Media Select Home button. I'm not sure if this is the correct one so you need to check it yourself. I've described more in this thread:

Same problem also here with same setup. Interkey 0 and noise cancelling helped a bit, but often when pressing up und down the command is issued twice. Latest FW 3.1 running with Fire TV profile.

Hi, Do you know how to use command line? There is an executable called flirc_util.exe in Flirc folder (on Windows) or just flirc_util under Linux and OS X. You can try running it like that: flirc_util.exe record_api 154 102 (remove .exe from the command name in case of Linux and OS X). After you press enter it will wait for a remote button to be pressed like in the GUI. Please let me know if this works.

The Flirc has some great features and *can* be relatively easy to use. However, without documentation of any kind, I must start actively recommending fellow hardware users in various hardware forums I participate in to avoid purchasing the Flirc (I have been actively pushing the Flirc for various devices for over a year up to this point). I can't understand how anyone can release hardware of this potentially advanced nature without any documentation whatsoever. Even as a one man shop, documentation should be of the highest priority in any hardware and software released for public consumption. Take the command line utility flirc_util.exe. It seems to be very powerful and is often given as the cryptic answer for various issues all over this forum. Cryptic is the key: without documentation, how is anyone supposed to guess at its actual workings? A perfect example is the record_api fucntion.. I've seen 10's of threads asking how to record the "menu" key for various hardware. The answer is often given as use flirc_util's record_api fuction. Wonderful that the developer has created such a utility that can solve those kinds of issues, but without documentation it is limited to his own use and a cabal of a few other advanced users only. I'm not trying to bash the Flirc in any way... I see it as a wonderful piece of hardware with great potential and easy use for limited applications. I am a realist, however, and the conclusion of that realism is: without documentation the Flirc is more of a potentially frustrating curiosity than an actual tool for many people. Please document both the GUI and, most important, the command line utility for those that actually need to go beyond an extremely simple setup. Thank you.

Hey, I've got a lot of troubles with my Flirc. For beginning, it didn't function at all under Win7, GUI crashed immediately. After searching for a while the problem was a WD external HD, it sounds totally funny, but after the WD was connected to the external USB3 port, and the Flirc to an internal USB2 the Gui crashed. After connecting the WD to an external USB2 port, the problem was gone. Making any sense, not at all, but it was the solution! But now if installed Win 8.1. Flirc is correct installed, and functions. But i can't program it, can't bind keys, can't delete keys, nothing at all. When is use the command based version of Flirc, it telles me that the Firmware version=V240.240 . I think it isn't able to write and read from the Flirc, if i change a setting, Interkey Delay, it isn't saving the value. Anybody with tips? Running in win 7 modus doesn't help.

I'm not sure I understand what you mean by "remote profile." I launch Flirc. I select Full Keyboard, because I need to teach it keyboard commands such as Command F1 through Command F5 and Option F1 through Option F5, plus Command ESC, and so on. I'm not pairing Flirc with Boxee or Plex. I'm using Flirc to trigger keyboard commands that control various applications. I checked Advanced Settings, and Noise Canceler isn't checked. I'm not suggesting Flirc doesn't work. I'm just finding that it often misses commands if the remote isn't pointed enough in its direction, and I'm surprised because it sits next to my Mac's IR receiver which has no trouble picking up commands even if the remote is pointed nowhere near it.

First of all is the Flirc below the "line of sight" when you take the IR signal bouncing from the wall in front of the couch? What I mean is you point the remote in the direction of the stereo and it bounces from the wall and goes back. If not you could use an USB extender cable to rise the Flirc higher so it can see the bounced signal. I have my Flirc out of the line of sight from the remote (actually in another room next to the one with TV) and I get 100% reception of the IR signal when pointing remote at the TV (it bounces of at least one wall). It also depends on the power of the remote's IR LED. Now to your question. Short answer: yes, it's possible with some amount of work. Long answer: It depends on the firmware of your router. Are you using OpenWRT or some other custom firmware? I'll base my answer on OpenWRT as it is most popular and open router firmware. There is a daemon (service) called triggerhappy. It's available in package repository for OpenWRT so it's installation should be easy but you need to be comfortable with using Linux terminal. Triggerhappy allows you to catch events from an input device (like keyboard) and execute your own scripts upon them. Next you would need some software or script on both devices (the router and the Mac) which would allow to push events over the network. I'm not familiar with Mac applications so I can't help you with this part. For Windows I would use EventGhost which has network input plugin (acts as a server and allows event generating clients to connect to it and push events to it). I also see a way to keep the wake key functionality. It requires the ability to wake the computer with Wake-on-LAN magic packet (most modern computers do) and just map the power button to wol command in the triggerhappy config.

Alongside some back-and-forth with Jason (THANKS man!) -- I blew away 2 of my 3 flircs (in very similar fashion to the process you used, maxwell), and additionally made an adjustment to my Harmony 650 per the instructions here: http://support.myharmony.com/en/article.htm?faqid=s-a-2158&ref=s-ts-3001--a-3-3& There, I changed Device Command Repeats to 0 (from 1) for the Flirc Media Player device. After some testing I handed the remote back over to the missus, who is usually the best test case ever. She didn't manage to cause repeating keys, so I'm cautiously optimistic. edit=fired it up this morning and unfortunately I'm hitting the bug again.

Hi Guys Thanks for all the useful information in this thread. I started on the journey with a harmony 650 and the flirc xbmc profile. The latest gui (3.1 at this point) takes away almost all the pain for XBMC. The only place where I got stuck was - The amazon fire home button - couldn't get it to work with the command line mapping to 101 - Solved The back button for amazon fire (the return button works fine for xbmc) - Not Solved If anyone is looking for a solution to home button not working with 101 - I ended up using 69 ( in the command ;) ) as follows - flirc_util.exe record_api 0 69 The logic behind that number is this post here which maps all key presses to their codes - Additional details for logitech Harmony or anyone trying to troubleshoot remote key presses- As mentioned, I was working with a Logitech Harmony 650. I waanted to map the Menu button with Home and exit button with back for fire tv (not XBMC). For a while I tried a few other buttons and couldn't see any of them even registered on the remote as sending anything. If you understand the harmony remote universe, I was trying this within an activity for watching movies - i.e. while the remote was working in a combined mode of sending key presses for volume commands to the amp and any media key presses to flirc+aftv etc. To be able to see what exactly the remote was doing, I installed eventghost (free). If you have used it you would know what its for, if you haven't - suffice it to say it can be used to program your windows OS (and therefore XBMC on windows) to map remote buttons to specific actions. So the setup was - My laptop running wondows + eventghost and flirc plugged in to the laptop. I also enabled the keyboard plugin on eventghost so that it listens and translates to flirc events as keyboard events. That would mean that any keypresses on my harmony were seen by flirc Passed to EG and displayed on screen as keyboard event they represented. Result - Part 1 - Event-ghost confirmed that the menu and exit keys on my remote were not doing anything. For this one, I used the harmony software to include these keys for my chosen activity (watch movies). The action on these buttons could be anything for now, as I wanted to just ensure that the keys were working. (For good measure, I also added these two menu options to the onscreen menu on lLogitech but you can ignore that ) Part 2 - Now that the buttons were firing, I needed to map them to send in whatever fire tv receives as a home button. I repeated the command line option in the thread so that the button press would be seen as F12. Maybe I tried it too many times but for some reason I couldnt get EG to report it as F12. It would either be registered as something else or an F12 followed by two returns. That is when I did some more digging and got to the post mentioned above with details on key presses and their numerical equivalents. Ultimately, I got to see F12 and it works. Part 3 - For some reason though, I still couldnt get the whole thing to work for back button. It should be recognised as an escape key. As with F12, I have used the corresponding code for my harmony exit button as well as the screen option. It is received as an escape followed by two returns. It might be a case of flirc keeping the old values, although I've tried deleting it a few times. Or it might be a case of fiddling with the key repeat time etc. I was too tired to persist with it but will try again later Hope all of that is useful to someone.

I'm trying to upgrade my current FLIRC package using the following command rpm -Uhv flirc-1.2.6-2.i386.rpm and it produces the following error / conflicts Preparing... ################################# [100%] file / from install of flirc-1.2.6-2.i386 conflicts with file from package filesystem-3.2-19.fc20.i686 file /lib from install of flirc-1.2.6-2.i386 conflicts with file from package filesystem-3.2-19.fc20.i686 file /usr/bin from install of flirc-1.2.6-2.i386 conflicts with file from package filesystem-3.2-19.fc20.i686 is this the latest and is there a packaging problem here?

There is something else fishy going on! I was just relearning some of the keys missing, number 1 to 4 and added two keys with modifiers "Ctrl+Shift+X". Here is a before/after Lirc_Util keys command. Look at the second output how "7" is suddenly missing! Maybe this related to the sometimes strange behavior of the dongle, seems like a bug whatsoever. Sequence Modifier are disabled in GUI. Is this needed to be able to learn keys with modifiers? As I understand it right, it is okay to not see every index number in the output as these are probably unprintable commands. Right? C:\Program Files (x86)\Flirc>flirc_util.exe keys Recorded Keys: Index hash key ----- --------- --- 0 5E639B9B 5 1 2A32099B 6 2 BA0E9B9B 7 3 CC95779B 8 4 EE402D9B 9 5 3825899B 0 6 F79C9B9B up 7 3339099B down 8 87792D9B left 9 90F9099B right 10 9A00099B return 11 8C0C899B backspace 12 1BE91B9B c 13 65CE779B s 15 FA3E659B F8 16 2993899B f 17 5901B9B r 18 609C9B9B y 19 C7A8F79B suspend 20 9E2A9B9B l 21 A3171B9B e 22 29DC9B9B h 23 8BC72D9B i 24 C7639B9B tab 26 652FF79B x 27 D0C0099B space 28 956CAD9B p 29 32F3AD9B pageup 30 F7573F9B pagedown 33 C8021B9B w 38 20D59B9B F7 39 59D03F9B 1 40 F5AB099B 2 41 BEA1F79B 3 42 4E7E899B 4 43 C9F3AD9B F9 44 8A1AF79B F10 C:\Program Files (x86)\Flirc>flirc_util.exe keys Recorded Keys: Index hash key ----- --------- --- 0 5E639B9B 5 1 2A32099B 6 2 CC959B9B 8 3 EE402D9B 9 4 3825899B 0 5 F79C9B9B up 6 3339099B down 7 87792D9B left 8 90F9099B right 9 9A00099B return 10 8C0C899B backspace 11 1BE91B9B c 12 65CE779B s 14 FA3E659B F8 15 2993899B f 16 5901B9B r 17 609C9B9B y 18 C7A8F79B suspend 19 9E2A9B9B l 20 A3171B9B e 21 29DC9B9B h 22 8BC72D9B i 23 C7639B9B tab 25 652FF79B x 26 D0C0099B space 27 956CAD9B p 28 32F3AD9B pageup 29 F7573F9B pagedown 32 C8021B9B w 37 20D59B9B F7 38 59D03F9B 1 39 F5AB099B 2 40 BEA1F79B 3 41 4E7E899B 4 42 C9F3AD9B F9 43 8A1AF79B F10 C:\Program Files (x86)\Flirc>123456

For me: "Or the only remedy is to press another key, but that key gets stuck." Not just a bit sticky like when I hit keys too many times to fast. Really stuck till the break of dawn. ;-) Right now, on another USB port, my nice Flirc behaves brilliantly, no stuck keys, nothing. I am back on FW3.1 by the way. And yes, I see it works great without replugging. I even have the GUI open, using flirc_util and test the commands in XBMC all at the same time right now, just minimizing the GUI. The time with the stuck keys I am very positive that I weren't able to press ANY learned keys by just closing the GUI. I had to replug Flirc first. I am using Flirc on Windows 7 64 bit right now to program it and will now hop over to the Ubuntu HTPC to test Flirc there. Thanks for the effort and your support! On another note: flirc_util only give output in a command window when you type "flirc_util.exe" INCLUDING the file extension. Made my head scratch pretty hard. ;-)