Beginning with version 5.3, Vector’s interface has been stream-lined to bring the user experience more in line with that of our RTS clients. The several test-type specific tab sheets of Vector’s main run-time window have been replaced with the traditional RTS-style trio: Static Specs, Action Specs and User Options.
What this means for the user:
The Pre-Defines button—whose location varied with test type in the old Vector interface—is now found in the top left corner of the Static Specs tab for all test types—just like in RTS. Also, in the Static Specs tab, Vector now has an RTS Defines feature which, like RTS, is where device-specific settings will be assigned to a test's control variables.
The Post-Defines button has also been moved to the traditional RTS location. It is now found in the lower right corner of the User Options tab (with the caption “Advanced Options”). The timer/ input configurations which used to be found in Vector’s Timers tab are also now in the User Options tab.
The content of all other test-specific tabs (States, Triggers, Transient, and FastFault) has been folded into the Action Specs tab.
In addition to the face lift, Vector 5.3 includes an important new feature which our clients have requested: The ability to auto-load fault data from attached ss1 files. With this feature, our users retain all of the traditional advantages of the library/system model while testing with terminal-specific, fault values generated by Aspen One-Liner or similar products.
To use this feature, attach one (or more) ss1 files to the routine. Then open Vector’s new RTS Defines window from the Static Specs tab and set the USE_SS1_FILE field to 1. The two remaining fields then specify (respectively) which file to load from, and which fault from that file to load. Files are indexed in alphabetical order beginning with 1. The fault index is also a 1-based index. |
