Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

  1. ModalAI Support Forum
  2. General Questions
  3. VOXL2 Wifi+Doodle

VOXL2 Wifi+Doodle

Scheduled Pinned Locked Moved Unsolved General Questions
5 Posts 3 Posters 840 Views 2 Watching
  • 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.
  • C Offline
    C Offline
    ctitus
    Contributor
    wrote on last edited by
    #1

    Hi,

    I'm using the VOXL2 with the VOXL 2 Ethernet and USB Hub Add-on board, and I have wifi on the USB3 port (J11), a doodle radio on the USB2 port (J12), and keep the ethernet port open for hardwiring with an ethernet cable (J13). My problem is when I use the voxl-configure-modem command to set the static ip for the doodle, I cannot ping it. It works just fine using the USB3 UART Add-On, and I think this is because that board only exposes eth0. However, the Ethernet and USB Hub Add-on board has both eth0 and eth1. If I run ip addr add 10.223.1.101/16 dev eth1, I am able to ping the doodle and it works just fine.

    My question is what is the intended method (if any) to essentially run voxl-configure-modem such that it configures everything for eth1 instead of eth0? If there is no way to do that, how would you recommend I persist a static ip on eth1 though reboots?

    tomT VinnyV 2 Replies Last reply
    0
    • C ctitus

      Hi,

      I'm using the VOXL2 with the VOXL 2 Ethernet and USB Hub Add-on board, and I have wifi on the USB3 port (J11), a doodle radio on the USB2 port (J12), and keep the ethernet port open for hardwiring with an ethernet cable (J13). My problem is when I use the voxl-configure-modem command to set the static ip for the doodle, I cannot ping it. It works just fine using the USB3 UART Add-On, and I think this is because that board only exposes eth0. However, the Ethernet and USB Hub Add-on board has both eth0 and eth1. If I run ip addr add 10.223.1.101/16 dev eth1, I am able to ping the doodle and it works just fine.

      My question is what is the intended method (if any) to essentially run voxl-configure-modem such that it configures everything for eth1 instead of eth0? If there is no way to do that, how would you recommend I persist a static ip on eth1 though reboots?

      tomT Offline
      tomT Offline
      tom
      admin
      wrote on last edited by tom
      #2

      @ctitus The voxl-modem-start script which gets run on boot after running voxl-configure-modem is hard-coded to eth0 but it is just a simple bash script that you can modify if you'd like to fit your use-case.

      The script itself lives at /usr/bin/voxl-modem-start

      This is the area you would want to modify:

      https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start?ref_type=heads#L86-111

      1 Reply Last reply
      0
      • C ctitus

        Hi,

        I'm using the VOXL2 with the VOXL 2 Ethernet and USB Hub Add-on board, and I have wifi on the USB3 port (J11), a doodle radio on the USB2 port (J12), and keep the ethernet port open for hardwiring with an ethernet cable (J13). My problem is when I use the voxl-configure-modem command to set the static ip for the doodle, I cannot ping it. It works just fine using the USB3 UART Add-On, and I think this is because that board only exposes eth0. However, the Ethernet and USB Hub Add-on board has both eth0 and eth1. If I run ip addr add 10.223.1.101/16 dev eth1, I am able to ping the doodle and it works just fine.

        My question is what is the intended method (if any) to essentially run voxl-configure-modem such that it configures everything for eth1 instead of eth0? If there is no way to do that, how would you recommend I persist a static ip on eth1 though reboots?

        VinnyV Offline
        VinnyV Offline
        Vinny
        ModalAI Team
        wrote on last edited by
        #3

        Hi @ctitus
        M0062 USB2 ports are not current-capable of powering a Doodle Radio at full specs. They are only 1A.
        https://docs.modalai.com/m0062/#details

        Doodle requires 2A support, which can only come from our 10-pin format USB ports on M0130.
        This table does not include M0062 since it was never intended to be a production product (so I need to update that table):
        https://docs.modalai.com/expansion-design-guide/#usb-expansion-over-j3--j5

        You should certainly get basic stuff working, but you will not achieve Doodle published ranges and output powers on any board we have other than M0130 or M0078: https://docs.modalai.com/usb-epxansion-with-fastboot-v2-datasheet/

        C 1 Reply Last reply
        0
        • VinnyV Vinny

          Hi @ctitus
          M0062 USB2 ports are not current-capable of powering a Doodle Radio at full specs. They are only 1A.
          https://docs.modalai.com/m0062/#details

          Doodle requires 2A support, which can only come from our 10-pin format USB ports on M0130.
          This table does not include M0062 since it was never intended to be a production product (so I need to update that table):
          https://docs.modalai.com/expansion-design-guide/#usb-expansion-over-j3--j5

          You should certainly get basic stuff working, but you will not achieve Doodle published ranges and output powers on any board we have other than M0130 or M0078: https://docs.modalai.com/usb-epxansion-with-fastboot-v2-datasheet/

          C Offline
          C Offline
          ctitus
          Contributor
          wrote on last edited by
          #4

          @Vinny @tom Thanks for all the help. I have the doodle powered on a different bus, I just have the signal going to the J12. And modifying the voxl-configure-modem script worked for me, I now have custom IPs on eth1 like I wanted.

          VinnyV 1 Reply Last reply
          0
          • C ctitus

            @Vinny @tom Thanks for all the help. I have the doodle powered on a different bus, I just have the signal going to the J12. And modifying the voxl-configure-modem script worked for me, I now have custom IPs on eth1 like I wanted.

            VinnyV Offline
            VinnyV Offline
            Vinny
            ModalAI Team
            wrote on last edited by
            #5

            Hi @ctitus
            OK great! I am glad you picked that detail up!
            M0062 was a rather early design that we almost stopped making, so we never documented it nicely. But, there is so much demand for an RJ-45 that we decided to make a few more 🙂

            1 Reply Last reply
            0

            Reading along? Create a free ModalAI Forum account to join in.

            With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.

            Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.

            Register Login
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            ModalAI
            Categories Recent Tags ModalAI.com Docs
            © 2026 ModalAI® · Accelerating autonomy for smaller, smarter, safer drones · Powered by NodeBB
            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups