Accelerometer Calib PixHawk 3.3.3 Question

Hi All,  (Quad PixHawk 3.3.3  >> MP 1.3.37)

 I realize that this may be a trivial question to those

 who have their own Calibration techniques well sorted,

  however, my question is -

  During the Accel Calibration procedure -

         One is prompted to 'Level Auto-Pilot' -

            1) Do one position the Craft such that the PixHawk Unit itself is at Level?,

                 which was  pre-mounted on the Craft during the assembly

           2) or Does this mean that you place the Craft on a Level surface.

            3) Both options  correct?

      I would say 2)  Assuming of course one have mounted the Pixhawk as

          close to the Centre position of the Craft and as level as possible, at assembly.

   I am looking forward to your valuable feedback, thank you.

Regards,

Gerhard

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

Join diydrones

Email me when people reply –

Replies

  •  To me, technically both are correct. Essentially, you want your craft to be level during normal flight, or for the pixhawk to know what 'level' is for your craft. Installing mine, I made sure that the pixhawk is true and level in relation to the craft itself and then, when calibrating, I used small spirit levels that I can clip onto the frame in two orientations to ensure the craft is perfectly level.
    So, in doing that, and with the pixhawk  installed level relative to the craft, and with the craft level relative to the earth, then 'level' will be the same orientation for them both.

    If your pixhawk is crooked on the craft and you have calibrated the pixhawk to level off the craft or it's installed crooked, then the pixhawk will level itself and the craft will be 'off kilter', which I should think will mean the motors are constantly going to have to fight to fly true because they are also now not level.

    • Hi Doug,

      Thanks for your reply.

      I take your point to ensure that -

      Pixhawk unit installed level to to the craft, the craft level to to 'ground'.

      I assume here that the IMU's on the PixHawk are used to 'sense' the orientation, eg level.

      If that is the case, I think that, once the the craft is positioned level, the pixhawk unit will accept the reading

      from the imu's as 'level' whether it is 'true' level or not.  This reading will then be used as 'level' and deviations from that during flight is used by the FC to determine its 3D orientation in the air. If I am wrong in this reasoning, then please correct me.

      I admit this is the first time I am using Pixhawk, so therefor my very basics questions to understand the

      practical calibration procedures to ensure I get the best results.

      I have done the Accel Calibration now with the Craft being place on a 'prepared' level area.  I have noticed with a bubble compass on top of the PixHawk unit, that the unit is a bit off-level, even though the Craft is now positione  on a level surface.  I continued doing the accel calibr and some value '19...' was reported, according to MP voice.  Which params hold these values, where can I review it?  Is this reported value of '19' correct, well, acceptable?

      I proceeded with the compass calibr using the rotating 'chair' method.

      All the 'white' dots were hit and the samples were > 1200

      The Compass #1 (external) offset > -140, 34, -74  == calc ~162, which is lower than 600 (should be)

      according to wiki >> http://ardupilot.org/copter/docs/common-compass-calibration-in-miss...

      I am not sure whether this Compass offset is 'good' or 'bad' ??

       Compass #2, internal, -300, -55, -192   >>Not used.

      Which other parameters can I look at to evaluate whether the Craft's Calibration is 'acceptable'

      or in fact 'good'.   Which are the go / no-go calibr params one can review?

      I am going to do a test flight in the new day to evaluate my findings.

      Any other helpfull info or comments/video examples are very welcome, thank you very much.

      Regards,

      Gerhard

      Compass Calibration — Copter documentation
This reply was deleted.

Activity

Gremsy liked Gremsy's profile
Mar 12
DIY Robocars via Twitter
RT @chr1sa: Donkeycar 4.4 released with tons of new features, including path learning (useful with GPS outdoors), better Web and Lidar supp…
Nov 27, 2022
DIY Robocars via Twitter
RT @NXP: We are already biting our nails in anticipation of the #NXPCupEMEA challenge! 😉 Did you know there are great cash prizes to be won…
Nov 24, 2022
DIY Robocars via Twitter
RT @gclue_akira: レースまであと3日。今回のコースは激ムズかも。あと一歩 #jetracer https://t.co/GKcEjImQ3t
Nov 24, 2022
DIY Robocars via Twitter
UC Berkeley's DIY robocar program https://roar.berkeley.edu/
Nov 24, 2022
DIY Robocars via Twitter
RT @chr1sa: The next @DIYRobocars autonomous car race at @circuitlaunch will be on Sat, Dec 10. Thrills, spills and a Brazilian BBQ. Fun…
Nov 24, 2022
DIY Robocars via Twitter
RT @arthiak_tc: Donkey car platform ... Still training uses behavioral cloning #TCXpo #diyrobocar @OttawaAVGroup https://t.co/PHBYwlFlnE
Nov 20, 2022
DIY Robocars via Twitter
RT @emurmur77: Points for style. @donkeycar racing in @diyrobocars at @UCSDJacobs thanks @chr1sa for taking the video. https://t.co/Y2hMyj1…
Nov 20, 2022
DIY Robocars via Twitter
RT @SmallpixelCar: Going to @diyrobocars race at @UCSDJacobs https://t.co/Rrf9vDJ8TJ
Nov 8, 2022
DIY Robocars via Twitter
RT @SmallpixelCar: Race @diyrobocars at @UCSDJacobs thanks @chr1sa for taking the video. https://t.co/kK686Hb9Ej
Nov 8, 2022
DIY Robocars via Twitter
RT @PiWarsRobotics: Presenting: the Hacky Racers Robotic Racing Series in collaboration with #PiWars. Find out more and register your inter…
Oct 23, 2022
DIY Robocars via Twitter
RT @Hacky_Racers: There will be three classes at this event: A4, A2, and Hacky Racer! A4 and A2 are based around UK paper sizing and existi…
Oct 23, 2022
DIY Robocars via Twitter
Oct 23, 2022
DIY Robocars via Twitter
Oct 19, 2022
DIY Robocars via Twitter
Oct 18, 2022
DIY Robocars via Twitter
RT @NeaveEng: Calling all UK based folks interested in @diyrobocars, @f1tenth, @donkey_car, and similar robot racing competitions! @hacky_r…
Oct 13, 2022
More…