The following script format is associated with 6.5 and earlier firmware 

(originally associated with the FTH modules) 


Note: with the release of the FTQ module and 7.X firmware, modifications to the script format have been made including the additional DMX RampX attribute, DMX duration at a 1ms resolution, a two-row header, and other optional column changes.


For the latest script format, see the following article:  New 7.X fireTEK Script Details.


For simple steps to convert existing scripts to the new 7.X script format see the following article: Convert Existing Scripts to the 7.X Format 


When used by the fireTEK system, the script is loaded as a comma-separated value file or *.csv file.  The new FTQ file consists of a single-row header record that defines each value separated by commas in the script.  Each additional row or line is a separate record or scripted command. 



The tabular data is arranged in the following column order in a CSV editor or Spreadsheet:


1/A

2/B

3/C

4/D

5/E

6//F

7/G

8/H

9/I

10/J

ID

Rails

Channel

Time

Sequence

Value

Duration

Custom 1

Custom 2

Custom 3

1

1

1

4000

0

0

0

Left

Blue

Song 1

1

1

2

5000

0

0

0

Center

Red

Song 1

2

3

1

6000

0

0

0


Blue

Song 1

2

3

2

6500

0

0

0

Center

Red

Song 2

3

1

101

10204

1

255

250

Left



3

1

102

10205

1

120

250

Left

White

None

3

1

201

10206

2

120

250

Center

Red

None

3

1

202

10207

2

120

250

Center

Red

None


1. Module ID (required) - [Column 1/A]

  • It encodes the Module assigned to the event
  • Valid values are from 1 to 99
  • It is used for DMX and Pyro events
  • It is required for the scripted file to be validated


2. Rail (required) - [Column 2/B]

  • It encodes the Rail assigned to the event
  • Valid values are from 1 to 4 
  • It is used only for Pyro events and for  DMX events it should be set to 1
  • It is required for the scripted file to be validated


3. Channel (required) - [Column 3/C]

  • It encodes the Pyro Channel or DMX Channel assigned to the event
  • Valid values for Pyro events are from 1 to 16
  • Valid values for DMX events are from 101 to 200
  • To separate DMX channels from Pyro Channels, DMX Channels are identified in the fireTEK script starting with 101 for DMX Channel 1.  For example, a DMX device set to Channel 17 will be scripted as DMX Channel 117 in the fireTEK Script

Note: DMX Device Channel + 100 = fireTEK DMX Script Channel

  • It is required for the scripted file to be validated


4. Time (required) - [Column 4/D]

  • It encodes the event time, also referred to as ignition time or firing time for each event
  • The maximum duration of the script is 24 hours or 86,400,0000ms
  • The time is in Millisecond format Valid values can be from 1 to 8,640,000  (24 hours).  

Some Examples:

  • 0.25s is 250ms
  • 12s is 12000ms
  • 1 minute is 60000ms
  • 1 minute and 12.25 seconds is 72250ms
  • 2 minutes is 120000ms
  • It is required for the scripted file to be validated


5. Sequence - [Column 5/E]

  • It encodes Sequence ID
  • Sequences are groups of events that are unique to each assigned sequence number.  The individual sequences are subscripts within the main script that can be triggered individually and will fire to their unique timing. 
  • The main script that begins when the system goes into PLAY is defined by sequence 0. 
  • Scripts 1 to 99 can be triggered by separate actions from the Controller, Computer, Android, or firing module. 
  • Valid values are from 0 to 99
  • It is used for Pyro and DMX events
  • The default value is 0
  • It is required for the scripted file to be validated


6. DMX Value (required for DMX) - [Column 6/F]

  • It encodes DMX value of a channel
  • If it is used for DMX events it can have a value from 0 to 255
  • It is normally used for DMX events
  • The default value is 0, even with fireTEK pyro events
  • It is required for the scripted file to be validated


7. Duration (required for DMX) - [Column 7/G]

  • It is normally used for DMX events
  • The default value is 0, even with pyro events
  • It is required for the scripted file to be validated
  • It encodes the duration in tenths of a second for this event before the DMX Values is set to 0.   
    • Maximum is 25 seconds = 250.   (.1s X 250 = 25s)
    • For longer than 25 seconds, default Duration to zero and use 2 lines - one to start/open and one to stop/close the channel.


Note:  in the newer script released in 2020 with the FTQ module, Duration is at a millisecond resolution and there is a new DMX attribute added "RampX" to the script in front of Duration.  

For the latest script format, see the following article:  fireTEK FTQ Script Details.  


8. Custom 1 (Optional) - [Column 8/H]

9. Custom 2 (Optional) - [Column 9/I]

10. Custom 3 (Optional) - [Column 10/J]

  

The headers will default to “Custom 1”, “Custom 2”, and “Custom 3” unless you change the fields in the header record of the CSV file.  If you change them to unique headers, there needs to be data in all three fields.  Otherwise , the FTKontrol App will default back to “Custom 1”, “Custom 2”, and “Custom 3”