yawor
-
Posts
1,003 -
Joined
-
Last visited
-
Days Won
74
Posts posted by yawor
-
-
MCE remotes use RC6 protocol which alternates two (or more) codes at each press of a button - not only power button but every one of them. It requires recording each button at least two times with the same key combination in the GUI. It is a well known issue with MCE remotes here on the forum and I think this has nothing to do with the way Harmony remote behaves. You can also use the same trick that is used with MCE remotes and just record the power button two times.
-
Shimsim is probably right. You have to make sure that the motherboard is able to supply power to the USB devices in S5 state (full power off). There may be an option in the BIOS for that.
-
Hi,
You can't do this in the GUI, but there is a command line tool (installed with the GUI) named flirc_util, which allows to display recorded keys:
flirc_util keys
There's a bug on Windows so you need to execute it with full file name:
flirc_util.exe keys
You need to be on one of the latest releases (1.3.5 or 1.3.6 maybe) because earlier versions haven't displayed all the keys.
-
I think that this may be a Harmony issue rather than the Flirc one. I don't have Harmony so I won't be much of a help in this area but maybe there is some setting for the power button to send different signals on consecutive presses?
-
Hi. Are you sure you haven't changed the keyboard layout in the OS? Have you tried plugging Flirc to different USB ports?
-
Hi,
I'm sorry you are experiencing such problems. I'm not sure I'll be able to help but there are a couple of things you can do to help pinpointing the problem:
- What power supply are you using to power RPi? Can you post the output power ratings?
- Do you have another power supply you can test with? As it is powered using microusb you can use any phone charger.
- Have you tried plugging Flirc into PC and test it there? Do you see keys highlighting in Flirc software when you press the remote button after you recorded it? You can also do a notepad test and check if it write something when you press the buttons.
- Have you tried plugging Flirc into other USB port on the Pi?
-
How do I install v3.5 or higher? I'm running v2.6 and don't see the FireTV option. I feel like an idiot, but I can't seem to find the higher releases anywhere. When I go file->advanced and force firmware upgrade it says v2.6 is the latest.
Thanks!
Hi,
The firmware is embedded in the Flirc software. To upgrade the firmware you need to first upgrade the software on the PC/Mac. It should then automatically detect you are on outdated firmware and offer an upgrade. If not the you can always go to advanced and force the firmware upgrade.
-
You shouldn't need to do anything in the system. Flirc IS an USB HID keyboard (at least it acts as one). You need to use Flirc software first to record button presses from the remote and assign them to specific keys.
-
The RC6 protocol usually toggles only a single bit but the problem is that the whole signal is stored in a hashed form. Even single bit change can generate very different hash value in the Flirc. The trick is to properly detect that the signal is an RC6 one and do something with it. The best thing would be to ignore this bit so no matter if it is set or not the hash would be the same. But I don't think it is possible with processing power of microcontroller used in Flirc as this would require to actually decode the signal into raw data. The other course of action would be to ask the user to press the button one more time if RC6 signal is detected - not ideal solution because user still needs to press the button multiple times but at least there is no need to manually record the same key combination again.
-
Yes, you can delete the button from the GUI but there is also a delete command in flirc_util.exe. If you run flirc_util.exe without any parameters you will get all available commands.
The Fn key is a keyboard controller extension and it's not sending anything to the system itself. It just changes the HID code sent to the system by the controller when the key is pressed with or without holding the Fn key. In your case the PrintScrn key is sent when Fn key is pressed but this is just a hardware keyboard behavior. Using PrintScrn HID code in Flirc should be enough.
-
It should be available in /dev/input/. It acts as a standard USB HID keyboard.
-
You need to remember that Flirc will always act upon receiving the signal if it's one for the already learned buttons. So if the HTPC with Flirc plugged in is powered on even when you just use the cable every time you use directional and OK keys your HTPC will also react.
I'm not familiar with the remote you have. But if it is an universal remote then you should be able to program it to control different devices. Does it have device select buttons to switch the device you want to control? Can it be programmed to control more than one device?
-
Recording buttons from remote doesn't change how the remote works. If this is a remote for your other hardware you're still using then it'll still be recognized by the hardware. If you want fully separate control then you should use remote for a device you don't own or use a universal remote which has the ability to control multiple devices.
-
Hi,
Until the feature is implemented you can use command line util to record keypad buttons.
flirc_util.exe record_api XXX YYY
where XXX is modifier value and YYY is a key HID code.
HID codes for keypad are:83 Keypad Num Lock and Clear 84 Keypad / 85 Keypad * 86 Keypad - 87 Keypad + 88 Keypad ENTER 89 Keypad 1 and End 90 Keypad 2 and Down Arrow 91 Keypad 3 and PageDn 92 Keypad 4 and Left Arrow 93 Keypad 5 94 Keypad 6 and Right Arrow 95 Keypad 7 and Home 96 Keypad 8 and Up Arrow 97 Keypad 9 and PageUp 98 Keypad 0 and Insert 99 Keypad . and Delete
So if you want to record a button for keypad 8 without any modifiers then you should use
flirc_util.exe record_api 0 96
and after pressing enter the command should wait for you to press some button on the remote.
The modifier value is described in the help of the record_api command itself. The flirc_util.exe is in the same folder where the Flirc.exe is installed.
-
In my personal opinion the Harmony hardware is simply not strong enough to support their firmware/software fast enough or the firmware/software is not very well optimized. I've resigned from buying one and went with OFA Simple 4 (URC-6440). It's not as advanced as most Harmony remotes but it offers good amount of options for the price and it also has backlit keys.
-
I don't know if I understand step 3 correctly. Did you desolder the header pins from the Flirc SE board? If yes, then why don't just use female header connector? Also I'm not exactly sure about step 4. Maybe some pictures would help better understand these steps.
-
Hi,
I'm using RPi2 with OSMC and I don't have any problems at all neither in the menu nor while in playback. Maybe it's something wrong with the openelec but it would be strange. Both distributions are using Kodi, so unless openelec modified it in some strange ways I don't see why would it behave that way.
-
Hi,
Are you trying to use Flirc with USB3.0? If yes then please take a look at this thread
-
Hi,
Try plugging it to different USB port. There's sometimes a strange Windows error where the keyboard part of the Flirc stops working on current port. I think it is somehow connected to installing new version of Flirc software when Flirc is plugged in. So next time you install newer version unplug Flirc first. I don't know if it helps for sure but was working for me so far.
-
Hi,
As you have noticed it's not a problem with the Flirc itself as the normal keyboard is also not able to wake up your hardware. I don't know the Zotac brand so I can't tell you for sure what the problem is. You should definitely check your BIOS settings and maybe check if there is a BIOS upgrade. If this is a normal x86/x64 hardware then you could try running a Windows on it and check if it's able to configure wake up for USB devices properly.
-
1
-
-
Hi,
I would suggest using something different than AppleTV remote (for example LG or Samsung TV) and directly from the emitter.
-
I don't know if it's as simple as compatibility with USB 3.0. I think that many people here are actually using Flirc plugged into USB 3.0. The problem may be more complex and may be connected to some specific USB host controllers on the motherboard or maybe combination of controller and Windows 8. That's why this needs more testing and it's really great that you are even willing to buy the USB 2.0 hub to try to resolve this problem - of course there is no guarantee that this methods will be successful, if not then we will be trying other approaches.
I would need to check this with my hardware as I have 2 USB 3.0 ports on the motherboard if the issue is present on my hardware too.
PS. I'm just helping here on the forum and I have no influence on the way the Flirc is sold or described. I agree that if there really are some issues with specific hardware then there should be some info available before purchasing. But I don't think that the lack of such info is because of some bad will. Flirc is developed and maintained by a single person and he is really balancing on an edge trying to split his time between his daily work, his family and Flirc development. And he is really trying his best to make Flirc work for everyone and on every hardware combination (you have to agree that there are so many possible hardware combinations that there is no way to test it fully even on a small portion of them - even big companies sometimes have problems with that).
-
Do you have some friend or colleague who have an USB 2.0 hub? If yes then please borrow one and connect Flirc via the hub. If the problem is really with USB 3.0 then Flirc should start working correctly when connected via the USB 2.0 hub.
-
Hi,
Nice instructions. I don't speak Russian but I've translated it using Google Translator to check it out. As for the IR noise you need to check for possible sources of it. It can be a Plasma TV or incandescent light. You can try turning off lights in the room and check if you still need the foil. Without the foil you should record buttons from the remote from some distance (1-2 meters away from the receiver) or point the remote in different direction (for example at the ceiling).
I've also looked at the comments. I see a lot references to cheaper IR receivers. You should point out that Flirc is not just a simple IR receiver. It acts as an USB keyboard and after programming it doesn't need any software installed on the machine at all (for example you can do programming on one PC but use it in another - for example an HTPC connected to a TV receiver and the HTPC doesn't need any additional software installed for Flirc to work).
Flexible Flirc - One way to set up a Flirc to power up your HTPC
in How To
Posted
I see you've updated your post. Now it explains more clearly what have you done. Previously it sounded like you'd desoldered the male pin header connector from the Flirc board :) and soldered the wires directly.