Manually Creating a Session File

• 

Session files are simply text files with a list of commands and timings that are used by Commander to run a program through a 2B. You can record a session, thus creating a session file, or load and playback a session file you have created or obtained from another source. 

We suggest you use a simple editor like notepad as attempting to use something like Word will add unnecessary formatting that may cause issues on playback.

If you don’t know where to start then have a look at a pre built session files (from our forum), or simply record your own in Commander or E-Stim Connect, then open upthe file in a text editor.

What’s in a session file?

Header

Sessions files normally start with a header block, This sets your 2B from a known state. if you are creating your own session file, at the very least set the mode. Setting a mode with automatically reset the levels and settings to the defaults. 

0.1 M0

Program

The program is made up of multiple single lines with a delay (in seconds) and a command so 

0.1 M3 

Will wait 0.1 seconds and switch to mode 3 

5.0 A10 

Will wait 5 seconds and then change the level on channel A to 10%

Changing levels

5 A10

5 A15

This will then wait 5 seconds and set channel A to 10%. 5 seconds later the level will increase to 15%. If you want both channels to closely match then 

0.1 A10

0.1 B10

5.0 A15

0.1 B15

will give you both channels at 10% and after 5 seconds both will jump to 15%. You could also use the join command, and then just adjust the level of channel A, channel B will match the level

0.1 J1

0.1 A5

5.0 A10

Remember the delay value is the time to wait before the command is executed.

Later versions of firmware allow relative level changes so A+ will increment the level on a by 1%, what ever it was. 

 

Comments

You can embed comments within a session file, as anything after a semi colon ; is stripped out.

 

Other settings

Changing feel is generally a D value, timings for pulses etc are normally a C value, but it does depend on the actual mode.

 

most session files end with a single command

K

which switches the outputs off.