need that answer still @mikEEE
2 Likes
Yep I been thinking about this. but until i’ve been through it I didn’t want to advise it. if it’s working for him with sensorless cog style then i’m on the side of leave it alone.
and mine? i’ve tried to slide the beta values around and don’t feel comfortable with it. I’d rather figure out the HFI path. he would also have to get his connector’s broken wire repaired. work we’ve avoided.
2 Likes
just thinkin’ to myself here… pardon the randomness… but if I were in @mikEEE’s shoes what would I do…
first lower the motor amps
second raise the max temp setting in the VESC tool… 120c is the max I could get on my firmware
then I’d plug the sensors back in, ride casually, and observe the motor temp.
If he’s getting cut outs at 120c I feel he’s running in the danger zone
and I’d lower motor amps to a level to not get to 120c and alter my riding style to keep the craptor hubs from melting…
yup… that’s what I’d do
1 Like
I don’t have a temperature sensored motor at my disposal but if your a smart cookie and can observe static temperature as you adjust the sliders you could say look at the settings and the temperature and say slide the beta values where 25c would equal something way less say 5c or zero C…
but I’ve already said my piece above at what I would do in his situation…
YUP
I had similar thoughts.
… i failed on hat last part. 
but if it’s working for him. except drop motor currents. I think it’s better not to change anything else.
1 Like
i think the curve is non linear on a thermistor ???. so adjusting with a lower temp observation does different stuff at a higher temp. if i were doing it myself I’d probably heat it up and then tweak the settings. I did play with this before trying to avoid my flaky motor temp overcurrent faults.
Oh, I think I got this wrong.
Were you having “throttle stuck on” issues? that’ll be something else. nothing we’ve done so far addresses that.
1 Like
exactly… and we could debate/collaborate to solve this issue but I feel we both agree this is not the path he should take…
when I first swapped over my Unity to FW5 I experienced some weird thermal throttling that was not actual high temperatures but a firmware filtering problem…
I just depinned the thermistor at the sensor plug and trusted I knew my motors…
now apparently it is fixerated in FW5.02, but I’ll be gawd damned if I’m going to open up my board again (on a perfectly working mach-scheen) to add back in the temperature sensor…
1 Like
@mikEEE what version of the firmware are you running?
and remaining action item:
set your motor currents down from 60A. your battery current is set to 23.33, motor is still 60A. set them on both sides. try between 23.33 to 30A. as low as you can stand.
leatetes , thats the same thing you set for motor and battery regen values in the wiz ?
so there’s a solid change its gonna have “throttle stuck on” and the breaks only half worke ?
Just set it in the regular UI. “motor settings” -> “general” -> “Current tab” -> “motor current max” and “motor current max brake”
what motor firmware version are you running?
That’s a more unusual issue. I’m hoping for no, not a solid chance. Did it happen more than once? what firmware version were you running at the time? was that with the VX2 remote? which remote are you using now?
ok. also a new issue since I unplugged my motors to sodder , they now start in reverse upon boot
@fessyfoo
did you change anything since you successfully rode it? it doesn’t make sense to me that it would work normal then flip directions on reboot.
is it both motors? or just one.
Does it no longer ride properly? or does it just do this on the bench?
"have you tried turning it off and on again. "
there’s a couple ways to flip the directions on the motors, but if you didn’t change anything they shouldn’t change AFAIK. did you ever disconnect the big phase wires going to the motors? 3 per motor. I don’t think you would have I think you’d have had to cut the shrink wrap i see in your photos above.
no its perfect it I just have to put my remote in reverse mode on both motors every time
I did unplug them
Oh so your test runs were in “reverse”. ok. then it makes sense.
The two ways to solve that are:
Replug them. if they are plugged in to positions 1, 2,3. then you’ll want to plug em in 3,2,1. I think, but am not actually sure you should re run motor detection. (does that matter if there’s no hall sensors to detect? )
alternatively there’s a vesc setting “motor settings” -> “general” -> “general tab” -> “invert motor direction” but I think that’s usually downplayed. not sure why.
Take a good picture of the motor phase wires before and after if you mess with them.
What version of the firmware are you running?
don’t forget to drop your motor current max amps down from 60A to 25A or the lowest you can stand.
ill just inverte the motor direction in app setting should be fine
well that’s it I guess
Cheers m8 now its all good to go and I’m so happy I couldn’t tell you
Hope you have agreat day and a few beers to top it off 
you where of valuable help
2 Likes
congrats. 
you never quite answered this one. what version of the firmware are you running?
you should be able to see it in vesc-tool. “firmware” section lower left section of the screen when you connect.
FW version 4.3 I believe i’ll double check tomorrow
1 Like
4.3 isn’t a version. 4.1 and 4.2 are.
cool.
1 Like