Wow. Not bad at all for a first timer (or an old timer).
Tip 1: careful that close to the ground. The barometer isn't perfect. If air pressure changes (for example as a storm approaches), it will trick the barometer into thinking the Solo is higher (or lower) than it is. You could run the same cable cam and run into the ground.
Tip 2:
Experiment a lot with the way cable cam works. Because it generates spline curves between points on the cable, the flight path may arc around into trees or arc down into the ground. So I build the cable, then test it slow first. Then test it faster in the opposite direction, keeping an eye out for issues.
Thank you, Erik. But, complimenting the operator of a Solo flying MPCC is a bit like complimenting a chef on the roast beef. (The cow did all the work.)
** Regarding baro, are you saying that flying low to the ground is not using GPS for maintaining height, but relying on baro? If so, at what height is GPS positioning reliable? (I not understand how the two work together.)
Yes, the shot would have been more tasteful and dramatic at a slower speed. I was flying that at full speed just to see how it dependable the software tracking would be. In fact on a subsequent run of the same cable, Solo jumped the track and kept going in one direction. Tech support said it was probably due to the magnetic interference they were seeing. (I was pretty close to utilities and large earth moving machines, so I can buy that.)
Thanks for your tips.
Assuming that was cable cam and assuming that you want to make smooth video with nice transition then yes.
Looks real good
Actually, Ed, I was motivated to post my inadvertent thread hijack by your comment on the cinematography market... and then by Steve's comment regarding the bar for autonomous camera work set by Solo. I'd bet that if I send my clip to a cinematographer and explain how easily a rank amateur could pull it off, he/she would immediately want Solo on the set.
And that cable could be refined and made even smoother. I had about 20 points on it, and I'm sure it could have been made much smoother with about 1/3 less of them.
Oh, and tip #3. Learn to to/land/fly in manual mode. This is very important for the day your solo has GPS issues.
Thank you, yes, Ed. I haven't flown a smart shot since early July—just working on GPS FLY and manual FLY. I've quickly learned that GPS is not going to serve me well in close at low height... which is my only disappointment. (I had hoped to pull smart shots on close work near buildings in an urban environment.)
In addition to tip #3, stuck buttons on the controller and fw glitches almost mandate that you program the "A" button or the "B" button as a manual mode. It may or may not allow you to regain control but it's worth the effort just in case.
Thank you, Don. I do have A and B set manual, and fly ready to hit pause.
Yes. The stuck buttons is an issue I've experienced on one controller (that's been in some dusty desert like conditions - grit got into the buttons) . I just keep an eye on it and use my fingernail to quickly unstick.
Erik, it's the power button that's sticking for me, and I think it is powering down the controller... and sometimes preventing it from completing the power off cycle. It hasn't happened in mid-flight, but it has happened just as I was getting ready to fly. The pinky trick isn't likely to serve me well if controller powers off when Solo is in the air.
that takes a lot of balls to fly solo so close to subjects/ground
it can drift easily....I would keep at least 25ft away from objects....I try not to fly below 60ft
"Balls?" Well, let's say, since it was my 2nd batt, "naiveté." If I do a high speed MPCC at that height again, we could say, "stupidity." Thanks for the advice. However, I do plan to try to incorporate low height shots as transitions most of my projects. I am learning that I will have to be extremely cautious, not only to protect the investment, but to avoid damaging property and causing injury.
Thank you all for your advice. And again, apologies to kabong57 for the hijack.