You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open your web browser and browse to `<https://github.com/wpilibsuite/2024Beta>`__. Near the top right corner of the page, click "Sign In" (if the Sign-In box does not automatically appear), enter your username and password and click "Sign In". If you have two-factor authenticatio enabled you may need to complete an action on your mobile device to verify your log in attempt.
14
+
Open your web browser and browse to `<https://github.com/wpilibsuite/2025Beta>`__. Near the top right corner of the page, click "Sign In" (if the Sign-In box does not automatically appear), enter your username and password and click "Sign In". If you have two-factor authenticatio enabled you may need to complete an action on your mobile device to verify your log in attempt.
15
15
16
16
The Project Homepage
17
17
--------------------
@@ -21,7 +21,7 @@ The Project Homepage
21
21
22
22
The project homepage contains a ReadMe file. Throughout the beta, the ReadMe section may be updated with the latest information from the *FIRST* technical staff. The top ribbon contains tabs allowing you to navigate to the different sections of the project:
23
23
24
-
2. Code - The Code tab will take you to the ReadMe with Beta announcements as well as allow you to access file releases using the "Releases" section on the right hand side of the screen.
25
-
1. Issues - The Issues tab is where the bug tracker for the project is located.
26
-
4. Discussions - The Discussions tab contains a forum which will allow teams to post questions or discussions about the Beta test, software or documentation. Task reports will also be posted here.
27
-
3. Wiki - the Wiki tab will contain any documents to be distributed to Beta teams. We do not currently expect to use this but if there is any documentation that we want to restrict to Beta Teams only it will be posted here.
24
+
1. Code - The Code tab will take you to the ReadMe with Beta announcements as well as allow you to access file releases using the "Releases" section on the right hand side of the screen.
25
+
2. Issues - The Issues tab is where the bug tracker for the project is located.
26
+
3. Discussions - The Discussions tab contains a forum which will allow teams to post questions or discussions about the Beta test, software or documentation. Task reports will also be posted here.
27
+
4. Wiki - the Wiki tab will contain any documents to be distributed to Beta teams. We do not currently expect to use this but if there is any documentation that we want to restrict to Beta Teams only it will be posted here.
The purpose of Task 1 is to complete installation of the new Control System software. This task consists of 1 Objective
20
20
21
-
1. Install the necessary software for your assigned Beta Test language (LabVIEW or VSCode + plugins, NI FRC Game Tools, CTRE installer if using CANTalon SRX, REV installer if using SPARK MAX or new REV hardware)
21
+
1. Install the necessary software for your assigned Beta Test language (LabVIEW or VSCode + plugins, NI FRC Game Tools, and any vendor libraries e.g. CTRE Phoenix, REVLib, etc)
22
22
23
-
Task 2 - Basic Benchtop Test (Targeted Completion 11/6/2023)
23
+
Task 2 - Basic Benchtop Test (Targeted Completion 11/4/2024)
The purpose of Task 2 is to get the base new Control System software set up and running. This helps minimize complexity to ease debugging of any issues that do occur. In this task you will set up the development environment for your programming language, configure the roboRIO, load and debug a simple program. This Task consists of 2 Objectives:
27
27
28
28
1. Configure the roboRIO
29
29
2. Create, Build and Load Default Program
30
30
31
-
Task 3 - Port Previous Robot Code (Targeted Completion 11/20/2023)
31
+
Task 3 - Port Previous Robot Code (Targeted Completion 11/18/2024)
The purpose of Task 3 is to port the previous year's robot code with the new Control System software and bring it to full functionality. This Task consists of 2 Objectives and 1 Optional Objective:
@@ -37,12 +37,14 @@ The purpose of Task 3 is to port the previous year's robot code with the new Con
37
37
2. Wireless Operation of FRC Robot
38
38
3. (Optional) Play with robot at offseason event
39
39
40
-
Task 4 - New Code and Advanced Feature Testing (Targeted Completion 12/4/2023)
40
+
Task 4 - New Code and Advanced Feature Testing (Targeted Completion 12/6/2024)
Note: Objectives in Task 4 may be completed in any order.
44
44
45
45
The purpose of Task 4 is to write new code in order to test features and functionality of the new Control System software. While we have written up a number of ideas, please feel free to come up with your own and report on what you tried/are trying and how it went.
46
46
47
-
1. Java/C++ - SysID (currently work in progress)
47
+
1. Java: Use :doc:`Epilogue annotation logging </docs/software/telemetry/robot-telemetry-with-annotations>`
48
+
2. Java: Use the re-written :doc:`Java units library </docs/software/basic-programming/java-units>`
49
+
3. Java/C++: Utilize the new Vendor Dependency manager in Visual Studio Code
0 commit comments