Differences

This shows you the differences between two versions of the page.

--- pidgesture [2017/06/13 10:36]
markus_gritsch
+++ pidgesture [2017/07/03 01:54] (current)
silverxxx
@@ Line 1: / Line 1: @@
 ===== Gesture PID tuning =====
-The gesture based PID tuning allows the pilot to change the acro PIDs at the field, without the use of a computer. The new PIDs can be saved, and will be loaded next time the quad powers up. If not saved by performing the appropriate gesture, they will be discarded when the quad is powered off.
+The [[:Gestures|gesture]] based PID tuning allows the pilot to change the acro PIDs at the field, without the use of a computer. The new PIDs can be saved, and will be loaded next time the quad powers up. If not saved by performing the appropriate gesture, they will be discarded when the quad is powered off.
 Silverware branches of [[https://github.com/silver13/BoldClash-BWHOOP-B-03|BWHOOP]], [[https://github.com/silver13/H8mini_blue_board|H8BLUE]] (both STM MCU), [[https://github.com/silver13/H101-dual|H101/H8S]] and [[https://github.com/silver13/h8mini-dual|H8Green]] (GigaDevice MCU) now have the possibility to tune the PIDs via Tx gestures (thanks to RCGroups user eitama for adding it!).
@@ Line 60: / Line 60: @@
 For PID tuning, it's highly recommended to use [[:silvervise|SilverVISE]] Android app, where you can see the cursor and also see the PID numbers / changes. For all infos how to use the app please click at the link above.
-For all that don't own an Android device and are interested in the actual numbers, debug mode can be used (with Keil), where the PIDs can be seen (as decimal numbers). Just add pidkp, pidki, and pidkd to the Watch1 window:
+For all that don't own an Android device and are interested in the actual numbers, [[:using_debug_mode|debug mode]] can be used (with Keil), where the PIDs can be seen (as decimal numbers). Just add pidkp, pidki, and pidkd to the Watch1 window:
 {{https://static.rcgroups.net/forums/attachments/6/4/6/0/1/1/a10069931-74-pid_debug.png?nolink&1003x703}}
@@ Line 69: / Line 69: @@
 <font inherit/inherit;;#FF0000;;inherit>Entering debug will automatically flash code unless a setting is turned off.</font>
+To use debug mode without reflashing the quad, you can do the following:
+In the last tab of the settings ( utilities ) uncheck "update target before debugging"
+Also go to stlink - settings , where the algorithms are, and set "do not erase" , also uncheck program and verify. This way it can't program it even if it tries to. This is just for added safety, the first option should do it but some things one really don't want erased even if it's unlikely. Be aware that this procedure only works if you use the exactly same Silverware version you flashed at the quad, otherwise you may get crappy values (because the values shown are stored in a particular memory section, and only the compiler knows where they are. Therefor, it's standard to reflash the code before using debug mode.

Silverware Wiki

User Tools

Site Tools

Differences

Page Tools