Repository files navigation

• Supported IR Protocols
• Common problem with IRremote
• Using the new library version for old examples
  • New features of version 4.5
  • New features of version 4.x
  • New features of version 3.x
  • Converting your 2.x program to the 4.x version
  • How to convert old MSB first 32 bit IR data codes to new LSB first 32 bit IR data codes
  • Errors when using the 3.x versions for old tutorials
  • Staying on 2.x
• Why *.hpp instead of *.cpp
• Using the new *.hpp files
• Tutorials
• 3 ways to specify an IR code
• IRReceiver pinouts
• Receiving IR codes
  • decodedIRData structure
  • Ambiguous protocols
  • RAM usage of different protocolsl
  • Handling unknown Protocols
    • Disclaimer
    • Other libraries, which may cover these protocols
    • Protocol=PULSE_DISTANCE
    • Protocol=UNKNOWN
    • How to deal with protocols not supported by IRremote
• Sending IR codes
  • Sending UNKNOWN protocol
  • Sending IRDB IR codes
  • Send pin
  • Polarity of send pin
    • List of public IR code databases
• Tiny NEC receiver and sender
• The FAST protocol
• FAQ and hints
  • Receiving stops after analogWrite() or tone() or after running a motor
  • Receiving sets overflow flag
  • Problems with Neopixels, FastLed etc.
  • Does not work/compile with another library
  • Multiple IR receivers
  • Multiple IR sender instances
  • Increase strength of sent output signal
  • Simulate an IR receiver module
  • Minimal CPU clock frequency
  • Bang & Olufsen protocol
• Examples for this library
• WOKWI online examples
• IR control of a robot car
• Issues and discussions
• Compile options / macros for this library
  • Changing include (*.h) files with Arduino IDE
  • Modifying compile options with Sloeber IDE
• Supported Boards
• Timer and pin usage
  • Incompatibilities to other libraries and Arduino commands like tone() and analogWrite()
  • Hardware-PWM signal generation for sending
  • Why do we use 30% duty cycle for sending
• How we decode signals
• NEC encoding diagrams
• Quick comparison of 5 Arduino IR receiving libraries
• History
• Useful links
• Contributors
• License
• Copyright

NEC / Onkyo / Apple    Denon / Sharp    Panasonic / Kaseikyo

JVC    LG    RC5    RC6    Samsung    Sony    Marantz

Universal Pulse Distance    Universal Pulse Width     Universal Pulse Distance Width

Hash    Pronto

BoseWave    Bang & Olufsen    Lego    FAST    Whynter    MagiQuest    Velux

Protocols can be switched off and on by defining macros before the line#include <IRremote.hpp> likehere:

#defineDECODE_NEC//#define DECODE_DENON#include<IRremote.hpp>

Or"I build a gadged with 2 motors controlled by IR and theIR stops after the first motor command".
This is due to the fact, that the motor control by AnalogWrite() uses the same timer as IR receiving.
Seethis table for the list of timers and pins.

This library has been refactored, breaking backward compatibility with the old version, on which many examples on the Internet are based.

• Support formultiple receiver instances.
  irparams_struct irparams is now member ofIRrecv. ThusrawDataPtr (pointer to irparams) was removed fromIrReceiver.decodedIRData.
  OldIrReceiver.decodedIRData.rawDataPtr->rawbuf is nowIrReceiver.irparams.rawbuf, the same holds forIrReceiver.irparams.rawlen.
• LED feedback is always enabled for sending. It can only be disabled by using#define NO_LED_SEND_FEEDBACK_CODE or#define NO_LED_FEEDBACK_CODE.
• The second parameter of the functionIrSender.begin(uint_fast8_t aSendPin, bool aEnableLEDFeedback) has changed touint_fast8_t aFeedbackLEDPin. Therefore this function call no longer works as expected because it uses the old boolean value of e.g.ENABLE_LED_FEEDBACK which evaluates to true or 1 as pin number of the LED feedback pin number.
• New experimental Velux send function.
• Send function for Marantz version of the RC5x protocol. This protocol has an additional 6 bit command extension and adds a short pause after the address is sent to identify this variant of the protocol.

• Since 4.3IrSender.begin(DISABLE_LED_FEEDBACK) will no longer work, use#define NO_LED_SEND_FEEDBACK_CODE instead.
• New universalPulse Distance / Pulse Width / Pulse Distance Width decoder added, which covers many previous unknown protocols.
• Printout of code how to send received command byIrReceiver.printIRSendUsage(&Serial).
• RawData type is now 64 bit for 32 bit platforms and thereforedecodedIRData.decodedRawData can contain complete frame information for more protocols than with 32 bit as before.
• Callback after receiving a command - It calls your code as soon as a message was received.
• Improved handling ofPULSE_DISTANCE +PULSE_WIDTH protocols.
• New FAST protocol.
• Automatic printout of thecorresponding send function withprintIRSendUsage().

• You must replace#define DECODE_DISTANCE by#define DECODE_DISTANCE_WIDTH (only if you explicitly enabled this decoder).
• The parameterbool hasStopBit is not longer required and removed e.g. for functionsendPulseDistanceWidth().

• Any pin can be used for receiving and ifSEND_PWM_BY_TIMER is not defined also for sending.
• Feedback LED can be activated for sending / receiving.
• An 8/16 bit **command value as well as an 16 bitaddress and a protocol number is provided for decoding (instead of the old 32 bit value).
• Protocol values comply toprotocol standards.
  NEC, Panasonic, Sony, Samsung and JVC decode & send LSB first.
• SupportsUniversal Distance protocol, which covers a lot of previous unknown protocols.
• Compatible withtone() library. See theReceiveDemo example.
• Simultaneous sending and receiving. See theSendAndReceive example.
• Supportsmore platforms.
• Allows for the generation of non PWM signal to justsimulate an active low receiver signal for direct connect to existent receiving devices without using IR.
• Easy protocol configuration,directly in yoursource code.
  Reduces memory footprint and decreases decoding time.
• Contains avery small NEC only decoder, whichdoes not require any timer resource.

-> Feature comparison of 5 Arduino IR libraries.

Starting with the 3.1 version,the generation of PWM for sending is done by software, thus saving the hardware timer andenabling arbitrary output pins for sending.
If you use an (old) Arduino core that does not use the-flto flag for compile, you can activate the line#define SUPPRESS_ERROR_MESSAGE_FOR_BEGIN in IRRemote.h,if you get false error messages regarding begin() during compilation.

• IRreceiver andIRsender object have been added and can be used without defining them, like the well known ArduinoSerial object.

• Just remove the lineIRrecv IrReceiver(IR_RECEIVE_PIN); and/orIRsend IrSender; in your program and replace all occurrences ofIRrecv. orirrecv. withIrReceiver and replace allIRsend orirsend withIrSender.

• Like for the Serial object, callIrReceiver.begin(IR_RECEIVE_PIN, ENABLE_LED_FEEDBACK)orIrReceiver.begin(IR_RECEIVE_PIN, DISABLE_LED_FEEDBACK) instead of theIrReceiver.enableIRIn() orirrecv.enableIRIn() in setup().
  If IR_SEND_PIN is not defined (before the line#include <IRremote.hpp>) you must use e.g.IrSender.begin(3);

• Olddecode(decode_results *aResults) function is replaced by simpledecode(). So if you have a statementif(irrecv.decode(&results)) replace it withif (IrReceiver.decode()).

• The decoded result is now in inIrReceiver.decodedIRData and not inresults any more, therefore replace any occurrences ofresults.value andresults.decode_type (and similar) toIrReceiver.decodedIRData.decodedRawData andIrReceiver.decodedIRData.protocol.

• Overflow, Repeat and other flags are now inIrReceiver.receivedIRData.flags.

• Seldom used:results.rawbuf andresults.rawlen must be replaced byIrReceiver.irparams.rawbuf andIrReceiver.decodedIRData.rawlen.

• The 5 protocolsNEC, Panasonic, Sony, Samsung and JVC have been converted to LSB first. Send functions for sending old MSB data were renamed tosendNECMSB,sendSamsungMSB(),sendSonyMSB() andsendJVCMSB().The oldsendSAMSUNG() andsendSony() MSB functions are still available.The old MSB version ofsendPanasonic() function was deleted, since it had bugs nobody recognized and therefore was assumed to be never used.
  For converting MSB codes to LSB seebelow or use the new functionsbitreverseOneByte() orbitreverse32Bit() for reversing.

#include<IRremote.h>#defineRECV_PIN2IRrecvirrecv(RECV_PIN);decode_results results;voidsetup(){...  Serial.begin(115200);// Establish serial communication  irrecv.enableIRIn();// Start the receiver}voidloop() {if (irrecv.decode(&results)) {      Serial.println(results.value, HEX);      ...      irrecv.resume();// Receive the next value  }  ...}

#include<IRremote.hpp>#defineIR_RECEIVE_PIN2voidsetup(){...  Serial.begin(115200);// // Establish serial communication  IrReceiver.begin(IR_RECEIVE_PIN, ENABLE_LED_FEEDBACK);// Start the receiver}voidloop() {if (IrReceiver.decode()) {      Serial.println(IrReceiver.decodedIRData.decodedRawData, HEX);// Print "old" raw data      IrReceiver.printIRResultShort(&Serial);// Print complete received data in one line      IrReceiver.printIRSendUsage(&Serial);// Print the statement required to send this data      ...      IrReceiver.resume();// Enable receiving of the next value  }  ...}

For more, see theUnitTest log.

Protocol=NEC Address=0xF1 Command=0x76 Raw-Data=0x89760EF1 32 bits LSB firstSend with: IrSender.sendNEC(0xF1, 0x76, <numberOfRepeats>);Protocol=Kaseikyo_Denon Address=0xFF1 Command=0x76 Raw-Data=0x9976FF10 48 bits LSB firstSend with: IrSender.sendKaseikyo_Denon(0xFF1, 0x76, <numberOfRepeats>);

For the new decoders forNEC, Panasonic, Sony, Samsung and JVC, the resultIrReceiver.decodedIRData.decodedRawData is nowLSB-first, as the definition of these protocols suggests!

To convert one into the other, you must reverse the nibble (4 bit / Hex numbers) positions and then reverse all bit positions of each nibble or write it as one binary string and reverse/mirror it.
This can be done by using the new functionsbitreverseOneByte() orbitreverse32Bit().

0xCB 34 01 02 MSB value
0x20 10 43 BC after nibble reverse
0x40 80 2C D3 LSB value after bit reverse of each nibble

 0->0   1->8   2->4   3->C 4->2   5->A   6->6   7->E 8->1   9->9   A->5   B->D C->3   D->B   E->7   F->F

If youread the first binary sequence backwards (right to left), you get the second sequence.
0xCB340102 is binary1100 1011 0011 0100 0000 0001 0000 0010.
0x40802CD3 is binary0100 0000 1000 0000 0010 1100 1101 0011.

Use thistool provided by analysir.

Sending old MSB codes without conversion can be done by usingsendNECMSB(),sendSonyMSB(),sendSamsungMSB(),sendJVCMSB().

If you suffer from errors with old tutorial code includingIRremote.h instead ofIRremote.hpp,just try to rollback toVersion 2.4.0.
Most likely your code will run and you will not miss the new features.

Consider using theoriginal 2.4 release form 2017or the last backwards compatible2.8 version for you project.
It may be sufficient and deals flawlessly with 32 bit IR codes.
If this doesn't work for you, you can be sure that 4.x is trying to be compatible with earlier versions, so your old examples should work just fine.

• Only the following decoders are available:
  NEC    Denon    Panasonic    JVC    LG
RC5    RC6    Samsung    Sony
• The call ofirrecv.decode(&results) uses the old MSB first decoders like in 2.x and sets the 32 bit codes inresults.value.
• No decoding to a more meaningful (constant) 8/16 bit address and 8 bit command.

Every *.cpp file is compiled separately by a call of the compiler exclusively for this cpp file. These calls are managed by the IDE / make system.In the Arduino IDE the calls are executed when you click onVerify orUpload.

And nowour problem with Arduino is:
How to setcompile options for all *.cpp files, especially for libraries used?
IDE's likeSloeber orPlatformIO support this by allowing to specify a set of options per project.They add these options at each compiler call e.g.-DTRACE.

But Arduino lacks this feature.So theworkaround is not to compile all sources separately, but to concatenate them to one huge source file by including them in your source.
This is done by e.g.#include "IRremote.hpp".

But why not#include "IRremote.cpp"?
If you try it, you will see lots of errors, because each function of the *.cpp file is now compiled twice:
first when the huge file is compiled, and second when the .cpp file is compiled separately, as described above.
Therefore, using the.cpp extension is no longer possible. One solution is to use the.hpp extension to indicate that it is an included .cpp file.
Any other extension would work, e.g.cinclude, buthpp seems to be common sense.

In order to supportcompile options more easily,youmust use the statement#include <IRremote.hpp> instead of#include <IRremote.h> in your main program (aka *.ino file with setup() and loop()).

Inall other files you must use the following, topreventmultiple definitions linker errors:

#defineUSE_IRREMOTE_HPP_AS_PLAIN_INCLUDE#include<IRremote.hpp>

Ensure that all macros in your main program are defined before any#include <IRremote.hpp>.
The following macros will definitely be overridden with default values otherwise:

• RAW_BUFFER_LENGTH
• IR_SEND_PIN
• SEND_PWM_BY_TIMER

• A very elaborated introduction to IR remotes and IRremote library fromDroneBot Workshop.

There are 3 different ways of specifying a particular IR code.

The timing of each mark/pulse and space/distance_between_pulses is specified in a list or array.This enables specifyingall IR codes, but requires a lot of memory and isnot readable at all.One formal definition of such a timing array, includingspecification of frequency and repeats is thePronto format.
Memory can be saved by using a lower time resolution.For IRremote you can use a 50 µs resolution which halves the memory requirement by using byte values instead of int16 values.For receiving purposes you can use thehash of the timing provided by thedecodeHash() decoder.

There are 3 main encoding schemes which encodes a binary bitstream / hex value:

1. PULSE_DISTANCE. The distance between pulses determines the bit value. This requires always a stop bit!Examples are NEC and KASEIKYO protocols. The pulse width is constant for most protocols.
2. PULSE_WIDTH. The width of a pulse determines the bit value, pulse distance is constant. This requires no stop bit!The only known example is the SONY protocol.
3. Phase / Manchester encoding.The time of the pulse/pause transition (phase) relative to the clock determines the bit value. Examples are RC5 and RC6 protocols.

Phase encoding has aconstant bit length,PULSE_DISTANCE with constant pulse width andPULSE_WIDTH haveno constant bit length!

A well known example forPULSE_DISTANCE with non constant pulse width encoding is theRS232 serial encoding.Here the non constant pulse width is used to enable aconstant bit length.

Most IR signals have aspecial header to help in setting the automatic gain of the receiver circuit.This header is not part of the encoding, but is often significant for a special protocol and therefore must be reproducible.

Be aware that there are codes using aPULSE_DISTANCE encoding where more than a binary 0/1 is put into a pulse/pause combination.This requires more than 2 different pulse or pause length combinations.TheHobToHood protocol uses such an encoding.

Using encoding schemes reduces the specification of an IR code to a bitstream / hex value, which is LSB by default and pulse / pause timings of header, 0, and 1.The hex value isquite readable.These schemes can not put any semantics like address, command or checksum on this bitstream.

There are a few common protocols that are implemented directly in IRremote.They specify the frequency, the timings of header, 0, and 1 as well as other values like checksum, repeat distance, repeat coding, bit toggling etc.The semantics of the hex value is also specified, allowing the usage of only 2 parametersaddress andcommand to specify an IR code.This saves memory and ishighly readable.Often the address is also constant, which further reduces memory requirements.

Adafruit IR Sensor tutorial

In your program you check for acompletely received IR frame with:
if (IrReceiver.decode()) {}
This also decodes the received data.
After successful decoding, the IR data is contained in the IRData structure, available asIrReceiver.decodedIRData.

structIRData {decode_type_t protocol;// UNKNOWN, NEC, SONY, RC5, PULSE_DISTANCE, ...uint16_t address;// Decoded addressuint16_t command;// Decoded commanduint16_t extra;// Used for Kaseikyo unknown vendor ID. Ticks used for decoding Distance protocol.    IRRawDataType decodedRawData;// Up to 32 (64 bit for 32 bit CPU architectures) bit decoded raw data, used for send<protocol>Raw functions.#if defined(DECODE_DISTANCE_WIDTH)    DistanceWidthTimingInfoStruct DistanceWidthTimingInfo;// 12 bytes    IRRawDataType decodedRawDataArray[DECODED_RAW_DATA_ARRAY_SIZE];// 32/64 bit decoded raw data, to be used for sendPulseDistanceWidthFromArray functions.#endifuint16_t numberOfBits;// Number of bits received for data (address + command + parity) - to determine protocol length if different length are possible.uint8_t flags;// IRDATA_FLAGS_IS_REPEAT, IRDATA_FLAGS_WAS_OVERFLOW etc. See IRDATA_FLAGS_* definitions    IRRawlenType rawlen;// Counter of entries in rawbuf of last received frame.uint16_t initialGapTicks;// Contains the initial gap of the last received frame.};

This is thelist of flags contained in the flags field.
Check it with e.g.if(IrReceiver.decodedIRData.flags & IRDATA_FLAGS_IS_REPEAT).

auto myRawdata= IrReceiver.decodedIRData.decodedRawData;

The definitions for theIrReceiver.decodedIRData.flags are describedhere.

IrReceiver.printIRResultShort(&Serial);

IrReceiver.printIRResultRawFormatted(&Serial,true);`

The raw data depends on the internal state of the Arduino timer in relation to the received signal and might therefore be slightly different each time. (resolution problem).The decoded values are the interpreted ones which are tolerant to such slight differences!

IrReceiver.printIRSendUsage(&Serial);

TheNEC protocol is defined as 8 bit address and 8 bit command. But the physical address and data fields are each 16 bit wide.The additional 8 bits are used to send the inverted address or command for parity checking.
Theextended NEC protocol uses the additional 8 parity bit of address for a 16 bit address, thus disabling the parity check for address.
TheONKYO protocol in turn uses the additional 8 parity bit of address and command for a 16 bit address and command.

The decoder reduces the 16 bit values to 8 bit ones if the parity is correct.If the parity is not correct, it assumes no parity error, but takes the values as 16 bit values without parity assuming extended NEC or extended NEC protocol protocol.

But now we have a problem when we want to receive e.g. the16 bit address 0x00FF or 0x32CD!The decoder interprets this as a NEC 8 bit address 0x00 / 0x32 with correct parity of 0xFF / 0xCD and reduces it to 0x00 / 0x32.

One way to handle this, is to force the library toalways use the ONKYO protocol interpretation by using#define DECODE_ONKYO.Another way is to check ifIrReceiver.decodedIRData.protocol is NEC and not ONKYO and to revert the parity reducing manually.

On a long press, theNEC protocol does not repeat its frame, it sends a special short repeat frame.This enables an easy distinction between long presses and repeated presses and saves a bit of battery energy.This behavior is quite unique for NEC and its derived protocols like LG and Samsung.

But of course there are also remote control systems, that uses the NEC protocol but only repeat the first frame when a long press is made instead of sending the special short repeat frame. We named this theNEC2 protocol and it is sent withsendNEC2().
But be careful, the NEC2 protocol can only be detected by the NEC library decoderafter the first frame and if you do a long press!

On a long press, theSamsungLG protocol does not repeat its frame, it sends a special short repeat frame.

TheRAW_BUFFER_LENGTH determines the length of thebyte buffer where the received IR timing data is stored before decoding.
100 is sufficient for standard protocolsup to 48 bits, with 1 bit consisting of one mark and space.We always require additional 4 bytes, 1 byte for initial gap, 2 bytes for header and 1 byte for stop bit.

• 48 bit protocols are PANASONIC, KASEIKYO, SAMSUNG48, RC6.
• 32 bit protocols like NEC, SAMSUNG, WHYNTER, SONY(20), LG(28) require abuffer length of 68.
• 16 bit protocols like BOSEWAVE, DENON, FAST, JVC, LEGO_PF, RC5, SONY(12 or 15) require abuffer length of 36.
• MAGIQUEST requires a buffer length of112.
• Air conditioners often send a longer protocol data streamup to 750 bits.

If the record gap determined byRECORD_GAP_MICROS is changed from the default 8 ms to more than 20 ms, the buffer is no longer a byte but a uint16_t buffer, requiring twice as much RAM.

This library was designed to fit inside MCUs with relatively low levels of resources and was intended to work as a library together with other applications which also require some resources of the MCU to operate.

Use theReceiveDemo example to print out all informations about your IR protocol.
TheReceiveDump example gives you more information but has bad repeat detection due to the time required for printing the information.

If your protocol seems not to be supported by this library, you may try theIRMP library, which especially supports manchester protocols much better.

Forair conditioners , you may try theIRremoteESP8266 library, which supports an impressive set of protocols and a lot of air conditioners and works also on ESP32.

Raw-IR-decoder-for-Arduino is not a library, but an arduino example sketch, which provides many methods of decoding especiallyair conditioner protocols. Sending of these protocols can be done by the Arduino libraryHeatpumpIR.

If you get something like this:

PULSE_DISTANCE: HeaderMarkMicros=8900 HeaderSpaceMicros=4450 MarkMicros=550 OneSpaceMicros=1700 ZeroSpaceMicros=600  NumberOfBits=56 0x43D8613C 0x3BC3BC

then you have a code consisting of56 bits, which is probably from an air conditioner remote.
You can send it withsendPulseDistanceWidth().

uint32_t tRawData[] = {0xB02002,0xA010 };IrSender.sendPulseDistance(38,3450,1700,450,1250,450,400, &tRawData[0],48,false,0,0);

You can send it with callingsendPulseDistanceWidthData() twice, once for the first 32 bit and next for the remaining 24 bits.
ThePULSE_DISTANCE /PULSE_WIDTH decoder just decodes a timing stream to a bitstream stored as hex values.These decoders can not put any semantics like address, command or checksum on this bitstream.But the bitstream is way more readable, than a timing stream. This bitstream is readLSB first by default.If LSB does not suit for further research, you can change ithere.

If RAM is not more than 2k, the decoder only accepts mark or space durations up to 2500 microseconds to save RAM space, otherwise it accepts durations up to 10 ms.

If you see something likeProtocol=UNKNOWN Hash=0x13BD886C 35 bits received as output of e.g. the ReceiveDemo example, you either have a problem with decoding a protocol, or an unsupported protocol.

• If you have anodd number of bits received, your receiver circuit probably has problems. Maybe because the IR signal is too weak.
• If you see timings like+ 600,- 600 + 550,- 150 + 200,- 100 + 750,- 550 then one 450 µs space was split into two 150 and 100 µs spaces with a spike / error signal of 200 µs between. Maybe because of a defective receiver or a weak signal in conjunction with another light emitting source nearby.
• If you see timings like+ 500,- 550 + 450,- 550 + 450,- 500 + 500,-1550, then marks are generally shorter than spaces and thereforeMARK_EXCESS_MICROS (specified in your ino file) should benegative to compensate for this at decoding.
• If you seeProtocol=UNKNOWN Hash=0x0 1 bits received it may be that the space after the initial mark is longer thanRECORD_GAP_MICROS.This was observed for some LG air conditioner protocols. Try again with a line e.g.#define RECORD_GAP_MICROS 12000 before the line#include <IRremote.hpp> in your .ino file.
• To see more info supporting you to find the reason for your UNKNOWN protocol, you must enable the line//#define DEBUG in IRremoteInt.h.

If you do not know which protocol your IR transmitter uses, you have several choices.

• Just use the hash value to decide which command was received. See theSimpleReceiverForHashCodes example.
• Use theIRreceiveDemo example orIRreceiveDump example to dump out the IR timing.You can then reproduce/send this timing with theSendRawDemo example.
• TheIRMP AllProtocol example prints the protocol and data for one of the40 supported protocols.The same library can be used to send this codes.
• If you have a bigger Arduino board at hand (> 100 kByte program memory) you can try theIRremoteDecode example of the Arduino libraryDecodeIR.
• UseIrScrutinizer.It can automatically generate a send sketch for your protocol by exporting as "Arduino Raw". It supports IRremote,the oldIRLib andInfrared4Arduino.

If you have a device at hand which can generate the IR codes you want to work with (aka IR remote),it is recommended to receive the codes with theReceiveDemo example, which will tell you on the serial output how to send them.

Protocol=LG Address=0x2 Command=0x3434 Raw-Data=0x23434E 28 bits MSB firstSend with: IrSender.sendLG(0x2, 0x3434, <numberOfRepeats>);

You will discover thatthe address is a constant and the commands sometimes are sensibly grouped.
If you are uncertain about the numbers of repeats to use for sending,3 is a good starting point. If this works, you can check lower values afterwards.

If you have enabledDECODE_DISTANCE_WIDTH, the code printed byprintIRSendUsage()differs between 8 and 32 bit platforms,so it is best to run the receiving program on the same platform as the sending program.

All sending functions support the sending of repeats if sensible.Repeat frames are sent at a fixed period determined by the protocol. e.g. 110 ms from start to start for NEC.
Keep in mind, thatthere is no delay after the last sent mark.If you handle the sending of repeat frames by your own, you must insert sensible delays before the repeat frames to enable correct decoding.

Bear in mind, thatsome devices only accept commands if they are repeated one or two times.

Sendingold MSB codes without conversion can be done by usingsendNECMSB(),sendSonyMSB(),sendSamsungMSB(),sendJVCMSB()or byconverting them manually to LSB.

If the protocol is unknown by IRremote, which often is the case for airconditioner codes,you can store the timing sequence in an array and send it with IrSender.sendRaw() or IrSender.sendRaw_P()like done inSendDemo.Do not forget to send repeats.

The codes found in theFlipper-IRDB database are quite straightforward to convert, because the also use the address / command scheme.
Protocol matching is NECext -> Onkyo, Samsung32 -> Samsung, SIRC20 -> Sony with 20 bits etc.

The codes found in theirdb database specify adevice, asubdevice and afunction.Most of the times,device andsubdevice can be taken as upper and lower byte of theaddress parameter andfunctionis thecommand parameter for thenew structured functions with address, command and repeat-count parameterslike e.g.IrSender.sendNEC((device << 8) | subdevice, 0x19, 2).
Anexact mapping can be found in theIRP definition files for IR protocols."D" and "S" denotes device and subdevice and "F" denotes the function.

Any pin can be chosen as send pin as long asIR_SEND_PIN isnot defined.This is because the PWM signal is generated by default with software bit banging, sinceSEND_PWM_BY_TIMER is not active.
OnESP32 ledc channel 0 is used for generating the IR PWM.
IfIR_SEND_PIN is specified (as C macro), it reduces program size and improves send timing for AVR.If you want to use a variable to specify send pin e.g. withsetSendPin(uint8_t aSendPinNumber), you must disable thisIR_SEND_PIN macro e.g. with#undef IR_SEND_PIN.Then you can change send pin at any time before sending an IR frame.See alsoCompile options / macros for this library.

By default the polarity is HIGH for active and LOW for inactive or pause.This corresponds to the connection schema: Pin -> Resistor-> IR-LED -> Ground.
If you want to use the connection schema: VCC -> IR-LED -> Resistor -> Pin, you must specifyUSE_ACTIVE_LOW_OUTPUT_FOR_SEND_PIN.

http://www.harctoolbox.org/IR-resources.html

Flipper IRDB Database

For applications only requiring NEC, NEC variants or FAST -see below- protocol, there is a special receiver / sender included,which has verysmall code size of 500 bytes and does NOT require any timer.

Instead of sampling the input every 50 µs as IRremote does, TinyReceiver receiver uses apin change interrupt for on-the-fly decoding which limits the choice of protocols.
On each level change, the level and the time since the last change are used to incrementally decode the protocol.
With this operating principle, wecannot wait for a timeout and then decode the protocol as IRremote does.
Instead, we need to know which is the last bit (level change) of a protocol to do the final decodingand the call of the optionaluser provided callback functionhandleReceivedTinyIRData().
This means,we need to know the number of bits in a protocol and therefore the protocol (family).

Check out theTinyReceiver andIRDispatcherDemo examples.
Take care to includeTinyIRReceiver.hpp orTinyIRSender.hpp instead ofIRremote.hpp.

//#define USE_ONKYO_PROTOCOL    // Like NEC, but take the 16 bit address and command each as one 16 bit value and not as 8 bit normal and 8 bit inverted value.//#define USE_FAST_PROTOCOL     // Use FAST protocol instead of NEC / ONKYO#include"TinyIRReceiver.hpp"voidsetup() {initPCIInterruptForTinyReceiver();// Enables the interrupt generation on change of IR input signal}voidloop() {if (TinyReceiverDecode()) {printTinyReceiverResultMinimal(&Serial);    }// No resume() required :-)}

#include"TinyIRSender.hpp"voidsetup() {sendNEC(3,0,11,2);// Send address 0 and command 11 on pin 3 with 2 repeats.}voidloop() {}

Another tiny receiver and sendersupporting more protocols can be foundhere.

The FAST protocol is a proprietary modified JVC protocolwithout address, with parity and with a shorter header.It is meant to have a quick response to the event which sent the protocol frame on another board.FAST takes21 ms for sending and is sent at a50 ms period.It has full 8 bit parity for error detection.

• Bit timing is like JVC
• The header is shorter, 3156 µs vs. 12500 µs
• No address and 16 bit data, interpreted as 8 bit command and 8 bit inverted command, leading to a fixed protocol length of (6 + (16 * 3) + 1) * 526 = 55 * 526 = 28930 microseconds or 29 ms.
• Repeats are sent as complete frames but in a 50 ms period / with a 21 ms distance.

#defineIR_SEND_PIN3#include<IRremote.hpp>voidsetup() {sendFAST(11,2);// Send command 11 on pin 3 with 2 repeats.}voidloop() {}

#defineUSE_FAST_PROTOCOL// Use FAST protocol. No address and 16 bit data, interpreted as 8 bit command and 8 bit inverted command#include"TinyIRSender.hpp"voidsetup() {sendFAST(3,11,2);// Send command 11 on pin 3 with 2 repeats.}voidloop() {}

The FAST protocol can be received by IRremote and TinyIRReceiver.

The receiver sample interval of 50 µs is generated by a timer. On many boards this must be ahardware timer.On some boards where a software timer is available, the software timer is used.
Be aware that the hardware timer used for receiving should not be used foranalogWrite().
Especiallymotor control often uses theanalogWrite() function and will therefore stop the receiving if used on the pins indicatedhere.
On the Uno and other AVR boards the receiver timer ist the same as the tone timer. Thus receiving will stop after atone() command.SeeReceiveDemo example how to deal with it, i.e. how to useIrReceiver.restartTimer().

The flagIRDATA_FLAGS_WAS_OVERFLOW is set, ifRAW_BUFFER_LENGTH is too small for all the marks and spaces of the protocol.This can happen on long protocol frames like the ones from air conditioner.It also can happen, ifRECORD_GAP_MICROS is smaller than the real gap between a frame and the repetition frame, thus interpreting both as one consecutive frame.Best is to dump the timing then, to see which reason holds.

IRremote will not work right when you useNeopixels (aka WS2811/WS2812/WS2812B) or other libraries blocking interrupts for a longer time (> 50 µs).
Whether you use the Adafruit Neopixel library, or FastLED, interrupts get disabled on many lower end CPUs like the basic Arduinos for longer than 50 µs.In turn, this stops the IR interrupt handler from running when it needs to. See also thisvideo.

Oneworkaround is to wait for the IR receiver to be idle before you send the Neopixel data withif (IrReceiver.isIdle()) { strip.show();}.
Thisprevents at least breaking a running IR transmission and -depending of the update rate of the Neopixel- may work quite well.
There are some other solutions to this on more powerful processors,see this page from Marc MERLIN

Another library is only working/compiling if you deactivate the lineIrReceiver.begin(IR_RECEIVE_PIN, ENABLE_LED_FEEDBACK);.
This is often due totimer resource conflicts with the other library. Please seebelow.

This library now supports multiple IR receiver instances (IRrecv) per CPU see theMultipleReceivers example.

There is also another way to use multiple receivers.You can connect the output pins of each IR receiver to one input pin.Then you can use the standard receiver object (IrReceiver).The IR receiver modules internally use an NPN transistor as output device with just a 30k resistor to VCC.This is basically an "open collector" and allows multiple output pins to be connected to one Arduino input pin.
However, keep in mind that any weak / disturbed signal from one of the receivers will also interfere with a good signal from another receiver.

This library only supports one IR sender object (IRsend) per CPU.
However since sending is a serial task, you can usesetSendPin() to switch the pin to send, thus emulating multiple sender.

The best way to increase the IR power for free is to use 2 or 3 IR diodes in series. One diode requires 1.2 volt at 20 mA or 1.5 volt at 100 mA so you can supply up to 3 diodes with a 5 volt output.
To power2 diodes with 1.2 V and 20 mA and a 5 V supply, set the resistor to: (5 V - 2.4 V) -> 2.6 V / 20 mA =130 Ω.
For3 diodes it requires 1.4 V / 20 mA =70 Ω.
The actual current might be lower since ofloss at the AVR pin. E.g. 0.3 V at 20 mA.
If you do not require more current than 20 mA, there is no need to use an external transistor (at least for AVR chips).

On my Arduino Nanos, I always use a 100 Ω series resistor and one IR LED 😀.

To simulate an IR receiver (such as the TSOP1738) which provides an active-low output, you only need to enable theUSE_NO_SEND_PWM macro.In the case you must simulate exotic IR receivers, which provides an active-high output, you also need to enable theUSE_ACTIVE_HIGH_OUTPUT_FOR_NO_SEND_PWM macro.

For receiving, theminimal CPU clock frequency is 4 MHz, since the 50 µs timer ISR (Interrupt Service Routine) takes around 12 µs on a 16 MHz ATmega.
The TinyReceiver, which requires no polling, runs with 1 MHz.
For sending, thedefault software generated PWM has problems on AVR running with 8 MHz. The PWM frequency is around 30 instead of 38 kHz and RC6 is not reliable.You can switch to timer PWM generation by#define SEND_PWM_BY_TIMER.

The Bang & Olufsen protocol decoder is not enabled by default, i.e if no protocol is enabled explicitly by #defineDECODE_<XYZ>. It must always be enabled explicitly by#define DECODE_BEO.This is because it has anIR transmit frequency of 455 kHz and therefore requires a different receiver hardware (TSOP7000).
And becausegenerating a 455 kHz PWM signal is currently only implemented forSEND_PWM_BY_TIMER, sending only works ifSEND_PWM_BY_TIMER orUSE_NO_SEND_PWM is defined.
For more info, seeir_BangOlufsen.hpp.

The examples are available at File > Examples > Examples from Custom Libraries / IRremote.
In order to fit the examples to the 8K flash of ATtiny85 and ATtiny88, theArduino library ATtinySerialOut is required for this CPU's.
See alsoDroneBot Workshop SimpleReceiver andSimpleSender.

TheSimpleReceiver andSimpleSender examples are a good starting point.A simple example can be tested online withWOKWI.

TheSimpleReceiverForHashCodes uses only the hash decoder.It converts all IR frames longer than 6 to a 32 bit hash code, thus enabling receiving of unknown protocols.
See:http://www.righto.com/2010/01/using-arbitrary-remotes-with-arduino.html

Ifcode size ortimer usage matters, look at these examples.
TheTinyReceiver example uses theTinyIRReceiver librarywhich canonly receive NEC, Extended NEC, ONKYO and FAST protocols, but does not require any timer.They use pin change interrupt for on the fly decoding, which is the reason for the restricted protocol choice.
TinyReceiver can be tested online withWOKWI.

TheTinySender example uses theTinyIRSender library which canonly send NEC, ONKYO and FAST protocols.
It sends NEC protocol codes in standard format with 8 bit address and 8 bit command as in SimpleSender example. It has options to send using Extended NEC, ONKYO and FAST protocols.Saves 780 bytes program memory and 26 bytes RAM compared to SimpleSender, which does the same, but uses the IRRemote library (and is therefore much more flexible).

If the protocol is not NEC and code size matters, look at thisexample.

ReceiveDemo receives all protocols andgenerates a beep with the Arduino tone() function on each packet received.
Long press of one IR button (receiving of multiple repeats for one command) is detected.
AllProtocolsOnLCD additionallydisplays the short result on a 1602 LCD.The LCD can be connected parallel or serial (I2C).
By connecting debug pin to ground, you can force printing of the raw values for each frame. The pin number of the debug pin is printed during setup, because it depends on board and LCD connection type.
This example also serves as anexample how to use IRremote and tone() together.

Receives all protocols and dumps the received signal in different flavors includingPronto format.
Since the printing takes much time, repeat signals may be skipped or interpreted as UNKNOWN.

Sends all available protocols at least once.

Demonstrates sending IR codes toggling between 2different send pins.

Demonstratesreceiving while sending.

Record andplay back last received IR signal at button press. IR frames of known protocols are sent by the appropriate protocol encoder.UNKNOWN protocol frames are stored as raw data and sent withsendRaw().

Try to decode each IR frame with theuniversalDistanceWidth decoder, store the data and send it on button press withsendPulseDistanceWidthFromArray().
If RAM is not more than 2k, the decoder only accepts mark or space durations up to 2500 microseconds to save RAM space, otherwise it accepts durations up to 10 ms.
Storing data for distance width protocol requires 17 bytes.The ReceiveAndSend example requires 16 bytes for known protocol data and 37 bytes for raw data of e.g.NEC protocol.

Serves as a IRremote macro expander. Receives Samsung32 protocol and on receiving a specified input frame, it sends multiple Samsung32 frames with appropriate delays in between.This serves as aNetflix-key emulation for my old Samsung H5273 TV.

Framework forcalling different functions of your program for different IR codes.

Control a relay (connected to an output pin) with your remote.

Example for a user defined class, which itself uses the IRrecv class from IRremote.

Example for sending LG air conditioner IR codes controlled by Serial input.
By just using the functionbool Aircondition_LG::sendCommandAndParameter(char aCommand, int aParameter) you can control the air conditioner by any other command source.
The fileacLG.h contains the command documentation of the LG air conditioner IR protocol. Based on reverse engineering of the LG AKB73315611 remote.
IReceiverTimingAnalysis can be tested online withWOKWIClick on the receiver while simulation is running to specify individual IR codes.

Example for receiving and sending AEG / Elektrolux Hob2Hood protocol.

This example analyzes the signal delivered by your IR receiver module.Values can be used to determine the stability of the received signal as well as a hint for determining the protocol.
It also computes theMARK_EXCESS_MICROS value, which is the extension of the mark (pulse) duration introduced by the IR receiver module.
It can be tested online withWOKWI.Click on the receiver while simulation is running to specify individual NEC IR codes.

ReceiveDemo + SendDemo in one program. Demonstratesreceiving while sending.Here you see the delay of the receiver output (blue) from the IR diode input (yellow).

• Simple receiver
• Simple toggle by IR key 5
• TinyReceiver
• ReceiverTimingAnalysis
• Receiver with LCD output and switch statement

Thisexample of theArduino PWMMotorControl library controls the basic functions of a robot car using the IRremote library.
It controls 2 PWM motor channels, 2 motors at each channel.
Here you can find the instructable for car assembly and code.

IR_RobotCar with TL1838 IR receiver plugged into expansion board.

• Do not open an issue without first testing some of the examples!
• If you have a problem, please post the MCVE (Minimal Complete Verifiable Example) showing this problem. My experience is, that most of the times you will find the problem while creating this MCVE 😄.
• Use code blocks;it helps us to help you when we can read your code!

To customize the library to different requirements, there are some compile options / macros available.
These macros must be defined in your programbefore the line#include <IRremote.hpp> to take effect.
Modify them by enabling / disabling them, or change the values if applicable.

These next macros forTinyIRReceiver must be defined in your program before the line#include <TinyIRReceiver.hpp> to take effect.

The next macro forIRCommandDispatcher must be defined in your program before the line#include <IRCommandDispatcher.hpp> to take effect.|USE_TINY_IR_RECEIVER | disabled | UseTinyReceiver for receiving IR codes. ||IR_COMMAND_HAS_MORE_THAN_8_BIT | disabled | Enables mapping and dispatching of IR commands consisting of more than 8 bits. Saves up to 160 bytes program memory and 4 bytes RAM + 1 byte RAM per mapping entry. ||BUZZER_PIN | | IfUSE_TINY_IR_RECEIVER is enabled, the pin to be used for the optional 50 ms buzzer feedback before executing a command. Other IR libraries than Tiny are not compatible with tone() command. |

First, useSketch > Show Sketch Folder (Ctrl+K).
If you have not yet saved the example as your own sketch, then you are instantly in the right library folder.
Otherwise you have to navigate to the parallellibraries folder and select the library you want to access.
In both cases the library source and include files are located in the librariessrc directory.
The modification must be renewed for each new library version!

If you are using PlatformIO, you can define the macros in theplatformio.ini file withbuild_flags = -D MACRO_NAME orbuild_flags = -D MACRO_NAME=macroValue.

If you are usingSloeber as your IDE, you can easily define global symbols withProperties > Arduino > CompileOptions.

Issues and discussions with the content "Is it possible to use this library with the ATTinyXYZ? / board XYZ" without any reasonable explanations will be immediately closed without further notice.
ForESP8266/ESP32,the IRremoteESP8266 library supports animpressive set of protocols and a lot of air conditioners.
ATtiny CPU's are tested with theArduino library ATtinySerialOut library.

Digispark boards are tested only withATTinyCore using theNew Style pin mapping for the Digispark Pro board.
ATtiny boards are tested only withATTinyCore ormegaTinyCore.

• Arduino Uno / Mega / Leonardo / Duemilanove / Diecimila / LilyPad / Mini / Fio / Nano etc.
• Arduino Uno R4, but not yet tested, because of lack of a R4 board.Sending does not work on thearduino:renesas_uno:unor4wifi.
• Teensy 1.0 / 1.0++ / 2.0 / 2++ / 3.0 / 3.1 / 3.2 / Teensy-LC - butlimited support; Credits: PaulStoffregen (Teensy Team)
• Sanguino
• ATmega8, 48, 88, 168, 328
• ATmega8535, 16, 32, 164, 324, 644, 1284,
• ATmega64, 128
• ATmega4809 (Nano every)
• ATtiny3217 (Tiny Core 32 Dev Board)
• ATtiny84, 85, 167 (Digispark + Digispark Pro)
• SAMD (Zero, MKR*,but not DUE, the latter is SAM architecture)
• ESP8266
• ESP32 (ESP32-C3 since board package 2.0.2 from Espressif). New CPUs (as of January 2025) are not guaranteed to work!
• Sparkfun Pro Micro
• Nano Every, Uno WiFi Rev2, nRF5 BBC MicroBit, Nano33_BLE
• BluePill with STM32
• RP2040 based boards (Raspberry Pi Pico, Nano RP2040 Connect etc.)

We are open to suggestions for adding support to new boards, however we highly recommend you contact your supplier first and ask them to provide support from their side.
If you can provideexamples of using a periodic timer for interrupts for the new board, and the board name for selection in the Arduino IDE, then you have way better chances to get your board supported by IRremote.

Thereceiver sample interval of 50 µs is generated by a timer. On many boards this must be a hardware timer. On some boards where a software timer is available, the software timer is used.
OnESP8266timer1 is used for receive interrupts, which makes it incompatible to the Servo and other libraries.
OnESP32hw_timer_t is used for receive interrupts.

Every pin can be used for receiving.
If software PWM is selected, which is default, every pin can also be used for sending. Sending with software PWM does not require a timer!

The TinyReceiver example uses theTinyReceiver library, which canonly receive NEC codes, but does not require any timer and runs even on a 1 MHz ATtiny85.

The code for the timer and thetimer selection is located inprivate/IRTimer.hpp. The selected timer can be adjusted here.

Be aware that the hardware timer used for receiving should not be used for analogWrite()!.

Thesend PWM signal is by default generated by software.Therefore every pin can be used for sending.The PWM pulse length is guaranteed to be constant by usingdelayMicroseconds().Take care not to generate interrupts during sending with software generated PWM, otherwise you will get jitter in the generated PWM.E.g. wait for a formerSerial.print() statement to be finished bySerial.flush().Since the Arduinomicros() function has a resolution of 4 µs at 16 MHz, we always see a small jitter in the signal, which seems to be OK for the receivers.

Software generated PWM showing small jitter because of the limited resolution of 4 µs of the Arduino coremicros() function for an ATmega328	Detail (ATmega328 generated) showing 30% duty cycle

If you use a library which requires the same timer as IRremote, you have a problem, sincethe timer resource cannot be shared simultaneously by both libraries.

TinyReceiver does not require a timer, it relies on interrupts, thus avoiding any timer resource problems.

The best approach is tochange the timer used for IRremote, which can be accomplished by specifying the timer before#include <IRremote.hpp>.
The timer specifications available for your board can be found inprivate/IRTimer.hpp.

// Arduino Mega#elif defined(__AVR_ATmega1280__) || defined(__AVR_ATmega2560__)#if !defined(IR_USE_AVR_TIMER1) && !defined(IR_USE_AVR_TIMER2) && !defined(IR_USE_AVR_TIMER3) && !defined(IR_USE_AVR_TIMER4) && !defined(IR_USE_AVR_TIMER5)//#define IR_USE_AVR_TIMER1   // send pin = pin 11#defineIR_USE_AVR_TIMER2// send pin = pin 9//#define IR_USE_AVR_TIMER3   // send pin = pin 5//#define IR_USE_AVR_TIMER4   // send pin = pin 6//#define IR_USE_AVR_TIMER5   // send pin = pin 46#endif

Here you see the Arduino Mega board and the available specifications areIR_USE_AVR_TIMER[1,2,3,4,5].
Youjust have to include a line e.g.#define IR_USE_AVR_TIMER3 before#include <IRremote.hpp> to enable timer 3.

But be aware that the new timer in turn might be again incompatible with other libraries or Arduino functions.
For non AVR boards/platforms you must look for the appropriate section guarded by e.g.#elif defined(ESP32).

Another approach can be to share the timersequentially if their functionality is used only for a short period of time like for theArduino tone() command.An example can be seenhere, where the IR timer is restarted after the tone has stopped.

IrReceiver.stopTimer();// Stop timer consistently before calling tone() or other functions using the timer resource.tone(TONE_PIN,2200,8);delay(8);IrReceiver.restartTimer();// Restart IR timer after timer resource is no longer blocked.

This works on AVR boards like Uno because each call to tone() completely initializes the timer 2 used by thetone() command.

If you defineSEND_PWM_BY_TIMER, the send PWM signal is forced to be generated by a hardware timer on most platforms.
By default, the same timer as for the receiver is used.
Since each hardware timer has its dedicated output pin(s), you must change timer or timer sub-specifications to change PWM output pin. Seeprivate/IRTimer.hpp
Exceptions are currentlyESP32, ARDUINO_ARCH_RP2040, PARTICLE and ARDUINO_ARCH_MBED, wherePWM generation does not require a timer.

Wedo it according to the statement in theVishay datasheet:

• Carrier duty cycle 50 %, peak current of emitter IF = 200 mA, the resulting transmission distance is 25 m.
• Carrier duty cycle 10 %, peak current of emitter IF = 800 mA, the resulting transmission distance is 29 m. - Factor 1.16The reason is, that it is not the pure energy of the fundamental which is responsible for the receiver to detect a signal.Due to automatic gain control and other bias effects, high intensity of the 38 kHz pulse counts more than medium intensity (e.g. 50% duty cycle) at the same total energy.

The IR signal is sampled at a50 µs interval. For a constant 525 µs pulse or pause we therefore get 10 or 11 samples, each with 50% probability.
And believe me, if you send a 525 µs signal, your receiver will output something between around 400 and 700 µs!
Thereforewe decode by default with a +/- 25% margin using the formulashere.
E.g. for the NEC protocol with its 560 µs unit length, we have TICKS_LOW = 8.358 and TICKS_HIGH = 15.0.This means, we accept any value between 8 ticks / 400 µs and 15 ticks / 750 µs (inclusive) as a mark or as a zero space.For a one space we have TICKS_LOW = 25.07 and TICKS_HIGH = 45.0.
And since the receivers generated marks are longer or shorter than the spaces,we have introduced theMARK_EXCESS_MICROS macroto compensate for this receiver and signal strength as well as ambient light dependent 😞 specific deviation.
Welcome to the world of real world signal processing.

Created with sigrok PulseView with IR_NEC decoder by DjordjeMandic.
8 bit address NEC code16 bit address NEC code

This is a short comparison and may not be complete or correct.

I created this comparison matrix formyself in order to choose a small IR library for my project and to have a quick overview, when to choose which library.
It is dated from24.06.2022 and updated 10/2023. If you have complains about the data or request for extensions, please send a PM or open a discussion.

Here you find anESP8266/ESP32 version of IRremote with animpressive list of supported protocols.

* The Hash protocol gives you a hash as code, which may be sufficient to distinguish your keys on the remote, but may not work with some protocols like Mitsubishi

• Online NEC to Pronto converting tool
• List of public IR code databases
• LIRC database
• IRMP list of IR protocols
• IRDB database for IR codes
• IRP definition files for IR protocols
• Good introduction to IR remotes by DroneBot Workshop
• IR Remote Control Theory and some protocols (upper right hamburger icon)
• Overviev of many protocols
• Overviev of many protocols on one page (v2.45)
• "Recording long Infrared Remote control signals with Arduino"
• The original blog post of Ken ShirriffA Multi-Protocol Infrared Remote Library for the Arduino
• Vishay datasheet

Up to the version 2.7.0, the License is GPLv2.From the version 2.8.0, the license is the MIT license.

Initially coded 2009 Ken Shirriffhttp://www.righto.com
Copyright (c) 2016-2017 Rafi Khanhttps://rafikhan.io
Copyright (c) 2020-2025Armin Joachimsmeyer