We're updating the issue view to help you get more done. 

Reduce RAM usage on f1 and f3 targets.

Description

There are quite some bytes allocated by telemetry module for setting the logging period for registered UAVOs.
telemetry.c comment makes a note about logging period stuff:

1 * 8-9 loggingUpdateMode Update mode used by the logging module (UAVObjUpdateMode)

If coptercontrol does not use logging module (as it seems to be the case), then there is no point in doing the logging period magic. Voiding setLoggingPeriod() function saves whopping 1056 bytes of RAM.

Are there any downsides to doing this?

Status

Assignee

Vladimir Zidar

Reporter

Vladimir Zidar

Labels

None

Components

Fix versions

Priority

Medium