FC2 schematic and board file
-
Hi there, can you please provide the FC2 schematic and board file? we'd like to measure/hooking CAN bus/UART/PWM etc signals during our development. Thanks.
-
-
Hi @Jacob-Camarillo, thanks for your information about FC V2 but I'd like to see more of peripheral ICs/Modules pins connection and power tree design, can ModalAI please share the schematic with me?
Thanks,
Daniel -
Hi @daniel
We do not have an open-source HW platform, so we do not share schematics publicly.
If there is specific info missing on our tech docs page, please let us know. We provide an elaborate diagram in there which includes the power distribution and mux tree: https://docs.modalai.com/flight-core-datasheets-v2-functional-description/#block-diagram
Our pin tables also provide all access points you should need: https://docs.modalai.com/flight-core-v2-datasheets-connectors/Thanks!
Vinny -
Hi @Vinny , we have can bus no communication issue, according to J8 - CAN Bus Connector Notes CAN “Silent” pin (STBY) is controlled by STM32 PD15 pin (default pulled-LOW in hardware), can you please provide the STM32 PD15 pin's location or board file for our measurement?
Thanks,
Daniel -
Hi @daniel
Here is the SCH snippet of the CAN XCVR device and connector... note pin 8 is pulled LOW by default to keep it active. SW must drive the CAN1_SILENT pin HIGH to place it in STBY mode.
Hope this helps!
-
Thanks @Vinny , can you please also provide the PX4 detect/Monitor circuits? if possible using that monitor circuit to read the battery level through ADC1/ADC3 instead of can bus?
-
Hi @daniel
Our block diagram shows we have 4 ADC inputs exposed on a connector, J14, for general purpose use.
However, I'm not sure if it is linked in PX4 use or not:
https://docs.modalai.com/flight-core-v2-datasheets-connectors/#j14---external-spii2cadcFor the PX4 monitoring circuits, we do not recommend messing with those in any way. Those are basic 5V and 3.3V voltage detect circuits and ID settings, and I'm pretty sure PX4 will balk if those are re-purposed. However, we do show on the block diagram all pin assignments if you look carefully. If you are trying a so-called "bare metal" design (non-PX4, your own code through the ST32 Cube IDE), then do so at your own risk but we cannot offer any RMA service on boards modified from their intentional design.
-
Hi @Vinny
Yes, I see the pin assignment on the block diagram, but I want to see the circuits of "basic 5V and 3.3V voltage detect circuits and ID settings" seem like those configs are important for PX4.Can you please tell how many ways that FCv2 can get battery information? is it via I2C3 bus to read the battery information from power module? any other way?
Thanks!
Daniel -
HI @daniel
Yes, battery info is from the power module via I2C3.
The detect/ID circuits are part of our proprietary design that we cannot share over a public forum. Hence, we do not recommend you mess with the detect functions at all.
Hope that helps. -
Hi @Vinny,
Please advise the FCv2 MCU stm32h753ii for PCB stackup, how many layers of PCB? Is it need HDI or just normal PCB process?
Thanks! -
HI @daniel
That is part of design strategy that your Engineering team needs to decide when working with various parts and PCB Fab manufacturers. This is not something we can share (and even if we did, it would not be applicable).
Thanks! -
Hi @Vinny ,
I have couple questions on FCv2 hardware, thank you!- what is the purpose of STM32 UART7 through level shifters (74LVCH2T45)? both VCCA and VCCB are same 3.3V domain?
- J2 - where is VPP_STM connect to and what is the function?
- J5 - why there is no level shifter on UART5?
- J13 - Is that PM monitoring really need for FC? Can I just use a adc pin to monitor battery voltage through the divided resistors?
- RGB1 LEDs are controlled by GPO PE3/4/5, please confirm which pin for witch color.
Thanks,
Daniel
-
Hi @daniel
Please see responses below.@daniel said in FC2 schematic and board file:
- what is the purpose of STM32 UART7 through level shifters (74LVCH2T45)? both VCCA and VCCB are same 3.3V domain?
Yes, an early proto-type design had that port at 5V, so we had the level shifters. We then changed it to 3.3V for our production version, so technically the level shifters would not be needed, but it will give you longer cable drive range because of it.
- J2 - where is VPP_STM connect to and what is the function?
You can get this info from any STM device spec. We (a programmer device) use it the way STM specifies
- J5 - why there is no level shifter on UART5?
It is not needed. See response above.
- J13 - Is that PM monitoring really need for FC? Can I just use a adc pin to monitor battery voltage through the divided resistors?
That feature is your choice. The power monitoring will be MUCH more accurate since we use a 16-bit device as highlighted here https://docs.modalai.com/power-module-v3-datasheet/ , and it is capable of coulomb counting if the PX4 drivers that can do that. There are tons of research articles out there about pure voltage monitoring vs coulomb counting, so we leave it to you to decide what works best for you.
- RGB1 LEDs are controlled by GPO PE3/4/5, please confirm which pin for witch color.
We go in order of the port pins noted as "RGB", so PE3 is RED, PE4 is GREEN, PE5 is BLUE. All are "Active LOW" to Illuminate the LEDs.
Hope this helped!!
To me, based on all the questions you've been asking these past weeks, it seems as if you are designing your own version of HW that you want to be compatible with our FCv2 firmware.
If this is true, just let us know and we can try to assist you better. If you want a different form-factor for the board, that might be something we'd be interested in supporting if it helps you better. Just ask!
Feel free to use our contact page if you want the conversation to be less public: https://www.modalai.com/pages/contact-us
