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.
To get 360 degrees why cant a user put two condition yaw commands in a row each with 180?
https://github.com/diydrones/MissionPlanner/issues
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)