Recent content by human

Oh, come on, where's your spirit of adventure? Humans can survive for up to 15 minutes in 0 degree water. That should be long enough to find your drone. ;) But seriously, what I was hoping to convey was that the last GPS position might not be too far off the actual location, and depending on...

FWIW, I dropped my Solo into the ocean (pilot error) about 1000 feet off shore in 20 feet of water. Swam out 3 days later with a snorkel and GPS, and found it pretty easily. It was actually only about 10 feet away from the last GPS position, which is amazing (or lucky) given the position error...

I flew mine into the ocean a couple of weeks ago. It was 1000 feet off shore, but amazingly. I was able to find it when I went looking for it a couple of days later. I didn't expect to be able to reuse anything but the props and shell, and that was certainly the case. Everything electronic was...

Wow, those are some nice pics, pyrate. I can never get my closeups to focus that well!

That is, unless you're flying a DJI drone. In that case, 100ft seems to be the new limit, unless you comply with their draconian registration and software update policy. :)

Out of curiosity, did you experience the ESC reset with the "MOT_THST_MAX" parameter set to the de-rated (0.94 / 0.965) value? I'm assuming there are some (ugly?) non-parameter based fixes (hacks?) as well, otherwise I don't see why the ArduPilot wouldn't just include the changes in master for...

I have a feeling it may have been flying without a power cycle that causes the jitters. I never tried it that way myself (I always power cycle after a firmware update, just out of habit). When I have a second, I'll give it a try, and see if I can reproduce the problem. I'm still not sure why...

Sorry to hear you had problems. I'd like to try and figure out what was different about your drone setup. Did you turn off and on the drone after installation? Had you made any other config or parameter changes before you started?

Wow, that sucks. There's nothing like that sinking feeling you get as you see your Solo plummeting to the ground. :( On the bright side, you've now got a lot more spare parts. :) Hopefully somebody will come out with a 3rd party housing we can put all of our spare parts back into...

Sounds like fun to me. I'd just give it a try, watch your battery level carefully, and turn around early. Just as long as you stay less than 400ft above the ground (even if you're going up the side of a mountain), you're legal. (assuming you're not in a no-fly zone of course) Just watch out for...

@XevetS, I don't have many examples, but take a look at the default initialization file here: solo-led-control/init_leds at master · hugheaves/solo-led-control · GitHub It uses a phase offset to make the rear lights blink at alternative times. Also, I've only been able to get it to work with...

Whoops, sorry about that. I guess it actually helps if I push the changes to github. The new version is there now, so if you download again, it should work.

I've made a change to the scripts that run on Solo that should greatly improve the response time when running led_control.py. On the new version, I only get a 1-2 second lag between clicking the button in Solex and the LEDs changing color. If you run the install script, it will update...

If you programmed Solo to climb straight up at its maximum ascent rate, it would reach roughly 15,000 feet altitude before the battery ran out. (Depending on load) Horizontally, you could go around 60,000 feet before the battery ran out and it dropped to the ground. These are both rough...

Yeah, I've got to agree... Solo controller is one of the worst designs I have used. Between the full color LCD that displays virtually no useful information, the general lack of control buttons / toggles, the ridiculous size and weight, I really don't know what they were thinking.