Thank you very much for following up! Was going to recommend just reinstalling the system image as described here, but replacing the antennas is even easier

Here is the antenna we use for reference https://www.digikey.com/en/products/detail/molex/1461531100/8543422

There's a few files (as we use DRY even on params 😉 The procedure to do this is here

When you reload the airframe (via these parameters) you'll end up losing calibration and having to go through the calibration process. This is documented here

You'll end up loading these, in this order:

configures core airframe for m500 with 4S battery (standard):
https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/raw/master/platforms/v1.10/m500_4s_config.params

VIO indoor EKF
https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/raw/master/helpers/ekf2_indoor_vio.params

Serial params (to be safe, these should be set by default)
https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/blob/master/helpers/mavlink_serial_ports.params

If needed and applicable, radio
https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/blob/master/helpers/gimbal_dx8_config.params

Thanks Travis!

And thanks for the excellent support.

Hello, When you ran the wizard, what did you enter for the camera configuration question, it should have been option 3 (hires+stereo+tracking) for a flight deck.

Do you mind running voxl-vision-px4 manually in odometry debug mode to see if VIO is working and share the output? You can use this command:

voxl-vision-px4 --debug_odometry

Thanks!

We do not have a thermal option available today, though the Flir Boson and Lepton have been integrated by customers in the past using USB

Stereo cameras need to be co-planar and mounted rigidly. Then they need to be calibrated. Otherwise you should be able to mount wherever convenient

@Pavel-Ardashov
Hi Pavel,
Our circuit boards are all manufactured and assembled with RoHS components and processes (allows us to sell our development components in Europe). However, we are not CE or FCC marked since we do not sell final enclosed products (with a UPC/Bar Code for example). However, some of our sub-components may be marked. For instance if we resell a modem or radio device, it may already be FCC/CE marked.
It is usually our customer's role to undergo specific regulatory requirements and markings for their final product(s) and market locations and we can certainly help you as best as possible should you have further questions.
Hope this helps you.
Vinny

@Eric-Katzfey The main cause was system image version. The internet problem has solved!
now i'll try again the QGC setup.
Thanks a lot.

@Mark-Sears
Hi,

I have also got the flight deck only. Now, I would like to connect to FS-iA6B receiver. For that given cable is not suitable. Could you please suggest me in this regard.

Thanks

Our sense resistors aren't capable of measuring that amperage (out of spec for this power module), but the connector would be an XT90 or greater. To get accurate current readings (not sure if that's critical for you or not), then you'd need to rework the power module's and then update some PX4 params.

Thanks, Chad!

Thanks @modaltb! I just searched for "voxl-logger" and nothing came up because it's not the name of a project. I will spend some time exploring the repos.

Here is our rma page to follow: https://www.modalai.com/pages/rma?_pos=2&_sid=4b1e0e876&_ss=r

ADB was not connected.
After connecting the fastboot board, it turned out to turn on the device in fastboot mode.
After connecting in the fastboot mode manually, using the fastboot command, the disk partitions were flashed, as is done in the install.sh script.
Problem solved

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.

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

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

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.

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