I was finally able to get the free time to set up and run the clash recorder. This is using Proffie’s master branch, up to commit 5de73a894938ce2f71e6478ec9cc5059151a687a (yesterday). What I tried doing was recording 3 true clashes by turning the volume down to 10% and hitting the saber. Then, I recorded 3 false clashes by maxing out the volume and triggering the false clashes by using blaster blocks. I’m not sure why 7 files were created instead of 6.
Another thing to note is that after updating to the master’s latest, I noticed that I received the improvements to the false clash rate regardless of whether I set the accel range back to 4; I was able to set it back to 16 and had the same improved (but not fixed) behavior. Also confirmed that switching back to Sabertrio’s fork reintroduced the high levels of false clashes, and reconfirmed that setting the accel range to 4 with Sabertrio’s fork resulted in the improved false clash rate.
Sabertrio wants me to send in my saber for warranty service, so I will be doing that soon. I hope this has been helpful!
Did you try lowering your volume?
If you cut your volume in half do you still get false clashes?
Have you tried better supporting or insulating the board from the speaker?
If you go back through this thread there are other suggestions in addition to CLASH_THRESHOLD_G and AUDIO_CLASH_SUPRESSION_LEVEL to try, including the recent suggestions from profezzorn.
Last I remember was that we had some very odd results with changing the accelerometer ranges. For some reason, restricting the range in software did not work the same as restricting the range on the device, which would indicate that the device itself is producing weird values when we set the range to 16g.
I’ve added CSV to the list of extension that can be attached.
I will take a look at the things you recorded when I have a chance.
That’s weird, because I don’t think I’ve done anything that would change clashes on the master. Makes me wonder if maybe there is something simpler going on here, like maybe I’m using data at the same time that DMA is writing to that data? Time to review the code again I guess.
Im also getting the clash issue on an Sabermach Saber (basically an 89 Sabers) Kenobi. interestingly I though it was a shorting issue as when screwing the pommel on the clashes are really bad and the chassis I have has the metal surround … I increased my clash threshold to 3.5 (the original was 2.5 when I got it) and its better … also got the audio suppression at 25 and its definitely better but still there … I think its a case of tweaking but its slightly irksome that it goes off randomly … also some fonts seem worse than others (I have 4) which doesn’t seem to make a ton of sense but I guess that might be to do with the wav files not being levelled?
This thread’s a bit outdated now, there have been multiple additions/changes including new clash detection that are now part of pre-alpha OS7.x. You’ll want to get the current version of Master from github to test.
Different fonts and or specific sounds can absolutely have different results if it’s volume/speaker vibrations that are causing false clashes. I would test the new pre-Alpha master and read through here for all of the settings available to tweak (including just lowering the volume if you’re pushing the speaker too hard).
sorry one last thing … I did reign back the volume as it happens from 2100 to 1900 … again it was set originally at 2000 but it was horrendously loud and that original config it came with was super simple.
Not sure how to do a post on here. I’ve been using the test for clashes because my saber was horrible. This addition is AMAZING! I can now have my clashes on 1.0 with the sound at max and I no longer get false clashes or ignitions. I can tap my blade ever so slightly to cause a clash. I absolutely love it!
Clash detection on 1.0, Suppression at 10, font 1 notch below max.