I saw the threads (including Rowse). Lets take things a piece at a time. It is always good when troubleshooting to cut your problem in half. I learned this long ago in tech school. From what you have said (partially in the other threads) is that you have narrowed it down to (I believe) the GoPro being powered down (and thus the recording stopped abnormally).
If the Solo is the culprit then it has to be turning off the GoPro. If the GoPro turns off (or otherwise corrupts files) without Solo, then it is the GoPro. Depending on which, you can follow that diagnostic path, but it is important to try and determine which. I know that sounds simplistic, but it is an important step not to skip.
I know it may also sound crazy, but try leaving the GoPro in the gimbal without connecting it to the bus on the back. That way you keep as much the same as possible, and remove only one possibility. Put a piece of thick tape over the buss connector so that you know it isn't connected. Tape the Gopro in if you have to. Connect the hdmi connector to the gimbal as usual. Turn on the GoPro and recording. Fly several flights this way.
Put it back to normal. Fly the same number of flights. Ideally in the same conditions, temperature etc.
Take it out of the Solo, put it in something to insulate it slightly (just like the gimbal) and plug it in to power, then let it record a while.
By doing thesae things, you are attempting to keep as much the same as possible, while eliminating only one possibility.
I know you are fairly convinced that it is the Solo/Gimbal, and it is possible, but given that there are only a few (two I think) other reporting this, the details of which are a little sketchy, and this is a also known issue with some (bad) GoPro's and cards (look at the GoPro forums) I would make sure I had a troubleshooting strategy that includes the GoPro as a possibility.
I understand the idea of "what has changed?" and that is useful to try and understand what is happening, but it isn't always right, and many times people put to much weight on it, concentrating only on what has changed. As they say "correlation is not causation" and sometimes a problem will show up at the same time as a change, just by chance....
As I mentioned on another thread, I have had over a dozen GoPro's, and I have had two that did this. One did it only after a while, and only when it was plugged in and operating (after about 1/2 hour) and as it turns out was more temperature sensitive over time. I originally thought it was a firmware update, as it started showing up (or at least i noticed it first) after that. In the end, it got steadily worse, and I actually put that one in the refridgerator as a troubleshooting step to isolate that behavior (it would reliably work well if it was cold).
The trick is to isolate the behavior and cut the problem in half. Another way to do that in this case is to use another GoPro (borrowed if necessary). Again, just as a troubleshooing step to see if the problem follows the Solo or GoPro... You could try another Solo, but that is a little tougher to get.
I do know that if you were to get a GoPro at Best Buy, you would have at least 72 hours to return it.... With some planning, you would have enough time to test them side by side, which might be very instructive.
Just sayin
Last edited:
