Posts made by Eloi

Thanks,
BTW, i've checked it with the help of a team mate and this is the correct FOV orientation for the sensor (not the measurements):

Keep in mind that the Graphics Industry Standard is W x H and you have H x W = 85ºX106º and should be W x H = 85ºx106º (for this position in the picture)
Also, W x H = 85ºx106º vs Horizontal x Vertical = 100ºX80º on the different images can cause confusion with the different orientations and values.

I would suggest to use the same ratings on both pictures.

This is the correct HxV position of the sensor:

Eloi

Dear ModalAI,

At https://docs.modalai.com/M0040/ you have:
FOV (H x W) 85.1° 106.5° (measured by experiemnt)

At https://www.modalai.com/products/voxl-dk-tof you have:
FOV (H x V) 117° x 117° (near field 100° x 80°)

Which is the correct FOV?

Also, which is the correct position of the sensor (as vertical and horizontal plane)?
from this link https://docs.modalai.com/M0040/ or
from this link? https://www.modalai.com/products/voxl-dk-tof

I want to create a 3D cone covering the "view" to be sure that it doesn't see anything else, but cannot due to different FOVs and that i don't know what is the horizontal plane of the sensor.
By now I'll use the more restrictive FOV 117ºX117º...

Thanks for your work!
Eloi

Dear,
We bought the VOXL2 kit + VOXL ESC V2.
And in the web from the VOXL ESC says:
The VOXL ESC is assembled in the USA and works directly with PX4 and VOXL 2.

This is not true, because the cables included (MCBL-00013 & MCBL-00014) are not compatible with the VOXL2 connector.
It needs the https://www.modalai.com/products/mcbl-00029 cable.

Please, modify the webpage info!

Many thanks!
Kind regards,
Eloi Vilalta from Eurecat

So, 80mm or ~85.57mm?C
Can this be changed via software? Where?
Thanks!

Dear ModalAI,
While integrating your VOXL2 kit I found out some features we are missing and we have to do very intricate cable management to deal with it.

I would find very interesting the option to "turn" the cameras 90 degrees with cables or some adaptors like the VOXL2 to Flex camera adaptor.
i.e.: The Camera extension flex but with the connector 90 degrees (left or right), not straightforward.
Also the extension cables could turn upside down the sensors, so when you connect the stereo sensors directly to the VOLX2, one can be looking down instead of both up.
i.e.: for the extension flex, instead of the male connector on the upper part and the female connector on the lower part, both connectors at the upper part of the cable so the cameras faces opposite direction.

Also, it can be beneficial to have a more "open" solution for cables, such as FFC/FPC cables for placing the sensors or think about the already solutions they provide but for your system:

With an adaptor people can route the sensors with more flexibility (not ensuring the proper function of the system of course).

Thanks!
Much appreciated answer!
As we are based in the EU, the company have some "bureaucratic" difficulties to buy outside EU... If we don't break, way better XD
By the way, I would love to find some 90 degree angles cables/adaptors! so the cameras can be just on the side of the board and make everything much smaller! (I'll post the same sentence to the "Feature Requests")
Thanks again!

With Futaba/FrSky/FlySky/TBS/Immersion/etc you just have to look if it's inverted S.Bus or not. There is also some mini inverters PCBs, i.e.: (naze32 does not have anything related to this inverter, works with any flight controller/signal)
https://aerialpixels.com/shop/transmitters-and-receivers/encoders-and-decoders/sbus-to-naze32-sbus-inverter/

Dear everyone,
Which is the minimum bending radius aloud to "twist" the cable sensors around?
Is there any warranty settlements about that?

Once plugged, both pair of stereo sensors looks "up" and we need one to look "down".
But as we don't have much space, a small radius is needed, we will 3D print a "router" for the cable so it doesn't bend over this min radius.

Thanks!
Eloi

Here is the weight in a balance with and without power module.

For our application, we will change the huge 12AWG cables and XT60 connectors for short 18AWG cables and XT30 connectors.

Eloi Vilalta

Well, no one replied, so I did it myself.

It weights fully loaded 134.3g (without: 5GHz board + antennas, power cable missing, usb wifi dongle)

I don't have it, but the possibility to have it and be able to adapt it to any frame, would be a really nice idea from them and expand the VOXL to any platform besides any "DJI 450" alike frame!
Also because they don't sell the "shell" itself.
Eloi

Dear,
By any chance is possible to use one of this PCIe M.2 B-Key wifi modules or also this one on the 5G Modem carrier? This way we have wifi + USB3.0 available!

In case it's not possible: is this another option that could let us use wifi E-Key modules?

BTW: I opened this question about the 5G Module Carrier here because there is only the Microhard and LTE discussion forums.

Thanks!
Eloi

Dear,
Is clear that the computer from VOXL2 is 16 grams.
But if I want to purchase a full kit like:
https://www.modalai.com/products/voxl-2?variant=39914779934771 with the 5G Modem carrier + 5G modem + antennas + GPS option.
How much weight is it? (without the charger)
We want to test the drone with the weight to get proper flight times so we can modify it in advance.

Also, I have some doubts about some weights:

• Here it says 4 grams: https://docs.modalai.com/voxl-stereo-camera-datasheet/#m0015-1
  Is it just for one camera or both cameras + T cable? How much is the T cable?

• Here says "Full APM with XT60 connector is 34 grams": https://docs.modalai.com/power-module-v3-datasheet/#size-and-weight
  Which APM are you speaking about? Do you mean with the cables and connectors?

• When reading about the VOXL 2 Flight deck with 5G LTE, it says it weights 165.3g: https://docs.modalai.com/voxl2-flight-deck-datasheet/
  With what components? GPS? Power Module? Extension cables? With or without the 3D printed case? In that case, how much is the 3D printed case?

Also no info about IMX412 weight: https://docs.modalai.com/voxl-hires-camera-datasheet/#mdk-m0061-1-m12-imx412-120-fov-buy-here
and OV7251 weight: https://docs.modalai.com/voxl-tracking-camera-datasheet/#specification

Thanks!
Eloi

I'll continue this post, as is related to dimensions:
From https://docs.modalai.com/m0010/#2d-diagram it says on top: "100mm edge-to-edge for an 80mm baseline, ~20mm “T” height", but the sensor to sensor distance is roughly 85mm between the stereo cameras following the dimensions of the drawing, notice the cameras are on the middle of the "short cut":


See below the real distance following the dimensions:

In the CAD from the Seeker it's 80mm, just like the description of the cable (a the bottom of the image says 80mm):

Which should be the correct distance between stereo sensors?
If it's 80mm we can bend a bit the "T shape cable" to get the cameras to 80mm without much problem.

Thanks!
Eloi

Many Many thanks @Vinny !
So useful! now we can have everything in CAD!

For me, this post can be "closed"!
Eloi

Dear @Vinny!
Many many thanks for the update!
We thought this list could help you organize the info provided as we found those inconsistencies! Awesome rework!

There is only 3 missing CADs so we have everything we need:

• https://docs.modalai.com/m0084/#2d-diagram the CAD in general
• https://docs.modalai.com/m0076/#2d-diagrams just the offset from the J1 connector as J2 looks centered!
• MFPC-M0040 2D-diagram cable extension from https://docs.modalai.com/voxl-tof-sensor-datasheet/#2d3d-drawings
  (the extension of it with +-1mm precision is enough so you can check it with a caliper if you have one around!)
  By the way, I got the name from the images of your link, this name is not listed anywhere else! (nor written!)

Thanks!

Dear,
We are missing some dimensions from the cables to add them into our 3D model of a drone:

https://docs.modalai.com/m0008/#3d-step-file and https://docs.modalai.com/m0008/#2d-diagram redirecting to the same web page and no 2D images of the dimensions.

https://docs.modalai.com/m0010/#3d-step-file and https://docs.modalai.com/m0010/#2d-diagram redirecting to the same web page with 2D images but no dimensions.

https://docs.modalai.com/m0036/#2d-diagram with 3D cad, but 2D images missing "heights", "accepted" as there is 3D model.

https://docs.modalai.com/m0074/#3d-step-file without 3D CAD, but redirecting to the same web page with 2D images but no dimensions. What's the real lenght? it was 15cm for the 14.5cm extension cable. Is 6.5cm for the 6cm extension cable? (notice the oposite in lenghts and "product name")

https://docs.modalai.com/m0076/#3d-step-file redirecting to the same web page with 2D images but no full dimensions, heigh of the board?

https://docs.modalai.com/m0084/#2d-diagram with 2D images but no dimensions, "accepted" as there is 3D model.

MFPC-M0040 extension cable for ToF sensor missing datasheet?

Thanks!
Eloi

My solution:
Save both files in different folders.

Import .step as:

Save as .part and import to assembly:

But it gets really "dirty"...

At least I can work with it now!
Thanks!

BTW: tried to edit each post, but couldn't and had to create one each time.

Somehow I get both "temporal" files open at the same folder, so one takes the parts of the other...
Can you check if you can open both at the same time? VOXL2 and VOXL2 IO...

Trying to open VOXL2 while IO opened at the background:

Edit: I think I got it, saving the files in different folders....

Well, dunno what happens,
Deteled all files (from download and folder), reset Solidworks and now it opened correctly at first.
Now, when trying to open foth VOXL2 and IO it "breaks":

I guess it's my fault... you can delete de post if you wish as it doesn't help anyone!