Knowledge Base Article #168 - FasTest Test Results and how they interact with print and graph macros
DateApr 18, 2008
ByENOSERV
Filed UnderRTS General
ClassGeneral
 
Issue Addressed
We ran into our customers that see a Theoretical Graph printed on a TOC graph and wonder, "Mine does not do that. Why does that no appear on my graph?"

Another customer is running a timing test and the Range information reported incorrectly, but the relay still passes. They run the same routine in the default FasData.mdr, and the problem does not occur.

Another customer has very long operate times, and they do not see the times with the results, rather ******. If they run the routines on the latest FasData.mdr database, it works.

What is the deal?

 
Causes of Issue
When we display results or graphs, we do that with print macros and graph macros. These macros are simply text files that tell where to position the data, what titles to print, what information should be included, etc. When you run a FasTest procedure, the RTS.exe selects what print macro and graph macro to use to display the saved result data, based on the procedure just ran. When the results are printed, the RTSPrint.exe looks for the chosen macro in the database for that macro, in order to display results and graphs as determined by the command written in that specific macro.

If the macro is found in your database, all print and graph instructions will be performed based on the macro that is located in the connected database. If the print macro or graph macro is NOT found in your database, the instuctions for each specific FasTest macro is located in the RTSPrint.exe, and those instuctions will be used for printing and graphing.

The first few years after the release of RTS, the macro text did NOT exist in the RTSPrint.exe, as we had not considered that possibility. Because of that, our print and graph macros HAD to be in the database for the results to print. For many of our customers, the initial print and graph macros will be present in your current database. It was only after the idea was implemented and proven over a period of time that we removed all the FasTest macros from the default FasData.mdr database to perform as we do at the current time.

The reason problems as above occur is becuase of older FasTest print and graph macros that exist in the database that have not been updated with either modifications or new additions. In this case, they actually get in the way of progress. If they were not present, the latest print and graph ideas could be utilized if they were not present in the database at all.
 
Solution to this Issue
All FasTest macros start with the initials R_xxxxxx.TSP or R_xxxxxx.TSG. This nomenclautre was chosen as we believe we can isolate the FasTest macros from a potential name the customer might choose. If we remove these macros from the database, it will allow RTSPrint.exe to use that latest and greatest macros that are hard coded in the exe.

To remove the macros, open your database in RTSBackupMerge and choose the macro button located in the middle of the window. Highlight ALL macros that have a R_ as the start of the macro name (R_PICKUP.TSP, R_TIMING.TSP, ect.), then right click to DELETE these files. It is okay, as the macro text for each of these macros is present in RTSprint.exe.

 
Other Comments
As an additional comment, this should also open up ideas to you as a company if you actually do want to control the look of your print operations. You can maintain these macros in the database, or add them into your database as they are on the ENOSERV website. They can be modified internally as desired to change to look and feel of the print operation. Contact ENOSERV Support for processes to implement such ideas.

Login to Support
Email:
Password:
Contact Support to reset your password

Support Links
Support Main
Register for Support
Knowledge Base

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