startrceuid=33(www-data) gid=33(www-data) groups=33(www-data) endrce
Loading...
 

Create an initial PROSOFT file

Once the list of functions to monitor from the Control Tower is complete, you can start creating an initial PROSOFT file.
This file needs to contain:

  • The necessary hardware for all the functions that need to be monitored from the Control Tower (Relay, Dimmer, Motor modules, digital input interfaces, analogue input interfaces,…)
  • All functions to be monitored from the Control Tower (Moods, …)
  • All common configuration (e.g if input X is closed, set alarm Y ON)
  • A Control Tower client GUI. This is a GUI with only 1 page on which all the items to be monitored / controlled by the Control Tower are placed.
  • All the Alarms to be monitored on the Control Tower. For these alarms set the type to ‘Alarm’ (not to Message). Pay particular attention to the number of beeps for the alarms, the Control Tower uses this to define the alarm type. If desired the Control Tower can play recorded voice messages for critical alarms (e.g. Fire Alarm) so that even if the Control Tower operator is not looking at his screen at that moment, he can still be informed through the audio message. So give each alarm for which an audio message will be used a unique number of beeps (we advise to use high numbers of beeps for this). If the Control Tower receives an alarm with a number of beeps for which no audio message is present, the Control Tower will simply play that many beeps. Make sure that the alarm is enabled on the Control Tower client GUI.

When the initial PROSOFT file is finished, save it for the different Central Units in the project. When you start the configuration of the individual Central Units, start from this initial PROSOFT file and add whatever is necessary. Create an individual .NBT file for each Central Unit.

Switch Language

Technical Handbook:

Internal documentation

TT School