Port 14550 is meant for external connections to different IP addresses such as multiple ground control instances. Only one connection to localhost is supported on port 14551. To support multiple local IP connections a separate port and thread would likely need to be opened. You can also have multiple local processes communicate through the "vvpx4_mavlink_io" pipe using libmodal_pipe instead of UDP.

Thank you @Chad-Sweet for your reply.

Missed that part, thank you, it seems to do the trick.

Perfect! I know how to run those. Thank you

Outstanding! Thank you for following up

Hi, Thank you very much. I've check EKF2_AID_MASK,it was a problem with my setup (Flight core wasn't configure well). Now I'm working with VOXL FLIGHT and on QGroundControl I see ODOMETRY message as well. Maybe could you help me with understanding the following issue?: With VOXL flight I want to execute the outdoor flights without GPS. But on QGroundControl ,I didn't see DO_SET_HOME button(request) like with GPS flights and therefore i couldn't execute auto flights. How i could did it? Thanks again

That really depends on the environment. VIO is not limited in height, but does require visible features to track with computer vision

We don't sell any platforms with the M0024 sensor onboard by default. If you're just trying to use it for color fpv/more general inspection I'd suggest just VHB taping it to the front, if you're trying to use it for hyper-accurate detections you'll have to modify one of our platforms or design your own (as most of our platforms are meant to serve as reference designs and not full production hardware).

We have never tried that radio, but you are likely correct. The list of receivers tried is on our documentation here

Thanks Alex. Mainly wanted to check if this was a known issue with hardware or the AE algorithm. It is strangely repeatable on this flight deck. Works indoors in pretty extreme high contrast, fails outside in hazy/overcast conditions. Another flight deck was working well in the same/similar conditions. We've ordered some more hardware and will follow up after doing more testing with AE settings.

Hi @relevinsky , We use an external mag (we ship our m500s with the Holybro "2nd" GPS with the 6 pin connector) and it plugs into here: https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1012---external-gps--mag-usart1-i2c1-connector

@modaltb Using USB 2. Got my hands on an OTG adapter, seems to be doing the trick.

My fault. Found a small tear in the ribbon for the stereo cameras RESOLVED

Hey, just wanted to give an update it looks like the problem was a hardware fault. The behavior stayed the same after detaching the LTE and the setup works on a different VOXL Flight, so yeah...^^ cheers

@Chad-Sweet I have tried with flysky receiver also but it's not working. Please suggest the receiver which is compatiable with flight deck.

Thank you so much!

There should be no expectation that VIO will work at night, it is a computer vision system that relies on visual features. Please see details here on troubleshooting VIO: https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

Yes, I've tried tracking->hires->stereo, that does not work. How would it be hardware if each of the cameras can run fine on their own and any combination of the two work at the same time?

In theory two VOXLs networked together are possible. We have not actually done that ourselves though. You could potentially use the UART side port to send data back and forth with libvoxl_io, that might be the most straightforward.

The Flight Core portion on the Flight Deck is very similar to a standard Pixhawk with very close to stock PX4. There are 8PWM, so if you assign all of them to motors in an Octo configuration, it should work as any other PX4 flight controller would work.