Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by jason

  1. 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);
  2. Send over your config. Probably accidentally recorded noise, we can delete it.
  3. 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.
  4. 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.
  5. 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.
  6. Is it possible your keyboard language is not us on one of the machines?
  7. 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?
  8. Just shoot me a email at the support website, I'll drop some in the mail for you. I do it all the time.
  9. Just keep me posted and let me know if it seems fixed.
  10. 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.
  11. To clarify, when the laptop is on battery, not plugged in.
  12. Do you get the same noise on your laptop in the same room?
  13. don't use an extension chord, it might be the extension chord more than the phone.
  14. 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.
  15. 1. The config is applied to the dongle, not on the computer. 2. Yes, it stays with the dongle when moved 3. Yes, install on the destination machine, or you can reach out to me directly, and if planned together, you can purchase custom units pre-loaded in white label boxes.
  16. Nothing I can do about two. You need to learn without your phone present, and then it should work fine. Can you confirm?
  17. Yeah that’s really interesting about the phone. I wouldn’t have suspected that. Sensitivity is the same. It’s the same sensor. A better algorithm. It’s not as responsive because it’s less “slippery”. It’s more consistent about button presses and when you let go real quick or when you are holding it down. i don’t follow the remaining problems. Can you summarize?
  18. Go to File->Device Logging. Enable device logging. Let's see what kind of noise it's picking up.
  19. Yes, unfortunately this is a version 2 only feature. It definitely wont work on version 1 due to various limitations, and I have no intention on doing anything other than maintenance releases for gen1 devices.
  20. It's not the CLI that needed to be updated, but the firmware No guarantee this will break something else. I've updated the report ID so that you can go as high as 255. Try it and let me know. dori.release-4.9.4.bin nemo.release-4.9.4.bin
  21. no, it wouldn't be in the HID table, it would be in the consumer table, which is a valid system wide table for system control, and should work. My keyboard report is limited to 101, artificially. I could extend this, but I would need to look into the impact. Anything above 231 is reserved.
  22. On my GUI, go to controllers->media keys. There is a suspend key there. Try that, and let us know.
  • Create New...