Makes a lot of use of this documentation: https://github.com/KonradIT/goprowifihack/blob/master/HERO3/WifiCommands.md
Python script that controls the GoPro via REST endpoints on the camera's build-in wifi AP.
One drawback to this method is that the GoPro API only works over the AP that the camera broadcasts, which is not very strong or fast. The result is that it takes a long time from captures to transfer for each image (around 20 seconds), and it will be difficult to capture images any faster.
### Routes Used
#### Routes Used
-`http://10.5.5.9/bacpac/SH?t=goprohero&p=%01` - Activate shutter (take single image)
-`http://10.5.5.9:8080/gp/gpMediaList` - Retrieve media list from GoPro
-`http://10.5.5.9:8080/videos/DCIM/[DIRECTORY]/[IMAGENAME]` - Download image with path
-`http://10.5.5.9/camera/DA?t=goprohero` - Delete images on camera (so that SD card won't fill up)
## Webcam
### Webcam
Bash script that controls the webcam with `fswebcam`, which should be one of the faster options.
Round-trip times were about 5-6 seconds for each image.
\ No newline at end of file
Round-trip times are shorter, 5-6 seconds, and the connection is safer (direct cable as opposed to wireless). The
## Notes
- rsync in batches?
- --time-limit 30 // transfer for 30 minutes and then stop.
- --remove-source-files // remove files from beaglebone as they are transferred.
- Local mass storage might be a better option then trying to transfer these back to the cluster.
- do we need to take pictures all year? Only during bright months?
## Tests
| Camera | Resolution | Capture Time | Picture Size | Data Rate Sec | Data Rate Hr | Data per year |
|---|---|---|---|---|---|---|
|HZQDLN Webcam HD 1080P|1920x1080|~6s|~1MB|180KB/s|648MB/h|5.7TB/y|
