GoProController
GoProController copied to clipboard
joshvillbrandt
Loss of Communication to GoPros
I lose communication with the GoPros after some time. Usually between 30mins-2hours. Does the proximity between GoPros have any bearing? Is there a known firmware revision that works best?
I have found when this happens that the Ubuntu network manager shows the gopro as having several networks. Changing the poll rate in app/app.js doesn't seem to help either. For instance, what starts out as GoPro-1 will eventually look like GoPro-1 1, GoPro-1 2, GoPro-1 3, ... in the network manager.
Hey there,
I have definitely seen this before. Unfortunately, I think it is an issue with the camera itself.
Just for completeness, which GoPro model and firmware version are you using? For me this happens most frequently with HERO 4 cameras and substantially less frequently with HERO 3 and HERO 3+ cameras.
This could also have something to do with the NetworkManager on Ubuntu. Sometimes I have seen this and it seems like the act of me interrogating the wifi status brings the interface back up. Maybe something to wake up or restart the network manager every so often would fix this. More often then not though, it is the cameras that I need to restart before the wifi communication will continue.
By the way, if your computer does not have NetworkManager installed, https://github.com/joshvillbrandt/wireless will fail over to usingwap_supplicant, which might be a more robust method of controlling the wireless adapter.
I've noticed lockups for a camera I'm controlling, usually just when the camera is turned on from sleep. The proxy stops responding, though it is still running. I've found a reliable way to kickstart it back to life is to queue up a sleep command and restart the proxy service once or twice. It usually comes back after this.
I can only guess that there's some kind of data the proxy is getting from the camera that it doesn't know how to parse, causing the process to lock up or loop. This happens with a 3+ Black.
