Closed GoogleCodeExporter closed 8 years ago
EDIT: I don't think there is any issue with Mode Zero (0). I think the issue I
was having is that I put RTL in that slot, and for some reason, APM Planner
only shows Loiter instead of RTL (see issue #363).
However, I still think it would be nice if CLI could display the modes as 1-6
instead of 0-5, this would save infinite confusion for those of us looking back
and forth between the code in APM_Config and CLI.
Original comment by bjior...@gmail.com
on 12 Jun 2011 at 8:27
what firmware version are you running? there was a shuffle of modes between
some of the 2.x versions, the planner is correct with the latest build.
Original comment by Meee...@gmail.com
on 15 Jun 2011 at 12:23
Oops, that was a typo above - it should have said I am using 2.1.2 from May 29.
It still shows Position 0 in CLI in both "Setup -> Modes" and "Test ->
Modeswitch".
I don't see how Planner would have much to do with it, CLI is just
serial-printing whatever APM tells it.
I've changed this in my own copy, it only requires modifying two lines. This
doesn't change any of the functionality, just what CLI prints.
In the Setup tab, change the print_switch function to (change is adding 1 to
p):
void
print_switch(byte p, byte m)
{
Serial.printf_P(PSTR("Pos %d: "),p + 1);
Serial.println(flight_mode_strings[m]);
}
In the Test tab, change the following line in the test_modeswitch function (I
am not showing the whole function - again here, the change is adding 1 to
switchPosition):
...
Serial.printf_P(PSTR("Position %d\n"), switchPosition + 1);
...
Original comment by bjior...@gmail.com
on 15 Jun 2011 at 12:35
To be clear - this fixes the annoyance that modes are displayed as 0-5 in CLI.
It has nothing to do with the other issue I raised about Mode Zero not working.
That one turned out to be bogus and is not a problem, at least for me. It is
more rightly handled in issue #363
Original comment by bjior...@gmail.com
on 15 Jun 2011 at 12:37
Original comment by Meee...@gmail.com
on 26 Jun 2011 at 7:12
Original issue reported on code.google.com by
bjior...@gmail.com
on 12 Jun 2011 at 5:04Attachments: