Jump to content
Flirc Forums

jason

Administrators
 View Profile  See their activity

  • Posts

    3,757

  • Joined

  • Last visited

  • Days Won

    231

 Content Type 

Posts posted by jason

  9. Windows 8

    in General Questions

    Posted

    I have tried the solution you provided via the link. So far it has work great, but it seems like the flirc registers quite a few double presses. Has anyone else experienced that?

    What kind of remote are you using? It's most likely a remote issue. The driver is just to do the initial pairing, otherwise it's all the firmware.

  10. Windows 8

    in General Questions

    Posted

    Hey Guys, I don't want to leave you hanging, this is turning out to be puzzlingly difficult. Here is a solution that you can use in the mean time. Since I use libusb, there is a free safe utility that creates a signed driver on the fly. I've outlined the steps to do this, it's extremely straight forward:

    http://flirc.clarify-it.com/d/epnthl

    The drivers these create are one time use, they wont work if you try to share them, which is what I initially did wrong. I'm trying to figure out how to solve that. Thanks everyone.

  12. Windows 8

    in General Questions

    Posted

    Sorry guys, I wasn't getting updated of thread events.

    In windows 8, go into device manager. Right click flirc, and update driver. You need to say have disk, and point to the files I attached.

    So sorry for the confusion, the attached isn't an executable.

    Did you guys who received an error try the same method?

    Let me know. I'll try and get to the bottom of this. Yes, I'll update the installer once I can confirm it works for people other than myself.

  15. Windows 8

    in General Questions

    Posted

    Yes, that's basically what we've been talking about. In fact that page more or less exactly replicates instructions earlier in this thread :)

    It's not a good solution. Not only will it throw of a lot of users - and now that Windows 8 is officially released, that will happen more often - but it's a huge security risk because you are disabling signature enforcement for all drivers.

    I understand it's more or less a one man show with volunteer help, and I've been supportive of the effort (and I've also bought 4 FLIRC modules) but the lack of updates on this and many other issues is really starting to bum me out where this product is concerned. At the end of the day it is a paid product.

    You are absolutely justified, and it's easily perceived as though I've neglected the project. I promise it's not the case. I'm working so hard behind the scenes so that I don't waste time on repetitive tasks, that it's taken time away from being able to keep up with development. But I'm pretty much done with that. I do this alone, and on the side of a full time job. But, every second of free time I have goes into this project because I absolutely love it and the supportive customers. I wish so much that I can do this full time, it's truly my passion, but I wouldn't be able to support my family.

    This is not an excuse, but just an explanation. Not only will I address the windows 8 issue immediately, but expect more frequent updates as I'm pretty much knee's deep in development again.

    A special thanks to Chris for always notifying me of forum updates, which I sometimes miss.

    Again, I will post an update on this thread as soon as I figure out how to get a signed driver in my app. Expect firmware issues to be resolved, better documentation, and more features.

    My sincerest apologies for the lack off communication, I'm going to make a commitment to update my blog once a week.

  18. Flirc presses keys without me using the remote

    in Firmware Bugs

    Posted

    I see the problem, you definitely have spurious signals recorded.

    You have 5 signals paired with Backspace

    You also have two signals paired with 'i'

    I deleted all instances of those, please record backspace and 'i' again.

    Remember, if the GUI says successfully recorded and you don't feel like you've recorded the key, hit the 'delete' button and wait for that same signal to be deleted. I'm going to fix this in the next firmware release. Find the modified config attached. Let me know how it goes.

    MJMC_modified_config.bin

  25. Can't get sensitivity to work

    in Remote Controls

    Posted

    Thank you Chris for responding while I've been out of town.

    Yes, I agree, from the above post you mentioned you only thought you had to close the GUI and re-open it. Did you unplug and re-plug in the flirc. No need to close the GUI.

    Here is how it actually works. The sensitivity changes my algorithm to make things a bit more 'sensitive'. This actually gets stored as a configuration bit, so if you were to save your configuration from the GUI, this 'sensitivity' would be embedded in the GUI. Configuration values only get 'loaded' when you turn on the device. I should have also changed the firmware to load new values when they change, although easy, I have to many firmware images floating around to create another one.

    For each sensitivity, you need to record new button presses. The algorithm changes the capturing of remote signals, so they may not match the ones already saved on the device, which is why you have to re-record.

    However, having said that, you don't really have to format. Your previous sensitivity values are still saved, and 'shouldn't conflict with the new ones. It's good practice to start clean again, but you can switch back and forth once saved only having to unplug and plug.

    Also, what remote are you using? Can you post your configuration at each sensitivity? Please format in-between as I wont be able to distinguish which saved button was at which sensitivity.

×
×
  • Create New...