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
Copy file name to clipboardExpand all lines: .github/dependabot.yml
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -10,8 +10,10 @@ updates:
10
10
- package-ecosystem: "github-actions"
11
11
# Workflow files stored in the default location of `.github/workflows`. (You don't need to specify `/.github/workflows` for `directory`. You can use `directory: "/"`.)
(Driver Station and associated tools), and the [2025 CTRE Phoenix Tuner X](
35
+
https://v6.docs.ctr-electronics.com/en/stable/docs/tuner/index.html). Take a
36
+
moment to update all software and firmware before attempting to load your new
37
+
robot project.
38
+
39
+
Please note that you need these _minimum_ versions of the following components:
40
+
41
+
* WPILib `2025.1.1`
42
+
* RoboRIO image `FRC_roboRIO_2025_v2.0`
28
43
29
-
**The Az-RBSI requires the 2025 WPILib Installer (VSCode and associated tools),
30
-
2025 firmware installed on all hardware (motors, encoders, power distribution,
31
-
etc.), the 2025 NI FRC Game Tools (Driver Station and associated tools), and
32
-
the 2025 CTRE Phoenix Tuner X. Take a moment to update all software and
33
-
firmware before attempting to load your new robot project.**
44
+
--------
45
+
46
+
### Setting up your new project
34
47
35
48
When your new robot code respository is created, it will have a single commit
36
49
that contains the entire Az-RBSI template for the current release. (See the
@@ -42,9 +55,19 @@ steps you need to complete:
42
55
43
56
1. Add your team number to the `.wpilib/wpilib_preferences.json` file. The
44
57
generic Az-RBSI template contains a team number "0", and your code will not
45
-
deploy properly if this variable is not set (*e.g.*, VSCode looks for the
46
-
RoboRIO on IP address `10.TE.AM.2`, and it will not find anything if it
47
-
tries to contact `10.0.0.2`.)
58
+
deploy properly if this variable is not set (*i.e.*, since VSCode looks for
59
+
the RoboRIO on IP address `10.TE.AM.2`, it will not find anything if it
60
+
tries to contact `10.0.0.2`.) If you forget to change this value, you will
61
+
get an error message when deploying code to your robot like:
62
+
63
+
```
64
+
Missing Target!
65
+
=============================================
66
+
Are you connected to the robot, and is it on?
67
+
=============================================
68
+
GradleRIO detected this build failed due to not being able to find "roborio"!
69
+
Scroll up in this error log for more information.
70
+
```
48
71
49
72
2. If you have an all-CTRE swerve base (*i.e.*, 8x TalonFX-controlled motors,
50
73
4x CANCoders, and 1x Pigeon2), use Phoenix Tuner X to create a swerve
@@ -76,14 +99,24 @@ method are encouraged to submit bug reports and code fixes to the [Az-RBSI
76
99
repository](https://github.com/AZ-First/Az-RBSI).
77
100
78
101
6. The Az-RBSI expects an Xbox-style controller -- if you have a PS4 or other,
79
-
change this at the top of the `RobotContainer.java` file in the
80
-
`src/main/java/frc/robot` directory.
81
-
82
-
7. Power ports...
102
+
substitute the proper command-based controller class for
103
+
`CommandXboxController` near the top of the `RobotContainer.java` file in
104
+
the `src/main/java/frc/robot` directory.
105
+
106
+
7. Power monitoring by subsystem is included in the Az-RBSI. In order to
107
+
properly match subsystems to ports on your Power Distribution Module,
108
+
carefully edit the `CANandPowerPorts` of `Constants.java` to include the
109
+
proper power ports for each motor in your drivetrain, and include any
110
+
motors from additional subsystems you add to your robot. To include
111
+
additional subsystems in the monitoring, add them to the [`m_power`
112
+
instantiation](
113
+
https://github.com/AZ-First/Az-RBSI/blob/38f6391cb70c4caa90502710f591682815064677/src/main/java/frc/robot/RobotContainer.java#L154-L157) in the `RobotContainer.java` file.
83
114
84
115
8. All of the constants for needed for tuning your robot should be in the
85
116
`Constants.java` file in the `src/main/java/frc/robot` directory. This file
86
-
should be thoroughly edited to match the particulars of your robot.
117
+
should be thoroughly edited to match the particulars of your robot. Be sure
118
+
to work through each section of this file and include the proper values for
0 commit comments