#15

Q: What is the purpose of ‘Special Script’?




Special Script

Do we have all the features you need? If not we may still be able to help you. For if you have a special requirement, chances are that other folks can benefit too. So here is a special deal just for you: We do what you want - or at least, pretty close to it. Then we give you a special keyword which you add to your script default file (Spscript.txt), or create a new "filename.txt" containing just the keywords you wish. Upon detecting the presence of this keyword, the special feature is invoked. Here are some examples of some Special Script keywords:

  • SayGroupInPinAssign
  • MouseMoveCount 20; between 5 and 50
  • PrintShmooResult
  • WatchDogTimer
  • RunContinuouslyWhileMeasureCurrent
  • ShowPmuFile
  • GetPinsFromTrn
  • CurveTrace
  • DoDisplayDepth
  • Note that the keywords themselves are fairly descriptive of their purpose. You may need to contact us about implementation if you don't readily understand the keyword.

    Executing Special Scripts can be done in two ways. From the Translators window, click on Special Scripts to begin. Click on "Scripts..." and the file "AllScriptNames.txt" will be created and displayed in NotePad. Each time you receive a new release of ETSNT you should do this to update this script file. Now cut away all the script names you don't want and leave only the desired features in the file, and save the file with a different name. For instance, put only CurveTrace in the file and then call the file "curve.txt"; you'll know immediately what this file is for by its name alone. Close the NotePad and click "Load" on the Special Scripts window, selecting the new file. When you click "Execute", the script is enabled and will remain enabled until you close and reopen ETSNT.

    Another option for use of the scripts is to place all of the scripts you wish into a file called "Spscript.txt". This list of scripts will be executed automatically whenever you open the ETSNT application, relieving you of the manual Load/Execute process. If you ever want to override these scripts, you must modify or delete the "Spscript.txt" file, then close and reopen ETSNT.

    Why would we not just implement your special feature without requiring a special keyword? There are two reasons. First, we wish not to obsolete our manuals and helpfiles for all of our customers every time we assist one of our other customers. Secondly, it may turn out that our initial implementation - and for that matter any other implementation - proves less useful than hoped for. So we retain the keyword until the feature has been sufficiently time-honored and effectively applied, and we are ready for a new update of the manual. Then, and only then, will we dispense with the Special Script keyword and let the feature we tailored for you be an integral part of the ETS tester - to the benefit of all. Prior to this, we’d rather not burden other users with excess software “baggage” until the feature has proven its usefulness.

    There are dozens of Special Script keywords at any given time, and new ones appear with almost every release of ETSNT updates. View the file “AllScriptNames.txt” with your release of ETSNT and see the latest Special Script keywords available.

    QL15.zip is a zipped Word file of this Q'nApp.


    Click your browser's Back button to return to the Q'nApps index.

    © 1999 HILEVEL Technology Inc.