Customizing the Process History View

CLI for the Process History View

The CLI for the Process History View is designed to support different initial startup situations for the Process History View application. You can start the Process History View application with an Events, Charts, or E+Charts document and then modify it to display the desired result.

Note

You can use a hyphen (-) in place of a forward slash (/) to indicate parameters. Therefore, you can enter /area as -area. If there is a file name, it must be the first parameter. After each parameter, there must be a space followed by the value for that parameter.

The startup command is CHS. This example starts the Process History View application and opens a saved file called Reactor.phvc. If you do not provide a specific directory, the Process History View application searches for the file in the default charts subdirectory (DeltaV\Dvdata\Charts). In this example, Process History View opens the file Reactor.phvc, which resides in the default charts subdirectory (DeltaV\Dvdata\Charts):

CHS Reactor.phvc

Parameters are order independent and uncoupled, except for time options. However, some only affect a specific type of display. For example, if displaying a Chart, the event-specific parameters are ignored. If a file name is provided, it must be the first parameter after the CHS command.

Avoid combining mutually exclusive searches. For example, you can pair the event type ALARM with the category PROCESS, DEVICE or HARDWARE, but using Event Type of Alarm with a category of SYSTEM would return 0 matches.

Note

The CLI accepts mutually exclusive search criteria with the results being that records are not found in the chronicle.

Wildcards

You can use the wildcard characters * or ? when specifying an Event Filter parameter (area, device, and so on). The wildcard character * represents zero or more of any printable character, and the wildcard character ? represents a single printable character. Both wildcard characters can appear multiple times in a parameter, and there are no restrictions on the placement of the wildcard characters. Wildcard characters can appear at the beginning, end, or anywhere in a parameter.

The following sections provide details for each parameter.