Exporting EAGLE data to ASENT Last revised: 8/15/2005

Exporting EAGLE Data To ASENT Sometimes when doing upgrades or redesigns there may be some legacy data that exists in the LSAR database that is not currently in ASENT. This data can be passed from EAGLE to ASENT to populate the product tree structure and other data, giving the design analysis team a huge head start in their analysis effort.

Exporting EAGLE Data To ASENT Passing data from EAGLE to ASENT is easily accomplished with a quick, two-step approach: 1) In EAGLE create a fullfile for the End Item of interest, and 2) Use ASENT’s LSAR Interface to import the EAGLE fullfile.

Exporting EAGLE Data To ASENT Invoke EAGLE and select the Administration discipline from the EAGLE Navigator. Double-click on the ‘Create Fullfile’ function.

From the Export Fullfile window, use the Output File Browse button to select the file name of the fullfile you are about to create. Make sure that the Output Type is set to B and click on the Modify Fullfile Settings button. Exporting EAGLE Data To ASENT

Click on the ‘Only LSAR Tables’ tab on the Modify Fullfile Settings window and click on the OK button.

Exporting EAGLE Data To ASENT Click on the Execute icon on the EAGLE toolbar, and when asked whether or not to overwrite the existing report and message files, click on the Yes buttons.

Exporting EAGLE Data To ASENT This is an example of the status screen that is displayed as the EAGLE fullfile is being created.

Exporting EAGLE Data To ASENT Here is an example of the status window once the fullfile has been created in EAGLE.

Once the EAGLE fullfile has been created, then it is brought into ASENT using ASENT’s LSAR Interface, Import option. Refer to the ASENT LSAR Import tutorial for more details. Exporting EAGLE Data To ASENT

LSAR DB Data Exchange RAMS DB

ASENT, EAGLE, and AIMSS are trademarks of Raytheon Company. Microsoft and SQL Server are registered trademarks of Microsoft Corporation.