|
||
| We strongly recommend saving project files so your settings and trace data can be restored and reused. | ||
| Description | ||
| Projects are compressed binary files which contain the GoLogic configuration and the open trace, reference, and scope data in a single unit. Projects store each window's position, marker positions, bookmarks, scroll positions, plus the active PlugIns and their configuration. The complete GoLogic session is restored when loading project files. | ||
| Saving projects | ||
Save project files using the Toolbar’s
 button or the "File
> Save Project..." menu command. Project files use the PRJ file extension
(which stands for "PRoJect").The project file saves the active GoLogic session exactly how it appears on screen. If you only want to save the GoLogic configuration with no trace data, simply close all open data before saving the project file. |
||
| Opening projects | ||
Open project files using the Toolbar’s
 button or the "File
> Open Project..." menu command. The menu's "File > Recent Projects" feature
conveniently lists the past eight projects you saved.Opening a project restores the GoLogic setup and all data that was open when the project was saved. All window positions plus the active PlugIns and their configurations are also restored. PlugIns which are not installed are ignored. |
||
| Opening old projects | ||
|
Project files created with v5.00 through v5.20
can be loaded into the v5.21 or later software. Simply use the "File > Open
Project..." menu command to load the file. Files created with v4.34 and earlier cannot be loaded into the v5.21 or later software. The v5.20 software was the last version which offered "File > Import > Old 4.34 files" menu commands. If you have older v4.34 files which you need, install v5.19 or v5.20 from our "Downloads > Old Products" page. Import and resave the files using the new software. You may then upgrade to v5.21 or later once all project files are converted to the modern format. |
||
| Closing projects | ||
| Close the project using the "File > Close > Project..." menu command. Closing a project closes all open data and resets all setup parameters to their default values. | ||
| Importing files | ||
| Import Trace from Project | ||
| Use the "File > Import > Trace from Project file..." menu command to import trace data from saved project files into the active project. The data can be imported to the Trace area or the Reference area. See Chapter 9 - Measurements chapter for details on using the Trace and Reference data areas. | ||
| Import Verilog VCD | ||
| Value Change Dump (VCD) files can be imported as Trace or Reference data using the "File > Import > Verilog VCD" menu command. These files are produced by simulators, and can be compared against the trace data actually captured by the GoLogic. | ||
| Import SDK Trace | ||
| The "File > Import > SDK trace file..." menu command imports a binary trace file produced by the GoLogicSDK "file save trace" command. This import feature allows SDK programmers to view trace data captured from their custom software using NCI's advanced features such as the WaveForm window. | ||
| Exporting files | ||
| Export Numeric to TXT | ||
The "File > Export > Numeric to text file..."
menu command saves the captured trace data to an ASCII text file. The text file
contents matches the appearance of the Numeric window. The Numeric
window options also affect the text file appearance. Therefore, you should
first edit and arrange the columns as desired before exporting the TXT file...  |
||
|
Finally, the text file export can be automated with each trace capture using the "Options > System options..." menu command. See Chapter 11 - Options chapter for details. |
||
| Export Numeric to CSV | ||
| The "File > Export > Numeric to CSV file..." menu command saves the captured trace data to an Comma Separated Value ASCII text file. The CSV file contents matches the appearance of the Numeric window. The Numeric window options also affect the CSV file appearance. Therefore, you should first arrange the columns as desired before exporting the TXT file. Finally, the CSV file export can be automated with each trace capture using the "Options > System options..." menu command. See Chapter 11 - Options chapter for details. | ||
| Export PlugIn | ||
| The "File > Export > PlugIn to text file..." menu command saves the contents of the topmost PlugIn to an ASCII text file. The text file contents matches the appearance of the topmost PlugIn window. Note: This feature is only available for text-based plugins. Graphics-based plugins such as NCI's FFT cannot be exported to text files. | ||
| Verilog VCD | ||
| Trace data can be exported to an ASCII Value Change Dump (VCD) file using the "File > Export > Trace to Verilog VCD text file..." menu command. This file can then be loaded into other software such as a VCD viewer. | ||
| SDK Setup | ||
| The "File > Export> SDK setup file..." menu command exports the active logic analyzer setup values to an ASCII text file. This file can then be loaded by an SDK program using the "file open setup" command. This allows SDK programmers to test and debug the triggering and trace capture using the GoLogic software, then load the setup into their custom program to capture and analyze the trace data. | ||
| Copyright and trademark information | ||
| Contents |