Control.ini - Case Studies

Here you'll find some case studies, which will help you to understand the structure of a Control.ini file more easily. You'll also learn how you can control the show logic with different ASCII commands. ATTENTION! AFTER EACH #-CHARACTER A NEW COMMAND LINE HAVE TO BE BEGUN! The following command combination cannot be interpreted properly and therefore it will not be executed correctly: !i1c!rsn1#!i2c!rsn2# ||| ATTENTION - Before you edit your Control.ini file, please run the latest firmware update first to ensure that your device is able to interpret the latest ASCII commands.

Is there any reason why the control.ini will not be executed, although the commands are correct?
ATTENTION! AFTER EACH "#"-CHARACTER A NEW COMMAND LINE HAVE TO BE BEGUN! The follow...
Wed, 2 Sep, 2015 at 6:45 AM
Control.ini
The Control.ini file is an easy way to assign different trigger events to the ProCommander Series without any special show programming. A level chan...
Tue, 15 Mar, 2016 at 9:54 AM
Structure of the Control.ini file - Input event
Each command line of the Control.ini must always start with the definition of a trigger event. As a start condition either an "!i: Input event&quo...
Wed, 2 Sep, 2015 at 5:30 AM
Structure of the Control.ini file - Time event
It must always start with the definition of the trigger event. As a start condition either an "!i: Input event", "!t: Time event", "...
Mon, 7 Sep, 2015 at 6:26 AM
Structure of the Control.ini file - Real time clock event
It must always start with the definition of the trigger event. As a start condition either an "!i: Input event", "!t: Time event", "...
Tue, 8 Sep, 2015 at 10:15 AM
Structure of the Control.ini file - Variable event
It must always start with the definition of the trigger event. As a start condition either an "!i: Input event", "!t: Time event", "...
Tue, 1 Sep, 2015 at 11:14 AM
Structure of the Control.ini file - DMX event
  It must always start with the definition of the trigger event. As a start condition either an "!i: Input event", "!t: Time event", ...
Thu, 10 Sep, 2015 at 10:04 AM
Structure of the Control.ini file - Infrared event
  It must always start with the definition of the trigger event. As a start condition either an "!i: Input event", "!t: Time event&qu...
Mon, 14 Sep, 2015 at 5:13 AM
Example of a Control.ini file
The content of the Control.ini file can look like this: !i1c!ess1001# !i6c!edv10:255# !i2c!esd3:"Hello World"# !i3o!epf1%20<...
Tue, 12 Jul, 2016 at 9:06 AM
The first show runs in a loop and is interrupted by the second show every 45 minutes
The project consists of two show files.  The first show (001_SHOW.WM1) runs in a loop and is interrupted every 45 minutes by the second show (00...
Fri, 18 Sep, 2015 at 3:34 AM