Jump to content
Flirc Forums

yawor

Administrators
  • Posts

    1,003
  • Joined

  • Last visited

  • Days Won

    74

Posts posted by yawor

  1. Hi,

    The guide you've linked to is not very good. I would probably have problems with setting it up using this guide myself. So just forget about it for a moment.

    What keyboard layout are you using? Can I assume it's not US keyboard? If I'm right then go to Advanced options (in File menu in Flirc GUI) and turn off built-in profiles because they are working properly only with US compatible layouts (the problem is with location of "-", "+" and few other keys on the keyboard). Disabling built-in profiles means that even when you choose Flirc/Kodi profile in Harmony it won't work out of the box (but it usually doesn't work properly with non US keyboard layouts anyway).

    You can select Flirc/Kodi profile in Harmony but you're not required to do so. You can try with a profile for some TV (good choices are LG or Samsung for example) - you just need to select something different than you have at home (so don't use Samsung TV profile if you have one).

    To program a key (for example some letter) in Flirc you need to click this key in the GUI. If you need a modifier like Shift, Command etc you press the modifier first and then the key. The application will ask you to press a button on the remote. The message will disappear when the IR signal is received.

    You can do a test and record few letter keys and then open a text editor and press the buttons on the remote. You should be able to type in the editor using keys you've recorded.

    Please try above and let me know if it works up to this point. If it's OK then I'll try to explain how to proceed further.

    • Like 1
  2. This can't be done with Flirc hardware alone. It acts as an USB keyboard and you can't run some script or app by pressing a keyboard key unless you also have some keyboard app/driver installed in the system (like Logitech's SetPoint software dedicated for their hardware). In your case the AutoHotKey is exactly that. It provides you with an ability to map a key to an executable. There are many alternative apps which can also do that like EventGhost for example. Flirc GUI is for programming only and doesn't provide any run time functionality.

  3. Hi,

    Can you try plugging Flirc into different USB port and test if it works again? No need to reinstall anything or record again (if it already has some keys recorded). You can also try plugging Flirc into different PC. Please reply with your results.

  4. Hi,

    I don't remember anyone doing what you want to do. First of all you need to take into an account the length of wires. The IR sensor/chip is sending data with some frequency so the wire will be susceptible to electromagnetic interference from other sources (and also can cause an interference in other nearby hardware). The longer the wire the more there's a chance of the interference. You would probably want to use a shielded wire on the output from the IR chip and properly connect shield to ground on both ends. You should be able to google the datasheet for the IR receiver chip to check which pin is the output pin.

  5. I haven't tried it yet on my PC but I unplug the power from my RPi2 setup from time to time and there has never been a problem with this. Currently I don't use any of my Flircs with a PC but I should be able to do some tests in the following days. I don't think that I'll have similar behavior you see with your units though as I don't remember having such problems when I've used Flirc with PC and I'm fairly sure that there were times when I've unplugged the power from the PC and I didn't have to reflash Flirc afterwards.

  6. To be honest it doesn't make any sense to me. I've thought that either case 2 or 3 would require a reflash, not case 1. If there's some voltage issue on the USB port when the power is plugged or unplugged from the PC then in case 1 there's no way it would affect Flirc as it is unplugged when these would occur

    Do you have all your PCs properly grounded? There were some cases where the hardware hasn't had a proper ground connection in the mains power connection and Flirc misbehaved.

  7. You can try configuring drives to go to sleep after some idle time (you need to consult with documentation or community of the distribution you're using on your RPi). In that state they will be still drawing some power but it should be a really small amount required for drive electronics to detect a request and spin the drives up. Also you're probably using a powered USB HUB because there's no way for RPi be able to power that many drives. Do you unplug the power from the HUB after shutting down the RPi? If not the HUB and the drives themselves still draw some amount of power.

    Now regarding the power management. Flirc can't do something that the platform itself doesn't allow. There's no power management on the RPi board so plugging Flirc is not going to somehow add it. There are some external power management boards for the RPi and they maybe could work with Flirc-SE and there are some boards with IR input integrated. 

  8. Hi,

    It is certainly not an expected behavior. Flirc doesn't need to be powered to retain its configuration or firmware as it is flash/eeprom based. Does this happen with every single Flirc on all your PCs?

    If you could do a few tests please try these scenarios:

    1. Turn off the PC, unplug Flirc, unplug the power, plug the power back, plug the Flirc back, turn on the PC.
    2. Turn off the PC, unplug Flirc, unplug the power, plug the Flirc back, plug the power back, turn on the PC.
    3. Turn off the PC, unplug the power, unplug Flirc, plug the power back, plug the Flirc back, turn on the PC.

    These scenarios differ only in the order of unplugging and plugging back the power and Flirc. After each test check if Flirc works or does it require to be reflashed again.

  9. Hi,

    There are two different "power on" options with Flirc-SE. One is an USB wake up (which is also available in normal Flirc) and the second is a hardware power on switch (uses power on button header on the mobo). Now the first one behaves like you've said. Any button known to Flirc will wake up the PC unless the wake key is programmed. On the other hand the power on button doesn't work like that. You need to specifically record it. I don't know if it's already been added to the GUI so you probably need to record the key using flirc-util command line utility.

    I won't help you with Harmony side though because I don't have nor use one. You probably can add extra keys in some ways to work as a Power On button.

    One thing you need to remember is that the power on button is not stateful right now. If you press the button associated with this function it will trigger power button switch when the power is off but also when it is on which, depending on your power configuration, can turn the PC off or put it into sleep.

  10. Hi,

    There's a really great number of different IR control schemes out there. They may differ in a carrier frequency, modulation schemes and data encoding schemes. It's hard to tell what exact combination this keyboard uses. You would need to have an IR receiver that can capture raw IR signal to a file and then analyze the signal with an IR remote control analysis software. If it's one of the standard RC protocols known by the software used then it should give you some details what it is exactly.

    Flirc uses an IR receiver tuned to about 38kHz carrier frequency because most remote controls are using frequencies like this. It can receive some frequencies around 38kHz but not very far from it. I think that when the receiver get a signal with a frequency that is much higher than the 38kHz then it won't be able to fetch all the raw data and some bits may be lost. If the difference between two signals is in the bits that are lost then these two signals would be recognized by Flirc as one signal. This is just my theory and the reason may be also different.

    Now regarding the issue with modifier keys (shift, alt etc) I don't think there's currently a way to fully use this keyboard (besides the "key already exists" issue). This would need to by analyzed (like I described in the beginning of this post). I wonder how the keyboard encodes information about multiple keys pressed at the same time. I think the control scheme used may be too complicated for Flirc's logic (which is rather simple: one remote code -> one key combination). Also I don't think that a future firmware upgrade would solve these issues.

  11. Yes I can clearly see that you are confused :).

    Flirc basically maps IR codes to keyboard key presses. It has some predefined mappings hardcoded in its firmware but it also allows the user to record new mappings. The name for the hardcoded mappings is built-in profiles.

    The only thing user can change regarding to built-in profiles in the Flirc is to disable or enable them as a whole. There's no option to selectively enable or disable a single built-in profile. I don't know exactly how many built-in profiles Flirc now has because I don't follow this topic closely. These profiles use IR codes that are not used by any other device (they are created for Flirc specifically). To use any of the built-in profiles you just need to configure your Harmony remote to use one of the Flirc profiles in Harmony software.

    You can't just use MCE keyboard profile in Harmony. It won't work out of the box. Flirc is NOT an MCE receiver. If you really want to use this profile you need to map remote button to actual keyboard keys using Flirc software. This is also true to any other Harmony profile or remote control in general that hasn't been created for Flirc built-in profiles.

  12. VIdeonisse I don't have Harmony so I'm not missing anything :). Also I like to have more control over remote to keyboard mappings and also I'm using modified keyboard.xml file in the OSMC/Kodi where I've mapped some functions that are not there by default (for example there's no keyboard shortcut for subtitle search window in Kodi).

    What I think about built-in profiles is that they are nice for a quick start. You just plug it in and basic functionality just works. But after a while you want more. IMO when that happens it's best to just disable built-in profiles at all and map remote yourself to what you want and need. You don't need to resign from Flirc/Kodi profile in Harmony. Just record it in Flirc yourself.

    Also the issue with built-in profiles is that they won't work properly with keyboard layouts that are not compatible with US QWERTY because some symbols are in different places on the keyboard (I've described it on the forum and in more details in my private message to you). I don't think Jason can do anything about that but there probably could be a warning on the website and/or forum that such issue exists.

  13. Hi,

    I would not bother with MCE profiles. MCE remotes are using not very user friendly protocol - it can work but requires extra work. If you want extra keys then add them from some standard device profile like some new LG or Samsung TV (depending on which you don't have so they won't collide with each other). Then just connect Flirc to PC (or Mac), install Flirc software and use Flirc GUI to map remote buttons to the extra keys you need (for example using a keyboard controller in the GUI).

    Regarding controllers, there's no such thing in the Flirc itself. A controller is just a pre-configured page in the Flirc GUI containing key combinations under familiar looking keys (like play, stop etc buttons). Under the hood it's still just a key combination (for example a Stop key in Kodi controller in GUI is just mapped as X key). If you know the key combinations yourself then you can just use full keyboard controller and record all the keys you want there.

    Flirc has built-in profiles for Harmony. It means that there are a few Harmony profiles for Flirc/<some software> pairs (like Flirc/Kodi for example). For the built-in profiles to work you actually need to select Flirc/* profiles in Harmony. Personally I'm not a fan of built-in profiles so I have them disabled (there's such option in the Flirc GUI to disable them).

    • Like 1
  14. any help possible? I would be glad-thank you.

    Even though the Flirc itself can work with any system keyboard layout, the GUI is designed to support only US QWERTY compatible ones. The specific devices controllers (like Kodi) and built-in profiles are also not compatible with non-QWERTY layouts so it's best to not use/disable them in such situation.

    I see that you use non-QWERTY keyboard on the PC (probably german QWERTZ layout). Do you also use non-QWERTY layout on OSMC? I also use OSMC but I don't remember if there's an option to change keyboard layout anywhere (because polish keyboard layout is US QWERTY compatible).

    You can still use the GUI to program Flirc but it requires some extra work. You need to use the full keyboard controller in the app but don't look at the labels of the keys. Just ignore them. Look at your PC keyboard where exactly is the symbol (like +, -, or some letter or number) you want to record in Flirc (the row and how many keys from either side) and if it requires some modifiers like Alt, Ctrl etc. Then use the same modifiers and the key at the same position in the GUI (the same row etc).

    For example you have - (minus) sign next to right shift button (/ and ? on QWERTY). If you want to use minus with Flirc on QWERTZ you need to record a remote button for "/" key in the GUI because it is physically on the same spot on the keyboard.

    I hope I've described this enough. You can also look for my post about French AZERTY layout setup where I've also described this.

  15. Please try if plugging Flirc to a different USB port helps. I've had this issue on my system as well that sometimes a configuration for Flirc on specific port gets messed up and Windows won't react on key presses when Flirc is plugged in that port. After plugging it into another it started working for me (at least for some time). After OS reinstall it stopped doing that so it could be something messed up in the Windows.

    I'm not saying that you have the same issue but it's worth trying.

  16. Hi,

    You need to take into account that Flirc is working as an USB keyboard. That means that you can only send keys you can actually press on a normal keyboard.

    This means that:
    1. You can't use <remote> section in the XBMC config with Flirc as Flirc is not visible as remote receiver but a keyboard.
    2. You shouldn't use any F-keys above F12, as most (if not all) current keyboards don't have those keys anymore. There were some keyboards maybe 20 years ago with them :). That means that some systems won't even process such keys as a valid keyboard input. At least I've tested this on Windows and it doesn't work at all.

    What you should do is to start up the Flirc GUI, select some key combination like ctrl + F12 for example and then record the blue key from the remote so Flirc know that when it receives the IR signal assigned to blue key on the remote it must send ctrl + F12 (or the combination you choose) to the PC.

    After that you can map the function you want to that key combination in Kodi/XBMC.

  17. Please do a test. Start with HTPC suspended and in some activity other than "Watch Videos". Switch to another activity, but still different than "Watch Videos". According to what you said it will wake the HTPC anyway. Wait a moment to let the HTPC fully wake.

    In that state you can do two types of tests:

    1. Switch between two activities (still no Watch Videos) waiting a moment between switching and check if you trigger suspend in the HTPC.
    2. Switch to Watch Videos activity and check if the suspend has been triggered.

    I think there may be two possibilities: either Harmony is sending a button you've recorded for suspend/wake every time when you switch activity (maybe some bug in Harmony) or you've recorded multiple different buttons for wake up.

    EDIT: Have you recorded a specific button to wake the HTPC? Flirc has two wake up modes. If you don't record a wake key then every key that is recorded in Flirc can wake the PC. You can also record a specific remote button to wake the PC and then only this single button will be able to do this. But then this button can't be used for anything else.

  18. Have you both tried if this also happens with different PC? You don't even need to install Flirc software there. Just make sure that Flirc is in working state, load your config or record some letters for testing, unplug Flirc and plug it into different PC and test in notepad for example if it works. Then do some reboots etc.

  19. There's a pin on the ATX connector that always has 5v available no matter what the power state is. It is required for proper ATX operation (turning on the board by power switch and always powered ports like USB on some motherboards).

    http://www.smpspowersupply.com/connector_atx_pinout.GIF

    As you can see it's the pink/violet colored pin named +5VSB (SB means stand by).

    There should only be a single ground in the whole system. You can take the ground connection from the ATX connector directly or you can leave it connected to USB header on the board.

    You can also look for some options in the BIOS as sometimes the USB power in S5 state is software controlled.

    SATA is not powered in power down state for sure. The only 100% sure source of power in this state is the +5VSB in the ATX connector.

×
×
  • Create New...