Jump to content
Flirc Forums

jason

Administrators
  • Posts

    2,695
  • Joined

  • Last visited

  • Days Won

    116

Everything posted by jason

  1. Yup, I am on some time off, but am working this week. I'll send you beta firmware. I re-wrote my entire IR stack. I have an architecture now to easily add protocols, decode, and denon is already done. I'll post a section for a beta release this week.
  2. I need to touch base with NVIDIA. I’m not sure why it’s not working yet. I’m worried they are blocking anyone but their remote from doing this.
  3. My pleasure, really so sorry about the trouble. It looks like everyone having issues is using windows. Other operating systems ignored the report descriptor issue, but windows USB has always been a nightmare. It was the main motivation for the second generation Flirc which has a custom USB stack and uses only HID, which run completely driverless to avoid windows problems.
  4. Unplug, restart, and give it another go. I think windows is just confused because it's stuck in a bad state from last firmware.
  5. Yeah. Have you tried restarting or using a different USB port? We can do a team viewer session
  6. gen1 isn't supported with remote buddy. It's unfortunately not possible with the microprocessor I used.
  7. let's do a team viewer session. Let me know if you are free tomorrow.
  8. Oh I'm so sorry, I modified the content and forgot to update the CRC. Try the attached. Sunrise_Flirc_updated.fcfg
  9. You can't just re-load the configuration file. Re-learning the keys is necessary because I'm using new USB codes. I've edited your config file. Load this up and try that. Sunrise_Flirc.fcfg
  10. Wait. Flirc can’t work with Bluetooth, I’m not following?
  11. If you did the flirc.ini changes, a flirc.log file should have been created and put on your desktop, do you see that?
  12. Go to Program Files (x86) \ Flirc\ edit flirc.ini Change loglevel = 5 and change all false words to true. Run the app again, and let's see the log.
  13. Okay, I think I got it. Everyone was using windows, and there was something that needed to be fixed in my report descriptor and it looks like other OS's were more lenient. Sorry, please try the attached. File->advanced to get your sku, and then do file->upgrade ,and upload one of the attached. gen 1 devices can use the flirc-gen1v3.12.bin file nemo.release-4.9.1.bindori.release-4.9.1.bin flirc-gen1-v3.12.bin
  14. If you are using harmony, you shouldn't need to repair anything. Can you post your configuration?
  15. You need to re-pair your remote. Can you go to file->device log. enable ir debugging, and press some keys after you recorded some?
  16. Also, save your configurations and post them here too.
  17. I have done so much testing and my changes were very minimal with the gen2 device, I'm baffled. Can you guys go to flie->devicelog. Try and record some buttons, enable IR debugging, and then save and post the log here.
  18. I don’t think the downgrade will help, but we can try it. Can you show me the device manager. There are two interfaces, interface 0 and interface 1. You do not want interface0 to be assigned by ZADIG. You want to remove that so that windows installs the default HID driver.
  19. Hi @Adri, we’ll fix it. What version are you using? The plastic version, or the metal gen2 device?
  20. I've published the update. This should support both gen1, gen2 devices, and you'll need to relearn the buttons that don't work. feel free to follow-up here with issues. I've done a lot of testing and regression testing, but it's not impossible I missed something.
  21. I've re-written all my IR stack, and I'm going to post an update in the next few weeks. I'll try and grab one of these remotes to ensure everything works correctly.
×
×
  • Create New...