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

Temperature checking is occasionally reporting bogus temperatures and disabling motors. #37

Closed
brettle opened this issue Mar 20, 2023 · 1 comment · Fixed by #41
Closed
Assignees
Labels
bug Something isn't working

Comments

@brettle
Copy link
Member

brettle commented Mar 20, 2023

For now, just comment this line out:

MotorErrors.reportSparkMaxTemp(spark, temperatureLimit);

I've tried to reproduce the problem by checking if the temp is too high from within RobotCode2023's Arm.java but haven't succeeded. However, not calling reportSparkMaxTemp() definitely makes the problem go away.

@brettle brettle added the bug Something isn't working label Mar 20, 2023
@brettle
Copy link
Member Author

brettle commented Mar 20, 2023

Specifically, I'm seeing:

Port 17 spark max is operating at 188.0 degrees Celsius! It will be disabled until the robot code is restarted.

but the value displayed on SmartDashboard seems to be consistently at 24. So I suspect the reported temperature spike only happens occasionally for some reason. Notably, the report high temp occurs shortly after:

Whoops, big oopsie : fault error(s) with spark max id : 17: [ ], ooF!
Bruh, you did an Error : sticky fault(s) error with spark max id : 17: kIWDTReset kEEPROMCRC kCANRX kHasReset kSoftLimitRev , Ouch!

I suspect the sticky faults are unrelated, but it's getting some sort of fault.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants