Announcement

Collapse
No announcement yet.

ZTE Speed Error Messages

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

  • ZTE Speed Error Messages

    We are having some trouble with our ZTE Phone communication since the update. We have also been emailing with Modern Robotics. If anyone can please help? Thank you.

    What we know:
    *Two ZTE phones with android version 4.4.4 on them.
    *The Driver Station has Version 2.35
    * We are using MIT App Inventor
    * In App Inventor we modified version to 2.35
    * We set our Channel changer to auto, but have also tried other channels
    * We factory reset our phones and then setup again for robot game play.
    * We downloaded the latest version of MIT App Inventor on two laptops and have tried the using each software.
    * We have most up to date version of virtual box.
    * We were having trouble configuring our Robot on the phone, but suddenly it just worked. Nothing changed.
    * we used the Core Device Discovery from Modern Robotics. All modules tested great and worked well.
    * We have not send in our modules for firmware update, they are from season 2015-2016.

    Error message:
    * The message is on the Driver station phone and it says it not able to communicate with the motor controllers.
    * The Robot controller shows all is working properly.
    * The Robot controller phone also shows telemetry from our Logitech gamepad.
    * Nothing moves.

    We tried:

    * We have tried, unplugged the grouping of dc/servo controllers and just using one at a time. Nothing moves.

    We are unsure what to trouble shoot next and where to look. Any suggestions would be greatly appreciated. Thank you. Team 6027.

  • #2
    If everything works with the core device discovery module program then the problem is with the phone or the OTG USB cable from the phone to the CPDM.

    If the driver station says there's a problem communicating with controllers then it's just relaying that error message from the robot phone.

    I'd try finding a new cable from the phone to the CPDM and possibly swap your RC and DS phones to see if that changes anything.

    Comment


    • #3
      Originally posted by mlwilliams View Post
      If everything works with the core device discovery module program then the problem is with the phone or the OTG USB cable from the phone to the CPDM.

      If the driver station says there's a problem communicating with controllers then it's just relaying that error message from the robot phone.

      I'd try finding a new cable from the phone to the CPDM and possibly swap your RC and DS phones to see if that changes anything.

      Thank you. Tried with different cables to/from CPDM and nothing worked. We have also used several RC and DS. We have a few phones.

      Nothing works. We are now getting the USB Failure error again when we try to configure our robot on the robot controller.

      Comment


      • #4
        Originally posted by FTC6027 View Post
        * We are using MIT App Inventor
        * In App Inventor we modified version to 2.35
        What does it mean that "In App Inventor we modified version to 2.35"?

        If you are saying that you changed the VersionName property of the Screen1 component in the App Inventor designer, that is not going to work.

        If the driver station is version 2.35, then you need to use the version of App Inventor that automatically shows 2.35 in the VersionName property of the Screen1 component without you modifying it.

        Comment


        • #5
          Originally posted by Comrade 17 View Post
          What does it mean that "In App Inventor we modified version to 2.35"?

          If you are saying that you changed the VersionName property of the Screen1 component in the App Inventor designer, that is not going to work.

          If the driver station is version 2.35, then you need to use the version of App Inventor that automatically shows 2.35 in the VersionName property of the Screen1 component without you modifying it.

          In order to get the robot to move our programmer had to rewrite all code. It would not when we tried to open code in new version.
          We see now that another version is available but are nervous to update our version. Will we need to write the code again?
          We are still getting the USB error. It comes up at times. The PDM can see one or two motor controllers, but not all of them.
          We have swapped PDMs and it is still not working.

          Comment


          • #6
            Originally posted by FTC6027 View Post
            In order to get the robot to move our programmer had to rewrite all code. It would not when we tried to open code in new version.
            We see now that another version is available but are nervous to update our version. Will we need to write the code again?
            We are still getting the USB error. It comes up at times. The PDM can see one or two motor controllers, but not all of them.
            We have swapped PDMs and it is still not working.
            You shouldn't need to rewrite your code again. Make sure you are keeping regular backups of your projects. App Inventor has two menu items to help you download your projects to your hard disk. Click on Projects at the top of the screen.
            Export selected project (.aia) to my computer
            Export all projects

            Use these menus to download either a single project (as a .aia file) or all of your projects (as a .zip file containing a bunch of .aia files).
            Backing up is important because if you upgrade to a new version and you do have trouble (you shouldn't, but if you do), then you still have your projects.

            Regarding the USB error: Do you have a screen shot of the error that you can post here?

            Comment

            Working...
            X