jason

I actually toyed with the idea of the IR plastic, but the product was absolutely atrocious. It scratched easily, and ended up looking purple. I'm going to see what I can do about this, it seems to trouble several people.

what is the remote that isn't working?

No unfortunately, I have to do it manually with a fixture. Where did you find it locally?

There have been no hardware changes, but the bootloader has changed. The oldest one had a bug. There is a small silkscreen on the device chip inside. It should say fw 3.0 or so. Thanks Darryn. Very Sincerely, Jason

other remotes work okay?

I haven't made any changes to the hardware, but the bootloader is indeed different. A lot of people are experiencing problems with repeaters and small cabinets where the flirc registers a bunch of signal bounces. While your firmware upgrades probably went okay and succeeded, there are chances of corruption still. Chances are small, but it's not worth ruling out. Feel free to shoot me an email, I'm more than happy to see if a new one helps. Just let me know.

sweet!!

Try forcing a firmware upgrade again. Sometimes it takes a fresh upgrade to ensure the firmware gets loaded correctly on that generation of devices. If you continue to have problems, let me know.

= )

Nope, that's the minimalist view. Check out the rest of the controllers in the file menu. You are essentially mapping keyboard keys. That GUI you used is just the essentials. I present a full keyboard, and pre-mapped shortcuts for favorite apps in the controllers. XBMC, Keyboard, Media Center, WMC, etc

Sorry, missed your first reply. Any chance we can set up a team viewer session?

Yes, you found out before I was able to get back to you. They use non-standard frequencies and it messes with flirc a bit. I have it on my todo to fix this. Try samsung or panasonic profiles. Those work great.

No problem, appreciate you understanding. It's been pretty tough. Which version of the GUI are you on? You on the latest?

I mentioned this in a few places, but don't like to because it doesn't excuse much, but it's just me here. I do everything, support, development, sales, packaging, testing, assembly, you name it. It's literally enough jobs for 2 people full time, and I do it outside a full time job. I may miss an occasional post, which I did, and I really apologize. One way to get a hold of me is by going to that contact support site, it goes directly to my email and is managed by zendesk so I don't lose track. That's a problem that is due to a bad driver. Give this a try: https://flirc.zendesk.com/hc/en-us/articles/200712548-Using-the-ZADIG-Utility I apologize I missed your post.

I mentioned this in a few places, but don't like to because it doesn't excuse much, but it's just me here. I do everything, support, development, sales, packaging, testing, assembly, you name it. It's literally enough jobs for 2 people full time, and I do it outside a full time job. I may miss an occasional post, which I did, and I really apologize. One way to get a hold of me is by going to that contact support site, it goes directly to my email and is managed by zendesk so I don't lose track. I'll respond about what your specific problem is in your thread.

Yes they would, and yes you just need to use different profiles.

Any chance I could you post a picture of your cabinet?

Glad it finally worked, not sure why it took so many attempts but it shouldn't be an issue any more. Sorry for the trouble.

How about trying to install the libusb driver?

Try this: https://flirc.zendesk.com/hc/en-us/articles/200712548-Using-the-ZADIG-Utility ** EDIT ** you have an old driver, the installer doesn't do a good job of replacing the old driver, and I don't know why. Following the instructions, you'll force the update of the driver, and everything should be good. The -16.-16 is because that request to the device doesn't work because the old winusb driver is restricting commands.

In the advanced menu, disable 'built-in profiles'

That's a really interesting find. Try the same command with sudo

It's not too bad. Here is what I would recommend to help out. Use an sftp application, on the mac, it's transmit/cyber duck. There are plenty for windows. What this will do for you, is look like an FTP browser but connect over SSH. You'll want to connect to your raspberry pi on port 22. Use the default raspberry pi login and password for your distribution. root/openelec Then, browse to the location of the xml file. Looks like it's here: /storage/.xbmc/userdata/ (found on this website: http://wiki.xbmc.org/?title=HOW-TO:Modify_keyboard.xml) Then, with that application, you could double click it, and open with a text editor, or drag it to your computer, edit it, and then send it back. That should make things easier. Let me know.

Yes, it's definitely the keymap file in XBMC. I tried to use the most common keys, but often, the keymap on the distribution, xbmc, openelec, etc, will be different. You need to ssh into the box and locate that xml file.

Thanks Chris. Yes, just a one man show. I have a number of things I'm working on to get me more free time.