I just got this today too for the first time happened after I switched from APS 6384s to Maytech 6396’s
If I wasn’t getting this with the APS’s I assume it’s from them not having temp sensors. Have you tried pulling out the temp sensor? That’s likely what I’m going to do.
no I’m still on 3.65. Been meaning to get my head around The similar problem people complained about in fw5 but that showed up later, so I don’t know if it’s the same thing. .
Has anyone discussed using toroids for high frequency noise suppression? This appears to becoming common when using variable frequency drives in industrial machinery and automation, to deal with the spikes… Might be necessary in conjunction with the current low-pass filtering.
Generally you use the toroidal cores around the actual wires to/from the motor and controller, with inductively suppress high frequencies very effectively. The spikes themselves are inductive I think, and shielded wires aren’t enough to stop them showing up in the motor windings, and are bad for the longevity of the motors regardless.
This is outside of my wheelhouse, so I’m simplifying and probably getting some of the jargon wrong, but, worth exploring. I know the toroids available “specifically” for this application tend to be pretty expensive from domestic suppliers, but there’s been some videos recently on the effectiveness of similar import cores that are pretty inexpensive ($20-30 for larger ones) and testing effective suppression in the frequencies necessary. Let me know if you want some links.
to me, it seems far easier to do analog-digital conversion adjacent to the sensor itself, and convey the measured temperature to the esc over a relatively noise tolerant bus like i2c. parts like mcp9808 are inexpensive, have acceptable precision, have libraries already available (because they are commonly used by hobbyists), and are 5v tolerant.
i don’t expect everyone to share my view, since most people ride with hall sensors instead of as5047’s
So I am also running 3.65 and experiencing this fault. Hesitation and cogging around 18 mph and then this motor temp fault hits. Seems random, motor is not hot to touch…
Is this a fw bug, time to upgrade? I’m running a Flipsky Dual and heard 3.65 is latest stable for this ESC
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
also worth checking out later part of that thread:
Alright, I got the fault to trigger a bunch more - I’m not sure if it’s really my motors overheating or caused by noise.
It seems I can feel my motors hesitate and buck when I approach 18.5 MPH. If i really push this on the throttle, it will trigger a fault and cut out. Here are faults from Metr:
easy enough just to depin the temp. sense wire from the plug and test it…
I had some wonky riding situations, disconnected the temp. wire and no mas problemos…
I may try FW5.02 when it comes out of beta… or may not… everything runs purrrfect now…
De-pin the temperature sensor pin from the JST connector… pull “gently” up on the little plastic tab and the female pin will slide out of the JST… insulate it from shorting anything, and you can always just slide the pin back in the connector
Most of the time the Temp. wire is adjacent to the 5v, find a pin out of your VESC and it will show the location…
You’re getting overtemp motor at 43c?? What are your values for
motor temperature cutoff start
motor temperature cutoff end
Acceleration temperature decrease.
if they’re anywhere near defaults. ( 80c - 100c - 15% ).
then you’re definitely getting spurious readings to have it say 43c in the fault and not be anywhere close to those settings.
but since you have metr you should be able to upload a record of you ride and share the url with us. you can see the noisy temp readings on the temperature graph.
Lift the correct plastic tab with like an exacto blade and the female pin will easily pull out…
Then you can simply push it back in again when you wish to use it again