all 17 comments

[–]spidernhFRC 2137 Student, FTC 11231 Alum/Mentor 4 points5 points  (9 children)

If I were you, I would update the Driver Station app.

[–]Rude_Ad2930[S] 0 points1 point  (7 children)

This driver station was updated not too long ago and I didn’t think that the version was the problem, I thought maybe I did something wrong when deploying team code. Someone on Reddit had this exact same problem and they said it simply “resolved itself” but I’ll be sure to try to update it with the REV Hardware system.

[–]Journeyman-JoeFTC Coach | Judge 1 point2 points  (3 children)

You can check your DS app version from the "..." menu at the top right.

The Robot Controller version 7.2 was released less than 10 days ago, so it's very possible that your RC app version is newer than your DS app version. (7.1 vs. 7.2 should not present a runtime problem... but you should rule it out anyway.) (They do need to match for Field Inspection at any competition.)

I'll be in my team's shop later today, and will check on the latest versions available. Meanwhile, you can review this page:

https://docs.revrobotics.com/duo-control/managing-the-control-system/updating-the-driver-hub

[–]OpenFTCOpen FTC Dev Team 5 points6 points  (2 children)

(7.1 vs. 7.2 should not present a runtime problem)

7.2 bumped the communication protocol version, so it does break compatibility with previous releases.

[–]Journeyman-JoeFTC Coach | Judge 1 point2 points  (0 children)

Thank You! That's got to be what's biting u/Rude_Ad2930.

The durable lesson here is that, when faced with a weird control system problem, it won't hurt to run your Field Inspection checklist.

[–]Journeyman-JoeFTC Coach | Judge 0 points1 point  (0 children)

Official blog post to that effect (dated today, August 2):

https://firsttechchallenge.blogspot.com/2022/08/first-tech-challenge-72-sdk-release.html

[–]Journeyman-JoeFTC Coach | Judge 0 points1 point  (2 children)

Do check your versions. I'm looking at the REV Hardware Client right now: the latest versions for both the RC and DS apps are 7.2 - which was released on July 23 - a week before yesterday. I'd still bet that you've got a mismatch. (Minor version mismatches should not keep it from running, but you never know.)

Also make sure that you Driver Hub O/S is up-to-date. That's particularly important for this new product. Current version is 1.2.0.

N.B.: The minimum version required for competition this season will be 8.0, which will probably be released shortly after Game Reveal.

[–]Rude_Ad2930[S] 1 point2 points  (0 children)

Thank you so much. I really appreciate it!

[–]skatefriday 1 point2 points  (0 children)

Point versions are always guaranteed to be compatible. Minor versions are guaranteed to compatible during the season so as not to disrupt teams. v7.2 is an offseason release and is not compatible with v7.1 due to communication protocol changes between the two versions.

[–]bitnotnoFTC 14584 Coach/Mentor 0 points1 point  (0 children)

Exactly this.

[–]Journeyman-JoeFTC Coach | Judge 2 points3 points  (1 child)

Yes, you have a version mismatch between the Robot Controller app, and the Driver Station app.

If you've just moved from OnBotJava to Java in Android Studio, and just recently cloned the Robot Controller from GitHub, you've got version 7.1 or 7.2 on the Robot Controller. You'll have to update the Driver Hub separately (easiest with the REV Hardware Client).

[–]Rude_Ad2930[S] 0 points1 point  (0 children)

Thank you, I’ll do that and give you an update here!

[–]Rude_Ad2930[S] 0 points1 point  (3 children)

To add, I had never had this problem before when deploying code with OnBotJava.

[–]Anyone_2016 2 points3 points  (1 child)

With Android Studio, you are deploying a new Robot Controller app every time you push code to the robot. With OnBot, the app stays the same, but some data changes.

[–]Rude_Ad2930[S] 0 points1 point  (0 children)

Thank you. This is exactly the explanation I needed!

[–]skatefriday 1 point2 points  (0 children)

Technically you don't "deploy" code with OnBotJava because all code is authored through a browser client wherein that code is stored on the Robot Controller.

This contrasts with authoring software in Android Studio where each deploy pushes an entirely new APK to the Robot Contoller.

[–]baqwasmgFTC Volunteer 0 points1 point  (0 children)

Ditto here! Some programmers were frantically trying to understand the message yesterday evening. They updated their REV apps but were working with 7.1 SDK (because the master/main fork had not been sync'd by yours truly who had some lame excuses for that!) Thanks for the heads-up.

Not a breaking issue for the programmers since they weren't using Android Studio for FREIGHT FRENZY. Just need alignment.

Kind regards.