ZigmaDK

It has been a little while since I last got a report about this, but I will remember to get the bootloader version. And I will also let our teams know that they should use the 2.0 port instead of the 3.0. Thank you for your help on this, but I still hope that it would become possible to select which firmware should be loaded into the flirc in the future :)

The store owners don't install the FLIRC program unless they experience a problem with it. So it might happen now, it might happen in 6 months. The units that get stuck in bootloader are usually fixed by just connecting them to a PC running FLIRC. It will say "FLIRC in bootloader" load something in the top left corner of the tool and then be back to working again. It was a bigger issue in the beginning (around May '14) but not so much lately. So maybe 3.x fixed some instability for us. How can I check the bootloader version? Is this the same as firmware version? The FLIRCs are connected to the USB 3.0 port of a Madcatz M.O.J.O.

Let me get straight to the point. I find it very odd, that I have to download a new FLIRC tool, in order to get the latest firmware for my FLIRC. Why not just make it autodownload the latest firmware or even better, let me select which version I want to download and then program my FLIRC with. We use it in our company in our store displays and when the FLIRC sometimes gets stuck in bootloader, we have to guide our store managers to download a specific version of the FLIRC tool, to make sure they get the version that we have tested. First time we ran into issues with this, was when the firmware was updated from 2.6 to 3.x. The configuration we had made and distributed to all dealers stopped working, when they used the latest FLIRC tool. Could it not be made, so the force FW upgrade gives a dropdown of some select firmware versions within 1.x, 2.x, 3.x etc.? That way, it is possible to download the latest FLIRC.exe and then still get the 2.6 firmware that we have tested with. Just an idea that would make my life as a supporter easier :)

What solved the problem for you? Could you write the solution here? It might help others.

Did you get a reply to this? I have several that are doing the same and am looking for a fix for this. I connected it to a PC and opened FLIRC and it detect bootloader and then the small loading bar appeared (and loaded) for 5 seconds. I plug it back into the media player and it works again with the previously programmed config. They are running version 2.4, but force FW update says 2.4 is the only one available. Regards Henning

Hi I have a media player that runs android and I want to use the FLIRC to control it. it works fine when the player is on, but when it goes to sleep, I can't wake it up with the FLIRC. If I connect a keyboard and then let it go to sleep, I can keep the Enter key pressed for a short while (2-3 seconds) and then the player wakes up again. Is there a way I can emulate that with a IR command? And what would I need to do in the FLIRC settings? I hope someone here has a good idea what I can try :)

I just registered to shed some light on this issue. The Beo4 can't send other frequencies than the 455KHz. The Beo5 and Beo6 have support for 3rd party IR, but this needs to be programmed into the remote using their Config Tool and it is usually only used to control Light controls or curtains and such. (although it is possible to change it to simulate a MCE or Apple remote, for instance. But this is not officially supported) If you have a B&O TV, it is possible to simulate any of the remotes that B&O have decoded, by adding a PUC table to the TV and connecting an IR blaster from the TV to the FLIRC. This is what I have done on my B&O TV together with my Raspberry Pi. I use a PUC table from a standard remote, and then I put those commands into the LIRC config on my RPi. This works perfect :) Just wanted to clarify the Beo4/5/6 things :)