Trying to run yagsl driving closed loop is giving us very weird behavior.
Changing the p doesnt solve the problem at all we tried a large range of values without any success.
It is like the motor is driving then stopping than starting again
Is your battery charged?
Yes this are not brownouts
We had something similar we were troubleshooting and it ended being a low charge battery so I had to check that first lol. It would be nice if you could link your code.
Our code is the yagsl example with the only changes being the jason and changing to a ps5 controller
@nstrike maybe do you know whats the problem?
I’m unsure of whether this would be causing your problem or not but I do notice you have “swerve/neo” for your deploy directory but you do not have a neo folder in your swerve folder.
1 Like
This would!! It refers to the place where the swerve drive files are, if it is not correct nothing will be.
The students had downloaded the newest version of the exmple code and forgot to chabge that when we ran the code this was correct.
Still looking for a solution did anyone else had this problem ?
Also was anyone successful running yagsl 2025 with vortex?
Sorry, i thought the PID changing had fixed the issue. What does it look like in FRC Web Components, or Elastic, or AdvantageScope?
No prob i see how you might got confused
I will check it Tomorrow but from what i remember when checking the speeds the target speed looked good and the actual spped looked low than stop than low again tried turning the pid up and down and the only diffrent was the didstance from the target velocity but still had that weird stop issue.
Well since your directory wasn’t correct my assumption would be that your changes to the PID wouldn’t actually change the output unless you are using PID in a different place.
When we tested the directory was correct
Aside from this the code in the repo should be effectively the same but wasent commited after the testing.
The wrong directory is a debug attempt of the students, they just copied the class from the example again to be sure they didn’t accidentally change something in the class. The exact code in the repo now was never ran but should be almost identical to the version we ran.
Also if the directory was wrong the swerve completely wouldn’t work as it would fail to create the swerve.
Another thing other than a small bug we already talked about in the main yagsl thread the swerve worked fine using open loop the problem is only with closed loop
1 Like
After updating to the latest version of yagsl and the other libs the problem has seem to be resolved thx to everyone who tried to help
1 Like