Help

Something does not work? Check the common problems, run the System check, or tell us: report the problem or chat with us on WhatsApp.

Ask about the manual

Ask in your own words, in any language. The answer is made from the manual, with links to the sections it used.

Not sure what to ask? Try one of these

AI answers are based on the manual; for anything about safety follow the manual and contact us.

Report a problem or suggestion

Tell us what happens, or what you would like: about the manual, a device, its firmware or the FTK Studio app. We read every report; with a contact we can answer you.

What is it about?DeviceState of the systemWhat kind of problemWhat happens (what you see on the screen, what you did before) or what you suggestFirmware version (optional, from the start screen, e.g. 0.98a)Photos (optional, up to 3)

Attach the report from the systemReport files (optional, up to 3, or one ZIP)

The show reports of the controller, the event log, a module report or the ZIP exported by the app; 8 MB together. How to get the report from your system

E-mail or phone, if you want an answer (optional) I agree that FireTEK receives this report (with the photos and the contact I added and the type of my browser) and keeps it to solve the problem and to improve the manual. To have it deleted, write to us on WhatsApp or by e-mail with its number.

Chat on WhatsApp

Write to us on WhatsApp: the message starts with the page and the device, and the report number if you sent one.

Chat on WhatsApp +40 744 671 127

Known issues

Problems we know of, with what to do. The complete list is in the troubleshooting chapter.

Common mistakes

The mistakes made most often when the system is prepared and used: how you recognise them and what to do.

Arming right after power-on, while the saved script is still loading.
How you recognise it SCRIPT LOADING / PLEASE WAIT on the status row; nothing arms, and nothing arms by itself later.
What to do Wait until the script is loaded, then turn the key switch back to TEST and to ARM again.
See §2.6, §12.8
A module or a SyncBox set to another channel or another wireless key than the controller.
How you recognise it The device never appears on the controller although it is switched on and close; Wireless Settings shows a different KEY:… CH:nn.
What to do Give all devices the same channel and wireless key (or use ADD MODULES), then restart them.
See §10.2.4, §10.2.8
A Wireless Reset or a new wireless key made on one device only.
How you recognise it After the change some devices no longer find the others.
What to do Set the same network on every device and restart all of them so they find each other again.
See §10.2.4, §16.11, §14.9
Switching on the second controller without holding SZ at power-on.
How you recognise it It starts as a main: OTHER CONTROLLER ONLINE on the main, BACKUP STARTED AS MAIN on the second one.
What to do Switch it off, then switch it on again with SZ held until the backup screen appears; accept it on the main.
See §21.2, §21.4
Pyro or DMX disabled from the menu for a test, and forgotten there.
How you recognise it Nothing fires in the show and Manual Fire says PYRO IS DISABLED; the setting stays off over the deadman, the key switch and STOP.
What to do Enable Pyro / DMX again from the menu before arming.
See §6.11, §3.7
Releasing DMS-1 in a pause and then pressing only PLAY.
How you recognise it The show stays paused; the screen asks HOLD DMS + PLAY.
What to do Hold DMS-1 and press PLAY together.
See §6.5, §13.5
Trying Manual Fire with the key switch still on TEST.
How you recognise it MANUAL FIRE BLOCKED / TURN KEY TO ARM for 5 seconds; nothing fires.
What to do Turn the key switch to ARM, then fire.
See §3.7, §2.5.1
Connecting a module that is not in the script.
How you recognise it The module page says NOT IN SCRIPT; after arming its loaded channels show the orange bolt and n LOADED CHANNELS / NOT IN SCRIPT; the show does not fire them.
What to do Add the module to the script (or give the module the ID the script uses) and load the script again before the show.
See §2.7.11, §16.4
Two modules with the same ID in the same fleet.
How you recognise it The controller shows only one of them; the other one seems missing.
What to do Give every module its own ID (1 to 99) and check the IDs against the script.
See §16.4
An igniter (e-match) wire put in the rail without closing the lever, or on the wrong channel.
How you recognise it The channel shows no igniter in TEST, or the effect fires on another channel than planned.
What to do Insert the wire, close the lever, and check every channel in TEST against the script before arming.
See §16.5.6, §2.4.1
Several igniters in parallel on one channel, on long cables.
How you recognise it A whole rail, or part of it, did not fire although the igniters were seen at arming.
What to do Wire the igniters in series and make a firing test with the same cable; use 24 AWG or thicker, 100 % copper cable.
See §16.5.7
Arming while the modules are still in Standby.
How you recognise it The controller asks WAKE UP BEFORE ARM; the module pages show the Standby state.
What to do Wake the fleet first, wait until every module is back in TEST, then arm.
See §2.7.4, §22.5
Changing the script on the controller and arming without the UPLOAD to the modules.
How you recognise it SCRIPT MISMATCH at arming.
What to do Make the UPLOAD to the modules (or use UPLOAD & ARM), then arm.
See §12.4, §12.5
The antenna of a module or of the controller horizontal, or next to metal.
How you recognise it Modules lost often (MISS, LOST), a weak signal, a module close by heard only through a repeater.
What to do Mount the antennas vertical, away from metal and as high as possible; use a repeater over long distances.
See §25.1, §10.4
No repeater designated on a large site.
How you recognise it The far modules are lost often, or missing at the arming check (MISSING MODS: n).
What to do Designate a repeater (R1 / R2) placed between the controller and the far modules.
See §10.4.1, §20.2
Taking the modules to the site with their batteries not charged.
How you recognise it The battery icon is low or blinks; modules switch off or are lost during the evening.
What to do Charge every module the day before and check the battery icons in TEST before the show.
See §16.5.1, §25.3
Skipping COLLECT MODULE REPORTS? after the show (R4).
How you recognise it After another script is loaded the question comes back once; ignored again, the report of the old show is lost.
What to do Answer R1 (or R2 with a USB stick) right after the show.
See §23.2
A music file in a format the controller does not play (a VBR or mono MP3, a 24-bit or 96 kHz WAV).
How you recognise it The music is refused with a reason (NEED 16/32 BIT, NEED 44.1/48 KHZ, …) and the show has no sound.
What to do Export the music as a stereo 16-bit WAV at 44.1 / 48 kHz or as a CBR MP3, and load it again.
See §12.9
Copying the files into a SyncBox internal memory that is not formatted as exFAT.
How you recognise it The SyncBox does not find its music or its script.
What to do Format it from SETTINGS → Format Card (exFAT; everything on it is lost), then copy the files again.
See §14.8, §14.6
A USB stick with many script or music files in its root.
How you recognise it TOO MANY SCRIPT FILES / TOO MANY AUDIO FILES, or a wrong script picked from the list.
What to do Keep only the files of this show in the root of the stick.
See §12.2, §27.18
Setting a programmed start time while the time or the time zone of the controller is wrong.
How you recognise it The show starts at the wrong hour, or not at all.
What to do Check R1 Set TimeZone and R2 Set Time first, then set the start time.
See §9.3.3
A time code source with a level too low, or at 24 / 29.97 fps.
How you recognise it WAITING FOR TIME CODE, TIME CODE LOST or TimeCode NOT RECOGNIZED; the show does not follow the time code.
What to do Raise the output level of the source, use LTC at 25 or 30 fps, and test it before the show.
See §15.3, §15.8
Expecting a START from an SSSBox whose key switch is on OFF.
How you recognise it KEY OFF at the bottom of the SSSBox screen; a press only pauses the show or blocks zones.
What to do Turn the key switch of that SSSBox to ON when it must start the show or release zones.
See §19.2, §19.6
Expecting a press on the SSSBox to stop the show.
How you recognise it The show goes to PAUSE, not back to TEST.
What to do Resume with START on the controller, or stop the show from the controller.
See §19.7
Connecting the app over Bluetooth only after arming, or counting on Bluetooth for control during the show.
How you recognise it The app gets only VIEW, or a new Bluetooth connection is refused in ARMED / PLAY / PAUSE.
What to do Connect the app in TEST; on a PC prefer the USB cable for the whole show.
See §27.4, §27.22
Skipping the test of exactly what will be used: modules, rails, music, time code, the backup.
How you recognise it Problems are found only during the show; the start-up warning OPERATOR RESPONSIBILITY reminds it at every power-on.
What to do Run the System check and test everything in TEST with the same cables and files you will use.
See §2.3, §2.4.1
Devices with different firmware releases in the same system.
How you recognise it Some functions do not work on some devices, or a device is not accepted.
What to do Update the controller, the modules and the SyncBoxes to the same release.
See §31.3

All the common mistakes (troubleshooting)

Known issues

No known issues at the moment.

All the common problems (troubleshooting)

Anonymous usage

Share anonymous usage

Once a day the manual sends which pages were opened and what was searched, counted together, to help us improve it. No name, no contact, no address, no number that identifies you.

The reports go to FireTEK only. Usage counters and answers to "Was this page helpful?" carry no personal data.