Configuration scan not recognizing core legacy module

[FTC8133]

We're having trouble with the Robot Controller configuration scan recognizing our core legacy module. The servo controllers and motor controllers are recognized without issue, but the core legacy module doesn't show up no matter how many scans we do, even if we use the same ports and the same USB cables that were successful for the servo/motor controllers.


We have downloaded and installed the most recent SDK and Driver Station app. That didn't appear to make a difference.

Jeff
8133

[Alec]

First, do a DOA test on the Core Legacy module. One way to do a DOA test on a MR core module is to connect it to a Windows 7+ system. If you can get the USB serial number of the core module per this method, then the core module is likely not DOA.

[Tom Eng]

First, do a DOA test on the Core Legacy module. One way to do a DOA test on a MR core module is to connect it to a Windows 7+ system. If you can get the USB serial number of the core module per this method, then the core module is likely not DOA.

Alec,

Thanks for the suggestion - great idea.

Tom

[FTC8133]

Alec,

Thanks for that suggestion. I followed the steps and it doesn't look like it's DOA, since I got a serial number (AL00XQHM).

Anything else from you or Tom as far as a next step?

Jeff

[Tom Eng]

Alec,

Thanks for that suggestion. I followed the steps and it doesn't look like it's DOA, since I got a serial number (AL00XQHM).

Anything else from you or Tom as far as a next step?

Jeff

Hi Jeff,

Just to double check, are you connecting to the Legacy Module through the Power Distribution module?

If so, here's what I recommend trying. Turn off the Power Distribution module and disconnect the USB adapter that connects the Robot Controller phone to the Power Module. Swipe close the FTC Robot Controller app. Wait a few seconds, then power on the Power Distribution module so that the attached modules (I assume the motor controller, servo controller and legacy module) have power. Then connect the phone to the USB adapter and watch the screen.

When the devices are detected by the Android phone it should auto-launch the FTC Robot Controller app. Be on the lookout for any dialog boxes that prompt you if it is OK launch this app (the robot controller app) for the hardware device that was detected. If you see this prompt you want to make sure the checkbox is checked (so that it will associate the app with this hardware) and hit OK.

Sometimes what happens is that one of your hardware modules (such as the legacy module) does not have the FTC Robot Controller app associated as its default app. If this is the case, you might not be able to reliably detect the module when the robot controller is scanning for modules because there might be a hidden prompt (obscured by the main activity of the robot controller app) asking if you want to associate this module with the app.

Please make sure that all of your hardware modules are associated with the FTC Robot Controller app.

Also (and this is important for App Inventor users especially) you should only have one FTC Robot Controller app installed on a device. If you have more than one robot controller type of app (for example, if you create multiple using the App Inventor) then the android device might associate some hardware modules with one app, and other hardware modules with another app.

If you are still in a pickle and unable to get the module recognized, then you might want to try the following... unplug the phone from the USB connection to the power module. Swipe closed the FTC Robot Controller app. Go to the Settings activity of your Android device and launch the Apps activity and look for the FTC Robot Controller app. open the App Info activity for the FTC Robot Controller app and you can clear the defaults associated with this app by pushing the "Clear defaults" button under the Launch by Default category. If you clear the defaults associated with the app, then the next time you plug in your phone to the power module, you should be challenged with prompts for each of the detected hardware device. You want to associate the FTC Robot Controller app as the default app for any of the detected Modern Robotics Hardware Modules.

I hope this info helps. Please let us know if you're able to make progress with this issue.

Tom

[skatefriday]

Alec,

Thanks for that suggestion. I followed the steps and it doesn't look like it's DOA, since I got a serial number (AL00XQHM).

Anything else from you or Tom as far as a next step?

Jeff

This probably isn't the problem you are having but last weekend
we had 2 motor controllers sitting on a PDU and could not get the
Robot Controller to recognize the second one.

Eventually we swapped out the battery and, bingo, the second
controller appeared. When we put the swapped out battery back
on our charger to which we have one of these hooked up

http://www.adafruit.com/products/460?gclid=CIqIkdD6nsgCFUSRfgod_noEpw

it read 12.4 volts. So it appears even a moderately
discharged battery can create usb scan problems.

[Tom Eng]

This probably isn't the problem you are having but last weekend
we had 2 motor controllers sitting on a PDU and could not get the
Robot Controller to recognize the second one.

Eventually we swapped out the battery and, bingo, the second
controller appeared. When we put the swapped out battery back
on our charger to which we have one of these hooked up

http://www.adafruit.com/products/460?gclid=CIqIkdD6nsgCFUSRfgod_noEpw

it read 12.4 volts. So it appears even a moderately
discharged battery can create usb scan problems.

Skatefriday - very good point.

We have also noticed in our pilot testing and stress testing and demos that if the voltage falls too much on the 12V main battery, you can sometimes have problems detecting modules.

Tom

[Alec]

This probably isn't the problem you are having but last weekend
we had 2 motor controllers sitting on a PDU and could not get the
Robot Controller to recognize the second one.

Eventually we swapped out the battery and, bingo, the second
controller appeared. When we put the swapped out battery back
on our charger to which we have one of these hooked up

http://www.adafruit.com/products/460?gclid=CIqIkdD6nsgCFUSRfgod_noEpw

it read 12.4 volts. So it appears even a moderately
discharged battery can create usb scan problems.

Skatefriday - very good point.

We have also noticed in our pilot testing and stress testing and demos that if the voltage falls too much on the 12V main battery, you can sometimes have problems detecting modules.

Tom

However, the Power Module has a voltage regulator, so running it at 12V (or even 9V) shouldn't be a problem:

I think you can power the Legacy Module using the 9.6V battery - it just has a smaller capacity than the 12V battery. The Modern Robotics Power Module has a voltage regulator that can accept either the 9.6V or 12V battery (according to Modern Robotics). This means you should be able to drive your legacy module (which is powered by a 5V USB port) via the 9.6V battery.

[...]

Tom

Modern Robotics, please comment.

[FTC8133]

Thanks for the continued advice. No luck so far. Here's what I've done:

1. Cleared all defaults and plugged the phone in. I got five prompts, which I assume were for (1) Power Distribution, (2) Core Motor 1, (3) Core Motor 2, (4), Core Servo, and (5) Core Legacy, in some order. I checked the box on all five prompts. Upon scanning, only the Core Motors and Core Servo came up.

2. I tried the same process with only the Core Legacy plugged in (thinking maybe the other three were drawing resources). Cleared the defaults, plugged the phone in, got two prompts, and checked both. Upon scanning, got the feedback "No devices found."

3. Tried a brand new battery, fully charged, and repeated the first step. The scan recognized only the Core Motors and Core Servo.

I will throw out one other variable I have noticed while working this problem that may or may not help. When I throw the power on, half of the time all Core hardware will light up: blue for the Power Distribution and red for the other four. However, the other half of the time, the Core Legacy module doesn't light. If I plug the phone in, then it lights. Makes me think something is wrong with the circuitry. Thoughts?

Jeff

[Tom Eng]

Alec,

Thanks for that suggestion. I followed the steps and it doesn't look like it's DOA, since I got a serial number (AL00XQHM).

Anything else from you or Tom as far as a next step?

Jeff

Hi Jeff,

Did you also try the DOA test through the power module (where the legacy module.is connected to the power module and the power module is connected to the Windows comouter?

Also regarding what we've seen with the 12v battery and a low voltage.... I should clarify that in our.pilot tests and demos we ran the bots for several hours on a freshly charged 12V. We didn't see any issues until after we ran our bit's for a long time (at least a few hours of constant driving). They would last at least half a day of continously k9 bot use without issues and we would switch out or recharge the batteries when the voltage got low (around 12V).

The power modules do have regulators built in but I suspect the DC motors can draw a lot if current and if your voltage is low, you.might occasionally see issues

Tom

[FTC8133]

I had previously only tried connecting the legacy module directly. Just now I tried connecting it to the computer through the power module and it passed the DOA test. My computer was able to identify the serial number of the legacy module.

Jeff

[FTC7665]

I am having a similar problem. My core servo controller, core motor controller, and core device interface are all found by the robot control app on the ZTE, no problems. I can even control the motors and servos via the x-box controller, and read distance and touch sensors via the device interface. I cannot get the ZTE to find the core legacy module. I've tried all the above suggestions. When I connect the legacy module directly to the pc, I can get a serial number. However, once in a while, I catch an error on the ZTE that it cannot connect to legacy module serial #AL00XQXP. I've also tried connecting to the legacy module using the Modern Robotics core device discovery utility. It returns the serial number, but says it cannot connect. I'm wondering if my legacy module has a problem. Is there anything else I can try doing and/or if not, how do I get a replacement legacy module.

Thanks,
Rob
Mentor, team 7665