Announcement

Collapse

Technology Forum Has Moved!

The FIRST Tech Challenge Technology forum has moved to a new location! Please take a look at our forum blog for links and instructions on how to access the new forum.

The official blog of the FIRST Tech Challenge - a STEM robotics programs for students grades 7-12.


Note that volunteers (except for FTA/WTA/CSA will still access their role specific forum through this site. The blog also outlines how to access the volunteer forums.
See more
See less

RC app does not scan for USB devices

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Thank you Phil. We used your advice to get to our system working again. We had to close and restart the robot controller app quite a few times to get the black dialog screens to come up. Once we finally had one for each controller on the robot we were able to scan and complete the config.

    Comment


    • #17
      Originally posted by mschueren View Post
      I have found that using the Core Device Discovery utility from Modern Robotics (Link) is a good way to check hardware. You can see if the modules are powered up correctly and run any of the devices through the interface. Last season, if we had module recognition issues, we would use it to get all the core modules to a good state and then plug in the phone. If you think a module may be bad, this is the best way to troubleshoot it short of sending it back to MR.
      Great idea. I will test the "bad" MC and see what happens.

      Comment


      • #18
        Originally posted by JoanneB View Post
        Thank you Phil. We used your advice to get to our system working again. We had to close and restart the robot controller app quite a few times to get the black dialog screens to come up. Once we finally had one for each controller on the robot we were able to scan and complete the config.
        I have posted videos on how I get a fresh App install to "connect" to the devices for the first time.

        This approach works 99% of the time for me, with an easy re-do if things hickup.

        ZTE - https://www.youtube.com/watch?v=xQJsADvNH_k

        Moto G - https://www.youtube.com/watch?v=o1weHW2N-58

        Phil.

        Comment


        • #19
          In our case, we can't see the dialog boxes come up at all.

          Team 8369

          Comment


          • #20
            Originally posted by FTC8369 View Post
            In our case, we can't see the dialog boxes come up at all.

            Team 8369
            They only do it when you FIRST install the app.

            If you start with the app NOT running, plug in the usb cable, and then turn ON the 12V, the app should start up.
            If it does not, then you have a USB/Module hardware problem.

            So you have 4 blue lights ON your PDM?

            Comment


            • #21
              I have 4 lights on the PDM. I was able to see dialog boxes for each controller as I plugged them in, and I clicked the boxes for each one. When I run the configuration, the robot controller phone only finds one device at a time. It will find all of the devices individually, but not together, and not more than 1 device at a time.

              Comment


              • #22
                Originally posted by FTC8369 View Post
                I have 4 lights on the PDM. I was able to see dialog boxes for each controller as I plugged them in, and I clicked the boxes for each one. When I run the configuration, the robot controller phone only finds one device at a time. It will find all of the devices individually, but not together, and not more than 1 device at a time.
                What phone/Android version are you using. This sounds like the known Android 5.x problem.

                Comment

                Working...
                X
                😀
                🥰
                🤢
                😎
                😡
                👍
                👎