Strange values in new MP version

Hi, since my Mission Planner has updated to 1.3.24 the "Extended Tuning" page is showing strange and wrong values:

Rate IMAX is now 100 instead of 1000. Throttle Accel IMAX is 80 instead of 8. And my tuning range for Acro Yaw P goes now from 4500 to 9500 instead of 4.5 to 9.5!!!

3691195354?profile=originalIn the Full Parameter List these values seem to be the correct old ones except of MIN/MAX tune which also is 4500/9000 now!

What has happend there?

All the best, Markus

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

Join diydrones

Email me when people reply –

Replies

  • Hi Markus,

    Did you try to fly with those new settings? If so, what was the result? Did you also try to fly with your previous settings (before the upgrade)? If so, what was the result? Do you see a difference between the two?

    Regards,

    Richard

    • Did you try flying?  Was it the same?

      • Yes, I'm flying with these values since then and noticed no difference....

  • I have the same issue. My previous IMAX settings were exactly the same as Markus' settings. See setting below before upgrade.

    3701984724?profile=originalAfter the upgrade to 1.3.24 the IMAX settings were decreased with factor 10 for Rate_Roll,Rate_Pitch, but increased with factor 10 for Rate_Yaw and Rate_Loiter and Throttle_Accel.

    What can be the result of these changes when flying?

    Regards,

    Richard

  • Developer

    have  look here
    Imax is in percent * 10

    http://copter.ardupilot.com/wiki/configuration/arducopter-parameter...

    so the new numbers are correct for the percent value.

    and same for the Tune_low and tune_high

    http://copter.ardupilot.com/wiki/configuration/arducopter-parameter...

    • hello Michael, can you help understand how to use ch6 and tune_low and tune_high.

      how to map the 0-32765 to rate_roll_Kp for instance, if roll rate should have a value arrond 0.08 , than I woul expect to usea value of tune_low = 0.05 and tune_high = 0.10.

      now the value scale is 0-32765 what value should I use for Tune_low and tune_high to get the interval 0.05 to 0.10 ?

      thnaks

      Pedro

      • I got it.

        I played arround a litle bit and found that integer values on tune_low and tune_high, map directly to decimal values of the parameter, so to get a 0.150 to 0,200 I just insert Tune_low = 150 and tune_high to 200.

    • Thanks for your answer, Michael. The MP version before the update was 1.3.16, I think (Not exactly sure. Normally I update to any new version, but I was in holiday a few days ;))

      What I don't understand: My Imax values in the "Extended Tuning" page have both decreased AND increased: Rate Imax is now 100 (before: 1000; that fits to your percent * 10 explanation), but Throttle Accel Imax is now 80 (before: 8). Means: Some values seem to be 10 times smaller now, but some (in fact: one) is 10 times bigger.

      Relating to the tune values: There is nothing in the wiki that says Tune_low and tune_high are percent * 10.

      • For better understanding a screenshot of my "Extended Tuning" page (longer) before the update:

        3702692085?profile=original

  • Developer

    what mp version where you using prior to the upgrade?

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @SmallpixelCar: Wrote a program to find the light positions at @circuitlaunch. Here is the hypothesis of the light locations updating ba…
yesterday
DIY Robocars via Twitter
RT @SmallpixelCar: Broke my @HokuyoUsa Lidar today. Luckily the non-cone localization, based on @a1k0n LightSLAM idea, works. It will help…
Thursday
DIY Robocars via Twitter
@gclue_akira CC @NVIDIAEmbedded
Wednesday
DIY Robocars via Twitter
RT @luxonis: OAK-D PoE Autonomous Vehicle (Courtesy of zonyl in our Discord: https://discord.gg/EPsZHkg9Nx) https://t.co/PNDewvJdrb
Wednesday
DIY Robocars via Twitter
RT @f1tenth: It is getting dark and rainy on the F1TENTH racetrack in the @LGSVLSimulator. Testing out the new flood lights for the racetra…
Wednesday
DIY Robocars via Twitter
RT @JoeSpeeds: Live Now! Alex of @IndyAChallenge winning @TU_Muenchen team talking about their racing strategy and open source @OpenRobotic…
Nov 20
DIY Robocars via Twitter
RT @DAVGtech: Live NOW! Alexander Wischnewski of Indy Autonomous Challenge winning TUM team talking racing @diyrobocars @Heavy02011 @Ottawa…
Nov 20
DIY Robocars via Twitter
Incredible training performance with Donkeycar https://www.youtube.com/watch?v=9yy7ASttw04
Nov 9
DIY Robocars via Twitter
RT @JoeSpeeds: Sat Nov 6 Virtual DonkeyCar (and other cars, too) Race. So bring any car? @diyrobocars @IndyAChallenge https://t.co/nZQTff5…
Oct 31
DIY Robocars via Twitter
RT @JoeSpeeds: @chr1sa awesomely scary to see in person as our $1M robot almost clipped the walls as it spun at 140mph. But it was also awe…
Oct 29
DIY Robocars via Twitter
RT @chr1sa: Hey, @a1k0n's amazing "localize by the ceiling lights" @diyrobocars made @hackaday! It's consistently been the fastest in our…
Oct 25
DIY Robocars via Twitter
RT @IMS: It’s only fitting that @BostonDynamics Spot is waving the green flag for today’s @IndyAChallenge! Watch LIVE 👉 https://t.co/NtKnO…
Oct 23
DIY Robocars via Twitter
RT @IndyAChallenge: Congratulations to @TU_Muenchen the winners of the historic @IndyAChallenge and $1M. The first autonomous racecar comp…
Oct 23
DIY Robocars via Twitter
RT @JoeSpeeds: 🏎@TU_Muenchen #ROS 2 @EclipseCyclone #DDS #Zenoh 137mph. Saturday 10am EDT @IndyAChallenge @Twitch http://indyautonomouschallenge.com/stream
Oct 23
DIY Robocars via Twitter
RT @DAVGtech: Another incident: https://t.co/G1pTxQug6B
Oct 23
DIY Robocars via Twitter
RT @DAVGtech: What a great way to connect why @diyrobocars community is so valuable and important! Have to start somewhere @IndyAChallenge…
Oct 23
More…