Hi @Mihir-Bala
You will need a 2S minimum to satisfy all the requirements of our power module: https://docs.modalai.com/power-module-v3-datasheet/
Then, you need to do the math to support a 30Watt transient on power up... which equates to a ~5amp burst at the low end of the 2S cell ~6.4V.
So, if you have a 1,000mAh cell at 2S, that will require a 5C rating.
If you have a 2,000mAh cell, you need ~2.5C rating, and so on...
Hope this helped!
Hi @jacobcayetano1
Apologies for not updating some of the tech docs content about that test board we developed.
Here are some links:
https://docs.modalai.com/voxl2-dev-test-board/
That describes the board and provides schematics and other useful user info.
Since the test board is a very easy way to destroy your VOXL 2, we keep the sale of it on our Beta page to alert customers that it is an "at-risk" design since you can easily void your VOXL 2 warranties by over-stressing the VOXL2 and introducing ESD and other signal shorting risks.
That said, here is the purchase link:
https://www.modalai.com/pages/beta-voxl-2-b2b-breakout-board
It comes as a kit with many goodies for it's use including cables, a mounting case, and an SD card.
Now, as far as being able to use Microhard AND J5, we recommend using the standalone version ("dongle") of the Microhard board: https://www.modalai.com/collections/modems/products/mdk-m0048-2 since that will allow you to cascade it off any USB port we have (or one that you include in your design).
Here are some tips for designing a good USB port with our Voxl ecosystem: https://docs.modalai.com/expansion-design-guide/#usb-expansion-over-j3--j5
Should you go down the route of designing a custom VOXL 2 plug-in board, we will offer a courtesy review of your schematic to help you along! Feel free to tag me again when you are ready, and we will start an email exchange to share your data so you are not posting it on our forum (unless you wanted to).
Hope this helped.
Vinny
Hi @serviceberry
From a HW viewpoint (I am HW team) that sounds reasonable to use the hub the way you suggest. But I know for a fact from personal experience the Boson's are very dependent on VBUS rise times, and a very fast rising 5V supply may not allow it to enumerate properly. We have had an instance in the past where one particular VBUS port rose really fast, and the Boson did not enumerate until we slowed it down. It's one of those situations that may require testing to check. Our J3 10-pin host port has a nice moderate rise time that allows Boson to enumerate. So, when using a Hub, check the VBUS rise times compared to J3.
I do NOT expect J9 USB-C OTG port to work with Boson.
The Snapdragon SOC is very smart, and when in OTG mode, it will not provide more than 500mA to any device that enumerates as USB2 which I am lead to believe how the Boson enumerates. if the Boson could enumerate as a USB3 device and the drivers were all present in the Kernel for this, the Snapdragon will give it 900mA over VBUS letting it boot but I think this is a non-starter without the Boson being able to do that.
Our Boson kits use USB2 only and we provide 1A support to enable them to work without requiring enumeration to negotiate more current, hence why they work on the J3 ports and other expansion board ports that have more than 500mA: https://docs.modalai.com/expansion-design-guide/#usb-expansion-over-j3--j5
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
@Ansel-Misfeldt Hi,
The approach we will take for CANBUS right now is similar to what we have. That is, to add CANBUS, it requires the use of a FlightCore Flight Controller. So, with Voxl1, you have Voxl-Flight which integrates the FlightCore, or you add on Flight Core independantly.
For Voxl2, you can still use a FlightCore, but we have some exciting news coming soon for a newer improved FlightCore, we will likely call it FlightCore V2 
It will retain CANBUS functionality but has a slew of other upgrades and user improvements added in, all in the same form-factor as FCv1.
Our Docs portal is just about ready for launch and I think we did a better job up-front on this one to help our customers get running quickly.
Stay tuned, we should be posting it for sale in the up-coming days!!
Hi @austin-c
yeah, and it will not.
There are dozens of changes between the two boards.
It's just easier and cheaper to order the correct version. We have no documents showing how to convert it is simply not doable for the cost and risk and time.
Not the news you wanted, but please trust me on that one.
Hi @dougmiller
If your VOXL 2 Mini is TrustZone Configured for UART over J10, then yes, there are 2 pins available as inputs.
https://docs.modalai.com/voxl2-mini-connectors/#j10---external-uart
You can see GPIO_40, GPIO_46 and GPIO_64 are input capable.
GPIO_40 and GPIO_64 are able to be configured to do wake events in the SoC so they have extra configuration to route to a power manager. Depending on how you write your IRQ routine, that may or may not help.
Hope this helps!
Hi @saegsali
Yes, we are actively working on 3 other solutions with different vendors.
We understand the importance of having options here.
Nothing is in production yet, so please bear with us as we continue our development.
We hope to have some extra support by Q3 of this year with at least 2 other products, one being what you mentioned, and NOT over USB
Thanks!
Hi @John-Nomikos
Have you confirmed the issue we pointed to in the other forum post?
https://forum.modalai.com/topic/1356/sentinel-drone-randomly-reboots?_=1673383475709
Do you have Kapton or another insulating tape you can place on the J5 120-pin B2B connector on Voxl2 to help confirm the Microhard is not touching J5? We've seen it first hand that it triggers resets.
I doubt all 3 MCBL-00001 are all bad on you (although we do know they go bad fast from users pulling them out by the cable wires instead of the plastic shroud, but that's another issue).
Let us know.
Thanks!
Hi @dlee
All of our Doodle configs are only using USB2, not UART.
Hope that answers your questions.
Thanks!
Hi @saegsali
Yes, we are actively working on 3 other solutions with different vendors.
We understand the importance of having options here.
Nothing is in production yet, so please bear with us as we continue our development.
We hope to have some extra support by Q3 of this year with at least 2 other products, one being what you mentioned, and NOT over USB
Thanks!
Thanks @Nikos-Mavr for the drawing, that helped.
The thing to be careful about is the I2C voltage levels.
https://docs.modalai.com/voxl2-connectors/
J19 port I2C's are set to 3.3V with on-board pullups. So, I'm not sure what the 12S module I2C levels are, but be sure they are either (3.3V) or (set by host, i.e.: no pulls on the battery side)
I'm not sure what voltage is feeding into this portion... make sure it is limited to 6S:
Now that Eric has given you a bunch of guidance, let us know if there are still problems overall.
Thanks!
Hi @Nikos-Mavr
Please provide a drawing or sketch of your setup in question for the I2C interface, include as many details as possible so I can help you.
Thanks!
Vinny
@jmltt
Yes, that looks correct.
https://docs.modalai.com/voxl-2-wifi-setup/#overview
The dongle is expected to have the specific Realtek RTL8812/8818 part in there. You'll see the RTL part number in the serial console or ifconfig (I think, I'm not SW).
Hi @Jetson-Nano
Sorry for my delay, I was OoO when the first message came through.
In any event, I can only say we have no plans at the moment to explore this new Lepton, and I have not even reviewed the spec sheet, so I cannot offer any guidance on it.
Sorry I can't be of more help.
Hi @austin-c
yeah, and it will not.
There are dozens of changes between the two boards.
It's just easier and cheaper to order the correct version. We have no documents showing how to convert it is simply not doable for the cost and risk and time.
Not the news you wanted, but please trust me on that one.
Hi @wetherbeej
Oh yikes..
You should really work with us on that change. There is a high likelihood to damage your VOXL 2 and the MEMs sensors are likely all broken now from the extra reflow cycles.
Flash provisioning is all done over QFIL tools, not PCAT.
@Pelle-Bredegg-Hermansen
Hi Pelle,
I emailed you the schematic review report for your considerations, just wanted to post here this task is completed.
Keep us posted!
Thanks!
Hi @Richa
We have not provided our pinouts for this and have no plans to.
For our Micro Coax direct CMOS based sensors, you need to use our products end-to-end to guarantee functionality.
Hope this helps clarify.