Compiling issues

** Clash with HardwareSerial library **

A very common problem some users report about is a clash with the HardwareSerial library that comes with the Arduino development tool. If the message you are getting is like the following you should keep on reading.

core.a(HardwareSerial.cpp.o): In function __vector_18': /Applications/Arduino.app/Contents/Resources/Java/hardware/arduino/cores/arduino/HardwareSerial.cpp:115: multiple definition of__vector_18'
Conceptinetics/Conceptinetics.cpp.o:/Users/.../Documents/Arduino/libraries/Conceptinetics/Conceptinetics.cpp:1059: first defined here

It is known that the HardwareSerial library can not work together with this DMX library, even not if you only use other serial ports than the one used by the DMX Library (Some boards do have: Serial1, Serial2, Serial3). The main reason is that when you create a single reference to one of the Serial objects it will hook onto every serial port present on your Arduino board.

Q: I want to use hardware serial in combination with the Conceptinetics DMX library.
A: This is not possible since the Conceptinetics DMX library wants to register the interupt service routines himself for the first serial port.. this will cause a clash

Q: I am not using the HardwareSerial library and still get the above error message
A: It might be possible that you use a library that actually uses the Serial port for debugging, the developers of that library might have forgotten to remove or comment out those references.. simply look into those libraries and see if they make use of the HardwareSerial library.

Q: I want to make use of the other Serial ports on my Arduino board and also like to use the Conceptinetics DMX library.
A: You have to remove the Serial object and the interrupt service routine yourself from the HardwareSerial library so it doesn't uses the first USART anymore.. after that you can still use the other Serial port (Serial1, Serial2, Serial3).

If you run into any other problems or issues, please create a ticket so it can be investigated and possibly inform other users on how to solve that issue.....