• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Register
  • Login
ModalAI Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
    • Register
    • Login

    Flight Core part of VOXL Flight stopped responding

    Ask your questions right here!
    3
    4
    229
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Artur
      last edited by 16 Oct 2021, 10:53

      Hello,
      I have VOXL Flight Deck with single board VOXL Flight and i encountered a problem with Flight Core part of the board. The VOXL companion computer part works well and responds to adb, but i suddenly can not access Flight Core part even if i connect it directly by usb to my computer. Also the STM32 gets really hot, so i don't know if it could be a software issue or if something gone wrong with hardware. What would You suggest to do in this situation? Is there any other way to check if Flight Core hardware is ok other than connecting with QGC?

      M 1 Reply Last reply 16 Oct 2021, 16:16 Reply Quote 0
      • M
        m4v3r @Artur
        last edited by 16 Oct 2021, 16:16

        @Artur yes, try connecting to Mission Planner. Did you change any MAV related settings?
        cheers

        Ch.B.

        1 Reply Last reply Reply Quote 0
        • M
          modaltb ModalAI Team
          last edited by 18 Oct 2021, 16:54

          Hi @Artur ,

          There's a mechanism to attempt to talk via UART from VOXL to the STM32, please see here: https://docs.modalai.com/voxl-vision-px4-nuttx-shell/

          Typically, more heat than normal could be a HW fault, where current is leaking through some "undesired" path.....

          1 Reply Last reply Reply Quote 0
          • A
            Artur
            last edited by 19 Oct 2021, 22:46

            Thank You for Your responses. Unfortunately Mission Planner doesn't see the device. I also tried via nuttx-shell, but voxl doesn't get any response from stm32, so it's probably a problem with the hardware.

            1 Reply Last reply Reply Quote 0
            1 out of 4
            • First post
              1/4
              Last post
            Powered by NodeBB | Contributors