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

    New VOXL2 not connecting to Windows machine that connects to Older VOXL2

    VOXL 2
    2
    7
    552
    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.
    • R
      rdjarvis
      last edited by 22 Mar 2024, 18:01

      I was previously able to connect to an older VOXL2 with my windows machine with both CMD and WSL. Just got a new VOXL2 yesterday and it is not recognized by the same windows machine.

      USB-C to USB-A

      QUSB_BULK_SN:A37F2E68

      This is the device in device manager. Is there a driver for this device?

      1 Reply Last reply Reply Quote 0
      • R
        rdjarvis
        last edited by 25 Mar 2024, 13:45

        **
        Does anyone have a driver for this?

        A 1 Reply Last reply 25 Mar 2024, 15:27 Reply Quote 0
        • A
          Alex Kushleyev ModalAI Team @rdjarvis
          last edited by 25 Mar 2024, 15:27

          @rdjarvis , please make sure you are using a proper USB3.0 cable (USB-C to USB-A) or try another cable.

          How are you testing if the device is recognized? Are you using adb to test this? On some machines you need run sudo adb in order to access VOXL2. (may need to run adb kill-server before trying sudo adb)

          R 1 Reply Last reply 25 Mar 2024, 15:43 Reply Quote 0
          • R
            rdjarvis @Alex Kushleyev
            last edited by 25 Mar 2024, 15:43

            @Alex-Kushleyev Thank you the reply.

            Yes I have the VOXL and multiple VOXL2s. I have used the same cables (USB-A-USB-C).

            Device Manager sees the QBULK (Qualcomm) device, but cant install any drivers.

            Both VOXL1 and previous VOXL2 connects without an issue.

            I have tried ADB kill-server/start-server. then adb devices. Nothing appears.

            I had the same issue with the VOXL in October and received help from the DEV team. No Luck. CHAT GPT helped and I was able to get the device recognized by adjusting the environmental variables on the Windows machine with success on VOXL and VOXL 2.

            The new VOXL2 I just received isnt popping up under adb devices, and I cant find the driver for the QBULK device.

            RDJ

            A 1 Reply Last reply 26 Mar 2024, 04:43 Reply Quote 0
            • A
              Alex Kushleyev ModalAI Team @rdjarvis
              last edited by 26 Mar 2024, 04:43

              I believe that if the device is showing up as QBULK, it boots into recovery mode. It is strange that this is happening to a brand new VOXL2. I will check about this. Have you ever tried the unbricking procedure for VOXL2? https://docs.modalai.com/voxl2-unbricking/ ?

              Before you do try it on this board, let us get back to you.

              R 1 Reply Last reply 26 Mar 2024, 14:35 Reply Quote 0
              • R
                rdjarvis @Alex Kushleyev
                last edited by 26 Mar 2024, 14:35

                @Alex-Kushleyev Thank you for the response. I have not tried unbricking.

                A 1 Reply Last reply 26 Mar 2024, 14:42 Reply Quote 0
                • A
                  Alex Kushleyev ModalAI Team @rdjarvis
                  last edited by 26 Mar 2024, 14:42

                  @rdjarvis ,

                  The board is in eDL mode (emergency download). Can you please check that SW2 is off and if the issue is persists, provide serial number of voxl2 board, we will check test records.

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