Jump to content
Flirc Forums

AllardSijm

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About AllardSijm

  • Rank
    Junior Flirc-er

Recent Profile Visitors

1,788 profile views
  • K22

  1. Thank you K22, for your reply. I will try your solution later this day and will report back whether it worked for me also. [edited] Your solution worked for me too. In the end I didn't need to uninstall the latest version, I ran the 1.4.4. executable while v2.0.2. was still installed. The earlier version upgraded the firmware succesfully and after that I could just run v.2.0.2. to start programming. Again thank you for the solution!
  2. This Flirc has been in use for some time withouth problems. Today I wanted to change some settings so I installed the latest Flirc software. After running the software, it automatically tried to update the firmware on the Flirc. Seconds later it showed a message like "upgrade failed". Since then, the Flirc device is no longer recognized. The Flirc logfile is here: http://paste.ubuntu.com/23647032/ Note, I enabled logging only after the problem occured. I tried connecting the Flirc to several PC's (Windows 10 and 7) but on all I got the same "Please connect Flirc" message. The flirc bootloader
  3. Yes, the Flircs are fantastic. Much better than the MCE-IR receiver I used previously (and that one was more expensive). Only problem remaining is with waking up the computer via Flirc. The flirc seems to wake the computer randomly, even with the remote not being used, and in a dark room. It's not a showstopper for my and probably new firmware will fix it. I do have a suggestion for the software: It would be nice if one could easily review which buttons bound to which key(combination)s. Perhaps a list of all assignements, or maybe the onscreen keyboard could highlight already recorded keys
  4. Thank you Chris for your reply. WIth me, the confusion was that there is no save button, I don't mean save configuration, but "save to flirc" or "save to device". The recorded keys are only written to the device when you quit the program, so I think it would me more intuitive to rename that option "quit and save" instead of just "quit".
  5. This morning I completely reprogrammed the flirc and discovered something weird: During programming, I can verify that recorded buttons work in notepad. If I remove the flirc and reconnect it while the flirc program is running, the recorded buttons no longer work. If I quit the flirc software before removing the flirc, the recorded buttons still work after reconnecting it. So it seems that quiting the software is a necessary step to make sure the programmed keys are stored in the flash memory of the flirc. Even saving the configuration to file doesn't save it to the flirc. The weird thin
  6. The same problem just developed on one of my flircs too. I have one remote (Logitech Harmony) and have two flircs programmed for it with the same keys. What I did was the following: I changed three buttons on the Harmony remote and then (re)programmed these buttons one of the two flircs. I saved the configuration when I was done. I then connected the flirc to another computer (where I run XBMC) and found that non of the keys were working, not even the keys that I hadn't changed. I connected the other flirc (which wasn't reprogrammed) and it recognised all buttons. I then connected the f
  7. I am also waiting for the new drivers since the one Jason posted are not yet working. I get the same errors as others (A problem was encountered while attempting to add a driver to the store).
  8. Just received my order for 4 flircs and started immediately. It took about 15 minutes to install the drivers and programm all the keys. Except for wake up everything worked great the first time. Since the delivery took nearly three weeks I had plenty of time to prepare. I had already made a keyboard.xls for XBMC, configured the Harmony software and most importantly, I made a list of which button would be assigned to what key and what it does in XBMC. Also, after reading about ghost button presses, I decided to use a box that was open at both ends. The flirc goes into one, the remote in the o
×
×
  • Create New...