Hi Gaurav,
The PWM Output port J1007 provides 5V DC as a reference on pin 1. This same voltage connects to the main power 5V that powers Voxl.
https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1007---8-channel-pwm--4-channel-dshot-output-output-connector
If you are providing a separate power source on the ESCs different from Voxl's 5V, then you should either insert a blocking diode on this or remove that cable position from J1007.1 and only use a 9-conductor cable, positions 2-10.
If you are using the same 5V supply on Voxl and the ESCs, then these are just shorts and do not matter.
We provide a variety of power tap-off options on Voxl and Voxl Flight and we know sometimes it can create tricky cabling solutions.
Let me know if you would like more info, and if you do, please provide us with the ESC part number you have.
Thanks!
Vinny

@gauravshukla914
Great, thanks for the response. Glad we could help.
Just FYI, that 2A 5V BEC will not properly power a Voxl, nor would any 5V supply though any of the JST or Hirose connectors, although you may see Voxl try to power up.
In those conditions, be sure to use our Power Module as the main 5V so it has a successful power up. This is the only connector that was designed to support the current demand Voxl needs during power up: https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1013---5v-dc-power-input-i2c3-to-power-cable-apm
https://docs.modalai.com/power-module-v3-datasheet/

Be sure to reach out with any additional questions.
Thanks!
Vinny

@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

Hi Raj,
Can you please be more specific with your question?
Are you just referring to hardware connections or are you asking for software device detection?
I'm not familiar with the Jetson systems, but from what I can tell, purely from a hardware viewpoint, there are a bunch of UARTs and I2C ports exposed on a Nano 40-pin header that can be connected to Voxl directly since Voxl is also at 3.3V logic levels for our external interfaces.
https://docs.modalai.com/voxl-datasheet-connectors/
Now, how you expect to use the combined system is a more complicated SW systems question, so this is why I asked if you can elaborate more.
How do you want the Voxl to interact with the Jetson? This will tell us if the bandwidth of the common interfaces (I2C, UART, SPI) are even suitable for your application(s). If a USB interface is more suited to your application for higher throughput, then it can get a bit harder. The Nano appears to have a variety of USB ports, as do our systems, but you'd need to understand who is the USB Host and USB Client/Device and connect them accordingly.
Thanks!
Vinny

Hi Ryan,
Apologies for the long response time. I'll do my best to help you.
Our IMX377 camera module housing has those two side mounting holes on the drawing that indicates a diameter of 1.80mm. So as long as you are smaller than that with sufficient retention you should be good to go. The outer "ear" of that hole shows it is a 4.2mm diameter, so you do not want your screw head larger than that.
Hope that helps.
Vinny

Hi Ryan,
We provided several 3.3V and 5V tap-offs for exactly these reasons. For 3.3V, you have 2 options. J12.1 (with J12.4 as the return) as you pointed out, but be aware that this is the R/C port power which has the option to be disabled by software for binding. By default, I believe it is ON. You can pull 250mA safely from this port without harming the rest of the board. The other port that has 3.3V is J13.1 (and J13.2 respectively for the return). That can also easily provide 250mA. However, Be advised, we did not design either of those 3.3V PTO's (power tap-offs) to the tight ripple specification/requirement of the RM3100. That spec calls for only 50mV of ripple. We designed for a much wider range. So, the RM3100 board should have a lot of capacitance to help reduce this potential spec violation, and I would certainly measure it at the RM3100 if you are expecting to meet their performance specs.
For the I2C interface, all of our I2C busses are at 3.3V logic levels. The port on J6 pins 4/5, J10 4/5, and J13 3/4 all have pullups to 3.3V of 4.7K-Ohms installed on-board. The RM3100 specifies an IOL of just 1mA, so we should be ok there, but make sure you do not have any other pull-ups in the system or you will start to exceed 1mA. I would recommend you try with the J13 port since you get all you need with one cable, and the pull-ups are not on the potential switched rail of the R/C port (in other words, if you use J12 for power only, and J10 or J13 for I2C, there is a chance the SW will disable the power rail, or during startup before it is ON, the pullups are back-feeding into the magnetometer device).
That connector is a BM05B-SRSS-TB(LF)(SN), and you can find the mating shrouds SHR-05V-S-B on digikey with pre-crimped wires as well, or even a 1:1 cable assembly A05SR05SR30K152B.
Let us know if you have any other questions.
Thanks!
Vinny

Hi Nikhil,
Sorry for our delayed response on this. I just recently joined our forum to help out with more HW centric question.
As Chad mentioned, this does require HW mods if you do not want the SW driver timestamp method (which would be our recommendation/preference).
The Lepton signal VSYNC (on GPIO3 most likely is what you are referring to) is running at the VIO voltage of 2.8V to 3.1V per Lepton specs. Our camera sensors are MIPI based, and as such all of those I/Os are at 1.8V, so a level translator would be required which makes connecting these a bit tricky, especially if you need bi-directional support with another sync controller/snoop device. This would need to be something done on a custom interface between the Lepton and the stereo sensors. We do not have such module but would be happy to give further guidance if you need it.
Thanks!
Vinny

@gauravshukla914
Great, thanks for the response. Glad we could help.
Just FYI, that 2A 5V BEC will not properly power a Voxl, nor would any 5V supply though any of the JST or Hirose connectors, although you may see Voxl try to power up.
In those conditions, be sure to use our Power Module as the main 5V so it has a successful power up. This is the only connector that was designed to support the current demand Voxl needs during power up: https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1013---5v-dc-power-input-i2c3-to-power-cable-apm
https://docs.modalai.com/power-module-v3-datasheet/

Be sure to reach out with any additional questions.
Thanks!
Vinny

Hi Gaurav,
The PWM Output port J1007 provides 5V DC as a reference on pin 1. This same voltage connects to the main power 5V that powers Voxl.
https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1007---8-channel-pwm--4-channel-dshot-output-output-connector
If you are providing a separate power source on the ESCs different from Voxl's 5V, then you should either insert a blocking diode on this or remove that cable position from J1007.1 and only use a 9-conductor cable, positions 2-10.
If you are using the same 5V supply on Voxl and the ESCs, then these are just shorts and do not matter.
We provide a variety of power tap-off options on Voxl and Voxl Flight and we know sometimes it can create tricky cabling solutions.
Let me know if you would like more info, and if you do, please provide us with the ESC part number you have.
Thanks!
Vinny