Recently I've used MP to add a DO_JUMP command toward the end of the waypoint list. But it had no effect at all, when reaching the last waypoint, the plane flew home. At close look, I see that MP sets DO_JUMP command parameters as P1 = WP#, P2 = repeat, P3 = P4 = 0. However, in Arduplane 2.65 code_description.txt, DO_JUMP parameters are defined as P1 = WP#, P3 = repeat. And in commands_logic.pde the first command of do_jump() is "if (next_nonnav_command.lat == 0)" which checks whether DO_JUMP P3 parameter is zero and then ignores the DO_JUMP execution.
You need to be a member of diydrones to add comments!
Replies
Can you please upload ( or cut-n-paste) the mission file you are using, so we can see what your issue looks like first-hand. Also, with regard to the "zero", this is supposed to be used to cause the system to "not jump" when repeat count is zero. Is it possible that your repeat count has decremented to zero since uploading the mission? EG: upload a mission with a non-zero repeat count, fly it, and then download it from the plane, and you will see the repeat count decrements *in the mission data* each time it is flown.
this is a known bug. add a dummy waypoint directly after a DO_JUMP , and the problem will no longer manifest. code contribution/s to fix it are welcome.