@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 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

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 Steve,
Thanks for the compliment of that design. It is not an open source design, but we are also willing to share with partners with some type of license that we can provide to you (over email, we should be able to contact you in the next day or so).
Keep in mind, the parts on the power module are very (and I mean really very) hard to find and source.
If you do not already have a reputable supply of them, you might be creating more problems than to just keep buying our modules. To give you an example, the main DC/DC switcher on there we have been getting new quotes at over $80-240 EACH PIECE for new builds... (it was an $8 part 3 years ago).
So, something to keep in mind.
I'm sure Chad will reach out to you soon to discuss further and I would be your POC for the actual design details should you move forward with that course.

Thanks!
Vinny

Hi @Ed-Sutter , I'll look at the EM7565 and get back to you.
Hopefully I can find all the info I need to make a determination on the HW side.
SW side, I cannot comment on, but let me check first before they need to look further.

Thanks!

Hi @Roy-Wood,
Great question...
TP21 is VREG_S4A_1P8V which is all the native I/O power rail:

and then right next to that is TP17 which is a DGND (you'll need that one too!)


Hope this helps!

Hi @Roy-Wood
Oh wow, you have an older M0012... We added the TPs on the M0048 version which replaced the M0012 a couple years ago. So, the website is correct, since we do not sell the older version anymore.
Sorry, but I hope that explains the difference you see.

Hi @Roy-Wood,
That would be a good use case had we designed the MH carrier after Voxl2. It was designed for Voxl1 originally and the UART exposed on the Expansion adapter is not even a UART on Voxl1, only Voxl2.

You have two options:

1. SW Option: On the MH carriers, we do expose the Linux debug console UART (noted as "Serial Console" in the image on our docs pages). It's the smaller 1mm pitch JST-SR series connector J2 that exposes the signals at 3.3V.
   .
   So, if someone is savvy with the the Kernel builds to turn that QUP_12 into a normal UART, it could be re-purposed just as UART/QUP_7 is now used on the expansion board.

2. HW Option, (but will void your warranty)
   The UART signals the expansion board picks up are on Test Pads on the MH carrier (bottom side). They are at 1.8V nominally, not 3.3V,so you would need to blue-wire them to a level translator (using solder will void your warranty) and then connect to your external FC.
   But, if you were really curious and handy with a soldering iron, TP28 (right side TP circled in green) is the UART_RX, and TP29 (left pad) is the UART-TX.
   

Hope that helps... Keep us posted since that is a good idea. If we spin this carrier, we will certainly add that as a feature to match the expansion board.

Hi @Jan-Hartmann ,
If you review our MH carrier block diagram here: https://docs.modalai.com/microhard-add-on-datasheet/#block-diagram
You'll notice we unfortunately do not expose the other Microhard Ethernet port. I'm not optimistic there is even a way to get it with blue-wires. Sorry about that.

For S.BUS support, we offer a small standalone product noted here: https://docs.modalai.com/voxl2-io/
We think that is a great little gadget that expands your PWM and I/O options and is meant for Voxl2.

Let us know if you have any other questions!

@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!!

@Aks Hi,
The Chirp solution connects though our 5G modem add-on board (M0067 in that diagram is now M0090).
https://www.modalai.com/collections/voxl-2-add-ons/products/m0090?variant=40594936463411

So, from a HW viewpoint, as long as you use that board, there is no difference. Both connections on J9 are to I2C_10.

We did not design Voxl2 with regards to the TDK mezzanine, so I cannot say how we could connect to it. To my understanding, the TDK design is intended for the RB5 Robotics Development Kit, which is loosely related to our RB5 Flight Platform, but they are very different systems.

We do not sell the Chirp adapters independently from the RB5 Drone kit, and I'm not sure we are planning on that as of yet. It is actually a very intricate solution with a bunch of sub-assemblies. M0086 is our way of talking to two Chirp EVKs sold here: https://www.digikey.com/en/products/detail/tdk-invensense/EV_MOD_CH201-00-01/13174314?
Built into our RB5 Flight Deck are also flex cables to the Chirps, and special mating plastic apertures for the Chirps to mount in, so it is not easy to offer this solution as a standalone.

I've tagged some SW folks internally to respond to your query, so hopefully we can provide a response soon regarding that aspect of it.

@Kevin-Racktoo Glad we can help.
If you would like us to review your schematic for Voxl2 integration before you tape-out, just let us know!
You can use our contact form to reach out and we'll respond back.
https://www.modalai.com/pages/contact-us

Thanks!

We just made a new page for the M0094 product.
Please check out the following link for a detailed description of the M0094 board and the pin tables for both RB5 Flight and Sentinel drone platforms.
https://docs.modalai.com/sentinel-spektrum-bind-board/

Thanks!

@Kevin-Racktoo Hi again Kevin,
I'm happy to provide this updated resource: https://docs.modalai.com/voxl2-custom-expansion/
We just added a new zip file with all the outputs that someone with Altium could make (but I added in some extra ASSY views with dimensions for you that are not part of the original Altium package).
Hope this helps speed up your design process.
Let us know if you have any more questions or need more help!

Thanks!

@Kevin-Racktoo Hi Kevin,
Please give me a few hours and I'll update our website with some extra 2D .PDFs to help with your questions. I'll be sure to include relevant dimensions that are obtained from the altium package.
I'll post a link here once that new data is live.