You can configure the History module by starting the program via command line and specifying some startup parameters: in particular, you can set the command line as follows:

 

History80.exe [/F<Path>] [/T<Title>] [/P] [/M] [/G] [/I]

 

The parameters above have the following meaning:


 

/F<Path>

Specifies the path in which historical data should be searched, when this differs from the standard path of recording historical data in the project directory on the local machine. If the system has one or more network stations, you must specify the network path of the folder that contains the historical data, residing on the server station (otherwise the data would be searched on the local station).

 

 

/T        

           

Specifies the title to display in the window. 

/P        

If specified, disable print commands

 

 

/M       

If specified, hide the menu bar

 


/G       

Specifies the Signaling group for which events are to be viewed.

 

 

/I

Specifies the Item for which events are to be viewed.

Note: in the field you can specify a filter criterion containing wildcards (see "Joker characters" in the paragraph "Standard editing techniques").

 

 

Note: The <Title> and <Archive> fields previously described must not contain the "/" character; vice versa, the character is considered by the system as a command line config delimiter character

 

The following are two examples of command lines:

 

History80.exe /TStorico /P /GGruppo1

 

The History window will have the title "History", the print commands will be disabled and only the alarms of the Group1 signaling group will be displayed.


 

History80.exe /TStorico /P /IMOTORE*

 

The History window will have the title "Historical", the print commands will be disabled and only the alarms generated by Item with name starting with MOTOR will be displayed (e.g. MOTORE01, MOTORE_PT, etc.).



History80.exe /TEventi del Sistema /F\\MyServer\MyShare /M

 

History will display events by searching data at the root of the MyShare share at server station \\ MyServer; the window will have the title "System Events" and no menu will be visible.

Note: the command line can also be used as an activation parameter for executing the Event History action (see "Configuring a control element for activating the History module"). In this case the name of the executable is omitted.

Note: all the parameters described are optional. If omitted, the default values described below will be assumed. The order of insertion of the parameters is not significant.


 

 

Default values

Path:

History folder within the project directory on the local machine.

 

Title:

Event History

 

Print commands:

Enabled

 

 

Menu:

Visibles