Mission Planner "Get params 12"

Hello. I am running MP 1.3.43 and Pixhawk hardware with 3.7.1 firmware.Tonight I had an experience that has not happened before. I was previously running MP 1.3.42 and same Pixhawk 3.7.1 firmware, and when connecting via telemetry radio I get the message "Getting Params 1" in a pop up window. As soon as that operation successfully completed the screen refreshed and all of a sudden a new pop up window appeared with the message "Getting params 12" and it stays there forever unless you press the cancel button, and then the screen refreshes, you are connected and everything works fine from that point forward. I have also tried connecting over USB and got the same results. I noticed there was a MP 1.3.43 update available so I updated and tried connecting again via USB and also telemetry radio, and got the same results. This has never happened to me before, so I'm wondering if I have a setting that's been changed incorrectly or if this is a bug. I've never seen the message "Getting params 12" before, so either it never does that or it goes by so quickly I have missed it. The only other thing I have updated besides MP is my minimosd_extra screen settings. Any assistance is appreciated. If I have placed this post in the wrong forum plz let me know. ThxRegardsMike

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

Join diydrones

Email me when people reply –

Replies

  • If anyone is still having this issue, it appears to be fixed by updating minimosd-extra firmware to version 927 or above. The changelog for v927 says:

    • "fixed bug with "Reading param 12" in MP

    Hopefully this is helpful as I was getting quite confused by the issue.

    -Greg

  • I am late to the party but I am also having the same issue.Everything was working fine until my old osd stopped working and I replaced it with a micro minimosd.I have tried switching the Tx and Rx wires since that seems to always cause me problems but the only thing that does is it either gets stuck on param 12 or if I switch the wires it doesn't connect at all and times out.

  • Same behaviour.

    I've also a minimOSD connected.

    Any solution to solve the issue?

    Pascal

  • Hello, same behaviour.

    Do you have the solution ?

  • I have the same problem, " "Getting Params 1" in a pop up window. As soon as that operation successfully completed the screen refreshed and all of a sudden a new pop up window appeared with the message "Getting params 12" and it stays there forever unless you press the cancel button,"

    When I remove the Minimosd from Pixhawk telemetry #2 port there is no problem loading when connected to USB.

    MORE information.

    1) With the OSD connected I do not have a problem loading Parameters with telemetry (no USB connections)

    2) If I connect to QGroundcontrol with USB the same thing happens, "Getting params 12" goes on forever. I hit cancel and go into QGroundcontrol software.  The interesting thing is, there is a section that shows Vehicle #1 and Vehicle # 12. Vehicle #1 shows all the parameters (params 1). Vehicle # 12 show no parameters.

  • Yes, I am seeing the same thing.  I am setting up a Pixhawk and it was fine until I added the Minimosd.  Now, I get the "Getting Params 12" at the end of the load.  If I disconnect the OSD it works again so it was related somehow.

  • You might try posting to
    http://discuss.ardupilot.org/c/ground-control-software
This reply was deleted.

Activity

DIY Robocars via Twitter
RT @chr1sa: Just a week to go before our next @DIYRobocars race at @circuitlaunch, complete with famous Brazilian BBQ. It's free, fun for k…
yesterday
DIY Robocars via Twitter
How to use the new @donkey_car graphical UI to edit driving data for better training https://www.youtube.com/watch?v=J5-zHNeNebQ
Nov 28
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…
Nov 26
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…
Nov 25
DIY Robocars via Twitter
@gclue_akira CC @NVIDIAEmbedded
Nov 23
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
Nov 23
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…
Nov 23
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
More…