New member of this forum here. Was hoping for a more triumphant introduction, but I've run into a problem with my first saber build.
I first posted this on the TCSS forum, and while it seems to be similar to what a few other posters have experienced, I haven't received any responses yet.
Built a saber in late December using a CF 9 board I bought on clearance from the TCSS. Shortly after getting it put together and running the SD card died.
This happens occasionally with SD cards so I figured I got a bad one, and replaced it with a new one that was reformatted and set up with the stock config from the Plecter Labs site.
On activation the saber immediately started making constant swing and clash sounds.
I thought that it was feedback from the speaker so I tried adjusting the sensitivity and the distance of the board from the speaker, but this had no effect.
After messing around with it for a while my kid pointed out that it worked normally when we switch sound fonts during the same session.
The battery is fully charged and the board looks clean under a magnifying glass. The config is currently stock, but I have tried tweaking the motion sensing parameters which seems to have little effect on the problem.
I've verified there are no shorts and have re-soldered my connections once to make sure I didn't mess anything up. Don't see any obvious signs of damage to components, but the area around the motion sensor seems to be a little hot when running. Not sure if this is normal or not.
Don't have a R.I.C.E. connector, so can't do real-time checking.
This happens whether the board is in the saber or when it's pulled and laid out on the bench, and I've checked it with various combinations of sound, main LED and FOC LED's disconnected.
Also, this doesn't seem to be linked to any specific font. It always starts up flashing and clashing, and then settles down once we switch or re-select the current font.
Does this sound like a config or component problem? If component is there a repair option?
In hindsight I wish I'd installed a R.I.C.E. connector, and may still do so.
At the end of the day I got a good deal on the board, and it works, but any help would be appreciated.
Here are the steps to reproduce the problem:
1 - Remove the kill key. The saber boots.
2 - Activate the saber. It ignites and immediately begins making swing and clash sounds.
3 - Deactivate the saber, and use the auxiliary button to select a font (even select the same font).
4 - Reactivate the saber. It ignites and operates normally. (This is true for all subsequent font changes as well.)