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

Moderator

@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

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

Chad Sweet

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

patrickpoirier

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

patrickpoirier

@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 ?

patrickpoirier

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

patrickpoirier

I decided to test on PX4
Flashed the CUAV NORA with PX4 using QGgroundControl
Connected and tested by looking at ODOMETRY signal
Working Good

patrickpoirier

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".

patrickpoirier

@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 ?)

patrickpoirier

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