Team 1736 Task Reports

[gerth2]

Progress Reporting for FRC team 1736 evaluating the 2024 beta

[gerth2]

Task 1 - Install

Win 11, installing over a fully-functional 2023 install (including robotpy)

Success on 2x pc's so far.

Overall good, but two notes:

NI installer still has this option as "optional" - I checked the box, but I'm not sure if it matters

Since we're running python we're not tied into using the wpilib vsCode install.... so I'd prefer to use our own. I had to click through the warnings that said "No, don't do this!". I knew enough to know it would be OK. Forward-going.... will the vsCode for wpilib include python support?

[calcmogul]

Yes.

[gerth2]

Task 2 - RIO Config

No issues observed! Got a RIO2 freshly imaged and configured via all the same processes we've used in past years. Docs appear accurate.

One minor note I went out of order: RobotPy is able to deploy to a roboRIO even without me configuring a team number, and the driver station did not recognize the RIO existed.

I think this is a corner case specific to my setup though. I had deployed to this same RIO with the 2023 setup, and my vsCode project... maybe... cached the IP address to use?

[virtuald]

Yes, there's a file that the robotpy-installer stores the team number in, so if you ran it from the same directory it would reuse that information.

[gerth2]

Task 3: Porting

Built, re-ran unit sims, deployed. Everything is passing.

Starting from this python codebase developed over the summer with 2023. Zero changes required in core wpilib libraries.

The only thing required was commenting out pathplanner things, since these aren't yet supported.

[gerth2]

Update: This work has been tested on a real robot, no issues observed!

[gerth2]

Task 4: New Features

SysID - launches, and I can see where to put in my json file.

Docs don't look up to date yet, I'm not sure what format to provide the .json in. I do have plenty of .wpilogs from on robot though, I can go get some and smush them into json format when needed.