Session Files

Session files are the files generated and used by Commander, generated by E-Stim Connect and are effectively a recording of a play session. They are a simple text file they can be created by hand as well as edited in order to refine your play session. You can also download and playback session files created by others. Our E-Stim Forum is a good source.

Recording a Session File

Both Commander and E-Stim Connect are capable of recording session files. If you wish you can also create your own Session File from scratch.


Recording with Commander

coming soon


Recording with E-Stim Connect

coming soon

What is inside a Session File?

Category: Session Files

Session files are ASCII text files with a .csf extension. Inside a session file you will find a services of lines. Each line in the file is a command, with a delay in seconds before the command is processed allowing you to recreate an entire session from a connected Computer running Commander.

A typical session file would look like

0.2 M0

0.2 L

0.2 A0

0.2 B0

0.2 C73

0.2 D71

1 A5

1 A6

1 A7

1 A8

1 A9

1 A10

Running this session file will set Mode 0 (Pulse), Low Power, Channels All Zero, C Value set to 73 D Value Set to 71, then the A Channel Level will rise from 5% to 10% over 5 seconds.

Session Files normally have a header with the initial state of the 2B stored when the session is first started. This means that sessions will always start at the same point.

Commander 4, offers the option to create a session file with no header (Menu Advanced ->Session Header) which then allows more flexibility in sessions.


Session Commands





Increment Channel A Level by 1% Commander 4 / Beta Firmware only


Increment Channel B Level by 1% Commander 4 / Beta Firmware only


Increment C value by 1 Commander 4 / Beta Firmware only


Increment D value by 1 Commander 4 / Beta Firmware only


Decrement Channel A Level by 1% Commander 4 / Beta Firmware only


Decrement Channel A Level by 1% Commander 4 / Beta Firmware only


Decrement C value by 1 Commander 4 / Beta Firmware only


Decrement D value by 1 Commander 4 / Beta Firmware only


Set Channel A Level to nn% ALL


Set Channel B Level to nn% ALL


Set C Level to nn ALL


Set D Level to nn ALL


Factory Reset ALL


Select High Power ALL


Select Dynamic Power Commander 4 / Beta Firmware only


Select Low Power ALL


Join Controls
J0 Join Off,
J1 Join On


Kill Output ALL


Set Mode ALL


Set Warp Factor Commander 4 / Beta Firmware only


Set Bias for Dynamic Power Commander 4 / Beta Firmware only


Select Output Map
0 - Map A
1 - Map B
2 - Map C
Commander 4 / Beta Firmware only


Modes numbers are basically the Mode Number you see on the screen on the 2B, minus 1, so Mode 0 is PULSE and so on. The mode will depend on which version of firmware you are using. Not all modes are available for use with Commander, and not all modes are available with every firmware

Example Modes

M0 Pulse

M1 Bounce

M2 Continuous

M3 Flo

M4 A Split

M5 B Split

M6 Wave

M7 Waterfall

M8 Squeeze

M9 Milk

M10 Throb

M11 Thrust

M12 Cycle

M13 Twist

M14 Random

M15 Step

M16 Training



Manually Creating a Session File

Category: Session Files

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?


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


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. 



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


which switches the outputs off.