ENOSERV :: Support

Knowledge Base Article #143 - Re-Associating Linked System Routines from Traditional Librarys Routines to FasTest Library Routines
Date	Nov 27, 2006
By	ENOSERV
Filed Under	RTS
Class	General

Issue Addressed
Previous to the introduction of RTS with the FasTest method of creating Library Routines, customers wrote Library Routines in Traditional Code (Basic code) using the product UltraTest. Although Traditional Routines perform the same as a FasTest Routine, they take expertise to create, modify, and maintain. Becuase of this, some ENOSERV customers desire to migrate to the new FasTest Procuedres only they would like to maintain their original System Routines and Results as well.

Causes of Issue
This is an acceptable choice, but one that cannot be performed with the push of one button. Two items are present that create issues that must be dealt with. 1. FasTest Routines are not given the same name as Traditional Routines, named as such simply to display a difference in the contstruction of the routines. System Routines are linked based on the Library Routine name. This link requires modification. 2. FasTest Routines may have settings names that do not match Traditional Routines. In this case, System Routine created from Traditional Routines will have setting names that do not align with the FasTest Routine. For these cases, the FasTest test procedure will be improperly written for the setting nomenclature expected. Setting nomenclature of the System Routines must be changed after a Link modification has occurred. NOTE: The majority of routines have the same nomenclature. Changes in setting name of the FasTest Routines were changed strictly for consistency within the Library Routines.

Solution to this Issue
Steps can be taken to successfully migrate System Routine linked to Traditional Tests to FasTest Routines. Documentation is given below explaining the steps required. 1. You first need a comparison list between your availiable Library Routines and Setting Names as well as the default FasData.mdr database and Settings Names. This list can be supplied by ENOSERV in either a text or Execl format. E-mail your database to RTS Support and we will return this list. 2. You will then take the list and develop a plan based on differences seen. Execl is a very powerful tool to with the abiltiy to compare cells to located differences, rather than attempting to perform this step manually. Actions items will need to be determined in your game plan. a. List what FasTest Routines can be used to replace your Traditional Routines. b. List which FasTest Routines have different setting nomenclature than the Traditional Routines. c. For setting name differneces, list which setting names should be added in the System Routines. d. For setting name differences, list which setting names should be replaced in the existing System Routines. 3. Insure you have the latest RTS updates, including the RTSTools.exe. Log on to www.enoserv.com and migrate to the Support->Download section. Logon, select �Downloads� ,and look under the [ RTS Downloads ] section to download RTSExes.zip. This can be extracted to your RTS directory, overwriting existing files, as we only have program updates in this file. 4. It is also suggested to download the latest RTS FasTest database as well, FasData.zip. When you extract this file, make sure you do not overwrite any existing database that contains data that you wish to keep. 5. We will use the RTSTools.exe file loacted on your computer. It can be opened directly through the Windows Explorer or the RTS Main window under the �Utilities� menu item. 6. MOST IMPORTANT: Backup your original database just to make sure you can return to the original database if needed. 7. The next step could be go a number of ways, but here given is the recommendations of ENOSREV. 8. Use the RTS Backup window to copy data from the downloaded FasData.mdr database into the Customer database. To make the process faster, remove all �Copy Associated� check boxes, but apply all �Overwrite Existing� checkboxes (as they apply). Copy all Library�s Routines from FasData.mdr to the Customer.mdr, followed by Macros, Curve Data, and Translation Tables. 9. Open the Customer database and delete all Library Routines that are to be replaced with the FasTest Routine. (Example: Delete BDD-15 in place of the new BDD-15.FST) 10. After the original Library Routines have been deleted, you now have �Orphaned� System Routines, that is System Routines that do not have a Library to operate. To fix this problem, you open RTSTools.exe and look in the group [ System Routine Modifications ] for the button �Link Orphaned Routines�. As you click this button a window appears listing all Library Names in the connected database and the Orphaned System Routines. One by one, select a Library Routine Name to an Orphaned System Routine name followed by the �Re-Link Selected Routines� button. The Orphaned Routines will be re-linked to the new Library Name and the window will be refreshed. Continue this process until all Orphaned Routines have been linked. 11. NOTE: For reference, you may want to maintain a record in the excel spreadsheet that this link was performed. If you find a link from your list that was not performed, it will be because the original Library Routine was not deleted or no System Routines for that Library exist (which in that case nothing needs to be done) . 12. Once the System Routines have been re-linked to the new Library Routine Names, we know have to change the settings names in the System Routines as needed. For this you will still use RTSTools.exe, but look in the group [ Enter/Modify Data in Primary Tables ] for the button �Add/Replace Settings�. 13. Here is where the created list will come in handy. In order to save you some headaches, delete all entries that have anything to do with SEL. These are �self-populated� based on the relays settings themselves, so you do not have to worry about them. 14. Use the list to determine which setting names need to be added to which System Routines. Enter a Variable Name and Default Value, then Enable Filter in order to select only the Library Routine names in which the setting should be added. Choose to Add Settings to Linked System Routines only and apply the �Add Settings� button. Perform this same operation for each setting name that needs to be added, �making sure to reset the Filter� for each operation. 15. Follow the same process to Replace Setting names. 16. At this point, you should be done. Your original System Routines will be linked properly to the new FasTest Library Routine. All results will still be linked properly. You should be ready to go. NOTE: If you do see anything un-expected, do not hesitate to contact ENOSERV. With this many changes, there is always the chance that something was overlooked (especially when replacing/adding settings). If a mistake was made, anything can be fixed. ENOSERV will work with you to get it straightened out.

Knowledge Base Article #143 - Re-Associating Linked System Routines from Traditional Librarys Routines to FasTest Library Routines

Date

Nov 27, 2006

ENOSERV

Filed Under

RTS

Class

General

Issue Addressed

Previous to the introduction of RTS with the FasTest method of creating Library Routines, customers wrote Library Routines in Traditional Code (Basic code) using the product UltraTest. Although Traditional Routines perform the same as a FasTest Routine, they take expertise to create, modify, and maintain. Becuase of this, some ENOSERV customers desire to migrate to the new FasTest Procuedres only they would like to maintain their original System
Routines and Results as well.

Causes of Issue

This is an acceptable choice, but one that cannot be performed with the push of one button. Two items are present that create issues that must be dealt with.

1. FasTest Routines are not given the same name as Traditional Routines, named as such simply to display a difference in the contstruction of the routines. System Routines are linked based on the Library Routine name. This link requires modification.

2. FasTest Routines may have settings names that do not match Traditional Routines. In this case, System Routine created from Traditional Routines will have setting names that do not align with the FasTest Routine. For these cases, the FasTest test procedure will be improperly written for the setting nomenclature expected. Setting nomenclature of the System Routines must be changed after a Link modification has occurred.

NOTE: The majority of routines have the same nomenclature. Changes in setting name of the FasTest Routines were changed strictly for consistency within the Library Routines.

Solution to this Issue

Steps can be taken to successfully migrate System Routine linked to Traditional Tests to FasTest Routines. Documentation is given below explaining the steps required.

1. You first need a comparison list between your availiable Library Routines and Setting Names as well as the default FasData.mdr database and Settings Names. This list can be supplied by ENOSERV in either a text or Execl format. E-mail your database to RTS Support and we will return this list.

2. You will then take the list and develop a plan based on differences seen. Execl is a very powerful tool to with the abiltiy to compare cells to located differences, rather than attempting to perform this step manually. Actions items will need to be determined in your game plan.

a. List what FasTest Routines can be used to replace your Traditional Routines.
b. List which FasTest Routines have different setting nomenclature than the Traditional Routines.
c. For setting name differneces, list which setting names should be added in the System Routines.
d. For setting name differences, list which setting names should be replaced in the existing System Routines.

3. Insure you have the latest RTS updates, including the RTSTools.exe. Log on to www.enoserv.com and migrate to the Support->Download section. Logon, select �Downloads� ,and look under the [ RTS Downloads ] section to download RTSExes.zip. This can be extracted to your RTS directory, overwriting existing files, as we only have program updates in this file.

4. It is also suggested to download the latest RTS FasTest database as well, FasData.zip. When you extract this file, make sure you do not overwrite any existing database that contains data that you wish to keep.

5. We will use the RTSTools.exe file loacted on your computer. It can be opened directly through the Windows Explorer or the RTS Main window under the �Utilities� menu item.

6. MOST IMPORTANT: Backup your original database just to make sure you can return to the original database if needed.

7. The next step could be go a number of ways, but here given is the recommendations of ENOSREV.

8. Use the RTS Backup window to copy data from the downloaded FasData.mdr database into the Customer database. To make the process faster, remove all �Copy Associated� check boxes, but apply all �Overwrite Existing� checkboxes (as they apply). Copy all Library�s Routines from FasData.mdr to the Customer.mdr, followed by Macros, Curve Data, and Translation Tables.

9. Open the Customer database and delete all Library Routines that are to be replaced with the FasTest Routine. (Example: Delete BDD-15 in place of the new BDD-15.FST)

10. After the original Library Routines have been deleted, you now have �Orphaned� System Routines, that is System Routines that do not have a Library to operate. To fix this problem, you open RTSTools.exe and look in the group [ System Routine Modifications ] for the button �Link Orphaned Routines�. As you click this button a window appears listing all Library Names in the connected database and the Orphaned System Routines. One by one, select a Library Routine Name to an Orphaned System Routine name followed by the �Re-Link Selected Routines� button. The Orphaned Routines will be re-linked to the new Library Name and the window will be refreshed. Continue this process until all Orphaned Routines have been linked.

11. NOTE: For reference, you may want to maintain a record in the excel spreadsheet that this link was performed. If you find a link from your list that was not performed, it will be because the original Library Routine was not deleted or no System Routines for that Library exist (which in that case nothing needs to be done) .

12. Once the System Routines have been re-linked to the new Library Routine Names, we know have to change the settings names in the System Routines as needed. For this you will still use RTSTools.exe, but look in the group [ Enter/Modify Data in Primary Tables ] for the button �Add/Replace Settings�.

13. Here is where the created list will come in handy. In order to save you some headaches, delete all entries that have anything to do with SEL. These are �self-populated� based on the relays settings themselves, so you do not have to worry about them.

14. Use the list to determine which setting names need to be added to which System Routines. Enter a Variable Name and Default Value, then Enable Filter in order to select only the Library Routine names in which the setting should be added. Choose to Add Settings to Linked System Routines only and apply the �Add Settings� button. Perform this same operation for each setting name that needs to be added, �making sure to reset the Filter� for each operation.

15. Follow the same process to Replace Setting names.

16. At this point, you should be done. Your original System Routines will be linked properly to the new FasTest Library Routine. All results will still be linked properly. You should be ready to go.

NOTE: If you do see anything un-expected, do not hesitate to contact ENOSERV. With this many changes, there is always the chance that something was overlooked (especially when replacing/adding settings). If a mistake was made, anything can be fixed. ENOSERV will work with you to get it straightened out.

Login to Support
Email:
Password:

Contact Support to reset your password

Support Links
Support Main Register for Support Knowledge Base

Support Links

Support Main
Register for Support
Knowledge Base

Contact Support
Phone: (918) 622-4530 . . . . . . . . . . . . . . . . . Email: [email protected]

Contact Support

Phone:
(918) 622-4530
. . . . . . . . . . . . . . . . .
Email:
[email protected]

ENOSERV delivers software to help power companies meet the challenges of relay testing in today's time sensitive regulatory environment. ENOSERV supplies companies with rock-solid automation tools that support workgroup uniformity, process transparency & easy test results reporting.
Copyright © 2020 Doble Engineering Company ® All rights reserved.