Baro and Compass in terminal show no values?

Hey guys,

 

back at it again and i see .42! awesome.

 

does anyone know if there is a bug in mission planner when you jump into terminal and test command "altitude" or "compass" do they work? 

when i do it, i see no values. do i have a hardware issue or is this a planner bug?

 

cheers,

 

paul.

 

keep up the great work guys!

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

Join diydrones

Email me when people reply –

Replies

  • haha. thanks mike! i tried touching the baro and blowing into it. nothing! my compass is in the recommended config with pins soldered to board. i am totally dumb founded on why these sensors have stopped working. Someone PLEASE help!

     

  • hi mike, thanks for your diagnostics ! very detailed.  however no luck on my end?! strange, i pretty sure it was working in the past! now its just giving me this.

     

    compass:

    Heading: 347, XYZ: 0,0,0

     

    and for altitude:

    Baro: 0cm

     

    all this while in CLI mode, GPS light on and Green "A" light on.

     

    any clues?!

     

  • Moderator

    2.0.42 on my hardware does produce data for test/altitude and test/compass.

     

    Details of testing: I took an APM which was running ArduPlane, loaded 2.0.42 from Planner 1.0.67. No airframe, I do have a magnetometer hooked up, but no sonar, no ESCs, no rail power, no RX, no GPS (this last item might be important, it is plausible, not having read all the code, that you might have a GPS that has not fix, and some form of mixing is resulting on no results for compass or altitude. If I were to guess, however, from having read other CLI/Test code, I would bet against this "plausible" theory.)

     

    I switched it to CLI and Terminal, but it just told me to setup first.

    I used setup to enable the magnetometer and "+" mode, nothing else.

    I switched to Terminal, CLI/Log Switch and here is the rest. It works for me:

     

    NOTE: You must disconnect and move the slider switch when done to use other tabs

    Opened com port

     

     

    Init ACM

     

    RAM: 2574

    FW Version 107

    ----------------------------------------

     

     

     

    Entering interactive setup mode...

     

    Type 'help' to list commands, 'exit' to leave a submenu.

    Visit the 'setup' menu for first-time configuration.

     

    ArduCopter 2.0.42 Beta] test

    test] altitude

    Hit Enter to exit.

     

    Baro: 0cm

    Baro: -60cm

    Baro: -60cm

    Baro: -69cm

    Baro: -78cm

    Baro: -78cm

    Baro: -87cm

    Baro: -104cm

    Baro: -113cm

    Baro: -130cm

    Baro: -130cm

    Baro: -139cm

    Baro: -156cm

    Baro: -156cm

    Baro: -165cm

    Baro: -165cm

    Baro: -165cm

    Baro: -165cm

    Baro: -174cm

    Baro: -174cm

    Baro: -174cm

    Baro: -156cm

    Baro: -156cm

    test] 

    test] compass

    Hit Enter to exit.

     

    Heading: 14, XYZ: 203, -92, 182

    Heading: 14, XYZ: 203, -92, 182

    Heading: 14, XYZ: 202, -93, 182

    Heading: 14, XYZ: 202, -93, 182

    Heading: 14, XYZ: 203, -93, 183

    Heading: 14, XYZ: 203, -93, 182

    Heading: 14, XYZ: 203, -92, 182

    Heading: 14, XYZ: 203, -93, 183

    Heading: 14, XYZ: 203, -92, 183

    Heading: 14, XYZ: 203, -92, 182

    Heading: 14, XYZ: 203, -93, 183

    Heading: 14, XYZ: 202, -93, 183

    Heading: 14, XYZ: 202, -93, 182

    Heading: 14, XYZ: 202, -92, 183

    Heading: 14, XYZ: 203, -93, 183

    test]

     

  • Moderator

    Terminal-> test, on Mission Planner is basically a serial terminal link, so if you get far enough to type "test" and "compass" then it would have to be an ArduCopter issue, hardware or software, if it is not giving you data you expect. I'll fire mine up at see what data I get w/ 2.0.42 right now...

This reply was deleted.

Activity

DIY Robocars via Twitter
Sunday
DIY Robocars via Twitter
Saturday
DIY Robocars via Twitter
Saturday
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
Saturday
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…