I have a 89 sabers Anakin Ep 3 neopixel lightsaber with a proffie board (with 2 buttons, a power (ignition/retraction) button and an aux button). I recently tried to add new fonts / blade styles to my saber. After I flashed the board with the new config file, I am experiencing 2 major issues:
When I hit the aux button to change presets, the saber sometimes ignites automatically without me separately pressing the power/ignite button (i.e saber ignites automatically upon switching presets); and
Sometimes, when I hit the power off/retraction button, the blade starts to power off but before its fully powered down, it will then automatically power back on (i.e. it won’t turn off). It takes me a few times pressing the power off button for the blade to retract
Has anyone else run into this issue and figured out the solution?
Its not a hardware issue as I had no ignition/retraction issues right before I changed the config, and its not a battery charging issue, as I fully charged the battery but the issues still occur.
That’s not the Serial Monitor. That’s your upload.
Hook your saber to the computer. In Arduino choose Tools > Serial Monitor and repeat what is causing the problems. Then copy and paste what the Serial Monitor says is happening.
Unfortunately, based on where the micro-USB chord slot is located on my board chassis, I can’t insert into the saber and while the micro-USB chord is attached, and, without inserting the board chassis into the saber, it’s difficult to tell if the board / saber is malfunctioning. But I got the message below when I used the font that has been triggering an automatic ignition when I switch to that preset/font with the aux button (Kyberphonic ANH Training):
I have this exact same issue on a graflex 89saber. I’ve also lost the ability to adjust the volume. It almost never happens when the chassis/board is outside the hilt, and just like OP I can’t attach a microusb while it’s in the hilt due to the design of the hilt.
The only new symptom is the lack of volume control, but OP might have had the same issue without realizing it.
Aside from that I’m having the same random ignition while changing presets, and the issue of being unable to reliable retract blades.
My issue also started when I tried to flash a a new config to the board, and persisted after flashing the 89sabers default config, and even after trying older ProffieOS versions (6.7, 6.3) with the default config.
I can still start a new thread if that makes sense.
I tried putting the original config file back on, but there was no change in the behavior(aside from styles going back to stock). There are other variables at play(such as the version of ProffieOS and compiler output variations) that I can’t account for, as I didn’t take a binary dump of the saber’s flash before messing with it.
Try removing the FETT263_STAB_ON and FETT263_THRUST_ON defines and see if it corrects. My guess is your speaker is triggering the Stab/Thrust detection due to loud in.wav sounds. That’s why it happens more on different fonts.
If you hook to Serial Monitor I expect you’ll see the same thing in the output.
I believe this has solved my issue. Also probably why I had trouble recreating it with the board outside the hilt, not enough soundwaves bouncing back at the board.
Thank you for your support, ya’ll are pretty epic.
I guess the next riddle is what was the actual config+proffieOS on the 89saber when OP and I got got ours. I’ll get in touch with CCSabers and see what they think of this, and update thread with findings for future visitors to this thread.
Following up, the volume control is working, but it’s different now. Instead of pressing buttons to increase or decrease volume, you twist the saber. So I think the root cause is that the saber shipped with a really old version of ProffieOS, and trying to use the factory config with any recent OS will not restore the saber to factory configuration.
So for anyone trying to update their new 89saber from CCSabers, update these defines when flashing ProffieOS 6.8: