Kill switch methods

I’m interested in learning more about this capability. I know a little bit but can’t find much detail by searching forum.

I know a few have gone about this with some kind of tether between rider and board as a “trigger” for when you fall off and that VESC supports the function.

I think some commercial builders have done something like this (Takuma) but I recall that Flite has some kind of auto shut off if the rhe board heeled abruptly.

If anyone can supply detail about how they did this, associated risks, reliability, effectiveness etc and/or detail about what commercial builders did I would appreciate it.

Thanks in advance

No ideas how the companies have done it.

But I have considered implementing something like this, but did not get beyond the initial stages.

It should be reasonably easy to do with gyro data of the board. When not in a failure situation, the board has only very limited range in pitch and roll.

Once you fall of the board, the board pretty much always does something aggressive in pitch, which should trigger the motor to turn off.

As far as I know (have never seen a Takuma in person) they used/use a magnet to attach to a point on the board on the hatch. When the magnet comes off it somehow triggers a stop.

This is what is posted on the Fliteboard site about their method.

Lift indicates the board does “auto-shutoff” when the controller hits the water. Not sure what that means.

I can’t find anything about if or how Waydoo does this

Check this thread here.

Magnet operated kill switch?

1 Like

The vesc has a digital control you can implement a hall/magnet kill switch.

PITA :wink:

1 Like

Some manufacturers rely on the remote losing contact when it’s underwater, after you fell
Shut-off with gyro in Rx or Tx is a option too, requiring more programming though
Magnet+Foot strap gets in the way sometimes, I personally don’t like it

No matter what you do, always cut the signal to the ESC or use the VESC cutoff input, but DO NOT cut power to the esc while it is spinning a motor. That can lead to destruction of the ESC.

2 Likes

Yes I picked up on that from the topic @windego linked!

After reading that topic (not sure why I didn’t find that one myself) and some Googling :grinning:. I have the impression that the Hall effect switch (thankyou @Larsb ) is more reliable than reed but the issue of where to place the “trigger” magnet so it’s not in the way (and of course the lanyard being a trip hazard) and the potential for getting stranded if I lose the magnet has dampened my enthusiasm for the idea.

I’m also not clear if the Fliteboard I use would require a mod that would compromise the waterproofness of the hull. I know that the magnet doesn’t have to touch the Hall effect component of the circuit to work in air but would it work through the existing hull material as I’m extremely reluctant to drill any holes in the board.

PITA indeed!:wink:

True but I’m seeking a solution that would work every time.

I’m used to the boating approach with the lanyard that grounds the circuit that supplies spark, works even when you don’t want it to sometimes :wink:

Nothing works “every time”.

Not sure how you want to implement it, but I assume with some “leash” disconnecting?

I can see plenty situations, where you get some body parts at the prop before the line disconnects.

What scenario do you have in mind, where a contact disconnects without the board tilting in any way?

Only way I could think of, is the board cruising at very low throttle.

I would appreciate some advice/feedback on how to wire the hall switch to my VESC.

I’m using this model of Flipsky 75200

I am using port 2 UART2 for Bluetooth
I am using port 6 COMM for Flipsky remote receiver

Logically I would use the COMM port for the Hall switch for ACD2, GRD and 3.3V but in my case it’s already occupied but GRD is the only one of those that the receiver uses (TX,RX,5V,GRD).

Is it good/OK practice to make a wire harness connector that would give me the three pins I need from the COMM port. The GRD would be “shared”

Yes I’m thinking of a leash based system rather than an imu - acute angle type for a few reasons.

The leash type would work in scenarios where the motion type wouldn’t. I have come off my board where it travels quite level until it stops but your correct either type might not trigger in all situations to prevent injuries.

My reasons are
Prevention of runaway board scenario - leash would “always😉” work imu might not
Secondary shutoff to back up normal trigger release/remote disconnect stop - either would work
Visible method - easy to demonstrate to public and/or law enforcement - leash method is external vs imu internal. Board doesn’t have to move to prove the system is functional, imu would require a “crash”

So to my thinking leash would work “better”

(post deleted by author)

(post deleted by author)

(post deleted by author)

I did not completely work through the other thread.

But if you want to use a leash, why not simply use one of those pogo connectors instead of hall sensors?

Hall seems more complex for no additional benefit.

If you want to be real safe I probably would have the leash kill the power to the Rx of your remote completely.
If you use a hall sensor, get one with an output that can drive a small relay - use that relay to switch the supply line to your Rx
Otherwise connect the hall sensor power input to 5V or 3.3V on any connector, gnd to gnd on any connector, output of hall to ADC 1 or 2
And take a unipolar hall switch, not a linear hall sensor

Hall switch with strong magnets will penetrate CF+Styrofoam no problem for a few cm

1 Like

@ludwig_bre

Thanks for the feedback. :grinning:

I’m likely wrong as I have a rudimentary electronics understanding but it’s my current belief that the ACD2 connection to the VESC coupled with the KS function activates the VESC to cut power to the motor. The other connections would seem to work in a similar if not identical manner.

Your idea of implementing a relay / RX is interesting but I don’t understand why that approach would be “safer”. Could you expand on that please.

I’m also concerned about adding another component (relay) that could potentially fail or malfunction. I subscribe to the KISS method in most things :wink:

Gonna have to get back to you after I Google this one up😉

So is this what you are referring to??

If so wouldn’t that require the pin to project above the board surface so that you could close it?

And isn’t that what you want?

Because in that case you don’t rely on the VESC to cut power based on a software function that reads the killswitch input, but rather you take away the throttle signal completely.

Thanks for expanding I now understand the logic behind the RX approach but isn’t the RX also related/dependent on a VESC software function to work to some degree?

I’m a bit out out my depth on this stuff so thanks for confirming my undertanding of the ACD2 part of my post.