Jump to content
Flirc Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


jason last won the day on July 2

jason had the most liked content!

Community Reputation

167 Excellent

About jason

  • Rank

Profile Information

  • Gender
  • Location
    Santa Clara
  • Interests
    flirc, that's all I have time for.

Recent Profile Visitors

15,327 profile views
  1. Did you by any chance use the zadig driver utility?
  2. 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.
  3. I see you emailed me too, can you also post a dmesg when the device stops working?
  4. 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);
  5. Send over your config. Probably accidentally recorded noise, we can delete it.
  6. You use the GUI to capture the IR waveform, and use the CLI or SDK to retransmit that same waveform. Only the 38khz frequency is supported.
  7. 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.
  8. 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.
  9. Is it possible your keyboard language is not us on one of the machines?
  10. 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?
  11. Just shoot me a email at the support website, I'll drop some in the mail for you. I do it all the time.
  12. Just keep me posted and let me know if it seems fixed.
  13. 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 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.
  • Create New...