FAQ Summary:

FAQ Content:

It means that a file is missing or hasn’t been found. It can be the boot sound, or the configuration files. In really rare cases, like powering off the saber during a sound bank selection operation, the module can store a wrong bank as the last selected one. When powered again, it will look for this fake sound banks in a fictive directory (like /bank255) and of course it won’t find any of the files. Since it does not find the main files (boot.raw, config.txt, leds.txt), it emits 3 beeps.
To get rid of this problem, press the aux. button when powering up the saber and go in the vocal menu to (re)select the appropriate soundbank.
Otherwise, it can be due to some file overwritting when you updated the sounds. You must format the SD card (in FAT / FAT16) before updating the sounds, while it’s not necessary to do so for the configuration files that can be edited in place on the SD card. To simplify the update process, put the new sounds on the SD, overwrite the old ones. Then select the whole contents of the SD card, and copy it in a temporary directory/folder on the hard disk. Format then the card, and next copy the files back to the SD card in one run.

FAQ Statistics:

Viewed:1421

Current Reviews: 0