Steun onze actie WeGoSTEM

Voor onze actie WeGoSTEM zoeken we nog vrijwilligers. Doe mee via

Dwenguino FAQ and Troubleshooting

Overview of common questions and problems


Why do I get “Error Compiling” while verifying my sketch?
This message means that your code contains an error, in other words your code file can’t be translated into computer-language. Please read the orange error message: it will tell you where and what your error is.
If the error is “Dwenguino.h: No such file or directory”: Go to “Tools > Board” and select “Dwenguino”. If you can’t find Dwenguino in the board list, install the Dwenguino package, see install tutorial.

Why can’t I upload my sketch to the dwenguino board?
This can have many causes:

  • If you get a message “Error Compiling”, you first need to solve the code errors: see previous section.
  • Make sure you connect your board to the computer using an USB cable.
  • Hardware problems: make sure there are no shorts on the board and it isn’t touching anything metallic.
  • Try to reconnect the Dwenguino board to your computer and restart Arduino IDE.
  • Select the right serial port for the Dwenguino board in menu “Tools > Port” you should find an item in this list like “COMX (Dwenguino)” on Windows or “/dev/…usbmodem…(Dwenguino)” on Mac and Linux.
  • If you can’t find such an item in the list: on Windows this is probably a driver problem, follow the steps of the driver section on the install tutorial. On Linux there can be a problem with permissions, see according section on the install tutorial.
  • Bootloader problem: The dwenguino comes with a pre-burned bootloader to communicate with the Arduino IDE: If you’ve programmed the board once with a AVR-programmer or made a severe short, the bootloader can be removed. See this tutorial to burn the bootloarder again.
  • If you’re still having problems, contact us at

How can I retrieve my old code?
It is a good practise to save your code (from ArduBlock or Arduino IDE depending whether you are programming graphically or textual). Do not forget to add a version number to your file name, for example: "robotproject_v1". In your next test or big update you can use "robotproject_v2"... Advanced users should use a subversion system such as github or SVN.


Why doesn’t my board power up when I connect a battery pack or charger to the power plug?

  • There is a switch to disconnect the batteries, try toggling this switch.
  • Are the batteries charged?

Why are the motors running so slowly while my board seems to work fine?
Note that the motors require an external power source connected to the power plug and put the switch on. If you only power your board with an USB cable your motors will barely move. All other functionality can work with both the usb-cable and power plug.

Why is the text on the LCD display not / barely readable?
This is probably because the contrast is poorly configured. You can adjust the contrast by turning the potentiometer above the LCD display with a small screw driver.

Why isn’t my servo working?
Make sure you connect the wires with the right orientation. Ground wire (often a black or brown cable) should be connected to the ground pin (indicated with a ‘-‘ symbol on the dwenguino board).

Why isn’t the buzzer working?
Check if the jumper above the buzzer is installed: “JP1”.

Why isn’t my own sensor working as expected?
First of all check if the sensor is connected properly to the dwenguinoboard as stated in the datasheet:

  • “Ground”, “GND”, “-”, “Vss” pins should be connected to ‘-’ labeled pin.
  • “Power”, “Vcc”, “+5V” pins should be connected to ‘+’ labeled pin. Note that the Dwenguino board provides 5V on all ‘+’ pins, make sure your sensor is 5V compatible. On the expansion board there is one additional 3.3V power pin.
  • All analog output pins should be connected to ports A0-A7. Only on these pins you can directly measure the voltage level.
  • Other output pins should be connected to one of the digital ports: numbered 0 - 23. Make sure you use the same port number in your code. Also note that some ports share different functionalities: see pin-mapping table