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

    Communication through J18

    Ask your questions right here!
    5
    23
    1649
    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.
    • Eric KatzfeyE
      Eric Katzfey ModalAI Team @Filip Slezak 0
      last edited by

      @Filip-Slezak-0 The board I am suggesting has USB and UART.

      Filip Slezak 0F 1 Reply Last reply Reply Quote 0
      • Filip Slezak 0F
        Filip Slezak 0 @Eric Katzfey
        last edited by

        @Eric-Katzfey So you're thinking switch out the boards, use the UART for the wifi dongle and communicate over USB with the microcontroller?

        Eric KatzfeyE 1 Reply Last reply Reply Quote 0
        • Eric KatzfeyE
          Eric Katzfey ModalAI Team @Filip Slezak 0
          last edited by

          @Filip-Slezak-0 No, keep using USB for the WiFi dongle and use the UART to communicate with the Teensy.

          Filip Slezak 0F 1 Reply Last reply Reply Quote 0
          • Filip Slezak 0F
            Filip Slezak 0 @Eric Katzfey
            last edited by

            @Eric-Katzfey Got it, this is getting clearer. Is it safe to use the Teensy's 3.3V pins? According to this, the Voxl2 comm pins are at 1.8V even though its GPIOs are at 3.3V https://docs.modalai.com/voxl2-linux-user-guide/#devttyhs1---b2b-connector-uart

            Eric KatzfeyE 1 Reply Last reply Reply Quote 0
            • Eric KatzfeyE
              Eric Katzfey ModalAI Team @Filip Slezak 0
              last edited by

              @Filip-Slezak-0 Yes, should be fine. We use that UART to connect with our external flight core boards that have 3.3V rx / tx.

              Filip Slezak 0F 1 Reply Last reply Reply Quote 0
              • Filip Slezak 0F
                Filip Slezak 0 @Eric Katzfey
                last edited by

                @Eric-Katzfey Thanks Eric, got it working easily after that using a classic pyserial script. Great help!

                1 Reply Last reply Reply Quote 0
                • Filip Slezak 0F
                  Filip Slezak 0
                  last edited by

                  @Eric-Katzfey Hi again, can we expose another UART port for programming on the Voxl2?

                  Filip Slezak 0F 1 Reply Last reply Reply Quote 0
                  • Filip Slezak 0F
                    Filip Slezak 0 @Filip Slezak 0
                    last edited by

                    @Filip-Slezak-0 Thinking about ttyHS2 or ttyHS3 maybe shown here https://docs.modalai.com/voxl2-linux-user-guide/#uarts

                    modaltbM 1 Reply Last reply Reply Quote 0
                    • modaltbM
                      modaltb ModalAI Team @Filip Slezak 0
                      last edited by

                      @Filip-Slezak-0 please see here: https://docs.modalai.com/voxl2-linux-user-guide/#apps-proc, we have ttySH2/ttyHS3 routed to the B2B connectors, but you need a carrier board to pick them up...

                      For example, ttyHS2 goes to our M0090 - 5G Add-On Board J9 Pins 2/3 (Tx/Rx)

                      9f1f7f3b-71fb-44c2-a032-f2bd1acb538a-image.png

                      Filip Slezak 0F 1 Reply Last reply Reply Quote 0
                      • Filip Slezak 0F
                        Filip Slezak 0 @modaltb
                        last edited by

                        @modaltb Hey, thanks for the quick reply. Unfortunately, none of these work for us since it seems exposing one port prevents us from accessing another (I also can't find a ref to buy the M0130).

                        We found a workaround by having a USB hub on the m0125 instead of going over the native uart.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Powered by NodeBB | Contributors