RobotPy 2022 now available

Technical Python
1

We’re happy to announce the release of RobotPy for 2022!

  • WPILib 2022.2.1 libraries with most features
  • Old commands (please stop using it!) and new commands
  • All supported vendors – CTRE, NavX, PWFusion, Rev, Romi

Everything is very lightly tested, and I’ve only tested the core WPILib stuff on a roboRIO. Try it out, find a bug, file an issue on github!

The documentation and examples have not been updated yet. We would love your help doing that! Please.

Coming soon

Later this season, we will bringing back pytest support for your robot! I’ve definitely missed it, and I think I have an approach that will work (want it to come sooner? Implement #3867 for me!).

Thanks

Thanks as always to @auscompgeek and @TheTripleV for their help getting this season’s release out.

Do not post support requests on this thread

Make a new thread, it’s super easy! I subscribe to the python forum, I’ll see it or someone else will. I will not answer support requests on this thread.

8 Likes
2

Minimal announcements tonight:

  • Various documentation updates, but there’s still a lot of room for improvement!
  • @TheTripleV has added wrappers for the PhotonVision vendor library, check out those docs!
2 Likes
3

Minor update to wpilib (2022.2.1.1) tonight provides support for the Mechanism2d objects for drawing things via Networktables.

1 Like
4

If you’re using robotpy-ctre, make sure you update to 2022.0.4! Anything prior to that will crash pretty hard if you do just about anything.

5

WPILib 2022.2.1.5 had a bug where it would sometimes crash when the robot code exited. It’s fixed! Be sure to update.

6

As of pyfrc 2022.0.1, your PhysicsEngine object can accept a second argument to its constructor, and it will be an instance of your robot class. PhysicsEngine is created right after robotInit is called, so you should have access to all of your motors and such. If you run python robot.py create-physics there’s an example that includes this.

pyntcore had issues with values with string arrays, this is fixed as of pyntcore 2022.2.1.2 .

7

robotpy-cscore is now available for 2022. Thanks to @auscompgeek for doing a bunch of work on this.

3 Likes
8

I pushed some RobotPy packages that depend on WPILib 2022.3.1, which depend on a new NI image that hasn’t been released yet. Don’t upgrade RobotPy on your RoboRIO until you’ve upgraded to the (as yet unreleased) NI image, or you’ll get a very strange error.

If you do get this strange error, it is fixable – but hopefully the new NI release will be out soon. Stop by our gitter chat and we can discuss.

9

The NI image has been released, get the NI Game Tools 2022 f1 and install the latest RoboRIO image to use the latest version of RobotPy/WPILib.

Sorry about the inconvenience!

10

Those obnoxious C++ stack traces are now replaced with python stack traces as of robotpy-wpiutil 2022.3.1.1. See https://github.com/robotpy/robotpy-wpiutil/pull/34 for more details.

11

Very minor, but the link to #3867 in the post is I believe a 404 (it’s missing the “issues/” portion). Should be https://github.com/wpilibsuite/allwpilib/issues/3867

12

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.