Jump to content
Flirc Forums
Michiel

Firmware 3.8 / RC6 behaviour

Recommended Posts

Hi All,

I just bought myself a Flirc because of the lack of 3rd party IR support in OSX. When installing and configuring the Flirc device I've updated the Firmware to 3.8 (GUI 1.4.4) and then started configuring my Microsoft MCE (Model 1039) RC6 Remote. While configuring I get an error message saying 'Button already exists' when recording some of the buttons on the remote. This is happening for my Up and Down buttons, it seems the Flirc device reads the IR signals sent by my remote as being the same for some button pairs (Up/Down, OK/Back). After searching this forum I fiddled around with the Advanced settings and I could not resolve the issue. One forum topic mentioned something about downgrading the Firmware so I thought lets try.

After downgrading the Firmware to version 3.1 (GUI 1.2.8) on OSX with the 'flirc_util dfu' command and starting the GUI which then allows to install the lower Firmware, I noticed on 3.1 the RC6 behaviour is perfect, no more duplicate button messages and everything seems fine. I still have to record all the buttons twice because of some RC6-specific difficulties mentioned in other topics, but that's no problem.

When doing some more testing I noticed the Flirc device would not wake up my Mediacenter from sleep, so I searched this forum again and tested all the configurations I found in different topics regarding sleep issues (Sleep detection and different suspend/wake/power button mappings) but none of them solved my problem. I am testing my Flirc device on 2 machines, one Mac Mini (2011) running OSX El Capitan (10.11.5) and one MacBook 12" (2015) also running OSX El Capitan (10.11.5). When putting the machine to sleep I can wake it again using my remote for about 1 minute, after this minute the machine does not respond to any buttons. On the Mac Mini I can see the Power LED going from steady to blinking when putting the machine to sleep, and this takes about 30 seconds. It seems that when the Power LED is still steady I can wake it using the remote, and when the LED goes blinking I can not.

Because I'm very curious I updated the Flirc's firmware to 3.8 and tested the Sleep/Wake behaviour on this firmware, and on 3.8 the wake works just fine! Even after this one minute and with the Power LED blinking on the Mac Mini I can successfully wake it up using one of the desired Flirc configurations (one button with wake, or all buttons without wake).

So now I'm in the position where I want the FW 3.1 RC6 behaviour but I need the FW 3.8 Sleep/Wake behavior so I'm kind of stuck here and I think I need some assistance from Flirc developer @jason.

 

TLDR; On FW 3.1 RC6 is fine but Sleep/Wake doesn't work, on FW 3.8 RC6 is broken but Sleep/Wake works fine. Help!

Edited by Michiel
added tags

Share this post


Link to post
Share on other sites

Any news on this?
I myself have the same Microsoft Remote Control and see the same problems with the Up/Down, OK/Back.
Next, I can not program the numbers 0 to 9 with no errors.

If I use it against an old philips remote control, I have no problems with programs more than 20 features, but the layout of button-front is illogical. So the one I can not use ...

I do not have the old firmware so I can not test whether it works.

Share this post


Link to post
Share on other sites

Any news on this?
I myself have the same Microsoft Remote Control and see the same problems with the Up/Down, OK/Back.
Next, I can not program the numbers 0 to 9 with no errors.

If I use it against an old philips remote control, I have no problems with programs more than 20 features, but the layout of button-front is illogical. So the one I can not use ...

I do not have the old firmware so I can not test whether it works.

Hi Ginderskov,

No updates from my side, I'm still waiting for @jason to hopefully provide a fix. In the meanwhile I can send you the Flirc 1.2.8 GUI that contains firmware 3.1, you will have to force the FW downgrade with 'flirc_util dfu'. One thing worth to mention is that this 1.2.8 version is for OSX only, would you like me to send you this DMG?

Share this post


Link to post
Share on other sites

Due to lack of support on this issue I formatted the Mediacenter back to Win10 with built in MCE IR support. The FLIRC dongle has been archived in a dusty drawer. I'm not going to put any effort in getting a refund, and my overall experience with FLIRC has dropped below freezing point.

Share this post


Link to post
Share on other sites

Michiel - I thought you mentioned that firmware 3.1 fixed it? Was that not the case? I'm sorry, I can't see past black friday at this point.

I will be working on the algorithm shortly after. I have some new code and simulations written so that I can write something to accomodate this remote as long as it's within the 38kHz.

Share this post


Link to post
Share on other sites

Hi Jason,

At 3.1 firmware the buttons behave OK but the wake functionality does not work. But at 3.8 the wake functionality is OK but the buttons don't work as expected. So both firmwares have their own separate downside for me, combining the 3.1 button config and the 3.8 wake functionality would be awsome! I will repeat the OP down here:

Hi All,

I just bought myself a Flirc because of the lack of 3rd party IR support in OSX. When installing and configuring the Flirc device I've updated the Firmware to 3.8 (GUI 1.4.4) and then started configuring my Microsoft MCE (Model 1039) RC6 Remote. While configuring I get an error message saying 'Button already exists' when recording some of the buttons on the remote. This is happening for my Up and Down buttons, it seems the Flirc device reads the IR signals sent by my remote as being the same for some button pairs (Up/Down, OK/Back). After searching this forum I fiddled around with the Advanced settings and I could not resolve the issue. One forum topic mentioned something about downgrading the Firmware so I thought lets try.

After downgrading the Firmware to version 3.1 (GUI 1.2.8) on OSX with the 'flirc_util dfu' command and starting the GUI which then allows to install the lower Firmware, I noticed on 3.1 the RC6 behaviour is perfect, no more duplicate button messages and everything seems fine. I still have to record all the buttons twice because of some RC6-specific difficulties mentioned in other topics, but that's no problem.

When doing some more testing I noticed the Flirc device would not wake up my Mediacenter from sleep, so I searched this forum again and tested all the configurations I found in different topics regarding sleep issues (Sleep detection and different suspend/wake/power button mappings) but none of them solved my problem. I am testing my Flirc device on 2 machines, one Mac Mini (2011) running OSX El Capitan (10.11.5) and one MacBook 12" (2015) also running OSX El Capitan (10.11.5). When putting the machine to sleep I can wake it again using my remote for about 1 minute, after this minute the machine does not respond to any buttons. On the Mac Mini I can see the Power LED going from steady to blinking when putting the machine to sleep, and this takes about 30 seconds. It seems that when the Power LED is still steady I can wake it using the remote, and when the LED goes blinking I can not.

Because I'm very curious I updated the Flirc's firmware to 3.8 and tested the Sleep/Wake behaviour on this firmware, and on 3.8 the wake works just fine! Even after this one minute and with the Power LED blinking on the Mac Mini I can successfully wake it up using one of the desired Flirc configurations (one button with wake, or all buttons without wake).

So now I'm in the position where I want the FW 3.1 RC6 behaviour but I need the FW 3.8 Sleep/Wake behavior so I'm kind of stuck here and I think I need some assistance from Flirc developer @jason.

 

TLDR; On FW 3.1 RC6 is fine but Sleep/Wake doesn't work, on FW 3.8 RC6 is broken but Sleep/Wake works fine. Help!

Share this post


Link to post
Share on other sites

Hi Jason,

At 3.1 firmware the buttons behave OK but the wake functionality does not work. But at 3.8 the wake functionality is OK but the buttons don't work as expected. So both firmwares have their own separate downside for me, combining the 3.1 button config and the 3.8 wake functionality would be awsome! I will repeat the OP down here:

Working on a fix right now for you. Thanks for being patient. 

Share this post


Link to post
Share on other sites

Let me know if I can help with the test. I would like to...

For in the moment, it becomes pretty worthless, it is just floating in the corner.

Looking forward to a firmware update.

I want to apologize for the delay again. So here is a bit of back story. Flirc has been a side gig for 5 years and it's blown up in a good way. But managing the company, IP, development, orders, production, architecture, business model, marketing, customer support, etc, are all full time jobs themselves. However, I was a full time employee already at NVIDIA working on their GPU's for deep learning. Outside of that, I'm also a dad. It's been a journey, and I'm not making any excuses, but trying to describe why things have been a bit slow.

About a month ago, I took the leap and left NVIDIA. It was absolutely a necessary step, especially being that this last month has been one of the most important defining months of the company. For the past year and a half, I've been working on the new flirc. The limitations with the original couldn't be overcome with any more tricks. It was time to start over.

I've entered production and encountered a show stopping bug. Certain USB hubs weren't working, and after a bunch of all-nighters, we finally proved that it was the PLL in the device and not locking. Got a fix, and working on trying to figure out how to update the thousands in manufacturing. (The problem is the boot loader can't be updated). I've proven a couple ways to overcome this.

The feature you're asking for is actually really trivial. But my time is needed ensuring a smooth launch, pretty much the entire company is riding on this.

The new one is stunning, a work of art inside and out. It's built with stainless steel, and it packs a ton in it.

Not only will I push an update to the one you guys have, but I'll send you the new one on the house to both of you as a thank you for not giving up on me. 

The site will be updated today. Once I push an update to manufacturing, I'll address this again. I pretty much have to figure this out by Sunday.

Thanks again for being patient. And happy thanksgiving to you guys.

161117_DSC00459-Edit_ScreenOff_1.jpg

Share this post


Link to post
Share on other sites

Congratulations Jason!!  That is a huge step.  I definitely support you in my small way, and am pleased to see how you're working on taking care of people when you know about your time constraints.

 

Wish you the best of luck with this new product, and the growth of the company!

Share this post


Link to post
Share on other sites

I want to apologize for the delay again. So here is a bit of back story. Flirc has been a side gig for 5 years and it's blown up in a good way. But managing the company, IP, development, orders, production, architecture, business model, marketing, customer support, etc, are all full time jobs themselves. However, I was a full time employee already at NVIDIA working on their GPU's for deep learning. Outside of that, I'm also a dad. It's been a journey, and I'm not making any excuses, but trying to describe why things have been a bit slow.

About a month ago, I took the leap and left NVIDIA. It was absolutely a necessary step, especially being that this last month has been one of the most important defining months of the company. For the past year and a half, I've been working on the new flirc. The limitations with the original couldn't be overcome with any more tricks. It was time to start over.

I've entered production and encountered a show stopping bug. Certain USB hubs weren't working, and after a bunch of all-nighters, we finally proved that it was the PLL in the device and not locking. Got a fix, and working on trying to figure out how to update the thousands in manufacturing. (The problem is the boot loader can't be updated). I've proven a couple ways to overcome this.

The feature you're asking for is actually really trivial. But my time is needed ensuring a smooth launch, pretty much the entire company is riding on this.

The new one is stunning, a work of art inside and out. It's built with stainless steel, and it packs a ton in it.

Not only will I push an update to the one you guys have, but I'll send you the new one on the house to both of you as a thank you for not giving up on me. 

The site will be updated today. Once I push an update to manufacturing, I'll address this again. I pretty much have to figure this out by Sunday.

Thanks again for being patient. And happy thanksgiving to you guys.

Hi Jason,

This is good and exciting news! Let's hope your Flirc batch that's currently in manufacturing can be updated to contain the necessary fix. I would gladly help you by testing the new Flirc device with the mentioned RC6 remote. And hey, the brand new Flirc device on the house, that's totally awsome, thanks!

Let me know when the units are ready for testing and shipping, I will PM you my address details and such when you need them.

Happy thanksgiving!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...