When we used the 2024 version of YAGSL, everything was working perfectly. Our team was interested in trying the 2025 beta and other beta firmware and software to have an easier transition after kickoff.
I updated all spark maxs, cancoders, robo rio, driver station, wpilib and YAGSL all to their 2025 betas. When I open the driverstation none of the encoder values are reporting and when I enable, the swerve drive jitters and resists my inputs. An error is also posted saying “x and y components in Rotation2d are zero”.
This is my first time investigating the beta software for FRC, so if I did something silly, sorry for taking up your time
I may have found the issue. My spark maxes are on REV 2025 beta 7, while the vendor library in my code is listed as beta 3. If I can get some confirmation about wether this is correct thinking that would be great. I’ll test it in a couple of hours.
AFAIK this issue is caused by my scaleTranslation function which doesn’t have a non-zero check. If you can post your output i can fix this by the next release
Here is the stacktrace. Is there any temporary fix we can do before the next release? Also does this explain why encoder values are returned as “Number”? Thanks for the help!
Loop time of 0.02s overrun
Warning at edu.wpi.first.wpilibj.IterativeRobotBase.printLoopOverrunMessage(IterativeRobotBase.java:436): Loop time of 0.02s overrun
This error doesn’t harm anything but is fixed in the latest version that has not been released you can safely ignore it for now.
This is unrelated from encoder values being returned as “Number” (I am unsure what you mean by this). I do not recommend using the development version and will release the next version tomorrow or Wednesday after I test performance on a RIO1.
Sorry, I’m still confused. I’m not sure what issue I am having with the swerve drive then. The swerve wheels keep jittering and when I try to move forward, the wheel moves forward and then backwards. Everything worked fine with the 2024 version, but we were hoping to test some of the new features. I also can’t check if I need to invert the motors because no values are being posted to shuffleboard. Each encoder has a string that says “Number” instead of an actual value.
Can you send a video of this happening in a swerve widget?
Have you tried Elastic instead of shuffleboard?
Also this is a beta for now, so the issues you’re seeing will go away thanks to your involvement and testing! So Thank you very much for reporting and discovering this issue now!
I’m happy to help! Here is the picture of the Shuffleboard. No I have not tried using elastic yet. Some values are reporting on Shuffleboard while others are not.
And I’m having trouble accessing anything to put into the swerve widget in FRC Web Components. Is there a version mismatch somewhere? I cloned your example repo and updated all of my devices to 2025, but is there something I’m missing? Do I need a specific beta version of firmware on my devices?
Sorry about that, I didn’t get this message from CD when I responded earlier. Here is the link to our code. I appreciate all of the help you have been! GitHub - FRC3546/YAGSL-2025-beta
We didn’t have a team meeting today, I was working on the robot during my independent study and lunch. I’ll let you know if it works tomorrow morning when I’m back in the school. I’m hoping I can view the dashboard values and then fixing any inversions will solve the issue. I’m expecting to change the inversions from the previous config because we have a NavX.
I got connected to the robot again today and all of the dashboard values are populating. I went through and didn’t have any inversions to change. I am checking right now to see if our NavX firmware is the correct version. Is there a 2025 beta firmware for NavX?
I updated the NavX to the latest firmware (I can’t remember what it was, but it was along the lines of 4.501??? and I can’t find the firmware online…). I’m still experiencing issues, but I now have videos showing the output. For each video I move the Joystick forward, left, right, and backward.
