Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by jason

  1. Are you learning the remote?

    If you have your old batteries, can you do something.

    Hook Flirc up to the PC, fire up my application, and  go to advanced, and enable IR debugging. 

    Press and hold a button a couple times, the same one. Save the log. 

    Clear the log, put the old batteries in, and do it again, save the log to a different file. Remember, when you are doing this, don’t hold the remote close to flirc, point it at the ceiling, simulate the distance of the actual setup. Let me take a look at the logs.

  2. I really fucked up, I'm sorry. I'll get you a new board, I'm sorry it got messed up while you were waiting.

    I updated github with better instructions, a quick fix to samd targets, and binaries. I also included schematics.

    I don't do much work on this. I am so overwhelmed with this new product. Harmony competitor. Massive project. Years in the making. Starting production shortly. Still a lot to do but it's all quickly coming together.

  3. On 4/15/2021 at 2:22 AM, igaroka said:

    Hi gents

    I have a corporate request to develop custom feature
    We need AIO device: Flirc + USB Flash Drive (64-128 GB)

    Is it possible? What's MOQ?

    Kindly contact me via email

    Need a lot more information. What is the required speed of flash? It won’t fit in the current case. Does it need a new enclosure? If it’s a product, Min engineering time, cad, fcc/CE certifications, prototypes, packaging, test fixtures, etc, a lot. 

  4. This is an NEC code:

    This is the timing marker for the button:


    This is the elapsed time in between the next signal it receives: e40 <-- 40ms

    This is specific to the NEC specification which stands for repeat the last thing you saw: 0,9041,2181,621

    Here is the commandline:

    sendir --pattern=0,153,1231,131 --repeat=3 --ik=32000

    So the first is the pattern, how many times we want to repeat the pattern, and the time between the signals. In the case above, it is 

    0,153,1231,131 (wait 32ms) 0,153,1231,131 (wait 32ms) 0,153,1231,131

    But for NEC, it gets tricky, because the follow-up pattern is simply no the first. So for this, we have a few options.

    Send the first packet only once:

    flirc_util sendir --pattern=0,9043,4430,652,1563,651,439,622,465,625,465,622,465,621,465,626,465,621,465,621,469,622,1589,625,1589,626,1589,644,1571,648,1563,626,1590,626,1589,647,1563,652,439,621,465,622,469,621,465,621,465,626,465,622,465,621,469,622,1589,626,1589,622,1589,652,1563,626,1590,621,1590,651,1564,626

    Send the first packet a few times:

    flirc_util sendir --pattern=0,9043,4430,652,1563,651,439,622,465,625,465,622,465,621,465,626,465,621,465,621,469,622,1589,625,1589,626,1589,644,1571,648,1563,626,1590,626,1589,647,1563,652,439,621,465,622,469,621,465,621,465,626,465,622,465,621,469,622,1589,626,1589,622,1589,652,1563,626,1590,621,1590,651,1564,626 --ik=40000 --repeat=3

    Or alter the signal so that the first includes the repeat signal. The initial 0 is the timing marker, we remove that, so it becomes:

    0,9043,4430,652,1563,651,439,622,465,625,465,622,465,621,465,626,465,621,465,621,469,622,1589,625,1589,626,1589,644,1571,648,1563,626,1590,626,1589,647,1563,652,439,621,465,622,469,621,465,621,465,626,465,622,465,621,469,622,1589,626,1589,622,1589,652,1563,626,1590,621,1590,651,1564,626 + 400000,9041,2181,621 ->

    flirc_util sendir --pattern=0,9043,4430,652,1563,651,439,622,465,625,465,622,465,621,465,626,465,621,465,621,469,622,1589,625,1589,626,1589,644,1571,648,1563,626,1590,626,1589,647,1563,652,439,621,465,622,469,621,465,621,465,626,465,622,465,621,469,622,1589,626,1589,622,1589,652,1563,626,1590,621,1590,651,1564,626,40000,9041,2181,621,40000,9041,2181,621,40000,9041,2181,621

  • Create New...