Blink - Troubleshooting Guide

This document is a supplement to the user manuals for our Blink time lapse controller product. The manuals should be read in conjunction with the troubleshooting Q & A below.

Before consulting the troubleshooting guide, make sure that:

  1. Your GoPro is running the most recent firmware available
  2. Your Blink is running the most recent firmware available
  3. You are using an SD card that has a minimum read and write speed of 30MB/s (U3 rating). Our website has a link to an SD card speed tester to determine if your SD card has the required speeds for reliable use with the GoPro cameras.




Troubleshooting Questions

Blink is designed to be powered from the GoPro battery, so any external power supply should be attached to the GoPro's USB port to keep the internal battery charged. Blink's USB port is used for updating firmware and does not charge the GoPro battery.

Blink firmware will be released periodically with new features and/or bug fixes. Head over to this page for detailed instructions.

Make sure that the file name has not been changed or Blink will not recognize the file, for example, "blink_update(1).bin" or "blink_update.bin.txt". When updating the Blink firmware with the OTG cable, make sure to have Blink unplugged from the GoPro camera while having Blink and the flash drive connected to the OTG cable before the male USB-A end is plugged into a 5V DC source. The USB flash drive must be using the FAT32 file format to be able to perform the Blink firmware update.

The FAT file saving format is the default format for PC and used with most USB flash drives. Large capacity drives might be using the exFAT format. Make sure that the drive is using FAT32 which is commonly referred to as just FAT. If you are using a MAC, the following link explains how to format a USB flash drive to the FAT32 format.

Blink WiFi can be turned on via the wired remote that ships with the product. Plug the remote into the 2.5mm jack on the side of Blink (on the opposite side from the mini USB port. It is on the right hand side when looking at Blink from the back of the camera).

Blink with controller

Hold down the wired remote button for 3 seconds - you will see the LED on the back of Blink flash cyan three times to indicate WiFi signal has been enabled. The LED will continue to flash blue every 5 seconds while WiFi is active. Blink WiFi can be turned off manually by pressing the wired remote button again for 3 seconds and the LED will flash cyan twice to indicate WiFi is turned off. WiFi will also automatically turn off after 15 minutes.

Why does Blink's WiFi not activate when I use the remote?

Blink requires more power when the WiFi signal is active. If Blink's LED flashes purple, this is typically an indication of insufficient power available to activate the WiFi signal. Make sure to use a fully charged battery or have an external power source plugged in when activating WiFi. Once the new shooting schedule has been programmed, WiFi is no longer needed for regular operation and the system can continue to run off a lower charged battery.

Why does my device not stay connected to Blink's WiFi signal?

Some phones and computers have a WiFi setting that will automatically connect to a known WiFi network with the strongest internet signal rather than staying connected to Blink. Since connecting to Blink's WiFi network does not provide external internet access, some devices will not stay connected. You might need to temporarily deactivate this setting or remove other known networks in the area for the period required to set up the new shooting schedule of Blink.

I have Blink powered from an external battery pack. Why does the shooting schedule only last for one day when I still have power in the external battery pack?

Most of the batteries on the market, including ours, have an automatic power saving feature which turns off the battery if the battery is not constantly supplying power to a device. If the GoPro is powered off for more than a few minutes between triggers, the external battery might automatically shutdown due to inactivity. However, our V15 and V44 battery packs have two modes of operation, the standard Automatic Off mode and an Always On mode. The Always On mode is important to prevent the battery from automatically turning off when insufficient current is being drawn due to the camera being turned off by Blink between triggers to conserve power.

If using our V15 or V44 battery, make sure to activate the Always On feature. It is easiest to determine the battery's operating mode when the battery is disconnected and neither charging or supplying power. When in Always On mode, if you double tap the power button a few times, the LED should continue to stay lit. If the LED goes dark between every other double press, you are not in Always On mode. To switch modes, hold down the power button for six seconds. If the charge indicator flashes 3 times and stays lit for a second or two, you are now in Always On mode. If the charge indicator flashes 3 times and then goes dark, you are now in Automatic Off mode. If you are not in the desired mode. Press the button again for 6 seconds to change modes.

Blink is turning the GoPro on at the scheduled time, but why is the shutter not being triggered?

Make sure you do not have have the "Enable Scripting" checkbox enabled at the top of the UI. If this checkbox is enabled, Blink will only turn the camera on at the scheduled time with no further function since it expects a script on the camera's SD card to control the functionality once the camera has been turned on. If you are not using scripts, make sure to disable this checkbox for regular operation.

Why is my continuous video footage being split into multiple files?

The splitting of the files into sections is called "chaptering", and the final video clip can be joined back into a single file by using GoPro Studio, Adobe, or another video editing software. The chaptering a recording into multiple files reduces the chance of losing the entire footage if the power is suddenly lost, the camera crashes, or another issue causes the last recorded file to become corrupted to the point where it cannot be repaired by the camera. The length of each file is determined by the recording mode used but has a maximum file size of 4GB per file. This is because the GoPro camera saves files to the SD card in the FAT32 format which has a maximum file size of 4GB. The GoPro requires that the SD card has a FAT32 format, or exFAT for 64GB or larger cards, however, the file will still be saved in the FAT32 format that has a maximum file size limited to 4GB. 

Please connect only CamDo approved accessories to these jacks.  Do not connect any live voltage source, such as your solar panel or battery, to these jacks.  Doing so will damage your equipment.

What are the status codes in the Blink Error Log?

When Blink encounters a problem, an entry is saved into the Blink Error Log. You can access the Blink Error Log when connected to Blink's WiFi and using your webbrowser to navigate to the URL: or by clicking the Error Log link at the bottom of the standard Blink programming UI.

A few of Blink's status codes are as follows:

  • STATUS_CODE: 10 is an indication that "the Blink Email notification has been successfully sent".
  • STATUS_CODE: 11 is an indication that Blink "failed to send email and will retry 10 seconds later"
    Blink will attempt to send the status email with a 15second timeout up to three times.
  • STATUS_CODE: 13 is an indication that Blink "did not send an email after multiple attempts and will not continue trying"
  • STATUS_CODE: 16 is an indication that "Blink Email has the incorrect password to the WiFi network"
    Blink firmware v2.00 has a 16 character limit on the password and Blink firmware v2.01 has a 32 character limit on the password. If your WiFi password is longer than the character limit, Blink will truncate the password field causing a failed connection. For use with Blink, please ensure your WiFi password is below the character limit.
  • STATUS_CODE: 18 is an indication that "the SSID was not found" or that you are "attempting to connect to WPA PSK without a password"
    Blink has a 32 character limit on the SSID. If your WiFi network's SSID is longer than the character limit, Blink will truncate the field causing a failed connection. For use with Blink, please ensure your WiFi SSID name is below the character limit.
    Make sure that WiFi router is in range of Blink. Note that Blink does not have as advanced of a WiFi antenna as most phones/computers so Blink may have difficulties transmitting to the router although you can detect the WiFi signal with another device in the same location. We always recommend that the router should be placed as close to the GoPro as possible to provide an adequate signal strength from Blink to the router.
  • STATUS_CODE: 250 is an indication that Blink "was not able to turn the camera on"
    When 250 occurs, it is typically an indication that the system either has insufficient power to turn on the camera, or the GoPro has crashed and is no longer responding.
  • STATUS_CODE: 251 is an indication that "the camera did not respond to the command request".
    When 251 occurs, Blink will attempt the command another two times before resetting the camera if it does not respond (reset function is only available on HERO4 camera's with a Black colored Blink). If the 251 status shows up less than three times, your camera has been able to perform the command after another attempt has been made.
    251 errors are typically due to the use of an SD card that does not meet the GoPro camera's read and write speed requirements or the camera has entered USB mode.
    • A slow SD card can affect the timing of both the Blink and GoPro camera resulting in issues such as: corrupted footage, overheating, missed triggers, and camera crashes.
      The GoPro camera requires an SD card with a minimum read and write speed of 30MB/s (U3 rating) for reliable operation. An SD card's read/write speed can significantly decrease as the card becomes more full, and drop below the required 30MB/s read/write speed if the card is not U3 rated. Our website has a link to an SD card speed tester to determine if your card has the required speeds for use with the GoPro camera: .
    • The GoPro camera will not respond to commands from Blink or the physical camera buttons when in USB mode. If the camera is switching in and out of USB mode, it can be slow to respond and prone to failure. The GoPro camera will enter USB mode if the data lines of the USB cable are connected to the GoPro camera. If your camera is entering USB mode, try using another USB cable without the data lines, a different 5V power source, or a USB data blocking adapter.
  • STATUS_CODE: 254 is an indication that Blink has attempted to "reset the GoPro camera"
    This feature is only available when using a HERO4 camera and the system is powered through Blink's USB port (black colored Blink only) with the GoPro battery removed. The HERO3+ camera and white colored Blink require a charged GoPro battery inside the camera for reliable operation and cannot use this reset feature.

Why does my Blink Log show dates from Jan1, 2015?

The GoPro camera has a small internal (not removable) battery that is used to retain the clock time when all power is removed. The GoPro has either crashed or lost power for a period of time causing the clock time and date to become reset to the default of Jan1, 2017. When all power is removed, Blink will only retain the programmed shooting schedule but does not have an internal battery to retain the time and date settings. When power is restored to Blink, it will determine the clock time and date information from the GoPro camera to resume the shooting schedule.

I didn't find the answer in the Troubleshooting Guide, what is the next step?

Please contact CamDo support and provide information about your setup and problem including:

  • GoPro camera type and firmware version
  • Blink firmware version
  • Type of SD card being used
  • Type of power supply being used
  • A screenshot of your Blink schedule(s)
  • A screenshot of Blink's Error Log from this page:
Back to Top