Hey! Our team is new to robot characterization and we’ve been trying to get Sys ID to work on test bot recently. However, we seem to be having trouble with the way that we’re entering parameters or the way it’s plotting the simulation data.
Either way it’s causing our sim velocity r squared value to be incredibly low, which is making us unable to use the constants we’re being given (to my knowledge).
Also if it’s helpful to know, our encoders do seem to giving the proper distances back when running the tests.
Upon further testing it doesn’t appear to be an issue with our gear ratio, in fact the recorded encoder distance seemed to off by a factor of whatever we put in as the gear ratio.
It seems to be more of an issue of the “analysis type” being set as “drivetrain” in the generator, at least for characterizing our robot’s movement on the x axis.
What I mean by that is we do seem to be getting better plot simulation data when we set our mechanism on the logger as “drivetrain (angular)” while it’s listed as “drivetrain” in the generator as shown in the image below:
I was able to find a work around to what seems to be good data for our robot’s movement on the x axis while setting the analysis type as “general mechanism” on the generator and “simple” on the logger as shown in the image below:
The “drivetrain” and “drivetrain (angular)” both use the drivetrain generator type. The non-angular logger setting runs the robot in a straight line (both wheels going the same direction), while the angular version spins the robot in place (wheels going in different directions. This is to achieve analysis of both linear and angular velocity and acceleration.
