Jump to content
Flirc Forums

yawor

Administrators
  • Content Count

    993
  • Joined

  • Last visited

  • Days Won

    69

Everything posted by yawor

  1. yawor

    QNAP RM-IR004 Remote?

    This remote seems to use MCE protocol. I've analysed all the buttons and I couldn't find any issues with the signals. They all decoded correctly. Flirc v2 shouldn't have any issues with MCE. Go to Advanced settings in Flirc GUI and disable all built in profiles. MCE protocol uses a toggle bit, which means if you press the same button two times in a row, the remote is going to send two slightly different signals. So to properly record your remote, you need to record each button twice in a row - select the same function in the GUI the second time to have both signal variants assigned to the same function.
  2. Short answer: no. As you've mentioned it yourself, Flirc uses USB HID, so something on the system needs to be able to support specific usage page and translate HID codes into some action. To send Android Keycode directly, Flirc would need to implement whole ADB protocol to be able to speak to ADB on the device and execute shell commands on it. Can you even use ADB on the device in USB host mode? Flirc is an USB device, so anything you plug it into needs to work as USB host.
  3. yawor

    Flirc Raspberry Pi 3 Case with Odroid C2

    @GuiBacon is your reply related to Flirc Raspberry Pi case in any way? Because it's hard to understand what do you mean in the context of this thread.
  4. Did you use the same USB cable to the hub before and after moving the HTPC? Interference issues may be hard to handle. Is all your equipment properly grounded? This includes a ground connection in your mains socket, extension cords/power strips etc. Maybe that's an electrical issue, some EM interference. Some people had some problems with the older 1st gen Flirc, when their equipment wasn't grounded and properly grounding the installation helped resolving the problems. There were no such issues with 2nd gen but may still be possible.
  5. Hi, Flirc v2 has a built in support for MCE remote, but it's not a direct replacement for the original MCE receiver. Flirc is seen as an USB keyboard in the system. That means that for Flirc to work with some software, it needs to know how to map a button press on the remote to some keyboard function or letter. As I mentioned above, Flirc has a built-in profile for MCE remotes and it should at least do something in the Kodi or notepad, but it's not meant to use with Kodi. You can try following. In the Flirc GUI, go to Advanced settings and actually disable available built-in profiles then close advanced settings dialog. In the GUI's menu select Controllers and Full keyboard. Click some letter (for example A) on a virtual keyboard in the Flirc program - it should ask you to press a button on the remote. So press one of the buttons - but don't just quickly press and release, it's better to hold the button until the message disappears. Then do a test in the notepad. Press the same button you've recorded few times when the notepad window is active. It should print the letter a. If you followed everything above then probably letter a is only showing every other press on the remote. That's because MCE IR protocol changes signal a little between every other key press (it has a toggle bit). This means that you should actually repeat programming two times for each remote button in the GUI (for example, click on Up Arrow in the GUI, press Up button on the remote, click on Up Arrow again, and again press the button).
  6. yawor

    Testing key Presses On Windows

    Ah, that makes sense. I thought you were talking about Xbox controller as in gamepad, not a remote control.
  7. Hi, Ad 1) It should. But you need to have that remote to first teach your Flirc to respond to its buttons. Keep in mind that there are some remotes which don't work well with Flirc, so first do some tests to be sure that the remote itself works correctly before configuring your Alexa device. Ad 2) You can use as many Flircs as you want with a single PC (or at least as many as the number of USB ports :)). These behave just like standard USB keyboard and you can use multiple keyboards without issues. Things to remember: - If you're using Harmony remote and built-in profiles, then make sure that only a single Flirc has built-in profiles enabled (in GUI in Advanced settings). 1st generation of Flirc (original USB one in clear plastic and Flirc SE) can only turn on/off all built-in profiles at once. 2nd generation Flirc can enable/disable specific profiles. If you don't use harmony, then just turn off all built-in profiles in all Flircs you use just to be sure. - You can't have multiple Flircs connected during programming/configuration (GUI or command line tool). To program each of your Flircs you should disconnect all other on that PC. - When programming your Flircs, be sure not to program the same buttons on the remote to multiple ones. If you do that, then all (programmed) Flircs will react to the button press and may send conflicting key presses to the system.
  8. yawor

    Testing key Presses On Windows

    Hi, Do I understand correctly that you're trying to use Xbox One controller with Flirc? Flirc is an IR control receiver. Xbox One controller uses RF connection (custom Microsoft RF protocol, unless you have newer Xbox One S controller, then it also has Bluetooth). Can you describe your setup in more details?
  9. Sorry, I've never used one. Just search for some IrDA USB dongle/adapter. Just make sure it's for data connection, not something for remote control which was improperly named IrDA, as that's totally different hardware.
  10. Hi, No, it can't work as an IRDA. You need a proper serial IRDA interface for that.
  11. yawor

    flirc = sign is sent by flirc in error

    Please save your configuration into a file (in Flirc GUI) and post it here.
  12. There's no default config. Flirc always comes with empty configuration. There are built-in profiles (for the Harmony remotes) but as the name implies, they are built into the firmware and they don't take any space in the configuration area.
  13. yawor

    "erase" Does Not Work

    To erase you need to press a button on the remote which was previously recorded, not a button in the Flirc GUI.
  14. yawor

    Macro Questions

    I think it should be followed by multiple record_macro calls. But I don't have a way to check it right now.
  15. yawor

    Harmony 650, Ubuntu, NUC

    You need to play around the Ubuntu settings. System sees Flirc as a keyboard so you need to adjust the keyboard settings. I can't help you with Ubuntu specific settings as I don't have any machine with it.
  16. Sorry. There's no pause feature. The keys in the macro are called sequentially as fast as possible. Regarding applying the modifiers to arbitrary keys when recording macro or long press, unfortunately there's currently no way to do that. The way these commands work right now, the modifier key is applied automatically when you record a sign which is achieved by using the modifier (so for example, if you run flirc_util record_macro A, then the util will translate this to shift + a).
  17. yawor

    Control TV Volume w/Flirc

    Do I understand correctly, that you want to control other devices from HTPC with Flirc plugged in? If yes, then it's possible with Flirc v2 (the metal one) as it has IR blaster diode built-in. The command line tool flirc_util (you install it together with Flirc configuration software) has a send_ir_raw command, which takes raw IR data formatted as a series of comma-separated values (times in microseconds) and transmits the signal using the IR blaster LED in the Flirc. But you need to take some things into account: There IR LED is not very strong. It may require a direct line of sight between the Flirc's IR window side and the other hardware's IR receiver window. It may depend on the sensitivity of the receiver in the hardware you want to control. There's no built-in automation for transmitting. The Flirc's main focus is still on controlling the PC (or other USB Host hardware) to which the Flirc is connected. This means that you can't configure the IR signal to be automatically transmitted by the Flirc itself in response to a different IR signal. You need some kind of software or scripting on your HTPC, which will call the flirc_util command line with correct IR data. If you use Windows, then software like EventGhost or AutoHotKey should be able to do that. The IR control is prone to interference if more than one IR transmitter is sending control signals at the same time. For example, if you want Flirc to send a command to your TV when you press a button on your HTPC remote, then there's a high probability that both signals (from the Flirc and from the remote) will interfere with each other causing the TV not to recognise the signal from Flirc. This is the same situation as when you'd try to use two different remotes, pressing buttons on them at the same time. IR remote control doesn't have any mechanism for collision detection or avoidance. So to sum it up, it's possible, but the usability may vary depending on your needs and hardware.
  18. yawor

    Flirc will not control fire tv

    Have you made any changes to the Android configuration in the meantime, like turning on the USB debugging for example? Flirc (or any USB device for that matter) won't work with USB debugging turned on.
  19. yawor

    Flirc on an RV

    Ah yes. You need an OTG Y-cable - it has a full USB Type-A socket and both MicroUSB plug and socket, so you can still connect the power supply.
  20. yawor

    Flirc on an RV

    You need to use an OTG cable to connect Flirc to your FireTV Stick. The OTG cable goes into the MicroUSB port on the FireTV stick and gives you a full USB Type-A socket. Be sure to buy an OTG cable which is compatible with the FireTV Stick (I don't know if they're all compatible or not).
  21. yawor

    Cant get macros to work properly

    OK, it's like I've said before. The signal you've recorded is using an RC6 protocol. It is an IR control protocol created by Philips. Actually Microsoft's MCE protocol is based on RC6 (it's in the same family). I've decoded the signal. It toggles between: - protocol = RC6, device = 0, obc = 10, misc = T=0 - protocol = RC6, device = 0, obc = 10, misc = T=1 As you can see the T param (from toggle) changes between 0 and 1. This causes the waveform of the signal to change slightly and it's recognised by Flirc as two different buttons. So either you need to use the setup code on your remote or find some non-RC6 remote to learn from. The brands I've mentioned before are a good candidate because there's a high possibility that they are using a NEC family protocol, which works really well with Flirc.
  22. yawor

    Cant get macros to work properly

    Open the Flirc GUI application and go to File menu and select Device Log. In the Log window, check "Enable IR Debugging". Then press few times the button on the remote that you're trying to set the macro on. Then disable the IR Debugging and save the log to file and post it here.
  23. yawor

    Cant get macros to work properly

    No, you record the same remote button twice. First time you need to use record with a key that you want as a 1st in a macro (for example F10). Then you do (for example) record_macro F11 and then press the same remote button as for the F10. The record_macro command adds another keyboard key on top of already recorded ones for the same remote button. BTW I usually differentiate between keyboard and remote like this:keys on the keyboard -> keys (or keyboard keys); keys on the remote -> buttons (or remote buttons). As for the remote setup, I'm not 100% sure as I don't have this model. I have few remotes from the UEI (a company behind the One For All brand) and they all share some features, but this one seems to be quite unusual. Anyway, according to the manual, the remote supports up to 3 physical devices and assigns buttons by color to these devices (third one is an audio device and overrides the volume buttons). You should read through the manual to fully understand what your remote is capable of. Setup codes set specific part of the remote, not just a single button. Even if you set your remote using the setup codes from the book, you can always overwrite specific buttons by recording a signal from another remote. Recorded signals take precedence before an original function.
  24. yawor

    Cant get macros to work properly

    I think it would be much better if you used a code entry method to set your remote. I've checked the quick setup guide for the URC-6810 and it is possible (it uses some keys as numbers when you enter a setup code). You should also have a code book included in the manual for the remote. If you don't have the manual, then it can be downloaded (together with the code book) from the OneForAll website. If you want to try this approach, then select an equipment brand you don't have any hardware from. For example, if you don't have anything from LG, then use codes for LG hardware. I'd suggest one of these: LG, Samsung, Panasonic. You can try multiple codes to find one that works best for you. Regarding the commands you've listed, using record command second time with the same remote button should exit with an error, that the button is already recorded. To create a macro, first use a record command like you've done, but then add another key to the macro using record_macro command.
  25. yawor

    Cant get macros to work properly

    OK, so what's the setup code for the device you're using for Flirc? Did you set it up as an MCE remote? The MCE protocol (and some others too) uses a toggle bit in the signal, which toggles on each key press. This means if you press the same button two times then each time the signal sent is going to be a little different. Flirc sees these signals as two different ones. So you actually didn't create a macro, but you've recorded F10 for one variant of the signal and F11 for the second one. I think the best approach would be to reconfigure your remote to use something else than MCE. Possibly something without a toggle bit. BTW are you using a RemoteMaster software to modify your remote's settings?
×