Thats the same issue i was having. We need to investigate that further.
thx for testing!
There might also be a problem with the traces between the connector and the MCU pin24 (PC4). When I soldered the NTC directly to the mcu pill pin 35 TEMP_MOTOR (green circle) and GND, the values were flipping around between 60 and 150 degrees and I got overtemp errors.
I measured the path from the PH2.0 Temp pin to the mcu pin 35 and it was NOT OK. The path from the mcu pill pin35 to the mcu LQFP64 pin 24 (PC4) seems OK (hard to mesure).
with just the mcu pill, NTC between pin 35 and GND:
It is very sensitive, if I touch the ntc it quickly climbs to 150 degrees C.
but that could be settings issue i guess?
no, I checked my settings, it is 10k Ohm Beta 3950. I use them with two other vescs to measure the battery temp and Log it with metr (as motor temp). Temp is accurate within 1 degree C.
Did another test and swapped IN14 and IN15 in the ADC Vector setup and built a new binary:
- 9 (1):|IN14||ADC_15 <------ swapped!
- 10 (2):|IN15||TEMP_MOTOR <------
#define ADC_IND_TEMP_MOTOR 10
#define ADC_IND_EXT3 9
This changes the MOTOR_TEMP input to IN15 which is not used and available on the mcu pill. Connected the NTC to ADC15 (mcu pill pin 34), same result as before. Must be some config issue, I aslo compared the temp calculation with trampa 75300, it looks the same.
could it be that there is a resistor or something missing for the correct values? i mean compared to the trampa 75300?
It didn’t work, even with a 10k pullup and a 100n cap to gnd it is flipping around 60 to 150 degrees C. Maybe a problem with ADC arrangement, complicated stuff: ADC Vector Arrangement | VESC Project
1 Like
so we have to investigate that a bit further, so it could be software related as well. (expect the problem with the trace)
1 Like
Yes, better figure it out before ordering a new HW Version. I’m a bit clueless at the moment and might just use that VESC without Motor temp as it does not seem to be a problem with your setup.
1 Like
i changed it to a value that is not effecting pushbacks or something.
@jens_overby could also try to figure something out, on why its not working, I will try something myself. Maybe it is a software issue.
You can also disable motor temp in motor settings, then it will be set to 0 degrees and will never throttle down.
i know the thing was because it was jumping arround i thought it is working and I just tried to fix it via settings and never changed it again.
1 Like
FreeDRIVE running MESC firmware. Yes, M. E. S. C. with an M
SILENT HFI even for Low-Side-Shunt hardware. AMAZING.
4 Likes
As you can see in my most recent post, I’m ramping up my effort on the FreeDrive. I could easily be a config issue - never tested if the motor temperature worked b.t.w.
2 Likes
Credits to David Molony a.k.a. mxlemming (& co.) for programming the MESC firmware.
1 Like
I have thought about a very simple solution for a momentary switch, but with that implentation you would not be able to turn off the hardware - only turn on. The good thing is that this solution would enable the Vesc turn off by itself. This could be after e.g. 5 min of no activity… Simple to implement, but I don’t know if people can live without turn-off functionality.
It’s nice that the firmware has the ability to turn off the hardware, because it can save your battery if you forget to manually turn off.
Hello, could you post a picture of your setup? Thank you.
ok well at the moment its not a problem, cause my thermals on free drive are not that great (i have to work on that) . So the motor will not overheat . The fets will get to 85 C first . Nevertheless it would be great if we can figure it out. I mean i try to improve the heatsink for the fets and i guess after that I will need the motor temp in check. I will also try solve it . Btw here is the updated version for 20s and the new IC GitHub - shambler123/ICM-20948: FreeDrive changed to 20s and changes the IMU to ICM-20948
1 Like