paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] experimental feature : persistent settings


From: Martin Mueller
Subject: Re: [Paparazzi-devel] experimental feature : persistent settings
Date: Sun, 03 Apr 2011 21:25:02 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8

Hi,

the persistent settings feature is now also available for the LPC21.

Again: It is experimental and you should never store settings while in flight. It might take around 40ms for the STM or even 400ms for the LPC to write them. No other code/irq is serviced in that time. Do not disconnect power while saving settings/writing to flash.

The stored settings are erased when you flash a new software, so make sure you put them into the aircraft xml file before recompiling/uploading.

Martin


On 25.03.2011 12:08, antoine drouin wrote:
Hello World

We just added a new experimental feature to Paparazzi : you can now
save part or all of your "settings" to flash.

In order to do that you need to define the USE_PERMANENT_SETTINGS build flag

for example :

<firmware name="rotorcraft">
      <define name="USE_PERMANENT_SETTINGS"/>

then you can mark a setting as persistent in your xml setting config, eg

   <dl_setting var="nav_radius" MIN="-150" STEP="0.1" MAX="150"
module="navigation" unit="m"  persistent="true" />

now you can trigger the writing to flash using... a setting

  <dl_setting var="settings_store_now" min="0" step="1" max="1"
shortname ="store" handler="StoreSettings"
module="subsystems/settings"/>

Please refrain from doing this in flight as flash timings are probably
not compatible with the mainloop timing.

Eric is currently in the process of using this to implement a
"plugless" binding for spektrum.

Have fun and report

Poine

_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel




reply via email to

[Prev in Thread] Current Thread [Next in Thread]