Copyright. Proprietary Notice

Transcription

1 Mastering ifix

2 Copyright Proprietary Notice The manual and software contain confidential information which represents trade secrets of GE Fanuc International, Inc. and/or its suppliers, and may not be copied or disclosed except as provided in the license with GE Fanuc International, Inc. The information in this manual is subject to change without notice and should not be construed as a commitment by GE Fanuc International, Inc. GE Fanuc International, Inc. assumes no responsibility for any errors that may be in this document GE Fanuc International, Inc. ALL RIGHTS RESERVED. Trademarks 2003 GE Fanuc International, Inc. All rights reserved. Microsoft is a registered trademark of Microsoft Corporation. All other brands or names are property of their respective holders. ifix Version

3 Contents 1. Scheduler... 1 Overview... 1 Using the Scheduler with ifix... 4 Getting Started with the Scheduler... 5 Using the Scheduler... 6 Securing Schedules... 6 Resolving Schedules... 6 Running Foreground and Background Schedules... 7 Opening Pictures From Background Schedules... 7 Debugging VBA Scripts... 8 Starting the FixBackgroundServer Task... 8 Adding Schedules to the Background Task Startup List... 8 Foreground Schedule Checklist... 9 Background Schedule Checklist... 9 Designing Schedules... 9 Event-Based Entries Time-Based Entries Script Authoring Experts Writing VBA Scripts that Access the Intellution WorkSpace Contents iii

4 Creating and Editing Schedules and Entries Sorting the Spreadsheet...14 Viewing and Controlling Entry Diagnostics Writing Custom Scripts for the Scheduler Script Authoring Expert Sample Code Form Script Sample Code Button Script Sample Code Generated Script Sample Code Failover and Redundancy Understanding Failover and LAN Redundancy SCADA Server Failover and LAN Redundancy Configuration Example Overview Checklist Understanding SCADA Server Failover SCADA Server Failover Messages Writing Data Alarm Handling for SCADA Servers SCADA Server Failover Configurations Primary and Backup Groupings Configuring SCADA Server Failover Updating the HOSTS File for SCADA Server Failover Configuring the SCADA Server Pair Enabling SCADA Server Failover Disabling SCADA Server Failover Synchronizing the Clocks on the SCADA Servers Assigning Manual Failover Privileges iv Mastering ifix

5 Understanding LAN Redundancy LAN Failover Messages Reading and Writing Data Alarm Handling for LAN Redundancy LAN Redundancy Configuration Configuring LAN Redundancy Enabling LAN Redundancy Updating the HOSTS File for LAN Redundancy Disabling LAN Redundancy Optimizing System Performance Enabling the Alarm Startup Queue Service Working with the Network Status Server Using the ifix Diagnostic Display Accessing SCADA Servers Using True Links Reading Data Creating Displays Using Logical and Physical Node Names Network Status Server Fields Troubleshooting Local Node Alias Enabling Local Node Alias Using Local Node Alias...55 Local Node Alias Examples Picture Example Recipe Example Historical Collection Group Example Contents v

6 4. Reporting ifix Report Experts Using the Report Experts Print Crystal Report Print Crystal Report Expert Sample Report The Cross Reference Tool Understanding the Cross Reference Tool Searching for All Tags Searching for One Tag Searching for Text Using the Report Wizard or the Quick Report Exploring the Cross Reference Tool Interface Using the Cross Reference Tool Toolbar Creating Quick Reports...74 Creating Reports Using the Cross Reference Report Wizard Specifying Search Settings Specifying Multiple Files for the Report Specifying Report Settings Options Reviewing the Report Settings Viewing the Report Results Viewing the Status Trail Viewing a Search that Resolves Tags Using All Tag Group Files Viewing a Search that Includes VBA Scripts vi Mastering ifix

7 Selecting Print Options and Printing a Report Selecting Page Options for Printing Customizing Header or Footer Text Creating a Cross Reference Tool Report from the Command-Line Creating Picture-specific Help Files Why Create Picture-specific Help Files? What's This? Help What's This? Help Design Adding Help to an ifix Picture Creating the Help File Requirements Creating a Topic File Creating a Map File Creating and Compiling a Project File Testing Your Help File Example: Creating a Picture-Specific Help File In Microsoft Word In the Intellution WorkSpace In Microsoft Help Workshop Testing the Sample Help File Customizing the System Tree Adding Folders to the System Tree Adding Files to the System Tree Deleting Folders and Files from the System Tree Index Contents vii

8 viii Mastering ifix

9 Figures Figure 1-1: Scheduler in the Configuration Environment... 2 Figure 1-2: Scheduler in the Run-time Environment... 3 Figure 2-1: SCADA Backup Node and LAN Redundancy Configuration Figure 2-2: SCADA Server Failover Configuration from an iclient Figure 2-3: SCADA Server Failover Configuration from a SCADA Server Figure 2-4: Typical Configuration of an iclient with a Primary and Backup SCADA Figure 2-5: SCADA Server Configuration with a Backup SCADA Figure 2-6: Invalid Primary and Backup Grouping Configuration Figure 2-7: Correct Primary and Backup Grouping Configuration Figure 2-8: Invalid SCADA Configuration in a SCADA Server Pair Figure 2-9: Invalid Version Configuration in a SCADA Server Pair Figure 2-10: Typical LAN Redundancy Configuration Figure 2-11: LAN Redundancy Configuration with an Excluded Card Figure 4-1: Sample Crystal Report Figure 5-1: Report Results of a Search for All Tags Figure 5-2: Report Results for a One Tag Search Figure 5-3: Report Results of a Text Search Figure 5-4: Cross Reference Tool Toolbar Button Figure 5-5: The Cross Reference Tool Window Figure 5-6: The Quick Report Dialog Box Figure 5-7: Cross Reference Report Wizard - Search Settings Tab Figure 5-8: Cross Reference Report Wizard - Files Tab Figure 5-9: Cross Reference Report Wizard - Report Settings Tab Figure 5-10: Cross Reference Wizard - Apply and Go Tab Figure 5-11: Status Trail Figure 5-12: Search Results of Resolving Tags using All Tag Group Files Figure 5-13: Search Results of Including VBA Scripts in Search Figure 5-14: Cross Reference Tool Print Dialog Box Figure 5-15: Page Setup Dialog Box Figure 5-16: Change Header and Footer Attributes Dialog Box Figure 7-1: System Tree Customization Overview Figures ix

10 x Mastering ifix

11 Tables Table 2-1: Network Status Server (NSS) Fields Table 5-1: Cross Reference Tool Toolbar Buttons Table 5-2: Search Results Table 7-1: Folder Attributes Table 7-2: File Attributes Tables xi

12 xii Mastering ifix

13 The Mastering ifix manual is intended for system integrators, OEMs, and process control engineers responsible for implementing a software automation solution using ifix. This manual assumes that you are familiar with Microsoft Windows NT or Windows 2000, Microsoft Visual Basic, the Intellution WorkSpace, and your plant's network. Reference Documents For related information about ifix, refer to the following manuals: Understanding ifix Writing Scripts Creating Pictures Setting Up the Environment Implementing Alarms and Messages xiii

14 xiv Mastering ifix

15 1. Scheduler There are certain tasks that you may want to perform at a specified time or interval, or when a change occurs in a database value or in any OPC data server value. For example, you may want to run a Visual Basic for Applications (VBA) script that generates a report at the end of every shift or replaces the currently-displayed picture when a database point exceeds a certain value. The Scheduler allows you to create, edit, monitor, and run both types of actions as scheduled entries. In the Scheduler, you define the time or event that triggers a scheduled entry, and the action, referred to as an operation, that you want to occur. ifix supplies Script Authoring Experts for common tasks such as replacing a picture. These Experts generate scripts based on the information that you supply to the Expert. You can also write custom scripts for common tasks that do not have Script Authoring Experts. Refer to the Writing Scripts manual for detailed information on writing VBA scripts. Overview In the configuration environment, ifix displays schedules in the Intellution WorkSpace, allowing you to easily create, edit, and start monitoring entries while you work on your project. Chapter 1. Scheduler 1

16 Indicates if the schedule will run in the foreground (F) or background (B) Scheduled entries Schedule Entry tabs Scheduled entries Schedules Schedules folder Figure 1-1: Scheduler in the Configuration Environment In the run-time environment, you can view the status and statistics of the entries in your schedule. You can also control your entries using the Start/Stop, Reset, and Fire Now buttons. 2 Mastering ifix

17 Scheduled entries Indicates if the schedule runs in the foreground (F) or background (B) Schedule Entry tabs Entry status, name,statistics, description, and controls Figure 1-2: Scheduler in the Run-time Environment Chapter 1. Scheduler 3

18 The Scheduler provides the following features: Spreadsheet design that allows you to easily view and edit entries. Ability to schedule as many entries as necessary and to trigger them as often as necessary. Ability to run as a service under Windows NT or Windows Script Authoring Experts for common events. Ability to easily monitor entries and view diagnostic statistics. Ability to trigger scheduled scripts on demand. Ability to run schedules as a foreground or background task. Using the Scheduler with ifix Individual schedules can be run as a foreground or the background task. When you run a schedule in the foreground, you can easily test and debug scripts in the run-time environment. When an error occurs, VBA launches the Visual Basic Editor (VBE) debugger, where you can edit and save changes to a script. You cannot run scripts in the configuration environment. When you run schedules as background tasks, they run regardless of whether the Intellution WorkSpace is in the run-time or configuration environment, and regardless of whether the Intellution WorkSpace is running. If you modify a scheduled entry, it automatically restarts. When the Intellution WorkSpace is in the run-time environment, you can view Scheduler statistics and diagnostic information about each entry in the schedule, including the number of times each entry has been fired and the last time it was fired. You can also run the Scheduler in the background as a service under Windows NT or Windows Because the Scheduler runs as a service, operators can log in and out of an NT or 2000 node without affecting scheduled entries, and entries are triggered regardless of whether or not the Intellution WorkSpace is running. 4 Mastering ifix

19 You can create multiple schedules, which allows you to organize and easily maintain entries. Each schedule can be configured individually to run as a background or foreground task. Also, as you add events to a schedule, you can choose whether or not to start monitoring them immediately, or to wait until the next time the Intellution WorkSpace starts. The Scheduler supports a powerful Find and Replace feature that allows you to quickly and easily modify information in a schedule. For additional information on using the Find and Replace feature, refer to the Finding and Replacing Data section of the Understanding ifix manual. Getting Started with the Scheduler Before you start scheduling entries, you should understand how the Scheduler executes scripts. The Scheduler can run as a foreground or background task. When you run a schedule in the foreground, it runs on the same thread as the scripts in the Intellution WorkSpace, allowing you to quickly test and debug scripts in the run-time environment. When you run a schedule in the background, it runs on a separate thread from the scripts in the Intellution WorkSpace, monitoring the system and triggering scheduled events. The Scheduler does not loop; it waits for events to occur. When a selected event occurs, the script is triggered from a schedule running in the background, it is added to the queue, and it executes after the scripts in front of it have finished executing. For this reason, when a schedule is run as a background task it is ideal for monitoring tasks. This is exactly the same as scripts triggered from schedules running as foreground tasks in the Intellution WorkSpace. Generally, schedules created to run in the foreground are used for testing and debugging. Once a schedule created to run in the foreground has been tested and debugged, we suggest that you set it to run in the background. Refer to the Running Foreground and Background Schedules section for more information. Refer to the Writing Scripts manual for an explanation of how scripts are implemented in the Intellution WorkSpace. Chapter 1. Scheduler 5

20 Using the Scheduler Schedules are spreadsheets with separate tabs for event-based entries and time-based entries. Double-clicking an empty row in a schedule displays a dialog box for adding an entry. Once you have created an entry, you can edit individual cells in the spreadsheet without using the dialog box. Time-based entries create a timer object while event-based entries create an event object. These ifix objects have associated properties, methods, and events that you can use in VBA scripts. They are displayed in the system tree and are the objects to which scheduled scripts are tied. Securing Schedules ifix s schedule protection prevents unauthorized users from accessing or modifying schedules. To configure security for your schedules, enter a security area in the Properties window. For more information on configuring security, refer to the Implementing Security manual. 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 which slows 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. These modifications include: Loading a different database. Deleting database tags. 6 Mastering ifix

21 Running Foreground and Background Schedules You can select whether you want your schedules to run as foreground or background tasks. When you create a new schedule, the default is for it to run in the foreground. To run a schedule in the foreground, the Intellution WorkSpace must be running in the run-time environment. Running a schedule in the foreground is useful for testing and debugging VBA scripts. To run a schedule in the background, the FixBackgroundServer task must be running. If the FixBackgroundServer task is not running, it is automatically started when a schedule is added to the background task. To create a schedule that runs in the background you must change the default setting in the Scheduler Properties dialog box, which is available by right-clicking a schedule and selecting Scheduler Properties from the pop-up menu. You can use this dialog box to change the default setting for a new schedule or for an existing schedule that is set to run in the foreground. Also, you can select whether you want a schedule to run in the foreground or the background, set the window properties, and set the statistics refresh rates. NOTE: An unsigned write occurs when a database tag is configured for electronic signature, but you write a value directly to that tag without capturing a signature. If you are working in a secure environment with the Electronic Signature option enabled, you must be aware of the impact of unsigned writes to the process database. Unsigned writes can originate from schedules. Refer to the Implications of Database Writes With Electronic Signature section of the Using Electronic Signatures manual for detailed information. Opening Pictures From Background Schedules If a picture opens from a background schedule while you are editing a picture or schedule in the WorkSpace, you may experience unexpected behavior. In some instances, the picture may open over a modal dialog box and you will not be able to get back to the dialog box. To avoid this problem, we recommend that when adding an entry to a background schedule, you configure the schedule to check whether the WorkSpace is in the runtime or configuration environment before opening a picture. NOTE: Schedules that are configured to run in the background cannot reference pictures. When FixBackgroundServer opens a schedule that references a picture, it also tries to open that picture. Since FixBackgroundServer cannot open pictures, an error message appears. Chapter 1. Scheduler 7

22 For more information on creating new schedules and using the Scheduler Properties dialog box, refer to the Creating and Editing Schedules and Entries section. Debugging VBA Scripts If a scripting error occurs while a schedule is running, the VBE debugger automatically launches to allow you to quickly edit and save the changes made to the script. If the schedule is running in the foreground when the VBE launches, any changes made to the script are automatically saved in the schedule. If the schedule is running in the background when the VBE launches, close the VBE editor, re-open it in Intellution WorkSpace, and make the necessary changes to the script. Any changes made to the script are automatically saved in the schedule. NOTE: In order for scripting changes to be saved in a schedule, the VBE must be started in the Intellution WorkSpace. Any scripting changes made in the VBE launched from the FixBackgroundServer task will not be saved in a schedule. Starting the FixBackgroundServer Task The FixBackgroundServer task can run on its own or as a Windows service. Refer to the Setting Up the Environment manual for more information on configuring startup tasks. Adding Schedules to the Background Task Startup List Normally, you want your schedules to start automatically when ifix is started. To do this, you must add the schedules to the background task startup list. If you are adding entries to a schedule that is already running in the background, you can choose whether or not to start monitoring the entry immediately. 8 Mastering ifix

23 Foreground Schedule Checklist The following is an overview of the steps necessary to successfully implement a foreground schedule: [1] Create a foreground schedule in the configuration environment of the Intellution WorkSpace. [2] Monitor entries as necessary from the run-time environment of the Intellution WorkSpace. Background Schedule Checklist When creating a schedule that runs in the background, you can create it directly as a background schedule or create a foreground schedule and convert it to a background schedule. The following is an overview of the steps necessary to successfully implement a background schedule: [1] Create a background schedule in the configuration environment of the Intellution WorkSpace. [2] Add the schedule to the background task startup list, using the Background Startup tab in the User Preferences dialog box. [3] Monitor entries as necessary from the run-time environment in the Intellution WorkSpace. Designing Schedules This chapter explains the issues you need to consider while you are designing schedules. When creating schedules, there are two types of entries that you can select: event-based entries and time-based entries. This section describes both types of entries and the triggers that can be used by each. Chapter 1. Scheduler 9

24 Event-Based Entries Event-based entries are created using the Add Event Entry dialog box. Event-based entries can use any data source available to the system to trigger an action. To select a data source, you can either enter the data source in the Data Source field or click the Browse button to access the Expression Builder. Five event types are available to trigger an action based on the value of a data source. For example, you may want to have a certain action occur when an alarm equals HIHI. By tying the value of the alarm field to the OnTrue event type, you can trigger an action when the value of this field becomes equal to HIHI. The following table lists the event types that are available and when they trigger: The event type... OnDataChange OnTrue OnFalse WhileTrue WhileFalse Triggers... When the expression changes. When the expression resolves to a non-zero value. When the expression resolves to zero. At the specified interval as long as the expression evaluates to a non-zero value. At the specified interval as long as the expression evaluates to zero. 10 Mastering ifix

25 Time-Based Entries Time-based entries are created using the Add Timer Entry dialog box. Time-based entries trigger at a scheduled time and are not tied to a data source. The following table lists the time triggers that are available and when they trigger: The time type... One Shot Continuous Triggers... Once at the specified date and time. For example, you can schedule an entry to trigger at 5:00 p.m. on 7/4/98. Continuously at the specified interval, starting at the specified time. For example, you can schedule an entry to trigger every eight hours. NOTE: You may notice in the log file that the timers occasionally fire +/- 1 or 2 milliseconds off. This may happen on the first fire and will return to the specified interval in a subsequent firing. Daily Monthly On the scheduled days of the week at a particular time. Optionally, you can specify an end time and interval. For example, you can schedule an entry to trigger Monday through Friday, at noon, or every hour from noon until 6:00 p.m. On the scheduled days of the month at a particular time. Optionally, you can specify an end time and interval. For example, you can schedule an event for the 15 th of the month, at 9:00 a.m., or every hour from 9:00 a.m. until 5:00 p.m. You can also schedule an event for the end of the month at a particular time. This setting determines the last day of the month for you. NOTE: If you have Daylight Saving Time enabled and you create a timed-based entry to have a 2:30 AM Start Time, be aware that during the transition from Standard Time to Daylight Saving Time, the schedule will actually fire at 1:30 AM. All other days of the year, it will fire at 2:30 AM. All time-based entries run the script tied to the OnTimeOut event procedure. Chapter 1. Scheduler 11

26 Adjusting for Daylight Saving Time The Scheduler supports daylight saving time for time-based events. Before allowing automatic Daylight Saving Time to be used in a production environment, you should test your application under each of the following scenarios for proper behavior: While in Standard Time. While in Daylight Time. During the transition from Standard Time to Daylight Time. During the transition from Daylight Time to Standard Time. Script Authoring Experts When you select an action in the Operation field of either the Add Timer Entry or Add Event Entry dialog box, ifix asks you whether or not you want to run the Script Authoring Expert now. If you select Yes, it automatically runs the Script Authoring Expert associated with that action. If you want to run the Script Authoring Expert at a later time, you can modify the entry and click the Run Expert button. After you have provided the Expert with the required information, the Expert generates a VBA script tied to the appropriate event. For example, the Replace Picture Script Authoring Expert asks which picture you want to display and, once you have provided it with a picture name, generates a script to replace the picture. Once the script is generated, you can edit it by re-entering the Expert or by accessing it directly using the VBE. In addition to the Script Authoring Experts provided in ifix, you can write your own custom scripts for frequently-performed tasks. Refer to the Writing Custom Scripts for the Scheduler section for information on how to create your own custom scripts for the Scheduler. Writing VBA Scripts that Access the Intellution WorkSpace When you write a scheduled script that opens, closes, replaces, or accesses a property of an object in a picture, you must ensure that the Intellution WorkSpace is running and that the picture you need to access is open and active. This differs from writing scripts that run from pictures. 12 Mastering ifix

27 Before you can access any information about the active picture in the Intellution WorkSpace, you must activate the Intellution Workspace using the GetObject method as shown in the following example. Dim AppObj As Object Set AppObj = GetObject("","Workspace.Application") You can now check to see if the picture is open: If UCase(AppObj.ActiveDocument.Name) = UCase("MyPicture") Then <perform a task or open the picture> You can then check to see which document or picture is open, and replace it if it is not the one you need. Once the proper picture is open, you can access its objects. Refer to the Writing Scripts manual for more information on using VBA with ifix. Creating and Editing Schedules and Entries The Scheduler allows you to create multiple schedules which help you to easily organize and maintain events. When you create a new schedule, you can control its properties from the Scheduler Properties dialog box. The following table lists the tabs on the Scheduler Properties dialog box and the properties that can be controlled from each: Tabs Run Time State Window Properties Properties Run in Foreground Run in Background Window Height Window Width Window Styles Chapter 1. Scheduler 13

28 Tabs Stats Refresh Background Files Properties Timer Statistics Refresh Rate (in seconds) Event Statistics Refresh Rate (in seconds) Lists all schedules running in the background. No changes can be made from this tab. You can create new schedules when the Intellution WorkSpace is in the configuration environment. NOTE: ifix does not support schedules that use the same name as the local node. Therefore, do not use your local node s name for any schedules you create. Once you have created a schedule, the schedule and all its entries appear in the Schedules folder of the system tree. You can open a schedule and view or edit its properties at any time by double-clicking the schedule name in the system tree. Once you have created a schedule, you can add new entries to it using the Script Authoring Experts in the Scheduler category or by writing your own custom scripts. You can edit an existing entry by selecting the entire entry or a particular cell within the entry. Once created, entries can be easily copied or moved from one schedule to another. Sorting the Spreadsheet You can sort Scheduler entries in ascending or descending order by clicking the heading of the column you want to sort. For example, if you want to sort entries alphabetically by name, click the Name column's heading. The entries will appear in ascending order. To sort them in descending order, click the Name column's heading again. NOTE: Sorting is only available in the configuration environment. In the run-time environment, entries appear in the order they were added to the schedule. 14 Mastering ifix

29 Viewing and Controlling Entry Diagnostics The Scheduler allows you to view and control entry diagnostics in the run-time environment. If you open a schedule in the run-time environment, you can view the status of entries, the number of times they have been fired, and the time when they were last fired. You can also: Start or stop an entry from executing. Reset the statistics (number of times it has been fired and time when it was last fired) of the entry. Trigger an entry to fire on demand. If you have loaded a schedule, but the scripts are not firing, you need to determine whether the problem is caused by the firing mechanism or by the script itself. Writing Custom Scripts for the Scheduler The Scheduler provides Script Authoring Experts that generate a script that is executed when an entry triggers. These Experts are available for common tasks such as toggling a digital point or generating a report. You can also create custom scripts for tasks that you need to perform. This section shows sample code that may be helpful when writing custom scripts for use with the Scheduler. For additional examples, use the VBE to view the code for the Experts, buttons, and forms supplied with ifix. Refer to the Writing Scripts manual for detailed information on writing VBA scripts. Chapter 1. Scheduler 15

30 Script Authoring Expert Sample Code The following properties store information that is passed between a Script Authoring Expert, the Scheduler, and the Intellution WorkSpace: ProcedureObject. EventProcedure. Property1 through Property10. Only the following two properties have a specific purpose: ProcedureObject the Timer or Event entry to which the script will be attached. For example, Event5 or Timer 3. EventProcedure the name of the event type that will trigger the script. For example, OnTrue. Property1 through Property10 are available to the Expert for operational parameters specific to the Expert. Initially, these parameters are passed from the Expert to the Scheduler, and do not appear in the Scheduler until after the script has been generated. For example, if the user re-enters the Expert, the Scheduler passes them back to the Expert, which can then use them to populate a form. The following example shows the code behind the Toggle Digital Point Script Authoring Expert. Private Sub ToggleDigitalPointWizard_Click() Dim CurrentObj As Object Dim szeventname As String On Error GoTo ErrorHandler Application.DeActivateWorkspaceUI True, False Prevent this button from being used in a Picture document If InStr(1, Application.ActiveDocument.Type, "FIXSchedule",_ vbtextcompare) = 0 Then Application.ActivateWorkspaceUI MsgBox "This button is not for use. Use the button _ from the Command Tasks category." Exit Sub End If 16 Mastering ifix

31 Pass the timer or event object s ProcedureObject and EventProceduure to the form Set CurrentObj = ToggleDigitalPointWizard.ProcedureObject szeventname = ToggleDigitalPointWizard.EventProcedure The FIX database tag is in Property1. Enter the tag in the form field frmtoggledigitalpointcommand.expressioneditor1.edittext = ToggleDigitalPointWizard.Property1 Call a subroutine in the form that enters the ProcedureObject and EventProcedure as global variables so that the script in the form can act on them Call frmtoggledigitalpointcommand.getschedulervalues(currentobj, szeventname) frmtoggledigitalpointcommand.bcancel = False Open the form frmtoggledigitalpointcommand.show Pass the FIX database tag back to the scheduler If frmtoggledigitalpointcommand.bcancel = False Then ToggleDigitalPointWizard.Property1 = frmtoggledigitalpointcommand.expressioneditor1.edittext End If Application.ActivateWorkspaceUI Exit Sub ErrorHandler: HandleError End Sub The following example shows the code behind the Generate Report Script Authoring Expert. Private Sub GenerateReportWizard_Click() Dim CurrentObj As Object Dim szeventname As String On Error GoTo ErrorHandler Application.DeActivateWorkspaceUI True, False Chapter 1. Scheduler 17

32 Prevent this button from being used in a Picture document If InStr(1, Application.ActiveDocument.Type, "FIXSchedule", vbtextcompare) = 0 Then Application.ActivateWorkspaceUI MsgBox "This button is not for use. Use the button _ from the Command Tasks category." Exit Sub End If Pass the timer or event object s ProcedureObject and EventProceduure to the form Set CurrentObj = GenerateReportWizard.ProcedureObject szeventname = GenerateReportWizard.EventProcedure The Crystal Report name is in Property1. Enter the report name in the form field frmgeneratereportcommand.txtreport.text = GenerateReportWizard.Property1 Call a subroutine in the form that enters the ProcedureObject and EventProcedure as global variables so that the script in the form can act on them Call frmgeneratereportcommand.getschedulervalues_ (CurrentObj, szeventname) frmgeneratereportcommand.bcancel = False Open the form frmgeneratereportcommand.show Pass the Crystal Report name back to the scheduler If frmgeneratereportcommand.bcancel = False Then GenerateReportWizard.Property1 = frmgeneratereportcommand.txtreport End If Application.ActivateWorkspaceUI Exit Sub ErrorHandler: HandleError End Sub 18 Mastering ifix

33 Form Script Sample Code The following example shows code that collects the name of the picture the user wants to display when the event is triggered, generates the script, and creates the event. The Procedures object is a collection of scripts. Before you generate the script, you need to get the index number for the next script using the GetEventHandlerIndex method. Once you generate the string that will become the script, use the AddEventHandler method to add the event. Private CurrentObject As Object Private EventName As String Public Sub GetCurrentObjectValues(obj, Str) Set CurrentObject = obj EventName = Str End Sub Private Sub CommandButton1_Click() 'get file name entered by user Dim FileName As String FileName = TextBox1.Value Dim WorkingObj As Object Set WorkingObj = CurrentObject.Procedures 'Get the index for the procedure Dim Index As Long Dim Found As Long WorkingObj.GetEventHandlerIndex EventName, Index, Found 'Generate code Dim StringCode As String StringCode = "Dim doc As Object" & Chr(13) _ & "Dim PicturePath As String" & Chr(13) _ & "PicturePath = ""c:\fix32\pic\"" & FileName" & _ Chr(13) & "Set doc = _ Application.Documents.Open(PicturePath)" & Chr(13) 'Add the event WorkingObj.AddEventHandler EventName, StringCode, Index 'Close the form End End Sub Chapter 1. Scheduler 19

34 Button Script Sample Code The following example shows code for a button object called MyExpert that gets the timer or event object, the event trigger name, and picture name, if any, from the Add Event dialog box. It passes this information in to the form using the GetCurrentObjectValues procedure, and then displays the form. Private Sub MyExpert_Click() Dim CurrentObj As Object Dim EventName As String 'Set procedure object, event name, and file name Set CurrentObj = MyExpert.ProcedureObject EventName = MyExpert.EventProcedure MyExpert.Property1 = frmopenpicture.textbox1.value 'Pass the object and event name into the form Call frmopenpicture.getcurrentobjectvalues(currentobj,_ EventName) frmopenpicture.show frmopenpicture.hide End Sub Generated Script Sample Code The following example shows the script that would be generated if you ran this Expert on the Timer7 object, using the OnTimeOut event. Private Sub Timer7_OnTimeOut(ByVal ltimerid As Long) Dim doc As Object Dim PicturePath As String PicturePath = "c:\fix32\pic\" & FileName Set doc = Application.Documents.Open(PicturePath) End Sub 20 Mastering ifix

35 2. Failover and Redundancy This section describes ifix SCADA server failover and LAN redundancy. Also included is information on monitoring and controlling your network using the Network Status Server and ifix diagnostic displays. Understanding Failover and LAN Redundancy Operators view process data received from a SCADA server using an ifix iclient. Should the SCADA server or LAN connection become unavailable, process data can become unavailable to the operator at the iclient. ifix SCADA server failover and LAN redundancy increase the availability of data to the iclient and minimize the amount of time that data is unavailable. It does this by allowing the iclient to connect to a primary and backup SCADA server and to use more than one LAN connection to the SCADA server. By recognizing multiple paths to the data, ifix can switch from one path to another automatically, improving overall system availability for critical operations. Switching from one connection to another is known as failover. SCADA server failover allows you to connect an iclient to both the primary and backup SCADA servers, the SCADA partners, that are connected to the same PLC. This feature provides two paths to the same process data instead of just one. The iclient establishes and maintains the connections to both the primary and backup SCADA servers, either of which can be the active server the SCADA node with which the iclient is currently communicating or the non-active SCADA server. When the connection to the active SCADA server is lost, ifix automatically fails over to the non-active SCADA server. LAN redundancy allows two physical network connections between the iclient and SCADA server, providing two network paths to the same process data. When the connection over one network path is lost, ifix automatically fails over to the other network path. Failover works the same way regardless of whether you are using SCADA server failover or LAN redundancy. In either case, failover to the non-active SCADA server or non-active network path occurs only if the non-active connection is available. Chapter 2. Failover and Redundancy 21

36 You can use SCADA server failover and LAN redundancy either individually or together. If you enable both SCADA server failover and LAN redundancy, SCADA server failover takes precedence over LAN redundancy. In other words, ifix tries to fail over to the partner SCADA node first. If the partner SCADA node is not available, failover occurs to the backup network path. ifix also provides the following features: Automatic session monitoring of each SCADA server and managed LAN connection. Improved display portability by using logical node names to represent the primary and backup SCADA partners. Availability of connection status information using the Network Status Server (NSS). Alarm acknowledgment synchronization when both partner SCADA servers are up and running, ensuring that you only have to acknowledge an alarm once. Manual failover feature that allows an operator to initiate SCADA failover to the non-active SCADA server. SCADA Server Failover and LAN Redundancy Configuration Example If you enable both SCADA server failover and LAN redundancy, SCADA server failover takes precedence over LAN redundancy. For example, in the following figure an iclient configured with the logical node name LGCL_ND1 is communicating with SCADA PACKER1 over network path 1. If the connection is lost, the iclient will attempt to fail over to PACKER2 before reconnecting to PACKER1 over network path Mastering ifix

37 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 iclient Network Path 2 Primary SCADA Node Network Path 1 Backup SCADA Node Local Node Name: PACKER1 Local Logical Name: LGCL_ND1 Local Node Name: PACKER2 Local Logical Name: LGCL_ND1 PLC Figure 2-1: SCADA Backup Node and LAN Redundancy Configuration Overview Checklist The following is a list of general tasks for implementing failover and redundancy: [1] Install your hardware and network connections, and ensure that they work and communicate independently of ifix. [2] Configure SCADA server failover: [a] [b] [c] Define a Logical Name. Configure primary and backup SCADA servers in the SCU. Configure the SCADA partners. Chapter 2. Failover and Redundancy 23

38 [d] [e] [f] Configure alarm acknowledgement synchronization. Synchronize the clocks on the SCADA servers. Assign manual failover privileges if security is enabled. [3] Configure LAN redundancy: [a] [b] [c] Configure network paths for LAN redundancy in the SCU. Update the hosts file if you are using TCP/IP. If necessary, optimize system performance by disabling network paths and balancing network timers and failover time. [4] Monitor and control network status using the Network Status Server fields and diagnostic displays supplied with ifix. Understanding SCADA Server Failover When ifix starts, the iclient attempts to establish communication with its primary and backup SCADA servers. The primary node is the SCADA node you want the iclient to communicate with at startup. The backup node is the SCADA node you want the iclient to communicate with if the primary node becomes unavailable. If both nodes are available, the iclient establishes a connection with both of them. The first SCADA node it establishes a connection with is the active node. If only one SCADA server is available, the iclient establishes a connection with it. If neither SCADA server is available, the iclient polls both nodes until it establishes a connection with at least one SCADA server. If the iclient fails over to the backup SCADA, it remains connected to the backup SCADA even when the primary SCADA becomes available. Automatic failover to the primary SCADA only occurs if the connection to the backup SCADA is lost and the primary SCADA is available. You can also manually initiate failover back to the primary SCADA once it becomes available. 24 Mastering ifix

39 SCADA Server Failover Messages You can identify when a SCADA server failover has occurred using a Network Status Server tagname, or through the alarm messages. Refer to the Working with the Network Status Server section for more information. ifix sends an alarm message whenever SCADA server failover occurs. This alarm message never appears at the remote nodes. For example, if you are communicating from an iclient named LN1_VIEW to a primary SCADA node named PACKER1, and the iclient fails over to the backup SCADA node named PACKER2, the message on the iclient is: 06/07/ :35:22.5 Connection Failover: connection to PACKER1 has been switched to PACKER2 Writing Data Data is written to the active SCADA server only. For example, if the active node is PACKER1 and the non-active node is PACKER2, before a failover the iclient writes data to PACKER1. After a failover, the iclient writes data to PACKER2. Alarm Handling for SCADA Servers When you configure networking and SCADA options in the SCU for both partner SCADA servers, the Alarm Startup Queue Service is automatically enabled. This service ensures that alarms are not lost during session loss and reconnection. To enable alarm acknowledgement synchronization between a pair of SCADA nodes, you need to define the partner SCADA for each SCADA. For example, if you have two SCADA nodes (SCADA1 and SCADA2), you can enable alarm acknowledgement synchronization by doing the following: [1] In Local Startup, define your logical node name. [2] In the SCU of SCADA1, select SCADA from the Configure menu. [3] In the SCADA Name field in the Partner SCADA section of the SCADA Configuration dialog box, enter SCADA2. NOTE: SCADA2 must have a different logical node name than SCADA1. Chapter 2. Failover and Redundancy 25

40 [4] In the SCU of SCADA2, select SCADA from the Configure menu. [5] In the SCADA Name field in the Partner SCADA section of the SCADA Configuration dialog box, enter SCADA1. [6] Make sure the primary and backup SCADA servers are listed as part of a logical pair in the Configured Remote Nodes list box of each computer s SCU network configuration. For more information on logical pairs, refer to Primary and Backup Groupings. NOTE: Do not list the primary and backup SCADA servers as individual remote nodes. [7] Make sure the process databases of both nodes are identical. The easiest way to do this is to compare the serial numbers of both databases. If they do not match, integrate the two databases and copy the resulting PDB file and AlarmAreas.AAD to each SCADA server. When an alarm occurs on a SCADA server, the alarm is sent to its iclient. The iclient accepts alarms from the active node only, regardless of whether it is the primary or backup SCADA. You cannot view alarms generated by the non-active SCADA. At the iclient, alarms and messages display the logical node name in brackets. In the following example, the logical node name is LNN. 04/29/98 22:49:45.1 [LNN] AI-1 HI However, if the message is generated by the Database Manager or because of networking problems, node names within the alarm text display the physical node name. When a node is configured as part of a partner SCADA server pair, the Alarm Summary Queue needs to be twice as big as it would be if the node were not part of a SCADA pair. For example, if you are generating 500 alarms, the Alarm Summary Queue must be set to If the Alarm Summary Queue overflows, you may see alarms appear and disappear in the alarm summary. Refer to the Implementing Alarms and Messages manual for more information on queue sizes. 26 Mastering ifix

41 SCADA Server Failover Configurations You can configure SCADA server failover from an iclient or from a SCADA server that also functions as an iclient. The following figure illustrates a SCADA server failover configuration from an iclient. iclient Alarm Acknowledgement Synchronization Primary SCADA Node Backup SCADA Node PLC Figure 2-2: SCADA Server Failover Configuration from an iclient The following figure illustrates a SCADA server failover configuration that involves two SCADA servers. Chapter 2. Failover and Redundancy 27

42 Local Node Name: PACKER1 Local Node Name: PACKER2 Alarm Acknowledgement Synchronization Primary SCADA Node Backup SCADA Node PLC Figure 2-3: SCADA Server Failover Configuration from a SCADA Server Even in this simple configuration, you want most applications on your iclients referencing the same database. In this example, when PACKER1 and PACKER2 have established a session, PACKER2 accesses information through PACKER1. In this configuration, automatic failover to the local node occurs if the remote node session is lost. Once the local node is active, only a manual failover will make the remote node active. Refer to the Working with the Network Status Server section for information on initiating a manual failover. Primary and Backup Groupings SCADA server failover uses a logical node name to represent the physical names of the primary and backup SCADA nodes. The primary node is the SCADA server you want the iclient to communicate with at startup. The backup node is the SCADA server you want the iclient to communicate with if the primary node becomes unavailable. The applications on the iclient communicate to the logical node name, and ifix substitutes the physical node name at run time based on which SCADA server is available. The combination of the logical node name and physical primary and backup SCADA server names is referred to as the primary and backup grouping. You configure the primary and backup grouping in the SCU of the iclient and of each SCADA server. 28 Mastering ifix

43 For all figures included in this section, the Local Node Names and Local Logical Names are configured in the Local Startup Definition dialog box of the SCU. The primary and backup groupings are configured in the Configured Remote Nodes section of the Network Configuration dialog box of the SCU. The Partner SCADA name, used for alarm acknowledgement synchronization, is configured in the SCADA Name text box in the Partner SCADA section of the SCADA Configuration dialog box in the SCU. NOTE: Ensure that the local logical node names are defined on the primary and backup SCADA nodes before configuring the primary and backup grouping. Define local logical node names in the Local Startup Definition dialog box of each SCADA node s SCU. Configuration Example 1 The following figure provides an example of a primary and backup grouping. Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Local Node Name: PACKER1 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Partner SCADA: PACKER2 iclient Local Node Name: PACKER2 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Partner SCADA: PACKER 1 Primary SCADA Backup SCADA PLC Figure 2-4: Typical Configuration of an iclient with a Primary and Backup SCADA Chapter 2. Failover and Redundancy 29

44 Configuration Example 2 The following figure shows a configuration that involves two SCADA servers that also serve the iclient function. Primary and Backup Grouping Logical Name: LGCL_ND2 Primary SCADA: PACKER3 Backup SCADA: PACKER4 Partner SCADA: PACKER 4 Local Node Name: PACKER3 Local Logical Name: LGCL_ND2 Primary and Backup Grouping Logical Name: LGCL_ND2 Primary SCADA: PACKER3 Backup SCADA: PACKER4 Partner SCADA: PACKER 3 Local Node Name: PACKER4 Local Logical Name: LGCL_ND2 Primary SCADA Backup SCADA PLC Figure 2-5: SCADA Server Configuration with a Backup SCADA Invalid Configuration Example 1 A SCADA server can only be used in one primary and backup grouping. For example, PACKER2 cannot be part of the primary and backup groupings of both LGCL_ND1 and LGCL_ND2, as illustrated in the next figure. The primary and backup grouping must be used by all iclients that communicate with the SCADA server. In addition, if a SCADA server is part of a primary and backup grouping, it can only be accessed by ifix iclients, and only as a pair. The nodes in the pair cannot be accessed individually. The following figure shows invalid primary and backup grouping configuration: 30 Mastering ifix

45 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Primary and Backup Grouping Logical Name: LGCL_ND2 Primary SCADA: PACKER2 Backup SCADA: PACKER3 iclient iclient Primary SCADA Backup SCADA Local Node Name: PACKER1 Local Node Name: PACKER2 Local Logical Name: LGCL_ND1 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Primary and Backup Grouping Logical Name: LGCL_ND1 Figure 2-6: Invalid Primary and Backup Grouping Configuration To work correctly, the second iclient can be connected in either of the following ways: Configured with the logical node name LGCL_ND1 and connected to PACKER1 and PACKER2 Configured with a different logical node name, such as LGCL_ND2, and connected to two SCADA servers other than PACKER1 and PACKER2, such as PACKER3 and PACKER4 The following figure illustrates the second case. Chapter 2. Failover and Redundancy 31

46 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Primary and Backup Grouping Logical Name: LGCL_ND2 Primary SCADA: PACKER3 Backup SCADA: PACKER4 iclient iclient Primary SCADA Backup SCADA Primary SCADA Backup SCADA Local Node Name: PACKER1 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Partner SCADA: PACKER 2 Local Node Name: PACKER2 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Partner SCADA: PACKER 1 Local Node Name: PACKER3 Local Logical Name: LGCL_ND2 Primary and Backup Grouping Logical Name: LGCL_ND2 Primary SCADA: PACKER3 Backup SCADA: PACKER4 Partner SCADA: PACKER 4 Local Node Name: PACKER4 Local Logical Name: LGCL_ND2 Primary and Backup Grouping Logical Name: LGCL_ND2 Primary SCADA: PACKER3 Backup SCADA: PACKER4 Partner SCADA: PACKER 3 Figure 2-7: Correct Primary and Backup Grouping Configuration Invalid Configuration Example 2 A SCADA server with a logical node name should only be accessed by clients using the correct logical node name, primary SCADA, and backup SCADA configuration. It is unsupported to access a single SCADA in a SCADA server pair. The following figure shows invalid SCADA configuration in a SCADA server pair: 32 Mastering ifix

47 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Primary and Backup Grouping Remote SCADA: PACKER1 iclient iclient Primary SCADA Backup SCADA Local Node Name: PACKER1 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Partner SCADA: PACKER2 Local Node Name: PACKER2 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Partner SCADA: PACKER 1 Figure 2-8: Invalid SCADA Configuration in a SCADA Server Pair Invalid Configuration Example 3 Only ifix SCADA servers can be accessed as part of a primary and backup grouping. It is unsupported to access an ifix SCADA server and a SCADA server using any version of FIX. The following figure shows an invalid SCADA server configuration that involves an ifix SCADA server and a FIX version 7.x SCADA server: Chapter 2. Failover and Redundancy 33

48 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 iclient Primary SCADA (ifix) Backup SCADA (FIX version 6.x) Local Node Name: PACKER1 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Partner SCADA: PACKER2 Local Node Name: PACKER2 Local Logical Name: LGCL_ND1 Primary and Backup Grouping Logical Name: LGCL_ND1 Primary SCADA: PACKER1 Backup SCADA: PACKER2 Partner SCADA: PACKER 1 Figure 2-9: Invalid Version Configuration in a SCADA Server Pair Configuring SCADA Server Failover This section provides detailed information on configuring SCADA server failover. IMPORTANT: ifix does not synchronize the process databases on the SCADA servers. You must ensure that both databases are identical. If you are using a System Extension Toolkit (STK), make sure the block type and index of each tag referenced on the iclient are identical on both SCADA servers. Updating the HOSTS File for SCADA Server Failover NOTE: You only need to update the HOSTS file on your iclient if you are using TCP/IP. 34 Mastering ifix

49 If you are using SCADA server failover, you need entries for the node names of the primary and backup SCADA servers. For example, if the physical name of the primary SCADA server is PACKER1 and the backup SCADA server is PACKER2, you need entries for both in your HOSTS file, as shown in the following example: PACKER PACKER2 You must configure the logical node names for the primary and backup SCADA pair in the SCU of each iclient using SCADA server failover. Configuring the SCADA Server Pair Use the SCU to configure both SCADA servers in the pair. Enabling SCADA Server Failover You can enable SCADA server failover on the iclient by entering a primary and backup grouping in the SCU. By default, SCADA server failover is not enabled. Disabling SCADA Server Failover You can disable SCADA server failover by deleting the primary and backup grouping in the SCU and clearing the partner SCADA in the SCADA Configuration dialog box of each SCADA server. Synchronizing the Clocks on the SCADA Servers To ensure that all iclients see the same data and alarms, synchronize the clocks on both the primary and backup SCADA servers. If the clocks are not synchronized and failover occurs, alarms received from the primary and backup nodes could have significantly different timestamps, even if both alarms were generated at the same instant. You can synchronize the SCADA clocks using the NET TIME command. Refer to the Windows Help system for more information. Chapter 2. Failover and Redundancy 35

50 Assigning Manual Failover Privileges The Manual Failover feature allows you to manually initiate failover from the active SCADA server to the non-active SCADA server if security is enabled. Manual Failover privileges are assigned to users or groups who are allowed to manually initiate SCADA failover. IMPORTANT: LAN redundancy is neither affected by the Manual Failover feature nor controllable by ifix security. Refer to the Implementing Security manual for more information on configuring ifix security. Understanding LAN Redundancy When LAN redundancy is enabled, an ifix iclient establishes and maintains two network paths to the SCADA server. These managed connections are referred to as the active and non-active network paths. ifix monitors the non-active network path by periodically sending messages to ensure that it remains available. When the active network path becomes unavailable, ifix automatically fails over to the non-active network path. You can add links to your pictures to monitor the availability of the non-active path. For more information, refer to the Working with the Network Status Server section. Multiple LAN support is always enabled when you have more than one available network path. This means that if you have several available and enabled network paths and LAN redundancy is not enabled, ifix attempts to connect to all available paths and keeps the first successful connection. Any other successful connections are closed. However, LAN redundancy is not automatically enabled. You must enable this feature on all the nodes on which you want to use LAN redundancy. If LAN redundancy is enabled, ifix establishes connections on each of the two paths and manages them both. LAN redundancy is only supported on ifix iclients and SCADA servers, not on nodes running any version of FIX. 36 Mastering ifix

51 LAN Failover Messages You can use a Network Status Server tag or the messages to identify when a LAN failover has occurred. Refer to the Working with the Network Status Server section for more information. ifix sends a message whenever LAN failover occurs. This message never appears at the remote nodes. The following are examples of LAN failover messages for each protocol. NetBIOS If you are communicating from an iclient named STATION1 over LANA 3 to a SCADA node named PACKER1, and the session is lost and reestablished over LANA 2, the message on the iclient is: 19:24:00.0 [STATION1] Switched network path to node PACKER1 from lana 3 to lana 2 TCP/IP If you are communicating from an iclient named STATION1 over TCP/IP address to a SCADA node named PACKER1, and the session is lost and re-established over TCP/IP address , the message on the iclient is: 19:24:00.0 [STATION1] Connection to [PACKER1] switched to to Reading and Writing Data After a LAN failover occurs, displays continue to update. However, the applications treat LAN failover as a session loss and send application messages to report this condition. You can suppress these application messages. Historical Collect continues to collect data after session loss and re-establishment. However, you may see a gap in the data for the length of time that it took the LAN failover to occur. Alarm Handling for LAN Redundancy The Alarm Startup Queue Service is automatically enabled. This service ensures that alarms are not lost during session loss and reconnection. Chapter 2. Failover and Redundancy 37

52 If you are using NetBIOS, the data and alarm sessions may be on separate LANs. If you are using TCP/IP, the data and alarm sessions will always be over the same LAN because they are using the same socket. LAN Redundancy Configuration The typical LAN redundancy configuration consists of two network adapter cards in an iclient and two in a SCADA server. This creates two independent network paths, as illustrated in the following figure. Network Path 1 Network Path 2 iclient SCADA Node Figure 2-10: Typical LAN Redundancy Configuration The following figure illustrates an iclient using LAN redundancy with an excluded card. The SCADA server has two network cards and an I/O driver Ethernet card that is excluded from LAN redundancy. 38 Mastering ifix

53 iclient SCADA Node I/O Driver Network Card PLC Figure 2-11: LAN Redundancy Configuration with an Excluded Card Configuring LAN Redundancy This section provides detailed information on configuring LAN redundancy. Enabling LAN Redundancy On each computer that uses LAN redundancy, use the SCU to enable both network paths and then to select the Enable LAN Redundancy check box. Once you enable LAN redundancy in the SCU, you must also update the HOSTS file on each computer for LAN redundancy to work properly. NOTE: If you are using LAN redundancy in addition to SCADA server failover, you must enable LAN redundancy on the iclient and on each partner SCADA server. Updating the HOSTS File for LAN Redundancy NOTE: You only need to update the HOSTS file on your iclient and your SCADA nodes if you are using TCP/IP. Chapter 2. Failover and Redundancy 39

54 After you enable LAN redundancy in the SCU of each computer, you must edit the HOSTS file on each computer to add entries for each network path. The HOSTS file is typically located in the WINNT\System32\drivers\etc directory. You need an entry for each network card. The names assigned to the second LAN must be the same as the names assigned the first LAN followed by a dash and the letter R (-R). For example, if the network cards on one LAN are STATION1 and PACKER1, the names on the second LAN must be STATION1-R and PACKER1-R, as shown in the following example: STATION PACKER STATION1-R PACKER1-R NOTE: If you are using LAN redundancy in addition to SCADA server failover, you must update the HOSTS file on the iclient and on each partner SCADA server. Refer to the Setting Up the Environment manual for more information on TCP/IP and hosts files. Disabling LAN Redundancy Use the SCU to disable LAN redundancy on both nodes. Optimizing System Performance To increase efficiency and reduce downtime during failover: Disable unnecessary network paths Balance network timers and failover time You may want to disable (or exclude) network paths from LAN redundancy to eliminate a slow or expensive path, or a path that you want to dedicate to a particular function (such as an I/O driver). 40 Mastering ifix

55 Disabling Network Paths In addition to enabling LAN redundancy, you may also want to disable certain network paths that you do not want to use. If you do this, you must ensure that the configurations are the same on both nodes. For example, you may want to disable network path 1 on both nodes. Re-Enabling Previously Disabled Network Paths All paths are enabled by default. However, if you have previously disabled a network path, you can re-enable it. Balancing Network Timers and Failover Time While multiple LAN support has one managed connection, LAN redundancy has two managed connections. LAN failover time from the active path to another available path on the same SCADA includes the time required to: Detect a connection loss Establish or switch low level connections Send an ifix connection establishment message Because re-establishment of a lost connection occurs over all paths in parallel using the first successful connection, LAN failover after the detection of a lost session takes normal session establishment time. With LAN redundancy enabled, ifix establishes and maintains two managed connections. Rebroadcast is unnecessary, allowing faster failover to the good connection in the event of connection loss. The total downtime when using NetBIOS is the time for the send timer plus the normal session establishment time. The total downtime when using TCP/IP is the greater of the send or receive timer plus the normal session establishment time. Configuring network session timers reduces the time it takes to detect a connection loss and, consequently, reduces downtime. Refer to the Setting Up the Environment manual for information on customizing network session timers. Chapter 2. Failover and Redundancy 41

56 CAUTION: Do not change the session timers unless you fully understand how they work and the consequences of what you are doing. If you make the timers too low, you could lose sessions. If you make them too high, it may take too long to fail over. Enabling the Alarm Startup Queue Service The Alarm Startup Queue Service is enabled by default when you enable networking and SCADA. This ensures that the iclient receives all alarms after a failover occurs. The Alarm Startup Queue Service provides the iclient with a list of alarms that occurred on the SCADA server prior to the time the iclient started. Refer to the Implementing Alarms and Messages manual for more information about this service. Working with the Network Status Server The Network Status Server (NSS) allows you to write application programs and create displays that monitor and control ifix networking. This section explains how to use the Network Status Server on the iclient to: Monitor network status Manually initiate failover to the non-active SCADA Temporarily disable automatic SCADA or LAN failover Trigger an event on failover to the non-active SCADA or LAN Monitoring Network Status You can monitor the status of the network using the NSS diagnostic fields. This feature allows you to monitor sessions on your network, determine which nodes are active, and display the name of the local node. In the event that a SCADA server becomes unavailable, you can also display an error code and text describing the current state of the connection with each SCADA server. ifix provides the NSD tag that you can use when designing displays for monitoring and controlling SCADA server failover and LAN redundancy. This tag is not a database block. It is a special tag residing on each networked node that displays diagnostic, failover, and network information. Refer to the table of available Network Status Server fields in the Network Status Server Fields section. 42 Mastering ifix

57 To access the fields, use the server.node.nsd.field syntax. In the following example, PACKER1 is the local physical name. NSD is always the tag. FIX32.PACKER1.NSD.A_PRIMARYSCADA_0 Refer to Table 2-1 for more information on the Network Status Server fields. Initiating Manual Failover to the Non-active SCADA In addition to automatic SCADA failover, you can also manually force a SCADA failover to occur at any time. For example, you can manually switch to the non-active node when the active node needs to be shut down for maintenance. If you are using a SCADA server that also functions as an iclient and the local node is active, you must initiate a manual failover to make the remote node active. To perform a manual failover, write to the A_CURACTIVENODE or F_CURACTIVENODE Network Status Server field. A 0 in this field indicates that the primary node is the active node; a 1 indicates that the backup node is the active node. Refer to Table 2-1 for more information on the Network Status Server fields. Temporarily Disabling Automatic Failover You may want to temporarily disable automatic failover when network connections are unreliable. To temporarily disable automatic failover to the non-active SCADA, write to the A_FAILDISABLE or F_FAILDISABLE Network Status Server field. A 0 in this field indicates that automatic SCADA failover is enabled if it is configured; a 1 disables automatic SCADA failover. Manual failover is still possible. To temporarily disable automatic LAN failover on a per connection basis, write to the A_LANFAILDSABL or F_LANFAILDSABL Network Status Server field. For F_LANFAILDSABL, 0 indicates that automatic LAN failover is enabled if it is configured; a 1 disables automatic LAN failover. For A_LANFAILDSABL, Enabled indicates that automatic LAN failover is enabled if it is configured; Disabled indicates automatic LAN failover is disabled. Refer to Table 2-1 for more information on the Network Status Server fields. Chapter 2. Failover and Redundancy 43

58 Triggering an Event on Failover You may want to trigger an event when a failover occurs. For example, you may want to display a message informing the operator of the failover, and once the operator acknowledges the message, close a valve or sound an alarm. Use the Scheduler to create schedules to do this. Refer to the Creating and Editing Schedules and Entries section for more information. To trigger an event on SCADA failover, write to the A_FAILOVER or F_FAILOVER Network Status Server field. This field is set to 1 on automatic or manual failover. You must reset it to 0 to receive notification of subsequent failovers. To see if any connection has had a SCADA failover, read to the F_SCADAANYFAILOVER field. It is set to non-zero if any F_FAILOVER field is set to non-zero. To trigger an event on LAN failover, write to the F_LANFAILOVER or A_LANFAILOVER field. This field is set to 1 on LAN failover. You must reset it to 0. To see if any connection has had a LAN failover, read to the F_LANANYFAILOVER field. It is set to non-zero if any F_LANFAILOVER field is set to non-zero. Refer to Table 2-1 for more information on the Network Status Server fields. Using the ifix Diagnostic Display ifix supplies a diagnostic display that contains links referencing diagnostic NSS fields. This display, called NetworkStatusDisplay.GRF, allows you to view the local node name, each incoming connection, each outgoing connection, and each connection's status. This display always shows the logical node name even if the backup node is the active node. NOTE: If you want to use the NSD picture on an iclient, you must first Search and Replace all instances of THISNODE with the local iclient name. The NetworkStatusDisplay.GRF file is provided in the Picture path of your iclient. You need to modify this file to reference your local node name. 44 Mastering ifix

59 Accessing SCADA Servers Using True Links If you want to read data from or write data to a specific SCADA server, you can access it by using its physical node name. Links that use the physical node name are referred to as true links. The SCADA server can be active or non-active, but a session must be established to it. If a diagnostic display shows data from a SCADA server using true links, data will not be available at the iclient if communication with that SCADA server is lost. Reading Data Displays with links to tagnames on the logical SCADA always attempt to show data from the active SCADA, regardless of whether it is the primary or backup SCADA. This is done without requiring the picture to be opened, closed, or replaced. When an iclient establishes a connection to an active SCADA server node, it starts to read data from that node. When the active SCADA server node becomes unavailable, the iclient loses its session with that node, causing a message box to appear with following message: Node.Tag.Field Connection Not Established With Node To disable this message, you can edit the FilteredErrors.ini file, which is located in the Dynamics\Local directory, to include error number Once you have edited this file you must restart the Intellution ifix WorkSpace for the change to take effect. When the iclient switches to the non-active node, the following events occur: [1] The links in the open pictures on the iclient symbols (as the default) to indicate that the session with the active node has been lost. [2] The non-active node becomes the active node and the failed node becomes the non-active node. [3] The pictures resolve automatically using the information from the new active node. This ensures data integrity. [4] signs are replaced with process data from the new active node. The node name referenced by these links does not change; it continues to display the name of the logical node. Chapter 2. Failover and Redundancy 45

60 [5] An event message indicating that a failover has occurred is sent to all alarm destinations configured for the iclient when failover occurs. NOTE: You can change the signs using the Comm Error setting on the Animations Data Error Defaults tab in the Users Preference dialog box of the Intellution WorkSpace. Creating Displays Using Logical and Physical Node Names You can use either the logical or physical node name in displays to access data. This section explains the impact of using one or the other and uses the Intellution WorkSpace as an example. This also applies to VBA scripts and any application that uses EDA (Easy Data Access) to access process data, such as Historical Collect. For more information, refer to the Writing Scripts manual. Pictures with links to tagnames on the logical SCADA always attempt to display data from the active SCADA, regardless of whether it is the primary or backup SCADA. This is done without requiring the picture to be opened, closed, or replaced after failover. If you want to access data from a specific SCADA server (and a session is established to it), you can read data from and write data to both the primary and backup SCADA, regardless of which one is active. Links that use the physical node name are referred to as true links. The picture displays data from the physical SCADA server specified. If communication with that SCADA server is lost, the data from the true links will not be available at the iclient after failover. NOTE: If you are using logical node names and SCADA server failover, you must ensure that the tags and fields are the same on both the backup and primary SCADA databases. If they are different, the message, Tag not found is displayed when failover occurs. For example, if the link to logical SCADA PACKER1 is PACKER1.DI_VALVE_OPEN.F_CV, and a failover to PACKER2 occurs, then the picture displays the data from PACKER2.DI_VALVE_OPEN.F_CV. Network Status Server Fields The following table lists the fields that are available in the NSS. 46 Mastering ifix

61 Zero-based NSD Fields In the table, _0 through _100 appended to field names indicates that information is available on a per-connection basis. When _0 is appended to a field name, the information pertains to the local node. Since there can be up to 100 node names in the SCU, _1 through _100 typically correspond to the ordering of the names in the SCU. However, any primary and backup grouping in the SCU that contains the local node name is always located at index _0. One-based NSD Fields If the field is 1-based, when _1 is appended to a field name, the information pertains to the local node. _2 through _100 typically correspond to the ordering of the names in the SCU. Any primary and backup grouping in the SCU that contains the local node name is located at index _1. Table 2-1: Network Status Server (NSS) Fields Field Name A_ACONNREASON_0 through A_ACONNREASON_100 A_ACTIVEPATH_0 through A_ACTIVEPATH_100 F_ACTIVEPATH_0 through F_ACTIVEPATH_100 A_ACTIVESCADA_1 through A_ACTIVESCADA_100 A_ACTIVESTATUS_0 through A_ACTIVESTATUS_100 F_ACTIVESTATUS_0 through F_ACTIVESTATUS_100 A_ALOCALADDR_0 through A_ALOCALADDR_100 Description The current state of the connection to the active node. This is either Established or text describing the current state. Indicates if the active path is the primary or backup path. A 0 in this field indicates that the primary path is the active path; a 1 indicates that the backup path is the active path. Active SCADA server name, which can be either the primary or backup node name. Status of the connection to the active SCADA (OK or an error code). It will be one of the primary, logical, or backup statuses. This is for the active network connection. For TCP/ IP, displays the local IP address used to reach the remote node. For NetBIOS, it is the LANA number. Chapter 2. Failover and Redundancy 47

62 Table 2-1: Network Status Server (NSS) Fields (continued) Field Name A_APATHSTATUS_0 through A_APARTHSTATUS_100 F_APATHSTATUS_0 through F_APATHSTATUS_100 A_AREMOTEADDR_0 through A_AREMOTEADDR_100 A_BACKUPPATH_0 through A_BACKUPPATH_100 A_BACKUPSCADA_0 through A_BACKUPSCADA_100 A_BACKUPSTATUS_0 through A_BACKUPSTATUS_100 F_BACKUPSTATUS_0 through F_BACKUPSTATUS_100 A_BCONNREASON_0 through A_BCONNREASON_100 A_BLOCALADDR_0 through A_BLOCALADDR_100 A_BPATHSTATUS_0 through A_BPATHSTATUS_100 F_BPATHSTATUS_0 through F_BPATHSTATUS_100 A_BREMOTEADDR_0 through A_BREMOTEADDR_100 Description Status of the connection over the active path. This is either the primary or backup status. This is for the active network connection. For TCP/ IP, displays the IP address of the remote node. For NetBIOS, this field is empty. Backup network path. When using LAN redundancy, it shows the paths per connection. When ifix is using NetBIOS, it is the LANA number. For TCP/IP it is the IP address. Backup SCADA server name for this connection. Status of the connection to the backup SCADA (OK or an error code). The current state of the connection to the backup node. This is either Established or text describing the current state. This is for the backup network connection. For TCP/ IP, displays the local IP address used to reach the remote node. For NetBIOS, it is the LANA number. Status of the connection to the backup network path. This is for the backup network connection. For TCP/ IP, displays the IP address of the remote node. For NetBIOS, this field is empty. 48 Mastering ifix

63 Table 2-1: Network Status Server (NSS) Fields (continued) Field Name A_CONNDIRECTION A_LANFAILDSABL_0 through A_LANFAILDSABL_100 A_LOCALNAME A_LOGICALNAME_0 through A_LOGICALNAME_100 A_LOGICALSCADA_0 through A_LOGICALSCADA_100 A_LOGICALSTATUS_0 through A_LOGICALSTATUS_100 F_LOGICALSTATUS_0 through F_LOGICALSTATUS_100 A_NETNAME_0 through A_NETNAME_100 A_PCONNREASON_0 through A_PCONNREASON_100 A_PLOCALADDR_0 through PLOCALADDR_100 Description Indicates whether the connection is incoming or outgoing. > if outgoing. < if incoming. < > if both outgoing and incoming. Enabled in this field indicates that LAN redundancy is enabled if it is configured; Disabled indicates LAN redundancy is disabled. Use this field to disable LAN redundancy on a per connection basis. Displays the local physical node name. Logical SCADA server name for this connection. (Same as A_LOGICALSCADA and retained for backwards compatibility.) Logical SCADA server name for this connection. Status of the connection to the logical SCADA (OK or an error code). Name used to connect to the remote node. For TCP/ IP it is the remote node name. For NetBIOS, _FIX, _SRV, or _DMACS may be appended to the remote node name. The current state of the connection to the primary node. This is either Established or text describing the current state. This is for the active network connection. For TCP/ IP, displays the local IP address used to reach the remote node. For NetBIOS, it is the LANA number. Chapter 2. Failover and Redundancy 49

64 Table 2-1: Network Status Server (NSS) Fields (continued) Field Name A_PPATHSTATUS_0 through A_PPATHSTATUS_100 F_PPATHSTATUS_0 through F_PPATHSTATUS_100 A_PREMOTEADDR_0 through A_PREMOTEADDR_100 A_PRIMARYPATH_0 through A_PRIMARYPATH_100 A_PRIMARYSCADA_0 through A_PRIMARYSCADA_100 A_PRIMARYSTATUS_0 through A_PRIMARYSTATUS_100 F_PRIMARYSTATUS_0 through F_PRIMARYSTATUS_100 A_PROTOCOL F_ALLOWREMOTEWRITES F_CURACTIVENODE_0 through F_CURACTIVENODE_100 A_CURACTIVENODE_0 through A_CURACTIVENODE_100 Description Status of the connection over the primary network path. This is for the active network connection. For TCP/ IP, displays the IP address of the remote node. For NetBIOS, this field is empty. Primary network path. When using LAN redundancy, it shows the paths per connection. When ifix is using NetBIOS, it is the LANA number. For TCP/IP it is the IP address. Primary SCADA server name for this connection. Status of the connection to the primary SCADA (OK or an error code). Displays the current protocol (NetBIOS or TCP/IP) that ifix is using for networking. This field is 1 if remote nodes are allowed to write to the NSD fields on this node, or 0 if writes are not allowed. Indicates if the active node is the primary or backup SCADA. A 0 in this field indicates that the primary SCADA is the active node; a 1 indicates that the backup SCADA is the active node. You can write to this field to perform a manual failover. 50 Mastering ifix

65 Table 2-1: Network Status Server (NSS) Fields (continued) Field Name F_FAILDISABLE_0 through F_FAILDISABLE_100 A_FAILDISABLE_0 through A_FAILDISABLE_100 F_FAILOVER_0 through F_FAILOVER_100 A_FAILOVER_0 through A_FAILOVER_100 F_FAILOVERMANL_0 through F_FAILOVERMANL_100 F_FAILOVERTOTAL_0 through F_FAILOVERTOTAL_100 F_LANANYFAILOVER F_LANFAILDSABL_0 through F_LANFAILDSABL_100 F_LANFAILOVER_0 through F_LANFAILOVER_100 A_LANFAILOVER_0 through A_LANFAILOVER_100 F_LANFLOVRTOTAL_0 through F_LANFLOVRTOTAL_100 Description SCADA server failover state. A 0 in this field indicates that SCADA server failover is enabled if it is configured; a 1 disables SCADA server failover. Manual failover will still be possible. You can write to this field to disable automatic failover to the non-active SCADA on a perconnection basis. This field is set to 1 on automatic or manual SCADA failover. You must reset it to 0 to receive notification of subsequent failovers. You can read to this field to trigger an event on SCADA failover. Total number of manual failovers to this node since ifix startup. Total number of failovers (automatic and manual) to this node name since ifix startup. Use this field to see if any connection has had a LAN failover. It is set to non-zero if any F_LANFAILOVER_# field is set to non-zero. A 0 in this field indicates that LAN redundancy is enabled if it is configured; A 1 indicates LAN redundancy is disabled. Use this field to disable LAN redundancy on a per connection basis. This field is set to 1 on LAN failover. You must reset it to 0. Total number of automatic failovers to this path since ifix startup. Session losses that are re-established over the same network path are not included. Chapter 2. Failover and Redundancy 51

66 Table 2-1: Network Status Server (NSS) Fields (continued) Field Name F_SCADAANYFAILOVER F_TRANSACTTIME_0 through F_TRANSACTTIME_100 Description Use this field to see if any connection has had a SCADA failover. It is set to non-zero if any F_FAILOVER_# field is set to non-zero. Indicates the amount of time, in milliseconds, that it took this iclient to get data from the SCADA server the last time data transfer occurred. Troubleshooting This section provides information for troubleshooting problems that you may encounter when you are implementing ifix failover and redundancy. Problem Nodes are not connecting for LAN redundancy. Check the SCU configuration and ensure that both nodes have the same network paths enabled. Refer to the Setting Up the Environment manual for more information. Check the hosts file and ensure that the name assigned to the second LAN is the same as the names assigned to the first LAN followed by a dash and the letter R (-R). Refer to the Updating the HOSTS File for LAN Redundancy section for more information. Problem Alarms are being lost during failover periods. Make sure that the Alarm Startup Queue is enabled and that the queue size is large enough to handle the alarms. Refer to the Implementing Alarms and Messages manual for more information on this service. 52 Mastering ifix

67 Problem Alarms are missing from the summary link or alarms appear and disappear in the alarm summary link. Make sure that the Alarm Summary Queue on the node is twice big as it would normally be if the node were not part of a SCADA server failover pair. For example, if you are generating 500 alarms, the Alarm Summary Queue must be set to Refer to the Implementing Alarms and Messages manual for more information on queue sizes. Problem Alarms that were acknowledged need to be re-acknowledged after failover. Ensure that the Partner SCADA field has been checked in the SCADA server's SCU. Refer to the Setting Up the Environment manual for information on configuring the SCU. Problem The iclient using logical node names cannot connect to a partner SCADA. Make sure that the iclient is using the correct logical, primary, and backup names. Refer to the Configuring SCADA Server Failover section. Problem Alarm acknowledgement synchronization is not occurring. Make sure that alarm acknowledgement synchronization is enabled in the SCU. Once alarm acknowledgement synchronization is enabled, you can confirm that it is working using Mission Control. Refer to the Setting Up the Environment manual for more information. Problem Failover takes a long time. Chapter 2. Failover and Redundancy 53

68 54 Mastering ifix Adjust the session timers. Refer to the Setting Up the Environment manual for more information.

69 3. Local Node Alias The local node alias feature allows ifix local SCADA nodes to share pictures, recipes, and historical collection groups across nodes without changing the node name. When you use this feature, you can create generic pictures and recipes and save development and maintenance time. Enabling Local Node Alias Before you can use the local node alias features you must enable the local node alias feature in the SCU. Using Local Node Alias Once you have enabled the local node alias feature, you can use the THISNODE placeholder in the node portion of the tagname (NODE.TAG.FIELD). ifix substitutes the local physical node name for the THISNODE placeholder, increasing the portability of pictures and recipes and eliminating the need to change tagname references for different nodes. The system tree in the Intellution WorkSpace always shows the actual node represented by the THISNODE placeholder. If, for example, you have ten production lines that produce similar products, you can create one generic display that can access real-time data from any of the ten lines. By using the THISNODE placeholder, if you need to change the display, you only need to make the change once. Refer to the Setting Up the Environment manual for more information. Local Node Alias Examples The local node alias feature can be used for pictures, recipes, and historical collection groups, as illustrated in the following examples. Chapter 3. Local Node Alias 55

70 Picture Example Assume that you have a Data link in a picture that is configured with the tagname FIX32.THISNODE.AI-1.F_CV, and your local SCADA node name is CANLINE1. When you open the picture, the Data link behaves as if it were configured as FIX32.CANLINE1.AI-1.F_CV. If you open the same picture on a different computer whose local SCADA node name is CANLINE2, the Data link s tagname resolves to FIX32.CANLINE2.AI-1.F_CV. Recipe Example Assume that you have two SCADA nodes: FERMENTER1 and FERMENTER2. The recipes Beer1 and Beer2 are used to make beer and download to FERMENTER1 and FERMENTER2, respectively. The Beer1 recipe defines the following items: Identifier Formula FERMENTER1:ILK1.F_CV 0 FERMENTER1:XCV1F1.F_CV 0 FERMENTER1:W16S1.F_CV 150 FERMENTER1:T16F.F_CV 55 FERMENTER1:K16F1.F_CV 132 The Beer2 recipe is identical except for the node name: Identifier Formula FERMENTER2:ILK1.F_CV 0 FERMENTER2:XCV1F1.F_CV 0 FERMENTER2:W16S1.F_CV 150 FERMENTER2:T16F.F_CV 55 FERMENTER2:K16F1.F_CV Mastering ifix

71 In this implementation, both recipes are required because each recipe has hard-coded node name references. The local node alias feature eliminates the need for two recipes. Instead, you can create one recipe for both SCADA nodes, as shown in the following example: Identifier Formula THISNODE:ILK1.F_CV 0 THISNODE:XCV1F1.F_CV 0 THISNODE:W16S1.F_CV 150 THISNODE:T16F.F_CV 55 THISNODE:K16F1.F_CV 132 After you create this recipe, share the directory that it resides in and map the recipe paths of both SCADA servers to the shared directory. For information on changing the recipe paths, refer to the Creating Recipes manual. Historical Collection Group Example Assume that you want to create a chart using the tank level and tank temperature from the two SCADA nodes in the Recipe example. On FERMENTER1 these tagnames are: Identifier Tank Level Tank Temperature Formula FIX32.FERMENTER1.AI_LEVEL.F_CV FIX32.FERMENTER1.AI_TEMP.F_CV Chapter 3. Local Node Alias 57

72 On FERMENTER2 these tagnames are: Identifier Tank Level Tank Temperature Formula FIX32.FERMENTER2.AI_LEVEL.F_CV FIX32.FERMENTER2.AI_TEMP.F_CV When you define the pens for the chart, use the following data sources: FIX32.THISNODE.AI_LEVEL.F_CV and FIX32.THISNODE.AI_TEMP.F_CV. If you open the chart on FERMENTER1, the tagnames resolve to FIX32.FERMENTER1.AI_LEVEL. F_CV and FIX32.FERMENTER1.AI_TEMP.F_CV. If you open it on FERMENTER2, the tagnames resolve to FIX32.FERMENTER2.AI_LEVEL. F_CV and FIX32.FERMENTER2.AI_TEMP.F_CV. 58 Mastering ifix

73 4. Reporting Detailed reports are important tools for reviewing the performance of a process. They allow you to quickly grasp the relationships between specific pieces of manufacturing process data so that you can make effective decisions. Using any third-party reporting application that supports ODBC queries, you can create customized reports based on ifix real-time and historical data. When you use ifix real-time data, you generate the report with current data extracted from a FIX database. When you create a report using ifix historical data, you generate the report based on data gathered over a period of time. Once generated, reports can be printed or displayed in the Intellution WorkSpace. The ability to display reports directly in the Intellution WorkSpace allows you to quickly view a report from any number of nodes in your system, greatly reducing the time it takes for you to make informed decisions about your process. For your reporting solution, we recommend using Seagate Crystal Reports Professional Version 8.5. This reporting application uses ODBC to access ifix data sources, allowing you to create professional, customized reports. The Report Experts included in Crystal Reports make the process of defining your query and designing the layout of your report quick and easy. This application provides unlimited sorting capability and lets you insert informative graphs that help you to effectively analyze your process data. Once created, your queries can be saved so you can quickly generate future reports based on these predefined queries. Crystal Reports v8.5 run-time DLL installation is included on the ifix CD. These DLLs allow you to enable the target system to execute Crystal Reports without requiring a development copy to reside on each node. For complete information on using Crystal Reports, refer to the Seagate Crystal Reports documentation. ifix Report Experts ifix provides you with two Report Experts that can be used in conjunction with Crystal Reports: Print Crystal Report and Print Crystal Report Expert. To use these Experts, you must add them to the toolbox or to one of the existing toolbars. You can Chapter 4. Reporting 59

74 also create a new toolbar with the Report Experts on it. For more information on toolbars, refer to the Understanding Toolbars section of the Understanding ifix manual. Using the Report Experts To use the Report Experts, make sure you have Crystal Reports Professional Version 8.5 installed on your machine. Once you have created a report and selected the data sources you want to use in Crystal Reports, you can use the Report Experts to generate or print the report. NOTE: The fixodbc.ini file, located in the Local path, can be edited to work with Crystal Reports. You can add or delete fields that are to be included in Crystal Reports real-time queries, such as A_TAG, A_NAME, or A_NODE. Historical queries are not affected by the fixodbc.ini file. Print Crystal Report The Print Crystal Report button lets you print Crystal Reports in the configuration environment. To print a report using the Print Crystal Report button: [1] Click the Print Crystal Report button on the toolbox. [2] Click the Select Report button and select the Crystal Report you want to print. [3] Click the Preview button to view the report on your monitor and then click OK. [4] Select the print range and click OK. Print Crystal Report Expert The Print Crystal Report Expert lets you write the PrintReport script found in Factory-Globals to an object s click event. Once this is done, you can print the selected Crystal Report in the run-time environment by clicking on the object. 60 Mastering ifix

75 To tie the PrintReport script to an object s click event using the Print Crystal Report Expert: [1] Click on an object in the Intellution WorkSpace. [2] Click the Print Crystal Report Expert. [3] Click the Select Report button and select the Crystal Report you want to tie to the object s click event. [4] Select the desired print range and click OK. You can also use the Print Crystal Report Expert to write the PrintReport script to an entry in a schedule. Refer to the Script Authoring Experts section for more information on using Script Authoring Experts in a schedule. Sample Report The following is an example of a Crystal Report that was created using ifix historical data. This report could be either printed or viewed directly in the Intellution WorkSpace. Chapter 4. Reporting 61

76 Thursday 3/19/98 Color:Blue Finish Time Mixer Quantity Batch ID 11:00:23AM MIXER :59:32AM MIXER :50:40AM MIXER1 1,000 2 Blue Total: 1,949 3 Color:Green Finish Time Mixer Quantity Batch ID 10:57:42AM MIXER1 1, Mastering ifix

77 10:49:14AM MIXER Green Total: 1,873 2 Color:Red Finish Time Mixer Quantity Batch ID 10:56:46AM MIXER Red Total: Grand Total: 4,622 6 Figure 4-1: Sample Crystal Report Chapter 4. Reporting 63

78 64 Mastering ifix

79 5. The Cross Reference Tool The Cross Reference Tool is an ifix utility that allows you to create a report identifying every data source or occurrence of a data source in pictures, scripts, schedules, or a User Global. Using the Cross Reference Tool, you can also locate a text string in object names, property names, and property values. By default, the report results display in the Cross Reference Tool interface. Additionally, the Cross Reference Tool provides options that allow you to configure the report to automatically print or save upon report completion. This chapter describes the Cross Reference Tool interface and its functionality including: Understanding the Cross Reference Tool Using the Report Wizard or the Quick Report Exploring the Cross Reference Tool Interface Creating Quick Reports Creating Reports Using the Cross Reference Report Wizard Viewing the Report Results Selecting Print Options and Printing a Report Creating a Cross Reference Tool Report from the Command-Line Understanding the Cross Reference Tool The Cross Reference Tool allows you to identify where tags are used within ifix pictures, scripts, schedules, and tag groups. Additionally, you can also perform a search to find a text string. Once you select which type of search you would like to perform and define additional search options, the Cross Reference Tool creates a report that details the objects, properties, and property values that are related to that tag or text string. Chapter 5. The Cross Reference Tool 65

80 You can create three types of searches using the Cross Reference Tool: All Tags One Tag Text For detailed information regarding the report results of each search, refer to Viewing the Report Results. For information on displaying the results of a search that includes VBA scripts or that resolves tag substitutions with Tag Group files, refer to the Viewing a Search that Includes VBA Scripts and Viewing a Search that Resolves Tags Using All Tag Group Files sections. Searching for All Tags The All Tags search type returns a list of all the tags in the selected object, picture, schedule, or User Global. This search returns a list that displays the name of the object that references the tag (Object column), the property of that tag (Property column), and the tag itself (Current Value column), as shown in Figure 5-1. Figure 5-1: Report Results of a Search for All Tags Searching for One Tag The One Tag search type searches for a specific tag in the selected object, picture, schedule, or User Global, and all tag group files. You can enter a string in the Tag field or click the Browse ( ) button to open the Expression Editor. 66 Mastering ifix

81 TIP: You can also search using a partial tag name. For example, entering AI would find AI1 and TANKAI. The One Tag search also allows you to perform a find on an object in an object to object connection. Using the Cross Reference Tool report results, you could then determine which object required modification and make the change manually. This search returns the name of the object that references the tag (Object column), the property type (Property column), and the tag name (Current Value column). For example, Figure 5-2 displays a One Tag search on the partial tag name ACTIVESTATUS. Figure 5-2: Report Results for a One Tag Search Searching for Text The Text search type searches for a text string in the object names, property names, and property values of selected object, picture, schedule, or User Global. Leave <ALL> in the Text field to display all object names, property names, and property values. To search for a specific text string, enter text that would appear in the either the object name, property, or property value. NOTE: Do not use a * wildcard in this field. Entering a wildcard returns a Search completed with no output error. Chapter 5. The Cross Reference Tool 67

82 The Text search returns the object name, property, and property value in the Report Results section. If the Cross Reference Tool finds the text string in the object name, all of the object properties are listed in the Property column. For example, Figure 5-3 displays a Text search on the Text string FOREGROUNDCOLOR: Figure 5-3: Report Results of a Text Search Using the Report Wizard or the Quick Report The Cross Reference Tool offers two utilities to create a report: the Quick Report dialog box and the Cross Reference Report Wizard. The Quick Report dialog box allows you to select from the most common Cross Reference Tool search features on one picture, schedule, User Global, or object listed in the Object Tree. The Cross Reference Report Wizard allows you to search on multiple files and configure automatic saving and printing options. Use the following feature lists to help you determine when to use each tool. 68 Mastering ifix

83 Quick Report Features The Quick Report dialog box allows you to do the following: Search for all tags, one tag, or a text string in the selected picture, schedule, user global page, or object. Display the search results in the Report Results screen. Once the search completes, you can manually print out the results or choose to save the search results to a.csv,.htm,.xls, or.tb2 file. Resolve tags during a search using all tag group files. Search through VBA scripts. Include a summary of the report at the end of the report. Automatically resize report columns. Append results to the Status Trail. For more information, refer to Creating Quick Reports. Chapter 5. The Cross Reference Tool 69

84 Cross Reference Report Wizard Features The Cross Reference Report Wizard allows you to do the following: Search for all tags, one tag, or a text string in the selected picture, schedule, user global page, or object. Select multiple files to search through and arrange them in a specific order. Resolve tags during a search using all tag group files. Search through VBA scripts. Configure report settings options, including: Automatically save report to file. Automatically save a status trail as a file. Automatically print the report upon generation. Include a summary of the report at the end of the report. Automatically resize report columns. For more information, refer to Creating Reports Using the Cross Reference Report Wizard. Exploring the Cross Reference Tool Interface To open the Cross Reference Tool, click the Cross Reference Tool button, shown in Figure 5-4. Figure 5-4: Cross Reference Tool Toolbar Button The Cross Reference Tool interface includes the following sections: 70 Mastering ifix

85 Object Tree Displays pictures, schedules, and User Globals that are currently opened in the ifix WorkSpace. You can select a file or select an object within that file. NOTE: If you have opened new files in the WorkSpace since opening the Cross Reference Tool, you will need to refresh the tree in order to see them displayed. To do this, click the Refresh button in the Cross Reference Tool Toolbar. Report Results Area Displays the results of the search. Refer to Viewing the Report Results for more information. Status Trail Displays the detailed status of the report, including error messages. Refer to Viewing the Status Trail for more information. Figure 5-5 displays the Cross Reference Tool interface. Chapter 5. The Cross Reference Tool 71

86 72 Mastering ifix Figure 5-5: The Cross Reference Tool Window

87 Using the Cross Reference Tool Toolbar You can quickly access many of the Cross Reference Tool features in the Cross Reference Tool toolbar. Table 5-1 describes the functions of the Cross Reference Tool toolbar buttons. Table 5-1: Cross Reference Tool Toolbar Buttons Use this button... To... Open the Quick Report dialog box. For more information, refer to Creating Quick Reports. Save the currently displayed report. Available files types include *.CSV, *.HTM, *.XLS, or *.TB2. NOTE: Microsoft Excel enforces a maximum row limit of If you try to save a report that exceeds this row limitation in Excel, you will be prompted to continue or cancel. Please be aware that rows exceeding that limitation may be lost if you select either option. Open the Print dialog box to configure print settings and print the currently displayed report. For more information, refer to Selecting Print Options and Printing a Report. Refresh the Object Tree. If you have opened new files in the WorkSpace since opening the Cross Reference tool, you will need to refresh the tree in order to see them. Open the Font dialog box. This dialog box allows you to specify font type, size, and style. Chapter 5. The Cross Reference Tool 73

88 Table 5-1: Cross Reference Tool Toolbar Buttons (continued) Use this button... To... Open the Report Wizard dialog box. For more information, refer to Creating Reports Using the Cross Reference Report Wizard. Open the Cross Reference Tool Help. Creating Quick Reports The Quick Report dialog box, shown in Figure 5-6, appears when you open the Cross Reference Tool. In addition to allowing you to select a search type, the Quick Report dialog box also allows you to select the following search, report, and view options: Search Options Resolve Tags using All Tag Group Files If the selected file or object contains Tag Group symbols, this option resolves those symbols by attempting to match symbols with all Tag Group Definition files and finds all substitutions. This option is available for all search types. Include VBA Scripts in Search Allows the Cross Reference Tool to search through scripts within the selected file for the tag(s) or text. Report Option Include Summary Adds a summary report to the end of the Cross Reference Report detailing the number of objects and tags searched. View Options Automatically Resize Report Columns Automatically resizes the columns in the Report results to accommodate the text. 74 Mastering ifix

89 Append to Status Trail If enabled, the status trail adds any new tracking information to the existing status trail. If disabled, each time the Report runs, all previous tracking information is overwritten by the new status trail. Figure 5-6: The Quick Report Dialog Box To create a report using the Quick Report dialog box, perform the following steps: [1] Select a file or object in the Object Tree. [2] Select the desired search settings in the Quick Report dialog box. Chapter 5. The Cross Reference Tool 75

90 [3] Click the Search button. NOTE: You cannot access the ifix WorkSpace while the Cross Reference Tool generates a report. Once the report completes, you will be able to access the ifix WorkSpace again. You can also double-click an object or file in the Object Tree to run a Quick Report. This runs the Quick Report using the default settings or the settings of your last report. The results of the Quick Report display in the Report Results section of the Cross Reference Tool. You can save or print the report manually using the appropriate toolbar buttons. Creating Reports Using the Cross Reference Report Wizard The Cross Reference Report Wizard, shown in Figure 5-7, walks you through the process of creating a Cross Reference Report. The Cross Reference Report Wizard allows you to search through multiple files, and then configure the report to automatically print or save upon report completion. To create a report using the Cross Reference Report Wizard, perform the following steps: [1] Select what you want to search for and specify search options. How? [2] Choose which files the Cross Reference Tool searches and modify the search order. How? [3] Select whether the report results are automatically saved or printed and modify additional output options. How? [4] Review the wizard settings and run the report. How? Specifying Search Settings The Search Settings tab of the Cross Reference Report Wizard, shown in Figure 5-7, allows you to select the type of search that the report runs and specify the following search options: 76 Mastering ifix

91 Resolve Tags using All Tag Group Files If the selected file or object contains Tag Group symbols, this option resolves those symbols by attempting to match symbols with all Tag Group Definition files and finding all substitutions. This option is available for all search types. Include VBA Scripts in Search Allows the Cross Reference Tool to search through scripts within the selected files for the tag(s). Figure 5-7 displays the Search Settings tab of the Cross Reference Report Wizard. Figure 5-7: Cross Reference Report Wizard - Search Settings Tab Specifying Multiple Files for the Report The Files tab of the Cross Reference Report Wizard, shown in Figure 5-8, allows you to select multiple files to search and allows you to arrange those files in a specific search order. Chapter 5. The Cross Reference Tool 77

92 Figure 5-8: Cross Reference Report Wizard - Files Tab The Select Files list displays all pictures and User Global files in the Dynamics/PIC folder, all schedules in the Dynamics/PDB folder, the User.fxg file, and any.evs files. If any of the selected files are not opened in the WorkSpace, the Cross Reference Tool opens these files during report generation. Once the report finishes, these files are closed. NOTE: Clicking the Select All button will select all files listed in the Files tab except for the Network Status pictures: LocalAsBackup.grf, LocalAsPrimary.grf, NetworkStatusDisplay.grf, and NetworkStatusRedundancyDisplay.grf. The Cross Reference Tool processes files from top to bottom in the list. You can rearrange the order in which the files are processed by selecting a file and clicking the up or down arrow button to move a selected file up or down in the list. 78 Mastering ifix

93 Specifying Report Settings Options By default, the Cross Reference Tool displays the results of a search in the Report Results section of the Cross Reference Tool. The Report Settings tab of the Cross Reference Report Wizard, shown in Figure 5-9, allows you to specify the following output options in addition to the default display: Save Report to File Automatically saves the report when the report generation completes. You can save the report to the default file and location listed, enter one directly into the Save Report to File field, or click the Browse ( ) button to locate a file or path. Available file types include *.CSV, *.HTM, *.XLS, or *.TB2. NOTE: Microsoft Excel enforces a maximum row limit of If you try to save a report that exceeds this row limitation in Excel, you will be prompted to continue or cancel. Please be aware that rows exceeding that limitation may be lost if you select either option. Save Status Trail Saves the status trail information when the report completes. You can save the report to the default file and location listed, enter one directly into the Save Status Trail field, or click the Browse ( ) button to locate a file or path. The available file type is *.TXT. Print Report Automatically prints the report when complete. Click the Advanced button to modify the Print settings. Refer to Selecting Print Options and Printing a Report for more information. Chapter 5. The Cross Reference Tool 79

94 Figure 5-9: Cross Reference Report Wizard - Report Settings Tab Additionally, the Report Settings tab also allows you to set the following report and view options: Include Summary Adds a summary report to the end of the report that details the number of objects and tags searched. Automatically Resize Report Columns Automatically resizes the columns in the Report Results section to accommodate the text. Reviewing the Report Settings The Apply and Go tab, shown in Figure 5-10, displays all of the settings you have selected in the Wizard. 80 Mastering ifix

95 Figure 5-10: Cross Reference Wizard - Apply and Go Tab Review your choices and if they are correct, click the OK button. If you need to modify any of the options, click the Back button to return to the appropriate tab. NOTE: You cannot access the ifix WorkSpace while the Cross Reference Tool generates a report. Once the report completes, you will be able to access the ifix WorkSpace again. Viewing the Report Results Once you create a report using either the Quick Report or Cross Reference Report Wizard, the results display in the Report Results section of the Cross Reference Tool interface. Chapter 5. The Cross Reference Tool 81

96 The information that appears in the Report Results columns depends upon which type of search you selected. Table 5-2 describes the search type and display results. Table 5-2: Search Results Type of Search All Tags One Tag Text Displays Returns a list that displays the name of the object that references the tag (Object column), the property of that tag (Property column), and the tag itself (Current Value column), as shown in Figure 5-1. Returns the name of the object that references the tag (Object column), the property type (Property column), and the tag name (Current Value column). For example, Figure 5-2 shows a One Tag search on the partial tag name ACTIVESTATUS. Returns the object name, property, and property values. If the Cross Reference Tool finds the text string in the object name, all of the object properties are listed in the Property Column. For example, Figure 5-3 shows a Text search on the string FOREGROUNDCOLOR. Additionally, if you selected the Save Report to File or Print Report options in the Cross Reference Report Wizard, those are automatically completed when the results display. Once the Report Results display, you can also save or print the report manually using the appropriate toolbar buttons. Viewing the Status Trail The Status Trail, shown in Figure 5-11, tracks the processing status of the report. This allows you to monitor the report progress and messages, and track errors encountered in the report. 82 Mastering ifix

97 Figure 5-11: Status Trail To automatically save the Status Trail to a.txt file when the report generates, select the Save Status Trail option in the Report Settings tab of the Cross Reference Report Wizard. You can also modify the name and default location of the Status Trail file in the Report Settings tab. Viewing a Search that Resolves Tags Using All Tag Group Files If you select the Resolve Tags Using All Tag Group Files option in either the Quick Report dialog box or the Cross Reference Report Wizard, the Cross Reference Tool attempts to resolve any tag substitutions found in the selected files with all Tag Group Files that you have on your computer during the All Tags, One Tag, or Text search. Figure 5-12 displays the results of an All Tags search with the Resolve Tags using All Tag Group Files option. Chapter 5. The Cross Reference Tool 83

98 Figure 5-12: Search Results of Resolving Tags using All Tag Group Files The Report Results section displays the object that references the tag, the property type of that tag, the tag substitution in the Current Value column, the resolved data source in the Resolved column, and the Tag Group File name that the substitution was found in. The Cross Reference Tool attempts to resolve the substitution in all Tag Group files. Therefore, if the substitution does not exist in a Tag Group file, the Resolved column displays Unresolved, as shown in Figure Viewing a Search that Includes VBA Scripts If you select the Include VBA Scripts in Search option in either the Quick Report or Cross Reference Report Wizard, the Cross Reference Tool searches through all scripts that are contained within the selected file(s) during an All tags, One Tag, or Text search. Figure 5-13 displays the results of an All Tags search with the Include VBA Scripts in Search option. 84 Mastering ifix

99 Figure 5-13: Search Results of Including VBA Scripts in Search If the Cross Reference Tool finds a tag in a script (or the tag or text string that you searched for), the Object column displays the object associated with that script, the Property column displays ScriptSource, and the Current Value column displays the line number and line text of the script that the tag appears in. NOTE: If the scripts contained in the files that you are searching include variables and those variable names are either custom alarm areas or tag names, the Cross Reference Tool displays the variable as a source. Selecting Print Options and Printing a Report The Print dialog box, shown in Figure 5-14, allows you to specify the print settings for a report. When a report completes and displays in the Report Results section of the Cross Reference Tool, you can access this dialog box by clicking the Print button in the toolbar to print the report as it appears. You can also access this dialog box by clicking the Advanced button in the Report Settings tab of the Cross Reference Report Wizard. The Print option in the Report Settings tab allows you to set these options for automatic printing once the report generates. Chapter 5. The Cross Reference Tool 85

100 Figure 5-14: Cross Reference Tool Print Dialog Box To select print options and print a report, follow these steps: [1] Select a Print Range. [2] Click the Page Setup button to configure page settings. How? [3] Select any of the following Print Options: Column Headers Prints column headers at the top of each page. Row Headers Prints row headers on the left side of each page. Grid Lines Prints spreadsheet grid lines. Border Prints the spreadsheet border. Data Cells Only Does not print empty cells beyond the last column and row containing data. Color Prints colors in the spreadsheet as they appear on the screen. Shadows Prints the shadow effect in the column and row headers. [4] Click the Printer Setup button to modify the current printer and printer options. [5] Optionally, click the Print Preview button to view how the Report will appear when printed. Select Close from the Print Preview screen to return to the Print dialog box. 86 Mastering ifix

101 [6] Click OK. If you accessed the Print dialog box from the print toolbar button, clicking OK prints the report. If you accessed the Print dialog box from the Cross Reference Report Wizard, clicking OK returns you to the wizard. Selecting Page Options for Printing The Page Setup dialog box, shown in Figure 5-15, allows you to: Select page orientation Enter or modify page margins Create or modify headers and footers How? Specify the Preview zoom setting Figure 5-15: Page Setup Dialog Box Chapter 5. The Cross Reference Tool 87

102 Enter any desired changes to the Page Setup dialog box and click OK to return to the Print dialog box. Customizing Header or Footer Text The Change Header and Footer Attributes dialog box, shown in Figure 5-16, allows you to create and modify headers and footers for your printed report. To access the Change Header and Footer Attributes dialog box, click the Change Header and Footer Attributes button on the Page Setup dialog box. Figure 5-16: Change Header and Footer Attributes Dialog Box To add a header or footer to your printed report, select either the Header Text or Footer text option from the Apply to section and enter your text in the appropriate column. For example, if you want your text to be centered, enter the text in the Center column. The Cross Reference Tool also provides some pre-configured common header and footer options, including: <Default Header> Inserts the Report Title including the file name, date, and time. 88 Mastering ifix

103 <Time> Inserts a time stamp (date and time). <Page Number> Inserts the current page number. To select from these pre-configured strings, select a cell in the table and right-click it. The display toggles through the options. Creating a Cross Reference Tool Report from the Command-Line The Cross Reference Tool also allows you create reports or access the Cross Reference Tool Help while the Cross Reference Tool is closed. You can run the command-line options outlined in the following table from the Windows Run prompt. Option Syntax Description /r crossreference.exe /r Creates a report with the CrossReference.ini settings. This runs the CrossReference.ini settings which were automatically saved when you last closed the Cross Reference Tool. If no CrossReference.ini is found, the report runs with the defaults. NOTE: You must use the Cross Reference Report Wizard once before using the /r command. The Cross Reference Tool writes to the CrossReference.ini file when you create reports using the Cross Reference Report Wizard. Reports created using the Quick Report do not get written to the CrossReference.ini file. The /r parameter allows you to set up an entire search in the Cross Reference Report Wizard, navigate to the Apply and Go tab, and then click the Cancel button to cancel the search. After exiting the Cross Reference Tool, you could then run the crossreference.exe /r command at any point to generate the report with the settings you had entered. /? crossreference.exe /? Displays Cross Reference Tool Help. Chapter 5. The Cross Reference Tool 89

104 90 Mastering ifix

105 6. Creating Picture-specific Help Files Picture-specific Help files are an efficient means of bringing more information to operators electronically without taking up valuable display space. This section describes how to add your own context-sensitive Help files to ifix pictures. Why Create Picture-specific Help Files? There are several reasons why you might want to create a picture-specific Help file. For example, you may want to provide operators with concise answers to the following questions: What piece of equipment does this object represent? Where is this equipment located? What does this equipment control? Who is the manufacturer of this equipment? What are the Standard Operating Procedures (SOPs) for this picture? In general, if you develop pictures that need to provide operators with equipmentspecific information or sets of instructions, you should consider creating picturespecific Help files. For example, let's say you are developing a picture that contains a pump. You can design the picture so that when operators click the pump and press <Shift><F1>, they receive a pop-up with information about the pump's manufacturer, voltage, amp rating, and horsepower. Similarly, you can use picture-specific Help to develop training screens for new operators. If you were developing a training screen for the pump picture in the previous example, you could display Help pop-up windows containing such basic information as how to know when the pump is on or off, and when it is operating properly. Chapter 6. Creating Picture-specific Help Files 91

106 What's This? Help Context-sensitive Help within a picture is in the form of What's This? Help. What's This? Help is a simple but highly useful form of Help that is designed to allow operators to quickly access Help information and return to their work. To get Help on an object within an ifix picture, an operator essentially points at the object and queries it for a brief explanation. In the following example, an operator has pressed <Shift><F1> while in a picture. The mouse cursor changes to the What's This? Help pointer. While in What's This? Help mode, operators can click any object in the picture (or even the picture itself) for a Help pop-up window on that object. 92 Mastering ifix

107 What's This? Help Design A What s This? Help file is a compiled file that consists of three source files: a project file, a topic file, and a map file. The Help project (HPJ) file contains the Help file s project options, such as the source files to include and compile, the name of the Help file, and so forth. The topic file is a rich-text format (RTF) file that contains topics, which are individual pages of text that display in pop-up windows when you invoke What s This? Help. Using Microsoft Word, you can easily create RTF files by selecting Save As from the File menu and specifying RTF as the file type. The map file is a header file that creates an association between the object that you want to provide Help for and the topics within the topic file. What s This? Help files are not difficult to create, since you only have to specify a couple of Help project options in order to build a useful context-sensitive Help file. However, if you are interested in building more complex, robust Help systems, refer to the HCW.HLP Help file located in the ifix Base path. Chapter 6. Creating Picture-specific Help Files 93

108 Adding Help to an ifix Picture First, specify the Help file name in the HelpFile property of your picture: [1] Right-click a blank space within the picture and select Properties from the pop-up menu. The Properties dialog box appears with the name of the CFixPicture object as the active object. [2] In the HelpFile property cell, specify the name of the Help file that contains your context-sensitive topics. Refer to the Creating Picture-specific Help Files section for steps on creating the Help file. [3] Save the picture. Next, assign a unique number, called a Help context ID, to each object in your picture that you want the operator to be able to get Help on. To do this: [1] Right-click each object in your picture (including the picture itself) for which you want to write a Help topic and select the Property Window command. The Properties window appears with the name of the selected object as the active object. [2] Set the HelpContextID property to the desired number. Remember that all context IDs within the same Help file must be unique. These values are used by the WinHelp application to correctly display the Help topic that is associated with the control. If two controls have the same context ID, the WinHelp compiler will display an error message. Finally, you need to make any object that you want an operator to be able to get Help on selectable. To do this: [1] Right-click each object in your picture (including the picture itself) for which you want to write a Help topic and select the Property Window command. The Properties window appears with the name of the selected object as the active object. [2] Set the IsSelectable property to True. 94 Mastering ifix

109 Creating the Help File This section discusses how to create the source files that comprise a picture-specific Help file, and also provides all of the steps required to successfully implement What's This? Help into ifix pictures. Requirements The requirements for creating a picture-specific Help file are: Microsoft Word or any other word processor that can save Rich Text Format (RTF) and text files. Microsoft Help Workshop. The Help Workshop is included with ifix and is installed in the ifix Base path (usually C:\Dynamics\HCW.EXE). Creating a Topic File When creating What s This? Help topic files, keep in mind that each topic must: Appear on a separate page in the RTF file. Therefore, you must make sure that there s a page break between each Help topic. (In Microsoft Word, select <Ctrl><Enter> to create a manual page break between Help topics.) Contain a unique topic ID. Topic IDs are specially-formatted footnotes that uniquely identify each topic in the RTF file. The WinHelp application (WINHLP32.EXE) needs this information to display Help topics correctly. To create a Help topic file in Microsoft Word: [1] Create a new document and select Footnote from the Insert menu. [2] Select the Custom Mark option button, enter a pound sign (#) in the adjacent field, and click OK. The document window splits so you can see the footnote area. [3] In the footnote pane, enter a unique context string to the right of the pound sign. Do not include spaces in the context string. One common method is to use underscores for more descriptive context strings, such as: Chapter 6. Creating Picture-specific Help Files 95

110 water_pump_onoff_btn [4] Click the Close button on the footnote pane to close the footnote area and return to a full-screen document window. (To view the footnote text again, double-click the footnote at the top of the topic.) [5] To the right of the footnote symbol, enter the information that you want to appear in the Help pop-up window. [6] Save the document as an RTF file. Creating a Map File In order for the WinHelp application to display the correct Help pop-up window when you select <Shift><F1> on a particular object, you must associate each unique Help topic ID (defined in the RTF file) with it s corresponding Help context ID (defined in the property page of an object). This association, or mapping, is done in the MAP section of a Help project (HPJ) file. The easiest way to map these values is to create a header file in a text editor and include that header in the MAP section. [1] In a text file, associate each topic ID with an object s context ID using the following format: <topic ID> = <context ID> For example, if you defined the HelpContextID property of the pump in the previous example as 1000, it would appear in the header file as: water_pump_onoff_btn = 1000 [2] Continue to add these define statements, one per line, until all of your Context IDs have been added to the header file. [3] Save the file as a text-only file and provide it with an.h file name extension. 96 Mastering ifix

111 Creating and Compiling a Project File The final step is to create a Help project file which allows you to compile the map file and topic files into one binary Help file. [1] In the Microsoft Help Workshop, select New from the File menu. [2] Select Help Project and click OK. [3] Enter the Help project file name and path in the File Name field and click Save. [4] Enter the name of your Help file in the Help File field. Remember to use the same Help file name that you specified in the picture's Properties dialog box. [5] Click the Options button and select the General tab. Enter the name you want to appear in the title bar of your Help system in the Help Title field. [6] Select the Files tab and click Change. Click Add and browse for the RTF file that includes your Help topics. [7] Click OK to return to the main HPJ dialog box. [8] Click Map. Click Include and browse for the header file that includes all of your map statements. Click OK to exit the Include File dialog box and click OK again to save your changes to the Map dialog box. [9] When you are ready to compile, click the Save and Compile button. Testing Your Help File [1] Copy your compiled Help file to the ifix Base path. [2] In the Intellution WorkSpace run-time environment, open your Help-enabled picture. [3] Press <Shift><F1>. The cursor changes to a question mark pointer, indicating that it is in What's This? Help mode. [4] Click an object to which you assigned a Help context ID. The Help topic that you assigned to the object displays in a pop-up window. To dismiss the Help pop-up window, click anywhere on the screen. Chapter 6. Creating Picture-specific Help Files 97

112 Example: Creating a Picture-Specific Help File This section serves as a mini-tutorial that walks you through the complete process of creating a sample Help file and assigning it to a picture. For clarity, this example assumes that ifix is installed to the C:\DYNAMICS path and that you are developing your Help file in a working directory entitled C:\DYNAMICS\HELP TEST. In Microsoft Word [1] Open a new document and select Footnote from the Insert menu. [2] Click the Custom Mark option button and enter a pound sign (#) in the adjacent field. Click OK. [3] In the footnote pane at the bottom half of the window, enter the following text directly to the right of the footnote symbol: my_square [4] In the document pane at the top half of the window, type the following text directly to the right of the footnote symbol: This is the Help topic for my square. [5] Save the document as an RTF file to C:\DYNAMICS\HELP TEST\SQUARE.RTF. In the Intellution WorkSpace [1] Open a new ifix picture. [2] Right-click the picture and select the Property Window command. [3] Enter the following text in the HelpFile property field: square.hlp [4] Click the Rectangle button from the Toolbox and draw a rectangle. [5] Right-click the rectangle and select the Property Window command. 98 Mastering ifix

113 [6] Enter the following number in the ContextID property field: 1000 [7] Set the IsSelectable property field to True. In Microsoft Help Workshop [1] Select New from the File menu, select Help Project, and click OK. [2] Enter C:\DYNAMICS\HELP TEST\SQUARE.HPJ in the File Name field of the Project File Name dialog box and click Save. [3] Click the Files button. The Topic Files dialog box appears. [4] Click Add, select SQUARE.RTF from the list, and click Open. The RTF topic file is added to the Topic Files list. Click OK. [5] Click the Map button and click Add. [6] Enter the following text in the Topic ID field: my_square [7] Enter the following number in the Mapped Numeric Value field: 1000 [8] Click OK, and then click the Save and Compile button. Testing the Sample Help File [1] Copy the SQUARE.HLP Help file to the C:\DYNAMICS directory. [2] In the Intellution WorkSpace run-time environment, open the HELPTEST picture. [3] Press <Shift><F1>. The cursor changes to a question mark pointer, indicating that it is in What's This? Help mode. [4] Click the rectangle. A Help pop-up window with the following text appears: This is the topic for my square. Chapter 6. Creating Picture-specific Help Files 99

114 100 Mastering ifix

115 7. Customizing the System Tree CAUTION: The instructions in this section are strictly intended for users who are creating their own custom installation CD. We strongly discourage customizing your system tree under any other circumstances. This information is meant for advanced users only. The Intellution WorkSpace system tree is the main tool for locating files and launching applications. It also provides access to your files and applications during the development of your pictures and schedules. Depending on your needs, you may want to remove certain applications or folders or add new ones. For example, you may want to add a custom application to the system tree. On the other hand, if you did not purchase FIX SCADA support, you may want to delete the Database Manager application and I/O Drivers folder. You can customize the system tree by modifying the text file SystemTree.CSV. This file defines the folders, applications, and files that appear when you start the Intellution WorkSpace. The file resides in the Local path. CAUTION: Any changes made to the SystemTree.CSV file are done so at your own risk. All changes made to the system tree are permanent. We recommend making a backup copy of the SystemTree.CSV file that, if necessary, can be used to reset the system tree to its default settings. NOTE: We recommend using Microsoft Excel when editing the SystemTree.CSV file. When saving the file in Excel, be sure to save it with a.csv extension. If prompted to save the file in Microsoft Excel Workbook format, select No. If the SystemTree.CSV file is saved incorrectly, the system may not be usable. When editing the file, you must use a comma (,) as the list separator. Other characters, such as the international list separator (;) cannot be used as the list separator in the SystemTree.CSV file. To view or modify the list separator setting on your system, double-click the Regional Settings icon in the Control Panel and click the Number tab. The SystemTree.CSV file is divided into two sections. The top section defines the folders in the system tree and the bottom section defines the files. Within each of these sections are attributes that determine how a folder or file appears in the system tree. For example, the Key field contains the name of the file or folder as it appears in the system tree, and the Key Type field defines whether it is a folder or file. The Chapter 7. Customizing the System Tree 101

116 remaining attributes have Entry and Value fields. The Entry field holds the name of the attribute and the Value field defines the corresponding attribute value. The attributes for folders and files are defined in Table 7-1 and Table 7-2. NOTE: Although not all of the attributes in this file need to be defined, it is important to note that if the Entry field is completed for an attribute, the corresponding Value field must also be completed. When you are ready to customize the SystemTree.CSV file, refer to the following figure for an overview of the required steps. Open the SystemTree.CSV file. This file resides in the Local path. Delete any files or folders you do not want to include. Add any files and folders you want to include. Save the file in the Local path with a.csv extension. Close the Intellution WorkSpace. Select Run from the Windows NT Start menu and enter the command: WorkSpace /unregserver Restart the Intellution WorkSpace. Figure 7-1: System Tree Customization Overview 102 Mastering ifix

117 Adding Folders to the System Tree You can add folders to the system tree by editing the top section of the SystemTree.CSV file. Use Table 7-1 as a guide to editing the file. To add a folder to the system tree [1] Open the SystemTree.CSV file located in the Local path. [2] Insert a row within the Define Intellution s Folder section. [3] Enter the information for the folder in the attribute fields. For example, to add a folder named Events that contains event files enter the following (leave unused fields blank): For the attribute Description Folders Extension Entry Extension of the files for this folder AutoFind Entry Used to find, create, and populate this folder on startup Fix Path Entry Default path for files in this folder Enter Events Folder Extension Evt AutoFind TRUE Fix Path ALM_PATH [4] Save the file in the Local path with a.csv extension. [5] Close the Intellution WorkSpace. Chapter 7. Customizing the System Tree 103

118 [6] Select Run from the Windows NT or Windows 2000 menu and enter WorkSpace /unregserver in the Open field. [7] Click OK. [8] Restart the Intellution WorkSpace. Folder definitions include the attributes in the following table. Table 7-1: Folder Attributes The attribute Description Folders AppKey Vendor of Folder ProgID of files in this folder Extension of the files for this folder Defines The names of the folders in the system tree. By adding a new name, you add a new folder to the system tree. If you want the folder to appear inside another folder enter the complete path. For example, to add a folder called Drawings to the Pictures folder you would enter: Pictures\Drawings Each entry as a folder and always has the value FOLDER. An entry that is reserved for future use and should be left blank. A company name. When you add a folder, enter the name of your company. Completing this attribute is optional. The program identification from the registry of the ActiveX documents residing in the folder. If the folder does not contain ActiveX documents, leave the ProgID blank. The file extension you want to associate with the folder. Completing this attribute is optional. If Used to find create and populate this folder on startup is set to TRUE, this attribute must be completed. 104 Mastering ifix

119 Table 7-1: Folder Attributes (continued) The attribute Used to find create and populate this folder on startup Fix Path Entry Disable New Entry OpenExclusive Defines Whether the Intellution WorkSpace automatically displays the files with the specified extension. Setting Used to find create and populate this folder on startup to TRUE displays the files; entering FALSE or leaving the extension undefined creates an empty folder. Typically, this attribute is set to TRUE. If set to TRUE, the Extension attribute must be completed. The path to each folder. When you add a folder, enter the complete path to it. This must be a FIX path. Whether the New command on the folder s right mouse menu is grayed out or enabled. Entering TRUE grays out the command; setting the attribute to FALSE or leaving it undefined enables the command. Typically, this attribute is set to FALSE. How the documents in the folder are opened. Entering TRUE opens the files exclusively for use in the Intellution WorkSpace; no other applications can read or write to these files. Setting the attribute to FALSE opens documents in a non-exclusive manner so that other applications can read or write the file. Typically, this attribute is set to FALSE. Adding Files to the System Tree You can add files to the system tree by editing the bottom section of the SystemTree.CSV file. Use the Table 7-2 as a guide to editing the file. To add a file to the system tree: [1] Open the SystemTree.CSV file located in the Local path. [2] Add a folder named Event as described in the Adding Folders to the System Tree section. [3] Insert a row within the Define Intellution s Files section of the file. Chapter 7. Customizing the System Tree 105

120 [4] Enter the information for the file in the attribute fields. For example, to add a text file called Text File within the Events folder enter the following (leave unused fields blank): For the attribute Description Files Fix Path Entry Path of this file AutoLoad Entry Used to determine if this file should be opened on startup by the WorkSpace Enter Events\Text File File Fix Path ALM_PATH\Test.txt AutoLoad FALSE [5] Save the file in the Local path with a.csv extension. [6] Using Notepad, create a text file named Test.txt and save it in your Dynamics\Alm folder. [7] Close the Intellution WorkSpace. [8] Select Run from the Windows NT or Windows 2000 menu and enter WorkSpace /unregserver in the Open field. [9] Click OK. [10] Restart the Intellution WorkSpace. 106 Mastering ifix

121 Folder definitions include the attributes in the following table. Table 7-2: File Attributes The attribute Description Files AppKey Vendor of File Path of this File Used to determine if this file should be opened on startup by the WorkSpace Hidden In Tree Entry Defines The names of the files that appear directly off the system tree root. By adding a new name, you add a new file to the system tree. If you want the file to appear inside a folder, enter the complete path. For example, to add a globals file called OEMGlobals to the Globals folder you would enter: Globals\OEMGlobals Each entry as a file and always has the value FILE. An entry that is reserved for future use and can be left blank. A company name. When you add a file, enter the name of your company. Completing this attribute is optional. The complete path to each file. This must be a FIX path and the file name. If the file resides in an ifix path, you can specify the path with a predefined alias, such as PDB_PATH or BASE_PATH. For example, if you are adding a globals file, enter PIC_PATH since all global files reside in the ifix Picture path. Whether the Intellution WorkSpace automatically opens the file on start-up. This attribute is set to TRUE for globals files only. Typically, this attribute is set to FALSE. Whether the file is visible or hidden in the system tree. In general, you only want to set this attribute to TRUE for any non-modifiable globals file you add to the system tree. Typically, this attribute is set to FALSE. Chapter 7. Customizing the System Tree 107

122 Table 7-2: File Attributes (continued) The attribute Not In Collection Entry Disable Close Entry Disable Show Entry Disable Save Entry Type of file we are creating ProgID of this file Determines if this file can be renamed and deleted Defines Whether the file should be included in a collection. A collection is one or more open ActiveX documents. Typically, you want to include all files except nonmodifiable (system) globals files in collections. Consequently, you enter TRUE for system globals files and FALSE for any other file. Typically, this attribute is set to FALSE. Whether the Close command on the file s right mouse menu is grayed out or enabled. Entering TRUE grays out the command; entering FALSE or leaving it undefined enables the command. Typically, this attribute is set to FALSE. Whether the Show command on the file s right mouse menu is grayed out or enabled. Entering TRUE grays out the command; entering FALSE or leaving it undefined enables the command. Typically, this attribute is set to FALSE. Whether the Save command on the file s right mouse menu is grayed out or enabled. Entering TRUE grays out the command; entering FALSE or leaving it undefined enables the command. Typically, this attribute is set to FALSE. Whether the file is a globals file. If it is not a globals file, enter DEFAULT. If it is, enter USER for userdefined globals files or SYSTEM for non-modifiable globals files. Typically, you supply system globals to prevent these value from being changed. The program identification for your system and user globals files. This attribute is left blank or set to FIXGLOBALSSERVER.FIXGLOBALSSERVER.1 Whether the Rename and Delete commands on the file s right mouse menu is grayed out or enabled. Entering TRUE grays out the command; entering FALSE or leaving it undefined enables the command. This attribute is set according to user preference. 108 Mastering ifix

123 Deleting Folders and Files from the System Tree You can delete folders and files from the system tree by editing the SystemTree.CSV file. To delete a folder or file from the system tree [1] Open the SystemTree.CSV file located in the Local path. [2] Delete the row with the file or folder information you want to remove from the system tree. [3] Save the file in the Local path with a.csv extension. [4] Close the Intellution WorkSpace. [5] Select Run from the Windows NT or Windows 2000 menu and enter WorkSpace/unregserver in the Open field. [6] Click OK. [7] Restart the Intellution WorkSpace. Chapter 7. Customizing the System Tree 109

124 110 Mastering ifix

125 Index A active network path 36 active server 21 alarm handling LAN redundancy 37 SCADA server failover 25 Alarm Startup Queue Service enabling 42 All Tags search in the Cross Reference Tool 66 Apply and Go tab 80 automatic failover temporarily disabling 43 Automatically Resize Report Columns 80 B background schedules 4 background task startup list 8 backup node in a SCADA server pair 24 backup SCADA servers See SCADA server failover buttons toolbar buttons for the Cross Reference Tool 73 C command-line options Cross Reference Tool 89 compiling a project file 97 configurations LAN redundancy 38 SCADA server failover 27 SCADA server failover and LAN redundancy 22 configuring LAN redundancy 39 network session timers 41 SCADA server failover 34 SCADA server pair 35 continuous entry 11 creating a map file 96 a project file 97 picture-specific help files 91 reports 76 the help file 95 topic file 95 Cross Reference Report Wizard 76 Cross Reference Tool 65 All Tags search 66 Apply and Go tab 80 automatically saving the report file 79 button 70 creating Quick Reports 74 customizing header and footers 88 including the summary report 74 introduction 65 introduction to 65 Object Tree 71 One Tag search 66 opening 70 Page Setup dialog box 87 printing a report 85 printing report automatically 79 Quick Report and Report Wizard 68 refreshing 73 Report Results 71 Report Settings tab 79 Report Wizard 70, 76 resizing columns 74 resolving tags 74 running from command-line 89 search settings 76 search types 66, 67 searching for text 67 searching through scripts 74 selecting multiple files 77 selecting print options 85 Status Trail 71 toolbars 73 types of searches 65 viewing files open in the WorkSpace 71 viewing results 81 viewing searches through scripts 84 viewing status trail 82 Index 111

126 Crystal Reports sample report 61 using with ifix 59 custom scripts writing for Scheduler 15 customizing the system tree 101 D daily entry 11 debugging VBA scripts in a schedule 8 diagnostic displays 44 diagnostics entry 15 disabling automatic failover 43 LAN redundancy 40 network paths 41 SCADA server failover 35 displaying the search results of a report 71 failover messages LAN 37 SCADA server failover 25 file attributes SystemTree.CSV file 107 files adding to the system tree 105 deleting from the system tree 109 selecting multiple 77 Files tab 77 finding tags in files 69 finding tags in the Cross Reference Tool 74 FixBackgroundServer task as a Windows service 8 folder attributes SystemTree.CSV file 104 folders adding to the system tree 103 deleting from the system tree 109 foreground schedules 4 E enabling Alarm Startup Queue Service 42 disabled network paths 41 LAN redundancy 39 SCADA server failover 35 entries continuous 11 creating 13 daily 11 diagnostics 15 editing 13 event-based 10 monthly 11 one-shot 11 time-based 11 event types 10 event-based entries 10 Experts Script Authoring 12, 15 F failover triggering an event 44 understanding 21 H Headers and Footers customizing 88 help adding to an ifix picture 94 creating the file 95 designing What s This? 93 understanding What s This? 92 HOSTS file updating for LAN redundancy 39 updating for SCADA server failover 34 Include Summary 80 Include VBA Scripts in Search 74, 84 LAN failover messages 37 LAN redundancy alarm handling 37 configurations 38 configurations with SCADA server failover 22 configuring 39 disabling 40 enabling 39 I L 112 Mastering ifix

127 LAN redundancy (continued) overview checklist 23 understanding 21, 36 updating the HOSTS file 39 local node alias enabling 55 examples 55 overview 55 THISNODE 55 using 55 logical node name creating displays 46 described 28 M manual failover assigning privileges 36 initiating to non-active SCADA 43 map file creating 96 monthly entry 11 multiple files searching through 77 N network paths disabling 41 enabling disabled paths 41 network session timers configuring 41 Network Status Server fields 46 working with 42 non-active network path 36 non-active server 21 NSS fields 46 working with 42 O Object Tree Cross Reference Tool 71 refreshing 73 One Tag searching for in Cross Reference Tool 66 one-shot entry 11 opening Cross Reference Tool 70 P physical node names creating displays 46 picture-specific help files creating 91 primary and backup groupings 28 primary node in a SCADA server pair 24 print Crystal Report 60 Print Crystal Report Expert 60 printing reports 85, 86 reports automatically 79 project file creating and compiling 97 Q Quick Report 74 All Tags 66 differences between Report Wizard and 68 feature list 69 One Tag 66 Quick Reports creating 74, 75 refresh Object Tree 73 Report displaying search results 71 report including a summary 74 reviewing settings 80 saving to a file 79 specifying output options 79 viewing report results 81 viewing search results that resolve tags 83 Report Experts overview 59 Print Crystal Report 60 Print Crystal Report Expert 60 using 60 Report Results 81 Cross Reference Tool 71 Report Settings Tab Save Status Trail 79 Report Settings tab 79 automatically print report 79 R Index 113

128 Report Wizard All Tags 66 automatically saving status trail 79 creating reports 76 differences between Quick Report and 68 feature list 70 One Tag 66 output options 79 resolving tags 77 search settings 76 searching through scripts 77 selecting multiple files 77 reporting overview 59 using ifix Report Experts 59 reports automatically printing 79 creating 75, 76 displaying status trail 71 printing 85, 88 resizing columns 74 selecting page options 87 viewing search through script results 84 resizing columns 74 Resolve Tags using All Tag Group Files 74 Resolve Tags using All Tag Group Files viewing results 83 resolving schedules 6 resolving tags using the Cross Reference Tool 74 using the Report Wizard 77 results of tag search 82 of text search 82 Save Status Trail 79 SCADA server failover alarm handling 25 backup node 24 configurations 27 configurations with LAN redundancy 22 configuring 34 disabling 35 enabling 35 failover messages 25 primary node 24 synchronizing clocks 35 understanding 24 updating Hosts file 34 S SCADA server pair configuring 35 understanding 21 Scheduler introduction 1 overview 1 running as a background task 5 running as a foreground task 5 script execution 5 using the VBE 4 using with ifix 4 schedules adding to background task startup list 8 debugging VBA scripts 8 designing 9 resolving 6 running in the background 7 running in the foreground 7 securing 6 sorting 14 Script Authoring Experts 12, 15 scripts searching through 74, 77 viewing reports 84 Search Settings tab 76 searching for tags 65 for text 66 for text strings 67 through scripts 77 types of searches for tags 65 searching for one tag 66 searching for tags resolving tags 77 securing schedules 6 selecting print options 86 sorting a schedule 14 Status Trail 82 automatically saving 79 Cross Reference Tool 71 viewing 82 summary report 74 synchronizing SCADA server clocks 35 system performance optimizing during failover 40 system tree adding files 105 adding folders 103 customizing 101 deleting folders and files 109 SystemTree.CSV file Mastering ifix

129 SystemTree.CSV file 101 true links 45 T tag name searching for a partial name 67 tags searching for all tags 66 searching for one tag 66 Text finding in files 67 Text search 67 THISNODE 55 time-based entries 11 toolbars Cross Reference Tool 73 topic file creating 95 VBA scripts to access the Intellution WorkSpace 12 writing custom scripts for Scheduler 15 VBE using with Scheduler 4 V W What s This? help designing 93 overview 92 wizards feature list for Cross Reference Tool 68 Report Wizard 70 Index 115

130 116 Mastering ifix