search

FIRST-Tech-Challenge / FtcRobotController

BSD 3-Clause Clear License
851 stars 5.28k forks source link

Driver Hub at 6.2.2 gives warning when connected to FtcRobotController built from 6.2 #145

Closed alan412 closed 3 years ago

alan412 commented 3 years ago

The Driver Hub from REV is at Driver Station 6.2.2

This builds a robot controller to version 6.2

So the Driver Hub gives a warning that the two don't match. I am concerned about the students learning to ignore that warning...

Is there any way you could release a robot controller 6.2.2. (or a version of both of them that is larger)

Thanks in advance,

Alan Coach FTC #16072, Quantum Quacks

cmacfarl commented 3 years ago

This is a known issue. The mismatch is harmless from a functional perspective, but a new APK for the Driver Hub was necessary, and there was no reason to release a new robot controller, so here we sit. When v7.0 is released for Freight Frenzy this will go away.

alan412 commented 3 years ago

I would humbly suggest that not training students to ignore warning messages is a reason to release a new robot controller. But I understand that with limited resources that might not be enough of a reason.

AlecHub commented 3 years ago

As a workaround, try setting android:versionName="6.2.2" in AndroidManifest.xml and then rebuild FtcRobotController.apk

alan412 commented 3 years ago

@AlecHub - Thanks but since we only have one driver hub then we'll have the same problem when a regular driver station tries to connect to our robot controller since we can't rebuild the driver station.... (except that will be 6.2 trying to connect to 6.2.2)

AlecHub commented 3 years ago

I suggest that Version X.Y.Z1 of RC/DS/DH be compatible with Version X.Y.Z2 of RC/DS/DH, and vice-versa, by design. No version mismatch warnings should be displayed if first two numbers (X.Y) of the versions match.

cmacfarl commented 3 years ago

@AlecHub I agree and thought about that as I composed my initial response. Filter version mismatch by major.minor, disregard point releases. We'll put it on the list to discuss with the tech team.

alan412 commented 3 years ago

@AlecHub That sounds like a great suggestion that would solve the problem in the future.

NoahAndrews commented 3 years ago

7.0 is out now, and implements @AlecHub's suggestion.