Software Packages

> BASE OPTIONS

| One Year Software Maintenance Extension / BIT-2001-0000-0

ValiFrame/N5990A One Year Software Maintenance Extension Lic. Sheet On-going product enhancements. First year included in N5990A Core Product (opt. 010) and N5990A upgrade options (e.g. opt. 011) . Minor CTS updates included . Major CTS updates excluded; require N5990A upgrade options

| TEST SEQUENCER / OPTION 010

Contains GUI, Report Generation, Remote Interface and 1 yr S/W Maintenance. Is needed to run all flavors of ValiFrame Test Automation Software (Options 100 – 199). Can be added to M8085A, when a Test Sequencer function is required.

| DATA BASE AND WEB BROWSER INTERFACE / OPTION 001

Option 001, the Database and Web-Interface adds the ability to store the procedure results in a database. These results will be reloaded once you select the same DUT again. You can also review the results using the web viewer. The web viewer works from any connected PC without a need for starting ValiFrame or having a separate license on that PC. The option hereby allows you to view the test results even if the system is occupied by a colleague.

| SWITCH SYSTEM AND DSGA SUPPORT / OPTION 002

Allows to integrate BitifEye´s 2100 Switch System and 3000 DSGA into Valiframe. Is only needed for receiver / sink test set ups.

| MULTI-LANE (MORE THAN 2) SUPPORT / OPTION 003

Allows to use the increased functionality of the new generation test equipment (M8020A, M8190A and M8195A). Is also needed e.g. for some ParBERT test set ups such as for MIPI D_PHY.Use programmable switches to test multiple lanes without manual re-connections. This can significantly reduce test times and required user interaction. This option is only required once per test station, not once per standard.
Not all standards support this option, so please contact BitifEye.

| INTEGRATED BER COUNTER INTERFACE / OPTION 005

For some DUTs proprietary tools exist to control the device (e.g. set it to loopback mode) as well as for reading internal checksum error counters, burst counters, or other indicators. These indicators make it possible to determine whether the receiver was able to receive the data properly. The integration of such proprietary tools into the Test Automation Software can be achieved with the iBerReader software interface. The interface acts as a wrapper for such tools and the definition is given in C# .NET. It follows the interface defined in the different MIPI PHY CTSs (e.g. for M-PHY: Appendix H – Standardized Software Interface for Test Automation), Computer Bus CTSs, or HDMI CTS.

| REMOTE POWER MANAGEMENT SUPPORT / OPTION 008

It is required to power-cycle the DUT several times at certain moments during the receiver tests. This means that the N5990A user needs to sit in front of the controller PC and wait until he is asked by the test automation to power-cycle the DUT. Not only is this task time-consuming, it is error prone. If the user forgets to or does not power-up the DUT properly, the current test will need to be repeated. With N5990A Option 008 or Remote Power Management Support, the number of user interactions and thus the room for errors and potential delays are minimized.
With N5990A Option 008, the user only has to make sure that the DUT is properly connected to a PDU (power distribution unit) or a Keysight power supply once during the very first receiver test and let the test automation power-cycle the DUT when required.
Suppoted PDUs are Koukaam NetIO-230B, Koukaam NetIO-230C, Allnet ALL 4076, Synaccess NP (USA connectors) Keysight Power Supplies (only used with USB tests): E3631A, E363xA, E364xA,N67xx

| USER PROGRAMMING / OPTION 500

The test platform is flexible and open. This means you can integrate your own C# code or program your own test sequences with the user programming option.
You can also easily integrate software dynamic link libraries (dlls) implemented in graphical environments such as LabView or VEE.
With this feature the user can implement custom calibration and test procedures as well as instrument drivers. Custom procedures can then be run from the ValiFrame user interface and access custom instruments. It is also possible to extend and modify existing procedures. We provide an example VisualStudio solution and documentation about the relevant ValiFrame classes to get you started with this.
This option is not required to programmatically control ValiFrame from another program through the ValiFrameRemote interface. That functionality is already included in every ValiFrame base license.