@tom Thank you so much! I was having the exact same problem with @marian. I could connect to the voxl via ssh but could not via adb shell. But could solve it after removing the /etc/udev/rules.d/51-android.rules. Try to remove the file, who are facing the same problem with me.

@Jetson-Nano Unfortunately not given the state of the board

@Jetson-Nano It's not something we've tried. The easiest way is to load firmware through QGC.

@Jetson-Nano Each host pc will be different depending on what peripherals you have plugged in. Run sudo dmesg -wH and plug in your flight core, you should see which port it enumerates on in the dmesg output

@Eric-Katzfey Thanks Eric, that makes sense!

Hey @KMillzOG , This doesn't help with your core issue, but I have had success running the ROS2 docker images on RaspiOS on a pi: https://docs.ros.org/en/foxy/How-To-Guides/Installing-on-Raspberry-Pi.html If you're comfortable running your software inside a Docker container, that'll solve your problem. Conveniently, you can also build a docker file for ARM or for X86, so you can run the same software on a more traditional PC or inside a CI pipeline. I also recently noticed that there is still an officially supported Ubuntu image for the Pi. I haven't tried it, but it might be another option. If you have a spare SD card, you could install ubuntu on the spare card, then see if that works for you. Then if it doesn't work you can just go back to the old SD card.

@JoeC Hello, all relevant files that you are looking for are included in the "3D STEP Sentinel" link provided at: https://docs.modalai.com/sentinel-functional-description/ Link directly to the download: https://storage.googleapis.com/modalai_public/modal_drawings/Sentinel_Drone_STEP.zip

@Alex-Kushleyev thank you for your response, this answers my question!

@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

Express LRS does work via the above wiring on VOXL flight after testing in Q Ground Control

What do you do if it gets stuck on "[INFO] waiting for device..."?

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

@JP-Drone VOXL Flight doesn't handle cameras any differently than VOXL so that is a bit surprising to me that it would work on one but not the other as they are they same hardware and software

@aashry Yes, definitely update the SDK first! We're many versions past SDK 0.9. Once you do, try again and let me know, I'll be happy to help. Thomas

@Moderator Thanks for your quick reply. I'm relieved to be sure. Kind regards,

@skl1g14 , very nice!! Thank you for documenting your configuration and results!!

@Alex-Kushleyev Yes, i believe that might be the case. There might be some other px4 firmware parameters that are causing it.

@Connor-Fuhrman , I am not sure. Please try to enable debug-level logging, so you may see some errors (both in your application) and voxl-streamer. In your application you can add the following : M_JournalSetLevel((M_JournalLevel) debugLevel); example: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/src/main.cpp?ref_type=heads#L301 voxl-streamer already has this option, just need a command line option : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-streamer/-/blob/master/src/main.c?ref_type=heads#L383