Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed Requirement during ManualFeedbackTuner or any Opmode created #372

Open
ftcaarya opened this issue Mar 5, 2024 · 11 comments
Open

Comments

@ftcaarya
Copy link

ftcaarya commented Mar 5, 2024

RR FTC Version

0.1.13

Observed Behavior

After all tuning has been done for drive encoders, I was running the ManualFeedbackTuner opmode that was given with no edits to the file. When I ran it though I get a error saying "Failed Requirement" And the team code line says a line, I delete that line and run again it shows a different line with the same error. All these lines are in a trajectory builder btw.

Tuning Files

No response

Robot Logs

No response

@ftcaarya
Copy link
Author

ftcaarya commented Mar 7, 2024

@rbrott

@rbrott
Copy link
Member

rbrott commented Mar 7, 2024

Can you please post the full stacktrace?

@ftcaarya
Copy link
Author

ftcaarya commented Mar 7, 2024

IMG_2887
IMG_2886

@rbrott
Copy link
Member

rbrott commented Mar 8, 2024

Can you attach a robot log?

@ftcaarya
Copy link
Author

ftcaarya commented Mar 8, 2024

Can you attach a robot log?

What does that mean? Like the telemetry or the robots behavior or logcat?

@rbrott
Copy link
Member

rbrott commented Mar 9, 2024

Go to http://192.168.43.1:8080/logs and download one of the files.

@ftcaarya
Copy link
Author

@ftcaarya
Copy link
Author

Go to http://192.168.43.1:8080/logs and download one of the files.

@rbrott I linked it

@rbrott
Copy link
Member

rbrott commented Apr 13, 2024

So your params are

MECANUM_PARAMS
  axialGain: 0.0
  axialVelGain: 0.0
  headingGain: 0.0
  headingVelGain: 0.0
  inPerTick: 0.02258823529411765
  kA: 0.0005
  kS: 1.466179965890956
  kV: 0.004050112092712909
  lateralGain: 0.0
  lateralInPerTick: 0.0
  lateralVelGain: 0.0
  logoFacingDirection: BACKWARD
  maxAngAccel: 3.141592653589793
  maxAngVel: 3.141592653589793
  maxProfileAccel: 50.0
  maxWheelVel: 50.0
  minProfileAccel: -30.0
  trackWidthTicks: 1330.9955862311713
  usbFacingDirection: UP

lateralInPerTick should not be 0.0. Follow the tuning instructions to calculate its value.

@ftcaarya
Copy link
Author

So your params are

MECANUM_PARAMS
  axialGain: 0.0
  axialVelGain: 0.0
  headingGain: 0.0
  headingVelGain: 0.0
  inPerTick: 0.02258823529411765
  kA: 0.0005
  kS: 1.466179965890956
  kV: 0.004050112092712909
  lateralGain: 0.0
  lateralInPerTick: 0.0
  lateralVelGain: 0.0
  logoFacingDirection: BACKWARD
  maxAngAccel: 3.141592653589793
  maxAngVel: 3.141592653589793
  maxProfileAccel: 50.0
  maxWheelVel: 50.0
  minProfileAccel: -30.0
  trackWidthTicks: 1330.9955862311713
  usbFacingDirection: UP

lateralInPerTick should not be 0.0. Follow the tuning instructions to calculate its value.

I had the letralInPerTick set but I was doing integer division instead of double division it was set as 24/1025 where it should be 24.0/1025 sorry for the trouble and thanks

@EthanHu29
Copy link

@rbrott , Any tool we can make the log files readable for human being? Or we have to write one ourselvles? Any suggestion? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants