Search the Community
Showing results for tags 'disconnected'.
Found 4 results
Hi, Just bought the FLIRC. Tried to install it on Windows 10. The FLIRC shows up as Keyboard under the "Bluetooth and other devices". But it did not show up in the Device Manager. I had to use to Zadig to make it even appear there. But the Device Manager shows both flirc 0 and flirc 1 under "libusbK" Devices. I have also provided the log. States that the HID-device can not be found (AFAICS). Anyone knows what to do? Cheers, Markus flirc_log.txt
jonascj posted a topic in General QuestionsHi all I have a Flirc SE (for the Streacom cases). On my current OS installation I can't get the Flirc GUI to recognize the Flirc board as connected. It always says "disconnected :(". This is regardless of whether or not I run it as root. The flirc_util happily programs the Flirc board, i.e. "flirc_util record up" works and records a key for the "up arrow"-keypress (and this keybinding works afterwards). This is without running flirc_util as root. It gets a bit bothersome to record keys with the flirc_util, so how should I get the GUI to recognize that the Flirc board is connected? My current OS is Ubuntu 16 daily 64bit, and my Flirc board is running firmware 3.8 flashed from Windows. The current x64 linux Flirc GUI and flirc_util is 1.3.6 (we need the newer version, please, http://forum.flirc.tv/index.php?/topic/2200-latest-firmware-on-ubuntu-x64/). I've seen this post about udev rules http://forum.flirc.tv/index.php?/topic/579-warningcannot-open-usb-device-on-linux/ , but with this version (1.3.6) there is already /etc/udev/rules.d/99-flirc.rules in place which contains the rules outlined in that post... Any suggestions?
I am unable to get the Flirc GUI to recognize the dongle on my HTPC. When I try to map the keys, the GUI asks me to "Please connect flirc" and displays the disconnected Flirc face. I have tried plugging Flirc into both USB 3 and USB 2 ports, but neither change the outcome. Flirc is recognized in the Device Manager, but a second (new) device under "Keyboards" does not appear when the dongle is plugged in (see first attached image); the HID Keyboard Device listed is that of my actual USB keyboard/mouse - not the Flirc. What's weird is that Flirc is recognized as an HID Keyboard Device in the "Devices and Printers" screen (see second attached image). I have also tried the zadig method (), which did not work for me, and finally tried running the application as Administrator, as someone else had suggested, but the GUI still asks me to connect the Flirc. Here are the specs for my HTPC: - Windows 7 Pro x64 - ASRock FM288M Extreme+ (Motherboard) - Flirc v1.2.7 I was able to plug in Flirc to another computer (Windows 7 Home Premium x64 and different motherboard) and it connected without any problems. I mapped the basic buttons on this second computer, plugged it into Computer 1 (my HTPC) and the device became unresponsive. Any help would be greatly appreciated!
Hello, I have a few problems with my FLIRC, using the GUI 1.2.2 on Win 7 x86_64: Whenever I start the GUI, I see "Disconnected" in the status. If I unplug and replug the FLIRC in a USB port that was not used in the past for it, the driver installs and it get recognized by the GUI. When recognized, I can (could, since I used all my USB ports in the meantime...) define key mapping using the GUI. I tried to update the firmware using the "Advanced>Force FW Update" menu, but this caused the GUI to hang each time (after it discovered a new version and I clicked to proceed). Even if the GUI does not recognize the FLIRC, it appears in the Device manager Zadig indicates the correct driver for FLIRC (interface 1): libusbK v18.104.22.168 The GUI indicates firmware v-16.-16 when I manage to get it to work. I already tried several installations of the GUI (including older versions) as well as uninstalling the device in Device Manager but to no avail. Any clue on how I could upgrade the FW and get the GUI to work in a more predictable way? Thanks in advance for your help. I can do some more research/debug if needed.