jason

Administrators
  • Content count

    2,221
  • Joined

  • Last visited

  • Days Won

    99

Everything posted by jason

  1. load mine. I fixed yours. I need to figure out how to fix this going forward. normalized.fcfg
  2. built in but not exposed. Probably will be release next week.
  3. I got excited. Oh well. Fuck LIRC.
  4. yup, pm me id and pw.
  5. we can setup a remote session. I'll take a look. Let me know.
  6. Flirc - interface 0. You want to remove it for that interface. Only want it for interface 1
  7. Did you use zadig? If you did, you might have used it on both interfaces, in which case you would have accidentally done it on the keyboard interface.
  8. when you record, does it say recorded successfully ? If you record the key again, does it work, or say, error, button exists?
  9. what's it say on the remote that doesn't work? Close the gui, usualy it's holding the device open.
  10. You're able to record buttons? Only some buttons will work in a text editor, try the enter keys and arrow keys.
  11. make sure you also wired the P+/P- signals to your motherboard.
  12. That's correct. No device logging on the streacom edition of the remote. You can pair all your buttons as normal, and then use the GUI to program the button on your remote to use as the power button.
  13. Your GUI is currently detecting the firmware at version 3.9.0?
  14. Wahoo, I'd be up for that. Yeah, would love to find out some more information about that, any chance you know where I can find some? Most of the time, I have to find that I have to pull apart existing firmware/etc, and I'm not in a position to reverse engineer anything time wise.
  15. No, but you should see that every other button press on your remote works. This is because your remote sends out alternating patterns every time you press a button. So you have to record all the buttons twice. Record up. Record up. Record left, record left. etc. Problem should go away.
  16. They are not configs. They are firmware images. File-upgrade firmware
  17. your remote sends out two different signals per button. Also, use the attached firmware, this is burning both our times. (disabling built in profiles). Check which sku your device is in file->advanced. dori.release-4.1.3.bin nemo.release-4.1.3.bin
  18. Good start, but you need to record your buttons twice. Looks like they are only there once. Sorry this has been so much trouble.
  19. http://cl.flirc.io/lbOd several buttons have issues. When you record, press and hold the button. It needs to see the second packet and when it doesn't, it saves a generic delay, which is 130. The Interkey delay is actually shorter than 130 on this remote, so it thinks you are lifting up and pressing the button again. In other words, flirc_util settings, or filrc_util.exe settings find all the buttons with 130, and delete them, and re-record them. Problem will go away. I need to make a way to edit configs in the GUI, actually not very easy. I'm not good at the GUI stuff.
  20. Please post your configuration file.
  21. one of the major reasons I haven't done this is because of windows. Fuck windows. I spent half my time with the first generation working on stupid driver issues, signing inf's and windows not correctly installing them. It's a gigantic waist of time and I lost a lot of sleep over it. Unless I figure out how to show up as a serial device in windows without a driver, I'm not in a position to do this. I'm working on finishing features for flirc gen2 and new products. I also haven't found a protocol definition for LIRC and UART. I also don't want to be in a position to be debugging LIRC. After all, Flirc stands for F[uck] LIRC. Built entirely out of my frustration with it. Flirc is an embodiment of "This shouldn't be this hard"
  22. You did the right thing clear your config. Record your buttons. That should be it. Explanation: If you clear your config, you'll notice your remote still works. That's because it's using the built in profile. When you record those buttons, you are effectively recording over the built in profile.
  23. http://cl.flirc.io/lbOz http://cl.flirc.io/lbXw It's a chrooted environment in my debian distro. Yeah strange that it's not really complaining that hard about the security ID. I do sign the package. You want to try it again, I issued an update yesterday. Perhaps the last release wasn't good?