Killed my Flirc

[St Veronus]

Hello,

I just purchased 2 dongles for my 2 AFTV's controlled by 2 Harmony 650's.  I downloaded the Windows installer today (1.4.4) and installed it.  I plugged the first dongle in, changed the remote to AFTV, started the programming, and pushed buttons on 650#1 to correspond with my choices.  Made it thru just fine.  Ejected the dongle, tested on AFTV#1 and it works beautifully.

Grab dongle#2, plug it in, registers fine with connected and firmware 3.6.  Grab 650#2, start the AFTV remote programming sequence and I get the button already programmed error.  Not knowing what happened or searching here first, I clicked on the Advanced>Force Firmware Upgrade.  I get the popup for using 3.8 and click okay.  I hear the dongle get disconnected, then the "Flirc.exe has stopped working" program crash in Windows 8.1.  Now whenever I'm running the app and insert this dongle#2, it crashes the app.  I can successfully plug dongle#1 in and it is fine, so I think I may have killed my dongle#2 trying to do the firmware update.

Please advise if I need to return this unit.

 

Cheers,
Ryan

[jason]

In your installation directory, there is a flirc.ini.

can you change the loglevel to 5

libusb = true

logtofile = true

append = true

re-run the app with the 'bad' flirc and post the log file here?

[St Veronus]

Thanks for the quick reply Jason!

 

 

 

Edited March 24, 2016 by St Veronus

[jason]

Doesn't look like it caught the session from the beginning. Can you try closing the app, opening, and trying again? 

Also, just making sure, you don't have the other device in the machine, right?

 

 

[St Veronus]

Spelling of true helps!  Sorry about that.

flirc_log.txt

[jason]

Any chance you can give this a shot?

 

https://flirc.zendesk.com/hc/en-us/articles/200712548-Using-the-ZADIG-Utility

[St Veronus]

Here is the log file after running that.  I had to use the bootldr option as Flirc wasn't shown in my list (vm).

flirc_log.txt

[St Veronus]

Hi Jason,

Should I return this unit to Amazon for replacement or?

[poissony]

I have exactly the same issue. Attempted to upgrade from 3.6 to 3.8 and now the dongle is dead. Is there a fix for this?

[poissony]

Nevermind I was using Windows 10 which seems to cause this. Updating firmware using a Mac and now working again.