The very latest Eclipse IDE doesn't work with Sloeber's Arduino system, so get a slightly older version from where you must choose 'Eclipse IDE for C/C Developers' for your computer's OS. This gets you an installer which you use to set up Eclipse on that computer. Sloeber is an Arduino IDE developed by Jantje Baeyens based on Eclipse, which is an established Java IDE. A screenshot of Sloeber. Sloeber is much easier to set up than Atom or Visual Studio Code as there is one file to download and it automatically sets itself up for Arduino upon installation. UPDATE arduino IDE (no longer)? Decompresses libraries and as such the libraries are unusable in Sloeber. Lets start with the Libraries What you do is: In arduino.
I don't know if this is a proper place to put questions about the Eclipse Sloeber Arduino IDE, but I will try anyway..I have just started using Arduino in order to make a special WiFi application using an ESP-07S module with ESP8266.But I had great problems working with the Arduino IDE and when I asked about these I got a recommendation to use Eclipse instead, specifically the Sloeber Eclipse IDE plugin (installed from the 'product' which says it includes Eclipse, Java and all else you need)..So I downloaded the installer (64bit) to my Windows7 X64 PC and ran the installer, then started the program.Now I have come as far as reaching the IDE and via the 'File/Open Projects from file system' menu I navigated to the already started sketch directory ehere the ino file resided and it opens in the new IDE.I can get edit windows for the files involved (which I could not in the Arduino IDE).But, nothing happens if I use the Verify command in the toolbar (except for opening an empty messages box at the bottom of the right-hand pane. THere seems to be no compile or anything like that performed.So I suspect I have not installed it properly.What are the steps to take in the IDE before opening an existing project (sketch)?Seems likely I have missed something important.[u]One observation:[/u]When I first opened the IDE there was a window saying it was installing stuff and then suddenly Windows Firewall popped up a message about it having blocked access to the Internet from this program:C:Programssloebersloeber-ide.exeIt took a little while before I realized I had to click a button to allow access, but at that time the 'installation window' had disappeared. Maybe it could not complete and my installation is now incomplete or something?How can I manually repeat whatever was going on at first start, if that is what it takes?
And is there some working tutorial on how to actually go from the downloaded installer to a position where one can start working on an existing ESP8266 based sketch without problems?I have found this: http://eclipse.baeyens.it/getting-started.shtmlbut it is very strangely done and I cannot find a 'guide for dummies', which I probably need.
Available as Arduino library 'IRremote'
Version 3.1.1 - work in progress
This library enables you to send and receive using infra-red signals on an Arduino.
A Doxygen documentation of the sources is available on the project homepage.
Click on the LibraryManager badge above to see the instructions.
Denon / Sharp, JVC, LG, NEC / Onkyo / Apple, Panasonic / Kaseikyo, RC5, RC6, Samsung, Sony, (Pronto), BoseWave, Lego, Whynter, MagiQuest.
Protocols can be switched off and on by defining macros before the line
#include <IRremote.h> like here:
This is a quite old but maybe useful wiki for this library.
- You can use any pin for sending now, like you are used with receiving.
- Simultaneous sending and receiving. See the UnitTest example.
- No more need to use 32 bit hex values in your code. Instead a (8 bit) command value is provided for decoding (as well as an 16 bit address and a protocol number).
- Protocol values comply to protocol standards, i.e. NEC, Panasonic, Sony, Samsung and JVC decode and send LSB first.
- Supports more protocols, since adding a protocol is quite easy now.
- Better documentation and more examples :-).
- Compatible with tone() library, see ReceiveDemo.
- Supports more platforms, since the new structure allows to easily add a new platform.
- Feedback LED also for sending.
- Ability to generate a non PWM signal to just simulate an active low receiver signal for direct connect to existent receiving devices without using IR.
- Easy configuration of protocols required, directly in your [source code[(https://github.com/Arduino-IRremote/Arduino-IRremote/blob/master/examples/SimpleReceiver/SimpleReceiver.ino#L18-L34). This reduces the memory footprint and increases decoding time.
This must be done also for all versions > 3.0.1 if
USE_NO_SEND_PWM is defined.
Starting with this version, the generation of PWM is done by software, thus saving the hardware timer and enabling arbitrary output pins.
Therefore you must change all
IrSender.begin(IR_SEND_PIN, ENABLE_LED_FEEDBACK);. If you use a 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.
- Now there is an IRreceiver and IRsender object like the well known Arduino Serial object.
- Just remove the line
IRsend IrSender;in your program, and replace all occurrences of
- Since the decoded values are now in
IrReceiver.decodedIRDataand not in
resultsany more, remove the line
decode_results resultsor similar.
- Like for the Serial object, call
IrReceiver.begin(IR_RECEIVE_PIN, DISABLE_LED_FEEDBACK);instead of the
decode(decode_results *aResults)function is replaced by simple
decode(). So if you have a statement
if(irrecv.decode(&results))replace it with
- The decoded result is now in in
IrReceiver.decodedIRDataand not in
resultsany more, therefore replace any occurrences of
results.decode_type(and similar) to
- Overflow, Repeat and other flags are now in
- Seldom used:
results.rawlenmust be replaced by
If you program is like:
it should run on the 3.1.1 version as before. The following decoders are available: Denon, JVC, LG, NEC, Panasonic, RC5, RC6, Samsung, Sony. The
results.value is set by the decoders for NEC, Panasonic, Sony, Samsung and JVC as MSB first like in 2.x.
- The old functions
sendJVC()are deprecated and renamed to
sendJVCMSB()to make it clearer that they send data with MSB first, which is not the standard for NEC and JVC. Use them to send your old MSB-first 32 bit IR data codes. In the new version you will send NEC commands not by 32 bit codes but by a (constant) 8 bit address and an 8 bit command.
The new decoders for NEC, Panasonic, Sony, Samsung and JVC
IrReceiver.decodedIRData.decodedRawData is now LSB-first, as the definition of these protocols suggests! To convert one into the other, you must reverse the byte positions and then reverse all bit positions of each byte or write it as one binary string and reverse/mirror it.
0xCB340102 byte reverse -> 02 01 34 CB bit reverse-> 40 80 2C D3.
0xCB340102 is binary 11001011001101000000000100000010.
0x40802CD3 is binary 01000000100000000010110011010011.
If you read the first binary sequence backwards (right to left), you get the second sequence.
- IR does not work right when I use Neopixels (aka WS2811/WS2812/WS2812B) or other libraries blocking interrupts for a longer time (> 50 us).
Whether you use the Adafruit Neopixel lib, 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. There are some solutions to this on some processors, see this page from Marc MERLIN
- The default IR timer on AVR's is timer 2. Since the Arduino Tone library as well as analogWrite() for pin 3 and pin 11 requires timer 2, this functionality cannot be used simultaneously. You can use tone() but after the tone has stopped, you must call
IrReceiver.start(<microsecondsOfToneDuration>)to restore the timer settings for receive. Or you change the timer to timer 1 in private/IRTimer.cpp.h.
If you can live with the NEC protocol, you can try the MinimalReceiver example, it requires no timer.
- You can use multiple IR receiver by just connecting the output pins of several IR receivers together. The IR receivers use an NPN transistor as output device with just a 30k resistor to VCC. This is almost 'open collector' and allows connecting of several output pins to one Arduino input pin.
- The minimal CPU frequency for receiving is 4 MHz, since the 50 us timer ISR takes around 12 us on a 16 MHz ATmega.
For applications only requiring NEC protocol, there is a receiver which has very small codesize of 500 bytes and does NOT require any timer. See the MinimalReceiver and IRDispatcherDemo example how to use it. Mapping of pins to interrupts can be found here.
This library was never designed to handle long codes like the ones used by air conditioners. See Recording long Infrared Remote control signals with Arduino.
The main reason is, that it 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.
If you see something like
Protocol=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 an odd number of bits received, it is likely, that your receiver circuit has problems. Maybe because the IR signal is too weak.
- If you see timings like
+ 600,- 600 + 550,- 150 + 200,- 100 + 750,- 550then 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.
- To see more info supporting you to find the reason for your UNKNOWN protocol, you must enable the line
//#define DEBUGin IRremoteInt.h.
How to deal with protocols not supported by IRremote
If you do not know which protocol your IR transmitter uses, you have several choices.
- Use the IRreceiveDump example to dump out the IR timing. You can then reproduce/send this timing with the SendRawDemo example. For long codes with more than 48 bits like from air conditioners, you can change the length of the input buffer in IRremote.h.
- The IRMP AllProtocol example prints the protocol and data for one of the 40 supported protocols. The same library can be used to send this codes.
- If you have a bigger Arduino board at hand (> 100 kByte program space) you can try the IRremoteDecode example of the Arduino library DecodeIR.
- Use IrScrutinizer. It can automatically generate a send sketch for your protocol by exporting as 'Arduino Raw'. It supports IRremote, the old IRLib and Infrared4Arduino.
- To increase strength of sent output signal you can increase the current through the send diode, and/or use 2 diodes in series, since one IR diode requires only 1.5 volt.
- The line #include 'ATtinySerialOut.h' in PinDefinitionsAndMore.h (requires the library to be installed) saves 370 bytes program space and 38 bytes RAM for Digispark boards as well as enables serial output at 8MHz.
- The default software generated PWM has problems on ATtinies 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
In order to fit the examples to the 8K flash of ATtiny85 and ATtiny88, the Arduino library ATtinySerialOut is required for this CPU's.
Sloeber Arduino Add Library
SimpleReceiver + SimpleSender
This examples are a good starting point.
ReceiveDemo + SendDemo
More complete examples for the advanced user.
ReceiveAndSend + UnitTest
ReceiveDemo + SendDemo in one program. Receiving while sending.
Record and play back last received IR signal at button press.
MinimalReceiver + SmallReceiver
If code size matters, look at these examples.
Framework for calling different functions for different IR codes.
Control a relay (connected to an output pin) with your remote.
To customize the library to different requirements, there are some compile options / macros available.
Modify it by commenting them out or in, or change the values if applicable. Or define the macro with the -D compiler option for global compile (the latter is not possible with the Arduino IDE, so consider using Sloeber.
|Before ||disabled||Disable carrier PWM generation in software and use (restricted) hardware PWM except for ESP32 where both modes are using the flexible |
|Before ||disabled||Use no carrier PWM, just simulate an active low receiver signal. Overrides |
|IRremoteInt.h||disabled||Disables the old decoder for version 2.x compatibility, where all protocols -especially NEC, Panasonic, Sony, Samsung and JVC- were MSB first. Saves around 60 bytes program space and 14 bytes RAM.|
|Before ||disabled||If activated, BOSEWAVE, MAGIQUEST,WHYNTER and LEGO_PF are excluded in |
|Before ||20||MARK_EXCESS_MICROS is subtracted from all marks and added to all spaces before decoding, to compensate for the signal forming of different IR receiver modules.|
|Before ||disabled||Required on some boards (like my BluePill and my ESP8266 board), where the feedback LED is active low.|
|Before ||disabled||This completely disables the LED feedback code for receive, thus saving around 108 bytes program space and halving the receiver ISR processing time.|
|Before ||disabled||Enable it if you use a RF receiver, which has an active HIGH output signal.|
|IRremoteInt.h||101||Buffer size of raw input buffer. Must be odd!|
|IRremoteInt.h||disabled||Enables lots of lovely debug output.|
|IRremoteInt.h||30||Duty cycle of IR send signal.|
|IRremoteInt.h||50||Resolution of the raw input buffer data.|
|TinyIRReceiver.h||2||The pin number for TinyIRReceiver IR input, which gets compiled in.|
|TinyIRReceiver.h||The pin number for TinyIRReceiver feedback LED, which gets compiled in.|
|TinyIRReceiver.h||disabled||Enable it to disable the feedback LED function.|
Modifying compile options with Arduino IDE
First, use Sketch > Show Sketch Folder (Ctrl+K).
If you did not yet stored the example as your own sketch, then you are instantly in the right library folder.
Otherwise you have to navigate to the parallel
libraries folder and select the library you want to access.
In both cases the library files itself are located in the
Modifying compile options with Sloeber IDE
If you are using Sloeber as your IDE, you can easily define global symbols with Properties > Arduino > CompileOptions.
- Arduino Uno / Mega / Leonardo / Duemilanove / Diecimila / LilyPad / Mini / Fio / Nano etc.
- Teensy 1.0 / 1.0++ / 2.0 / 2++ / 3.0 / 3.1 / Teensy-LC; Credits: PaulStoffregen (Teensy Team)
- ATmega8, 48, 88, 168, 328
- ATmega8535, 16, 32, 164, 324, 644, 1284,
- ATmega64, 128
- ATmega4809 (Nano every)
- ATtiny84, 85
- SAMD21 (DUE, Zero)
- ESP8266. This fork supports an impressive set of protocols.
- Sparkfun Pro Micro
- Nano Every, Uno WiFi Rev2, nRF5 BBC MicroBit, Nano33_BLE
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.
Eclipse Arduino Sloeber
The receiver sample interval is generated by a timer. On many boards this must be a hardware timer, on some a software timer is available and used. The code for the timer and the timer selection is located in private/IRTimer.cpp.h.
Every pin can be used for receiving.
The send 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 using
delayMicroseconds(). Take care not to generate interrupts during sending with software generated PWM, otherwise you will get jitter in the generated PWM. Ishqiya serial. E.g. wait for a former
Serial.print() statement to be finished by
Serial.flush(). Since the Arduino
micros() function has a resolution of 4 us 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 us of the Arduino core ||Detail (ATmega328 generated) showing 33% Duty cycle|
Hardware-PWM signal generation for sending
If you define
SEND_PWM_BY_TIMER, the send PWM signal is generated by a hardware timer. The same timer as for the receiver is used. Since each hardware timer has its dedicated output pins, you must change timer to change PWN output.
The timer and the pin usage can be adjusted in private/IRTimer.cpp.h
|ATtiny85 > 1 MHz||1, 4||0, 1|
|ATmega48, ATmega88, ATmega168, ATmega328||3, 9||1, 2|
|ATmega1284||13, 14, 6||1, 2, 3|
|ATmega164, ATmega324, ATmega644||13, 14||1, 2|
|ATmega8535 ATmega16, ATmega32||13||1|
|ATmega64, ATmega128, ATmega1281, ATmega2561||13||1|
|ATmega1280, ATmega2560||5, 6, 9, 11, 46||1, 2, 3, 4, 5|
|Leonardo (Atmega32u4)||5, 9, 13||1, 3, 4_HS|
|Zero (SAMD)||*, 9||TC3|
|ESP32||4, all pins||1|
|Sparkfun Pro Micro||5, 9||1, 3|
|Teensy 2.0||9, 10, 14||1, 3, 4_HS|
|Teensy++ 1.0 / 2.0||1, 16, 25||1, 2, 3|
|Teensy 3.0 / 3.1||5||CMT|
To add a new protocol is quite straightforward. Best is too look at the existing protocols to find a similar one and modify it.
As a rule of thumb, it is easier to work with a description of the protocol rather than trying to entirely reverse-engineer the protocol. Please include a link to the description in the header, if you found one.
The durations you receive are likely to be longer for marks and shorter for spaces than the protocol suggests, but this depends on the receiver circuit in use. Most protocols use multiples of one time-unit for marks and spaces like e.g. NEC. It's easy to be off-by-one with the last bit, since the last space is not recorded by IRremote.
Try to make use of the template functions
sendPulseDistanceData(). If your protocol supports address and code fields, try to reflect this in your api like it is done in
sendNEC(uint16_t aAddress, uint8_t aCommand, uint_fast8_t aNumberOfRepeats, bool aIsRepeat) and
To integrate your protocol, you need to extend the two functions
getProtocolString() in IRreceice.cpp, add macros and function declarations for sending and receiving and extend the
enum decode_type_t in IRremote.h.
And at least it would be wonderful if you can provide an example how to use the new protocol. A detailed description can be found in the ir_Template.cpp file.
8 bit address NEC code 16 bit address NEC code
Please see changelog.md.
See API reference in wiki.
To generate the API documentation, Doxygen, as well as Graphviz should be installed. (Note that on Windows, it is useful to specify the installer to add Graphviz to PATH or to do it manually. With Doxygen and Graphviz installed, issue the command
doxygen from the command line in the main project directory, which will generate the API documentation in HTML format. The just generated
docs/index.html can now be opened in a browser.
Why do we use 33% duty cycle
We do it according to the statement in the Vishay 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.16 The 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 and lower energy (duty cycle) of the 38 kHz pulse counts more than high low intensity and higher energy.
BTW, the best way to increase the IR power is to use 2 or 3 IR diodes in series. One diode requires 1.1 to 1.5 volt so you can supply 3 diodes with a 5 volt output.
To keep the current, you must reduce the resistor by (5 - 1.3) / (5 - 2.6) = 1.5 e.g. from 150 ohm to 100 ohm for 25 mA and 2 diodes with 1.3 volt and a 5 volt supply.
For 3 diodes it requires factor 2.5 e.g. from 150 ohm to 60 ohm.
Here you find an ESP8266/ESP32 version of IRremote with an impressive list of supported protocols.
This is a short comparison and may not be complete or correct
I created this comparison matrix for myself in order to choose a small IR lib for my project and to have a quick overview, when to choose which library.
It is dated from 03.02.2021. If you have complains about the data or request for extensions, please send a PM or open a discussion.
|Number of protocols||50||Nec + Panasonic + Hash *||12 + Hash *||17 + Hash *||NEC|
|3.Party libs needed||%||PinChangeInterrupt if not pin 2 or 3||%||%||%|
|Timing method receive||Timer2 or interrupt for pin 2 or 3||Interrupt||Timer2 or interrupt for pin 2 or 3||Timer2 or interrupt for NEC||Interrupt|
|Timing method send||PWM and timing with Timer2 interrupts||Timer2 interrupts||Timer2 and blocking wait||PWM with Timer2 and blocking wait with delayMicroseconds()||%|
|Send pins||All||All||All ?||Timer dependent||%|
|Encode method||OnTheFly||OnTheFly||OnTheFly||OnTheFly or RAM||%|
|Repeat handling||Receive + Send (partially)||%||?||Receive + Send||x|
|FLASH usage (simple NEC example with 5 prints)||1820|
(4300 for 15 main / 8000 for all 40 protocols)
(+200 for callback)
(+80 for interrupt at pin 2+3)
(1400 for pin 2+3)
(73 / 100 for 15 (main) / 40 protocols)
|Supported platforms||avr, megaAVR, attiny, Digispark (Pro), esp8266, ESP32, STM32, SAMD 21, Apollo3|
(plus arm and pic for non Arduino IDE)
|avr, esp8266||avr, SAMD 21, SAMD 51||avr, attiny, esp8266, esp32, SAM, SAMD||All platforms with attachInterrupt()|
|Last library update||2/2021||4/2018||9/2019||2/2021||2/2021|
|Remarks||Decodes 40 protocols concurrently.|
39 Protocols to send.
Work in progress.
|Only one protocol at a time.||Consists of 5 libraries. Project containing bugs - 45 issues, no reaction for at least one year.||Decoding and sending are easy to extend.|
Supports Pronto codes.
|Requires no timer.|
Sloeber Arduino Uno
- 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
If you want to contribute to this project:
- Report bugs and errors
- Ask for enhancements
- Create issues and pull requests
- Tell other people about this library
- Contribute new protocols
Check here for some guidelines.
Email: zetos[email protected][email protected][email protected]gmail[email protected].com Please only email me if it is more appropriate than creating an Issue / PR. I will not respond to requests for adding support for particular boards, unless of course you are the creator of the board and would like to cooperate on the project. I will also ignore any emails asking me to tell you how to implement your ideas. However, if you have a private inquiry that you would only apply to you and you would prefer it to be via email, by all means.
Up to the version 2.7.0 the License is GPLv2. From the version 2.8.0 the license is the MIT license.
Sloeber Arduino Debug
Sloeber Arduino Plugin
Initially coded 2009 Ken Shirriff http://www.righto.com Copyright (c) 2016 Rafi Khan Copyright (c) 2020-2021 Armin Joachimsmeyer