Training Paragon Upgrades Driver Database Java Support Knowledge Base	Converting from Paragon 500/550 to Paragon for Windows/OS2 Before converting an application from Paragon 550 to Paragon for Windows/OS2, please review the following sections, which outline the basic differences between the two packages, as well as follow the detailed steps listed below. Be sure to follow the "Before Converting" steps as well. Basic differences between the 550 and Paragon for Windows/OS2 packages Paragon 550 contains a Strategy Builder. The 550 Strategy builder provides for communication to hardware, as well as performing the logic or calculations necessary to manipulate the process. The Paragon for Windows/OS2 product also has a "strategy builder" called the Graphical Strategy Builder (GSB) which configures the Continuous Strategy (CS). However, the CS is only responsible for logic and calculations, as Paragon for Windows/OS2 contains a separate server, the Process I/O (PIO), that is solely responsible for hardware communications. For example, in 550, hardware blocks were pasted in the Strategy for hardware communication. Now the separate server PIO is configured for hardware communication. PIO (hardware values) are brought into the strategy via the use of Terminators. For data acquisition, Paragon 550 contained AHST blocks, which were pasted in the strategy blocks to collect History information. Paragon for Windows/OS2 contains a separate server, the Data Manager (DM), to perform history and data collection. Paragon 550 contained a Display Builder. Paragon for Windows/OS2 contains the Operator Interface (OI) builder, which is similar to the Continuous Strategy builder in that graphical images are pasted on the screen. For Recipes, Paragon 550 contained Recipe Blocks. Recipe Blocks are not supported in Paragon for Windows/OS2, as a separate Recipe Client. Is utilised. Note that the RCP files generated in 550 cannot be executed in Paragon for Windows/OS2 as the Process and Function naming conventions are different. However, they may be used as a guide to making a new recipe. Any text editor can be used for Recipe creation/ manipulation. Please refer to the Recipes Client chapter of the Reference Manual for further information. Before converting the application In the 550 Strategy, the %M Value (located at the bottom of the Strategy Builder screen) should be less than 85% in order to execute all of the blocks & connections properly. Before the 550 CS conversion can begin, verify in the 550 strategy that the %M filed is less than 85% within each Process. If not, then you will have to save out parts of the strategy to compound blocks and delete the blocks in the compound from the current strategy until the %M is lowered under 85%. (Steps to complete this are in the Step By Step Conversion Process below.) Next, paste down the compounds to new 550 strategies and convert them as well. After all 550 strategies have been converted, you can paste the "compound strategies" into the newly converted strategy. Paragon for Windows/OS2 does not contain the use of compounds, however it contains Layers which allow you to hide detail visually ñ the function blocks remain in the same process (steps to follow). Also, it is suggested that any passwords be removed before converting from 550. Once a strategy is converted to Paragon for Windows/OS2, password protection is provided to be saved with the strategy. When converting the 550 display files, take careful note to Pick Fields. In 550, a Pick Field can open another display during runtime. TNT will name the pick field as a Text object and attach a Left Mouse Down Action to launch a new display. If a Pick field had been configured to launch a new display on a Digital bit going high, then you must configure TNT Window Parameters to launch a new display on a CRA action. The Page table configuration in TNT does not exist because of increased functionality in launching new displays. Please refer to the Reference Manual for details. Overview of Conversion Process As mentioned above, the hardware communication block and history block functionality in the 550 strategy are replaced with separate servers. To help facilitate the conversion to the new PIO and DM servers, listings of the 550 strategy are generated in TNT Converting Process that list the I/O, history and process connections in the 550 strategy. They will be located in the TNT working directory after the conversion of the 550 strategy. The file names are 550 LIST, 550HIST, and 550IO, and short excerpts from theses files are attached to this application note. 550LIST: A detailed listing of each block and its parameters in the original strategy. 550HIST: A detailed listing of any historian connections in the 550 strategy. Historian connections will be removed from the converted strategy since TNT does not support History blocks. This listing aids in reconstructing these connections within the Data Manager. 550IO: A detailed listing of any I/O hardware connections in the 550 strategy. Hardware connections will be removed from the converted strategy since TNT does not support hardware blocks. This list aids in reconstructing these connections within the PIO and CS subsystems. Step by Step Conversion Process Run Paragon 550 and enter the strategy. Now check and make sure that the %M in each Process is less than 85%. If not, continue with step (2); otherwise skip to step (7). If any Process is over 85% then you must delete blocks until the %M falls below 85%. The easiest way to begin this is to find blocks that are not connected to other processes and save them out in a compound block. Save out the other half of the process into another compound. Then right click on the eraser and left click on the X. This will clear the %M back to zero. Paste one of the Compounds back into the Process. This must be done for each process over 85%. For all of the other compounds not placed back into the Process, make a new strategy and place down the compounds and save out a new strategy. Now you will have to convert two strategies. Once this is completed, move your *.db files for conversion to the TNT working directory in order to keep all of your files together. The next step is to bring up TNT and load the CS (Continuous Strategy Builder). Once in the CS builder, select File, 550 ConvertÖ and choose the .db file(s) that were placed in your TNT Working Directory. PIO processes will be added across the bottom of the Process layer. You will need to supply the name of the PIO library to the PIO process block. Terminators will graphically represent multi-level connections (made through Process blocks and/or compound boundaries). Lineless connections are also replaced with terminators. Adding a terminator will create the formerly invisible half of the connection. The connection will be made to the lower left corner of the source/destination function block. You may want to edit the positioning of the connection. Text used for block names and types will default to the System font. Text strings may appear truncated unless function block names are short. Select Objects, Subsystem Parameters to check the runtime parameters, such as scan periods and remote connections for this strategy. (These parameters are similar to the parameters set under Runtime Parameters in the Environment Manager.) Now attempt to save the strategy, File, Save, file .csb (where file is your new filename). If you have received an OIB014 "Errors detected" dialog, select Options, Validate Strategy. This will provide a list of errors that must be corrected. Most likely the error(s) are due to unconnected blocks. Missing connections are usually due to any missing blocks that are not supported by TNT, such as Hardware Blocks. The 550IO listing will help you to connect these blocks to the new PIO database, which takes the place of hardware blocks as described above. Terminators will need to be placed in the strategy to allow PIO data to be brought into the strategy. Please refer to the Reference Manual for information on placing and connecting terminators. Note: If the 550 strategy contained invisible tag names (blocks in the strategy that had an underscore (_) in the Tag field), they must be renamed to a legal TNT tag name. You can rename these blocks after the TNT convert easily by doing a Query on "*._*" in the GSB (see Reference Manual for details on the Query Function). When the Query function returns all of the blocks with "_" at the beginning simply by Alt-Right clicking in the Name field to type in a new name. Press Enter after you enter each new name. Open up a window and search your working directory for 550LIST, 550HIST, and 550IO files. It is suggested that you open them up in a text editor and perhaps print them out to make them easier to work with. If you have 550IO in your working directory, you will have to build a PIO database first before continuing with the GSB. Also if you have a 550HIST file, you will have to build a Data Manager database before continuing. See 550HIST to DM Conversion and 550IO to PIO Conversion below. (After completion of the PIO database.) PIO values need to be brought into the strategy to satisfy the missing "hardware block" connections. A PIO Process block needs to be placed at the root layer of the strategy (along with the CS process blocks) connected with a conduit. Please refer to the Reference Manual for this procedure. Next, enter Objects, External Connections to connect the appropriate Function block parameters to their PIO connections. If you had less than 85% (if you skipped Steps 2-6), in the Processes from 550 skip to step 21. Before you convert the second Strategy, open a window and save the listings (550LIST, 550 HIST, and 550IO) to another directory so that by converting the second strategy the first strategyís listings will not be written over, and may be saved for future use. Now convert the second Strategy. Since there were saved compounds, they will show up in the CS as Layer Blocks. Enter the Layer blocks and select Edit, Select All from the menu selections. From the Menu, select Edit, Copy. Now enter your other strategy and paste the function blocks into the appropriate Process. Make sure to check your working directory for listings. You may have some additional PIO of DM connections. Next open an editor and search the 550LIST file for NON Supported Paragon 500/550 Blocks. Non supported blocks and their replacement blocks (if any) in TNT are listed the Continuous Strategy chapter of the Reference Manual. Once you complete the External connections, Validate the strategy. If no errors are reported, save out the Strategy again, and continue on to the OI conversion Processes; otherwise continue validating your strategy to find the outstanding errors. Read the CS manual for additional information. Display (OI) Conversion: If you have AppDoc in Paragon 500/550, run the program on the GI files first. You should read the OI builder section and the Import section before continuing. Select a Paragon 550 display file (.GI) and select File, Import from the OI builder menu. After the conversion your pick fields will now have a Left Mouse Down action to open new displays. Note that Page Table configurations, PID faceplates, and trends do not covert over. PID faceplates may be made using Polygons with Percent Fill connections. A trend in 550 can be replaced by a Plot object. Refer to OI chapter on configuring Plot objects. For 550 AHIST block connections you can configure an Itrend to view past data, connecting to Data Manager database (History functions). For all other objects you nay have to reposition, resize, change colours, or modify actions appropriately. MSDos and Windows NT fonts are different and do not convert well. They will need to be checked. It is useful to run the 550 screens on a PC beside the one you are using for the conversion. This way you can check screen actions, fonts etc. for before and after conversion. 550IO to PO Conversion: Review the 550IO file for connection list, Com Port, IO Status (configured as inputs/outputs) and Type of Hardware Block. For example, Hardware block 04D with IO Status = IIII describes an Optomux block reading 4 digital Inputs. In 500/550 the Hardware inputs are directly connected to DIN blocks Inputs. However, in TNT, DIN blocks are not necessary to receive IO. If DIN blocks are not connected to downstream blocks for some type of computation, they may be deleted. Following this example using Optomux, in the PIO builder you can configure on DigInput Function with the appropriate Unit Address, StartChannel (Dig Input 0 in 550/550) and NumChannel 4 (consisting of Dig Inputs 0-3 in 500/550). For analog inputs and outputs in 550/550 you had to configure a Cond block to remap your data. Now in TNT you can configure a Conditioning table directly in the PIO builder. Each TNT Function requiring conditioning needs only to call out the conditioning Function. Alarming in 500/550 was configured in the Strategy using Alarm blocks with connections from Analog of Digital Input blocks. In TNT the PIO database can be configured directly without any CS blocks. Alarming on individual PIO functions is provided. The Process contains a listing of DM alarm destinations and the Functions within the Process list which from the list to send to using the AlrmDestCfg. Please review the PIO chapter in the Reference Manual for more information on PIO Library file. Also review DM Alarming in the Reference Manual. Excerpt from the 550HIST listing Hist Connect from OPTO.2.Out at Rate 1.000000 Hist Connect from OPTO.4.Out at Rate 1.000000 Hist Connect from OPTO.3.Out at Rate 1.000000 Hist Connect from OPTO.1.Out at Rate 1.000000 Hist Connect from two. 1. Out at Rate 1.000000 Hist Connect from two. 4. Out at Rate 1.000000 Hist Connect from two. 3. Out at Rate 1.000000 Hist Connect from two. 2. Out at Rate 1.000000 Excerpt from the 550IO listing *************Process OPTO************* 		 		 Block o4d Type OP4D TAG			= o4d COM PORT		= 2 IO STAT		= IIII					Watch Dog = Disabled COM STABLE	= N	 Connect List: Sensor Digital Connect from o4d. DI0 to 2.In Sensor Digital Connect from o4d. DI1 to 1.In Sensor Digital Connect from o4d. DI2 to 3.In Sensor Digital Connect from o4d. DI3 to 4.In *************Process One*************** 		 Block o4d Type OP4D TAG			= o4d COM PORT		= 2 IO STAT		= IIII					Watch Dog = Disabled COM DISABLE	= N Connect List: Sensor Digital Connect from o4d. DI0 to 4.In Sensor Digital Connect from o4d. DI1 to 1.In Sensor Digital Connect from o4d. DI2 to 2.In Sensor Digital Connect from o4d. DI3 to 3.In *************Process Two*************** 		 Block o4a Type OP4A TAG			= o4a COM PORT		= 2 IO STAT		= IIII					Watch Dog = Disabled COM DISABLE	= N Connect List: Sensor Analog Connect from o4a. AI0 to 1.In Sensor Analog Connect from o4a. AI1 to 2.In Sensor Analog Connect from o4a. AI2 to 3.In Sensor Analog Connect from o4a. AI3 to 4.In Excerpt from a 550LIST listing ****************Process OPTO***************** 		 Block 2 Type DIN TAG NAME		= 2 DESC			= 							SCAN			= 1.000000 Sec ON TEXT		=				OFF TEXT		= INH ALARM 	= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0 ALM VALUE		= 0 				ENT VALUE		= 0 TRACK		= N 		 Block 1 Type DIN TAG NAME		= 1 DESC			= 							SCAN			= 1.000000 Sec ON TEXT		=				OFF TEXT		= INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0 ALM VALUE		= 0				ENT VALUE		= 0 TRACK		= N 		 Block 4 Type DIN TAG NAME		= 4 DESC			= 							SCAN			= 1.000000 Sec ON TEXT 		=				OFF TEXT 		= INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0 ALM VALUE		= 0				ENT VALUE		= 0 TRACK		= N 		 Block 3 Type DIN TAG NAME		= 3 DESC			= 							SCAN			= 1.000000 Sec ON TEXT 		=				OFF TEXT 		= INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0 ALM VALUE		= 0				ENT VALUE		= 0 TRACK		= N 		 Block One Type PROC TAG NAME		= one 			Alarm Destination		Collection ID 		 Block Two Type PROC TAG NAME		= two 			Alarm Destination		Collection ID   *****************Process One***************** 		 Block 1 Type DIN TAG NAME		= 1 DESC			= 							SCAN			= 1.000000 Sec ON TEXT 	=				OFF TEXT		= INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0				 ALM VALUE		= 0				ENT VALUE		= 0 TRACK		= N	   			Block 2 Type DIN TAG NAME		= 2 DESC			= 							SCAN			= 1.000000 Sec ON TEXT 	=				OFF TEXT		= INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0				 ALM VALUE		= 0				ENT VALUE		= 0 TRACK		= N	 			Block 4 Type DIN TAG NAME		= 4 DESC			= 							SCAN			= 1.000000 Sec ON TEXT 	=				OFF TEXT		= INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0				 ALM VALUE		= 0				ENT VALUE		= 0 TRACK		= N	 Block 3 Type DIN TAG NAME		= 3 DESC			= 							SCAN			= 1.000000 Sec ON TEXT 	=				OFF TEXT		= INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0				 ALM VALUE		= 0				ENT VALUE		= 0 TRACK		= N	 *****************Process Two***************** 		 Block 2 Type AIN TAG NAME		= 2				UNITS		= PCT DESC			= 							SCAN			= 1.000000 Sec HI RANGE		= 100.0000			HI LIMIT		= 100.0000 LO RANGE		= 0.000000			LO LIMIT		= 0.000000 INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0				HHLL GROUP	= NNNNNNNN HI ALARM		= 100.0000			HIHI ALARM	= 100.0000 LO ALARM		= 0.000000			LOLO ALARM	= 0.000000 RATE ALM		= 100.0000			INIT			= Y DEADBAND		= 1.000000			FILT TIME		= 0.000000 Min ENT VALUE		= 0.000000			SCALE ENB		= N TRACK		= N				MAX SCALE		= 4095.000 SIG COND		= 0				MIN SCALE		= 0.000000	 			Block 1 Type AIN TAG NAME		= 1				UNITS		= PCT DESC			= 							SCAN			= 1.000000 Sec HI RANGE		= 100.0000			HI LIMIT		= 100.0000 LO RANGE		= 0.000000			LO LIMIT		= 0.000000 INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0				HHLL GROUP	= NNNNNNNN HI ALARM		= 100.0000			HIHI ALARM	= 100.0000 LO ALARM		= 0.000000			LOLO ALARM	= 0.000000 RATE ALM		= 100.0000			INIT			= Y DEADBAND		= 1.000000			FILT TIME		= 0.000000 Min ENT VALUE		= 0.000000			SCALE ENB		= N TRACK		= N				MAX SCALE		= 4095.000 SIG COND		= 0				MIN SCALE		= 0.000000	 			Block 3 Type AIN TAG NAME		= 3				UNITS		= PCT DESC			= 							SCAN			= 1.000000 Sec HI RANGE		= 100.0000			HI LIMIT		= 100.0000 LO RANGE		= 0.000000			LO LIMIT		= 0.000000 INH ALARM		= Y				ALRM GROUP	= NNNNNNNN PRIORITY		= 0				HHLL GROUP	= NNNNNNNN HI ALARM		= 100.0000			HIHI ALARM	= 100.0000 LO ALARM		= 0.000000			LOLO ALARM	= 0.000000 RATE ALM		= 100.0000			INIT			= Y DEADBAND		= 1.000000			FILT TIME		= 0.000000 Min ENT VALUE		= 0.000000			SCALE ENB		= N TRACK		= N				MAX SCALE		= 4095.000 SIG COND		= 0				MIN SCALE		= 0.000000	
NEMATRON SOLUTIONS   |   ABOUT NEMATRON   |   CUSTOMER SUPPORT   |   PURCHASE   |   SEARCH   |   CONTACT US