<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Flight Core v2]]></title><description><![CDATA[Flight Core v2]]></description><link>https://forum.modalai.com/category/36</link><generator>RSS for Node</generator><lastBuildDate>Tue, 21 Jul 2026 19:36:47 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/category/36.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 26 Nov 2025 01:59:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[MCBL-00010 cable fail to connect FC v2]]></title><description><![CDATA[I fix this issue.
switch the Pin1 &amp; Pin4 of MCBL-00010 cable is OK
]]></description><link>https://forum.modalai.com/topic/4890/mcbl-00010-cable-fail-to-connect-fc-v2</link><guid isPermaLink="true">https://forum.modalai.com/topic/4890/mcbl-00010-cable-fail-to-connect-fc-v2</guid><dc:creator><![CDATA[francis]]></dc:creator><pubDate>Wed, 26 Nov 2025 01:59:15 GMT</pubDate></item><item><title><![CDATA[PWM ESC calibration for VOXL ESC 4-in-1 Mini  and QGroundControl]]></title><description><![CDATA[Hi @Martin-Lukac
Good catch on the pin swap. The Table is correct, with Pin 6 = GND.
The one thing I was wondering is related to this comment:
" I can power the ESC and the FCv2 separately."
That is not necessarily a good thing, and likely to lead to problems if you are powered up or down at different times. If one output (TX) is driving an unpowered input (RX), it could put the HW in a bad state. Please make sure to have them synced for ON and OFF.
Thanks.
]]></description><link>https://forum.modalai.com/topic/4778/pwm-esc-calibration-for-voxl-esc-4-in-1-mini-and-qgroundcontrol</link><guid isPermaLink="true">https://forum.modalai.com/topic/4778/pwm-esc-calibration-for-voxl-esc-4-in-1-mini-and-qgroundcontrol</guid><dc:creator><![CDATA[Vinny]]></dc:creator><pubDate>Mon, 29 Sep 2025 01:38:02 GMT</pubDate></item><item><title><![CDATA[Flight Core V2 to replace a Pixhawk 6C]]></title><description><![CDATA[@Steven-Girouard Are you using PX4? ArduPilot? You could run that directly on the VOXL 2 mini depending on what your IO needs are.
]]></description><link>https://forum.modalai.com/topic/4745/flight-core-v2-to-replace-a-pixhawk-6c</link><guid isPermaLink="true">https://forum.modalai.com/topic/4745/flight-core-v2-to-replace-a-pixhawk-6c</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Tue, 16 Sep 2025 21:57:27 GMT</pubDate></item><item><title><![CDATA[barometer status]]></title><description><![CDATA[@ravi The documentation has been updated. If you are running a recent release from us then you will be using the ICP-20100 barometer. The BMP388 will not be started.
]]></description><link>https://forum.modalai.com/topic/4742/barometer-status</link><guid isPermaLink="true">https://forum.modalai.com/topic/4742/barometer-status</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Mon, 15 Sep 2025 14:38:28 GMT</pubDate></item><item><title><![CDATA[CAN support dropped?]]></title><description><![CDATA[@hula Would very much appreciate that, however, I don't see a way to send a DM to another use.  Feel free to DM me if I'm missing something or point me in the right direction here on this topic!
Very much appreciate any help!
]]></description><link>https://forum.modalai.com/topic/4671/can-support-dropped</link><guid isPermaLink="true">https://forum.modalai.com/topic/4671/can-support-dropped</guid><dc:creator><![CDATA[Ansel Misfeldt]]></dc:creator><pubDate>Tue, 12 Aug 2025 22:54:59 GMT</pubDate></item><item><title><![CDATA[UAVCAN error while building px4 firmware]]></title><description><![CDATA[@Eric-Katzfey I am using VOXL 2 to Flight Core v2 to VOXL FPV ESC, will this change affect any performance of the flight or any other abilities.
]]></description><link>https://forum.modalai.com/topic/4653/uavcan-error-while-building-px4-firmware</link><guid isPermaLink="true">https://forum.modalai.com/topic/4653/uavcan-error-while-building-px4-firmware</guid><dc:creator><![CDATA[Jetson Nano]]></dc:creator><pubDate>Wed, 06 Aug 2025 04:19:59 GMT</pubDate></item><item><title><![CDATA[VOXL2-MINI Serial Pin Mapping for Ardupilot]]></title><description><![CDATA[@TomP GPS on pins 2 and 3 is mapped to serial port 3 in ArduPilot. The RC port on pins 10 and 11 is mapped to 4. https://github.com/ArduPilot/ardupilot/blob/d977f318c68faf69b8afa9b5c1afe73932a1d946/libraries/AP_HAL_QURT/HAL_QURT_Class.cpp#L50
]]></description><link>https://forum.modalai.com/topic/4295/voxl2-mini-serial-pin-mapping-for-ardupilot</link><guid isPermaLink="true">https://forum.modalai.com/topic/4295/voxl2-mini-serial-pin-mapping-for-ardupilot</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Wed, 26 Mar 2025 21:11:56 GMT</pubDate></item><item><title><![CDATA[AUX Pins - Flight CoreV2]]></title><description><![CDATA[@Jetson-Nano It should be no different than with any other flight controller hardware running PX4. The PX4 documentation should be able to explain how to do that.
]]></description><link>https://forum.modalai.com/topic/4091/aux-pins-flight-corev2</link><guid isPermaLink="true">https://forum.modalai.com/topic/4091/aux-pins-flight-corev2</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Wed, 15 Jan 2025 13:26:11 GMT</pubDate></item><item><title><![CDATA[SBUS not detected]]></title><description><![CDATA[@Zachary-Lowell-0 Got it working.  It seems we encountered a documented bug where the defaults were somehow getting incorrectly set to the wrong parameter for RC input protocol when we reset the board to firmware defaults.  We were checking the COM_RC_IN_MODE but had always had the RC_IN set to Auto previously.  This made everything look fine until it glitched and changed the parameter without us knowing.
In case anyone else runs into it, here is the bug: https://github.com/PX4/PX4-Autopilot/issues/22986
Appreciate the assistance on figuring this out Zachary, we can switch over to Flight Cores and VOXL Flights for this client now which they'll be happy about.
]]></description><link>https://forum.modalai.com/topic/4047/sbus-not-detected</link><guid isPermaLink="true">https://forum.modalai.com/topic/4047/sbus-not-detected</guid><dc:creator><![CDATA[Ansel Misfeldt]]></dc:creator><pubDate>Thu, 19 Dec 2024 18:15:54 GMT</pubDate></item><item><title><![CDATA[No battery charge reported when using VOXL ESC FPV 4-in-1 (M0138) with FlightCoreV2]]></title><description><![CDATA[Hi Alex, I had and I still had the issue.
But once I built from https://github.com/modalai/px4-firmware/tree/voxl-fpv-dev and changed BAT1_SOURCE to power module (I originally had it set to ESC), when spinning the motors the current appeared correct and power draw updated correctly! Appreciate the help!
One interesting thing, with BAT1_SOURCE set to the ESC, when monitoring the battery_status mavlink message the current consumed and current battery values were invalid (both set to 0), I would've figured that mavlink message would still be valid irrespective of the source as its only coming from place?
Thanks
]]></description><link>https://forum.modalai.com/topic/3882/no-battery-charge-reported-when-using-voxl-esc-fpv-4-in-1-m0138-with-flightcorev2</link><guid isPermaLink="true">https://forum.modalai.com/topic/3882/no-battery-charge-reported-when-using-voxl-esc-fpv-4-in-1-m0138-with-flightcorev2</guid><dc:creator><![CDATA[Dracad]]></dc:creator><pubDate>Thu, 24 Oct 2024 03:43:11 GMT</pubDate></item><item><title><![CDATA[VOXL ESC FPV 4-in-1 (M0138) Not being detected on FlightCore start]]></title><description><![CDATA[Thanks for the reply! Good to know it was a known issue.
One thing, the links you sent point to modalai's fork of the px4 firmware, but alot of changes have been implemented in the mainline PX4 repository. I'd been building off the mainline repo, apologies if this has been answered before or is documented somewhere, is there a document that describes modal ai's release process so I can make sure im grabbing the latest iterations of code?
]]></description><link>https://forum.modalai.com/topic/3881/voxl-esc-fpv-4-in-1-m0138-not-being-detected-on-flightcore-start</link><guid isPermaLink="true">https://forum.modalai.com/topic/3881/voxl-esc-fpv-4-in-1-m0138-not-being-detected-on-flightcore-start</guid><dc:creator><![CDATA[Dracad]]></dc:creator><pubDate>Thu, 24 Oct 2024 03:26:45 GMT</pubDate></item><item><title><![CDATA[ArduPilot on Voxl2]]></title><description><![CDATA[@adiprin1 Can you please start a new forum topic for this? And please include information about the device that you are looking to attach? Thanks!
]]></description><link>https://forum.modalai.com/topic/3640/ardupilot-on-voxl2</link><guid isPermaLink="true">https://forum.modalai.com/topic/3640/ardupilot-on-voxl2</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Sat, 13 Jul 2024 04:55:19 GMT</pubDate></item><item><title><![CDATA[BMM150 Magnetometer on Flight Core V2 EOL]]></title><description><![CDATA[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!
]]></description><link>https://forum.modalai.com/topic/3564/bmm150-magnetometer-on-flight-core-v2-eol</link><guid isPermaLink="true">https://forum.modalai.com/topic/3564/bmm150-magnetometer-on-flight-core-v2-eol</guid><dc:creator><![CDATA[Vinny]]></dc:creator><pubDate>Tue, 18 Jun 2024 23:31:02 GMT</pubDate></item><item><title><![CDATA[Manual Control Lost during flight with Flight Core V2 + VOXL2 Setup]]></title><description><![CDATA[@Vinny @Moderator Thank you for the response.
The reason why we suspected a power issue is that the Flight Core PX4 logs have gaps in data. My apologies as I should have included that info initially. Here is an example from manual setpoint data.
[image: 1716303716023-6b5c0659-91f0-424d-93ae-6f5fb178bcb8-image.png]
Here is a scatterplot for throttle manual setpoint data to show that those straight lines on the line graph are indeed gaps in data and not inhumanly smooth setpoint changes.
[image: 1716303554866-bdc82181-0b10-4f33-a424-a91274f00989-image.png]
These gaps are consistent across all the data in the log, which led us to hypothesize that power was lost during these instances. We are using a custom controller that employs SBUS joystick protocol through QGC. Let me know if this info sparks any other ideas or is reminiscent of another issue.
]]></description><link>https://forum.modalai.com/topic/3458/manual-control-lost-during-flight-with-flight-core-v2-voxl2-setup</link><guid isPermaLink="true">https://forum.modalai.com/topic/3458/manual-control-lost-during-flight-with-flight-core-v2-voxl2-setup</guid><dc:creator><![CDATA[jacobcayetano1]]></dc:creator><pubDate>Mon, 20 May 2024 22:29:26 GMT</pubDate></item><item><title><![CDATA[Several modules failing during startup making controller unusable as-shipped]]></title><description><![CDATA[@Alex-Kushleyev I figured it why the orientation estimator wasn't running after reading through this post, where that user had the same (plus a few more) problems: https://forum.modalai.com/topic/1755/setup-problems-on-new-boards-sensors-and-qgc-connection-problems/18
Basically the problem is that the firmware as-shipped assumes you have at least one active mag, but that the built-in one isn't active. The documentation didn't say how to change the PX4 parameters to make it work without one. The default build does not start the built-in mag, so if you don't have an external plugged in (as in my use case), then EKF2 gets stuck while looking for the reading for one without any error printout, making it unclear what the problem is. I initially tried the version of activating it by adding the boot line to the etc folder of the sd card, and that worked once, but then it got deleted on the next reboot for unknown reasons. That is an easy enough fix with just a firmware rebuild where the magnetometer is started by default. That really is the version you should ship unless you are going to specify in your documentation that the as-shipped version will need an external mag to function. With the firmware as-is, you have to change two parameters on PX4 to make it work, specifically you have to turn off EKF2 magnetometer fusion and whether or not the system has a mag at all. Ie. EKF2_MAG_TYPE to NONE and SYS_HAS_MAG to Disabled. After doing that it will run.
Still haven't sorted out the issue with the telem lockout. I'll see if that got fixed with EKF2 now running normally.
]]></description><link>https://forum.modalai.com/topic/3425/several-modules-failing-during-startup-making-controller-unusable-as-shipped</link><guid isPermaLink="true">https://forum.modalai.com/topic/3425/several-modules-failing-during-startup-making-controller-unusable-as-shipped</guid><dc:creator><![CDATA[jcroughan]]></dc:creator><pubDate>Fri, 10 May 2024 23:36:29 GMT</pubDate></item><item><title><![CDATA[What connector would I use for a servo?]]></title><link>https://forum.modalai.com/topic/3397/what-connector-would-i-use-for-a-servo</link><guid isPermaLink="true">https://forum.modalai.com/topic/3397/what-connector-would-i-use-for-a-servo</guid><pubDate>Fri, 03 May 2024 21:14:00 GMT</pubDate></item><item><title><![CDATA[Uploading PX4 firmware on Flight Core v2 through VOXL2]]></title><description><![CDATA[@Jetson-Nano It's not something we've tried. The easiest way is to load firmware through QGC.
]]></description><link>https://forum.modalai.com/topic/3334/uploading-px4-firmware-on-flight-core-v2-through-voxl2</link><guid isPermaLink="true">https://forum.modalai.com/topic/3334/uploading-px4-firmware-on-flight-core-v2-through-voxl2</guid><dc:creator><![CDATA[tom]]></dc:creator><pubDate>Tue, 16 Apr 2024 01:49:49 GMT</pubDate></item><item><title><![CDATA[PX4 Firmware flashing - Flight Core V2]]></title><description><![CDATA[@Jetson-Nano Unfortunately not given the state of the board
]]></description><link>https://forum.modalai.com/topic/3306/px4-firmware-flashing-flight-core-v2</link><guid isPermaLink="true">https://forum.modalai.com/topic/3306/px4-firmware-flashing-flight-core-v2</guid><dc:creator><![CDATA[tom]]></dc:creator><pubDate>Tue, 09 Apr 2024 13:56:43 GMT</pubDate></item><item><title><![CDATA[Fatal Error Occurs When Enabling CONFIG_CAN: &quot;stm32_can.h: No Such File or Directory]]></title><description><![CDATA[@Will said in Fatal Error Occurs When Enabling CONFIG_CAN: "stm32_can.h: No Such File or Directory:

stm32_can.h

This has some more info: https://discuss.px4.io/t/nuttx-can-drivers-on-stm32h7x3/29828/2
]]></description><link>https://forum.modalai.com/topic/3177/fatal-error-occurs-when-enabling-config_can-stm32_can-h-no-such-file-or-directory</link><guid isPermaLink="true">https://forum.modalai.com/topic/3177/fatal-error-occurs-when-enabling-config_can-stm32_can-h-no-such-file-or-directory</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Thu, 07 Mar 2024 13:20:08 GMT</pubDate></item><item><title><![CDATA[Flight Core v2 not working with any telemetry radios]]></title><description><![CDATA[@prawinsankar , can you please clarify which firmware you are talking about?
If you are referring to PX4 and drivers for RC, you have to look at the specific driver for the RC and see how the baud rate is passed to the driver, typically as a param or launch argument when the PX4 module is loaded.
Alex
]]></description><link>https://forum.modalai.com/topic/3056/flight-core-v2-not-working-with-any-telemetry-radios</link><guid isPermaLink="true">https://forum.modalai.com/topic/3056/flight-core-v2-not-working-with-any-telemetry-radios</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Fri, 26 Jan 2024 15:43:21 GMT</pubDate></item><item><title><![CDATA[Supporting power monitor to see battery status]]></title><description><![CDATA[@Alex-Kushleyev
Yes, i believe that might be the case. There might be some other px4 firmware parameters that are causing it.
]]></description><link>https://forum.modalai.com/topic/2999/supporting-power-monitor-to-see-battery-status</link><guid isPermaLink="true">https://forum.modalai.com/topic/2999/supporting-power-monitor-to-see-battery-status</guid><dc:creator><![CDATA[skl1g14]]></dc:creator><pubDate>Wed, 10 Jan 2024 05:06:39 GMT</pubDate></item><item><title><![CDATA[Supporting Tattu Pro Battery via UAVCAN Integration]]></title><description><![CDATA[@Will Have you considered purchasing another one? They are not expensive, and might be much more worth it than your time lost to fight a non-functional USB on the MCU.
Food for thought...
Sadly, I am not one of the SW experts in our team... just HW.
Tag me anytime you have HW related questions!
Thanks!
]]></description><link>https://forum.modalai.com/topic/2982/supporting-tattu-pro-battery-via-uavcan-integration</link><guid isPermaLink="true">https://forum.modalai.com/topic/2982/supporting-tattu-pro-battery-via-uavcan-integration</guid><dc:creator><![CDATA[Vinny]]></dc:creator><pubDate>Tue, 26 Dec 2023 09:15:48 GMT</pubDate></item><item><title><![CDATA[FC2 schematic and board file]]></title><description><![CDATA[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
]]></description><link>https://forum.modalai.com/topic/2888/fc2-schematic-and-board-file</link><guid isPermaLink="true">https://forum.modalai.com/topic/2888/fc2-schematic-and-board-file</guid><dc:creator><![CDATA[Vinny]]></dc:creator><pubDate>Tue, 21 Nov 2023 08:08:48 GMT</pubDate></item></channel></rss>