When starting up, the tester will name the instruments based first on its pervious configuration, called the Tester definition (RiTesterDef). After a TIM changes location, the Tester must be saved with Tester > Save menu option from the configuration window. This is important when multiple instruments exist in the same configuration because the location of the 1st, 2nd, etc. instruments is very important. The tester may be confused when adding/moving/upgrading more than one TIM at a time. One way to avoid this, is to perform a System > Check for each change, "one for one". Before adding TIMs, be sure the calibration data is imported into Guru. See "To inspect the Instrument’s Calibration Date and Time" procedure in Import Cal Data .GZP via Guru Browser to confirm valid Cal data.
Reconfiguring a Tester:
1. Launch the latest Short Cut with all the current configured TIMs and open the Configuration window by choosing System > Tester from the main Cassini window.
2. Remove all TIMs that are being changed and perform a System > Check, the instruments in the removed TIMs will disappear from the configuration window.
3. Latch the first TIM into the correct location ("Instrument") and perform a System > Check. Confirm that "Instrument" has been added to the configuration in the correct T-Location. (Do Not add both at the same time, allowing the tester to assign the instrument names in a specific order.)
4. Now latch the second TIM into the correct location ("Instrument2") and perform a System > Check. Confirm that "Instrument2" has been added to the configuration in the correct T-Location. The tester will automatically assign the next number to the instruments in the TIM. For example, if a second RI8546C is added, containing the DutControl, PowerVI, and StaticDigital instruments, the new instruments will be assigned as DutControl2, PowerVI2, and StaticDigital2.
5. Repeat Step 4 for each additional change.
6. In the Configuration Window menu, select Tester > Save to commit all changes to the Tester definition so when the tester is restarted the instrument names will be preserved. When multiple copies of the same instrument exist, the tester definition differentiates them, naming which is instrument1 and which is instrument2, etc. The definition also enables simulated testers to know the tester's precise configuration.