Search the Community
Showing results for tags 'doa'.
I don't know if I'm doing something (or have done something) wrong or if my Flirc device is simply defective. I've looked at a bunch of the FAQs and various Forum posts and found lots of semi-relevant stuff, but no clear answers to my Flirc problem(s), so I decided it was best to start a new topic and explain things from the beginning... I just bought a Flirc-USB to use with a HarmonyOne remote and a FireTV box. As I understood (or misunderstood?) the Flirc website, the Flirc-USB should work straight out of package for my setup (w/no Flirc custom programming) by setting up Harmony Device using its programming tool,choosing Flirc under Media Center, and thennaming it Kodi or XBMC (not clear if name choice is even important).However, when I loaded the new programming into the HarmonyOne and tried to control FireTV, nothing would happen. I next tried using the Flirc GUI (v1.4.4) on Windows 7 Pro/64-bit. After fighting through some of the problems others have also had with getting things the GUI up and running (such as keyboard and mouse going dead), the GUI seems to communicate with the Flirc-USB because it understands when the Flirc is plugged into a USB port and – using Force FW Upgrade under File>Advanced – it claimed to upgrade the Flirc's firmware from version 3.6 to 3.8. (I should mention that along the way, I also tried some of the stuff above and below on a Windows 10 computer.) Yet, when I tried to program a key, the GUI gave no indication that programming was working... the selected key just kept flashing after I pressed a button on the remote. I tried different keys and different remote buttons (even under different Controllers choices) and none gave any feedback to indicate that programming was working. When I'd re-click the key on the GUI with my mouse (or choose a different key), it would say "Recording stopped," but there was certainly no visual feedback to show it was seeing the button-presses on the remote. Then (not thinking it might be a destructive step) I decided I'd better erase anything I'd done and start over, so I used File>Clear Configuration. It wasn't until then that I started wondering "maybe the GUI isn't designed to provide feedback that a button has been pressed?" If that was the case, perhaps programming actually was working? I tried to test that possibility by... saving a configuration file,programming a few more keys (or at least trying to),saving a second configuration file, and thencomparing the two files (in a couple of different ways).There was no difference between the two files and both were only 5-bytes long. When I saw how small the files were, I realized the Clear Configuration I'd done might have been destructive and that the built in Controller profiles might be gone. So, QUESTION#1 is do I need to do something to restore the Flirc to factory defaults? Even if Clear Configuration was destructive, the programming of keys using the GUI doesn't seem to be doing anything, so something very basic seems to be wrong. QUESTION#2a: What is the correct behavior of Flirc programming GUI: Should I be able to see visual feedback when I press remote button? QUESTION#2b: If there isn't visual feedback, what's the easiest or most definitive way to tell if it's working? QUESTION#3: How can I best test if my Flirc-USB is defective? And, the main question, of course, is where can I find the most complete guidance for a Flirc novice on getting up and running with the combination of hardware I described?