Jump to content


  • Posts

  • Joined

  • Last visited

rbridd's Achievements


Newbie (1/14)



  1. Further to my comments above... 1) Thank you to FLIRC support for following up and making suggestions which did in fact cure my problem. (Doing (another) reset.) 2) In following up this issue, I have found that using the FLIRC on my Raspberry Pi was what was causing it to go a bit wild. It is in effect, reprogramming itself, or losing it's programming, depending on which way you are viewing the matter. Remembering the addage that "90% of all Raspberry Pi problems are caused by an inadequate power supply", I replaced my cheap ebay 5V USB charger with an industrial strength unit capable of 8Amps delivery at 5V. (Although that amount of power is certainly not required...) The problem went away. It's been steady as a rock now for over a week. So it seems that the FLIRC is a bit succeptible to a fluctuating power delivery, in my case caused by a cheap PSU, but in the past I have seen slightly wobbly USB sockets cause power problems with connected devices. Hope this helps somebody.
  2. Interesting you should say that :) I have gathered Slightly more accidental information to the above observations. While, (after), removing the batteries from the remote control, (to be sure that it wasn't part of the equation) I jogged my desklamp... and the FLIRC generated a keypress. So I turned the desklamp OFF, and the FLIRC generated a constant stream of <enter> and <up> keypresses, interspersed with occasional "-"s. Depriving the device of light altogether, (Putting it in a cardboard box on a USB extension lead), stopped it... so it is behaving in this way in very low light conditions, but not No-Light conditions. So then I decided to reprogram it. Start from scratch, so I unplugged it and replugged it, but it appeared completely inert, not responding to any input. I had to reboot my PC to get it to be recognised, and then, the PC downloaded the bootloader/driver again. (Yes, it was always plugged into the same USB port). Long story short, once the PC recognised it again, I used the "clear configuration" option to start afresh, and reprogrammed it, and it appears to work. Turning lights on and off no longer has any effect on it. I'll keep an eye on it. <later> OK. It now transpires that it responds to the FLIRC software, but after programming the keys, and exiting the FLIRC software, it does not detect any button presses on the remote and generate any input detectible by EventGhost, or on the Raspberry Pi Raspbmc. It's possible that it's just a faulty item rather than a firmware bug, and the bahaviour with the lights was simply it's death throes. are there any further tests I can reasonably do at home, or should I return it for disection?
  3. Firstly... Thanks for an amazing product. However... ...this is another "me too". My RaspBMC was working fine, then not responding to the remote, then shortly after it would crash requiring reboot. This behaviour continued for a couple of weeks. I removed the FLIRC, and intending to reprogram it, (desperate measures. I was ready to try anything), and plugged it into my PC. I had a text editor open, and with window focus, and it was immediately apparent that the FLIRC was generating keypresses. I fired up EventGhost to capture the keypresses. Mostly <enter>, circa 200 presses, but with a healthy smattering of up down, left and right arrows, with a couple of -- thrown in in a five minute period. Then I had to go to work. On returning home, I started to investigate again, but could not replicate the problem! It is dark outside now, the previous test was done in daylight. I have tried to confuse the FLIRC with various light sources... LED torch Daylight bulb Long life bulb Standard torch "laser" pointer ...but it is steady as a rock. I'm going to plug it back into the media center for now, but it's clearly not something I can rely on. Please keep me informed of any developments in resolving this problem.
  • Create New...