WPNAV parameters changed to 0 after autotune??

I just did an autotune and was scanning the full list of parameters after and noticed that some of the WPNAV parameters got changed to 0. I'm not sure if they were like this before but it doesn't seem they should be 0.

Also it's impossible to scroll down completely to see the last item but it's WPNAV_SPEED_UP I believe. I haven't flown waypoints in a few months but remember tweaking these settings such as slow up and slow down.

http://copter.ardupilot.com/wiki/arducopter-parameters/#loiter_horizontal_maximum_speed_wpnav_loit_speed

3691264693?profile=original

3691264774?profile=original

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • How can I see this data in the TLogs? I opened one in APM Planner but don't see where these parameters are. Tried opening in textedit but got this:

    n(3’.ò˛◊2æWPNAV_SPEED lœ(3’.üÿ˛ÿ2øWPNAV_RADIUS Ö0(3’0I†˛Ÿ2¿WPNAV_SPEED_UP pô(3’0a˛⁄2¡WPNAV_SPEED_DN P¥(3’0d¯˛€2¬WPNAV_LOIT_SPEED ∏#(3’2®˛‹»B2√WPNAV_ACCEL ®](3’2.˛›»B2ƒWPNAV_ACCEL_Z ès(3’25–˛fizD2≈WPNAV_LOIT_JERK

    • open in APM planners's Graph view, then |look in the grid - it's not always in tlog, depends of when you booted, whatever APM planner already had the parameters loaded.   so dataflashlog is better that way

      • I tried that but only had data flash logs from the previous month and they all showed the same data so this wasn't changed by autotune.

        Where can I find what the default values should be for these WPNAV parameters?

        Now I think what might have happened. I've noticed before that sometimes all the parameters don't get loaded when connected via telemetry. If you then change one and press write then those zeros get written. Do you know if this is a known problem? Makes me wonder what others got changed to 0.

        • yes, I think you are right -  I don't think there are any logic to catch that.

          this could work in the other "simple" tuning views - but could not happen in full parameter view.

          one thing you could do to prevent this from happening, is to see if 100% or parameters are loaded before using those features, or click "read" if that's an option.

          • Yes I try to do that, or only make changes in full parameter view so I can make sure all values loaded before I make a change and write back. It would be good if there was a solution to this because making changes over a slow connection could cause this to happen and make a lot of parameters 0 without the user being aware. Maybe there could be a way to monitor this in APM Planner so that until it loads all the parameters fully, it will not allow a write to happen.

            • Already reported :) https://github.com/diydrones/apm_planner/issues/869

              • Andre, do you know what the default values are for these or where I can find?

                WPNAV_SPEED

                WPNAV_RADIUS

                WPNAV_SPEED_UP

                WPNAV_SPEED_DN

                WPNAV_LOIT_SPEED

                I know I could guess at the values but would like to get them nearby before I start trying them. Would be good if defaulted values were indicated like the range is indicated so we can see if anything is really off.

                • well, the proper/safest/best way to determine any strange changes you may have, and compare to what's default for your firmware would be:

                  -backup parameteres to .param file

                  -reset dataflash format (factory reset)

                  -compare with backup, import what you need

                  but to answer your question:

                  WPNAV_ACCEL,250
                  WPNAV_ACCEL_Z,100
                  WPNAV_LOIT_JERK,1000
                  WPNAV_LOIT_SPEED,1000
                  WPNAV_RADIUS,200
                  WPNAV_SPEED,650
                  WPNAV_SPEED_DN,150
                  WPNAV_SPEED_UP,250

                  • Thanks! I will make the backup and check it that way.

              • Thanks Andre!

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
Monday
DIY Robocars via Twitter
Monday
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
DIY Drones via Twitter
First impressions of the Intel OpenBot https://ift.tt/36qkVV4
Nov 10
DIY Robocars via Twitter
Nov 9
DIY Robocars via Twitter
Excellent use of cardboard instead of 3D printing! https://twitter.com/Ingmar_Stapel/status/1324960595318333441
Nov 7
DIY Robocars via Twitter
RT @chr1sa: We've got a record 50 teams competing in this month's @DIYRobocars @donkey_car virtual AI car race. Starting today at 10:00am…
Nov 7
DIY Robocars via Twitter
Nov 6
DIY Robocars via Twitter
RT @a1k0n: Car's view, using a fisheye camera. The ceiling light tracking algorithm gave me some ideas to improve ConeSLAM, and having grou…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: To get ground truth I measured the rug, found the pixel coordinates of its corners, calibrated my phone camera with my standard…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: @DIYRobocars is back in December, but outside. Time to reinvestigate ConeSLAM! I rigged up a quick and dirty ground-truth captur…
Nov 5
More…