Recent content by blackbandit

Thanks Chuck, look forward to hearing the updates in the future.

I bought this Solo the day it released from Best Buy, flew it for several months with absolutely no issues at all. Not a single scratch on this bird, no flips, crashes, etc. I am selling to fund other hobbies and hope someone will get good use out of it. I still have all of the original boxes...

How do you like the Samsung tablet? I'm thinking that's what I'll get for a dedicated solo tablet.

Yea that's why I like putty, the progress bar and status. Here's what I do, I start the controller first, so it emits the WiFi. Connect to the WiFi and ready putty to connect to the solo. Power up solo, and as soon as it's finished it's start up sequence, connect to it with putty and begin...

Yea I'm surprised you are having these issues, what SSH client have you been using? I've had great success with putty.

I take it you are doing a tower mission, for it to lose connection and keep going. So yes, really the only data you can use would be the dataflash log. Can you tell me the steps you have taken to get the dataflash logs?

As mentioned, stick calibration will fix this issue.

Try hooking the gopro up without docking it into the gimbal. Just support it yourself while it levels out. The HDMI connection on the side of the gimbal is straight passthru so if you get feed there, then something else is wrong. Hero bus does not affect the HDMI passthru, hero bus is used to...

Yes you need to run the script while ssh'd in the solo, not the controller, to flush the logs from the pixhawk. They will be sent to the logs folder in the solo. Then you can copy them to your local hard drive and have fun with them in MP.

The .bin file is the dataflash log from the solo, it is located on the solo. It has a lot more information than your tlog pulled from the controller. In MP you have to go to the dataflash tab to load one of these logs, and it does not do any playback of this log.

I have been using putty to log into the solo, not the controller. Once connected, I log into the root folder with the known password. I then run (loadLog.py latest) which flushes the most recent dataflash log from the pixhawk to the solo log directory. This also gives me the most recent...

@rrmccabe I've been meaning to update this. I've found out today how to use the script you suggested and have been downloading dataflash logs all night. Now, the latest command will only pull the last dataflash log available. Then you can use each of the previous log numbers to download the...

This is from my experience on the Solo owners FB page. I'll copy in the links this evening when I get to a computer. It might just be me, but of all of the people that have posted about a pod "clicking" and solo not booting, eventually let to a 03 motor short. Even one guys motor pod caught...

Use the manual to get the instructions to remove a motor pod. Then remove the #3 motor pod. With the motor pod removed, now try and turn it back on. It's a known issue right now for the #3 motor to nuke itself. Earldgrayjr beat me to it, but regardless 3DR is replacing these for people.

Right, no authentication with UDP connection. It always uses port 14550 too. I'm curious as to what the bottleneck is. Is the baud rate too low? Is the issue because we are going through the WiFi access point on the controller and then into the solo?