This post will describe how to control a GoPro camera (usually mounted on a gimbal), via a Raspberry Pi with a USB WiFi dongle. 

3689649827?profile=original

The ideal Raspberry PI for this setup is the A+ model because it is small and has the needed single USB port for the WiFi dongle. 

Parts List:

1 GoPro Camera 

1 Raspberry PI (suggest A+ model, but any PI will work)

1 USB WiFi dongle (PI approved) Suggest this one: AirLink N150

2 Jumper wires or 1 servo header that can plug into 1/10th center pins (with center power pin removed)

1 APM or PixHawk board

Of course, all of this is mounted on your Quad or Plane or whatever. On my hexicopter, the PI is powered by one of the ESCs UBEC outputs, where I cut a micro-usb cable and soldered the 'red' and 'black' wires to the power output of the UBEC of the same color. The other two USB wires are not used.

Setup:

Step 1: Enable the GoPro WiFi access:

The first step in making all of this work is to configure your GoPro camera to accept a WiFi connection. The camera is actually a WiFI access point. 

The details on how to setup your camera is here. If you can connect the GoPro App to the camera, then you can connect the Raspberry PI. You should verify that the GoPro WiFi is working with the GoPro App BEFORE proceeding to connect the PI. You can pick a unique access point name for your camera and use the same name in the Raspberry PI configuration when connecting to the camera with the PI.

Step 2: Connect the Raspberry PI to the GoPro Camera's WiFi:

Once you have established the camera's access point and assigned a name and password, you can make an entry in your PI's network configuration file to configure the connection.

From a shell prompt type the command:  sudo nano /etc/network/interfaces

Add some lines to the file as follows:

allow-hotplug wlan0

iface wlan0 inet dhcp
wpa-ssid "mygopro"
wpa-psk "mypassword"



Reboot the PI and it should automatically connect to the GoPro.

Step 3: Communicate with the GoPro

The GoPro camera should have the standard IP address of 10.5.5.9. If you can ping this address, you have successfully connected to the GoPro so now you are ready to send it commands.

The list of commands are here.  The camera is controlled by sending HTTP request commands in the form of a header string. 

for example, this string turns the camera on:

http://10.5.5.9/bacpac/PW?t="wifipassword"&p=%01"

Where 'wifipassword' is the password you set when configuring your GoPro.

You can experiment with sending commands with a web browser to get familiar with how to control the camera with web requests or write your own scripts.

Step 4: Use a Python Script to Control the Camera

Attached is a sample python script that will listen for a signal on GPIO pin 5 on the PI header, and send a request to the camera to take a picture when triggered.

gopro.py

To use the code, start the python script after connecting to the camera with the following command:

sudo python3 gopro.py -photoMode

This will start the script with the camera set to take pictures. If you want it to trigger a video instead, leave out the '-photoMode' option.

Step 5: Configuring APM or Pixhawk to send the signal to the PI

To use this setup with the APM or PixHawk control board, you need to connect the output of the 'relay' pin (A9 on the APM), to the GPIO pin 5 on the PI (or the pin of your choice).  The script is configured to use GPIO pin 5.

Here is a picture of the APM board from This link

3689649845?profile=original

The PI pinout is here

3689649876?profile=original

Connect Pin 29 (GPIO 5) on the PI to A9 (S) on the APM, and GND pin 30 on the PI, to GND A9 (-) on the APM.  Check the link on the APM website for the PixHawk settings for the relay output pins as I have not used PixHawk (yet).

Step 6: Configure your Radio to Trigger the Camera

In Mission Planner, you will need to select which channel on your radio to assign to trigger the camera input. 

This link describes how to configure the shutter.

3689649750?profile=original

Select "Relay" for the Shutter output (not RC10 as shown in the above image example).

Then set the Ch7 option to "Camera" as shown here:

3689649897?profile=original

This can also be set on the "Advanced Parameters" setup area.

Step 7: Start Script on Boot:

To make all of this automatic, you can configure your PI to always connect to the GoPro and start the script when the PI boots. Or you can do it manually when you want to fly. 

To make it automatic, you can modify your '/etc/rc.local' file to make the script start on boot. Here is a sample rc.local file:

rc.local

Once you have completed all of these steps, you should be able to trigger the camera to take a picture with a switch assigned to Ch7 on your radio. 

If you want to GeoTag your images, you can follow the instructions at the ArduCopter GeoTagging page.

Happy flying.

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • @Marc,   You have to compile the driver and install it in the kernel modules.  You will need the headers for your kernel to build it.    To install the headers, use this link:  https://github.com/notro/rpi-source/wiki

    You can build the driver then with the "make" command in the driver source folder, and then "sudo make install".  . Reboot your PI and it should see the WiFi dongle.

    notro/rpi-source
    Raspberry Pi kernel source installer. Contribute to notro/rpi-source development by creating an account on GitHub.
  • Hello Patrick,

    I'm trying to configure my RPI with Netis-WF2561 Wifi dongle. Can you help me to install Wifi Driver? Wifi dongle is OK on the MacPro but I do not know how to install it on Rasberry. I downloaded the Linux driver but I'm stuck with the installation process...

    Thanks,

    Marc

  • Patrick, thanks. I'm downloading NOOBS now from the Raspberry site and will install on a micro SD card.

    Downloads
    Download free software for the Raspberry Pi, including NOOBS, Raspbian, and third-party operating system images. Beginners should start with NOOBS.
  • @Richard, make sure you also get the OS for the Raspberry PI.  You can download it and install it on a micro SD card (8gb or larger), or buy a card with it pre-installed from the Raspberry PI foundation. 

  • Thanks Patrick!  You've been extremely helpful!  I've got all the parts on order so hopefully later this week I'll be able to let you know if I'm successful or not. Again, thanks!  btw...for anyone in the same boat, here are links on Amazon for ordering the Raspberry, the AirLink, and jumper cables.

  • @Richard, I think the relay pins on PixHawk are Aux 5 and 6 (pins 54 and 55).  The documentation is here: http://copter.ardupilot.com/wiki/common-optional-hardware/common-re...

    You can use the same pins on the Raspberry PI as the APM described above.   Those jumpers should work fine. Alternatively, you can use a 3-pin header, commonly used for servos if you have one laying around. You need female on both ends. 

  • Thanks Patrick.  That's very helpful. Regarding the "2 Jumper wires" listed under the Parts List at the beginning of the blog, is this a 2 pin jumper? Female on both ends?  Here's what I found link.  Also what pins do they connect on the Raspberry and on the Pixhawk?

  • @Richard, All you need is the A+ model Raspberry PI with a WiFi dongle. You can buy them online for $25 each. To trigger two GoPro cameras, you will need to change the IP address of one of them to something other than the default 10.5.5.9.  There are a few blogs online that describe how to do this. Then, in the python script, just send a second trigger command to the other GoPro.  You don't needy any extra hardware, it should work. 

  • I have the same need to trigger a GoPro Hero 4 with the Pixhawk.  Ideally I need to trigger two at the same time.  I'm new to this sort of endeavor so does anyone know someone with the technical skills to build this Raspberry PI device?

  • @Glenn,  the latency is about 1 to 2 seconds, which is not too good for FPV, but it's good enough for pointing the gimbals so you can see what you are recording. 

This reply was deleted.