OpModes do not appear on DS after updating RC app to v10.1

Question

OpModes do not appear on DS after updating RC app to v10.1

Closed this issue 4 months ago · 11 comments

I downloaded the RC app from here, as the REV hardware client says to do to update the RC app when using Android Studio, after loading the new app onto the control hub, I cannot see my Teleop's or Autonomous opmodes on the DS dropdown. I have made sure they are in a public class and have the @TELEOP(name="", group="") annotation. If you would like to verify this for yourself or look through my code you can find it here: https://github.com/lmcginnisno1/FTC-13917_2025

Answer 1 · 2024-09-26T00:10:56.000Z

Are you certain that you are deploying the workspace that you reference via the GitHub repo in this Issue description?

Can you provide some screenshots of your Android Studio workspace showing a successful deploy from this workspace?

If you remove the @disabled annotation from one of the pre-packaged sample OpModes does that OpMode not appear as well?

Answer 2 · 2024-09-26T00:16:39.000Z

Can see sample opMode but cannot see any of my opModes on DS

Answer 3 · 2024-09-26T00:36:47.000Z

I did a git clone of https://github.com/lmcginnisno1/FTC-13917_2025, opened it in Android Studio, deployed to my Control Hub and I see a lot of OpModes that are presumably yours.

Answer 4 · 2024-09-26T00:37:45.000Z

Do you see a teleop red, those opmodes are for tuning roadrunner not the teleop. Or any opmodes under teleop?

Answer 5 · 2024-09-26T00:40:02.000Z

Do you see a teleop red, those opmodes are for tuning roadrunner not the teleop. Or any opmodes under teleop?

Yes.

Ignore the Blocks OpModes that are obviously not yours.

Answer 6 · 2024-09-26T00:41:32.000Z

those opmodes are for tuning roadrunner not the teleop.

Also FWIW, Auto Test is yours.

@Autonomous(name = "Auto Test", group = "Auto Test")
public class AUTO_Test extends Robot_Auto {
     int m_Analysis;

Answer 7 · 2024-09-26T00:41:56.000Z

Weird, when I push the code, the only opMode I see is enable/disable dashboard.

Answer 8 · 2024-09-26T00:43:29.000Z

Also, when I downgrade to version 10(which has no issues) It changes the hub name to FTC-MYpa and I have to rescan for the expansion hub.

Answer 9 · 2024-09-26T00:48:10.000Z

If you are deploying software through Android Studio, you should not be using the REV Hardware Client to manage versions.

See https://ftc-docs.firstinspires.org/en/latest/programming_resources/tutorial_specific/android_studio/fork_and_clone_github_repository/Fork-and-Clone-From-GitHub.html#updating-your-fork-and-local-clone for a detailed writeup of how to update a fork of FtcRobotController.

Do you have any changes in your workspace that are not in the repository on GitHub?

Clone your GitHub repo into a fresh, new directory, load that workspace into Android Studio, and with no other changes, deploy that to your Control Hub.

Answer 10 · 2024-09-26T00:50:24.000Z

I will try this tomorrow afternoon, I am aware that I don't use the hardware client for RC versions, but I would need it to connect wirelessly to the robot and update the hub OS and firmware.

Answer 11 · 2024-09-26T20:03:26.000Z

Thanks for the help, when I cloned the repo into a new project it works now, not sure what the root cause is but it works now.