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 looking over the calculations in SwerveMath.calcMaxAccel(), and I think there might be a problem in the logic. When you check the reference wheel based on the angle, not all the wheels are selected, the front left is used twice, and back right is never used. Is this the intended functionality? (The math is a little over my head what the proper fix could be)
This is indeed intended functionality. However it is not the right functionality. I implemented this with square and rectangular robots in mind. If anyone uses a triangular robot this may suddenly become a problem (but might not if front left is the center module).
On the flipside if anyone who wants to use YAGSL with a triangular chassis, I will probably fix this the same day.
I just want to add, I know of several "unique" robots that would break this theory, 2481's 5 wheel swerve in 2022, and 9312's TurdSwerve that uses 2 powered swerve wheels to drive. (that robot you could probably put in a second configuration with 2 fake wheels to simulate the chassis easily)
EDIT: Just remembered 5 powered wheeled robots are probably a thing of the past with the 4 propulsion motor limit.
I was looking over the calculations in SwerveMath.calcMaxAccel(), and I think there might be a problem in the logic. When you check the reference wheel based on the angle, not all the wheels are selected, the front left is used twice, and back right is never used. Is this the intended functionality? (The math is a little over my head what the proper fix could be)
https://github.com/BroncBotz3481/YAGSL/blob/89e41639515e64865a23ff8c33107c1e00807e45/swervelib/math/SwerveMath.java#L214
(note, moved from BroncBotz3481/YAGSL#67 , although I find it weird this is not an example issue and instead a "core" problem)
The text was updated successfully, but these errors were encountered: