I have searched and haven’t found anything on this and I’m wondering if anyone else has run across this.
The saber turns on just fine but sporadically, when I press the activation switch to turn it off, it turns back on again. It does the same when I try to twist it off, it turns right back on again. Out of 10 activations, it will turn back on about half the time instead of turning off. Could there be a rogue wire touching it shouldn’t? The saber works fine otherwise. Thanks for any help.
It’s hard to answer without knowing more about your setup.
What prop file are you using?
What does your config file look like?
What does the serial monitor say?
Hey Prof! Thanks for replying but I think I figured it out.
Entirely optional, but it could be helpful to other people if you explain what the problem was.
My money is on clash threshold sensitivity combined with volume level = false “stab on” activations.
Sorry for the delay gentlemen! @NoSloppy was partially correct here. The clash threshold is at the standard 3. However; I did turn on “stab on” with this config and paired it with a high volume its what triggered the activation. I troubleshoot this by removing the “stab on” and it did not replicate my problem. I turned the saber down a bit and now there are no problems at all with “stab on” turned on. I guess wanting a very loud saber, depending on the resonance, combined with stab on, will do this.
It depends on the way the board is mounted, and the isolation (or lack thereof) of the speaker vibrations, but generally speaking you can likely just bump the clash threshold up a bit like 3.5 or 4 and find the happy point that STAB_ON still works without interfering with ignition.
Ya know… fine tuning.
^That. When I went to gesture ignitions, specifically Stab/ThrustOn I had to change my CT to 4. Then adding in #define AUDIO_CLASH_SUPPRESSION_LEVEL 5 got things perfect.