I was using the flightplanner to create a simple job, but encountered 2 problems so far. Perhaps some explanation could do.
First, if i enter more than 255 degrees in a CONDITION_YAW it will produce an error on writing.
I understand the error but a full circle has 360 degrees......
Second if i use a valid condition statement it writes perfect, but after reading th WP's from the ardu some parameters are reset to 0 ????
Before WRITE
After WRITE WP and READ WP
Some help is appriciated.
Pieter
Replies
Similar thing happens in mp 1.3.9.2 for plane if you select absolute or terrain for altitude and write the mission.... when you read it back it always shows relative in mp. The plane does terrain following nicely but I like to see the mission readback verbatim to make sure everything is as planned.
I have filed an issue and it seems that is has something to do with me living in a country that uses "," instead of "." for decimals. I.e 30,5 instead of 30.5. Mission planner then interprets the number in some way that manage to change 30,5 cm/s to 3048 cm/s wich is a bit fast as landing speed.
To get 360 degrees why cant a user put two condition yaw commands in a row each with 180?
I think I have found an bug in MP 1.3.9.
If you select something like 40 cm/s in the gauge in "standard params" and write this to pixhawk. Then refresh params the setting changes to 100 times more. It's repetable.
If I instead use "full parameter list" and write the settings it works rather well.
Does anyone seen this apart from me? Can You repeat and check if the problem is "global"?
I have tried to find the error as I had a crash from 60 meters because the engine stopped. This could posibly be the problem?
I understand that this is wrong place to report but I cant find a better place. Please advice me if im wrong.
best regards
Niklas
https://github.com/diydrones/MissionPlanner/issues
Thank you. I will do that.
The data presentation of APM/AC2 may need re-consideration. Some of them are too small. For example, the waypoint-radius/loiter-radius is only a byte, less than 255, which may be not proper for large and fast plane (e.g. those in the simulators)