I'm having a bit of an issue with my saber. I purchased a Sabertrio Neo saber, which uses a CFX board (and a neopixel setup). Out of the box, it worked fine. However, after installing a new soundfont, I noticed that sometimes the motion sensor would start acting up, and when the blade was ignited it would start making sounds as if I was swinging the blade around wildly even if I wasn't moving it at all. In an effort to fix it I tried restoring the settings with RICE, but now the issue has not only not gone away, but it's happening all the time with every soundfont no matter what. I tried upgrading the firmware to the latest beta (1.0.003), but it didn't fix the issue (in fact it made it so the blade wouldn't even turn on at all), so I reverted back to what the saber came with (1.0.001)
I've read in a Facebook post from Sabertrio that this might be caused by an issue with the motion sensor, but it's mainly a software issue. From their post:
[CFX MOTION SENSOR GLITCH]
There has been a handful of reported cases where a Crystal Focus X equipped Neo Saber would exhibit one of the following symptoms:
- Clash sounds triggering even though the saber is stationery.
- Smoothswing sounds going haywire.
- No swing sounds playing.
The reason for this is due to a production variance of the on board motion sensor where certain pieces required just a little more time than what was given during the boot stage to initialize. Further compounding this was that battery charge level also played a part in influencing the timing required which made this issue hard to detect during production quality checks and testing. As a result, the motion sensor did not properly reset and started given false readings which then creates the symptoms as described above.
Since it was sort of working out of the box, is there perhaps something I can do to fix it manually on my end? I'm kind of new to this whole saber stuff, so any help would be appreciated. It would suck to have my first saber already struck by hardware issues ^^