'''
Connect to flight controller over USB and get live sensor output
'''
import dronekit
from dronekit import connect, VehicleMode
import time
# Connect to the Vehicle (in this case a UDP endpoint)
vehicle = connect('udp:192.168.4.1:14550', wait_ready=True)
Like it should provide you with like a wifi hotspot to connect too?
When I browse to 192.168.4.1 and look at the setup for the wifi bridge, there are some options I don't understand (I'll admit I have little understanding of IP stuff)
So like this doesnt work for you?:http://ardupilot.org/copter/docs/common-esp8266-telemetry.html#connecting-from-a-ground-station
maybe try running mission planner as admin as well
or disable firewall
That causes connection failure
does that also show connection failure?
Anything obvious I should change?
With that station IP they list?
and with 192.168.4.1 see if that works
Wait in mission planner when you try to connect via UDP does it just prompt you with a listening port?
As more context, I have been able to successfully connect to the drone over USB and read the attitude. When I run a connect command from the shell (after connecting my computer to the drone WiFi) I get a link timeout error almost immediately (no heartbeat in 5 seconds).
Update: We have working Wi-Fi control! Two things were previously wrong and prevented us from connecting the drone to either Mission Planner or a dronekit script. First, we found from https://diydrones.com/forum/topics/wifi-telemetry-with-cheap-esp8266 that our telemetry connection from the FC board to the Wi-Fi board was wired incorrectly. This wasn't clear from the Ardupilot documentation, since it uses a Pixhawk in the wiring diagram, but those connections aren't labeled on the Pixhawk side. R goes to T, apparently. Second, the IP address to use is not the IPv4 address I find when I look it up on my machine, but the 0.0.0.0 that I found in the Wi-Fi board setup. Now everything appears to be working fine.
Is there a way to send trim commands with a dronekit script? We've got our drone taking off and trying to hold altitude, but it's spinning wildly in yaw. I've verified the motor order, spin directions, and prop orientations and locations. I also tried running ESC calibration through Mission Planner, but since we don't have an RC transmitter (full Wi-Fi control) I don't know if I did that process correctly. We're getting spin of about 2 rotations per second, counterclockwise.
Channel 4 is yaw
Hi Everyone, I've been trying without success to connect with a simple dronekit-python script to my drone running navio2+rp3. Connection to the drone works perfectly with both QGroundControl or APMPlanner ... connection works directly via the Wifi of the Raspberry since both drone and laptop running QGC or APM are connected to same wifi router. On Ardupilot running on Navio2 I have edited the file sudo nano /etc/default/arducopter with the configuration #TELEM1="-A udp:192.168.1.108:14550" where 192.168.1.108 is the IP address of my laptop. The droneKit script I'm using is vehicle = connect('192.168.1.114:14550', wait_ready=True) where 192.168.1.114 is the IP address of the drone on the wifi network. I simply run this script on my laptop. My goal is to connet to the drone, then get info about telemetry and send instructions for missions. Unfortunately this is not working ... any idea why?
Hi everyone, can someone explain why I can only communicate with multiple SITL instances when they start their own mavproxy instances? I can only communicate with max 1 SITL instance if I connect directly to SITL instances. This seems odd as both scenarios have distinct port numbers? I sifted through some of the previous gitter messages but I'm still confused
may i have a childish question?
how to build an app with these scripts?
by which way?
and so far I can just connect Qgroundcontrol/APM with Mavproxy to set up fly plan