Try right clicking the app and running as administrator. If that doesn't work, go to the Installation directory, drag flirc.exe to the desktop along with flirc.ini. Open up the flirc.ini and change the 0->5 and all the 'false' words to 'true'.
A log should be put on your desktop after running the application. Post that log and I'll take a look.
There is a flirc.ini file in your windows directory. Open that up, set all the false -> true. Set loglevel = 5 as well. If you can't save the file, copy the flirc.ini to the desktop and Flirc.exe to the desktop. Run from there. Try upgrading with the dori image. Send me the log file. that gets created when it fails.
Definitely didn't upgrade. Try it again. If it's stalled for a even a minute unplug it and plug it back in. Don't close the GUI When you start the software after a failed upgrade it will load the embedded version, and in this case is the known non working one. When did you get your flirc and are you using windows? Windows upgrades are always a bit more trouble, but they should work.
When all is said and done the firmware version in the lower left corner should match the one on the file name. 4.0.18
There are two hardware sku's. try to upload with nemo first. if it fails, use dori. Built in profiles are disabled in this one. I'll add proper support for this going forward so you can remove any one. Let me know if this solves your needs in the interim.
Okay, this is going to take a bit of work to do right, but I'm just going to post a firmware image here that has WMC disabled. I'll make it so you can disable / enable any one of them. Give me a second.
Okay, so I've been looking at this all day with a USB analyzer and scope. Unfortunately, everything is looking correct, but I have some ideas. Here is what I'm seeing. When the host is sleeping, gen1's USB+ and USB- lines go into the resume state. When the 'wake' signal gets sent. It's sending a K-state for roughly a second, well beyond the spec. All this is, is when the D+ and D- signals switch polarity. You can see that in the image where it says keep alive.
Now with Gen2, I see the exact same thing. It's much shorter, and controlled via the chip. The spec only says 1second to 15 seconds.Fully within spec, here it is:
The two obvious things that are different are: Gen1 is out of spec, too longGen2 is reversedGen2 being reversed is okay. Gen1 is operating at low speed USB while gen2 is operating at full speed. So there could be a few things causing this: Gen1 is out of spec, but it's a good thing?Gen2 is full speed vs gen1 low speedGen2 is not actually detecting when your computer is going to sleep.I'm suspecting that it's not 1. It would be crazy to think that you have to run the device out of spec in order for it to wake the host. I'm hoping it is 2. as that's a relatively easy fix. 3 is hardest to prove. I would need to send you guys a modified unit with an LED that turns on when the host is sleeping. When it's not working, is the led on? If it's not, than flirc is not detecting the host go to sleep. So attached is a firmware image to try with flirc running in low speed mode. (the bootloader will still be full speed, so upgrades will be fast still). Let me know if this seems any better. If not, we'll figure out how to do #3.
Thanks! our second girl, been a tough month to say the least and the office was necessary because I couldn't get anything done at home anymore. @Robawesome, can you clarify, when it was receiving commands from your Blue Ray player, was that gen1 or gen2? Can you fire up advanced settings with gen1 plugged in, do you have built-in-profiles enabled? @sssst, okay, this makes sense. I actually have a WMC profile built in, particularly for streacom, but it should work with inteset remotes. What remote are you using with firetv? Inteset?
I am going to fix this. It's just me, I just move the business out of the home, and into an office, and am back at work now. Plus we had a baby two weeks prior to this thread. Can you guys give me some information on the WMC profile that's on your harmony? How did you add it, manufacturer, and device. I'll reproduce this and push out a fix. Sorry for the delays. No need to return it, just need a nudge.