Jump to content
Flirc Forums

Search the Community

Showing results for 'SendIR command'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Flirc forums
    • Skip
    • Raspberry Pi Cases
    • Flirc USB
    • Flirc USB Gen1
    • Jeff Probe

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Interests

  1. Where is the command line documentation for Windows?
  2. Hi Jason, this evening I tried your suggestion with a WAKE command registered and I enabled the "sleep detection" and... I can confirm that this command works also from the full shutdown!!! I tried it without big hope because on the previous posts on this forum I was able oonly to get confirmation about wakeup from sleep S3 state and never about S5 state (Shutdown). Now I can confirm to everyone: with the new motherboards like the Asrock I have, FLIRC is able to completely Power ON and of course power OFF the PC!! This is perfect and lovely! Last improvement to become an amazing product would be to be able to program the same key for both Power ON and Power OFF, the current proposal requires a very complex procedure to emulate this feature. The post can be closed, now. Very good job! Thanks
  3. Hi Jason, Tel me how to create syntax in order to delete one of keys. I'm trying like that: C:\Program Files (x86)\Flirc>flirc_util.exe delete_index'16' [E] run_cmds(248): could not find command 'delete_index'16' It doesn't work. Here is my flirc_util settings: flirc_util version v1.2.3 [v1.2.3] Firmware: v2.4 Settings: sleep detection: Disabled noise canceler: Enabled inter-key delay: 3 state: 0 builtin profiles: Disable Memory Info: keys recorded: 32 keys remaining: 137 memory used: 23% Recorded Keys: Index hash key ----- --------- --- 0 65F8450 1 1 25D2475F 2 2 46EB8450 3 3 A562485F 4 4 C662485F 5 5 655E485F 6 6 8687D952 7 7 2513AF61 8 8 4613AF61 9 9 E55E8450 0 10 460CD99A up 11 65BF9B4B down 12 86B71F14 left 13 25B31F14 right 14 86BF9B4B return 15 46AB894B backspace 16 65B71F14 i 17 6708498 - 18 E5261F14 = 19 257BC215 t 20 6576B811 p 21 869FAF61 space 22 6FF9C61 x 23 C633C63C r 24 A5FA9C61 f 25 C6E38398 , 26 A5E38398 . 27 6484D90 / 28 A5120D14 pageup 29 C64B9C4B pagedown 30 E5474D90 w 31 C6948ADF c I want to remove line 16 ("info" button from my harmony). This button doesn't work. Nothing happens when I press it. When I assign "Info" button with flirc software there two info buttons (I dont know why). There is some conflict between default flirc xbmc from my harmony and builtin profile from Flirc.
  4. How does one go about setting up multiple profiles on the FLIRC and setting up a harmony button to switch between the two? Having a "watch MCE" button that fired off commands related to MCE and the same for XBMC would be ideal, but how would I tell the FLIRC to switch modes via an IR command?
  5. Hi there! I have an RTI dealer-programmed universal remote, which I'd love to use with Plex via FLIRC. The RTI communicates via RF to a controller box, which sends pre-entered IR codes via IR emitters placed on each component. When a command is entered on the remote, all of the IR emitters push the same signal to every component. To minimize interference (and my understanding is that this would apply to many dealer-configured universal remote setups), it would be great to specify non-assigned IR hex codes to map to keys. In other words, when I select 'shift+W', present me with a prompt to manually input an IR hex code, as opposed to simply activating FLIRC to listen for an IR signal (which relies on having a specific remote already). If this could be done, it would be a TREMENDOUS help for anyone planning on utilizing customized universal remotes. In any case - thank you for creating such a straight-forward solution to such a silly problem.
  6. This issue seems to be back around. I'm running a clean install of Mythbuntu 12.04.3 LTS. When I run Flirc (sudo or as myth-user), here's the results that I get: me@my-myth:~/Flirc-v1.2.2-x64$ ./Flirc ./Flirc: error while loading shared libraries: libQtSvg.so.4: cannot open shared object file: No such file or directory The results from lsusb: me@my-myth:~/Flirc-v1.2.2-x64$ lsusb Bus 002 Device 019: ID 20a0:0001 Clay Logic ... The results from flirc_util: me@my-myth:~/Flirc-v1.2.2-x64$ ./flirc_util version Warning: cannot open USB deviceWarning: cannot open USB devicedevice disconnected, can't run command Reading up on my issue, I tripped across a thread elsewhere where the person mentioned that the Flirc dongle & interface still worked on Win vX, so I tried it there & it worked. I was able to load some commands and save the profile. Plugging the Flirc back into the MythBuntu box produced no response; nothing at all. So what do I do about this to get Flirc (hardware and software) working on this MythTV box?
  7. I have used flirc across many computers, and I have never had any problems, untill upgrading my Ubuntu install from 12.10 to 13.04, and more recently to 13.10. All of the buttons are still functioning with their positions, and I am able to use Flirc from the command line. Has anyone experienced this, or knows how to fix it?
  8. Thank you for this great product. It would be great if the Flirc Harmony profile had both PowerOn and PowerOff commands and if the PowerOn command was mapped to the wake function on the Flirc.
  9. I executed the command as administrator but got an error: "Could not connect sessionID 0 to sessionname console, Error code 5 Error [5]:Access is denied.
  10. That's a really interesting find. Try the same command with sudo
  11. i'm having issue as well mostly using the directional arrows. making navigation through XBMC annoying. I upgraded to the latest release GUI and firmware. GUI 1.2.2 and Firmware V2.3. And I just tried running the command from the CLI to enable noise canceling and got this message: Warning: cannot open USB deviceenabling noise canceler any idea what that might mean?
  12. I had downloaded the right files for the right platform. But thanks to the last line of your last post ("$ sudo ./Flirc"), I realized that my user was not part of the "sudoers". So although the Flirc GUI program would start and say that the Flirc module was connected, there was no menu available. I remedied the problem with the following (in case someone else encounters the problem). Open the sudoers list by opening a root terminal window and using the visudo program to edit the list like so: # visudo Find the line that has "root ALL=(ALL:ALL) ALL" and copy it right below itself changing the word root to your username so it looks like below: # User privilege specification root ALL=(ALL:ALL) ALL username ALL=(ALL:ALL) ALL Now save your changes and restart the Flirc GUI program in a user terminal window with the command below. My desktop is KDE so I use "kdesudo". You might need to use "sudo" or "gksudo" for Gnome desktop, it depends on your system. $ kdesudo -u username ./Flic Once the program is started, click File -> Advanced -> then click the button "Force FW Upgrade". After a minute or so, "Firmware v2.3" will be displayed on the bottom left hand corner of the window. MrNice, I wish you a good life, you certainly made mine better today.
  13. Hmm. Which one would that be? Thank you for your help! I get the following commands: delete Delete next remote button flirc sees from saved database delete_index Delete button at index displayed in `flirc_util settings` dfu Kick in or out of Device Firmware Upgrade mode dump Dumps contents of eeprom to console format Remove all saved buttons from flirc help Show this help. Also try `help <command>` interkey_delay Test run command keys Shows the recorded remote keys and their pairings loadconfig Load configuration file from disk to flirc noise_canceler Noise canceler to prevent phantom presses normal Put flirc in normal user mode peek Peek EEPROM address profiles enable or disable built in profiles reboot Displays all the devices current settings record Record infrared buttons and link them to HID keys record_api Advanced button recording saveconfig Save configuration file to disk settings Displays all the devices current settings sleep_detect Turns on sleep/suspend detection space Displays information about the space used and remaining status Last Flirc Status upgrade Uploads new firmware image to flirc hardware version Print the application version and device version if connected wait Waits for the device to be plugged in (used for scripting)
  14. Hmm.. there is a CLI command for increasing sensitivity (unless it's been taken out recently). Have you tired re-programming flirc to see if it makes any difference?
  15. Thanks for the answer Chris! I have tried noise cancelling and it doesn't seem to change anything. No other devices either, but checking that was a good suggestion. I have a new theory though: At night we often roll up in blankets at this time of the year and I guess they will lessen the reflection of our surroundings. The funny thing is that sometimes the AVR blinks as it recognises a remote press (it does so even when it doesn't react, I use the directional keys for flirc which don't do anything for the AVR while not in a menu) and the Mac doesn't react, even when I'm right in front of the flirc. It seems to me that this happens when I don't press the button all the way down or at a slight angle. I tried to learn this "slight press" but it doesn't seem to give a different signal, flirc GUI says "button already learned" It's not too bad really. I just thought that I maybe missed some command for the CLI to increase sensitivity and was a bit surprised that the AVR picks the signal up more easily. Really love the Flirc and just wished I had found it before I spent weeks unsuccessfully trying to find a universal remote I liked.
  16. Well I fixed my own issue. I ran Flirc from the command line as root and it connected. I haven't tried it in my HTPC but at least it appears to work on my desktop
  17. ok so this is kinda specific android treatment for android devices where flirc is connected to!? Flirc receives the command a remote sends to it (e.g. "a") and flirc passes it through to the android device (like an ouya). The app acts as a "man in the middle" and "translates" the "a" key to "vol up"!?
  18. It's not easy to find a remote, which gives you full functionality for both devices without 1. to be a universal remote or 2. overlaps functionality and interfere the second device You can look for a dvd/ bd sony remote, which offers also tv functionality or vice versa. In both ways you will probalby not have full functionality for the second device on the remote (tv or dvd/bd) in most cases I know, that some older sony vcr remotes have some kind of mechanical switch to change the profile between vcr and tv, but they often are missing the navigation buttons (arrows) So the best solution for you seems to be an universal remote. There are cheap fancy ones, like one4all, which will grant you the best remote experience. As long as you have both devices in sight, using the same remote, you will always control these both devices with buttons/command related to both devices. There is no way to avoid this. In my case, i use a silver ATV remote to control my xbmc. Small, sleek design and functional. For enhanced commands like info, context menu, zoom etc. i'm using unused buttons from my tv remote, as long, as the long press feature is not implemented yet.
  19. do you guys have sleep detect enabled in the GUI? Also, make sure you haven't recorded any noise. use the commandline, flirc_util settings. Look for duplicates. Delete all duplicates and re-record those keys. When receiving a signal, flirc will send a character to the machine. Regardless of the state of the machine. Sleep detect tells flirc to check if the computer is sleeping. If it is sleeping, do not send any keys unless it's the 'wake-up' command. Further, if you don't have sleep detect, and have recorded erroneous noise, then the machine will see noise as a false signal, and send a command to the computer. ** EDIT ** TLDR; enable sleep detect in the gui
  20. So you're using a wmc (ir6) compliant profile with your harmony? Did you mapped every button twice? this is necessary,due to the wmc protocol sends a second command on every second keypress.
  21. Yes it's possible with either the GUI and the command line. It's under the file menu in the GUI.
  22. I found 2 old remotes saved from bin few years ago. Both have Play and Pause buttons separately. Both have the same behaviour; - Play with the first press Play button and play again from beginning with the second press. - Toggle file view/play list with Pause button - Stop paying with Stop button When a button is recorded with the xbmc profile then we con go to the keyboard profile and press recorded remote buttons, then key turn green according to the remote button pressed. So Play button sends p key Pause sends space bar Stop sends x key sudo ./flirc_util keys allows to check that as well. ($ sudo ./flirc_util settings as well) Could you run it and post please? I don't have a USB keyboard to compare when press p or space bar. BTW: I just note that my request in the other thread " Keyboard key (action) mapped to more than 1 remote key" is implemented. If you have more than 1 remote or 1 remote with more than 1 profile, you don't need to delete the previous record for one button to record a new button code to the same key (action). Not easy to explain. For example, you record Play button from the remote 1 with the xbmx profile, > is green. You can record the Play button from the remote 2 with the xbmc profile, > will be green as well. Look at the CLI command: $ sudo ./flirc_util keys Recorded Keys: Index hash key ----- --------- --- 1 9D6C74B0 tab 2 5F5A4B9D home 3 5B1B6912 escape 4 5B06EC4E x 5 9DC159A3 c 6 5B68E519 up 7 1917DA7B left 8 99BE5F32 right 9 5729038F down 10 5BAC361F return 11 99298E70 backspace 12 5F7C2097 , 13 5F386CE9 . 14 9D7D089E pageup 15 9D7D6728 pagedown 16 1D89F0E4 i 17 5BF9F14B / 18 5FF41AE4 p 19 8096252F p 20 862411 space 21 6104EE71 p 22 61C0603E space 23 61040FBF x I have 3 p keys, 2 space and 2 x. This is what I was saying in the other thread.
  23. Sorry for abcence, was busy. You're right. The behaviour depends only on the app. So as long as the app reacts on common keyboard commands, it will also respond to flirc, as long as the command is related to the corresponding keystroke.
  24. Hi, This is an idea, not very important for me right now but could be convenient. Let say you have a usual remote for some devices. At the top of the remote you have few keys to choose the device to send the beam: TV, DVD, SAT, PLAYER, AUX... First you press the device key and then press the action key to the selected device. What is the purpose of the play, pause, fast forward, etc when you select TV? Nothing. When you select PLAYEUR key the above keys are used to the right action for the player and mapped. Note the codes are not the same when device selected is TV or PLAYER. It could be usefull to map the play, pause, fast forward, etc to command the player with the both selected devices TV and PLAYER for example. So, to be able to map 2 or (more ?) remote keys (different codes) to 1 keyboard key (action). What do you think?
  25. For several weeks I'm now trying to get my Flirc to work with my Ouya, but without luck. I followed and tried various other things, but can't get a single remote command to work when Flirc is connected to the Ouya. I can safely assume that the USB port on the Ouya is working, as any memory stick, USB mouse or cable based USB keyboard works - any USB device I connect works on the Ouya. My Harmony One works with all other devices and send proper IR commands. I used the profile "Flirc > XBMC" for my activity I program the Flirc through a Mac. Using flirc_util, I get following output after a "fresh" install of the flirc: sh-3.2# ./flirc_util version Flirc Version v1.2.2 [v1.2.2] 2.3 01-25-2014 [0x3DB4D4F3] sh-3.2# ./flirc_util settings Settings: sleep detection: Disabled noise canceler: Disabled inter-key delay: 6 state: 0 builtin profiles: Enable Memory Info: keys recorded: 13 keys remaining: 156 memory used: 8% Recorded Keys: Index hash key ----- --------- --- 0 46AB894B escape 1 6576B811 F3 2 869FAF61 F4 3 6FF9C61 F5 4 C633C63C F6 5 C6E38398 F7 6 A5E38398 F8 7 A5FA9C61 F9 8 86BF9B4B home 9 86B71F14 left 10 25B31F14 right 11 65BF9B4B down 12 460CD99A up When I take the flirc and connect to a PC for example, it works. I can control a slide show and do other simple things using my Harmony. When I connect the flirc to my Ouya, nothing works. And whenever I had it connected to the Ouya, it seems to "loose its memory": When I connect it back to my Mac the flirc_util now shows: sh-3.2# ./flirc_util settings Settings: sleep detection: NA noise canceler: NA inter-key delay: NA state: 0 builtin profiles: NA Device currently in bootloader I tried this a few times, and can reproduce it consistently... Starting the flirc software on my Mac will re-program the flirc with fresh firmware and proper profile. Plug it into Ouya - everything gets lost... Does this sound like a hardware problem of my Flirc?
×
×
  • Create New...