[ do default stuff if no widgets ]

SDK Release, Linux, RPi, IR Transmit Support

Linux Updates

Over this past week I’ve re-written my linux deployment scripts. It was brought to my attention that things weren’t working right. A number of errors related to packages not being signed and trusted, which was fine on older versions of linux, but newer versions of debian weren’t having it. Also in combination with the released of the SDK, this had to get done.

I’ve also cleaned up the installation instructions and am now building standalone versions for users without debian. Not quite enough time to try and do RPM support, but it is planned. This should be more than sufficient for now. I’ll need to throw some instructions in the standalone version, but at least I have something up versus nothing at all.

You can find all this on the linux downloads page.

Raspberry Pi Release

As part of the linux deployment scripts, I’ve also taken the time to do one for the raspberry pi. Now the raspberry pi has it’s own apt repository, commandline version, and GUI. Long overdue. This was also a necessary step in order to build a static library for the released SDK.

SDK Release

We build all the flirc software around the SDK. So everyone can grab the SDK on the Flirc github page.

Needed is a lot of documentation. However, this is 99% identical to the same flirc_util cli that ships with the GUI. The only thing that’s not identical is the version command, which I’ll address later. But it serves as a complete example to integrating flirc pairing into your own application.

The libraries will be updated as part of GUI releases. It’s all part of the same build scripts. You’ll notice a lot of erroneous commits, that was just me working on my deployment scripts. That will stop.

Still needed is a python/perl wrapper, dynamic libs, a windows lib, and some better documentation.

IR Transmit Support

One of the new features on the new flirc is the ability to transmit IR code. There is a very small transmitter in flirc, it’s power isn’t the best, but it could certainly be useful for some home automation. I have some better features planned regarding this, but for now, an initial release is ready for users to start playing with. It only works with raw code right now and doesn’t understand protocol. The format is a comma delimited list of edges, that coincidentally can be retrieved with the GUI. Enable IR Debugging, hit a button on your remote, and you’ll get your list of edges. The :e:<num> is the delay in ms seen between packets. A big number means you haven’t hit the button in a while.

The latest API supports sending IR through a simple interface:

The commandline also supports sending a packet out with the exact list of edges seen.

Example code in the SDK is fairly straight forward, it parses the list of comma delimited edges, checks for errors, puts it in a buffer, and calls the api:

For the IR transmit to work, you’ll need firmware version v4.2.+

I’ll post this in the forums somewhere, or you can email me, but I expect to release this publicly in about a week after I do some more testing.


9 Responses to “SDK Release, Linux, RPi, IR Transmit Support”

  1. Jawa Says:

    Hello Jason,
    a question..just describing my planned use case:
    -flirc on a Pi3.
    -remote control Xfinity remote
    I want to receive Xfinity remote presses through Flirc IR receiver and simply transmit those code out using FLIRC IR
    while true:
    receive code through IR
    transmit code through transmitter
    is this use case scenario possible at all ? thought I would ask before I purchase and try out flirc.
    thanks a lot sir,

  2. Jason Kotzin Says:

    Yes absolutely. And I just pushed out the update, so it’s all public. Just a note, IR transmitter isn’t all that powerful, about 6-8 feet. Line of site. It’s only 2cm small.

  3. Jawa Says:

    Enable IR Debugging:
    how would I do this ?
    I downloaded the Linux download and launched flirc. I dont see this in the menu !

    Thanks !

  4. JAWA Says:

    I figured out the Enable IR debugging thing.
    Also I now have a windows computer at my disposal
    so you don’t have to waste time on the ubuntu question
    taking it for a test drive now !

  5. JAWA Says:

    So i captured from my stb remote like in the example you have given above.
    Firmware is 4.2.1
    I tried transmitting it standing right opposite the set top box receiver
    but the stb did not register anything from flirc transmitter
    tried several times.
    please let me know when you get a chance..just would like this to work for me !

  6. JohnR Says:

    I just ordered my FLIRC dongle can’t wait for it to get here. I plan on using it primarily for the transmit feature and hoping to incorporate it into my next Raspberry Pi Zero W project. In the mean time I would like to start getting up to speed on the API. From what I can tell it looks like the API is a C++ include file. Is this correct? Can you describe what the development environment should look like on a Raspberry Pi (running Raspbian Stretch Lite)? Any pointers on requirements will be helpful. I have read all the documentation I can find so if I missed it somewhere my apologies just point me in the direction and I will get going.

    I do most of my coding in Node.js so I want to write drivers for my FLIRC that can be called by node. I can issue command line calls if I have too but I would rather use your API.


  7. Flo Says:

    Can the IR transmit feature be interfaced with LIRC on Linux (rasbian/rpi 3)?

  8. Jason Kotzin Says:

    I don’t know what this means. But most likely.

  9. Flo Says:

    Sorry, I should have been a bit more clear! I wanted to know whether the FLIRC usb dongle is recognized as a supported device in LIRC ( I currently have a home made device plugged in the GPIO port of my raspberry pi, but I’m looking for something cleaner and easily portable to a different system, and FLIRC seems a good candidate. That is, if it is recognized out of the box as a valid hardware by LIRC.

Leave a Reply