![]() I am still not sure if I actually needed to program the up, down, left, right, enter and back keys but I did. On the reboot of the Rasbmc the Flirc gui was started and I was good to go. xbmc/addons section and added the udev rule as well. Turns out the flirc-xbmc repo was infact all I needed here. The funny thing is that I can plug the flirc into my windows laptop and it controls xbmc on that PC just fine! I feel like I've been banging my head against the wall trying to get my new flirc to work on RaspBMC.with no luck. Despite multiple tries - that utility continues to show disconnected on my Pi. I also tried the Flirc configuration add-on the allows you to program the flirc on RaspBMC. When that did not work, I tried the lirc setting. I also enabled the RaspBMC settings for the IR Remote feature and selected the Windows MC defaults. I too configured my Harmony remote with the Flirc device. I finally did get a successful upgrade to 2.3. It took me most multiple tries on Windows, Linux and OSX machines to finally get a successful firmware upgrade (to 2.3 in my case.) I too experienced the hanging you describe - in most cases not having any impact on upgrading the firmware. Can anyone walk me through this process to matbe see where I missed a step? I saw may mentions of the git repo for XBMC but due to it age and the dates on the commits I am not sure it is something I need or what. I am stuck, not sure if I missed something or what. I rebooted the unit and got a LIRC prompt on the bottom right that said a config was created successfully. I was hoping to see a Flirc profile to chose from but there is not one. So then I went into the RaspBMC settings and enabled the IR Remote feature and selected the Windows MC defaults I believe. I then tried to use the remote and it would not work. I synced and then plugged in the USB and rebooted the Raspbery Pi sporting the RaspBMC OS. ![]() Next I connected to and added the Flirc and XBMC profile and set up the activity to switch my Sony Reciver to the proper HDMI and my TV to the proper input and ofcourse use the Flirc XBMC device. I closed and finally got the firmware to update to v2.2. This failed once and the GUI just hung for about an hour. I connected my Flirc USB to my Windows 7 box and installed the GUI, then forced the firmware update to v2.2. So, since running XFCE desktop, I used the Keyboard settings panel to associate the CTRL-~ key to run a command: /home/myth/restartFrontend.sh.I have been through these forums all day and I feel like I am still missing something. Best option is to get something to listen to a keyboard shortcut. You cannot do that with FLIRC, as it mimics a keyboard. In LIRC, I used configured in the config file the file to run when a button on the remote is pressed. Replace the restart myth frontend capability. This took way longer to Google than I would wanted. This also means that if you want to remove the button, you need to erase it two in the FLIRC GUI as well. So, to fix this, either use a different profile, or do what I did – record the button twice. Turns out, with the remote, is that it is basically alternating what it sending. The issues I had with FLIRC (and possibly related to the Microsoft MCE), is that when I was pressing the button, I was getting two distinct codes. OK – let me say this, I have it trained to the old Microsoft remote that I had, and it is giving me 0.5 second delays between keypresses, not matter what inter delay setting I choose. I use a Harmony 650 remote, and while an OK remote, does not seem to place nicely with FLIRC. Unfortunately, it took longer to get going than what I expected. ![]() Having something that just is a keyboard is a great concept. Wanted to do this, as I am going to upgrade OS, and didn’t want to muck around with LIRC settings. So, purchased a FLIRC to replace an older MCE USB IR receiver. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |