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

    Voxl2 Mini Failed to Configure px4

    VOXL 2 Mini
    2
    14
    677
    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 @Nicholas Hansen
      last edited by

      @Nicholas-Hansen what do you see with systemctl status voxl-imu-server?

      Nicholas HansenN 1 Reply Last reply Reply Quote 0
      • Nicholas HansenN
        Nicholas Hansen @tom
        last edited by

        @tom here is what I got 6db85361-8214-4252-a722-93f35483dfa3-image.png

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

          @Nicholas-Hansen Hmm what do you see if you run voxl-imu-server manually from the command line?

          Nicholas HansenN 1 Reply Last reply Reply Quote 0
          • Nicholas HansenN
            Nicholas Hansen @tom
            last edited by

            @tom here is what I get when I run that command ff9affb7-249b-4858-a3f6-e9b52cb020f5-image.png

            tomT 3 Replies Last reply Reply Quote 0
            • tomT
              tom admin @Nicholas Hansen
              last edited by

              @Nicholas-Hansen d423ca41-24e9-462f-872e-fafb69a07259-image.png

              Here is what my setup looks like with the same release.

              Can you confirm that your config file looks the same:

              voxl2-mini:/$ cat /etc/modalai/voxl-imu-server.conf 
              {
              	"imu0_enable":	true,
              	"imu0_sample_rate_hz":	1000,
              	"imu0_lp_cutoff_freq_hz":	92,
              	"imu0_rotate_common_frame":	true,
              	"imu0_fifo_poll_rate_hz":	100,
              	"aux_imu1_enable":	false,
              	"aux_imu1_bus":	1,
              	"aux_imu1_sample_rate_hz":	1000,
              	"aux_imu1_lp_cutoff_freq_hz":	92,
              	"aux_imu1_fifo_poll_rate_hz":	100,
              	"aux_imu2_enable":	false,
              	"aux_imu2_spi_bus":	14,
              	"aux_imu2_sample_rate_hz":	1000,
              	"aux_imu2_lp_cutoff_freq_hz":	92,
              	"aux_imu2_fifo_poll_rate_hz":	100,
              	"aux_imu3_enable":	false,
              	"aux_imu3_spi_bus":	5,
              	"aux_imu3_sample_rate_hz":	1000,
              	"aux_imu3_lp_cutoff_freq_hz":	92,
              	"aux_imu3_fifo_poll_rate_hz":	100
              }
              
              Nicholas HansenN 1 Reply Last reply Reply Quote 0
              • tomT
                tom admin @Nicholas Hansen
                last edited by

                @Nicholas-Hansen Can you also provide me with the board's serial number?

                It will be on a white sticker in the format MXXXXXXXXXX

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

                  @Nicholas-Hansen Lastly can you provide the output of voxl-imu-server -t

                  1 Reply Last reply Reply Quote 0
                  • Nicholas HansenN
                    Nicholas Hansen @tom
                    last edited by

                    @tom M22000006B0 is the serial number, and the output of voxl-imu-server -t is 963ed4e9-2164-46a9-93be-7e720fc358d9-image.png

                    1 Reply Last reply Reply Quote 0
                    • Nicholas HansenN
                      Nicholas Hansen @tom
                      last edited by

                      @tom the config appears to match 151bac38-95dc-4f03-9f95-1ed30345be06-image.png

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

                        @Nicholas-Hansen It seems as though there is a hardware issue preventing the IMU from communicating correctly.

                        Our factory test data all looks good so this failure must've occurred post shipment.

                        If you'd like, you can send this board in for an RMA: https://www.modalai.com/pages/rma

                        Nicholas HansenN 1 Reply Last reply Reply Quote 1
                        • Nicholas HansenN
                          Nicholas Hansen @tom
                          last edited by

                          @tom Ok, thank you for you help & time in troubleshooting this issue

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