RI ATE System Basic Architecture
The measurement process is simple and direct. Signals to and from the Device-Under-Test (DUT) are provided through several types of connection schemes:
- Independent On Wafer Coplanar Probes
- On Wafer Probe Cards or Membrane Probes
- A Socket and Device Interface Board (DIB)
The System Hardware
| Cassini RF ATE System has 3 major components: |
|
An overview of each of the ATE system's major components will be covered in later chapters with more detail. It is good to understand how the system is designed to get maximum efficiency when using the ATE system in production. The "big" Cassini refers to systems with an Infrastructure model RI8557A, and is mentioned as the Large Cassini or Cassini 57, due to the model number. It has room for 3 infrastructure sources. Similarly, the "small" Cassini refers to systems with an Infrastructure model RI8556B, sometimes called Small Cassini or Cassini 56 with room for 1 source. Cassini 16 (RI8568B) does not have room for any sources, so an additional side rack or just TIMs are used. All Cassini infrastructure options include a touch-screen monitor so that Operators can use the system with a simple button interface. All Cassini systems use a graphical user interface that will be explained in more detail later.
Operating the System
- System power up sequence
- Using Fixture and DUT Board
- Docking with a Handler
- Using the System Controller (RIFL, eCS)
- Start and Stop RI System software
- Using Guru and the RI System Software
The following lessons describe how to use RI ATE systems and are designed to help you become familiar with the RI platform. After learning how to operate the system, the various instruments and hardware components are identified.
Guru provides storage, retrieval, revision and access control for the system controller.
When there is a Guru Server available, Guru also provides automatic updates, backups, and recovery of objects. Guru checks regularly for new versions and automatically updates. During the update process, Guru will close and restart with a newer version.
The basic architecture for controlling access to the system is defined by Users and Group membership. The user information includes name, title, department, company, and password. The Group contains users and permissions. Each user can belong to one or more groups. Guru objects are only accessible to users who are members of a group with the permission to access the object.
Every system controller is setup to automatically launch Guru while the system controller starts. If Guru is exited, it will automatically restart.