Jump to content
Flirc Forums

yawor

Administrators
  • Posts

    1,003
  • Joined

  • Last visited

  • Days Won

    74

Posts posted by yawor

  1. Hi,

     

    Probably a protocol the remote uses is not compatible with Flirc. There is a possibility that it can be made compatible but only Jason can tell that.

     

    But there is at least one thing you can try yourself. What was the distance between the remote and Flirc when you were recording buttons? If it's too close then there may be some problems as the signal from remote may be too strong.

  2. Hi,

     

    It's not true that the config is being wiped when upgrading firmware. Either you have a faulty Flirc unit or you've somehow cleared the config yourself. I don't remember anyone reporting such issue.

     

    As for the Harmony, it's true that those are extremely common, but that doesn't mean they are superior in every aspect. Unfortunately most of them don't have enough CPU power for their functionality and are slow compared to dedicated remotes and simpler universal ones - this was one of the reasons I've resigned from buying one.

     

    There is no documentation on reverting the firmware as it is not officially supported. If you really need to go back, then Jason can guide you through.

     

    I tried setting this to 0 in Harmony, as well as setting interkey to 5 in Flirc, and unfortunately it does not have any effect with my Harmony 550 using Media Center PC profile. It basically ignores every other key press.

     

    There were a lot of discussions on the forum (and I think it is now in the Knowledge base here https://flirc.zendesk.com/hc/en-us) on how MCE remotes operate. Please read this article https://flirc.zendesk.com/hc/en-us/articles/201054238-Every-Second-Key-Press-Doesn-t-Work

    • Like 1
  3. Everything is recorded and stored in the Flirc itself. You can use flirc_util.exe delete to delete keys you are unsure of. There is no easy way of displaying recorded keys when you are using my method. You can just save the config and figure out what is already recorded by checking its content in HEX editor. You just need to skip first 5 bytes and after that each mapping has 6 bytes - first 4 is hash of IR signal, then 1 byte modifier (in normal keyboard mode) or key code (in table 12 mode), then 1 byte key code (in normal keyboard code) or 0x66 for table 12 mode.

  4. Is the GUI working normally and the problem is only with command line util? Are you sure you are using full file name of the exec file: flirc_util.exe, not just flirc_util? Some people are having a problem like you described when they try to execute command line commands which shortened exec name (without .exe). I've also experienced it but I don't have any problems when using full exec file name.

  5. I installed your modified HID plugin into EventGhost. In the plugin configuration, there are 2 flirc devices. I was thinking that with the plugin installed and with the correct flirc dfevice selected, I would be able to see the remote keys show up in eventghost.  I tried both flirc devices listed but I don't see anything show up in Eventghost. Am I missing a step?

    Looking forward to using the plugin

    Ian

     

    Did you record the keys the way I've described using flirc_util record_api? It is a required step, because you can't catch normal keyboard keys using this method. To do a quick test you can record one of the multimedia keys in the GUI - it should show up in EG if correct flirc device is selected in plugin's configuration.

  6. I just purchased the Flirc for my PS4.  I plugged it into my laptop and installed the software under Win 7.  I was able to run the GUI to program it, but from the command line I get no response when trying to run "flirc_util record pause". It just returns immediately to command prompt.  I tried reboot as well as unplugging dongle and plugging it back in.

     

    Any help?

     

    This is some problem with Windows' cmd shell application. I also have this problem. You can fix this by using full file name: flirc_util.exe instead of just flirc_util.

    • Like 1
  7. Videonisse,

     

    It will be corrected sooner or later, but there are currently other problems Jason is working on right now (ones that can't be corrected by users themselves) and he is asking for patience. I know that it may be frustrating. It may be easy to correct those keys in the built-in profile, but on the other hand it IS also easy to just disable built-in profiles in Flirc and map correct buttons yourself. You don't even need to change the profile in the Harmony remote - just use Flirc GUI to remap the functions using XBMC or, even better, Keyboard controller.

     

    BTW I'm not sure why you think that up and down arrows should use Page Up and Page Down keys instead of Up and Down. How would you want to move 1 position up/down at a time in the list?

    • Like 1
  8. Yawor,

     

    Thanks for your advice however i do have limitations with the harmony hub as it will only send out the commands its been programmed for using its profile. The smart remote i think only communicates with the hub using RF protocols and it's the Hub itself that sends out a IR signal or Bluetooth signal for the playstation3. So it looks like for me to get the extra keys that i want to use i will need to program the Harmony Hub with the new values by using some existing remote and then go back and map flirc using the updated command with the mapped Smart Remote. I could always use a spare remote and program flirc with it for additional stuff, but that then defeats the purpose of using the Harmony setup with just one remote.

     

    Now are there any specific types of remotes i should not use for creating these custom commands with the harmony so that there is no  confusion and or overlapping between different devices i have?

     

    I don't know what can you do with the Harmony itself as I don't own one. If you are able to set up additional codes by yourself (even from a different profile) then you should be OK. If not then you can always change the profile to a totally different one which has enough buttons for you to map them in Flirc to everything you want.

     

    You can use almost any type of remote for extra commands, but there are some issues with some. For example RC6 protocol used by most MCE remotes uses alternating IR signal for each button - this requires recording each button at least two times to catch every signal for a single button. I like to use remotes which use NEC family protocols. I also prefer TV profiles as they usually have a lot of buttons - but remember to use a different manufacturer than the one you have your TV from. For example I have my remote set to some new Samsung TV and everything works like a charm. LG TVs also use NEC protocol, and probably some Panasonic ones too.

  9. Hi again,

     

    Flirc holds a simple mapping in its EEPROM, where it maps a value representing an IR signal from the remote onto the keyboard key (+ possible modifiers). Of course it also has a built-in profile for XBMC in its firmware, but it's the same thing as the mapping in EEPROM except it is not changeable by the user (it's hardcoded and only Jason can make changes to it by releasing new firmware versions). The built-in profile is a basic one, so if you want to get more from Flirc you need to build your own mappings from scratch.

     

    Changing the controllers in Flirc GUI has no effect at all on the Flirc stored config by itself. Actions that make changes to Flirc are: recording a button, deleting a button, making changes in Advanced options, clearing configuration (its like a format) and loading configuration (loads config from previously backed up one using save configuration).

    The GUI has multiple controllers but they are interchangeable, at least with the keyboard controller. They are just a simplified views with predefined key bindings - for example a Back key on XBMC controller is mapped to a backspace button. You can switch the controller at any time and record a button from it at any time. It'll just be added to the mapping. You can check that by recording a Back key on XBMC controller then go to Keyboard controller and press recorded button - the backspace key should light up.

     

    Now if you want to add more buttons to your config then I think it would be best to start from scratch. You can disable built-in profile by unticking the Built-in profiles option in Advanced options. After that you are free to map any button on the remote to any keyboard key combination (key + modifiers) you want. If you know what keys are used by XBMC/Kodi then you can just use the Keyboard controller to map its functions to remote buttons (personally my preferred way - XBMC controller is not 100% accurate). Just click a key in the GUI you want to map (if you want to add modifier you need to click them before the button) and when app ask you to press a button, press one on the remote and that's all.

     

    If you have any further questions don't hesitate to ask.

  10. Hi,

     

    I use the MythTV PVR plugin within KODI, and when browsing the EPG i usually use the 'record' button on my remote to schedule a recording of a TV listing.

     

    I'm not sure I understand you correctly. You are saying that you usually use record button to schedule the recording but at the same time you say that you can't find the record button. Do you have another IR receiver which allows you to use the record button?

     

    I don't use the TV functionality in Kodi, so I don't know key bindings for this context. You should be able to find them in Kodi documentation. Maybe Kodi has some key binding to set the schedule - if yes then you just need to record the "record" button on the remote for this key combination on Keyboard controller in GUI.

  11. I think the most important information here is that you don't need to save anything into Flirc. All the configuration is stored directly in Flirc and all changes (like recording new button) are stored on the fly in its EEPROM memory.

     

    Chris, there is an info on "What is Flirc" page (the first link you've pasted) about this but I think it's missing that info that every change in Flirc GUI/CLI is being made on the device right away and no saving is needed.

  12. Correcting XBMC/Kodi profile doesn't require changing anything on the Harmony side (unless some new buttons would need to be added). On the other hand to add new built-in profile (for example for WMC) Logitech would need to add new profile to the Harmony as well. I don't know if there is some open way to request a new Harmony profile to be added by Logitech or how Flirc/XBMC profile has been requested in the first place.

  13. Hi,

     

    This keyboard uses RF (Radio Frequency) as a transmission medium. Flirc can only receive IR (Infrared) signals. There is nothing you can do for this keyboard to work with Flirc. If you want to have free USB ports and plug in both Flirc and RF receiver then you need to buy an USB hub. Those come as either unpowered (take power from host's USB port) or powered (have their own power supply so you can plug more power hungry devices to it).

  14. It all depends on personal needs. One person likes to use multiple remotes, but another likes to use a single one. If you can use multiple remotes then find a remote for a hardware you don't have (or don't use anymore) that won't interfere with your current hardware and pair it with the Flirc. If you want to use a single remote then either use keys unused by your hardware (like TV, DVR etc) on a original dedicated remote or use an universal one that can handle all your hardware and Flirc. Personally I like the last option.

     

    I have a OneForAll Simple 4 remote (URC-6440) which can be configured by connecting it to a PC using USB cable. You can then use official http://simpleset.com/ website (you upload remote's config there) or you can use RemoteMaster software created by community on http://hifi-remote.com/forums/.

     

    On the other hand Logitech Harmony are probably the most popular remotes on this forum.

  15. It's not really a good idea to use a remote with Flirc that's dedicated for some other hardware you have, especially when both (Flirc and the device) can receive the signal at the same time, unless the remote has some universal remote capability. For example some remotes for DVD or Bluray players can be set to also control the TV. If you really want to control both TV and computer with Flirc with a single remote then I strongly recommend buying some universal remote. There are many cool and really configurable remotes out there (check out the Logitech Harmony or OneForAll remotes).

  16. I like the idea of a built in profile to help it be more plug and play for some users, but i see Yawor's point.  It might be nice to have the option of choosing or unselecting some profiles and adding others.  If that's "built in" or "user made" or a combination I think the flexibility would be nice if it's something that could be programmed in.

     

    I would need to find my previous post with that proposition because I had some more extended ideas, but about the plug&play ability so a user can just plug Flirc into USB, set Harmony to correct profile and be ready to go without even once running Flirc GUI, I had an idea that the Flirc could be already shipped with EEPROM pre-programmed with a few standard profiles (like current XBMC, but instead it being hardcoded in the firmware it would be contained in EEPROM so it could be even erased and replaced by the user). To upgrade Flirc to a newer firmware a user need to install and run Flirc software anyway so he/she then can also load one or more predefined profiles (as long as free space in EEPROM allows that). I know that this is a very big change but I think it's at least worth of consideration :).

  17. I know that this is Jason's decision in the end but I'm not very fond of built-in profiles. Not because I don't have Harmony and this is has no use for me (I would be able to create Harmony compatible device upgrade for my remote if I wanted to). They may seem like a good idea, but in the long run they make the maintenance harder. Also you need to keep in touch with Logitech if some changes are needed. Each built-in profile also takes up space in microcontroller's Flash memory (at least I think they are in the Flash, not in the EEPROM like normally recorded buttons) which is rather precious in case of Flirc because the firmware is also stored there and not having enough will block ability to maybe add some cool features in the future.

     

    I've already proposed this once, but I'll just mention this here quickly. Better than hardcoding a built-in profiles locked for specific remote series it would be better to provide pre-configured profiles stored in files (possibly in human readable format so anyone could create their own) and an option in Flirc GUI/CLI to upload selected profile into Flirc EEPROM. This could lead to opening a profile repository sometime in the future where anyone could submit their own profiles for others to use or submit fixes to existing ones.

  18. Raspberry Pi doesn't support power state management. It's either powered on (power plugged in) or off (power unplugged). You can of course shut down the operating system, but this doesn't mean that the Pi no longer takes the power, because it still does.

     

    There are external projects that try to add this capability to the Pi. For example this one http://spellfoundry.com/products/sleepy-pi/ but the price is not very tempting. Also you still couldn't power on the Pi using USB version of Flirc with this extra board. You would need to buy Flirc-SE (Streacom Edition), which has extra pins to power on a PC from any power state.

     

    You need to analyze if it's worth the price. The Pi doesn't consume much power. According to FAQ on the RPi website it draws current from 0.7A to 1A on 5V. Lets assume that it is 1A. The Pi uses 5 watts of power. 5 W * 24 hours * 31 days = 3.7 kWh (kilowatthours). Lets round it up to 4kWh. I don't know what is the price of electric power where you live but I pay about 15 cents per 1kWh where I live. This means that I would pay about 60 cents per month for running the Raspberry Pi constantly. OK power supplies don't have a 100% efficiency, so lets make it even $1 per month.

    Now take the amount of cash you would need to spend on the hardware to make the power on/off work:

    External board - £30.83 =~ $47
    Flirc-SE (I couldn't find a price quickly so I'll assume normal Flirc price) - $23
    It sums up to $70 I'll leave out the shipping and taxes out for this calculation.
     
    Given the total cost of hardware divided by monthly cost of running Pi all the time (70/1) you get that you can run the Pi for 70 months (almost 6 years) all the time to get to the price point of buying hardware to not run it constantly :) (and remember I didn't include taxes and shipping costs). I don't know how often you use your Pi but assuming its at least a few hours per week the time to recover the cost of buying the hardware would be even longer than those calculated 70 months. I think that sometime in those 6 years of time you'll get some other hardware for your media center.
  19. Fire TV remote doesn't use InfraRed to send commands and can't be used with Flirc. The remote uses Bluetooth as a communication protocol but I don't know if it can be paired to a PC with Bluetooth module.

     

    You can use Flirc plugged into the FireTV device and use other remotes (like Harmony or other universal ones) to control the FireTV.

×
×
  • Create New...