Chapter 34 Migrating from FIX v7 - read.pudn.comread.pudn.com/downloads203/doc/954495/Student Guide/34... · • Use Figure 34-2 to determine from which FIX SCADA nodes data and alarms

154 Student Guide

34. Migrating from FIX v7.x ___________________________________

Chapter 34

Migrating from FIX v7.x

Copyright © 2001, Intellution, Inc. 34-1

Intellution Dynamics iFIX

34. Migrating from FIX v7.x ___________________________________ Section Objectives In this section, we will go over issues and concerns that arise when taking a FIX32 application and migrating it to an iFIX application. This includes the following:

• What needs to be done before the migration process

• Migrating FIX32 files to iFIX

• Converting Pictures


154 Student Guide

34.1. Before Migrating to iFIX ________________________________

A. Notes

• iFIX was not designed as an upgrade to FIX v7.x

• iFIX is a separate and independent HMI/SCADA application

• However, many components from a FIX v7.x application can be used in an iFIX application

B. Before Installing iFIX

• Before installing iFIX, the following items need to be considered:

- Recommended system configuration

- Compatibility of FIX nodes on the network

- New command scripts

- Functionality conversion from FIX version 7.x to iFIX



34.1.1. Recommended System Configuration ____________________

A. Recommended System Configuration

• Figure 34-1 lists the recommended CPU clock speed, RAM requirements, video specifications, and operating system

• iFIX runs on the Windows NT or Windows 2000 operating systems

- Windows 95 and Windows 98 are not supported

• The physical memory and the CPU clock speed recommendations in Figure 34-1 are only minimum requirements

- System performance will improve if minimum requirements are exceeded

• iFIX supports Symmetrical Multiprocessor (SMP) computers

Item Requirement

Operating System

Microsoft Windows NT 4.0 SP4 (with IE 3.02 or later) or Microsoft Windows 2000

Minimum CPU Clock Speed

266 MHz Intel Pentium II. Intel Celeron is supported but not recommended

Minimum Physical Memory

96 Mbytes (iClients), 128 Mbytes or greater (SCADA Servers)

Video Specifications

64K+ Colors, 600 x 800 (1024 x 768 recommended for View Clients)

Figure 34-1: Recommended System Configuration


154 Student Guide

34.1.2. Compatibility of FIX Nodes on the Network ________________

A. Compatibility of FIX Nodes on the Network

• Use Figure 34-2 to determine from which FIX SCADA nodes data and alarms can be retrieved when running an iFIX iClient

If running a View Client…

Data and alarms can be retrieved from these SCADA Servers

Data and alarms can NOT be retrieved from these SCADA Servers

FIX for Windows NT/95 v7.x

FIX for Windows v5.5 /30


iFIX

FIX for Windows v5.0 or v5.5

FIX for Windows NT v4.1


FIX for Windows v5.5 /30

FIX for Windows v5.65


iFIX



iFIX FIX for Windows v5.5 /30




iFIX



Figure 34-2: Compatibility of FIX Nodes on the Network



34.1.3. New Command Scripts _________________________________

A. New Command Scripts

• iFIX uses new global subroutines in place of the FIX32 command scripts

• Figure 34-3 lists the new iFIX global subroutines that correspond to the FIX v7.x command scripts

FIX32 Command Script

New iFIX Global Subroutine

ALARMACKALL AcknowledgeAllAlarms([Picture As String])

ALARMACK AcknowledgeAnAlarm([DataPoint As String])

CLOSEDIG CloseDigitalPoint([DigitalPoint As String])

CLOSEPIC ClosePicture([Picture As String])

DIABLEALARM DisableAlarm([DataPoint As String])

ENABLEALARM EnableAlarm([DataPoint As String])

LOGIN and LOGOUT LogIn()

FINDLINK LocateObject(ObjectName As String, [bRelative As Boolean])

OFFSCAN OffScan([DataPoint As String])

ONSCAN OnScan([DataPoint As String])

OPENDIG OpenDigitalPoint([DigitalPoint As String])

OPENPIC OpenPicture([Picture As String], [PictureAlias As String], [TopPosition], [LeftPosition])

OPENPIC OpenTGDPicture([sPicture As String], [sPictureAlias As String], [fTop], [fLeft], [sTagGroup As String])

Figure 34-3: New Command Scripts


154 Student Guide

34.1.3. New Command Scripts ______________________________

FIX32 Command Script

New iFIX Global Subroutine

SETNICKNAME PictureAlias(PictureAlias As String)

(No FIX32 command)

PrintReport(ByVal Report As String, [Prompt As Boolean], [ByVal Copies As Long], [ByVal Coll As Boolean], [ByVal StartNo As Long], [ByVal EndNo As Long])

RAMP RampValue(RampValue As Double, ByPercent As Boolean, [DataPoint As String])

GETVAL ReadValue([DataPoint As String])

REPLACEPIC ReplacePicture(NewPicture As String, [OldPicture As String], [TagGroupFileName As String])

REPLACEPIC ReplaceTGDPicture(sNewPicture As String, sTagGroup As String, [sOldPicture As String = ""])

SETAUTO SetAuto([DataPoint As String])

SETMANL SetManual([DataPoint As String])

TOGGLEDIG ToggleDigitalPoint([DigitalPoint As String])

TOGGLEMANL ToggleManual([DataPoint As String])

TOGGLESCAN ToggleScan([DataPoint As String])

SETVAL WriteValue(Value As String, [DataPoint As String])

MESSAGE MsgBox

FILEOPEN

FILECLOSE

FILEREAD

FILEWRITE

Open

Close

Input #

Write #

NOTE: These four entries are standard Visual Basic statements, not iFIX global subroutines. See the Visual Basic Reference help for additional information.

Figure 34-3: New Command Scripts (continued)



34.1.4. Converting FIX Version 7.x Functionality __________________

A. Notes

• This section describes the functionality in FIX version 7.x that converts to iFIX

• Although a small percentage of v7.x functionality does not convert to iFIX, iFIX offers more system capability and extensibility

B. System Configuration Utility

• The System Configuration Utility converts to iFIX

C. Database

• Process Database

- FIX v7.x PDB files automatically convert to the iFIX format

- simply open the FIX v7.x *.PDB file using the iFIX Database Manager

- Note:

◊ once the *.PDB file is opened using the iFIX Database Manager, the file can not be opened on a v7.x node

• Easy Database Access (EDA) and Historical Data Access (HDA) Programs

- existing applications that use EDA and HDA will work with iFIX

- however, EDA programs built under the v7.x toolkit are not able to send or receive alarms

◊ recompile and link the program using the iFIX toolkit for these functions

• Database Dynamos

- recompile with iFIX Database Dynamo Toolkit

- the Database Dynamo conversion process is detailed in the new iFIX Database Dynamo toolkit


154 Student Guide

34.1.4. Converting FIX Version 7.x Functionality________________

D. Alarms

• Alarm Areas

- the FIX v7.x A-P alarm areas are compatible in iFIX

- no special conversion is needed

• Alarm Horn

- FIX v7.x has an alarm horn which causes the computer’s speaker to beep whenever there are unacknowledged alarms present

- this functionality is available in iFIX through the AlarmHornEnabled property of the Alarm Summary Object

• Alarm Counters

- this functionality is available in iFIX

- no special conversion is needed

E. I/O Drivers

• FIX 7.x Drivers work with iFIX, however they require export

F. OPC Servers

• All Intellution OPC servers developed with the v7.1 toolkit operate under iFIX

• Note:

- the OPCNIO.DLL option that makes 7.x drivers into OPC Servers is no longer provided by Intellution, nor will it work with iFIX

- all new Intellution OPC Servers are built using the 7.1 OSDK toolkit

- all 7.x I/O drivers work with iFIX




G. DDE (Dynamic Data Exchange)

• Process Database as a Server

- iFIX can act as a server to other DDE-Aware applications

- use the same DDE syntax that was used to access the FIX v7.x process database

• Process Database as a Client

- data can be brought into the iFIX PDB through the DDE Driver in the same way it was brought into the FIX v7.x PDB

• Intellution Workspace (Pictures) as a Client

- DDE is not supported within the Intellution WorkSpace

- use OPC or ODBC (with VisiconX) to bring data into an iFIX picture

• Report Generator

- the FIX v7.x Report Generator is not supported by iFIX because it uses DDE

- iFIX works in conjunction with Crystal Reports and many other third party reporting tools

- Examples

◊ access Crystal Reports via a wizard in a Schedule

◊ use VBA Automation to create reports in Word or Excel

◊ use the iFIX ODBC drivers to generate reports in Access

H. Key Macro Files

• iFIX uses different and more enhanced Key Marco than FIX v7.x

• FIX v7.x Key Macro Files do not convert to iFIX

I. Recipe Files

• FIX v7.x recipe files will work with iFIX, but they must be exported

J. Security Files

• FIX 7.x security files will work with iFIX, but they must be exported


154 Student Guide


K. Historical

• Historical Assign (HTA) Files

- Historical Assign (HTA) has not changed

- simply open the *.HTA files using the iFIX Historical Assign program

• Chart Groups, Pen Groups, Time Groups

- the Historical Display program is not used with iFIX

- existing Chart Groups, Pen Groups and Time Groups are not used in iFIX

- in iFIX, historical data is viewed in the chart object of a picture

- simply create and configure new chart objects within a picture in the Intellution Workspace

• Existing Historical Data

- view Historical Data from FIX v7.x nodes using the Chart Object in an iFIX picture

• Lab Data

- Lab data cannot be viewed directly in a Chart Object

- convert the lab data into a relational database and use scripting to view the data

• Existing SQL Queries

- SQL data cannot be viewed directly in a Chart Object

- use scripting to view the data

L. MHP (Message Handler Package)

• MHP is not used in iFIX, however this functionality can be achieved in several ways

• Example:

- a simple text object can be added to a picture and the caption of that text object can be animated

- use the Table conversion option and simply map an integer value into a text string

- when the value of the datasource changes, the text on the screen will also change




M. ODBC (Open Database Conectivity)

• From the Process Database (SQT & SQD Blocks)

- FIX v7.x Process Database files will automatically convert to the iFIX format

- simply open the FIX v7.x *.PDB file using the iFIX Database Manager

◊ once the *.PDB file is opened using the iFIX Database Manager, the file can not be opened on a v7.x node

• The ODBC Data Source

- the ODBC Data Source is configured in the Windows NT Control Panel and is not affected by Intellution software

• From Pictures (with the Command Language)

- the easiest way to view data from an OBDC data source in a picture is to use VisiconX

- this very powerful tool requires no scripting and is easy to use

N. Pictures

• Subpictures

- Subpictures functionality can be achieved in iFIX via scripting

• Shapes and Bitmaps

- Shapes and bitmaps in FIX v7.x pictures are converted to similar objects in iFIX

- using the new picture conversion utility, shapes and dynamic properties are converted to their closest iFIX equivalent

• Graphic Dynamos

- Graphic Dynamos are converted to objects in iFIX

- scripts do not convert

- details for this process are included in the Readme file that is provided with the Picture Conversion Utility

◊ more on this later in the course


154 Student Guide


N. Pictures (continued)

• BDF Files (Block Data Files)

- BDF files are not available in iFIX

- however, the information contained in BDF files can be created in a picture or by creating a user form in VBA

• Command Language Scripts

- iFIX does not support the FIX Command Language

- Command Language scripts are translated to comments in VBA script of the converted picture

- all Command Language functionality exists in VBA

- there is a Command Language Conversion tool available on the Intellution Knowledge Base CD (KBCD)

• Layout Files

- while iFIX does not contain Layout files, a default layout is configurable via User Preferences in the WorkSpace

• Tag Groups

- FIX v7.x Tag Group files can be converted using the iFIX Tag Group Editor

• Picture Templates

- while iFIX does not support the use of picture templates, this functionality can be achieved by simply creating read-only pictures

- these pictures can be opened and edited, but must be saved under a new name thereby preserving the original read-only file

• Zoom To Functionality

- Zoom To functionality can be achieved in iFIX via scripting



34.2. Migrating to iFIX ______________________________________

A. Migrating to iFIX

• This section describes iFIX migration tasks, including:

- backing up files

- networking machines

- getting updates

- tasks to complete on the computers involved in the upgrade

B. Backing up Files

• Intellution recommends a complete backup of the current FIX installation before proceeding with the migration to iFIX

• If a complete backup is not possible, ensure that at a minimum the following files are backed up:

- FIX/Local Files

◊ *.ini, *.scu,

- Picture (PIC) Path Files

◊ *.odf, *.lyt, *.sbl, *.tge, *.kmx

- Database (PDB) Path Files

◊ all files

- Historical Path Files

◊ all files

- Historical Data Path Files

◊ all files

- Security Files

◊ export current configuration from the SCU

◊ consult the FIX documentation for more information on this feature

- The STARTUP.XLA file located in the Microsoft Excel path

- Master and Control Recipes

◊ *.rcc, *.rcm


154 Student Guide

34.2. Migrating to iFIX ________________________________________

C. Networking Computers

• If iFIX is to be installed on a computer other than the one currently running the application, connect the two machines using a network

• If there is no network connection, files that are manually exported must be copied to the target machine using removable media

D. Obtaining Updates

• Intellution recommends obtaining the following updates before migrating to iFIX:

- Download the latest SIMs from the Intellution web site

- Download the latest release of the Picture Conversion Utility

- Download the latest Drivers

- Check with Intellution Technical Support for any new updates

- Download iFIX add-ons such as the Dynamo Wizard

◊ copy and expand these files on the iFIX computer

E. Completing Tasks on the Current FIX Installation

• Complete the following tasks on the computer containing your current FIX installation

1. From the Database Builder, verify the FIX Process Database by selecting Verify from the Database menu

2. From Historical Assign, export the FIX HTA file by selecting Export from the File menu

3. Import the HTA configuration back into Historical Assign file by selecting Import from the File menu

4. From Mission Control, click the I/O Control tab and note the Time Outs, the Retries, and the DRVST* error codes

5. From Mission Control, click the HTC tab and check for overruns

6. From Mission Control, click the SQL and check for errors

• Note, document, and correct errors when applicable




F. Manually Exporting Files

• Complete this procedure on the computer containing the current FIX installation to manually export FIX files that were not automatically exported

• Before beginning, create a separate directory for the exported files

1. If the current installation of FIX is not running, start it by selecting the Start Up icon from the FIX start menu

2. If security is enabled, log in using a user account with administrator rights

3. Start the System Configuration Utility (SCU)

◊ If Security is not enabled, skip to step 7

4. Enter the Security Configuration by selecting Security from the Configure menu

5. From the File menu, select Export

◊ Note the location of the exported files, and select Save

◊ Passwords are not exported and will need to be recreated later

6. From the File menu in the Security Configuration program, select Exit to return to the SCU

7. From the SCU main screen, select Report from the File menu

◊ Note the file name and location (NodeName.RPT)

◊ Intellution recommends that you use Notepad to print NodeName.RPT for future reference

8. From the SCU main screen, select SCADA from the Configure menu

◊ Select an installed driver (other than SIM or DDE), and then click Configure

9. Once the Configurator has started, select Save As from the File menu, and specify CSV file type

◊ Repeat this for each Channel of each Driver currently installed

◊ Note the file names and locations for later use

10. Exit the SCU


154 Student Guide


F. Manually Exporting Files (continued)

11. If the current project uses recipes (RCP.exe), start Recipe Manager

◊ Otherwise, skip to Step 13

12. From the File menu in the Recipe Manager, select Save As *.rcx (Master text) or *.rcy (Control text) for each Master and Control Recipe

◊ Note the file names and locations

◊ When finished, exit the Recipe Manager

13. If the current project contains Tag Groups, start the Tag Group Editor (TGE.exe)

◊ Otherwise, skip to Step 15

14. Open a TGE file, select Save As from the File menu, and specify file type CSV

◊ Repeat this for each tag group file

◊ Note the file names and locations for later use

◊ When finished, exit the Tag Group Editor

15. If iFIX is to be installed on a different machine, and the current FIX and target machine are on the network, share the FIX directory to allow network access

◊ Otherwise, make a copy of all the files created in the above steps

• Note:

- FileWedge is a utility that you can use to automatically export files

◊ FileWedge is available at http://www.taltech.com

- With FileWedge, hundreds of files can be opened, operated on and saved without user intervention

- FileWedge uses an ASCII file as a template for an integral SendKeys program, which can send an automated series of Keystrokes into any currently active window

- Example: to create a .TXT file containing a list of all the TGE files in the FIX32\PIC directory, from the command line type:

◊ DIR C:\FIX32\PIC\*.TGE /B > TGELIST.TXT.

- Using FileWedge, you can now operate on the entire file list




G. Completing Tasks on the iFIX Target Machine

• Complete the following tasks on the computer on which iFIX is being installed

• To complete these tasks, log in to the PC Operating System with a user account that has administrative rights on the local machine

1. Check the computer and its installed software

◊ From the Start menu, select Projects|Administrative Tools|Event Viewer

◊ Inspect the System and Application entries

◊ Note, document, and correct any errors

2. Check the size of the current Swap file

◊ Follow Intellution’s recommendations for correctly sizing the Swap file

3. Verify the virtual memory setting

◊ The virtual memory should be set to 2.5 times the physical memory (RAM)

4. If networked, verify that the network is functioning properly

◊ If using TCP/IP as a network protocol, verify that all Hosts files are correct and up to date on all FIX nodes on the network

5. If applicable, convert to Windows NT or Windows 2000

◊ The computer on which iFIX is to be installed must be running the Windows NT 4.0 or Windows 2000 operating system

◊ Windows 95 and Windows 98 are not supported

6. If applicable, turn off anti-virus software

◊ Disable the software and reboot the computer before installing iFIX

◊ Once the installation is complete, restart the anti-virus software


154 Student Guide


H. Installing iFIX Software

• If iFIX is to be installed on the computer currently running FIX, complete the following procedure:

1. Ensure the FIX software is not running, and close any other programs that are running

2. Login to the PC Operating System with Administrator privileges

3. Insert the iFIX CD into the CD-ROM drive

◊ If Setup doesn’t start automatically, from the Menu Bar, select Run from the Start menu

◊ In the Open Text Box, type: <CD Drive Letter>:setup.exe, then select OK

4. From the iFIX Welcome screen, select Install

5. When prompted “SCU found do you want to use its information?” Select NO, do not use the current SCU information

6. When prompted for the Destination Folder do not install over the current FIX installation (see previous step)

◊ Install iFIX into a unique folder

◊ When finished, select Next

7. Intellution recommends that Typical install is selected

8. Enter the Nodename

◊ reference the NodeName.RPT report described in step 7 of the Export FIX Files

9. Enter the Node Type and Network Type

10. Enter Remote Scada nodes if applicable

◊ Verify that IP and Names are in the Hosts file

11. Install applicable Drivers

◊ check Intellution’s web site, http://www.intellution.com, for the latest release

◊ The drivers must be installed before migration of the Process Database (PDB)

12. View the Release Notes, and restart the computer

13. Install applicable iFIX SIMs and add-ons from the Intellution web site




I. Setting Up the System Configuration Utility

• Once iFIX is installed, complete the following procedure to set up the System Configuration Utility on the iFIX node:

1. Start the iFIX SCU

◊ For the next two steps, reference the NodeName.RPT report described in step 7 of the Export FIX Files

2. Verify that the Node name is correct

3. Enter the Database Name that will be used

◊ For now, ensure it is the same name as the previous project

◊ When prompted, select Use Anyway

4. Verify drivers are present by choosing Configure|SCADA

◊ If required, add the SIM and DDE driver to the “Configured I/O Drivers.”

5. From the listed Drivers, select the current Hardware Driver, then Configure

6. From the Driver Configurator, select File|Open

◊ Change List Files of Type to CSV from the combo box

◊ From the Folders List, navigate and locate the file created in step 9 of the Export FIX Files section

7. Select File|Save As when done, and save the changes to the <drive letter>\Dynamics\Pdb directory

◊ Repeat this process for each Driver and Channel in use on the project

8. Save and Exit the Driver Configurator when finished with each driver

9. Save and Exit the SCU


154 Student Guide


J. Verifying the I/O Driver and Database Migration

• Once the SCU is configured, complete the following procedure to verify the I/O driver migration and to convert the Process Database:

1. Start iFIX

2. From the System Tree in Workspace, start Mission Control

3. Select the I/O Control tab and examine the information

◊ Ensure that there is data being polled

◊ If data is present, go to Step 6

4. If there is no data present, ensure that the Driver is loaded and is running

◊ Exit Mission Control and start the SCU

5. Select Configure|SCADA, select the I/O driver and verify that the Poll Records are present

◊ If they are not present, repeat steps 6 and 7 in the Setting Up the System Configuration Utility section

NOTE: It is very important that the Drivers are loaded before proceeding with conversion of the Process Database

6. Minimize the WorkSpace

7. Copy the PDB file to be migrated to the iFIX PDB Directory

8. Convert the Database

◊ Select Start|Run and type DriveLetter:\Dynamics\dbcvt.exe

◊ The Command Window will close automatically when complete

9. Maximize the iFIX WorkSpace

◊ Start the Database Manager and then select Database|Reload

◊ From the file list, select the converted PDB file

10. Save and exit Database Manager

11. You may see an Import Errors Found dialog box after your import

◊ If errors are found, Notepad will open and display a list of the import errors that occurred.

◊ Save a copy of this log so that you can identify the individual tags with which the import procedure had a problem

◊ Consult the manual or contact Intellution for further details on how to treat import errors




K. Finishing the Migration

• Once the I/O Drivers and Process Database are converted and running, complete the following procedure to finish migrating the FIX files:

1. Copy the old HTA files to the location specified in the SCU

2. Copy the HTRDATA files to the location specified in the SCU

3. From the iFIX WorkSpace System Tree, start Historical Assignment

◊ Select File|Open from the Folders List, navigate and locate the file you created in the Export FIX Files procedure, open the file and save to the <DriveLetter>:\Dynamics\htr directory

4. If you have Recipes you wish to import do so now

◊ From the system tree in the WorkSpace, select Fix Recipes|New Recipe and open the *.rcx and *.rcy files created by step 11 of the Export FIX Files procedure

◊ Save each in turn to the new Dynamics/rcm or Dynamics/rcc directory

◊ When finished, exit the Recipe Builder

5. If you have Tag Group Editor files, from the iFIX WorkSpace System Tree, start the TagGroup Editor

◊ Select File|Open

◊ Change File of Type to CSV

◊ From the Folders List, navigate and locate the files you created in the Export FIX Files procedure

◊ Open and save them to the <DriveLetter>:\Dynamics\Pdb directory

◊ When finished, exit the Tag Group Editor


154 Student Guide


K. Finishing the Migration (continued)

6. If you wish to import your old security configuration, you can do so now

◊ From the WorkSpace System Tree, select Security|Setup

◊ From the Security Configuration main menu, select File|Import. From the Folders List, navigate and locate the file you created in the Export FIX Files procedure

◊ Select Open, and follow the prompts

◊ Passwords may need to be reentered for the User configuration

◊ If you wish, you can enable security at this time

◊ When done, Exit and Save changes

7. Convert the FIX ODF file to iFIX GRF files

◊ Use the notes in the Converting Pictures section for more information



34.3. Converting Pictures______________________________________

A. Notes

• This section describes how to use the Picture Conversion Utility to convert pictures created in previous versions of FIX

• The following tasks describe how to download and use the utility

• Additional information about the utility is available in the Picture Conversion Utility Readme file

- this Readme file is installed to the Dynamics base path when the utility is downloaded and extracted

• NOTE:

- The Picture Conversion Utility converts pictures to iFIX from FIX versions 5.65, 6.0, 6.12, 6.15, and 7.x

• The Picture Conversion Utility is installed as part of iFIX

- C:\Dynamics\PictureConverter.exe

B. Downloading the Picture Conversion Utility

• The Picture Conversion utility is also available for downloading from the Developers’ Corner page on the Intellution Web site

• You should have your Intellution WebSupport Username and Password available before starting this procedure.

• To download the Picture Conversion Utility, go to http://www.intellution.com


154 Student Guide

34.3. Converting Pictures _____________________________________

C. Using the Picture Conversion Utility

• You can use the Picture Conversion utility to convert multiple pictures at the same time

• To use the Picture Conversion utility:

1. Ensure that the iFIX Workspace is running

2. Double click on the picture conversion utility (PictureConverter.exe) to open it

3. When the utility opens, select Set Destination Directory from the File menu and select the destination directory for the converted pictures

4. Select Open ODF File to Convert from the File menu

◊ The Select Picture Files for Conversion dialog box appears

5. Browse to the directory where the FIX pictures you want to convert are located

6. Select the pictures to be converted, and click the Open button

◊ The utility converts the pictures selected, outputting warnings or errors to the utility window

NOTE: Error and warning information is also written to the PictureName.log file.

7. Close the Picture Conversion utility

• NOTE

- Intellution recommends that you verify all of the .GRF files after converting



34.3. Converting Pictures _____________________________________

this page intentionally contains no data


Documents

Chapter 34 Migrating from FIX v7 - read.pudn.comread.pudn.com/downloads203/doc/954495/Student Guide/34... · • Use Figure 34-2 to determine from which FIX SCADA nodes data and alarms