V
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 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
@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!!
@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 @jacobcayetano1
Our Power Module is proven to deliver 30W continuous over the full industrial temperature range.
I'd be shocked if you can find a better module with all of it's features out there for this price point.
I encourage you to stress test it using a load box and you'll see how reliable it is. I'm happy to share a few of our validation plots if you wish. We also unit test every unit with a 3Amp load (15W) before shipping.
Let me know if you have any other concerns about the power module.
To add to what our Moderator has posted, the QGC "Avionics Power Low" feature and warning is useless. The ADCs on STMicro parts are frankly terrible, plain and simple. That is why we use a 16-bit INA231 on the power module for current measurement and reporting.
Additionally, You cannot power the FCv2 over USB fully featured as noted here:
https://docs.modalai.com/flight-core-datasheets-v2-functional-description/#power-supply-and-power-source-mux-details
That USB power option is provided as a convenience for programming w/o a bulky battery.
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 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 @jacobcayetano1
There are still over 500k units in available distribution which we can access.
I would not worry at all at this time and I fully expect we can still build FCv2 as is for years to come.
Our parts sourcing expertise is top notch!
(not sure if you recall but during the parts shortage craziness of 2020-21 we were one of the few vendors who still had product in-stock and shipping!!)
If you had a large order in mind, any head's up is appreciated so we can be sure to have sufficient stock.
Thanks!
@John-Nomikos Great to hear!
Yeah I have since taken over our Cable Tech Docs section and I am currently going though an entire revamp of that page. As part of it, I am going to hopefully get video(s) up there showing proper cable removal techniques.
The biggest issue I know of with MCBL-00001 is that it is just "easier" for users to pull it out using the wires, which strains the crimp pins, and damages the connections. It's required to pull it from the plastic shroud which can be somewhat blocked by the heatshrink on our Power Module, and I see even in our own internal teams that it's not always done correctly.... when done correctly, that cable should last years and years... I have some that are very old (pushing 10 years) and still work great. But I have had come across some internally that only lasted a few days. We might just start providing them in qty-2 batches instead of 1 just to help everyone get past that issue while we improve our training information to hopefully put this issue behind us.
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 @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 @liftedsystems
I just saw this now.. sorry for our delays on this...
We respond better when you start a new thread because we ALL get notified of it internally ... Thread replies are on a "best effort" basis to check so we miss some.... but if you wish to do so, please just tag us using the "@" like you did to get Chad and we will see that at a higher level too, but new threads are always the best!
Thanks, and I hope Travis gave you the info you were hoping for!!
Hi @Jyotish-Kumar
Our design is being assembled and we expect to have it in our hands next week for initial bring-up. Keep an eye out for website purchase links.
Hope this helps you out!!!
https://docs.modalai.com/voxl2-dev-test-board/
Thanks @aheyne for alerting us.
I had made the updates to our site and the 3D models are now there.
Let us know if you need any more help.
Thanks!
Hi @bendraper
Unfortunately, on Voxl2, we set that USB-C port as peripheral mode only, so it cannot be a host to any devices such as mass storage (thumb drives), ethernet dongles, and the like.
Hope that helps.
Hi @Jyotish-Kumar
Yes! We just sent the board for fabrication yesterday!
I'm hoping to get a page up soon to explain it and post the schematics and usage.
Please give us a month or so enabling us to validate it before making it available.
Thanks
Hi @saegsali
yes, I can help with this. Sorry for the delay in responding here...
I will email you to enable the schematic transfer and review setup.
For your schematic, these items will ensure a speedy and seamless review:
Thanks!
Hi @frafrat
It depends on what you have plugged in to the Voxl2 board. It's easy to use an external power supply for a board only setup (no BLDC motors) and run your use cases and read back the current your power supply shows.
We do not do this often since we make a development platform, and all customers use it differently. Moreover, we also do not feel the need to characterize an "idle" state since it is literally a 3rd or 4th order power consumption value compared to any simple actuation (motors or servos). The on-board LEDs are the dominate factor in idle, using about 5mA each at 3.3V and 5V.
My supply, with running nothing and just having an ADB connection pulls about 0.4W, but 0.1W of that is LEDs and I'm positive the rest is power supply efficiency losses, and we do not enter any sleep states especially with keeping ADB up and running the default voxl-suite.
It's likely faster for you to test your setup than to explain to us what your system is and how you wish to use it.
I think one of our SW team members was exploring some of the sleep states, but we just never saw the need to really enter them.
We have many tools in Voxl-suite to monitor running programs, so if you do this, I would recommend trying to understand what is running in "idle" and as you try to disable stuff, you can see the power consumption impact and compare against what functions you need to keep alive for your application.
We cannot share the actual QRB5165 data sheet. Perhaps if you join the Qualcomm Developer Network, you might be able to get some more data directly from there.
If you need further help, please ask.
Hi @Sonoaero
That is a valid electrical connection scheme.
If you plug into either J6 or J7 of V2 Mini, you'll match the configuration shown here:
https://docs.modalai.com/voxl2-mini-image-sensors/#tracking
Keeping in mind M0076 only picks up the "lower" CSI group functions.
I cannot advise as to how SW will work on this config switching from M0014 (OV7251) to M0113 (OV9782), but it is valid electrically.
Hope this helps.
Thanks!
