Describe the bug
While trying to publish my SwerveModuleStates to show them in AdvantageScope, I've noticed that the placement of each module is different that the one on the phyisical robot. The module has the order FR, BR, BL, FL, and I've made sure to select that option in the arrangement option, yet none appears to work. I've made sure to check that each of the modules' state is published on the correct order: 0 for FR, 1 for BR, 2 for BL, 3 for FL, and in AdvantageScope they are shown in the correct order, yet this order does not translate to the swerve tab.
To Reproduce
Steps to reproduce the behavior:
Publish the swerve module states. I've tried this:
@AutoLogOutput(key = "SwerveStates/Measured")
private SwerveModuleState[] getModuleStates() {
SwerveModuleState[] states = new SwerveModuleState[4];
for (int i = 0; i < 4; i++) {
states[i] = modules[i].getState();
}
return states;
}
Open AdvantageScope
Add SwerveTab
Add the published states to the red/blue states section of the swerve tab.
Expected behavior
A correct representation of the placement of each module on the Swerve Tab.
Thanks for finding this, the fix will be in the next release. It looks like this has been an issue for a while, but no one noticed because it didn't affect the more commonly used arrangements.
Describe the bug While trying to publish my SwerveModuleStates to show them in AdvantageScope, I've noticed that the placement of each module is different that the one on the phyisical robot. The module has the order FR, BR, BL, FL, and I've made sure to select that option in the arrangement option, yet none appears to work. I've made sure to check that each of the modules' state is published on the correct order: 0 for FR, 1 for BR, 2 for BL, 3 for FL, and in AdvantageScope they are shown in the correct order, yet this order does not translate to the swerve tab.
To Reproduce Steps to reproduce the behavior:
Expected behavior A correct representation of the placement of each module on the Swerve Tab.
Version (required):
Additional context This is important because we are updating our swerve to 2024, and we can't see if the code is working if the display is incorrect.