Waypoints are cyclically re-requested by copter on SITL

[khancyr]

See http://discuss.ardupilot.org/t/waypoints-are-cyclically-re-requested-by-copter-on-sitl/16200
It append when Mavproxy is used as a proxy.

To reproduce the bug, use launch SITL. Connect APMplanner or another GCS, create a mission, write the mission and see mavproxy flood with "re-requesting WPs [0, 1, 2, 3, 4]"

Probably related to b7765a0 ?

[AndKe]

this is not only in SITL, please update title, maybe i will get some attention.

[AndKe]

this issue can be worked around by loading misseditor module, and clicking "read WP"
or just do "wp list"

it's due to the comparsion in mavproxy_wp.py line 160:
if self.master is not None and self.master.time_since('MISSION_ITEM') >= 2 and self.wploader.count() < getattr(self.wploader,'expected_count',0):

self.wploader.count() returns "0" (while there should be 5)

[amilcarlucas]

This has been fixed in the latest version

[amilcarlucas]

Works in the latest release. Closing it now. Please reopen if the problem persists in the latest release.

[3efischer]

I'm still having this problem with the current release. I start up mavproxy and SITL with sim_vehicle.py -L Ballarat --map --console -D -G and after I connect to it with Dronekit (connect(127.0.0.1:14551)), the error "re-requesting WPs [0, 1, 2, 3, 4]" appears.

[amilcarlucas]

Make sure you use the latest 2.9.2 dronekit, together with the latest pymavlink. That bug has been fixed already.

[3efischer]

I'm using dronekit 2.9.2 and pymavlink 2.3.4 and I still get that error though.

[Heyuchen-330]

I have the same problem after starting mavros byroslaunch mavros apm.launch fcu_url:=udp://127.0.0.1:14550@

[Heyuchen-330]

I have the same problem after starting mavros byroslaunch mavros apm.launch fcu_url:=udp://127.0.0.1:14550@

solved by clearing the mission

[timtuxworth]

I'm getting this on master/plane as at 2022-May-31

[rmackay9]

The cause is probably different than the original report but I've re-opened this because I'm seeing it as well.

[timtuxworth]

wp list made it go away (for now)

[timtuxworth]

I just got it again. I had a clean clone (4.1), started SITL, all good, did a takeoff (crashed), switched to manual mode and started getting these messages. There was no mission or fence on the plane, it should have been a brand new, empty eeprom.bin,

[timtuxworth]

Oh. Ok so I did this:

1. Deleted the eeprom.bin
2. Reloaded params from a param file (I had downloaded this from Tridge's definition for the AeroScout)
3. Entered mavlink command: takeoff 50
4. Entered mavlink command: arm throttle
5. Started seeing re-requesting WPs [0] over and over (and there was one that said re-requesting WPs [] with no 0]

So is it possible there is something in the param file I loaded that causes the problem? This is it here:
https://www.dropbox.com/s/6p8t8qrr1hh3b1d/aeroscout.param?dl=0

I got it from here:
https://github.com/ArduPilot/SITL_Models/tree/master/RealFlight/Tridge/Planes/Aeroscout

[dvelozjr]

I also cleared the mission in MAVProxy, after "WP: mission received" message in MAVROS, by issuing this command: rosservice call /mavros/mission/clear "{}"