Optimizing Your iFIX System
Optimizing Your iFIX System
Optimizing Your iFIX System
All rights reserved. No part of this publication may be reproduced in any form or by any electronic or mechanical means, including photocopying and recording, without permission in writing from GE Fanuc Intelligent Platforms, Inc.
Disclaimer of Warranties and Liability The information contained in this manual is believed to be accurate and reliable. However, GE Fanuc Intelligent Platforms, Inc. assumes no responsibilities for any errors, omissions or inaccuracies whatsoever. Without limiting the foregoing, GE Fanuc Intelligent Platforms, Inc. disclaims any and all warranties, expressed or implied, including the warranty of merchantability and fitness for a particular purpose, with respect to the information contained in this manual and the equipment or software described herein. The entire risk as to the quality and performance of such information, equipment and software, is upon the buyer or user. GE Fanuc Intelligent Platforms, Inc. shall not be liable for any damages, including special or consequential damages, arising out of the user of such information, equipment and software, even if GE Fanuc Intelligent Platforms, Inc. has been advised in advance of the possibility of such damages. The user of the information contained in the manual and the software described herein is subject to the GE Fanuc Intelligent Platforms, Inc. standard license agreement, which must be executed by the buyer or user before the use of such information, equipment or software.
Notice 2008 GE Fanuc Intelligent Platforms, Inc. All rights reserved. *Trademark of GE Fanuc Intelligent Platforms, Inc. Microsoft is a registered trademark of Microsoft Corporation, in the United States and/or other countries. All other brands or names are property of their respective holders.
We want to hear from you. If you have comments, questions, or suggestions about our documentation, send them to the following email address: doc@gefanuc.com
Table Of Contents
About This Guide .............................................................................................................................. 1 Reference Documents .............................................................................................................. 1 Introduction ................................................................................................................................... 1 Designing Your Pictures to Achieve Maximum Performance ........................................................... 3 Using Screen Regions .................................................................................................................. 3 Using Animations .......................................................................................................................... 4 Blinking in iFIX Pictures ................................................................................................................ 4 Using ActiveX Controls ................................................................................................................. 4 Windowless Controls ................................................................................................................ 5 Using Shapes Instead of ActiveX Controls ............................................................................... 5 Animations on ActiveX Controls ............................................................................................... 5 Keep Message Reflection Enabled .......................................................................................... 5 Using Bitmaps in iFIX Pictures ..................................................................................................... 6 Choosing the Type of Bitmap to Use ........................................................................................ 6 Refreshing iFIX Displays .............................................................................................................. 7 Using Auto Scale ...................................................................................................................... 7 Resolving iFIX Displays ................................................................................................................ 7 Resolving Tags ......................................................................................................................... 8 Using ReplacePicture ................................................................................................................... 8 Simplify Overview Pictures ........................................................................................................... 8 Using the Alarm Summary Object ................................................................................................ 8 Minimize the Number of Objects in Each Picture ......................................................................... 8 Evaluating the Use of Groups....................................................................................................... 8 Reviewing the Number of Open Pictures ..................................................................................... 9 Using Timer Objects ..................................................................................................................... 9 Using the Expression Builder with Large Historical Tag Lists ...................................................... 9 Using VBA and Scripting to Achieve Maximum Performance ........................................................11 Tuning Your Scripting Performance ........................................................................................... 11 Cleaning Your Code ................................................................................................................... 11 Accessing the Database from Scripting ..................................................................................... 12 Using the Fix32 Object ........................................................................................................... 12 Using the FindObject Method ................................................................................................. 13 Using the FixDataSystem Object............................................................................................ 13 Accessing Animated Objects .................................................................................................. 14
iii
Placing Code in the Initialize and Activate Events ..................................................................... 15 Using iFIX Subroutines and Experts .......................................................................................... 15 Working with the Scheduler ........................................................................................................ 15 Resolving Schedules .............................................................................................................. 15 Running Schedules................................................................................................................. 16 Using Command Wrappers .................................................................................................... 16 Using a Single Timer or Event Object .................................................................................... 16 Referencing Pictures or Global Pages ....................................................................................... 16 User Globals ............................................................................................................................... 16 System-wide Optimizations ............................................................................................................ 19 Upgrading Your Hardware .......................................................................................................... 19 Installing an Accelerator Card ................................................................................................ 19 Defragment the Hard Disk ...................................................................................................... 20 Distributing Additional Applications ............................................................................................ 20 Minimizing the Amount of CPU Used in Steady State................................................................ 20 Evaluating Network Performance ............................................................................................... 20 Best Practices for Managing Multiple iFIX Users ........................................................................... 21 Determine the User Types .......................................................................................................... 22 Decide What Folders You Need To Share ................................................................................. 23 Recommendations on Folder Sharing .................................................................................... 24 Example of the iFIX Directory Structure for Multiple Projects ................................................24 Create a Project for Each User Type.......................................................................................... 25 Example of SCU Path Configuration ...................................................................................... 27 Use the Startup Profile Manager to Define Profiles for Each User in a Project .........................31 Use the Application Validator to Take a Snapshot of Your Project Folders ...............................32
iv
Reference Documents
For related information on subjects discussed in this manual, refer to the following manuals: Creating Pictures Writing Scripts Mastering iFIX
Introduction
With the introduction of the iFIX product, we presented you with a powerful tool. GE Fanuc has the first fully-integrated family of software automation products based on open, component-based technology. It is designed to remove the constraints of packaged software and allow easy integration and interoperability between your plant floor and business systems, as well as between GE Fanuc components and third-party applications. The inclusion of Visual Basic for Applications in iFIX presents you with a powerful scripting tool that allows you to quickly and easily automate operator tasks and create automation solutions. By providing you with an open graphical environment, iFIX enables you to incorporate internet controls (OCXs), reuse elements from other sources (such as bitmaps), or embed other OLE automation applications into your pictures. Like all tools, the successful implementation of these technologies requires careful planning and consideration. Your overall design strategy should consider using this new functionality to its maximum benefit, while striving for peak system performance. Each iFIX system will be different, so we don't offer any absolutes, but rather some suggestions to make your design and implementation more effective. This guide contains some strategies to consider while: Designing pictures Writing scripts Configuring the hardware and software in your iFIX system
To view screen regions in the WorkSpace, select Screen Regions from the View menu (Classic View) or on the View tab, in the Picture group, select Screen Regions (Ribbon View). When this feature is enabled, each time you click on an object in a picture, the screen region it occupies changes color. The size and location of the screen regions are based on the size of the window used to display the picture. When you use screen regions in configuration mode, make sure the picture's window is the same size as it will be in run mode. For example, if you are working on a picture that will be displayed full screen in run mode, use the full screen option in configuration mode when viewing screen regions.
Using Animations
Use animations instead of scripts whenever possible to set an object's properties. Animations are created with optimized C++ code and will always be faster than similar functionality scripted with VBA.
Using Shapes Instead of ActiveX Controls Animations on ActiveX Controls Keep Message Reflection Enabled
Windowless Controls
Use windowless controls whenever possible. These controls process messages faster and draw faster than their windowed counterparts. When you are developing your iFIX pictures and developing any new controls, remember that windowless controls go behind shape objects in your displays; windowed controls will never go behind iFIX shapes. You can use this information to test whether a control is windowed or windowless. To test a control: 1. 2. 3. Place the control in a picture. Draw a rectangle in the same picture. Select the control and then, in Classic view, select Send to Back from the Format menu. In Ribbon view, on the Format tab, in the Arrange group, click Arrange, and then click Send to Back.
If the control goes behind the rectangle, it is a windowless control. If the control stays on top of the rectangle even after you have selected the Send to Back command, then the control is windowed.
then every sub-classed control creates an extra window around itself. To enable or disable Message Reflection: 1. 2. 3. Open your picture. Select Picture from the right-click menu. The Edit Picture dialog box appears. Enable or disable Message Reflection by selecting or clearing the Message Reflection check box.
To change the bitmap type: 1. 2. In the LOCAL folder, locate and open the FixUserPreferences.ini file. In the Picture Preferences section, add the following line:
>
3.
Resolving Tags
If there are tag groups in the picture, run resolve from the Tag Group Editor once the final changes to the picture are made.
Using ReplacePicture
When using ReplacePicture, making both pictures the same size will improve this operation's performance. You can use the Generate Picture Expert, which you can access from the Toolbox, to achieve this result.
because you duplicated this group and used it in many pictures. At run time, there really is no reason for Group A to remain grouped, so consider ungrouping it. This strategy is not meant to imply that groups or Dynamo objects shouldn't have sub-groups; it simply suggests that you use groups judiciously. For example, if your main group has 6 objects, it probably doesn't need 4 sub-groups. However, if your group includes hundreds of objects, it may make sense to cluster the objects into a few smaller groups so that you can more easily duplicate or edit the objects in your picture.
3. 4.
Removing these two lines from the ExpressionEditor.ini file or setting TagListFromHta to 0 will cause the system to revert to the default method of retrieving the historical tag list from the HTC data files.
11
When evaluating the first three methods above, consider how each method ranks in terms of ease of use and performance. Scripting Method Using the Fix32 Object Executing a FindObject on the tag name Using the FixData System object Ease of Use High Medium Low Performance Low Medium High
Each of these methods has its own advantages and disadvantages, which are detailed in the following subsections.
This will be especially slow if the process is attempting to access a tag that is remote to the local node. Example The following code example demonstrates using the Fix32 object to access thisnode:tag.f_cv:
'Writes Fix32.thisnode.tag.f_cv = 1.0 ' Write a 1 to thisnode:tag.f_cv
'Reads Dim X as Single x = Fix32.thisnode.tag.f_cv 'Read the value to thisnode:tag.f_cv and assign it to single precision variable x
12
set DI = System.FindObject("Fix32.thisnode.tag.f_cv")
X = DI 'Read the value of thisnode:tag.f_cv and assign it 'to single precision variable x DI = 1 'Write a 1 to thisnode:tag.f_cv
13
FDS.Groups.Item("DataGroup1").Write 'Write out all the caches in the group (only write those 'items which have changed)
Y = AO.InputValue 'Get the current value of the animated horizontal position input
14
Resolving Schedules
Database information for each data source in a schedule is saved as part of the file on disk. When a schedule executes in the run-time environment, and the database information is not up-to-date, iFIX queries the database and resolves the tag definitions. This can be a time-consuming process the first
15
time the schedule loads, which can slow the execution of the schedule. Resolving schedules removes the need for iFIX to query the database. Therefore, resolved schedules execute faster in the run-time environment. We recommend resolving your schedules as a final step in the configuration process. The Resolve feature is available for both schedules and pictures. If the process database is modified after you resolve a schedule, you need to run Resolve again. To resolve a schedule: 1. 2. 3. 4. 5. Click the Resolve Files button on the Utilities Toolbar. In the File Types area, select the Schedule check box. In the Directories area, verify that your schedule directory is correct. If it is not, enter the correct path in the Schedules field. In the Resolve Files area, select the schedule file you want to resolve. To select every file in the list, click Select All. Click the Update Schedule Files button and click OK.
Running Schedules
Run schedules that do not pop up forms in the background. When forms or message boxes pop up, that schedule's VBA queue is paused until the form is closed or the message box is acknowledged.
User Globals
Place scripts that will be referenced by many pictures in the User Globals page. The User page is the location where you can put your own objects, methods, forms, and variables that you want to use
16
globally.If made public, the objects, methods, forms, and variable objects contained in the User page can be accessed from anywhere within your system. Since the items that you define as public in the User page can be accessed from anywhere in the system, make sure that what you enter is really what you want to expose. If you create a global public variable, remember that it can be changed from any script at anytime.
17
System-wide Optimizations
It is difficult to make hard and fast rules regarding hardware, because each iFIX configuration is so different. However, when it comes to hardware, the following guidelines are true:With hardware, more is better. More memory, more processing speed, and better graphic cards can all help to improve performance. Distribute the other applications your system is running. Try to minimize the amount of CPU used in steady state.
These methods of optimizing your system's hardware, as well as some additional system-wide optimizations, are discussed in the following subsections: Upgrading Your Hardware Distributing Additional Applications Minimizing the Amount of CPU Used in Steady State Evaluating Network Performance
19
20
The steps described in the following figure explain the best practices for configuring iFIX to be used with multiple users. Click a block in the diagram to jump to that section.
21
The following figure shows one example of the names that you might give to each user type when organizing users by function. Your iFIX application can use these groupings, or other ones. This is just one example of many scenarios.
22
Example of User Type Groupings Once you decide on names to group users by, consider which groups will: Share the same preferences? Be able to configure their own historical collection settings (HTA)? Work with recipes? Develop pictures? Have development rights? Have run-time rights? Work with one or more iFIX projects?
Anticipating the needs of your users allows you to successfully determine the configuration of your projects.
23
RCC
For a description of what each of these folders contain, refer to the Planning SCU Directories section. Each project can have its own set of these folders. For instance, if you have different groups of developers, you may want to create a separate directory that includes all of these folders for each developer's project, so that multiple developers can work on different types of projects at the same time. Other projects may share some of these folders. For instance, you might only want to share the iFIX picture path in the C:\Program Files\GE Fanuc\Proficy iFIX folder, but have all the other folders be project-specific. NOTE: The Base and the Language folders should be the same for all users. These folders are not project-specific.
PDB, PIC, APP, HTR, HTRDATA, ALM, RCM, and RCC PDB, PIC, APP, HTRDATA, ALM, RCM, and RCC
Run Time with Historical Collection Special Alarming Run Time Development
LOCAL, HTR
Supervisor
LOCAL, ALM
Supervisor
LOCAL, PDB, PIC, APP, HTR, HTRDATA, ALM, RCM, and RCC
None. Developers should have all unique directories except for NLS and the BASE path, which should always be shared.
Developer
24
25
To create a project in the SCU: 1. 2. Start the SCU. On the Configure menu, click Paths. The Path Configuration dialog box appears. IMPORTANT: The Base and Language Paths should be the same for each project. For instance, if you leave the Base and Language set to the defaults, the Base is set to C:\Program Files\GE Fanuc\Proficy iFIX and the Language is set to C:\Program Files\GE Fanuc\Proficy iFIX\NLS for each project. Leave the Base and Language paths set to the default, and proceed by editing the Project path fields. 3. 4. In the Project field, enter a path for the project. For example, a valid path that you might enter for a developer would be: C:\Program Files\GE Fanuc\Proficy iFIX\PRJ\Dev1. Click the Change Project button. A message box appears asking if you want to add the default iFIX files to the new project. IMPORTANT: The SCU will not copy the files or subdirectories from the existing directories to the new directories. 5. Click Yes. The project path information from the Project field is appended to the other project path fields, such as Local, Database, Picture, Application, and so on. For instance, if you enter C:\Program Files\GE Fanuc\Proficy iFIX\PRJ\Dev1 in the Project field, the SCU automatically adds \PRJ\Dev1 to the other project fields as well. For instance the Local path in this dialog box would now read: C:\Program Files\GE Fanuc\Proficy iFIX\PRJ\Dev1\Local. The Database path would read: C:\Program Files\GE Fanuc\Proficy iFIX\PRJ\Dev1\PDB, and so on. NOTE: While the paths displayed in the Path Configuration dialog box appear to be added at this point, the actual folders for these paths have not been created yet. While you can view the new paths from this dialog, you will not be able to view them from the Windows Explorer until you complete the remaining steps in this section. 6. 7. 8. 9. If there are any paths that you want to change, such as to a shared directory, manually edit the path fields. Click OK from the Path Configuration dialog box. A message box appears asking you to create the folders for the configured paths. Click Create All. A message box may appear indicating you do not have a valid Alarm Area Database file. Click Proceed to continue. iFIX creates the paths for the project folders. You should be able to view the new folders in Windows Explorer. 10. On the File menu, click Save As. The Save File As dialog box appears. 11. Browse to the Project's Local folder. For instance, for Developer1 browse to the C:\Program Files\GE Fanuc\Proficy iFIX\PRJ\Dev1\Local folder. 12. Enter a name for the SCU file. Valid SCU file names can be up to eight characters long. SCU file names can include alphanumeric characters, but must begin with a letter. Special characters, such as symbols and punctuation marks, cannot be used. For example for Developer1, you might enter Dev1.
26
13. Click Save. A message box appears asking you if this is the SCU file that you want to use next time you restart iFIX. 14. Click No. 15. If you have a template folder with iFIX files that you want to copy into one or more project folders, use the Windows Explorer to copy the files from the template folders into the new project folders. Once you have created all the projects, you can go back later and edit all the other SCU settings for each project that require changing. For more detailed information about configuring the rest of the options for the SCU files, refer to the Configuring iFIX Using the SCU chapter in the Setting Up the Environment manual. After you finish creating project directories and configuring the SCU files, you may want to use the Application Validator to create a baseline snapshot of the project directories. For more information on the Application Validator, including the command line options, refer to the Validating an Application section in the Mastering iFIX manual. Notes on Security Configuration for Multiple Projects When working with multiple projects for multiple users, make sure that you also enable global security paths in the Configuration dialog box of the Security Configuration. When you enable the global security paths option (Use these paths for all startup profiles), all iFIX user sessions on a computer share the same security configuration. To access the Security Configuration application, select Security from the Configure menu of the SCU. iFIX must be running to access this application.
27
Location C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\NLS C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1 C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\LOCAL C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\PDB C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\PIC C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\APP C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\HTR C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\HTRDATA C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\ALM C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\RCM C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\RCC C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV1\PDB
Dev2 For the second developer, the project name is Dev2, as shown in the following table. This developer will also have his own set of folders. None of the project folders in this example are shared. When you click OK from the Path Configuration dialog box, the SCU automatically creates the new project directories. Save the SCU file for this project to the Local path defined in the Path Configuration dialog box, the C:\Program Files\GE Fanuc\Proficy iFIX\PRJ\Dev2\Local folder. The following table lists the paths in this dialog box, properly configured for the Dev2 developer. Subfolders that specifically belong to the Dev2 developer appear in bold. Path Base Location C:\PROGRAM FILES\GE FANUC\PROFICY IFIX
28
Location C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\NLS C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2 C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\LOCAL C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\PDB C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\PIC C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\APP C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\HTR C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\HTRDATA C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\ALM C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\RCM C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\RCC C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\DEV2\PDB
Supervisors For all supervisor users, the project name is Supervisors, as shown in the following table. The supervisors in this example, have their own LOCAL, HTR, and ALM directories. They share the PDB, PIC, APP, HTRDATA, RCM, and RCC directories with other user types, such as Operators. When you click OK from the Path Configuration dialog box, the SCU automatically creates the new project directories. Save the SCU file for this project to the Local path defined in the Path Configuration dialog box, the C:\Program Files\GE Fanuc\Proficy iFIX\PRJ\Supervisors\Local folder. The following table lists the paths in this dialog box, properly configured for the supervisors. Subfolders that specifically belong to the supervisors appear in bold.
29
Location C:\PROGRAM FILES\GE FANUC\PROFICY IFIX C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\NLS C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\SUPERVISORS C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\SUPERVISORS\LOCAL C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PDB C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PIC C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\APP C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\SUPERVISORS\HTR C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\HTRDATA C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\SUPERVISORS\ALM C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\RCM C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\RCC C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PDB
Local
Operators For the all operator users, the project name is Operators, as shown in the following table. The operators in this example have their own LOCAL directory. They share the PDB, PIC, APP, HTR, HTRDATA, ALM, RCM, and RCC directories with other user types, such as Supervisors. When you click OK from the Path Configuration dialog box, the SCU automatically creates the new project directories. Save the SCU file for this project to the Local path defined in the Path Configuration dialog box, C:\Program Files\GE Fanuc\Proficy iFIX\PRJ\Operators\Local folder. The following table lists the paths in this dialog box, properly configured for the Operators. Subfolders that specifically belong to the operator appear in bold.
30
Location C:\PROGRAM FILES\GE FANUC\PROFICY IFIX C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\NLS C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\OPERATORS C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PRJ1\OPERATORS\LOCAL C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PDB C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PIC C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\APP C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\HTR C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\HTRDATA C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\ALM C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\RCM C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\RCC C:\PROGRAM FILES\GE FANUC\PROFICY IFIX\PDB
Database Picture Application Historical Historical Data Alarms Master Recipe Control Recipe Alarm Areas (AAD)
Use the Startup Profile Manager to Define Profiles for Each User in a Project
Each project can have multiple users. User profiles are used to associate a user with the iFIX project they will use. To define a user profile, you use the iFIX Startup Profile Manager. Each profile associates a Windows user name with a specific iFIX Project Configuration. The iFIX Project Configuration includes: SCU path and file name that you want the specified Windows user to use when starting iFIX. Node name that you want the specified Windows user to use when starting iFIX.
31
Restrictions on whether the user can modify the Nodename or SCU fields in the iFIX Startup dialog box (Launch.exe), or use the iFIX Sample System.
iFIX must be running in order to use the Startup Profile Manager application to create startup profiles. To access the Startup Profile Manager, in the iFIX WorkSpace's system tree, double-click the Startup Profile Manager icon. The Startup Profile Manager can also be accessed from the Start menu by pointing to Programs, Proficy HMI SCADA - iFIX, Tools, and then Startup Profile Manager. To configure your startup profiles, follow the steps in these sections: Configuring the Default Profile Adding Startup Profiles
32
Index
A accelerator cards ............................................... 19 ActiveX controls optimizing .......................................................4 windowless vs. windowed ..............................5 with animations ..............................................5 Alarm Summary object, optimizing use of .........8 Alarm Summary object.......................................8 Application Validator, overview ...................... 32 auto scaling .........................................................7 B best practices, managing multiple iFIX users ... 21 bitmaps, optimizing ............................................6 blinking, optimizing ...........................................4 C charts large tag lists ...................................................9 speeding up pen retrieval ................................9 code cleaning ........................................................ 11 in Initialize and Activate events ................... 15 configuration, example for SCU ....................... 27 CPU, amount used in steady state .................... 20 creating, projects .............................................. 25 D deciding, shared folders .................................... 23 defining, profiles .............................................. 31 designing, pictures ..............................................3 determining, user types ..................................... 22 directory structure for multiple projects, example ........................................................ 24 E example I iClientTS, determining types of user accounts ........................................................22 iFIX best practices for managing multiple users ...21 directory structure for multiple projects .......24 G global security paths .........................................25 grouped objects, optimizing............................... 8 H hardware accelerator cards ...........................................19 defragmenting hard disk ...............................20 optimizing .....................................................19 upgrading ......................................................19 video bit count ..............................................19 F FindObject method example.........................................................13 using .............................................................13 Fix32 object example.........................................................12 using .............................................................12 FixDataSystem object example.........................................................13 using .............................................................13 folders sharing recommendations .............................24 taking a snapshot ..........................................32 iFIX directory structure for multiple projects .....................................................24 SCU path configuration ................................27 Expression Builder, optimizing for charts ......... 9
33
iFIX optimization ...............................................1 M managing, multiple iFIX users ......................... 21 message reflection ..............................................5 multiple iFIX users, best practices .............................. 21 projects, example .......................................... 24 N network, performance ....................................... 20 O objects, minimizing number in picture ...............8 optimization, introduction ..................................1 optimizations hardware ....................................................... 19 system-wide .................................................. 19 optimizing historical tag retrieval .....................................9 pictures ...........................................................3 VBA scripts .................................................. 11 optimizing your iFIX system ..............................1 P path configuration example .............................. 27 paths, global security ........................................ 25 performance, optimizing.....................................3 pictures designing ........................................................3 optimizing .......................................................3 profiles, in project............................................. 31 projects example of the iFIX directory structure........ 24 folders ........................................................... 32 R recommendations on folder sharing.................. 24 refresh rate V S
expert ............................................................. 7 optimizing ...................................................... 7 ReplacePicture ................................................... 8 resolving pictures .......................................................... 8 tags ................................................................. 8
Scheduler, working with ...................................15 schedules running ..........................................................16 using command wrappers .............................16 screen regions .................................................... 3 scripting, accessing the database ......................12 scripts, tuning performance ..............................11 SCSI drives .......................................................19 SCU path configuration, example.....................27 security paths, global ........................................25 sharing, recommendations for folders ..............24 snapshot of your project folders .......................32 Startup Profile Manager, adding profiles ..........31 steady state........................................................20 structure for multiple project folders ................24 T Timer objects ..................................................... 9 U user globals .......................................................16 user types, determining .....................................22 users, best practices for managing multiple iFIX...............................................................21 using Application Validator ...................................32 Startup Profile Manager ................................31
34