Posts posted by yawor
Have you tried backspace in XBMC? I think this is the behavior you are looking for.
Here are all the keys you had mapped in the config file you posted:
Up Arrow Down Arrow Left Arrow Right Arrow Return (Enter) Escape . Page Up Page Down Home End s ctrl+h 1 2 3 4 5 6 7 8 9 0 ctrl+f m n Backspace F7 z , Spacebar r x Delete t l c o i q
Sorry, I've never used IR blaster so I can't tell you with one to choose based on my experience.
The EventGhost has plugins for UIRT2 and USB-UIRT compatible devices. I've checked and at least the USB-UIRT plugin has the ability to send IR signals. The EventGhost also has a keyboard input plugin which can be used to capture keys recorded in Flirc. You do this by creating an action in EventGhost to send IR signal with the blaster and add a keyboard event to trigger the action.
To be honest, in your case I would go with just the USB-UIRT as it is a two-way device - it can both send and receive IR signals. The USB-UIRT plugin in the EventGhost also supports both directions and it have the ability to learn an IR signal from real remote to be used later with IR sender. Flirc is a very nice device but in this case it would be redundant.
I don't know if I understand you correctly. Do you want to connect both Flirc and IR blaster to a single system (for example a PC) and use Flirc input to drive IR blaster?
It should be possible with help of some software stack to glue both together. Basically the software needs to catch input from Flirc and drive IR blaster software based on it. For example GhostEvent is capable of doing it and it has a plugin for IR blasters built-in, but it is Windows only software, so if you don't want to use Windows or you can't (if you use Raspberry Pi for example), then you need to find something else.
Oh, silly me. I haven't realized that I was searching only inside this thread :). OK, I've found the other topic about Intelliremote and I think I understand how the author managed to use it. He used two separate receivers: one original for MCE remote which works with Intelliremote which he set up to only do something for numeric and start buttons on the remote, and Flirc as a keyboard for everything else.
Flirc's main advantage is that it works as a keyboard, so you don't need any software for its normal operation (software is needed only for programming). I don't know the Intelliremote software so I can't tell you if there is any way for it to recognize Flirc. I don't think anyone here is using this software - at least no one had ever asked about it before you.
Ground should be common for the whole setup. It shouldn't matter where you attach it but I'm not electrical engineer. If you look at the thread I've linked you can see that in both cases those two users grounded the USB metal shield plug/socket part (shield).
I don't think that putting a very large resistor will work as a ground connection. I don't know if this is universal across different countries but in Poland you always have a phase wire and zero wire. In 2-wire installations the zero wire can also be used as a ground. As a electrical engineer you should know how this work in your country and you should be able to check which wire is for the zero if you have one.
I hope you understood my explanation. English is not my primary language and this subject involves some technical language I may be not familiar with.
1) Is your setup properly grounded? Does your MicroUSB PSU have a ground lead? There were already two cases where grounding RPi's USB port metal shield made the repeating key problem go away. You can follow the discussion here
2) Plasma TVs are known to produce IR pollution. The problem here is that Flirc is an universal receiver. Because of that it is very sensitive to all kinds of IR signals to allow a wide variety of remotes with different protocols. You can try covering its casing with some IR opaque tape or something like that to allow the IR signal to go in only from single direction (the opposite side from the USB plug) and place it in a way that it doesn't "see" the TV screen.
I'm sorry. I've forgotten to include link to the usage tables I've been referring to. I'll edit the post and add the link there too.
I've based my description on the numbers in this document. I'm not an expert with all this USB stuff so I can't tell if these numbers are correct or not.
BTW simulation control in the document I've linked above is in table 2. I wonder why the numbers are different from the ones in the official USB doc.
The zip files which are linked in 3.0/3.1 threads contain binaries for all systems, Linux included.
I have a crystal on my PCB, it's the metal box. The top of the metal is grounded. What's the resistance between the shield of the USB and the top of the crystal. (Do this when it's not plugged in).
Then can you check your USB mating shield on your motherboard with the ground your connecting the flirc to?
Someone could use power strip without ground wire or maybe ungrounded wall sockets. I think it depends on the country and the year the building was constructed. In Poland there is still a lot of ungrounded sockets in use in old buildings. I've replaced all electric installation in my flat after I bought it so it uses now a proper 3-wire cables and sockets with grounding.
Also microusb power supplies don't have often a ground connection so the Raspberry Pi setup is not grounded properly. Even if the TV is grounded it's not very good setup as both sides of shielded HDMI cable should be grounded properly. Now we have two cases of fixing Flirc operation by grounding the setup so maybe there should be some troubleshooting guide and one of the things to check should be checking if the setup is grounded :).
Flirc doesn't send scan codes. It uses USB HID protocol and sends HID key IDs. I've already described on the forum how you can assign keys from different layouts. The thing is that changing layout doesn't change IDs of the keys so for example Q key on QWERTY layout has the same key ID as A on AZERTY layout. So to assign A on AZERTY you actually need to record button for Q in Flirc GUI. Also using key modifiers (like shift, alt etc) doesn't change key ID so to assign 1 on AZERTY you need to record for Shift + 1 in Flirc GUI.
You can read more here:
1) Yes, you can record a remote's button which will be used for wake function. In new 3.0 firmware (which is still in Release Candidate state - available on the forum) there are some changes in the way the wake function works. By default, if sleep detection is enabled, the Flirc will wake up the computer with any of the recorded buttons (it won't wake the PC with a code not recorded in it) unless you record a single code for the wake function which will revert the behavior to the one from older firmware (only this one key wakes the PC).
2) I don't know about the apple's remote long press but I think it's not supported yet. About the wake key reuse there is no such option. You can record each remote's button only once and you cannot assign multiple keys to the button. The only way to use all keys and have keep the wake function is to use new wake behavior in 3.0 firmware as I've mentioned in point 1.
I'm using only Firefox and have no problem logging in on this forum. Maybe you disabled cookies or have some cookie blocking extension installed in your Firefox.
1. Have you already tried this with 3.0 firmware?
2. Why are you mapping F8/F10 keys to get mute and volume up? Have you mapped them in XBMC that way?
3. Have you tried with another remote?
4. Have you tried assigning problematic buttons on the remote to different functions? If it also neither record nor work for functions different than vol up and mute then the problem is that the protocol used in the remote may be incompatible with Flirc.
I think that first thing to do is to check if the device is properly grounded from the power outlet. If this is a PC with a three lead plug and the outlet is grounded then whole PC is already grounded together with its USB ports. If it's the raspberry pi we are talking about then there is a good chance that the power supply is a simple PSU without the ground lead. You don't need to solder anything to anything actually. RPi have ground pins in its GPIO pin header which can be used to ground the whole setup. Just look up the GPIO pin header description on Google or directly on RPi wiki. Just note which exactly version of pi you have as there were some changes with a second version (the one with mounting holes).
I think that you are being a little rude here. Also please refrain from using all caps - it's impolite.
If you want a step by step instructions then there is already one for each supported operating system on the forum. It's not hard to find it. Please look at the main forum page, there is a section called "Getting started with Flirc" and it has a topic with the same name. It should be totally sufficient as long as you don't need to upgrade the firmware of your Flirc. Just forget about "Force firmware upgrade" and go with the instructions provided.
After a lot of testing I have managed to solve my problem.
Can you post your solution? It will help future users if they stumble upon the same problem.
@Usernametaken: you have some valid points. Unfortunately I'm not in the power to change anything on the website as I'm only helping here on the forum in my free time.
Add a Home page link to every page on the website, for example in the page header of the forums so when a user needs to go back to the main site.
There is a link on the forum to the website. It's called Store Front and is just below Flirc logo.
Consider adding a link to latest firmware on front page and on "Downloads" page, the only way I found the firmware was by coming here and you providing me the link but now I have the link to the firmware I am confused even more than ever, I go here and it says " !! WINDOWS USERS: Go to advanced->force firmware upgrade" Ok great I am a windows user so where is the "force firmware upgrade" for me to download and use? Their needs to be a link to the file so I can download spent 10 minutes trying to find the "force firmware upgrade" with no luck.
The "force firmware upgrade" is an option menu in the software itself. If you look closely the version numbers in the change log are links. They are direct links to zip files containing all the needed files. For now those zips contain versions for all supported operating systems. They are not linked from the website because those are not yet considered as final release but as a release candidate. When Jason is sure the firmware is stable enough then he will release it as a final 3.0 version and it will be linked from the website.
One thing you need to know is that you actually don't need to install anything on the Raspberry itself. The software is only needed for firmware upgrade and configuration. You can do this on PC (Windows/Linux) or Mac. All recorded remote buttons are stored in the Flirc itself together with assigned to them keyboard keys. Then you just unplug Flirc from PC and connect it to Raspberry Pi.
You can use any layout at any time. This is only to make the mapping simpler for specific tasks like XBMC control. Basically the keyboard layout is the advanced one (+ the media keys one as keyboard layout doesn't have those buttons) and the rest is a subset with letters replaced by different icons. The layout itself is not saved into Flirc in any way.
You can test this by recording some buttons in XBMC layout, then switch to the keyboard layout and press buttons on the remote you recorded earlier. You will see that the keys on virtual keyboard are being highlighted.
I've notified Jason about this thread so hopefully he will respond soon.
You can always map one of the buttons on the remote to C key. This key opens a context menu on currently selected item in XBMC and you can navigate with cursor keys to select add to favorites.
You have some nice ideas. I like the idea of showing in the GUI which keys are assigned already but there is a problem with highlighting them on the virtual keyboard. You can have some buttons mapped to keys with modifiers and I just don't see a way how to present them all highlighted at once.
The problem with keyboard layouts is very well known already but supporting them all is very hard to a single programmer. It would be nice for GUI to support pluggable layouts which would allow to create them by the people on the forum and share them with others. Maybe some online repository of layouts which could be downloaded into the GUI could be nice.
I agree that messages could be better :-).
Flirc casing is almost fully transparent to the IR signal so there is no possibility of signal being reflected multiple times inside the case. If material is transparent to some wavelength then it cannot reflect the same wavelength.
I have only white walls in my home which is perfect for signal reflection but I don't experience the problem described here. Instead I have a very good signal reception from almost any position :-). Also the reflected signal is quickly dissipated and cannot bounce back and forth between walls that long.
Help I need step by step instructions on how to use the FLIRC.
Where I am so far, bought the FLIRC open the package and it says to go to the website for the free software, so I download the software, no instruction to be found any place, I assume since this plugs into the USB I plugged it into my computers USB port.
Have no clue what to do next.
Clicked on "Support" on the web page found no basic install or use instructions.
On the main page its says.
How it Works Flirc learns any remote control, not caring about different vendor protocols. Just walk through our super simple setup pairing individual remote buttons with 'Media Center Buttons' and you're done.
I have no idea what any of that statement means or how to make it apply to the FLIRC, their is a "Video" button I click on the link I get a black window that pops up, no video, no sound just a black box on my screen.
That's strange. I've just clicked on the Video now and the video plays without any problems. The video itself is stored on Vimeo. Maybe you'll have more luck playing it directly on http://vimeo.com/12542134.
I have to agree that the main Flirc website could be better and probably needs some refresh.
Trying to figure out how to get a email notification of any replies.
When you create new topic you have "Follow this topic?" check box in the right sidebar, next to the content editor. When replying, you need to click on the "More Reply Options" first to go into full editor mode.
First update the firmware. file:advanced:forcefwupgrade. Make sure you have latest version of program downloaded
Then simply look at the main screen and press GO. This will program the bAsic button paths. From there it depends on your application. Goto contollers: (pick app). You can manually program your key presses.
When done SAVE CONFIGURATION
If your front end is an android, simply program on windows box and install usb directly to android device when done. Good luck
Not to confuse anyone, you actually don't need to Save Configuration. This option allows to save configuration to a file for backup. Recorded keys are stored in Flirc instantaneously.
I also recommend downloading 3.0 firmware from the forum here http://forum.flirc.tv/index.php?/forum/73-firmware-30/. As of the moment of writing this the newest is 3.0 RC12. This version is very stable now and (unless some show stopping bug is found) will be released as 3.0 stable.
mac mini, flirc, and tv remote
in General Questions
1. You don't need to run Flirc application for Flirc to work. You only use the app to program Flirc to recognize your remote and send specific key strokes to the computer.
2. Flirc has a very good sensitivity but it also depends on the type of surface you have behind the Mac Mini - how good will it reflect IR signal from the remote. I wouldn't worry much about this. You can always use a short USB extender cable or even a small mirror right behind the Mac if it doesn't work out of the box :).
3. I don't know how Mac Mini's IR receiver works and if you can access and use it for your own purpose. But I suppose it's not a problem for you as you want to use Flirc anyway.
4. With Raspberry Pi you are probably using HDMI CEC to control XBMC with TV remote. When reusing the remote without CEC enabled for Mac Mini + Flirc you can run into a unwanted behavior on TV like some communicates or warnings (it depends on the TV). You need to know which keys are inactive on TV's remote when in HDMI input mode to avoid conflicts with TV functions. On the other hand if you also use the TV with other inputs (like Air or Cable TV etc) and use the remote in a normal way with the TV then you will also send the same signals to the Mac Mini which may also cause unwanted behavior. I would recommend a separate remote (maybe universal one if you want to use one remote for all equipment).