Recent content by STM

Neither Solo nor the controller have a hardware clock. Their system clocks gets set to the GPS time once it has a lock. The current system time gets periodically written to a file. When Solo and controller are turned on the time in this file gets loaded into the system clock. It runs from here...

No responses to this?

1. I have not looked into how the controller iMX6 is communicating with the drone iMX6. However, I'm pretty sure it is not MAVlink commands. Communication between iMX6 and PixHawk is using MAVlink commands. To send commands from a PC to the PixHawk you send MAVlink commands to a mavproxy...

Throwing another hypothesis in the mix: What if it wasn't a hardware malfunction? Under these flight conditions, going down a hill (up- or downdraft on the hill) with a high descend rate, it is not unlikely the aircraft got into its own downwash, i.e. it went into vortex ring state...

Don't mix up DroneKit with 3DR Services. 3DR Services is the interface to DroneKit on Android. I was referring to the Python version of DroneKit. The Solo iMX6 code is using DroneKit as well. Of course you can use pymavlink directly. But DroneKit for Python makes life a lot easier.

Your commands have to get to the Pixhawk. And this happens via mavlink. DroneKit uses mavlink commands. It just provides a higher level access. You connect your PC to the Solo WiFi. To connect to the drone with DroneKit use the following line in your python script: vehicle =...

At a higher level than direct mavlink commands you can try DroneKit (DroneKit by 3D Robotics). I'm using it to automatically program missions. It is very simple to use. Sending direct flight commands is as easy. I don't know how you would interface to MatLab. I'm sure there are ways of...

Change Speed as the first instruction of a mission never worked for me. I figured out I have to place a Waypoint before the Change Speed instruction. I never had an issue since. Maybe the Set Yaw is usually doing this for you. And in the second flight the Set Yaw didn't lead to any movements of...

The same thing happened to me a few weeks ago, also with motor pod 01. I turned Solo on and off a couple of times. No change. So I took it home and replaced the motor pod with a spare. All worked well. Then I decided to find out what the problem was. So I re-installed the old pod. And it worked...

OK, i think i've found it: rc_remap_sample.py Thanks

Which *sample*.py files are you referring to?

What firmware version are you using?

For a proper orthomosaic you want constant pixel size. This means you require constant height above ground.

Are you sure about this? I would have thought the lag comes from encoding/decoding not the transmission itself. I can't think of something in the actual transmission causing such a big lag.

Front left was green the other day on mine (see pic). It was a smooth flight without incident. Usually I have the standard colours (front white, rear red). App 2.3.0, Solo 2.4.0, Autopilot 2.0.20, Gimbal 1.3.6, Controller 2.4.0, Controller Firmware 1.2.11 on that flight. I thought I had seen...