How do we know if ours is a R3 ? I ordered one and got mine 2 weeks ago.
It will have a jumper plug and a power symbol like @RED-FPV has on his.
Picture copied from one of his posts:
Ok thanks ! I have the same unit then 
1 Like
I am wondering is the new 75/300 VESC power switch is ideal for a safety lanyard, rather than the bulky big relay I have used in the past.
Some measurements:
With the jumper installed, and the maytech receiver connected, and maytech remote turned on. The system draws about 22 mA.
with the Maytech remote turned off, the system draws 16mA.
With the Jumper removed the system uses so little current that I can not accurately measure it.
I don’t see why it wouldn’t work to use the jumper as an emergency kill, but I would message them and ask. Best to make sure that interrupting power that way while at a high power setting won’t damage the VESC.
@Flightjunkie do we know which ESC can be cut “violently” with a relay contact activated by the kill switch ?
If this doesn’t work, there is @Rienk’s solution (on its way 
)
1 Like
Agree. But, There is something comforting about a Relay, not relying on complex electronics that when fail, can fail on full blast.
My first 2 builds had the big relay cutting the power to the ESC. APS 380AMP ESC.
Magnet/reed switch setup for activation.
I have fallen/activated the safety switch more than 100 times. The only malfunction was initially I did not have a anti-spark circuit on the relay. The relay contacts would sometimes stick/weld closed. I then added a delay relay with resister to charge the caps for a couple seconds and the sticking problem stopped.
2 Likes
Yeah. The VESC jumper switch wouldn’t work if the problem was a VESC failure at full throttle.
Would you have a link to your anti-spark mod ? Thanks.
I understand, I have the same feeling as you, but we have to thrust electronics like when we are in a plane or a car. Mechanical switches can fail also.
I did it like this. It had one minor problem. When you ejected and pull the lanyard. The motor still responded to the hand control input, but at a very reduced power level. The motor was still getting some current through the resister built into the anti-spark lead of the ESC. Enough to power the motor. Did you follow that? I could have corrected it but never bothered to.
1 Like
Pulling the switch will send the VESC to a deep sleep mode and it should draw around 20 mico amps.
That is a lot less than the self discharge from the battery.
Using this feature as a kill-switch is probably not damaging the device in a hydrofoil application. But there is no guarantee that it will not. We haven’t tested that. The best sollution is some extra code that will let you use one ADC PIN on the COMM PORT to kill the power. Benjamin might code that for next FW update.
3 Likes
So applying a zero volt on this analog to digital converter pin would override the, say, 80%throttle PPM order, coming from the remote RX module by a fast decreasing PWM/PPM signal ?
Would the VESC 6 MKIII FW be concerned ?
Thanks for asking.
Would this be an update for all Versions?
That should work for all versions then.
I bought the 75/300 VESC and got the R3 version.
In my not finished build, I planed to use a separate Antispark Switch and a Reed Relay to cut the power from the Receiver when I am falling.
Now I read that and I will through out the Antispark Switch.
So I will not take the Risk to use the ON/Off Function from the VESC when I am falling.
So my question ist, when can those implementation for the new Firmware Update be implemented?
Thanxs a lot
1 Like
Any Idea why I am getting this error when I try to use my Android phone with the VESC tool App.
Each time I try to pair , my phone finds the VESC, but when I try to pair, I get “Pairing Rejected by VESC 52840 builtin”
I have cycled the power on both the VESC and the phone. Tried to pair repeatedly.
I had it connected and paired a couple weeks ago on the bench. But now I am having trouble.
Everything else seems to work OK.
Tried forgetting the bluetooth device on the phone and doing the pairing process again?
which bluetooth module do you have?