DKAY:
time to upgrade?
Maybe. can you show that you have noisy temperature sensor with any kinda telemetry?
would have to be a jump to 5.2. there was mitigation in 5.0 (stronger software low pass filter) but a new temperature related median filter bug in 5.0 and 5.1. 5.2 is still beta
This is a manually maintained list of known bad firmware versions for VESC/UNITY It’s a wiki now so you can add to it.
keep the description short and link to some reference thread or other documentation.
sudden cut off’s due to faulty readings . not exactly a bug, but mitigation was done in 5.0
3.63, uart priorty change leads to motors stuck on .
3.64 can bus issues on some hardware.
4.00 th…
also worth checking out later part of that thread:
The motor temp problem stems mostly from the fact that not everyone is running the same analog LPF on the motor temp sense and the lack of control on routing of the sense wires in the motor. I think a lot of the hardware has higher cutoff frequency around 100 hz which means noise passes through up to 1kHz. The vesc 6 LPF definitely makes this issue less prevalent. If you want to know why noise is coupled into the motors temp sense all you have to do is look inside a motor to find all the terrible coupling you need:
We’ll continue trying to improve the code to get reliable performance but there is only so far digital filtering can go when aliased samples are taken. On the stormcore we ended up swapping the cutoff freq of the LPF to address this but there isn’t much I can do for all the people using unity’s out there, except to say get a motor with better temp-sense routing.
4 Likes