m500 is not connecting to QGC or my DX6e controller

Moderator

@shippwr3ckk the drones all ship preconfigured and flight tested. There is definitely PX4 installed. It's on the flight core portion of the m500 and not on the VOXL. voxl-mavlink-server is used to communicate between the VOXL and the Flight Core

shippwr3ckk

@Moderator Got it. Why is the flight core not responding to the VOXL then? I have everything configured as recommended and I still can't get the drone to register with QGC.

shippwr3ckk

Update, I still have not been able to connect to the QGC.

What am I doing that could be causing connection issues?

How do I properly communicate with the PX4 content with the mavlink-server?

My WIFI is also not labeled at "VOXL:XXX.XX, etc..", is that an issue?

tom

@shippwr3ckk If you'd like to get back to a factory state you can download the latest VOXL SDK (1.2.0) and load the SDK using it's /install.sh script

tom

@tom You can also load your flight core with the latest version of px4 which is contained in the flight-core sub-directory of the SDK tar

shippwr3ckk

@tom

Update, I did not do a factory reset. But, I can connect to QGC but it only needed a wifi connection and not the "ssh root@". Do I need to "ssh root@" everytime I need to connect to QGC?

As of now, I cannot get the drone to connect to my radio or get it calibrated. It will not respond to any commands the QGC tries to send. Any ideas on what I should do next?

tom

@shippwr3ckk "Do I need to "ssh root@" everytime I need to connect to QGC?" I'm not entirely sure what you're asking here. Can you give some more detail of the process you're having to do to establish a connection to QGC that involves ssh

shippwr3ckk

@tom In the command prompt, while connected to the drone's wifi, I usually put in the "ssh root@_ip_ command. I don't know the full reason to type this but I saw it in the instructions when establishing a pre-flight. I figured it was another connection step when configuring with QGC.

tom

@shippwr3ckk SSH is just a way to access the drone's terminal remotely. It will give you access to the same terminal you get when you connect via USB and use adb shell

Running ssh root@DRONE_IP will give you remote access to then run commands. Running just the SSH command alone and then nothing else doesn't really do anything.

shippwr3ckk

@tom Thank you for the info!

After messing with it some more, I think it might have to do with the batteries I am using. Because the drone is currently turned on and my laptop is connected to the drone's wifi, but it is no longer connecting to QGC, even with a micro USB connection too.

The battery I am using is a "14.8V, 45C, 4S1P, 3300, 4 Cell battery". And it will only read on the QGC when it is around 30-50%.

Any ideas what I should try next?

shippwr3ckk

Thank you for the info!

After messing with it some more, I think it might have to do with the batteries I am using. Because the drone is currently turned on and my laptop is connected to the drone's wifi, but it is no longer connecting to QGC, even with a micro USB connection too.

The battery I am using is a "14.8V, 45C, 4S1P, 3300, 4 Cell battery". And it will only read on the QGC when it is around 30-50%.

Any ideas what I should try next?