If you want to update your firmware to the newest version, here's how...
WARNING: We are unable to offer support Triggertraps with custom firmware, so please, if you decide to upload new firmware to your Triggertrap, please ensure that you understand what the source code does, how to revert your changes.
If you have any questions or if you need assistance, try our Triggertrap Forum or .
In summary: Please do not install new firmware unless you know exactly what you're doing!
1 ) Go to Arduino.cc to download and install the newest version of the Arduino software. This is software that goes on your computer, and will handle the uploading of software to your Triggertrap.
2 ) Get a USB Micro B cable. That's the same cable as you get for many mobile phones, or your Amazon Kindle, for example. If you don't have one, you can buy one from Amazon.com or Amazon UK - or from your local hardware dealer.
3 ) Download the most recent version of the Triggertrap firmware. The most recent version can be downloaded from Github.
4 ) Reset your Triggertrap by pressing and holding the 'start' button for 15 seconds. The screen will read 'Reset Memory' for a very brief period of time. If you see a short flicker on the screen, you've reset the memory correctly.
5 ) Now, find your Arduino data folder on your computer, and the Triggertrap files you downloaded. Copy the files in 'libraries' to the 'libraries' folder in your Arduino data folder. If you don't have a 'libraries' folder, create it, or simply copy the whole 'libraries' folder across.
6 ) Copy the 'Triggertrap' folder to your Arduino data folder. It should contain only one file; TriggerTrap.ino
7) Check which version of the Triggertrap you are using. If you have a Triggertrap v1, you need to go to the Libraries -> TriggerTrap -> TTConfig.h file. here, you will find a line called " #define TT_SHIELD". Comment out this line by adding two slashes right at the beginning of the line. This makes sure that the code is configured for use on Triggertrap v1.
8 ) If you are new to Arduino, you may need to install a FTDI driver so your computer can communicate with your Triggertrap. If you're not sure, it can't harm to update to the latest drivers; if you think you may have them installed already, then feel free to skip this step. You can download it here.
9 ) Open up the Arduino software package you downloaded in step 1. Select "Open", and then navigate to the TriggerTrap.ino file. This will open the TriggerTrap firmware.
10 ) Select the correct port from the Tools menu (Tools → Serial Port → ). The correct port will differ from system to system, but if you have listed with the words "tty" and "usbserial" in them, that's the one. (Your available serial ports may look different for Windows users. It was COM3 for at least one of our users, though alternatively go to windows->device manager->Ports (COM & LPT) to verify which is your USB serial port.)
11 ) Select the correct Arduino board from the list (Tools → Board → Arduino Pro 3.3v, 8 mhz, ATmega 328). This ensures that the Arduino software tries to 'talk' in a language that the Triggertrap can understand.
12 ) Upload the Triggertrap firmware to your Triggertrap by choosing File → Upload to Board. As you do this, two LEDs on the back of your Triggertrap will start blinking (Tx means the Triggertrap is transmitting information, Rx means it is receiving information). DO NOT UNPLUG your Triggertrap until it says "Done Uploading" in the Arduino software. It will look a little bit like the picture below.
13 ) Finally, reset the Triggertrap software one more time, by pressing and holding the START button for 15 seconds.
And you're done!
If you get an Port Not Found error: You need to install the FTDI drivers, see step 8.
If you get a lot of errors like "LiquidCrystalFast.h: No such file or directory", that means you haven't installed the libraries correctly, as described in step 5. Make sure the libraries are copied to the 'libraries' folder in your Arduino folder, then shut down and re-launch the Arduino software.
If you get errors like "avrdude: stk500_getsync(): not in sync: resp=0x30", it means you've probably selected the wrong board or port - double check steps 10 and 11!