ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Requesting the factory original calibration files for ADK Ser#M2500000185

    VOXL Dev Kits
    2
    20
    57
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • tomT
      tom admin @latif
      last edited by

      @latif I wonder if you have the wrong kernel on there. If you run voxl-configure-cameras what options does it give you?

      L 1 Reply Last reply Reply Quote 0
      • L
        latif @tom
        last edited by

        @tom 610cafc9-ea38-4c27-98bf-6f251b8ed816-image.png

        1 Reply Last reply Reply Quote 0
        • L
          latif
          last edited by

          Maybe a different issue, running configure stand-alone shows this problem:
          2b918483-fbaf-4ba1-bbdc-5b74fe69d605-image.png
          Checking space I see this:
          38c840b4-5eb5-4c4d-a59b-04306a3afeb6-image.png

          tomT 1 Reply Last reply Reply Quote 0
          • tomT
            tom admin @latif
            last edited by tom

            @latif oh boy, well that is certainly an issue, can you run sudo du -h -d 1 / 2>/dev/null | sort -h to see which directory/partition is full?

            L 2 Replies Last reply Reply Quote 0
            • L
              latif @tom
              last edited by

              @tom Yeah, it's starting to look bleak! Here's the output:
              210015b2-efc8-4ece-ab9f-1e2172c7fc4e-image.png

              The only user data I have is under /home/root, about 1.8GB. I can free up some of it, but how do I redirect the configuration processes to use a different directory other than /usr, /lib, etc.?
              Also, is there a way to increase the overall storage size? I see that the biggest partition ("sda") is only 118G and now full.

              tomT 1 Reply Last reply Reply Quote 0
              • tomT
                tom admin @latif
                last edited by

                @latif /var being that full is very abnormal, here is a screenshot from one of my drones:

                eb2dc6a3-842d-450d-a522-16ae3674ae9b-image.png

                tomT 1 Reply Last reply Reply Quote 0
                • tomT
                  tom admin @tom
                  last edited by

                  @tom It's possible /var/log/journal/ is full for some reason? You could try clearing stale logs from there

                  1 Reply Last reply Reply Quote 0
                  • L
                    latif @tom
                    last edited by

                    @tom Yeah, it's starting to look dangerous. Here's the output:
                    4950b4c9-6f61-46c7-aa09-87e8bf9636c4-image.png

                    tomT L 2 Replies Last reply Reply Quote 0
                    • tomT
                      tom admin @latif
                      last edited by

                      @latif You should be able to go into /var and see what's full and deleting it

                      1 Reply Last reply Reply Quote 0
                      • L
                        latif @latif
                        last edited by

                        @latif Thanks! syslog was 27G! Emptied it out and running voxl-configure-cameras again. Hopefully this will fix the other issues.

                        L 1 Reply Last reply Reply Quote 0
                        • L
                          latif @latif
                          last edited by

                          @latif Hi @tom, cleaning up the /var/syslog file enabled the camera server to run - so the cameras are fine. I'm still not sure if all the calibrations are right, I see an error message 38b571ca-0981-47b6-840b-b372622479ca-image.png when I try to bind the Commando8 Controller. Also, could never get a "READY" sign on QGroundControl. Should I run the "Sensor Calibration" options? Not knowing what that'd do, I didn't run them.
                          If this is relevant information: I'm not getting GPS data consistently (right now getting nothing, but earlier at some point in time I did), right now I see this on QGC: cbaf5101-0eef-4acc-a295-5f60a218b725-image.png

                          tomT 1 Reply Last reply Reply Quote 0
                          • tomT
                            tom admin @latif
                            last edited by

                            @latif What do you see if you run voxl-check-calibration?

                            It sometimes takes a while to get a GPS lock for the first time in a new location, may have to let the drone sit outside for 5-10 minutes for the initial lock, will be much faster after that.

                            L 1 Reply Last reply Reply Quote 0
                            • L
                              latif @tom
                              last edited by

                              @tom I'll let it sit outside for a few minutes for GPS locks. Here's the output for voxl-check-calibration: 79b81c4c-46e8-43f4-9733-0a577fae95f1-image.png

                              Still seeing things like ac080230-6832-4f96-8494-e5cdb4ed5928-image.png

                              tomT 1 Reply Last reply Reply Quote 0
                              • tomT
                                tom admin @latif
                                last edited by

                                @latif You'll want to load the GPS specific px4 param file in order for "position" mode to use GPS position as opposed to VIO position.

                                If you run voxl-configure-px4-params -w and navigate to EKF2_helpers you should be able to see the relevant options.

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Powered by NodeBB | Contributors