Applied Parameters: ShowDialog=True
This command is used to access the New Project dialog. The dialog provides a powerful, yet intuitive interface, that caters for the creation of any of the project types supported by Altium NEXUS. Every design created in Altium NEXUS starts with a project file that stores project level settings, such as links to each of the design documents within that project. As well as creating the new project file on the hard drive, the dialog supports adding the new project to version control, or creating it as a managed project.
This command is accessed from any editor by choosing the File » New » Project command, from the main menus.
After launching the command, the New Project dialog will appear. Use the dialog to quickly create a new project, from the following project types supported by the software:
- PCB project (*.PrjPcb) - the set of design documents required to manufacture a printed circuit board.
The electronic circuit is captured as a schematic, built up from libraries of component symbols which are placed and wired together. The design is transferred to the PCB editor where each component is instantiated as a footprint (pattern) and the circuit wiring becomes point-to-point connection lines. A shape for the final PCB is defined, along with the physical layers the board will include. Design rules specify the layout requirements, such as routing widths and clearance. The components are positioned within the board shape and the connection lines are then replaced by routing, either manually or automatically. When the design is complete, standard format output files are generated which can be used to fabricate the blank board, configure an assembly machine, and so on.
- FPGA project (*.PrjFpg) - the set of design documents that can be processed to program a Field Programmable Gate Array.
The design is captured using schematics and/or HDL code (VHDL or Verilog). Constraint files are added to the project to specify design requirements such as the target device, internal net-to-device pin mapping, net frequency requirements, clock pin allocations, and so on. Design synthesis translates the source data into a low-level gate form, in a standard file format known as EDIF. Device vendor tools then process the EDIF data and attempt to place and route the design in such a way that it will fit in the specified target device, producing a device program file if successful. The design can then be implemented in the target device fitted to a suitable development board and the design can be tested.
- Core project (*.PrjCor) - the set of design documents required to produce an EDIF representation (model) of a functional component that can be implemented in an FPGA.
The design is captured using schematics and/or HDL code (VHDL or Verilog). Constraint files are added to the project to specify the supported target device(s). Design synthesis translates the source data into a low-level gate form, in a standard file format known as EDIF. A component symbol is drawn to represent the component on a schematic sheet, which then references its EDIF description.
- Embedded project (*.PrjEmb) - the set of design documents required to produce a software application that can be embedded with its executing processor in an electronic product.
The source of the design is captured in C and/or assembly language. When coding is complete, all source files are compiled into assembly language. The assembler then converts them into machine language (object code). The object files are then linked together and mapped into the specified memory space, producing a single, target-ready output file.
- Integrated Library package (*.LibPkg) - the set of design documents required to produce an integrated library.
Schematic symbols are drawn in a library editor, and model references defined. Referenced models can include PCB footprints, circuit simulation models, signal integrity models and three-dimensional mechanical models. Files that contain the models are added to the Integrated Library Package (*.LibPkg), or search paths are defined to identify their location. The source schematic symbol libraries and required models are then compiled into a single file, referred to as an Integrated Library.
- Script project (*.PrjScr) - the set of design documents that store one or more Altium NEXUS scripts.
A set of instructions that are interpreted whenever a script is executed in Altium NEXUS. The scripts are written and debugged in the same environment. There are two types of scripts - script units and script forms. A Script unit can use the Application Programming Interface (API) to modify design objects on a design document. A script form hosts controls, as well as using the API to a provide script dialog that act on design documents open in Altium NEXUS.
You can either create a shell project with no added documents (select the <Default> entry in the Project Templates region), or, where available, choose an existing, defined template. The latter are found in the specified Template Location. This is the location defined on the Data Management - Templates page of the Preferences dialog (\Users\Public\Documents\Altium\AD<VersionNumber>\Templates for a default installation).
Configure where, and under what name, the new project is to be created. This can be:
- In a folder on a local or network drive.
- In your version control system - within a nominated repository and folder therein - with a working copy in your preferred location.
- As a Managed Project - within a nominated repository and folder therein - with a working copy in your preferred location. A Managed Project is one that is stored in the version control system built into your Altium Vault.
With all options for the new project defined as required, click OK. On creation, the project will be opened in the Projects panel. If you are creating a VCS-based or Managed Project, the project (and associated source files if applicable) will be added to the specified folder within the target Design Repository, then checked out to the local working folder. Note that at this stage, the project is added to the Design Repository, but still needs to be fully commited, as indicated by the blue cross(es) in the VCS Status column of the panel.
- The default location for new projects (drive-based and checked out working copy) is based on the entry for the Document Path, on the System - Default Locations page of the Preferences dialog. The default Document Path is \Users\Public\Documents\Altium. A sub-folder, Projects, is added to this defined path, giving a full default location of \Users\Public\Documents\Altium\Projects. Note that if you determine your own location, that location will be remembered the next time you access the dialog.
- If you have not yet created a Design Repository, or are currently not connected to an existing one, click the Manage Repositories button. This gives access to the Data Management - Design Repositories page of the Preferences dialog, from where you can create/connect to a repository as required.
- Managed Projects is a feature of an Altium Vault installation.