Jump to content
Flirc Forums

yawor

Administrators
  • Posts

    1,003
  • Joined

  • Last visited

  • Days Won

    74

Everything posted by yawor

  1. There is no "rate control" in the Flirc itself. All Flirc does is that it reports to the operating system that the key is pressed. What controls the repeat rate is the operating system itself. For example, in Windows, there is a keyboard configuration applet in the Control Panel that allows you to change the repeat delay and rate. There may be some differences between how the operating system handles different keys. I don't know what keys are used for the Fire TV, but the minimalist controller is just using keyboard cursor keys for direction buttons and enter key for center button.
  2. Clear the configuration and only make sure that built-in profiles are enabled in advanced settings. In MyHarmony add Flirc/XBMC profile to your Harmony remote. You don't need to select XBMC/Kodi controller in the GUI. That's only for recording buttons manually (for people who don't want to use built-in profiles or don't have Harmony remote). You can also record extra buttons in addition to the built-in profile ones. But if you don't want to modify anything beyond the built-in profile you don't need to record anything. BTW it seems that you have a high IR background noise that makes Flirc go crazy. What kind of lights do you have in home? Some light sources can do this. Also a Plasma TV is a big source of IR radiation.
  3. Yes, a Harmony or some other universal remote capable of similar functionality is the easiest way of achieving what you've described. There were threads on the forum where some users had been trying to do this (using a TV remote control) and there are solutions described but they are Windows specific (based on AutoHotKey if I remember correctly). I think it may be possible to achieve this on the RPi but I don't know it's worth the time spent making it work and then on the fine tuning.
  4. Hi, Unfortunately this is not possible - at least not with a Flirc alone. First of all how would you want the RPi to detect when it should not accept commands from Flirc? By detecting if the HDMI2 is currently selected or not (I don't even know if this is possible)? Or by pressing some button on the remote to toggle the Flirc input? You need to describe how it should work in more details.
  5. In 3.5 firmware you should be able to at least have power up working correctly. It doesn't support power off yet. This has been fixed in firmware 3.6 which is in Flirc software 1.3.5 rc2 version (available on "beta" forum - don't be alarmed by the "beta" in the name of the forum, this is a release candidate version). Have you recorded a power button with flirc_util record power? If yes then only thing I can think of why you can't power on the HTPC is that Flirc-SE is not getting power through USB when in S5 power state. Can you confirm somehow that USB ports are powered in S5 (power off) state? Maybe you have something that can be charged from USB port - then just plug it in when the HTPC is shutdown. As for the volume keys not working: do you have volume punch through set up on the remote? When you switch to a device where you've set up the code for Flirc and press vol up/down does your AMP react? I have no problem at all with a Samsung TV code on my remote. I have PVR device button mode changed to TV and a Samsung TV code set on it. Every single button on the remote works and sends unique signal which is correctly recognized by Flirc. I think I've selected some newer TV model. Maybe that's the difference. You can also try some Panasonic TV (I haven't tried myself but I've read that they are OK). You also can't have your remote too close to the Flirc when recording. It is very sensitive and when the distance is too small then the signal gets distorted. You should have the remote at least 1 meter (3 feets) from the Flirc. Or you can point the remote in a different direction, for example at the ceiling.
  6. Hi. Try using Samsung TV codes. I'm using one with my URC-6440. Do you use RemoteMaster software to configure the remote? If yes then you can even create your own device upgrade which won't be recognized by any consumer hardware. I would use NEC1 protocol as I have good results with it and flirc.
  7. I think that you might have recorded volume buttons you normally use for your amp to control volume on the PC. Just go into Flirc GUI, press Erase and press volume up button on the remote and the repeat for volume down button.
  8. Hi, The power on feature is already included in 3.5 firmware, which is embedded in Flirc software version 1.3.4. This version is already available to download from main website. This version enables the motherboard power button connection support when PC is powered off, but disables it when PC is on, so you can't use the same button to power off. The 1.3.5 rc.2 version of the software which is available on "beta" forum contains firmware version 3.6 which also allow the power off to work properly - it uses the motherboard power button so you need to configure your system to shutdown or suspend when the power button is pressed depending on what you want. It won't brick your Flirc. The force firmware option doesn't automatically check for new firmware online. It flashes the one which is included in the installed version of the software.
  9. The most important thing is that Flirc programming is not affected by the selected keyboard layout. It is it's operation afterwards. It's because all Flirc knows is what HID key code send to the PC but it doesn't know how this code is mapped in the system.
  10. Raphnix what keyboard layout are you using? The mapping in GUI is based on US QWERTY keyboard layout. If you have different layout set in the system then you'll get different keys back when pressing remote buttons. This happens because Flirc acts as a HID keyboard device. HID standard doesn't map a HID code directly to a specific character on the key but to a key in specific location on the keyboard. Please look here I've described there the solution based on a french keyboard layout so you'll need to update it for your layout if you use something different. Basically you need to look at your physical keyboard where is the "=" key and use the same key location in the GUI (keyboard row and the position of the key in the row).
  11. I don't know what tax laws are in the Spain but you may need to pay import tax and/or vat when buying something outside of EU. I know that small purchases often are exempted from extra taxes but if you buy a greater number of devices at once (or in a short period of time) you may not be so lucky. At least this is how things look in Poland which is also in EU. So check your tax and import laws before buying to be sure it's still better option than buying from an European shop. As for the purchase I think you can try contacting Jason (via PM or email - it is on his profile page here on forum).
  12. The exploit problem has been dealt with. Once again thank you for the info :).
  13. Yes, this is the way you do it. When there olis no key you want on the other controllers you just need to use keyboard one. Thank you for the heads up about the exploit. I've not used google to search this forum for a long time and it somehow went unnoticed who knows for how long.
  14. I think that the best way of describing what can flirc do and what can't is to check what you can or can't do with you keyboard. Where does the key press goes when you press the key on the keyboard? Usually it is the app which is currently in focus. There can be some exceptions like the media keys where presses usually go to some kind of player even if the player is in background.
  15. The best resource about XBMC/Kodi is their wiki based documentation: http://kodi.wiki/view/Keymap You need to create a keyboard.xml file in proper directory (it depends on the system - the correct path can be found on the wiki page I've linked): <keymap> <fullscreenvideo> <keyboard> <enter>PlayPause</enter> <return>PlayPause</return> </keyboard> </fullscreenvideo> </keymap> This configuration overrides enter key in FullScreenVideo mode to emit PlayPause action. It means that when you play a movie and nothing more is displayed (no menu, player controls etc, just a video playing) you can use enter/return key to play and pause the video. You can still open player controls (OSD) using M key while playing the video. Of course you need to assign your center button to the enter key. If you already have a custom keyboard.xml then you need to edit it and add <enter> and <return> entries at correct location. If you don't know anything about XML files then post the file here I'll modify it for you.
  16. I'm sorry but this is not possible. At least not with flirc alone. First of all you can't assign multiple keys to one remote button, but also the flirc itself doesn't know anything about the software you are running. It can only send key presses, it doesn't receive info what is currently going on. There is a chance though. Xbmc/kodi is very flexible when it comes to customisation. You can try remapping keyboard controls using the keyboard.xml file so that you can use the same button for play, pause and OK.
  17. If you don't want to make any config changes to the flirc then you really don't need the flirc software at all. Just plug it into the PC and everything should work as before. You only need the software to change flirc configuration and to record buttons.
  18. You can threat it like 2 different wake modes. If no button is recorded for wake function at all then all the buttons that are recorded for any key in flirc will wake the PC. On the other hand if you record some button for wake key the only this button will wake the PC. But you need to remember that the button recorded for wake can't be used as a different key, so if you record you menu button to act as a wake then you won't be able to use it in any other way (for example to open a menu).
  19. Starting with some early 3.x firmware version any recorded button should wake the PC from S3 or S4 if those points are all true: 1. Suspend detection is enabled in the advanced settings 2. Windows power management settings are set to allow waking the system from the keyboard (can be set in device manager for specific keyboard and mouse devices) 3. No button is recorded to the wake key in flirc (if it is then only that button will wake the PC). There is no possibility to assign a wake key to button that is already assigned to a different keyboard key.
  20. The first problem here is that Flirc can accept only a single mapping per remote button. You can't tell it to use power button when PC is off and some keyboard key when it is on as you can't store two different actions for a single IR hash. Also in this rc firmware, as per request, Jason specifically removed part of the code that discriminated between power states for the "power" key so he would need to add it back and somehow allow to map second action for power-on state and this is not possible as I've mentioned before. To support multiple actions per IR hash whole config section in EEPROM would need to have different structure making new firmware once again incompatible with older one. If you are really able to capture ACPI event before it is received by the Windows then you can also emit S key to the Windows which would pop the shutdown dialog in Kodi. This would require a conditional execution (in pseudo-code): on (ACPI power button event) { if (Kodi window is present) { emit('s'); } else { exec('kodi.exe'); } } ---edit--- Hmmm I've re-read your posts and I maybe know what you meant. You want that when the host is powered on then Flirc shouldn't send the signal over the wires to the motherboard power switch pins but instead it should emit a Keyboard Power key with is defined as HID code 0x66 in the HID keyboard standard. Am I correct? Jason would it be possible to include this as an option in Advanced options? Something like "Send Keyboard Power key instead of pressing power button when in power on state". When unchecked it would retain current behavior (shorting mobo power pins independent of host power state), but checked would turn on power state detection and would send the 0x66 (or maybe 0x30 from consumer usage table?) key instead when host is in power on state.
  21. Flirc has rather a simple hardware: microprocessor, IR receiver, clock source (I don't know if this is a generator or a quartz oscillator) and few support elements. If your unit is really not showing up as anything in the system then I think there ale only two elements that could be somehow damaged: either the microprocessor or the clock source. The only reason why they could get damaged is that you may have a problem with power source or USB port voltage regulation and the voltage on the USB port is not stable. Maybe there is some overvoltage (I don't know if Flirc has its own voltage regulator to prevent overvoltage from USB).
  22. I don't think that's possible unless you can programmatically catch ACPI signal when the power button is "pressed" and conditionally prevent its propagation to the system which would normally trigger system shutdown. But if you have such possibility (to capture the ACPI signal) then you actually wouldn't need additional input from Flirc because you could use the ACPI signal itself to start the Kodi if it's not yet started. A quick search on Google tells me that capturing ACPI signal and preventing the system to shutdown upon it may be possible on Linux, but I couldn't find a Windows based solution. Flirc itself can't support such logic because it doesn't know anything about applications running on your system.
  23. Do you maybe have USB2.0 ports on the board? I think I saw some posts before about problems with USB3.0 but I'm not sure right now. Did you had any bootloader issues on firmware 3.x at all? The bootloader is programmed into a microprocessor during Flirc production and AFAIK is not upgradable by the user. The version should be engraved on the microprocessor and you can see it through the transparent case (at least in case of 2.0 and 2.1 bootloaders). You can also see the BL version during firmware upgrade or you can force Flirc to go into BL mode by using flirc_util dfu command in the CLI. When Flirc is in bootloader mode then you should be able to see bootloader version in Flirc GUI (can be a little cropped) or you can display it using flirc_util version command in the CLI. It should also be visible when Flirc is stuck in the bootloader.
  24. It's not in my power to make such decision so I'll skip the subject of the way firmware upgrade works right now. Why would you need to re-download Flirc software every time a unit is stuck in bootloader? You actually just need a single PC in the store with a Flirc software where you can fix your problem. Also there is usually really no reason to upgrade Flirc software other than upgrading the firmware bundled with it. If the software is changed somehow it is because that change is required for the new firmware. It is not a surprise that your config stopped working after upgrading from 2.x to 3.x, because IR signal processing algorithm has changed in 3.x making old configs incompatible - formatting and re-recording is required with that upgrade. I think the real problem here is why some of your units are getting stuck in the bootloader. If such thing happens again can you post which bootloader version you have? Also can you post what device is driving your displays? Maybe there is a problem with power supply and/or unstable voltage on USB ports.
  25. Hi, There is no flirc_util shutdown command. If you have your Flirc-SE connected properly (the Power button is routed through the Flirc instead of directly to the board) then you should record a button for "power" keys: flirc_util.exe record power and then you press a button on the remote. If you've upgraded Flirc to the rc.2 version I've linked to then you can send the power button signal when the PC is either on or off. It will turn on the PC from any power off state (from suspended, hibernation or full shutdown). When pressing when in power on state then the system settings decide what to do.
×
×
  • Create New...