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

wrong temperature reported in message for FAULT_CODE_OVER_TEMP_MOTOR #146

Open
fessyfoo opened this issue Mar 26, 2020 · 0 comments
Open

Comments

@fessyfoo
Copy link

I've repeatedly gotten FAULT_CODE_OVER_TEMP_MOTOR which reports a temperature less than my motor temp cutoff start. The reason is due to noise on my temp sensor causing sudden short spikes. That's it's own issue and not what I'm reporting here.

I would expect the temperature reported in the fault message to be the temperature that triggered the fault. which should be over 100c according to my settings and not the < 80c that gets reported ( and is my actual temps. )

Assuming that's correct seems like a bug in the message, somehow reporting a temperature read separately from the reading that triggered the fault.

Using Firmware 3.65

<l_temp_motor_start>80</l_temp_motor_start>
<l_temp_motor_end>100</l_temp_motor_end>
Fault            : FAULT_CODE_OVER_TEMP_MOTOR
Current          : 26.0
Current filtered : 26.1
Voltage          : 34.27
Duty             : 0.950
RPM              : 36460.8
Tacho            : 3554304
Cycles running   : 360106
TIM duty         : 7980
TIM val samp     : 2
TIM current samp : 4200
TIM top          : 8400
Comm step        : 0
Temperature      : 74.14
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

1 participant