This chapter describes the line and bar profile plots that comprise a series of data values plotted against a specific X-axis engineering unit.
The profile plot area displays a series of data points along its X-axis. The X-axis may represent, for example, length, distance, or frequency. The Y-axis represents the value of each data point. Up to four color-coded sets of data points may be displayed in the plot area in either a line style or a bar style. Only linear scaling is supported on the X and Y axes. Figure 10-1 shows an example of a multi-line profile plot for a paper-manufacturing machine.
Figure 10-1. Multi-line Profile Plot
Both the line and bar style profile plot use color to indicate:
Each line or bar line (1 to 4) with data values within normal limits
Each line or bar line of data values exceeding alarm limits
Each reference line (1 to 4)
The fill colors for bars, if filled bars are configured.
The following profile plot attributes are configurable via FoxDraw:
Number of pens and their colors
Number of points that can be displayed
Profile style (line or bar)
Reference line
Scan rate for the trigger
Appearance of markers
Profile plot background color
Appearance of a grid
Number of grid lines along the X-axis
Appearance of the Y-axis scales.
Operator buttons, typically located at the bottom of a plot area, can be configured via FoxDraw to allow you to:
Select the configured plot area to execute a display command such as accessing an overlay or displaying read-out values.
Toggle between the pause mode and unpaused mode.
When in the paused mode, the plot area is not updated.
Read out a data point by selecting the point along the X-axis.
A vertical hairline appears at the selected X-coordinate, and the point number and value on each line are recorded in FoxView memory and optionally displayed in the read-out fields in the profile area.
After performing a read-out, select a button to send the point number and value for each line to the configured compound:block.parameter or shared variable.
Select an object configured with both read-out and send, in order to read and send point numbers and values with one selection.
Request FoxView/DM to redraw the profile plot.
Profile Plot Appearance
Each of the plot lines (line or bar) has its own:
High and low scale values
High and low alarm limits, and
Reference line value.
This information is available from the profile-line-options configuration information or if not configured, from the Data Header record in the Data Array.
When the high and low alarm limit values are exceeded, a line or bar is drawn in the specified alarm color (see Figure 10-2). The fill color of a bar that has exceeded the alarm limits changes to the alarm color (see Figure 10-3).
Figure 10-2. Bar and Line Profile Plots with Reference Lines and Alarm Limits (Bottom)
Figure 10-3. Bar Profile Plots with Alarm Limits and Reference Lines
Lines or bar lines can be drawn:
On the X-axis from left to right (see Figure 10-1) or mirrored along the Y-axis (called “reverse X-axis”).
With a reference line indicating either the median value of the data (Figure 10-3) or located on the X-axis representing the low scale value.
When “reverse X-axis” is configured, the profile line is mirrored through the Y-axis. The line that is normally drawn from left to right is drawn from right to left creating a mirror image.
Depending on the profile style selected, the reference line (optional) is drawn under or on top of the line. When “line” is configured, the reference line appears under the plot line; when “bar” is configured, the reference line appears on top of the bar line.
The color and value of the reference line are configurable via FoxDraw. The reference line value is defined either by the display file, a process control variable, or the data-array header. It may be the median value or the low scale value represented by the X-axis. For example, the bar graph in Figure 10-3 has a different appearance depending on whether the reference line is the median value or the low scale value represented by the X-axis.
If any of the data values in a plotted profile is unavailable, out-of-service, bad, or in error, then no data is plotted for that point. A blank appears at that data point. In line plots, a break appears in the line. In bar plots, the bar is not plotted for that point number. On the read-out value field,
Operator Buttons and Data Fields
Profile plot displays typically include operator buttons at the bottom and data fields at the top of each plot area.
For the bar and line profile plots of Figure 10-2, the Point, Value and Time fields provide the point number and current value and time for the bar and line profile plots. The Prev Display button opens the previously displayed profile plot.
The buttons in the line profile plot of Figure 10-4, allow you to pause or redraw the profile plot.
Figure 10-4. Line Profile Plot with Operator Buttons
Data Updates
All data points on a profile plot are updated simultaneously and the previous values are discarded.
A profile plot (line or bar) with multiple configured lines has the following line priority scheme:
Line 1 has the highest priority, Line 2 has the next highest priority, and so forth. The lines are drawn on the screen in the following order: from Line 4 (lowest priority) to Line 1 (highest prior-ity). When one line is redrawn, all the other lines are also redrawn.
In bar profiles, when a single point changes every bar is redrawn.
Profile Plot Data
The data to be plotted is a set of string variables, which consists of Object Manager shared vari-ables. The data source for the set of string variables is an application program. The data source maintains an Object Manager list variable (the trigger connection), which is altered each time a change is made to the data stored in the string variables. The connection trigger name for each plot line is configured in FoxDraw.
Each profile line is connected to a trigger path variable via a change-driven connection. When a new value appears in the trigger variable, FoxView reads (via the Data Array path name) all the values from the set of string variables to be displayed.
When the trigger connection and the data array connection names indicate that both variables are in the same station, the FoxView/DM will use the OM list references to retrieve the PSAP address through a getval_list() OM call. To be valid for such a call, the Trigger name and Data Array name should be:
Data_Array_Name=trigger_name01
In case the names do not match the syntax described above, a single global_find() call is issued per trend line, which causes an IPC broadcast message. All the data arrays for the same profile line must be located on the same station; thus they must have the same PSAP address.
For optional connections, all the optional OM data variables must reside in the same station. The PSAP address is retrieved through a global_find() OM call once. If the global_find() call fails, no more attempts are made to retrieve the PSAP address or any of the optional connection data.
It is recommended that:
Per profile area, the trigger connection and the data connection variables reside in one station
Per profile plot line, the optional input connections all reside in the same station.
NOTE
1. Profile plots do not support connections to individual data points or individual bars.
2. The number of data points is not necessarily the width of the graph area in pixels.
FoxView/DM expands the space occupied by each point to fill the width of the graph area.
3. When a plot line has more points than pixels, the points may overlap when the plot line is drawn.
String variables are capable of holding multiple values to be plotted. The maximum length of string variables is 255 bytes. Therefore a string variable can hold a maximum of one of the
For example: Trigger Connection Name: PAPER
Data Array Name: PAPER01
The first Data Array contains the Data Header information as well as a set of data values. The Data Header includes the following information, which is only used if not defined in the profile plot configuration:
The data type being used (always used)
The number of points
High and low scale limits
High and low alarm limits
The reference value.
Therefore, the first Data Array cannot hold as many data points as subsequent data arrays. If the number of points in a profile plot exceeds the number of data values available in the first Data Array, additional string variables are used. (Table 10-1).
When multiple strings are required, the subsequent Data Arrays contain the same path name as the first Data Array with the exception of the last two characters. These characters are
automatically substituted with a number depending on the array, for example, 02 for the second array, 03 for third array ... 59 for last array.
If you need to display 480 data points that are stored in the data array type “float”, the number of string arrays needed is:
1 + (480-55)/63 = 8 data arrays
These 8 string arrays may be named, for example, FLOATARR01, FLOATARR02 ...
FLOATARR08.
When the 480 values are packed into the data array type “integer”, the number of arrays needed is:
1 + (480-114)/127 = 4 data arrays
Packing the same 480 values into a byte array would result in 2 arrays.
A special tool (/opt/fox/bin/tools/omary50) is used to create, get, set, or delete the Object Manager string arrays. Refer to Object Manager Calls (B0193BC).
To engineer data array access, refer to Display Engineering for FoxView Software and Display Manager Software (B0193MQ).
Table 10-1. Contents of Data Arrays
Type Type Length
Appendix A. Frequently Asked Questions
This appendix lists the answers to frequently asked questions (FAQs).
FoxView
Why did dmsepass not change the environment password?
Probably the environment name argument was not entered correctly. The environment names are the names that appear in the Change Environment dialog box, not the name of the file. For exam-ple, the Process_Eng environment is made up of many files: Process_Eng.env, Process_Eng.mbr, Process_Eng.dbr.
The correct way to change the password is with the command:
dmsepass Process_Eng -p new_password
Can I increase the FoxView cursor size on Solaris to make touchscreen work easier?
Yes, the FoxView cursor can be changed to a large cursor.
Change this line:
/usr/fox/wp/data/init.user
to the following line:
FXCURSOR=/opt/fox/wp/FoxView/cursor/crosshair_large
The cursor size does not change until the station is rebooted.
What can I do to shorten display call-up time?
1. Obtain the fastest possible workstation and do not overload it.
The P79 and P80 are the fastest Solaris workstations.
The Windows XP based P92 is the fastest Windows workstation.
If you are running on a slower box (such as 85 MHz or 110 MHz SPARC5s) with one FoxView/FoxDraw, install the 170 MHz CPU upgrade. Refer to P0971VJ.
NOTE
This upgrade is for SPARC5s only. It does not work on a SPARC4® (Model 51B).
SPARC4s run at 110 MHz.
2. Configure the displays in FoxDraw to use the Fast Scan option, as described in Fox-Draw Software (B0700BE).
3. Call-up is generally faster on WPs than on AWs because WPs compete less for system resources.
Do not use four FoxViews if you only require two FoxViews. Do not use two FoxViews if you only require one FoxView.
WPs are intended to be operator workstations. AWs are intended to be engineering workstations. If call-up time and security are major concerns, do not try to save money by forcing AW functionality and overhead onto operator workstations.
4. Use one font only. As often as possible, keep font sizes the same.
Do not use more than two font styles and three font sizes. Use the same font style and size for updating text. Human interface designers suggest using one font:
Helvetica on Solaris workstations
Arial on Windows based workstations.
5. Use the fewest number of display connections as possible. Call-up time is
proportional to the number of connections. 175 points is considered a large display.
The use of more than 175 points slows down display call-up time. 500-point displays can be created fairly easily, but require a call-up time of six to eight seconds (or more).
6. Be judicious with 3D objects. Use as few “fancy” objects as necessary to communicate the idea.
CAUTION
!
It is possible to create 100,000 polygons in a matter of seconds by copying and pasting fancy tanks, turbines, and other objects. Observe precautions.
7. If possible, use submodels for fancy graphics.
If you have more than two of the same configured object, such as a valve with fill color connections, use custom faceplates. Custom faceplates are preconfigured graphical objects in which all connections are made to the same block. The compound:block association is made once and applied to each parameter configuration, as would be done in a conventional PID faceplate.
8. Always test call-up time as you are building displays.
Do not spend weeks creating hundreds of complex displays only to learn that the displays take six seconds to call up when the process application requires a two-second call-up time!
9. If you plan to perform a remote draw from a Solaris FoxView to a PC X Server, use 32-bit X Server software. Ensure that the PC has at least 32 MB of RAM.
NOTE
Windows 3.1 and 16-bit X Servers cannot do the job.
If you are going to use an X Terminal, ensure that it has at least 32 MB of RAM.
X Terminals, which have no virtual memory, are starved for memory.
X Terminals are not cost effective WPs. Do not attempt to run configurators
(such as ICC) on X Terminals. If the network connection breaks, or someone powers down the X Terminal, ICC is left running with no way to exit. This leads to the CP database being out of sync with the ICC work files, requiring a major clean up.
Remember that X Terminals are not WPs. They are inexpensive because they have extremely limited capability.
A remote FoxView uses the resources (memory and CPU) of the station that hosts it.
10. Keep the following in mind when configuring your system:
If you process many Display Manager (dmcmd) commands when opening overlays, the commands are processed serially.
If your display button is configured to run several commands and then open the overlay, there is a delay while the commands are being performed.
11. Use links to commonly used objects, rather than copies.
How should I distribute display files to workstations?
The main issue is the possible corruption of display files. When you close a display, the display is saved to disk. Corruption can occur if the display is copied while it is being saved.
To avoid corruption, ensure that the displays are not being changed on the workstation as the updated displays are being distributed.
The safest way to distribute displays over these workstations is to call in a static display on the workstations and not allow the display to be changed until the distribution is completed. It is not necessary to optimize the displays before distribution.
FoxSelect
The docking positions for toolbars cannot be changed when in touchscreen font state. What is the reason?
When in touchscreen font state, the toolbars are always docked at the top left corner of the application window and cannot be moved. This feature prevents the movement when the toolbar buttons are selected in the touchscreen font state.
Appendix B. Glossary
This chapter provides a glossary of key terms used in this document.
Annunciator keyboard
Hardware panel with keys that light and blink to indicate process alarms.
A horn can also be configured to the keyboard.
Depending on how the annunciator keyboard is configured, pressing a key:
Acknowledges an alarm
Calls up a display
Carries out a command.
The I/A Series system also includes FoxPanels, software alarm panels that can emulate the same functions as hardware annunciator panels.
Checkpoint Run the Equipment Change Display command (from System
Management) to save changes to the control database, process tuning changes, and Fieldbus module status changes.
Compound A logical collection of blocks that performs a control strategy. When you configure the system, you can connect any block in any compound to any other block in any other compound in the system.
Detail Display A standard Invensys supplied display for a compound or block.
Use a Compound Detail Display to change modifiable parameters and to turn the compound on or off.
Use a Block Detail Display to tune loops, perform control tasks, view and control alarms, and view trend data.
EEPROM Update Command
This command, executed from System Management, overwrites firmware in the selected peripheral with updated EEPROM software supplied by Invensys.
Environment A collection of displays, programs, and utilities grouped according to users and the tasks they need to perform. The menu bar, menu options, and Display bar vary from one environment to another. Invensys supplies four default environments: Initial, Operator, Process Engineer, and Software Engineer.
Equipment Control Compound
An Invensys supplied compound that is automatically installed in the Control Processor (CP) on initial boot. The Equipment Control compound (ECC) contains the built-in primary Equipment Control Block (ECB) and any other Equipment Control Blocks that you insert.
FoxSelect FoxSelect is a window that provides an expandable hierarchical view of the control database, showing:
Stations
Station blocks
Compounds
Blocks.
You typically use this window to call up a Block Detail Display. Refer to the FoxSelect On-Line Help.
Group Display An arrangement of process displays grouped to meet your site’s operational needs.
Each Group Display includes:
Buttons that allow you to toggle a selected parameter on a face-plate or call up a Block Detail Display
Faceplates and real-time trend connections to different blocks.
A faceplate, for example, displays the block description, a measurement, and outputs. You can use a faceplate to manipulate the block state and provide direct access to a Block Detail Display.
ScratchPads A set of 20 trend overlays and 20 group overlays that can be created using the ScratchPad menu bar command.
Station block An Invensys supplied block that is automatically installed in the Control Processor (CP) on initial boot. The Station block holds
information about the station’s data collection status (active or inactive), processing cycle, processing load, and alarm output devices.
Station Compound
An Invensys supplied compound that is automatically installed in the Control Processor (CP) on initial boot. The Station compound contains the built-in Station block.
Index
access to turn them on and off 93 searching for 112, 113
selecting 113
turning on and off 114 Configurators 4
Configure Report dialog box 107 Control Database
maneuvering within 111 viewing 115
Cursor
changing size 85
changing size of FoxView cursor 155
Dialog box
Configure Report 107 Data Rate Selection 55, 62 FoxView Preferences 55 History Start Time 60
History Start/Stop Time 54, 61 NEW/EDIT/COPY Report 108 Display
call-up time, reducing 155 files, distributing 158 Display bar
assigning a display to 85 Displays
assigning to the Display Bar 80 Block Detail 11 Error messages, data entry 59
assigning to the Display Bar 80 Block Detail 11 Error messages, data entry 59