Hi @rapit were you able to connect with the docker container at the end?

Hi @awagner Electrically, yes. Depending on your VoxlCam config, the port may be used by something else. If you share a photo of your VoxlCam, we can help confirm. These plug-in boards all use the same 60-pin B2B (J13) on Voxl/VoxlFlight, but if you need to maintain 4G LTE modem or Microhard functionality, that uses the same 60-pin, so you'd have to play swap games back and forth.

@tom there is no other methods for example use your nsenter ?!

Since you are in the voxl-flight category, I'll assume you are using Flight Core v1. If so, here are the details https://docs.modalai.com/flight-core-firmware

hello @colerose how do u get all these topics by launching just roslaunch voxl_mpa_to_ros voxl_mpa_to_ros.launch because when i launch it i get just these topics : MPA to ROS app is now running Found new interface: hires Found new interface: qvio_overlay Found new interface: stereo Found new interface: tracking Found new interface: imu0 Found new interface: imu1 Found new interface: voa_pc_out Found new interface: qvio Thank u in advance for your reply

@Chad-Sweet

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 [image: 1682588997181-40f28124-b098-4482-a038-25c450b9df6c-image.png]

Can you run the following after boot and compare what you see on a board with working wifi and non-working one: dmesg | grep wlan There should be a bunch of wlan-related messages and you could diff the output between the two boards to help narrow down the issue. Alex

@Eric-Katzfey and @Vinny thank you for response, ive checked with the oscilloscope and it appears i am receiving signal. as for the wiring diagram, i have wrote it incorrectly. i went back and double checked and you are correct Mr.Vinny, i did, somehow still wire it correctly, but have not received frames. i think its best to move on the purethermal mini that was suggested. thank you all for your guidance, will update soon

@Ansel-Misfeldt FW update feature is working in QGC daily build starting today, no change needed on flight core v2. [image: 1681945120121-23df224f-21ae-4469-b90e-bb255be91ab0-image.png]

4G / LTE is a cellular protocol. The range and performance is determined by the cellular carrier whose service you are paying for. You can use your smartphone as a good proxy for performance. It would be best if you were comfortable with VPN and networking technologies before you try to build a cellular connected drone. There is know how and work involved.

You should compare the settings as configured in the code here. We provide the code so you can fork and implement your own configuration if needed

I was able to use the v1.13.2-0.1.1 file with mission planner, it connected but said update was not required. I will keep an eye out for the v1.13.2-0.1.2 drop. Looking into my compass setup, its a new release from MRO, could be an issue there

Hey, just to give a little update here: I found out how to set the "force mavlink mode" variable in the voxl-vision-hub.conf which was forcing the parameter back in PX4, and simultaneously set it to "Normal" in PX4. So far I don't see any downsides from using MAV_1_MODE=0 (normal). I'm only making use of voxl-mavlink-server and voxl-vision-hub for the time being, basically to use VOXL's connectivity to send MAV commands to the PX4. Do you think using "normal" will have any downsides? The inconsistency between your documentation and the .conf and PX4 firmware files still exists though, so I'd really like to get some more insight on this. Thanks and a great weekend to everyone.

@modaltb I sent it for repair You fond an issue with bad connexion on camera I received it back It is working OK BUT 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 [image: 1678979819117-f7f5c17a-561e-473f-8ddc-f930bc8f0b8a-image.png] Do you have a clue? Do you want me to open a new issue so we can follow more efficiently ? Regards

The Sentinel and VOXL 2 are open development platforms. ModalAI does not use or support Matlab UAV toolbox. So, if you need that feature you will need to figure out how to implement on VOXL 2. VOXL 2 is a Debian Linux system, so it is very flexible