Intergrating VL53L1x Range Finder with VOXL2

[Jetson Nano]

@modaltb is connected on J5 port of M0141.

[modaltb]

@Jetson-Nano can you take a picture? for example, we make a M0070 board that has this sensor on it. Are you making your own carrier board for the sensor?

[Jetson Nano]

@modaltb This is our setup,

[Vinny]

HI @Jetson-Nano
We have not seen that module before.
Is there a product link you can share so we can investigate for voltage and signal compatibility?

Thanks!

[Jetson Nano]

@Vinny @modaltb Here is the link of the product

Just a moment...

(www.ktron.in)

Thanks!

[Vinny]

Thanks @Jetson-Nano
Can you help us find schematics?
I do not know what these parts are doing and could be leading to some of your issues...

That site only has the link for the original datasheet.
Without more detail, I cannot offer much help aside from speculation.

Thanks!

[Jetson Nano]

@Vinny I was not able to get the schematics. But when I tested this sensor with a Pixhawk flight controller running PX4, I was able to get it working on I2C.

[Vinny]

Hi @Jetson-Nano
Pixhawk ports are 5V voltage output, we provide 3.3V.

So, that data point does not help me from the HW viewpoint. I am assuming you knew you had 5V VREF from Pixhawk and converted to 3.3V.

However, if we had the SCH of that module, that will tell me if they are actually trying to do voltage conversion of the I2C bus down to 1.8V (the default operating mode of these ST ToF units), which most likely is not compatible with our ports.

Most hobby electronics shops do not plan for all variations of translators, and most voltage translators do not like being cascaded. With a pixhawk, you are native 3.3V from the micro-controller w/o a level translator, so going through 1 level translator down to either 1.8V or 2.8V is no issue.
On VOXL 2 and VOXL 2 Mini, all of our JST ports have been translated up from 1.8V to 3.3V, which can limit the signal level translators we can work with since we end up with cascaded translators and that can be problematic if not designed correctly, especially I2C.
So, the SCH for that module is required for me to help further.
Sorry, but I can't do much else.

[Jetson Nano]

@Vinny Is there any other carrier board you recommend, because modalai doesn't have the rangefinder for sale yet?

[Vinny]

Hi @Jetson-Nano
Every time we try an OTS product, it is flakey due to level translation issues. So we have done our own internally, but not yet made it available standalone. It is on our roadmap to support these ST ToF modules, not just the VL53L1x, but others as well.

The Starling V2 Front End has one of these, but we have not made that little board a standalone product yet: https://docs.modalai.com/M0173/#downward-range-finder-and-flir-lepton

[Jetson Nano]

@Vinny Thanks!

[Vinny]

@Jetson-Nano
I'll try my best to tag you once we make the M0157 for sale individually, but it relies specifically on the hardware circuits on M0173 to work.
Again lots of interface nuances with these little ST sensors, and the newer ones are more painful to integrate since they are dual voltage. We are working that aspect now for future efforts. I know this does not help you now, but rest assured we are on it!

[Jetson Nano]

@Vinny I saw that M0173 is available in the modalai website. If I get that board with the new image sensors and use it with voxl 2, can I get the VIO running with three tracking cameras?

[Vinny]

Hi @Jetson-Nano
Sorry, not my area of expertise.

@modaltb, are you able to offer guidance here?
Thanks!

[modaltb]

@Jetson-Nano not at this time and not with QVIO. We are working on multi cam VIO but can't provide any details or release dates really at this time.

[Jetson Nano]

@modaltb Thank you for the update