Description
The type of board you are using.
Arduino ATmega328* board (UNO, Nano, etc.)
The boards name or FQBN (e.g. esp8266:esp8266:d1_mini:eesz=4M3M,xtal=80) for unspecified board.
No response
The board manager URL used for unspecified board.
https://
What IDE are you using?
Arduino IDE
What IR protocol are you using?
Unknown
Pin(s) used for IR-receive, if not default.
Arduino pin number: default
Example(s) you have checked while hunting the bug.
- SimpleReceiver
- ReceiveDemo
- SendRawDemo
- ReceiverTimingAnalysis
- TinyReceiver
- TinySender
- ReceiveAndSend
- SimpleSender
- SendDemo
- SendLGAirConditionerDemo
- UnitTest
- Other - please specify below
- I checked, if at least one of the examples was working.
Example(s) to reproduce the issue.
- SimpleReceiver
- ReceiveDemo
- SendRawDemo
- ReceiverTimingAnalysis
- TinyReceiver
- TinySender
- ReceiveAndSend
- SimpleSender
- SendDemo
- SendLGAirConditionerDemo
- UnitTest
- Other - please specify below
The library version you are working with.
- I use the latest Arduino library version and verified this!
- I use the latest repo version (download link) and verified this!
What are the steps to reproduce this issue?
include IRremote and DMXserial into one script like:
#include "PinDefinitionsAndMore.h"
#include <IRremote.hpp>
#include <DMXSerial.h>
void setup() {
}
void loop() {
}
Get DMXserial from here.
What happens?
compiler error: multiple definitions of "__vector_18" and "__vector_19"
I think this is because DMXserial uses hardwareserial for transmit/receive and IRremote uses serial, too.
I know, the Arduino nano only has one serial. That would be enough, because I do not need any USB-serial monitor or debugging to serial with serial.print.
I didn't find any options to disable serial in IRremote in general. That would be fine.
In my current project I just need IRsendRAW with constant arrays prerecorded with another script. I think/hope this works without ousing any hardware serial.
The serial output which indicates the error happened.
-nothing- not using serial...What were you expecting to happen?
Working code, because I'm not using serial for USB-debugging/monitoring.
Additional context.
No response
Final checklist for the bug report.
- I have read the README.md file thoroughly
- I have searched existing issues to see if there is anything I have missed.
- I have browsed the examples for one, that matches my use case.
- The title of the issue is helpful and relevant.