The time out in the app configuration should make it go idle in 1 second (1000ms) if no signal for control is received. So it seems the receiver is sending something but the wrong thing or there’s some other error in the config possible the erpm values but don’t think I have that limit enabled (I have a pretty low kv motor so didn’t mess with that)
@Jinra ah, ha, didnt noticed that, i input 0.00 to both, controller stopped acting crazy when i shutt it off now. Thank you,
How do i set the failsafe to coast?
I’m not sure 0 is a good value either. I would uncheck the option if you dont need it or dont know what it does.
See my response above, looks like you already have it set, can test by throttling up a small amount and disconnecting. It should coast to a stop. The failsafe on the VESC side should be good, but make sure your receiver doesn’t have some other failsafe config for if it loses connection to the transmitter for whatever reason and you should be fine.
This is my sons eboard, a little scared he gonna get hurt. I’ll ask psycotiller, thank you for catching that for me.
Ok, i fixed the values to 0.00 in the soft erpm limits, thats one issue fix, how do i set failsafe to coast? thank you for your help.
Sounds like the parameters aren’t set up correctly and you don’t have a big enough dead zone.
Squeeze the trigger in ‘disabled’ mode and note the value in the display box, place that value in the max field. Put on full brakes and note that value, put that in the min field, then try it out. If it’s still cutting out and/or running when back in the middle then increase the dead zone.
OH, it turns out that when I walked away before, my son accidently hit the keyboard from my computer while it was connected to bldc tool, it probably changed settings by accident when he picked it up from floor and he says he pushed some buttons when picking it up from floor, SMH.
its not cutting out nomore, soft ERPM values were wrong, i changed them to 0.00. How can i set fail safe to coast?
Yea, i know that part, how can i setup failsafe to coast?
its working now, but, how do i setup failsafe to coast?
Ok. What you need to do is put the bind plug in your receiver. Then turn on your board, then turn on your remote while pushing the bind button. When the light goes solid you are bound. Then rev up your board. While it is coasting to a stop, pull the bind plug. Now just turn everything off and then back on.
To test, throttle up your board and turn off your remote at the same time. If you’re board coasts your good
ok, i’ll try it, thank you.
There are 3 kinds of failsafe: Through the VESC, the RX, and one that you really, really don’t want. You need to figure out how the receiver responds when the TX disconnects.
If the RX goes into it’s own failsafe, you cannot configure a failsafe on the VESC, but rather you depend on what PPM value the RX outputs when the TX disconnects. This should the same value output when the motor is at an idle.
Now, if the RX doesn’t have fallback, it can do one of two things: Hold the current value indefinitely, or stop outputting a value. The former can be disastrous. Do NOT use an RX that holds the value. This will leave you full-throttle down the road with no control. Too many people get hurt due to controller failsafe malfunctions.
However, some receivers will just cut their output. In this case, it’s up to the VESC to detect the ‘no signal’ state on the PPM line and engage the failsafe state (set the motor to idle).
1 Like
I currently have ppm settings on (current, no reverse with brake), when i letgo the trigger on remote, it doesnt coast, the motor just stops sudenly, how can i make it coast?
How tight are your belts? Does it stop because of tension? or brakes?
Also, Did you turn off your remote to see what happens when your board loses signal?
The VESC should idle if the RX signal is at 1500µs. (assuming that your endpoints are 1000 and 2000)
When released, the remote’s signal value in BLDCTool should be: (upper+lower) / 2 You should tweak the endpoints to make sure that the center falls on this value, or tweak the deadband if all else fails.
Next, try THIS custom fork of the VESC firmware and its matching BLDC tool version. I say this because you can individually adjust the two endpoints, and the center. Then you can make sure that your remote is working properly. Especially if you do any modding, like the SPARKLE mod, or replacing any potentiometers, you’ll need to use really weird PPM settings where the center is not necessarily proportional.
1 Like
@Tampaesk8er, could you describe your new problem a bit further? Is it possible you simply bumped the trim pots on the GT2B?
I just resetted the vesc by reinstalling the firmware and everything is working properly. I use the 2.4ghz mini controller, not the GT2B.