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
I was updating REV's MAXSwerve Java and C++ templates which use an ADIS16470 as the gyro, and I was getting a driver station error in Java on initialization about being unable to find the ADIS16470 on the SPI port (I don't have the exact error at the moment). I wasn't getting any gyro readings, and of course the field centric driving did not work.
However, in C++ there were no issues on the same exact robot. I did not change any of the gyro setup since the 2024 version of the program, which I know was working then.
Here are where they are instantiated in the two languages:
There are a few commits that changed the ADIS16470 driver- since it's all at the java layer, would you be able to copy and paste the class into the project and bisect the history to find where it broke?
One possibility (though I haven't walked through all the logic to see why it didn't hit this last year) is that the product ID it's checking for is incorrect:
I was updating REV's MAXSwerve Java and C++ templates which use an ADIS16470 as the gyro, and I was getting a driver station error in Java on initialization about being unable to find the ADIS16470 on the SPI port (I don't have the exact error at the moment). I wasn't getting any gyro readings, and of course the field centric driving did not work.
However, in C++ there were no issues on the same exact robot. I did not change any of the gyro setup since the 2024 version of the program, which I know was working then.
Here are where they are instantiated in the two languages:
I am running WPILib 2025 beta 1 and NI game tools beta 1.
The text was updated successfully, but these errors were encountered: