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

    Microhard support

    VOXL 2
    3
    19
    419
    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.
    • VinnyV
      Vinny Dev Team @McMason
      last edited by

      @McMason great this can help. I was stuck today with assembly work and missed this so I'll try to review it this weekend and get you my thoughts and/or further questions by Monday!
      Thanks!

      1 Reply Last reply Reply Quote 0
      • M
        McMason
        last edited by

        Thanks @Vinny i appreciate the help and support.

        VinnyV 1 Reply Last reply Reply Quote 0
        • VinnyV
          Vinny Dev Team @McMason
          last edited by

          Hi @McMason
          Looking at your diagram, I do have a couple comments and info now that this is made much clearer for us. I also understand your original questions now too.

          First, the sales pitch.... I think you can consider FlightCoreV2 instead of the pixcube for flight control. We are much much smaller than anything I see in a quick search for "pixcube flight controller" and cheaper too... plus NDAA complaint. Not sure if that matters to you or not, but something to ponder. We support CANBUS on FCv2 and several UART ports, which based on your diagram, is all that is needed.

          So, few points, in random order (and some may feed back into each other as I think of them, so apologies for the poor flow of my writing):

          I see you are thinking about Voxl2 as an image processing unit, which is a smart plan, but I am not sure what images you are trying to process??? Is it from the NV gimbal, or other sensors not shown?

          We have worked with Nextvison Gimbals a few years ago, so maybe our SW team can chime in if support for that would be best from the FC or the companion computer. If you are really just focused on stable flight and attitude control from the FC, moving any kind of imagery the companion computer is a logical choice. It seems as if you are trying to pump the video feed right into the MH radio using ETH.

          Note: Our MH modules do not expose the Ethernet ports of the MH modules, only USB.

          If you want to pump the video from the NextVision gimbal into a companion computer for processing, we work best with raw data using MIPI, but USB could be an option. We do not have an HDMI input, which we have had to try before on the "DragonEye" module from NextVision, and it was not the smoothest. My PC is having a hard time accessing the NV website for some reason (claims destination issues), so I am not sure if DragonEye2, is still (or only) HDMI as an option. Is ETH an option? If so, we do have some designs with ETH, but they are not mainstream. We could possibly bring them to market if the business case was there. That's a conversation you'd have to have with Chad. For now, we kept ETH mostly as internal since most folks do not need/want it.

          We are almost about to announce our own NDAA WiFi module soon... so stay tuned to that... give us a month or so and we may have our first beta units ready. Keep in mind though WiFi + MH at 2450 will likely collide with each other at the 2.4G ISM band... make sure you get familiar with disabling one or the other and turning them back on from the scripts. I know our Dev Team member Tom has many forum posts/responses on related topics like that.

          So, when it comes to our MH radios, and our 4G/5G modems, they all operate over USB in our architecture. We have options for plug-in directly to Voxl2 through the B2B connectors, or we have stand-alone options as well, which just required an independent 5V supply and a link to one of our USB ports from the 60-pin B2B connector on Voxl2 (J3).
          We have a USB + UART board that can allow you the freedom to connect standalone Modem or Radio boards, and keep a UART link which might be mappable to Mavlink messaging. SW will need to chime in. I'll tag our teams internally to respond to this to make sure I am not sending you down the wrong path.
          Here is the USB + UART debug board:
          https://www.modalai.com/products/m0125?variant=40740708876339
          Here is our MH radio, (it's an older image as we now have a connector instead of bare wires) with a connector cable option to with tinned leads:
          https://www.modalai.com/products/mh-sa
          Included In Kit
          External power supply cable (MCBL-00017-1) used to connect to external 5VDC power supply
          https://docs.modalai.com/cable-datasheets/#mcbl-00017

          Note, if you decide to get a MH plug-in board for Voxl2 (as opposed to the Standalone variant link I posted above), it does not have a mating 120-pin connector (the MH design pre-dated Voxl2) so we would ask you to place Kapton tape on the 120-pin J5 of Voxl2 to prevent any possible shorting to components on the bottom of the MH board.

          I'll ask our PX4 experts to review this thread too and respond if I mis-stated anything (I am hardware, so not always sure the way this SW all works together).

          Let us know if that helps bring more clarity (or more confusion... haha) to your scenarios you are trying to figure out.

          1 Reply Last reply Reply Quote 0
          • M
            McMason
            last edited by

            Hi @Vinny, thank you for that. In the future we will look to going strictly VOXL2 or related. Right now we only have the time to integrate into an OEM that utilizes the above.

            The DragonEye2 has ETH and a couple of com ports which right now its eth up to the MH, and serial to the FC.

            Ill look into the USB side from NV.

            1 Reply Last reply Reply Quote 0
            • M
              McMason
              last edited by

              ef6f4d37-43ef-4379-b439-0fe502a8728b-image.png

              1 Reply Last reply Reply Quote 0
              • M
                McMason
                last edited by

                Ive been scouring some px4/ardupilot libs and found a few. this one gave me a little hope haha
                https://ardupilot.org/dev/docs/mavlink-routing-in-ardupilot.html

                VinnyV 1 Reply Last reply Reply Quote 0
                • VinnyV
                  Vinny Dev Team @McMason
                  last edited by

                  @McMason Keep us posted and let us know what you find out.
                  I asked one of our team experts to review this thread for me, so hopefully he'll respond with any news too.
                  To check the USB side of things, you can experiment with this cable:
                  https://docs.modalai.com/cable-datasheets/#mcbl-00009
                  Might need a straight pass from our Type-A to the NV Type-A, but worth a shot.

                  1 Reply Last reply Reply Quote 0
                  • M
                    McMason
                    last edited by

                    Also of mention, the other aspect of the vehicle would be tracking the object after detection

                    1 Reply Last reply Reply Quote 0
                    • M
                      McMason
                      last edited by

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • M
                        McMason
                        last edited by

                        HI @Vinny just poking to see if any of your team had any more ideas? Ill be integrating stuff next week.

                        VinnyV 1 Reply Last reply Reply Quote 0
                        • VinnyV
                          Vinny Dev Team @McMason
                          last edited by

                          @McMason Sorry, I know they are swamped too. Trying my best to help them out, but I am not SW, so the best bet is to get familiar with any and all PX4 docs that you can and if you have any issues integrating, then please start a new thread with specific issues/roadblocks you encounter. That will tag the whole team and maybe you can get new responses that way.
                          The more "generic" the forum question, it's harder for a good easy response. The more specific, the easier it is and our team usually can provide answers very fast that way.

                          1 Reply Last reply Reply Quote 0
                          • M
                            McMason
                            last edited by

                            @Vinny thank you, ill be working through it this week. I appreciate your help!

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