Optimise MAV FTP upload to improve performance about mavproxy HOT 3 OPEN

I'm able to upload using a similar setup (Copter on master, Pixhawk1, MAVProxy from install 1.8.66). It is quite slow - around 15-25kByte/sec.

A 33Mb terrain file took ~33min - so 1Mb/min transfer rate.

If you use ftp status during the transfer, is it showing progress?

from mavproxy.

I've changed the title to reflect that this is no longer considered a bug but rather an enhancement request.

On the Nov 14th dev call we discussed with Tridge and discovered that MAVFTP's implementation (both within the GCSs and the flight code) has been optimised for downloading (e.g. from the autopilot->GCS) but not for uploading (e.g. GCS->autopilot).

There were two suggestions for improving peformance:

1. send multiple MAVFTP messages from the GCS to the autopilot without waiting for a response.
2. create a new MAVLink message to send longer messages just like we do for downloading. Currently it seems the MAVFTP messages are only 80bytes long

I will still try @stephendade's suggestion to confirm that the FTP is working on windows even if it is very slow.

from mavproxy.

@stephendade (and anyone else who is interested),

I ran, "ftp status" during the transfer and saw what's below so it is making (slow) progress.

from mavproxy.