@Dmitry has provided an iptables script to communicate with a GoPro payload from the topside. It seems like other user DIY payloads could also be communicated with if they provided a WiFi AP like the GoPro or possibly just use sockets. My intent is to convey a basic toehold into payload communication that other DIYers could expand on.
Refer to Dmitriy’s github link for instructions :
Use GoPro official Android app with Trident Drone. | [“Use GoPro official Android app with Trident Drone”]
I only changed one item from Dmitriy’s instructions. My TSAP IP was 10.1.1.233 vs 10.1.1.243. It’s used when setting the TSAP WiFi connection → Advanced → Gateway IP.
Once the above is working, the following scripts copied to the /home/rov directory will execute gopro.sh like above, and also provide more visibility.
GoPro Payload.zip (3.6 KB)
gopro-setup.sh # Executes the following scripts
gopro.sh # Dmitriy’s iptables PayloadProvision for GoPro
gopro-check-PP.sh # Display IPs used in gopro-PP.sh
gopro-check-connected.sh # GoPro payload WiFi AP connected and signal level
GoPro HTTP Cmds.html # Basic commands, work in progress. Edit PASSWORD to yours.
I used JuiceSSH on Android to login to the Trident via the TSAP and execute ./gopro-setup.sh.
A good reference for GoPro commands and APIs is :
GitHub - KonradIT/goprowifihack: Unofficial GoPro WiFi API Documentation - HTTP GET requests for commands, status, livestreaming and media query.
I didn’t have any success using the GoPro Capture or Quik apps. I used the Android Camera Suite app and GoPro HTTP Cmds.html to communicate with the GoPro3+ Silver via the TSAP.
If you find this useful, consider contributing to Dmitriy’s iOS Cockpit Patreon account since there’s finally some payload communication.
DimaRU is creating is creating control app for the Sofar Trident Underwater Drone. | Patreon.