Very slow when connecting via Mission Planner

Hi all. I’m a little new to Ardupilot and still learning things on the go, so I apologise if this question is something basic.

I seem to be having trouble connecting to the ground control via Mission planner.
It especially takes quite a while when I turn the system on the first time in the day. I’m hoping to narrow down what is causing this problem. (It struggles and takes quite long to fetch the parameters too)

I need to speed this process, because I want to be able to tune parameters more quickly.
Thank you.

Ensure SERIAL0_BAUD is set to 115 , it should be by default.
In MissionPlanner check you connection setting is also set to 115k baud
image

If you connect via a telemetry radio, some of them also handle 115k but most do 56k by default.
So it’s important to set SERIALx_BAUD , MissionPlanner (and the radio if used) all to the same rate.

2 Likes

Thanks for your reply.

Apologies for not explaining this well, but we connect via Wifi (or at least I think so).

When I set up my devices, I turn the system with the Ardupilot on, and a Herelink Ground Control controller on.
And when I open my mission planner on my computer, it will detect a Mavlink stream and connect to it.

However, it really seems to take a lot of time getting the parameters.
Once it is connected it is usually ok, but I face the same problem when I reboot the systems.

Is there anything anyone could suggest to speed up the connecting process via Mission Planner on the computer?

Thanks.

OK, the typical instructions for the Herelink uses the default baud rate for the FC serial port, such as SERIAL1_BAUD,57
You’ll probably notice there are no settings in the Herelink to change this, and I suspect the air unit might be autodetecting the baud rate, because you can set:
SERIAL1_BAUD,115
and get improved connection and download speeds. Reboot everything after that change.
Set MissionPlanner to 115 too.

Logs still take a long time to download, but at least it’s not infinity+1 minutes

This may affect range if you are pushing the 20km advertised range, but if you’re not going past 10km I would not think it would be an issue. You could monitor the connection quality to be sure.

1 Like

Thanks again.
I’ve made sure the baud rate is both at 115 now.

Like you said it might be the logs taking time. But yes, you are totally right. It’s great that it doesn’t take forever forever.

It is weird because it seems to be taking time even though I am a meter away from all devices.
It also seems to also struggle with getting the parameters.

Do you know a way I could investigate further to narrow down the problem?

Thank you.

I’m not sure what else you can do - you’d have to contact Cubepilot to find out more details.
You could try posting on their forum:
Cubepilot