-
```
Connecting MinimOSD with Firmware v2.2 to an APM running Arducopter on a
hexacopter or octocopter will not update the flight mode osd. That's because
line 877 of OSD_Panel.ino (rev 563) is:
> …
-
```
Connecting MinimOSD with Firmware v2.2 to an APM running Arducopter on a
hexacopter or octocopter will not update the flight mode osd. That's because
line 877 of OSD_Panel.ino (rev 563) is:
> …
-
```
Connecting MinimOSD with Firmware v2.2 to an APM running Arducopter on a
hexacopter or octocopter will not update the flight mode osd. That's because
line 877 of OSD_Panel.ino (rev 563) is:
> …
-
```
Connecting MinimOSD with Firmware v2.2 to an APM running Arducopter on a
hexacopter or octocopter will not update the flight mode osd. That's because
line 877 of OSD_Panel.ino (rev 563) is:
> …
-
```
Connecting MinimOSD with Firmware v2.2 to an APM running Arducopter on a
hexacopter or octocopter will not update the flight mode osd. That's because
line 877 of OSD_Panel.ino (rev 563) is:
> …
-
-
```
Feature that you'd like us to add or change you'd like us to make:
Don't allow motors to start after APM bootup until explicitly enabled by some
means.
If the THR_MIN setting is not 0 then motor…
-
```
Feature that you'd like us to add or change you'd like us to make:
Don't allow motors to start after APM bootup until explicitly enabled by some
means.
If the THR_MIN setting is not 0 then motor…
-
```
Feature that you'd like us to add or change you'd like us to make:
Don't allow motors to start after APM bootup until explicitly enabled by some
means.
If the THR_MIN setting is not 0 then motor…
-
```
Feature that you'd like us to add or change you'd like us to make:
Don't allow motors to start after APM bootup until explicitly enabled by some
means.
If the THR_MIN setting is not 0 then motor…