I have it compiled into a Linux executable if you really need it, but you need to run it on Linux. I could compile it from source if you really, really, really need the naked .bin file.
Also
1 Like
Have the newest vesc version running on a unity. New METR pro unity model installed. I havenāt found anything yet but assuming we still donāt have a motor temp reading fix?
Turn off unity then turn on unity. āScanā > āPairā or āScanā > āConnectā > āPairā does not work?
Nope, it wonāt let you pair that way once you delete the paired vescs
1 Like
Strange, because that is how you can do it with Trampa VESCs.
(Also unpaired and re-paired different VESCs like this recently.)
It says thereās nothing connected and when you try to connect it just says you have to add the uuid manually or use the USB then immediately disconnects you.
Can you show that screenshot without the message pop-up?
Seems like you are connected to the Unity. What happens if you hit āpairā?
Edit: Try to delete all previously connected VESCs in paired list. After that, try to pair the current VESC/Unity.
Deleting VESCs in the paired list is what causes this problem, I think. I would not do that, or at least save the UUIDs before you do.
Recently, I could not connect new MK IV VESCs to the VESC app to run motor detection.
I deleted all previously paired VESCs from a MTB. After that I could pair the MK IV. I supect @Chase problem could be similar if he has previously paired VESCs saved in the app.
Edit: I am not sure if this is a bug in the app.
1 Like
This happened because I deleted all vescs in pairing list. It warned me but I was being stupid on the fly and did it. As soon as the pop-up message goes away it automatically disconnected you so when you hit pair it doesnāt work. Whatever the case be, I plugged it into the USB and fixed it.
2 Likes
Bit of an odd one: one of my motors spins backwards in hfi sometimes.
Specifically if it has been sitting for a while or stopped without braking all the way. This manifests in my back truck trying to turn while not accelerating.
I changed phase wires around, increased or decreased all parameters in the hfi tab, yet nothing but a hip flick fixes it.
What am i doing wrong?
1 Like
I donāt think youāre doing anything wrong. Sometimes that happens.
I would recommend saving the values you have now, and retuning the HFI and often that will fix it.
Also, for me, motor temperature has a lot to do with how well HFI works. When my motors get hot, HFI performance degrades drastically.
2 Likes
Does that imply that HFI is not really an option for offroad MTB riding? I mean as soon as you ride uphill offroad for 5-10 minutes or so motors usually are around or above 60Ā°C (140 Fahrenheit)?
HFI is only for applying throttle at exactly 0.00km/h. At any other speed, itās not needed and usually not even turned on above 2000erpm. It should be fine.
I just notice that when motors get hot it works much worse. I bet that if I tuned it while they were hot, my results have a chance of being different. But I donāt know, itās just what Iāve observed.
4 Likes
Mine seem to perform good at all temperatures, they just canāt get the direction quite right
Also, i seem to have found a pretty quiet spot:
30khz switching frequency
32 hfi samples
2/4v start/max voltages (with the start still being at 20v)
Erpm at 1000
Is there a limit to how high switching frequency can be?
1 Like
I noticed this behaviour when I played around and decreased the āSensorless ERPM HFIā. I think I had to stay above 1500 to avoid thisā¦ but that might also depend on the setup.
2 Likes
But they spin backwards (both motors randomly i noticed now) from standstill.
Lower erpm seems better even, as soon as one motor shoots over the erpm they both catch on with the observer in the right direction.
Pretty scared to bottom out 160 motor amps to properly test launching for nowā¦
Yes, but Iām not sure what it is. If you start getting the Watchdog fault then itās too high.
1 Like