-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QGC 4.4.2 + AP4.5.7 Waypoint and Rally Point Read Write Issues #12076
Comments
This looks like a firmware side protocol screw up. That said the full PlanManager lof isn't quite right. I just fixed a bug in there to get better logging. It was just merged. A new daily build with that fix should be available in about an hour. Can you repro this on daily and get a new PlanManager log from that? |
Sure, I'll wait for tomorrow and test with whatever Binary is linked here for linux. Thanks for looking into the issue. |
I tested daily build and I can relate the issue to the Mavlink via ELRS feature. When I connect the FC via Serial / USB everything works. I'm currently struggling to actually log something because the console log does not show anything that I presumably selected for logging. |
Sorry, can't get any logging working with daily build, even I'm running the daily of this commit But I'll try one last thing here, not going through port 14550 but through a serial attached to the elrs module's usb port. |
Same effect through the elrs modules usb port, but it was much much faster until it threw the error message. Again absolutely no logging even to command line except for the tile warnings. |
You can see what the problem is here in the logs:
The firmware is returning the wrong mission item. It looks like the protocol is completely out of whack. Almost seems like the Vehicle->GCS traffic direction is being sent more than once. Same thing indicated by AMP Planner not working. This isn't a QGC thing as far as I can tell. It's either a firmware problem or a downlink (vehicle->GCS) setup problem. |
Agreed, I believe it has something to do with being a stubborn sender. Closing the issue therefore. I'll try to achieve some logging and attach it here for reference. |
I can further confirm, that the issue is only present with 900Mhz Mavlink via ELRS feature. It must be some issue on the 900Mhz RF Link. |
I have another indicator that it's related to ELRS. The same test bench setup with mLRS on Seeed WIO-E5 modules works without any issues, also 900Mhz RF Link. I will open an Issue there. |
@DonLakeFlyer Am I correct in the assumption that |
Sorry lost track of this. Yeah that seems short. Try changing it to 1500 to see what happens. If you don't want to setup a whole build environment just submit a pull request with the change marked as Draft and then use the built artifact to test with. |
Setting I'll reopen this issue and eventually push PR afterwards. BTW: Good writeup on the building instructions, I was struggling with distribution based qt packages for a week until I finally gave in to using the online installer and create an account. |
If I remember correctly PlanManager is the base class for all of those isn't it? |
Aye, everything was solved by tweaking the timeouts. I pushed PR. Thanks for bearing with me ^^; |
Expected Behavior
Waypoint (read from | write to) FC is possible.
Current Behavior
During initial connection GQC reads configuration from FC.
After parameters are finished, it tries to continue with Mission Items, i.e. Waypoints, Rally Points.
It fails with error popup
Mission read failed, maximum retries exceeded.
once for waypoints and another one for rally points.
Steps to Reproduce:
Please provide an unambiguous set of steps to reproduce the current behavior
System Information
When posting bug reports, include the following information
Detailed Description
FC is connected by UDP Port 14550.
That port is fed from a RM BANDIT MICRO module attached to a RM TX12MK2.
RC connection runs mavlink via ELRS feature.
https://www.expresslrs.org/software/mavlink/
Running APM-Planner_2-2.0.30-rc3-x86_64 instead of GQC shows that there is some index issue in the transmitted waypoints.
I think the format has changed somehow.
Log Files and Screenshots
The text was updated successfully, but these errors were encountered: