Naigon Electronics Igniter 3 Setup Manual

IGNITER 3™ SETUP GUIDE

© 2017 by Scott DeBoer, Naigon’s Electronic Creations. Igniter 3™, Igniter 2™, Igniter™ and Naigon’s Electronic Creations have no affiliation
with Lucas Film, Disney, or its subsidiaries.

1. CONTENTS

1. Introduction ........................................................................................................................................................... 5

2. Getting Started ...................................................................................................................................................... 6

2.1. Important Notes ........................................................................................................................................... 6

2.1.1. 3.7v Power Supply ............................................................................................................................. 6

2.1.2. Battery Protection ................................................................................................................................... 6

2.1.3. Battery Brands ......................................................................................................................................... 6

2.1.4. Battery Size .............................................................................................................................................. 7

2.1.5. LED Choices .............................................................................................................................................. 7

2.2. Igniter 3™ Layout ......................................................................................................................................... 7

2.3. TruDrive™ Separation .................................................................................................................................. 9

3. Wiring Diagrams .................................................................................................................................................... 9

3.1. Basic Wiring .................................................................................................................................................. 9

3.2. RGB Wiring ................................................................................................................................................. 10

3.3. RGBW/RGBA/RGBX wiring ......................................................................................................................... 11

3.4. Color Changing Crystal Wiring .................................................................................................................... 12

3.5. X-Saber Wiring ........................................................................................................................................... 13

3.6. Pixel String Wiring ...................................................................................................................................... 14

3.7. Full Wiring With Accents ............................................................................................................................ 15

3.8. Dual Speaker Setup Using MaxAmp™ ........................................................................................................ 16

4. Configuration Editing ........................................................................................................................................... 17

4.1. Installation ................................................................................................................................................. 17

4.2. Copy Files to your machine ........................................................................................................................ 17

4.3. Launching The Application ......................................................................................................................... 18

4.4. Changing Soundfonts ................................................................................................................................. 20

4.5. Editing Settings ........................................................................................................................................... 22

4.5.1. Master .................................................................................................................................................... 22

Page | 2

4.5.2. Blade Effects .......................................................................................................................................... 24

4.5.3. Blade Color ............................................................................................................................................. 25

4.5.4. Clash ....................................................................................................................................................... 26

4.5.5. Blast ....................................................................................................................................................... 27

4.5.6. Audio ...................................................................................................................................................... 28

4.5.7. Motion ................................................................................................................................................... 29

4.5.8. FX ........................................................................................................................................................... 29

4.5.9. DP ........................................................................................................................................................... 30

4.5.10. MP ..................................................................................................................................................... 31

4.5.11. Advanced ........................................................................................................................................... 32

4.5.12. Accent ................................................................................................................................................ 33

4.6. Format Micro SD ........................................................................................................................................ 34

4.7. Copy Files Back To The Micro SD................................................................................................................ 35

5. Error Codes .......................................................................................................................................................... 35

6. Saber Operation................................................................................................................................................... 36

6.1. Idle Mode ................................................................................................................................................... 36

6.1.1. Idle Mode Interaction Table .................................................................................................................. 36

6.2. Running Mode ............................................................................................................................................ 37

6.2.1. Running Mode Interaction Table ........................................................................................................... 37

6.3. Saber Cinema™ .......................................................................................................................................... 38

6.3.1. Saber Cinema™ Interactivity .................................................................................................................. 38

6.4. Saber Apps™ ............................................................................................................................................... 38

6.4.1. Color Editor ............................................................................................................................................ 39

6.4.2. Motion Editor ......................................................................................................................................... 39

6.4.3. Saber Says .............................................................................................................................................. 40

7. Thanks .................................................................................................................................................................. 41

Page | 3

Page | 4

1. INT RODUCTION

Introducing Igniter 3™, the greatest soundboard on the market. Igniter 3™ has been rebuilt from the ground up,
allowing the best possible audio and motion experience:

 Amazing motion with SaberSense™ improved, for perfect swing and clash detection out of the box.
 16bit DAC off-CPU component, for full-speed, crystal clear volume
 Integrated MaxAmp™ - for the clearest, loudest volume possible out of a 3.7v battery.
 Adjustable volume for hums and effects now in 1/16 increments, to perfectly set the volume for each

speaker.

 On-board error LED to make installs a breeze.
 Switch hums during Dual Phase™, allowing the most vivid switching color experience on any saber.

In addition, you can still experience the classic features from Igniter 2™:

 Alternating Clash – harness the power of lightning, allowing the clash to alternate between the blade and

clash color.

 New Demo App to bring the saber to life without even interacting with it.
 Pixel Support! Supports WS2812B compatible strings.
 Improved audio with integrated MaxAmp™ - the audio hardware has been improved by integrating the

MaxAmp™ right on the main board! Now crystal clear and loud audio is possible without the need for

extra wiring and the extra satellite board. Further, for those that do still want to use the external
MaxAmp™ board to drive two speakers, the main board now has two small pads making the wiring much
easier for this scenario.

 Unparalleled experiences with Saber Apps™ - the most amazing way to get the full potential out of your

saber. SaberApps™ allows independent apps to be run on the board, allowing for totally separate

experiences from the main firmware. From utility, to editing, to games, this opens up a world of
opportunities that were never before possible in a saber.

 Configurability with on the fly editing – two editing apps are included by default for editing the motion

and color settings of the board. Accessible from the Saber Apps™ menu, these will make editing

parameters on the fly possible; there is no need to remove the uSD card or even be hooked to a
computer!

 Experience the first ever game for sabers – Saber Says™! Copy increasingly long sequences randomly

generated by Master Simone to get a high score. Play alone or challenge your friends in a round robin
game to see who can get the high score!

 The ultimate color mixing – independent settable colors for main blade color, clash/lockup color, blaster

block color and Saber Dual Phase™ color

 Saber Dual Phase™ - The ultimate in color. Now one font can switch between two colors on the fly with

the flick of the wrist!

 TruMix™ - hum sounds are mixed in real-time with other sounds
 Saber Cinema™ with selectable starting track on every font.

All of this now comes in a super tiny package – only 1.75” x 0.85” x 0.263” for the board, and 2.07” x 0.85” with the
TruDrive attached. This board operates on ONE 3.7v Li-ion battery, is tiny and is suited for just about any build.

To learn more about all the improvements in Igniter 3™, checkout the official release video here:

Page | 5

HTTPS:// YOUTU .BE/K NTRYSITORK

2. GETTING STARTED

2.1. IMPORTANT NOTES

PLEASE READ THIS SUBSECTION CAREFULLY AS FAILURE TO DO SO COULD CAUSE DAMAGE TO THE IGNITER
3™ BOARD.

2.1.1. 3.7v Power Supply

Igniter 3™ is designed around a 3.7v power supply input. In general, the best way to run an Igniter 3™ is to hook up
a single 3.7v battery to the VBATT+ and VBATT-/GND pads.

NEVER HOOK A 7.4V BATTERY DIRECTLY TO AN IGN ITER 3™ UNDER ANY CIRCUMSTANCES , OR YOU
WILL DESTROY THE BOARD.

NEVER REVERSE THE PO LARITY OF VBATT+ AND VBATT-/GND. IF USIN G A CON NECTOR FOR THE
BATTER Y, MAKE SURE T O USE ONE THAT ONLY CLIPS IN ON E WAY T O PREVENT DAMAGING THE
BOARD BY HOOKING THE POWER IN REVERSE.

2.1.2. BATTERY PROTECTION

Only use li-ion batteries that have a built-in protection circuit. NEVER USE UNPROTECTED CELLS AS THIS CAN

CAUSE DAMAGE TO THE BATTERY AND/ OR IGNITER 3™. IMR batteries are okay but since they are not

protected they can allow large amounts of power to the board and do not act like a fuse when there is a wiring
issue, so for beginners it is recommended to use the standard Li-ion with the protection circuit.

2.1.3. BATTERY BRANDS

Because only one battery is being used, it is very important that a quality battery is selected to get the best
experience from Igniter 3™. From internal testing, the following brands are the only ones recommended for use
with Igniter 3™:

 KeepPower
 Solo’s Hold custom
 Panasonic
 Sayno
 Tenergy

These batteries have the best life and have the most consistent voltage output, allowing for the best experience
through the entire life of the battery. If you choose to use another battery your experience will not be guaranteed.

Specifically when using the Pixel blades, the best battery that Naigon’s Electronic Creations recommends is the
KeepPower 3120mAh 18650. Based off the Sony VTC6 cell, it has a 15amp pcb, and very good discharge charistics
even under high amperage drain. You can find it here:

Page | 6

https://www.illumn.com/18650-keeppower-3120mah-sony-us18650vtc6-protected-high-discharge-button­top.html

Another good choice is the KeepPower 18650 3400mAh, which has a 10amp PCB:

https://www.illumn.com/batteries-chargers-and-powerpax-carriers/18650-keeppower-3400mah-panasonic­ncr18650b-protected-button-top.html

These batteries will not trip when using the Pixel strings with Igniter 3™, as they have a 15 amp and 10amp pcb
respectively, and both work very well for in-hilt LEDs as well.

Finally, Solo’s Hold just released a new Panasonic battery that also has a 10 amp PCB. These are great as well and
are highly recommended: http://www.soloshold.com.

2.1.4. BATTERY SIZE

The only battery that is recommended is the 18650. A 26650 can work as well if more runtime is desired. I do not
recommend a smaller battery as there are none that are known to have at least a 10amp PCB.

2.1.5. LED CHOICES

When using Igniter 3™ with a 3.7v power source the LEDEngin LEDs will not work well. This is because LEDEngin’s
green and blue dies require a forward voltage of 4.0v for maximum brightness. Thus it is highly recommended to
use the NECree RGB Red/Green/Royal Blue LED sold here at Naigon’s Electronic Creations.

http://saberigniter.com/NECreeRGB.aspx

The NECree RGB produces the brightest, most even blade for an in-hilt LED, but it also is pre-wired for 3.7v with a
diode built-in for the red, so no external resistors are needed. The standard TriCrees work as well but will require a
resistor for red, and a bit more wiring to connect all the positives together.

2.2. IGNITER 3™ LAYOUT

Before getting started, it is important to familiarize yourself with the layout of Igniter 3™, TruDrive™ and all of the
pads on the board. This will help in wiring up the board for use in a saber.

The following two diagrams show the important components of Igniter 3™, with an accompanying table describing
what each component does.

Page | 7

Figure 1 – Important components on the back of Igniter 3™.

Name

Label

Description

1. Micro SD card

holder

NA

Holds the micro SD card that contains the fonts and
configuration for Igniter 3™. Make sure that the card is fully
inserted before applying power to Igniter 3™.

2. TruDrive™

board

LED DRIVER PCB

Driving board that powers the high-power LEDs from Igniter
3™.

3. Battery +/-

pads

BAT+, BAT-

Hook power and ground from a 3.7v li-ion pack here.

4. Speaker pads

SPKR

Hook a 1.5-3.0w, 8ohm speaker here.

5. Accent

Common +

VLED+

Used to power all three of the accent LEDs. Optionally,
additional static LEDs can be powered from this pad. The
output is 3.3v, and it is rated at 200mA.

6. Accent LED

pads

1,2,3

Each pad can hold one 20mA accent LED. These LEDs will be
sequenced by the chosen pattern.

7. Accent LED

pads

4,5,6,7,8

Remaining LED pads that are smaller in size. 28AWG or smaller
wire is required for these pads.

8. LED connect

pads

1,2,3,4,GND

Pads that hook the TruDrive™ board to the Igniter 3™ main
board. Hook the corresponding numbers together with a wire.
Pad 1 connects the ground, pad 2 connects C1-, pad 3
connects C2-, pad 4 connects C3- and pad 5 connects C4-

Page | 8

9. Color Pads

C1-, C2-, C3-, C4-

Hook the main LED cathodes to these pads. C4- may also be
used for an accessory such as a rumble motor.

10. Switch Pads

MAIN, AUX

Pads for the switches. MAIN can be a momentary or latching,
AUX must be momentary. Make sure to select the correct type
of switch for MAIN in the Config Editor.

11. Clash Pads

CS+, CS-

Not necessary in Igniter 3™, though hooking a clash sensor
here will aid in detecting clashes.

12. S Pads

S1, S2

Used for connecting the XBee module or BT module

13. Comm Pads

DA, CL

Reserved for future use.

Figure 2 – Description of each component.

2.3. TRUDRIVE™ SE PARATION

Igniter 3™ will come by default with the TruDrive™ attached to the main board. If it is desired to have the
TruDrive™ separate from the main board for the install, then you can detach the two boards.

Separation is much easier than with previous board versions and can be performed by hand or with a small set of
needle nose pliers or forceps. Make sure to keep pressure off the middle of the board; hold it in your hands by the
two edges.

It is important to note that once the board has been removed it cannot go back on; plan accordingly before
separating the boards.

3. WI RING D IAGRA MS

The following diagrams are the most common to get your board up and running.

Note: It is very important that the correct resistor be used between the negative pad of the LED and C1-, C2-, C3­and C4- to prevent burning out the LED for warm color LEDs. For Rebel LEDs if a red, red-orange or amber LED is
used, then a 1ohm 1watt resister is needed. For any other Rebel colors a resistor is not needed. The STTH2L06
diode can be used in place of the resistor and it is a slightly smaller part.

3.1. BASIC WIRING

This is the most basic wiring that is possible to get the board up and running. It is great for testing your Igniter 3™
on the bench, or if you are doing a simple install into a saber that will have a removable battery. However, to
experience the full features of Igniter 3™ it is highly recommended to use an RGB LED, as shown in the diagrams
below.

Page | 9

Figure 3 – Basic wiring for Igniter 3™. This will drive a single main LED and would require a removable battery for charging. Note that a

resistor between the blue wire and C1- of TruDrive™ would be needed if the LED is red, amber, or red-orange.

3.2. RGB WIRING

The preferred setup of Igniter 3™ is to use an RGB LED. This allows the use of all the popular Igniter™ specific
features, such as separate colors for clash/lockup and blaster, ClashShade™, BlastShade™, and BladeShade™, and
the popular feature Saber Dual Phase™, among many others.

The recommended LED to use with this setup is the NECree RGB LED that is sold right from our store! This LED was
specifically designed to have the brightest possible colors throughout the entire color range, producing the most
even blade possible from an in-hilt LED.

http://saberigniter.com/NECreeRGB.aspx

The following diagram shows the NECree RGB wiring

Page | 10

Figure 4 – Wiring up Igniter 3™ with the NECree RGB LED. This setup uses RGB wiring and allows for full color-mixing for main blade and

blade effects. Notice that the diode for the red is built-on and thus no external resistance is needed!

3.3. RGBW/RGBA/RGBX WIRING

With Igniter 3™ a fourth die can be utilized for even more flash effects, and even more main blade colors! The
following diagram shows a Cree XML RGBW, which is the recommend RGBW LED to use

https://flipelectrical.com/products/led-world-10w-cree-xlamp-xm-l-rgbw-rgb-white-color-led-emitter-4-chip­20mm-star-pcb-board

Any combination for a fourth die could be used. For instance, an RGBA LED would allow for very rich purples not
previously available under the standard RGB color mixing model.

Page | 11

Figure 5 – Cree XML wiring that uses four unique colors instead of doubling up on one color. This setup allows for more varied colors but is

not as intuitive to get correct color mixing. Also, while an RGBW was used only the RED die needed a resistor/diode; if an RGBA is used a

second resistor would be needed for the amber die as well.

3.4. COLOR CHANGI NG CRYSTAL WIRING

With the advent of color mixing many people are wanting a blade matching crystal chamber to go along with their
build. If you want to experience this thrill, then look no further! The following diagram shows how to get this LED
wired and working.

Note: This diagram is only for in-hilt LEDs; Pixel installs need to use a single pixel LED for the chamber LED.

Page | 12

Figure 6 – Wiring with an RGB crystal chamber. This will have an RGB led that matches the blade color and pulses with the blade. Note that
all 3 pins have resistors for the small LED, and power does come from the battery. I recommend a 1ohm for R2 (x2), and a 22-33ohm for R1.

3.5. X-SABER WIRI NG

The following diagram shows the wiring of the X-Drive module with the Igniter 3™. This is the same wiring as for
the Spark Color 2 as well. Three NECree RGB LEDs are shown; standard tri-Crees could be used as well, but those
would require resistors/STTH2L06 diodes for all three red dies, so of course the NECree RGB is much easier.

Page | 13

Figure 7 - X-Saber wiring using the XDrive module, and three NECree RGBLEDs

After wiring this feature, not only does X-Saber need to be enabled in the master config, but also c4Percent should
be set to 95, and for each font C4COLOR, C4BLST, C4CLSH, and C4DUAL should be set from 100-255 for each font
that the side blades are desired to be on. Note that varying the value and setting to zero for any of these can have
the side blades off for different effects and fonts.

3.6. PIXEL STRING WIRI NG

Igniter 3™ fully supports Pixel string blades, aka WS2812B, out of the box! All that is needed is a separate SD card
with the string blade /dat and /appNN files. These strings are not only super bright, but they also support
Extension and Retraction Flow, allowing for super-realistic growing and shrinking blades, and Impact Blast™, the
ability to replicate bolts hitting the blade in defined spots.

The Pixel strings are quite easy to work with as there are only 3 wires coming out of each strip. When using the
5mm LEDs, these 3 wires are exactly what will be needed. When using the 144 led/meter strips, the three
connections will need to be run in parallel for each strip to light in the same way as the others.

The recommended Pixel string is the IntelliBlade sold here by Naigon’s Electronic Creations:

http://saberigniter.com/IntelliBlade.aspx

NeoPixel blades can also be built from the 144 led/meter strips:

Page | 14

https://www.adafruit.com/products/2969

or by building a blade from 5mm NeoPixel individual straw-hat LEDs:

https://www.sparkfun.com/products/12999

To see how awesome these look, check out the release video here:

https://www.youtube.com/watch?v=nP17IWlQS6M

IMPORTANT – Because the Pixels use a completely different driver system, the #2-#4 pins are used as simple

grounds when using a string blade. This means that if you want to wire a blade matching crystal chamber, you will
need to use a NeoPixel individual LED wired in parallel with the main blade. Rumble motors are thus not
supported.

Figure 8 – Wiring of the NeoPixel string style blades. When using the triangular prism or doubled 144 led/meter strips, make sure to wire all

3.7. FULL WIRING WITH ACCENTS

The following diagram shows how to wire all accent LEDs and the recharge port, which will utilize every feature of
Igniter 3™ (except for C4-). This will be the typical diagram for most folks that are looking for a build that utilizes all
the great features of the board without overly complicated wiring. Note that the accent pads 4-8 are in the middle
of the bottom of the board and require 28-30 gauge wire and surface type soldering (strip a small bit of insulation
from a solid core wire and push it through the accent LED hole from the top side and apply solder on the top of the
pad on the bottom side to seal).

three in parallel.

Page | 15

Figure 9 – Full wiring using all accent LEDs and a recharge port/kill key combo. This wiring will allow most features of Igniter 3™ to be

experienced without getting into super complex wiring. Note that the resistor/diode is needed for the red color.

3.8. DUAL SPEAKER SETUP USING MAX AMP™

With Igniter 3™, a MaxAmp™ audio amp is integrated on the main board. However, if you want to get clear bass
sounds with a dual speaker setup, then using the MaxAmp™ in conjunction with the on-board amp allows a dual
speaker setup that will provide the best sound a saber can produce. And, since this is running two MaxAmp™ amps
at once you can be assured this would be the loudest saber setup short of using wiring the saber directly into a
receiver.

The below diagram shows the full wiring with two speakers that utilizes the low pass filter to allow only the bass
tones through to the bass speaker. This can be omitted if desired, though the best sound when using two speakers
is using this filter.

Page | 16

Figure 10 – Full MaxAmp™ wiring that allows a subwoofer setup for great low tones! Note that both C1 (10uF capacitor) and R1 (1ohm,

1/4W resistor) are included with purchase of the MaxAmp™.

4. CONFIGURATION EDITING

Once Igniter 3™ has been wired according to the wiring above then it will work immediately with the default
configuration. However, changing the fonts and effects is completely possible and encouraged by using the
Igniter™ Config Editor. The following section will go through installing and using the editor to modify Igniter™
configuration.

4.1. INSTALLATION

To install the application, launch the .msi file from the installer zip file. You can get the file from SaberIgniter.com.
A version is also included on the micro SD card that came with Igniter™, but I recommend going to the site to get
the newest version in case any enhancements have been made to the program. Click through the wizard until the
application launches.

4.2. COPY FILES TO YOUR MACHI NE

Before opening Igniter™ Config Editor you will need to copy the files you want to edit from the micro SD card to
your local computer. First, insert your micro SD card into your computer using your SD card reader. If you do not
currently have one, I recommend this cheap one off eBay: Micro SD card.

Page | 17

Then, open a new window and find a place to put a new Igniter directory. In this example the Igniter directory will
be placed right on the root c:\ drive. Create a new directory and name it “Igniter”. Then, inside that directory,
create another folder with the name of your saber. In this example, “Saber1” will be used.

Now, with both the Saber1 empty directory open and the micro SD card opened, select all the files from the micro
SD card, and drag them into the Saber1 directory. When done, all the files should be copied to your hard-drive as
shown below.

Figure 11 – After creating a new directory called “c:\Igniter\Saber1”, the files are copied from the micro SD card (on the right) to the new

Saber1 folder (on the left). From here edits can be made to the files from the config editor.

4.3. LAUNCHI NG THE APPLICATION

To launch the config editor, you can use either the desktop shortcut that was created, or you can use the shortcut
from the Start Menu. Once launched you should see the program as below:

Page | 18

Figure 12 – Igniter™ Config Editor launched after installation.

You can then go to File->Open, and the open dialogue will appear. Navigate to the “c:\Igniter\Saber1” folder and
then go into one of the fonts to edit. When you see the config.ini appear in the window, double click it or select it
and click open to load the program for editing this font.

Page | 19

Figure 13 – Navigate to “c:\Igniter\Saber1” in the window, and then one of the font folders (font1 – font9) to edit. When you see config.ini,

double click it to open editing for the font.

4.4. CHANGING SOUNDFONTS

Changing soundfonts was never easier with the enhancements to the config editor in R5. With the auto-sync of the
app open you can switch fonts easily even when directly editing a font in the config editor. You also swap the font
before opening it for the first time.

To copy a new sound font, first go to the font that you want to change. In this example it will be
“c:\Igniter\Saber1\font1”. Navigate to that directory in explorer and then select both of the .wav files (font.wav
and multi.wav), and all the wav folders. I find the easiest way to do that is to select all (edit->select all or ctrl+A),
then hold control and click the config.ini and accent.ini files (along with the backup folder if already present) to
unselect those files. Then you can delete the original files to the recycle bin. Make sure you have a separate
backup of these waves before doing this.

Page | 20

Figure 14 – Delete the existing font by selecting all the files, then hold control and uncheck ‘accent.ini’, ‘config.ini’, and ‘backup’ if it is

present. Then the selected files font.wav, multi.wav, and the wav folders can be deleted or cut and pasted into a backup location.

After the wav files are removed and all that is left is the config files and backup folder, you can copy in all the new
wav files from a new font. You can find these from online saber sound websites, and there are some free ones
available from my website as well: http://SaberIgniter.com/fonts.aspx.

Once the files are copied, then either open the font in the config editor, or if the config editor was already opened
to this font, simply switch back to the config editor, and it will auto-sync the font numbers from disk, and it will
auto-convert them to 22050Hz, mono with appropriate headers!

Page | 21

Figure 15 – After making changes on the disk simply switch back to the app and it will sync with the correct numbers. In this case the

blst05.wav was deleted, but this will even work for swapping out an entire font.

4.5. EDITING SETTINGS

With the file open, you have access to all the configuration settings from Igniter™. With Igniter™, complete editing
of all parameters is available. This allows a completely customizable experience from font to font and saber to
saber, though it does mean a lot more tweaking of settings to get a saber working to one’s liking. The settings in
the Config Editor are logically grouped by tabs that correspond to the high-level feature. It is best to open a font
and get familiarized with all the settings before doing any editing. Clicking any individual setting will show a
description in the Description textbox below the Ignite-ulator™. Further, for any setting where the text is in red
changing the value will show the change in Ignite-ulator™.

After any edits are made, simply go to File->Save to ensure that all the changes are written back to the config. The
Config Editor will prompt before trying to open another font or close the program if there are changes that are not
saved.

Tabs are used to group individual settings into a high-level feature, helping to logically separate the changes that
are made. The following subsections document each high-level feature and what changes it makes to the saber.

4.5.1. MASTER

Master settings control features related to the overall saber. These are settings that are not font specific and
remain the same for every font. The most important settings in this section are C1PERCENT, C2PERCENT,

C3PERCENT, and C4PERCENT. These control the drive percentage for C1-C4 dies. These can be adjusted

Page | 22

individually; however, the easiest way is simply to pick the dropdown for the LED being used and it will be auto­populated.

Figure 16 – Master settings in the config editor. Use the top dropdown to auto-set the 4 drive parameters below. Also set if the main switch

is momentary or latching, and if the boot sound is being used.

The rest of the settings are described as follows:

ORIENTATION sets which rotation direction advances to the next font and which moves to the previous, along

with setting which direction is up or down. Orientation is assuming that the SD card holder is facing towards the
pommel; if the board is reversed then consider the reverse mapping for this setting.

X-SABER is used to enable or disable delayed ignition secondary blades.

REVERSE RED/GREEN can be enabled to fix certain NeoPixel LEDs where the red and green colors are swapped.

MBUTTON defines if the main button is either latching or momentary. If set to latching, do not enable SWAP
BUTTONS, as that is only supported for two momentary switches.

SWAP BUTTONS is used to swap which buttons are main and aux. This is especially useful if the two buttons are

inside a control box, as it allows the top/bottom button to be whichever the user prefers. Think of this as look
inversion for console shooter games.

Page | 23

When USE BOOT SOUND is enabled, the default boot.wav from the root will be played. Disabling this setting will
boot with the first sound font’s font.wav.

LOWPWR defines the length in seconds before the saber goes into Low Power mode, which is where the accent

LEDs shut off and the motion for the menu is disabled. Handy for cons as it saves a lot of power when hanging on
the belt since the accents drain a lot of power. Setting to 0 disables the feature so that the accents and motion do
not turn off.

NSTRP sets the number of LEDs in the NeoPixel string blade that is being used. This allows the timing to be correct

for the Extension and Retraction Flow effects. When using an in-hilt LED, this setting is not used.

4.5.2. BLADE EFFE CTS

The blade effects tabs contain settings for the blade’s pulsing scheme, along with the settings for the extension
and retraction effects.

ACTIVATION TYPE can be used to determine how the current font can be activated. The four choices are button

only, button + slash, button + twist, or all three.

Figure 17 – The Blade Effects tab in the Config Editor contains settings for the blade plusing along with the extension and retraction effects.

Page | 24

The values for MINBRIGHT and MAXBRIGHT can be used to adjust the depth of the pulse/flicker. Set these close
together to have a more subtle effect for a static blade, and set them farther apart for a more pronounced effect.
Unless a single die LED is being used MAXBRIGHT should be 98 or 99.

The values for MINPULSE and MAXPULSE control the pulse/flicker of the effect. Setting them closer together will
make more of a pulse and farther apart will make more of a flicker. Use these with the MINBRIGHT and

MAXBRIGHT in the Ignite-ulator™ to see in real time how the settings adjust the blade.

The values for INLEN and OUTLEN set the length of the blade effect for retraction and extension respectively.
Setting these to 0 will auto-detect the length of the sound file and match the blade length to the file, allowing for
varying file lengths to work perfectly!

Set INCURVE and OUTCURVE to adjust the overall speed of the effect. Lower values make the effect linear; higher
values make the effect more curved in nature, making the extension faster at the beginning and retraction faster
at the end.

4.5.3. BLADE COLOR

Figure 18 – Blade Color tab adjusts the main blade colors along with the bladeShade parameters.

Page | 25

Adjust the main blade color with these settings. Use the Ignite-ulator™ to check for which color is currently set.
Note that it is always assumed that blue is C1, green is C2 and red is C3; make sure when doing the install to set it
up this way or the colors will be mixed up.

BLADESHADE™ can also be adjusted from this tab. Setting this to zero means that every time the blade is turned

on it will be the exact color as set. Setting it to higher values will vary the color around the chosen color. Note that
for any color that is zero it will not be sampled; make sure to set the color values to one for any die that should be
considered for BLADESHADE™.

4.5.4. CLASH

The Clash tab contains settings for the clash color and ClashShade™, the Clash flicker effect, and a couple other
settings related to the clash and lockup features.

The LOCKKUPTYPE sets if after the Lockup is engaged if the button needs to be held, or if a simple tap will turn it
off. This is true both when Lockup was entered from the double tap and the EzLockup™ functionality.

The LOCKCTYPE sets if the Lock color mirrors the clash color or the blade color. The latter allows for a more

realistic experience when doing the EzLockup™, but the former works well for demoing or showing off colors at

cons.

ALTERNATING CLASH toggles the new Alternating Clash feature. When enabled, the low clash color will be that of

the blade, instead of alternating between a high and low value of the clash color.

The four settings C1CLSH, C2CLSH, C3CLSH, and C4CLSH contain the settings for the clash color. Set these values
and use the Ignite-ulator™ to see the color chosen by hitting the Lock button. Note that even if LOCKCTYPE is set
to Blade the Lock button will still show the clash color to be able to choose it correctly.

The values for MINCLASH, MAXCLASH, MINCLASHLEN and MAXCLASHLEN all effect the clash flicker effect. The

MINCLASH and MAXCLASH set how dramatic the effect is; bigger gaps will make it more dramatic. MINCLASHLEN

and MAXCLASHLEN set how quick the flicker is, where smaller values make it much quicker. Use the Ignite-ulator™
while playing with these values with Lock set to see how the effect is adjusted. As with the blade effects, it is
recommended to set MAXCLASH to 98 or 99.

CLSHLEN simply sets the length of the clash flicker. The blade color change is independent of the length of the

sound.

CLSHWAITLEN sets how long to wait before the effect can be interrupted. High values mean that once a clash is

performed a swing cannot interrupt; shorter values will allow swings to come in right after the clash happened.

BLOCKLEN sets how long the aux button needs to be held before a lockup effect is triggered. Recommended is

1000ms (1 second) as any shorter makes it tough to pull off the MultiPhase™ functionality by holding the aux
button and then performing the Dual Phase™ motion.

Page | 26

Figure 19 – Clash settings tab contains clash color settings, clash flicker effect settings, as well as a few other settings for clash and lockup.

4.5.5. BLAST

The Blast tab is similar to the Clash tab but for the Blaster Block effect. C1BLST, C2BLST, C3BLST, and C4BLST

effect the colors in the same way. BlastShade™ sets the color variance, and like BladeShade™ and ClashShade™ it

will not vary any die that has a value of zero.

BLSTLEN is for the length of the blast effect in milliseconds. This sets the blade length independently of the length

of the sound.

BLWAIT allows some padding after the blast sound is completed to still perform the EzBlast™ move. Setting this to

100-200ms is recommended to allow some time to do the moves.

NIMPACTBLST sets the range for the Impact Blast effect when using string blades. Set this as the distance from the

center of the blade in which you wish the blast to occur. Setting to zero will perform the legacy blast. This setting is
ignored when not using a NeoPixel string.

Page | 27

Figure 20 – The Blast tab contains color settings and blade effect settings for the Blaster Block feature.

4.5.6. AUDIO

The audio tab has some settings related to the audio and audio related features.

Saber Cinema™ can be enabled on a per-font basis from this tab. Make sure to have at least one trckNN.wav file
when using this feature.

Linear mode can be selected here for both the hum/in/out effect and for the actions (it can be set for the FX
feature in the FX tab). Setting to linear means that each type of sound is played in numerical order, as opposed to
being randomly selected each time. Enabling allows for great demoing ability of the sound font, and ensures that a
different hum will be selected each time if enabled for them.

HUMSTART sets the time when the hum will start mixing in with the outNN.wav sound, as a reverse offset in

milliseconds. For instance, if the outNN.wav being played is 2 seconds long and humStart is set to 500ms, then the
hum will start mixing in at 1500 milliseconds, which is 500ms before the end of the out wav sound. This allows for
a consistent experience with varying length out sounds.

The two volume settings are pretty straight-forward. Higher settings will make louder volumes. Now the values are
in true 1/16 increments, allowing perfect fine-tuning for any speaker. Recommended is 15 for effects and 8 for the
hum, but it’s dependent on the speaker.

Page | 28

TRCKSTRT (Track Start) defines the track that will be started first when playing tracks from this font. Since tracks

all live on the root this allows customization of the starting one per font.

Figure 21 – Audio settings tab allows the enabling of Saber Cinima™ for the current font, along with turning on the Linear feature for hums

and actions. It also contains the volume settings, and the setting for when the hum should start mixing in with the out sound.

4.5.7. MOTION

The motion tab contains a few simple settings for the on-board motion detection of swings. Use the thresholds to
set how easy/hard of a swing is required to register a swing and slash sound respectively. The swngWait is used to
set the swing sensitivity; lower values allow for quicker swings but can produce two swing sounds for one really
long swing; higher values will always make one swing sound but really quick swings may be missed. Recommended
is 300-500ms.

4.5.8. FX

The FX tab controls all the settings related to SaberFX™.

The Is Linear SaberFX™ setting enables the linear mode. Similar to the linear mode for actions and hum/in/out this

setting when enabled will play the FX sounds in numerical order as opposed to randomly sampling them. This
allows for re-enacting special scenes when using voice sounds, as the dialogue will be in the on-screen order.

Page | 29

FXSWNGOVRD will disallow the FX sound to be overridden with a swing when it happens. Enabling this means that

swings will not be allowed when the FX sound is playing. This works really well for action-based FX packs like the
Robot Armada pack that can be downloaded from my site.

FXHUMPER is the setting for how likely a sound will play when the saber is sitting still. Setting it 99 means a sound

will always play every 2 seconds; setting to 0 means it will never play. Setting to 50 will be small 5-10 second
pauses or so between sounds, but it is random so it could be longer or shorter. Recommended is 10-20 percent.

Similarly, FXPER is the setting for the likeliness of the FX sound being played after an action (swing does not count
as an action for FX). Setting to 100 means it will happen after every action; setting to 0 means it will not happen.
Recommended is 63, or about 2/3 of the time after an action.

FXIDPER is the new value for the probability that the sound will play in the idle menu. Setting to non-zero will

allow the FX sounds to play in the idle menu when the saber is not running for this font. 100 means it will always
play every 2 seconds; setting to zero means it will not play in the menu.

Figure 22 – The FX tab contains all the settings for the FX feature.

4.5.9. DP

The DP tab contains all the settings for DualPhase™. This is the exciting feature that allows a blade color switch

within a single font.

Page | 30

DPMODE sets if DualPhase™ uses the classic mode that switches between two colors, or the lock mode that

transitions into the new color until the AUX button is pressed. The latter is great for having a door-cutting feature.

The values C1DUAL, C2DUAL, C3DUAL, and C4DUAL control the color of the effect. Use the Ignite-ulator™ and
press the DP button to see this color. Also note that this color is affected by the BladeShade™ setting.

DPLEN controls the length of the color transition for the feature. Setting to 0 will actually select the length as the

dualANN.wav (or dualBNN.wav depending on the current color) to allow for a great transition with varying sound
lengths. Any other value is an actual time in milliseconds that the transition will take.

GXTHRESH sets how much twist is required to activate the feature. 20 means a very tiny twist will active it

whereas 120 and upwards require a very hard twist. Recommended is 90.

GYZTHRESH sets how much motion in the other directions is allowed to still call it a twist. Lower values mean that

no variance is allowed and the saber must be still while twisting. Higher values can even allow a partial swing when
twisting. Recommended value is 60.

Figure 23 – The DP tab is for the DualPhase™ feature. Control the color and other settings for this feature from this tab.

4.5.10. MP

Page | 31

The MP tab controls the enhanced MultiPhase™ feature. This is the exciting feature that allows shifting between
the fonts while the saber is running, switching the hums and colors! This allows every blade color and hum to be
used with every other font’s effects, allowing the broadest range of sounds and colors on any saber board.

Figure 24 – MultiPhase™ settings shown in the MP tab. Note that mpType, mpDir, and mpHum are global settings and will be the same for

every font.

MPTYPE sets what type of sound is used when doing the MultiPhase™ action into the next/previous font.

multi.wav will use the mult.wav from the font that the transition is going into; DP will use the dualANN.wav sound

for the font that is being exited.

MPLEN sets the length of the blade effect transition in milliseconds. Similar to the DualPhase™ length, setting to

zero will allow the length to be determined from the multi wav sound.

MPOSET allows the hum to stop playing for a short period, allowing for the multi sound to be more pronounced.

This is a reverse offset like the HUMSTART variable.

4.5.11. ADVANCED

The Advanced tab is used to help adjust the mix of colors for an LED, specifically for LEDs like the X4 where one
color is doubled up. For these LEDs where one color is stronger than the others, they may cause separation during
the retraction effect. To fix this, use these sliders.

Page | 32

For example, if a red and green mix is getting redder near the end of the retraction, then the red needs to be
turned down. This is true for the other colors as well; if any mix of two colors turns more towards one color then it
needs to be turned down a bit. If a value is already below 15 then it may be that the other two need to be turned
up.

4.5.12. ACCENT

The Accent tab is used to control all the accent LEDs. Use the AccentMode dropdown to select the accent pattern
that is currently being edited. Once that is selected, choose the desired AccentType and nLeds for this font. Finally,
the values can be adjusted accordingly.

The values work as follows, with all values being in milliseconds unless noted:

a. For the blinking effect, the top value is for the ON duration of that LED, and the bottom value is the off

time for that LED. Each LED has a completely independent on/off time that controls only that LED.

b. For BarGraph mode, the top value sets the length that an LED will be on once selected. Think of these

almost like percents; if using 4 leds and setting 10, 10, 30, 50 respectively then 50% of the time they will
all be on, 30% of the time 3 of the 4 will be on, 10% of the time 2 will be on and 10% of the time one will
be on. Further, since these are milliseconds it means that all four will be on for about 50 milliseconds in a
row before a new number is chosen.
The bottom values are different in that they mark the beginning and end of the graph. For example, when
using 8 leds and setting #2 and #7 on the bottom to 1 this will mean that the first LED will always be on
the last will always be off. Note that there should always be two 1’s and the rest zero on the bottom row
for this effect.

c. For all other effects, the top row is the amount of time that the sequence for that LED is on, but the

bottom row is how long all the LEDs go off before going to the next LED. This allows for making patterns
sparse.

The best way to really understand any of the effects is to use the above as a guide and just play with them in the
simulator.

Page | 33

Figure 25 – Accent settings. Use the Accent Mode dropdown to adjust the current mode’s settings. Make sure to use the dropdown for each

type to set all the patterns.

4.6. FORMAT MICRO SD

It is important to format the micro SD card before putting the modified config and sound fonts back on the card.
Starting with a clean card will ensure that there are no extra files and that the file chunks are contiguous on disk.
This will allow the fastest possible access times for the card. FAILURE TO DO THIS CAN RESULT IN CHOPPY

AUDIO AND A LESS SMO OTH EXPERIENCE.

To format the card, I highly recommend SDFormatter as it does a better job of formatting than Windows.

https://www.sdcard.org/downloads/formatter_4/

After installing, run the program to launch the main window.

When the format window pops up, choose FAT32. Enter the name for the card, and then click Format. After a new
window pops and shows the progress, the card will be formatted.

Page | 34

Num of Blinks

Error

2 Bad card, empty card, not formatted

Figure 26 – After the format window pops up choose FAT32, select your card name, and click Format to get the micro SD card ready to load

the modified fonts and configurations.

4.7. COPY FILES BACK T O THE MICRO SD

To copy the files back, simply move all the files from the “c:\Igniter\Saber1” directory to the root of the micro SD
card ONE FOLDER AT A TIME. This will ensure that the files are written well and can be accessed quickly by
Igniter 3™. If you try to copy everything at once they may get written in an incorrect order on disk and access times
can suffer, causing a jerky experience. Once this step is done the micro SD card is ready to be loaded back on to
Igniter 3™ to enjoy the new settings and fonts!

5. ERROR CODES

Igniter 3™ comes equipped with an on-board SMD error LED, which blinks to indicate certain SD or read failures,
making install a snap. When an error occurs, the led will blink a certain number of times, and then will pause for 1
second. Getting the number of blinks can then be used to determine the failure, by using the table below.

The following table shows the number of blinks and which error it represents. Errors in red are fatal errors and the
board will not be responsive until it is power cycled.

Page | 35

3 DAT not found

4 Boot wav not found

5 Main wav read error

6 Config file not found

7 Effect wav not found

8 Effect incorrect format

9 SD card locked

Figure 27 – Error code table to use when receiving an error-code from the on-board error SMD LED. Errors in red are fatal and the board will

Entry

Label

Action

Description

Main button

MAIN+/-

Press/Latch

Pressing the main button (latching when it is a latching switch)
puts the saber into running mode

Aux button

AUX+/-

Press

A single press plays the current font; multiple will advance to
the next font(s).

need a hard reset after receiving one of those.

6. SA BER OPERATION

To use your saber, with the micro SD card inserted and the wiring correctly completed, insert the battery or pull
the kill key. You should hear the boot sound or first font sound play (depending on the config setting), and you
should also see the first accent LED blinking rapidly. After this your saber will load into idle mode for the first font.

There are three main modes of operation for the saber: Idle mode, Running mode and Saber Cinema™ mode.
These two modes will be discussed in detail in the next sections.

6.1. IDLE MODE

Idle mode is when the saber is loaded for a font but not running. This is where the accent LEDs are running the idle
pattern, and the saber is ready for use. In this mode there are two ways to interact with the saber. The first is
hitting the AUX button to advance to the next font. When you are on font three, hitting AUX goes back to font1.
Igniter 3™ always assumes that there are 9 fonts present on the config card unless configured otherwise, so make
sure they are always present on the micro SD card.

Another way to interact with the saber is by hitting the main button. This puts the saber in running mode. For
more details on that see the next section.

The final interaction that is possible in idle mode is to hold the saber pointing straight down, and holding the aux

button. This will enter Saber Aps™, the exciting new mode where multiple different applications can be run on the

saber!

6.1.1. IDLE MODE INTERACTION TABLE

The following table lists all the interactivity that is possible with the saber while in idle mode.

Page | 36

Aux button

AUX+/-

Hold

Engages Saber Cinema™ for the font if one is enabled; nothing
if Saber Cinema™ is not configured for the current font

Aux/Main
button

AUX+/­MAIN+/-

Hold +
Press

Holding the aux button and pressing the main button within
one second will activate EzMute™.

Rotate Saber

NA

Rotate

Rotating the saber is the new EzOn™ motion that will turn the

saber on. Note that once in low power mode the aux button
will need to be pressed before the saber can be turned on
again.

Aux button

AUX+/-

Hold + Point
down

Holding the aux button while the saber is pointing down will
enter the Saber Apps™ menu.

6.2. RUNNING MODE

Entry

Label

Action

Description

Aux Button

AUX +/-

Press

Pressing the aux button engages Blaster Block mode. Once in

this mode, swinging the saber will perform EzBlaster™, where

another Blaster Block will be performed. Keeping the saber
still will cause the mode to exit.

Aux Button

AUX +/-

Hold

Taping the aux button twice is the second way to engage the
Lockup effect; the primary way is by EzLockup™ - tapping the
aux once after performing a Clash. Depending on the chosen
config setting, either releasing the button or tapping it again
will cause the mode to exit.

Aux Button

AUX +/-

Press (in
Clash)

Pressing the AUX button will perform EzClash™; immediately

after the press the Lockup sound will play when in Clash
mode. This is the preferred way to perform a clash on
Igniter™.

Swing saber

NA

Swing

Swinging the saber causes a single swing sound to be played.
If the swing is performed rapidly then a Slash sound will be
performed.

Rotate saber

NA

Rotate

Rotating the saber will engage the Dual Phase™ mode of the

saber, allowing the saber to switch between colors. If Dual

Phase™ is not enabled for current font then a swing will be

played.

When the saber is running, there are many actions that are possible. Swings, Blaster Blocks, Clashes, Lockups and
retraction all become available. Further, this is when the main LED runs and accent LEDs follow the patterns for the
actions performed. A detailed description on how to interact with the saber is given in the following subsection.

To stop the saber from running, simply hold down the main button (unlatch if it is a latching switch) until the
retraction sound and effect occur. The saber will then return to Idle mode. From here you can re-insert the kill key
or remove the battery. Do not remove power when the saber is running, as this can cause the micro SD card to get
corrupted, and then it would need to be reformatted. Granted this is very rare but it is better to put the saber into
Idle before disconnecting the power.

6.2.1. RUNNING MODE INTERACTION TABLE

The following table lists all the interactivity that is possible with the saber while in Running mode.

Page | 37

Rotate saber +
Aux button

NA
AUX+/-

Rotate
Hold

Holding the Aux button and then performing the rotation
action will engage Multiphase™. Rotation clockwise/counter
clockwise will go forward and backwards through the fonts.

Hit saber/Blade

CS

Clash

Hitting the saber against something or hitting your hand on
the hilt will cause the Clash sound to play. To return to
running simply wait for the clash to finish.

Main Button

MAIN+/-

Hold/Unlatch

Holding or unlatching the main button will cause the
retraction sound to play and then the saber will return to Idle
mode.

6.3. SABER CINEMA™

Entry

Label

Action

Description

Aux Button

AUX +/-

Press

Advances to the next track. When the last track file is reached
it goes back to the beginning.

Main Button

MAIN +/-

Press/Latch

This button will activate the saber, allowing you to have full
light saber capabilities while the saber is running.

Main Button

MAIN +/-

Hold/Unlatch

If the saber is running it will put it back into normal Saber
Cinema™ operation with the music playing.

Aux Button

AUX +/-

Hold

Puts the saber back into normal idle mode for the current
font.

Entry

Label

Action

Description

Aux Button

AUX +/-

Press

Advances to the next app. When the last app file is reached it
goes back to the beginning.

For any font with Saber Cinema™ engaged, holding the aux button for one second will engage the Saber Cinema™
player. Once Saber Cinema™ is engaged, the interactivity will be as described in the following subsections.

In Igniter 3™, all the tracks files are stored off the root in the /TRACKS folder. This means that ever font will be able
to play the tracks, so it is not required to navigate to a certain font to play tracks. However, to allow for a
customizable experience for each font, the starting track can be selected by using the TRCKSTRT parameter. See

4.5.6 Audio for more info.

6.3.1. SABER CINEMA™ INTERACTIVITY

The following table describes the interactivity for Saber Tracks.

6.4. SABER APPS™

Saber Apps™ is the exciting way to run multiple different applications on your saber. This opens up an entirely new
experience that was never before possible with sabers, allowing apps for configuration, games, and even new

saber experiences. Many apps; one Igniter™.

To enter the Saber Apps™ menu, simply point the saber down and hold the aux button during the menu of any
other app (except for the Motion Editor app, which automatically goes back to the Saber Apps™ menu when the
configuration is saved). You will then hear the “Saber apps menu sound”. Operation of the Saber Apps™ menu is
very similar to the normal Igniter™ menu. The interactions are shown in the table below.

Page | 38

Main Button

MAIN +/-

Press/Latch

This will enter the current app.

6.4.1. COLOR EDITOR

Entry

Label

Action

Description

Aux Button

AUX +/-

Press

Advances to the next font.

Main Button

MAIN +/-

Press/Latch

This button will activate the saber for editing.

Aux Button

AUX +/-

Hold

Plays the instructions.

Aux Button

AUX +/-

Hold + Point
down

Enters the Saber Apps™ menu.

Entry

Label

Action

Description

Aux Button

AUX +/-

Press

Increments/decrements the current color value by 10.

Aux Button

AUX +/-

Hold

Changes between incrementing and decrementing.

Swing saber

NA

Swing + Hold
Aux Button

Change the action being edited between: Blade, Clash, Blast,
and DualPhase™.

Rotate saber

NA

Rotate

Rotating the saber will change between the 3 colors blue,
green, and red.

Hit saber/Blade

CS

Clash

Increments/decrements the current color by 1.

Main Button

MAIN+/-

Hold/Unlatch

Holding or unlatching the main button will cause the
retraction sound to play and all changes made to this font will
be saved to disk.

The Color Editor is an exciting Saber Apps™ that allows editing of all the colors for every font on the saber. This
allows easy adjusting of colors selected from the Config Editor, and it even allows completely swapping the colors
without having to remove the SD card!

6.4.1.1. ENTERING COLOR EDITOR

To enter the Color Editor, make sure the saber is off by inserting the killkey or switching the master kill switch to
off. Then, press and hold the aux button and remove the kill key or flip the kill switch to on. Keep holding the aux
button until the Color Editor intro is played.

6.4.1.2. COLOR EDITOR INTERACTIVITY

The following subsections go over how to interact with the color editor.

6.4.1.3. COLOR EDITOR MENU

The color editor has a menu similar to the menu in Igniter™. This menu is used to navigate the fonts to select the

one to edit.

6.4.1.4. COLOR EDITOR EDITING

Once a font is selected the Color Editor is in editing mode for that font. From here all the changes can be made.

6.4.2. MOTION EDITOR

Page | 39

The motion editor is an app that is used to adjust the motion parameters on the fly. These parameters are used

Entry

Label

Action

Description

Aux Button

AUX +/-

Press

Increments the current motion parameter by 10.

Aux Button

AUX +/-

Hold

Plays the instructions.

Swing saber

NA

Swing

Plays the swing sound; swinging around the saber gets a feel
for the current motion settings.

Rotate saber

NA

Rotate

Plays the Dual Phase™ sound (no color change). Performing

this motion gets a feel for the current settings.

Hit saber/Blade

CS

Clash

Plays the clash sound. Performing the clash gets a feel for the
current motion settings.

Rotate saber

NA

Rotate +
Hold Aux

Advances to the next motion parameter to edit. Parameters
are Swing Threshold, Slash Threshold, Clash Threshold, GyroX
Threshold, and GyroYX Threshold respectively.

Swing saber

NA

Swing +
Hold Aux

Same behavior as rotating the saber and holding Aux; see
above.

Hit saber/Blade

NA

Clash +
Hold Aux

Same behavior as rotating the saber and holding Aux; see
above.

Main Button

MAIN+/-

Hold/Unlatch

Holding or unlatching the main button will cause the
retraction sound to play and all changes made to this font will

be saved to disk. The saber will then enter the Saber Apps™

menu.

Main Button

MAIN+/-

Hold/Unlatch
+ hold Aux
button

If the aux is held when the main is held or unlatched, then the
values will not be saved to disk, and the saber will enter the
Saber Apps™ menu.

Entry

Label

Action

Description

Aux Button

AUX +/-

Hold

Plays the instructions.

Aux Button

AUX +/-

Hold + Point
down

Return to the Saber Apps™ menu.

Main Button

MAIN+/-

Hold/Unlatch

Holding or unlatching the main button will start the game.

not only for every font of Igniter 3™ but also for every app as well.

Once in the Motion Editor, press the main button to enter editing. From there the following actions are possible.

6.4.3. SABER SAYS

Saber Says is the first ever saber game! Play alone to improve your best score, or challenge friends to an ultimate
round-robin high-score challenge. With Saber Says, your saber comes alive.

6.4.3.1. IDLE MODE

When in idle mode of Saber Says, you can play the instructions, start the game, or return to the Saber Apps™
menu.

6.4.3.2. RUNNING MODE

When the saber is running the game has started. The saber will operate like in the main firmware; however, an
increasing sequence of sounds will be played. You will then need to repeat this sequence to score and more to the

Page | 40

next higher sequence. For example, if swing, clash, swing is played, you will need to swing the saber, then clash the

Entry

Label

Action

Description

Aux Button

AUX +/-

Press

Do the blast sound.

Aux Button

AUX +/-

Hold

Do the lockup sound.

Swing saber

NA

Swing

Plays the swing sound.

Rotate saber

NA

Rotate

Plays the swing sound.

Hit saber/Blade

CS

Clash

Plays the clash sound.

Main Button

MAIN+/-

Hold/Unlatch

Holding or unlatching the main button will cause the
retraction sound to play, and the game will end with the final
score being played. This is similar to getting an incorrect
swing, but the “loser” sound will not be played.

saber, and finally swing the saber again. This will play the next sequence, which will be swing, clash, swing, plus the
next sound.

When the sequence is performed incorrectly or the main button is held, the game ends, and the final score is
played.

7. THANKS

Thanks to Kyle Miller (CJS Props), Shayé Whitmer, and Jimmy Hutson for all the testing and support during
development. You guys helped to make this the highest quality release for Igniter™ ever.

Special thanks to everyone that has supported me on this journey. It is the community support that makes this
worthwhile and gives me the passion to continue. God has really blessed me on this path, and I hope to spread His
joy back to you. Godspeed, and MTFBWY!

Page | 41

Revision History

Date

Revision

16 December 2017

Initial version for Igniter 3™.

Page | 42