Announcement

Collapse
No announcement yet.

"AL00YDKG is not a Modern Robotics USB Legacy Module" error

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

  • "AL00YDKG is not a Modern Robotics USB Legacy Module" error

    Hello all,

    Apologies in advance for clogging up the forum with obscure error threads, but we're still struggling to make our robot start rolling and we've had the parts for a while. To be fair, we were running this App Inventor program without a gamepad connected to the Driver Station phone, but it seems very confusing that we'd get this error. We're assuming AL00YDKG is the Legacy Module?

    Code:
    10-30 15:05:16.703: V/RobotCore(22265): Sending peer discovery packet
    10-30 15:05:17.373: E/FIRST(22265): ### ERROR: System Telemetry event: SYSTEM_TELEMETRY: Unable to open Modern Robotics USB Legacy Module
    10-30 15:05:17.373: E/FIRST(22265): AL00YDKG is not a Modern Robotics USB Legacy Module
    : W/UNKNOWN_FORMAT(): 10-30 15:05:17.373 E/FIRST   (22265):
    Thanks all,
    GHS Robotics

  • #2
    GHS Robotics,

    If you have a recent windows machine, you can download the Core Device Discovery program

    (see
    http://www.modernroboticsinc.com/coredevicediscovery
    ),

    power up your robot, and plug the windows machine in via USB to the PDM. IMPORTANT - make sure the device drivers mentioned on that page are installed. Then you can see what the internal serial numbers are of the Modern Robotics controllers attached to the PDM.

    It _may_ be that somehow there is an error in the robot's configuration .xml file. Re-scanning, editing, saving, and activating the configuration file may help.

    We here have taken to labeling each MR controller with its internal serial number.

    The adventurous can use
    Code:
    adb pull /sdcard/FIRST/<configfilename>
    to pull the config xml file to your PC / Mac / whatever. It can be edited there, and sent back again using
    Code:
    adb push /sdcard/FIRST/<configfilename>
    so if your robot's config file is called "test.xml"
    Code:
    adb pull /sdcard/FIRST/test.xml
    should do the trick. This assumes that adb is in your "path", or you are in the directory on your development machine where adb lives (and you probably don't want to leave the xml files around in that directory).

    Martin Haeberli
    Mentor, FTC 7593 TigerBots

    Comment


    • #3
      Originally posted by mhaeberli View Post
      GHS Robotics,
      This assumes that adb is in your "path", or you are in the directory on your development machine where adb lives (and you probably don't want to leave the xml files around in that directory).
      ADB can also be used from Android Studio's Terminal Window. CD (change directory) can be used to place the files where they need to be.

      Comment

      Working...
      X