Announcement

Collapse
No announcement yet.

No OpModes appear on DC

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

  • #16
    Originally posted by Philbot View Post
    What type of phone and computer do you have?
    Phones: ZTE Speed (N9130), factory reset, prepared as on https://www.youtube.com/watch?v=n597U6rcl2Y
    Computer: ASUS X556U, dual booting Windows 10 Home and Linux Mint 18. All attempts to get opmode done on Windows except as noted.

    Comment


    • #17
      Originally posted by Philbot View Post
      I can give specific directions [for accessing logs] knowing this...
      Phil.
      Thanks, Phil. I found instructions for doing that at https://drive.google.com/file/d/0B0z...pFSWpILW8/view and will give that a try tomorrow.

      Comment


      • #18
        Originally posted by Philbot View Post
        I would love to see the log generated when you do the Reproducible behaviour you have listed.
        Got the Driver and Controller logs off the Driver phone. Driver log has no occurrences of “opmode”. Controller log has many, of the following 3 general types:

        10-14 10:19:48.383 7201 7201 D OpmodeRegistration: registered {DefaultOpMode} as {$Stop$Robot$}
        10-14 10:19:53.603 7201 7269 V RobotCore: thread: 'opmode loop()' starting...
        10-14 10:20:26.383 7201 7444 V RobotCore: thread: ...terminating 'opmode loop()'

        Looks like the opmode added in Teamcode "MyOpmode" is not getting registered. Yes, I commented out the annotation @Disabled in the Teamcode. Full logs available on request (they're big).

        Comment


        • #19
          Originally posted by jrasor View Post
          Looks like the opmode added in Teamcode "MyOpmode" is not getting registered. Yes, I commented out the annotation @Disabled in the Teamcode. Full logs available on request (they're big).
          OK, so there seems like only two things to do at this point:

          1) Verify that you are in fact running your latest code.
          This is an easy test... start the RC app, and then use the three dots menu to select "about".
          Check the "App Build Time" and see if it matches the last time you built and downloaded the app.

          2) If the build time is OK, then we need to see your project....
          Can you zip up the project and upload it somewhere (google drive, dropbox etc).
          I'll grab it and build the project myself. It will be big, but may as well get the whole thing....

          Phil.

          Comment


          • #20
            Originally posted by Philbot View Post
            OK, so there seems like only two things to do at this point:

            1) Verify that you are in fact running your latest code...
            2) If the build time is OK, then we need to see your project...
            Big fat operator error. I was putting the apps on the wrong phones. Gory details:

            Developing on Linux. Looked through older logs on the Driver phone. MyOpmode was registered 4 times on 10/14, never again. No log from 10/13 is available; on that date the opmode ran correctly the first time.

            Uninstall all FTC stuff from both phones. Install Driver app on Driver phone from GitHub. Build FTC SDK 2.35 on Controller phone. Run Driver app on Driver phone. Takes a few seconds to pair with Controller phone. When it does, it offers and runs MyOpmode.

            Finally.

            Restart both phones. MyOpmode runs.
            Uninstall all FTC stuff again, re-install Driver APK on Drive phone, rebuild Controller APK on Controller phone. MyOpmode runs.

            It had to be something stupid.

            The takeaway: build FTC SDK on Controller phone, not the Driver phone. Install Driver app on the Driver phone, not the Controller phone.
            Studio on Windows. Uninstall all FTC stuff from both phones. Re-install and rebuild as above on the proper phones: MyOpmode runs.

            Comment


            • #21
              Originally posted by jrasor View Post
              The takeaway: build FTC SDK on Controller phone, not the Driver phone.
              Take heart in knowing you are not the first to make this simple mistake!
              I have had a number of kids make this same mistake multiple times. The first time I remind them which phone we load to & how the wi-fi direct works. If they make the same mistake a 2nd time, it is up to them to figure it out - even if it takes the whole meeting. It doesn't happen a 3rd time. ;-)

              Comment

              Working...
              X