Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

Posts posted by BarkerR

  1. Let me know, please upgrade to 3.8, that's the latest.

    Yep that sorted it :D great work, I'd have been a bit stumed otherwise as I just hammered every key on my keyboard and still couldn't find where home had moved to (I'm assuming it's now a media key or other non-standard key that's missing from my keyboard).

  2. All of a sudden the Flirc connected to my FireTV quit responding to "Home" key presses on both of my IR remotes (a Harmony 650 and a Sony RM-VLZ620 ), . I haven't messed with anything in over a year, so I can't imagine what would have all of a sudden make this start happening. I googled the problem and see there are a lot issues with the Home key, but I never had any until now and don't know what to try to fix it? Any suggestions?

    Note: I just now checked and there was a FireTV update installed two days ago, so it seems that's the cause!


    Mines gone the same way after the update. It looks like Amazon have changed the home key mapping so they can apps like Firestarter from detecting home key presses.

    I'm going to plug a usb keyboard in and try to find where it's moved to.


  3. How about the following, can you measure resistance 1 and resistance 2 in the pic attached?


    Hi Jason, just to let you know I haven't forgotten about this. My son decided he wanted to be born 6 hours after my last message, and on top of dealing with a newborn I've also been running an Indiegogo campaign so things have been a bit hectic.


    I'll get the readings as soon as get 10mins to myself ;)

    • Like 1
  4. I have a crystal on my PCB, it's the metal box. The top of the metal is grounded. What's the resistance between the shield of the USB and the top of the crystal. (Do this when it's not plugged in).


    Then can you check your USB mating shield on your motherboard with the ground your connecting the flirc to? 


    Here you go, 2 meters both the same reading http://1drv.ms/105bhDY


    I'll have to get back to you on part 2 as that involves dismantling stuff and I need to get to bed.

  5. Actually you don't need to learn from MCE remote. You can set up Simple 4 remote with MCE setup code using simpleset.com website :) (at least european URC-6440 can be set up this way, I think there was some strange problem with OARUSB04G). I'm also actively working with experts from http://www.hifi-remote.com/forums/ which is a community of EUI/OFA remotes modders (these remotes can have very advanced features) on supporting these new "SimpleSet" (like Simple 4) remotes and I think that we will release something really soon. The software we are working on allows to edit remote's configuration in much greater details.


    As for 3 you can always use some kind of script or software to map mouse movements to specific keyboard shortcuts and map those shortcuts to remote buttons.


    I assume you're talking about this thread http://www.hifi-remote.com/forums/viewtopic.php?t=15142&postdays=0&postorder=asc&&start=0 I've been watching it for a while :)

  6. Is any of the hardware in your setup properly grounded? All devices should share a common ground but it should also be grounded as a whole. Are your electric sockets grounded? I don't know what is the socket standard where you live.


    I'm in the UK so the electrical sockets are grounded although I'd say none of the hardware is actually grounded in standard configuration (it's grounded now as I've wired the USB shield to ground) - TV and Sky box are on unearthed 'figure 8' leads which are only live/neutral, and the Pi runs on an iPad 5v supply. On a side note the TV on my upstairs setup (which works fine) uses a 3 pin 'kettle lead' which is grounded.


    can you do a dmesg at the beginning of this test and at the end? Maybe that give us some clues as to what linux is seeing.


    Yep can do, give me an hour until my daughters gone to bed (she's using the TV at the moment).

  7. Maybe there is some problem with ground connection. Have you tried with different cable or even PC? Maybe the PC or the USB ports on the MoBo are not grounded properly.


    BTW I have the same OFA URC-6440 (Simple 4) remote :).


    I've tried it with other cables, and also plugged directly into the Pi itself with no joy. It works fine if I plug the flirc into my laptop or my Pi setup upstairs.


    The issue is potentially my Sky TV box as things improve if I unplug the HDMI lead for that. The shielding for the satellite dish grounds to the Sky box, which is a shared ground for the HDMI so maybe it's causing some interference?

  8. Ok, well the flirc working after swapping the USB seems to have been a fluke and it stopped working again :( however it brought me back to putting my finger on the USB plug to get it working - here's a vid demo of that http://1drv.ms/1zc7T63 It's hard to see but at the beginning I have my finger on the USB and it's working fine (other than the sticky button on my remote). When I take my finger off it works briefly then the key gets stuck - as soon as I out my finger back on the USB the sticky key stops. Looks like some kind of earthing issue so for now I've run a wire from the Earth on my house mains and attached it to the USB which seems to do the trick.

  9. Hello there, I've managed to fix my repeat keys problem using a method I've not seen mentioned here before - changing the USB plug on the Flirc. Here's the backstory for anyone interested:


    So, I've got two Flircs, one upstairs, one downstairs both plugged into Raspberry Pi's via a USB extension. The one upstairs has never given any issues, but the one downstairs has been a PITA from day one giving repeat keys one minute, then not responding at all the next. I tried every solution mentioned on here, clearing and reconfiguring the Flirc, changed interkey delays, changed remote controls, changed the PSU on the Raspberry Pi, removed the Wii sensor bar from the room (incase it was causing IR interference. Sometimes it would work fine for an hour, or a day then just go haywire again.


    Tonight I was determined to get it sorted out, so I went through everything all over again, plugged the Flirc back into the Pi and it was being quite unresponsive. I put my finger on top of the Flirc to cover some of the IR sensor, tried pressing some buttons and it was working great. Awesome! I thought as I headed out to the shed to grab the black electrical tape and mask some of the IR sensor. I sat back down on the sofa and... bugger it was playing up again. I tried plugging it straight into the Pi bypassing the USB extension and then it just didn't work at all, that was until I pressed down on it. I then plugged the Flirc back into the extension, squeezed the USB connection and it was working again, released the pressure and it started playing up. Tries a different extension with the same results so I figured something must be with the USB plug on the Flirc itself. Swapped that for one from an old memory stick and voila it works perfectly now  :D

  • Create New...