-
Two possible ways to get this would be to use the navx's collision detection capabilities or to use current sensing.
-
Create a command, TurnAngle, which will turn the given angle. The best way to accomplish this will be using a PIDCommand which pulls the angle off the navx.
-
-
Not sure if this is really even neccessary, but detecting if the IMU has detecting a crash or if it thinks the actual position has drifted significantly from the “dead reckoning” odometry seems kinda …
-
Using a gyroscope (in our case prob. navX) adjust the orientation of the robot to allow for movement relative to driver. If driver pushes away, robot moves away regardless of what direction is the fro…
-
`PIDSource`, `Sendable` and `SendableBase` have been deprecated in WPILib 2022. All three are used by the latest navx_frc build. When building robot code making use of the navx library, the following …
-
This is a similar issue to one that affected NetworkTables in prior years. When calling any of those APIs, they eventually call into the RegisterIO_* functions... which try to obtain the same lock tha…
-
Current idea as to why the issue is occurring: we initialize the Swerve Pose Estimator object with empty swerve module states meaning that the odometery object won't know where the wheels are point at…
-
When using field relative control, the robot kinda drifts off its rotation over time. Feedback control (PID) on rotation might help?
-
The gyro angle values aren't inverted when changing the gyro reversed to true
` public static final boolean kGyroReversed = true;`
It does invert the turn rate but not the angle/heading. So it …