Flight Core

• 

  Failsafe not working properly
  • Tamas Pal 0  

  2
  0
  Votes
  2
  Posts
  15
  Views

  

  Please follow the safety guidelines before running any mission: https://modalai.com/safety The failsafe is configured in PX4 via QGC. We do not set that explicitly as that before is up to you how to configure. Please review the PX4 failsafe documentation and understand how it behaves, and then test in safe conditions, before flying again https://docs.px4.io/main/en/config/safety.html These are drones for developers, and are highly configurable. Please take precaution and test each function before making any assumptions about behavior.
• 

  Telemetry interfering with UART?
  • Andrew Keefe  

  4
  0
  Votes
  4
  Posts
  13
  Views

  

  I have discovered that the entire module seems to stop. I had been assuming it was the UART that was failing. Is there some PX4 setting where when a telemetry link occurs that something would stop/pause running modules?
• D

  Flight core integrate with a Wifi module？
  • DarkKnightCH  

  3
  0
  Votes
  3
  Posts
  38
  Views

  

  Hey the answer is yes. I use DroneBridge for ESP32 but I believe there's a ton of other similar mavlink apps for ESPs. cheers
• 

  flightcore ver2
  • jconk  

  2
  0
  Votes
  2
  Posts
  18
  Views

  

  Originally the FW update via QGC worked, and ideally that would be the way it works, but at some point the update stopped working (note that our bootloader didn't change). The px_uploader tool to me uses the same protocol as QGC, and as this works, I have a hunch the issue will be QGC side, but the jury is still out while we track it down. I decided to proceed to ship Flight Core v2 as I found the work around acceptable and had the work around publicly documented. I agree that our product line is still a bit bent towards power users at this point, so the use of git and such is a big ask for most people. If you have the chance, with respect to this topic in particular on this thread, please let me know where you got stuck with this particular process with our documentation and then I can use that feedback to improve things. https://docs.modalai.com/flight-core-v2-firmware/#how-to-upgrade-using-px_uploader-tool
• B

  Fumble fingers problem on FC
  • Bulldog357  

  6
  0
  Votes
  6
  Posts
  44
  Views

  

  Hi @billybob I just stumbled upon this thread. Thanks for contributing to this forum!! If you need us to respond to anything or have any questions, the best bet is always a new thread. We get alerted (the entire company) on new threads, but not so for thread responses or "tack-on" thread posts. Just an FYI I've been updating that cables section recently (still have more to do!!!) and we are finding and posting workaround solutions for various Mavlink ports when someone's port breaks or they wish to change for mechanical reasons. I'm happy to see you found some of my notes. We are working to improve that too, especially since the older 5V on Voxl J12 is problematic on some new stuff, so I want to be sure everyone has all the info they need!!
• 

  Microstrain 3DMGX5 Interface
  • Andrew Keefe  

  3
  0
  Votes
  3
  Posts
  22
  Views

  

  I verified the UART is working fine using the loopback method, at a few different baud rates. I think the issue is the sensor itself must be encoding the packets differently than I am reading them. I might need to reduce the baud rate down to 9600 and review the data on the oscilloscope. The Arduino's SoftwareSerial library didn't work properly until I inverted the input, but I didn't see that option for the linux UART.
• 

  Datalog Transfer via Radio
  • Andrew Keefe  

  3
  0
  Votes
  3
  Posts
  19
  Views

  

  I am connecting my RFD 900+ to the J5 connector on the Flight Core. The radio is configured for 57,600 baud. I don't have any experience setting mavlink "modes." This is an underwater vehicle, so I only communicate with it on the bench. My hope is to not have to open up the pressure vessel to pull off the data logs, which is our current method.
• T

  Dead PWM Channels
  • tangotoo  

  2
  0
  Votes
  2
  Posts
  16
  Views

  

  Hi @tangotoo , If you have a DMM handy, can you confirm you get a high resistance reading between the PWM output pins and DGND on J7 with the PCB powered OFF and disconnected from the ESCs? Pin 10 is DGND. For example, if you measure DCR on Pin-2 to GND (pin-10), you should get ~200-300KOhm. And for Pins 3-9 as well. If any of those are much lower, then that implies an ESD or overvoltage event might have damaged the pins from the STM MCU or the ESD protection devices we have creating an internal short in the MCU or on the ESD diodes on those specific bad channels. If all the readings are in that high value range for all 8 PWMS, then our SW team will have to jump in to help. Thanks!
• 

  px4 based flightcore and iPhone 14
  • Suvasis M  

  1
  0
  Votes
  1
  Posts
  18
  Views

  No one has replied

• 

  Holybro Pixhawk 5x and modalai's flight core
  • Suvasis M  

  4
  0
  Votes
  4
  Posts
  65
  Views

  

  @Vinny Thanks for more clarifications. I was comparing: https://github.com/PX4/PX4-Autopilot/blob/main/boards/holybro/pix32v5/src/board_config.h and https://github.com/PX4/PX4-Autopilot/blob/main/boards/modalai/fc-v2/src/board_config.h table comparing the hardware features I will appreciate if you can share. The Modalai flight core is tiny compared to pixhawk5x, I wanted to mix and match flight core with voxl(which is essentially snapdragon) or Nvidia Jetson processors for drones or robot. Thanks. suvasis
• 

  Issue with aftermarket PMU and UAVCAN on FW 1.11.3
  • Caleb Rievley  

  7
  0
  Votes
  7
  Posts
  73
  Views

  

  Have you asked in the px4.slack.com Slack channel? All of the developers are there and there is tons of good support. They would probably have better recommendations on how to add the driver properly than we would.
• 

  Do we need to disable internal compass?
  • Moderator  

  2
  0
  Votes
  2
  Posts
  25
  Views

  

  Flight Core does not have an internal magnetometer (compass) so there's no need!
• 

  TOF camera
  • Zeev Mindali  

  2
  0
  Votes
  2
  Posts
  21
  Views

  

  @Zeev-Mindali Checkout your options here: https://www.modalai.com/pages/rma
• 

  Flight Core USB Power
  • Andrew Keefe  

  3
  1
  Votes
  3
  Posts
  23
  Views

  

  Yes, this "can" work, but it is not ideal due to the many unknown variables on someone's host PC. Hence it is not a default option, and we would not recommend it. Issues can range from USB VBUS being out of spec (as it is, it is allowed +/- 10% which puts it in on the edge of our needs), and most "correctly designed" PCs will not provide more than 100mA unless a device is enumerated that asks for more. I'm not sure if all version of PX4 do that correctly. 100mA is insufficient for most use cases. In a strictly "QGC config" mode, I can see this work, but it is not something we plan on supporting on this version board due to those risks above. This also opens the door for someone to leave that power feed in-place while then later connecting the power module which will create a serious power rail shorting problem between the module and the PC. However, we do have a design already figured out that can take USB power for QGC/Config type of applications, and it validates the VBUS through a smart fuse/mux before using it. This will allows us to globally claim support, and if someone's system is not correct or out of range, we protect the HW. Stay tuned!
• J

  Unable to open port while calibrating ESC
  • Jimk_Aero  

  2
  0
  Votes
  2
  Posts
  20
  Views

  

  Hi @Jimk_Aero , Sorry to hear about the problems. Not being able to power off USB does make this hard and is a carry over from the VOXL Flight.... Even without ESC calibration, you can manually attempt to spin a motor, if using PWM, via this: https://dev.px4.io/master/en/middleware/modules_command.html#pwm Do you have an oscilliscope? You could probe the PWM channel output pretty easy (pins 2-5 for a quad) and see if you see any signal coming out of the board. If there's no signal, when you expect it, on a single channel, try to look at those ESD diodes right next to the connector and check for any fried parts. PX4 FW version you are running? There are two programs to handle some edge cases, px4-esc-cal-tool-v1-11.py and px4-esc-cal-tool.py
• 

  Dash board no response of QGC
  • Nathan Ni  

  3
  0
  Votes
  3
  Posts
  29
  Views

  

  @modaltb Thank you for your answer, it is true that the problem is caused by the lack of magnetic compass.
• J

  ESC Power
  • Jimk_Aero  

  2
  0
  Votes
  2
  Posts
  28
  Views

  

  @Jimk_Aero Sorry so hear that you're still having problems. The built-in BEC shouldn't be required for basic use case. Unless you're trying to power some other on-board electronics/avionics with the BEC. All you should need is the "power in" to all 4 esc's from a PDB and then signal and ground from esc's to flight core J7, via the breakout board. Modalai's breakout board was designed for PWM signals only and works well in that regard. Also check to make sure that DSHOT_CONFIG is set to "disable" Here's some notes from our board designer to clarify. The primary design intent was to be used with a distribution board for power It is actually unsafe for these types of pin headers to have exposed voltages on them We wanted to prevent some customers from accidentally installing two BEC generators on these blocks which occur all the time in other hobbyist forums/kits and customers end up damaging their BEC modules. We apologize we did not make it clearer this is just a breakout board and not a BEC distribution block.
• 

  J5 telemetry voltage tolerance
  • Adam Ehrmantraut  

  2
  0
  Votes
  2
  Posts
  16
  Views

  

  Hi Adam, By default we have J5 TELEM as matching PX4 formats, with +3.3V signaling and the +5V power. We do not recommend operating J5 or any of the 3.3V based ports at 5V signaling. There are a few things to note: The default range of the pins in the MCU spec is a max of 3.6V If you want 5V signaling, consider using J1 which is 5V signaling, but note the pinout is a different format by design using a DF13 connector instead of the JST-GH https://docs.modalai.com/flight-core-datasheets-connectors/#j1---voxl-communications-interface-connector Although the MCU claims it is 5V tolerant, there are functional configuration limitations on that tolerance that the PX4 images may include, such as internal pullups. Refer to the STM32F7 series MCU spec for details on their 5V tolerance. It is limited. If you were to run "bare-die code" (not PX4) and meet the MCU limitations, and consequently drive inputs at 5V, keep in mind your outputs are still 3.3V based, so your 5V device you are trying to talk to (if it is a CMOS input) will not register the HIGH voltage and your interface will not work. Hence overall our recommendation is to keep 3.3V specified interfaces at 3.3V. Let us know if you would like any further info. Thanks!
• 

  Taranis Q X7
  • Moderator  

  12
  0
  Votes
  12
  Posts
  60
  Views

  

  Outstanding! Thank you for following up
• 

  LiDAR not showing up via I2C on J13
  • Ansel Misfeldt  

  3
  0
  Votes
  3
  Posts
  43
  Views

  

  @modaltb Interesting, that's good to know they should be identical (what I assumed), that's why I was puzzled when it didn't seem to work. On VOXL Flight we're using port J13 and it's always worked perfectly without issue the first time we're wired up a new unit. I have not tried starting via the command line, but that's a good idea to try. My best guess is a loose connection in the wiring somewhere or a pin not making good contact on the board. If it should be working the most obviously problem is user error on our part or something not making contact properly. We ended up sending them one of our VOXL Flight units where we knew it worked perfectly each time instead of using the Flight Core because they were in a rush to get things working. Thanks for the suggestions!