Documentation for Axxon PSIM 1.0.0-1.0.1.

Previous page XML file preparation  Description of events and reactions of system objects Next page


On the page:

Attention!

After preparing the required files and before creating custom objects in Axxon PSIM, it is necessary to update the main database using The idb.exe utility for converting databases, selecting database templates and making backup copies of databases.

When the DBI, DDI and XML files are ready, the objects of a new type along with the standard objects can be created in Axxon PSIM hardware tree.

 

Custom parameters are displayed on the settings panel of the created custom objectcustom_param1 and custom_param2 in this example. Their values can be set in the table.

Displaying on the map

When an object is created in the hardware tree it can be placed on the map and set reactions can be executed in the object context menu (see Configuring the interactive map for object state indication and controlling the objects).

 

Using in macros

When a custom object is created in the hardware tree it can be used in macros.

 

Note

Reactions of custom objects are automatically converted into events. Thus, in the example, when the ON reaction is executed, the object state changes due to set state transition rules (see DDI file preparation) and the icon corresponding to the state will be displayed on the map.

Sample program in JScript to change the state of a custom object

Problem. Using macro 1 change the state of a custom object 1 to ON and display the icon corresponding to this state on the map.

Solution. As state transition rules are set, when the ON event is sent from the custom object, the state will be automatically changed to ON and the icon specified in ddi file (see DDI file preparation) to this state will be displayed on the map. A script for sending the ON event looks like this:

if (Event.SourceType == "MACRO" && Event.SourceId == "1" && Event.Action == "RUN")

{

 var msgevent = CreateMsg();

 msgevent.SourceType = "CUSTOM";

 msgevent.SourceId = "1";

 msgevent.Action = "ON";

 NotifyEvent(msgevent);

}
  • No labels