Jump to content
Flirc Forums

jason

Administrators
  • Posts

    2,744
  • Joined

  • Last visited

  • Days Won

    118

Posts posted by jason

  1. This is the right version, but what you send definitely does matter. I'm sorry I don't have better logging:

    try this

    flirc_util.exe sendir --ik=23000 --repeat=3 --pattern=0,9071,4404,596,473,593,1579,569,1598,570,1600,604,464,590,1581,583,1627,551,1623,529,1597,592,1578,572,1600,574,545,526,490,581,500,572,494,578,1600,574,1578,585,1605,553,495,575,1595,577,491,582,496,623,449,570,507,553,1617,573,473,574,541,526,1597,577,1598,571,1650,526,525,547,498,573

  2. 5 hours ago, Knight77 said:

    Hi I've updated the Flirc 2nd gen to last firmware and also updated the program to the last version and now in Windows 10 it cannot record any key anymore.

    Any solution? 

    Thanks!

    Can you give me any more detail? If you go to enable device log, can you hit some buttons on your remote and paste the result?

     

  3. 42 minutes ago, justwantthistowork said:

    Yes, it does say successfully recorded. I actually never had any issues with the FLIRC software detecting key presses when it showed FLIRC in the connected state.

    I tried text editors, multiple media applications, web browsers, etc. with the button and nothing was ever sent to any window.

    Also yes as to it providing the "already recorded" error upon attempts to assign a second time.

    I've also tried the up, down, left, right, enter, and backspace keys on a separate trial attempt. Same results -- nothing works.

    Did you by any chance use the zadig driver utility?

  4. The windows virus thing is a problem, I don’t know why it says that. I wrote all the code.  I didn’t write any viruses. Chrome/firefox upload the binary to a third party, and it passes 15 checks, and one fails. It’s stupid. I don’t know how to fix it. 

    Everything looks like it’s working.


    When you hit ‘record a’ it says successfully recorded?

    It doesn’t always highlight on the virtual keyboard after you press it. It’s hit or miss.

    Fire up a text editor, and press the button you paired on your remote to see if it’s sent to the text editor as ‘a’.

    If you try to record the same button again on your remote, does it say, ‘error, already recorder?’

    You haven’t done anything wrong.

     

  5. https://github.com/flirc/sdk/blob/master/libs/flirc/flirc.h

     

      * fl_transmit_raw() sends a raw packet. Only supported on flirc gen2 hardware
      *
      * @param buf data to transmit, please be responsible, numbers are in
      * micro seconds
      * @param len length of buffer, don't send more than 100 bits, must be
      * even number of bits (edges).
      * @param ik delay to use inbetween packets. Required.
      * Defaults to 40ms if to low.
      * @param repeat repeat count, generally should be 3, 0 is infinit until
      * stopped, currently not supported.
      *
      * @return EOK
      * @return -1 error
      */
      int _DLL fl_transmit_raw(uint16_t *buf, uint16_t len, uint16_t ik, uint8_t repeat);
     

     

  6. I don’t have time to support it right now. It’s all possible through scripting, and quite honestly, I’m not pleased with the transmitter. I’m working on integrating a much higher power transmitter in the next generation. You need line of site, 6 feet max. It’s not good.

  7. I’m sorry, what is the ‘core’? Can you send me a direct message, and we can do a chat session so I can help you more in real time. I’m sure this is frustrating, and I’m sorry. It’s just me, and I can’t get anyone to the office to help me because of the pandemic, and I’m overloaded with a ton of bullshit work that eats most of my day.

  8. There is a whole lot in here I don’t understand. 
     

    flirc just translates remote buttons as keyboard keys. If a keyboard works, flirc will work. 
     

    try a keyboard. If that doesn’t work, something is wrong. 
     

    I don’t understand the need to setup flirc and then set it up again a second time ( the first manually recording and the second with harmony). What am I missing?

  9. 1 hour ago, 66LUX said:

     

    I'm not sure if you wanted to see if the Shield + Flirc combination having issues with the laptop nearby, or if you wanted the laptop + Flirc combination having issues with the phone nearby. Either way, I couldn't get any adverse reaction no matter which way I connected it.

     

     

    If I understand, the issue is not reproducible with a laptop. Leads me to believe you have a shielding issue, EMI issue, or just a grounding issue. If your ground isn’t good on the firetv, this would happen. 
     

    The IR sensor is sensitive, I’ve seen it spam out crap when the ground has noise 

     

    1 hour ago, 66LUX said:

    Strangely though, before your last post, I plugged the Flirc into my PC and performed a firmware update (I think that would effectively reset the Flirc USB). The version was the same as what was already on the Flirc USB, but since I reconnected it to the Shield (I still had to re-record the button mappings) it has not had the same power cycle issue. 

     

    If you had to relearn keys, then you definitely didn’t have the same firmware version. In fact, this was probably it. Nvidia changed a bunch of stuff in their usb report ID requirements. I updated the firmware and relearning keys were required. 
     

    you were probably on the old incompatible firmware. You weren’t prompted to update automatically when you started the app? This has to be it. You would get erratic behavior with the older firmware. 
     

  10. 2 hours ago, 66LUX said:

    Even without an extension, it still interferes if I bring the phone close enough. It also kind of defeats the purpose if I have to point the harmony accurately enough to make sure the signal bounces off the back of a shelf in my entertainment unit. It really should face forward.

    Considering the interference from the vacuum cleaner as well, I'm inclined to forget the whole thing, disconnect the Flirc and learn to juggle two remotes. The Shield was too expensive to risk damaging it from the rapid on/off sequences. It would have been so much easier if the Shield had just had IR like the older models. Thanks for your help anyway.

    Cheers, Dale

    Do you get the same noise on your laptop in the same room?

  11. God logitech sucks. Hang in there, I think something might be coming soon to put them to fucking shame...

    But for now, remove all this from logitech. Add a Samsung or Panasonic device to the logitech, rename it flirc. Add whatever device is NOT in your room. In other words, if you have a samsung, don't add the samsung.

    Now once that's added. Open up my software, go to the NVIDIA controller, and pair each key manually.

    Then go to advanced, disable all the built in profiles.

    Don't have roomba on as you're doing any of this.

    Let me know how that goes. 

×
×
  • Create New...