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

    voxl-mavlink-server[3036]: ERROR message magic number wrong #284

    Flight Core - ArduPilot
    3
    9
    632
    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.
    • M
      Moderator ModalAI Team
      last edited by Moderator 16 Mar 2023, 23:15 16 Mar 2023, 23:15

      @patrickpoirier Moving to a new topic from here for better visibility

      I have an other issue regarding connecting to ArduPilot

      It seems it is having issue with MavLink Message :

      voxl-mavlink-server[3036]: ERROR message magic number wrong #284
      And it seems to reconnect under a different ID

      5a63e3a5-517c-4bc5-ae4e-eb5028d695be-image.png

      Do you have a clue?
      Do you want me to open a new issue so we can follow more efficiently ?

      1 Reply Last reply Reply Quote 0
      • C
        Chad Sweet ModalAI Team
        last edited by 16 Mar 2023, 23:17

        An issue was recently identified where Mavlink 1 messages were causing issues. The fix is here on the stable branch. This might be related to what you are seeing

        1 Reply Last reply Reply Quote 0
        • P
          patrickpoirier
          last edited by 17 Mar 2023, 11:34

          @Chad-Sweet thanks for the link, I will apply and report back

          1 Reply Last reply Reply Quote 0
          • P
            patrickpoirier
            last edited by 21 Mar 2023, 13:23

            @Chad-Sweet still trying to figure out the best way to update the module.

            I would appreciate some guidance on the process, I mean do I have to build using voxl-emulator docker and upload the particular module ?

            1 Reply Last reply Reply Quote 0
            • P
              patrickpoirier
              last edited by 20 Apr 2023, 14:45

              OK I have upodated to latest suite
              voxl-suite: 0.9.5

              Enabled services and configure
              voxl-configure-cameras 7 rotate_stereo
              voxl-configure-extrinsics seeker_v1_voxlcam

              Magig number error is gone, but still experience the mavlink crasg and reboot that makes multiple instances on Mavlink inspector as showned above

              1 Reply Last reply Reply Quote 0
              • P
                patrickpoirier
                last edited by 20 Apr 2023, 14:51

                I decided to test on PX4
                Flashed the CUAV NORA with PX4 using QGgroundControl
                Connected and tested by looking at ODOMETRY signal
                Working Good
                63baa341-a0ee-4b59-a710-1f2452475a34-image.png

                1 Reply Last reply Reply Quote 0
                • P
                  patrickpoirier
                  last edited by 20 Apr 2023, 14:55

                  What would be the next step ?
                  My use case requires ArduPilot and at the present stage it seems to be impractical unless you complete the complete integration.

                  Meanwhile, I will try the ROS optin, but this is quite a big detour for something that I was expeting as "Plug and Play".

                  1 Reply Last reply Reply Quote 0
                  • P
                    patrickpoirier
                    last edited by 21 Apr 2023, 12:26

                    @Chad-Sweet
                    Could you implement a simple selection mode on the voxl-configure-vision-px4 allowing to specify px4 or ardupilot ?
                    And in the case of Ardupilot, just pass the qvio signal straight to mavlink (I guess it was like this before ?)

                    1 Reply Last reply Reply Quote 0
                    • P
                      patrickpoirier
                      last edited by 27 Apr 2023, 09:50

                      ok I found the problem...
                      the Cube Serial inteface are driven by TXS0108E Level Shifter powered both side with 3.3 volt making it marginal for the Voxl Primary Serial interface. Switching to secondary interface on the Voxl made it work correctly.

                      I sent a request for a change in the WIKI to reflect that configuration

                      40f28124-b098-4482-a038-25c450b9df6c-image.png

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