Posts made by QSL

I am curious what the recomendation is for installing a fan in the assembly of our enclosure that covers our platforms internal electronics.

We were planning to put a 20mm fan that is underside of the platform and pushing air into the body of the platform that the Voxl and the Autopilot/ESCs and Herelink radio will be located. We will be using a MRO Pixracer Pro connected to the Voxl for Obstacle Avoidance and GPS denied flight.

The plan is to have the voxl sitting a bit forward from the fan but it will definitely get some air pushed directly on it from below. I know the barometer is used when Voxl is also running PX4 inplace of an external autopilot, but I am unsure if it is used when its being used as a companion instead. If so, is it ok to run the fan in this layout?

@tom said in Missing Config File:

voxl-configure-vision-hub factory_enable

thanks. I tried the Sku Wizard then MPA but I seem to still have a blank file when I open it in nano. I will try the factory default next.

@Moderator any insight would be appreciated!

TIA

Hi,

I have a Starling 2 we just started getting acquainted with and I am not 100 percent sure what I did. I was being very careful as I am green to much of this but I believe I somehow erased the

/etc/modalai/voxl-vision-hub.conf

file. I was using Nano to just look through it but not altering anything. I believe I accidentally closed my terminal window and restarted a new one to then ssh back into Voxl over Wifi.

When I went back to examine the config file again it was blank....

See screen shot attached

I am not sure what to do now in terms of best path to restoring it or steps to reconfiguration that wikl recreate it.

I also am wondering if I have another instance running on the Voxl that has the file open maybe? If so I power cycled a few times but it still seems to be blank.

Any assistance would be great!

@Riley-Dove would you have any insight on this? Thanks!

@Moderator any help on this would be greatly appreciated.

@Alex-Kushleyev This absolutely is very helpful. I still have some questions though about your documentation about extending sensors further than these cables allow. It says to contact you guys about potential solutions.

We have a decently large size platform that we really want to understand how to position sensors in optimal locations that are not very close to where the Voxl2 is located. This 70mm Cable will still be too short for us to mount the sensor where we would like to.

Our platform is a y6 that is 7" size propellers. We can use a 170mm coax for the front sensor package but for the rear TOF I am wanting to know how could we get it to have 170-250mm cable length so it can be routed to the best location?

Thank you again!

@Idan-Fiksel let me know what we need I can get it.

@Moderator could you help us on this? Thanks!

BTW We currently have a hadnful of what seems to be the incorrect adapters listed here:

2x VOXL 2 Mini 40-Pin Connector TOF Adapter (MDK-M0172-1-00)
2x VOXL to VOXL 2 Image Sensor Interposer
2x VOXL 2 Dual Image Sensor Expander
2x Cable 26-pin Micro-coax for Image Sensor Modules

TIA

@Moderator So to confirm, we need the M0173 to connect the 3 front sensors then the M0172 for the single rear TOF, what cables would we use that are the longest ones available to then connect to the Voxl2 ports?

Thanks!

@Moderator This is appreciated, I had however already seen these docs. My issue is that though you have a 15cm extension that does not account for the orientation of the Voxl2 in relation to the sensor and location to mount them. due to this the 15cm connector is not long enough. Is there any advice on how we can extend these sensors beyond these lengths? Is there some shielding or other potential signal boosting we can do? Our goal is to eventually be able to position the sensors further away from the voxl2 as we want to use the hardware on much larger platforms where the rear sensors will need to be further than our current test development.

TIA for any insight.

@Moderator it would be great if we could get some assistance....