Prepare DIATwin_Machine_Pilot_Enterprise_1.6.0.msi and install it as follows.
Double-click the installer. If a permission prompt appears, allow the installer to run.
Wait for the installation wizard, then read and accept the software license terms.
Check the installation options. You can use the defaults. To change the installation scope or path, select Advanced and complete the settings.
Confirm the settings and start installation.
Wait for installation to finish, check that no errors are shown, then close the wizard.
2. Licensing and First Launch
Launch MachinePilot and choose the option matching your license. After activation, install the official equipment data.
Type
Required information
First use
Offline
License Text
Activate using the supplied license. Connect to the network first if online binding is required.
Floating
License Key
Maintain access to the license service in use.
2.1 Launch MachinePilot
After installation, select Launch and click Finish, or open the MachinePilot desktop shortcut.
On the license type screen, select Offline or Floating according to the license supplied.
Launch MachinePilot after installation (click to enlarge)
2.2 Offline: Select the License Type
Select I have an offline license and click Next >.
Offline license entry (click to enlarge)
2.3 Offline: Enter the License Text
Paste the complete license text into License text.
If your environment requires a proxy, enter the supplied Proxy Host and Port.
Click Validate and, after activation, continue with dtpkg installation below.
License text field and Validate button (click to enlarge)
2.4 Floating: Select the License Type
Select I have a floating license and click Next >.
Floating license entry (click to enlarge)
2.5 Floating: Enter the License Key
Enter the supplied License key.
Enter the required connection information for your license service and network.
Click Validate and continue with dtpkg installation after validation.
This section assumes that the license information is correct and activation succeeds. For license issues, see Troubleshooting .
License key screen; license value redacted (click to enlarge)
3. Install Models and Example Data (dtpkg)
This procedure assumes a first installation with no older equipment data at the selected location . After activation, the system checks equipment data using the existing settings. Follow the screens below to install the supplied official .dtpkg.
3.1 Set the Data Location
In Set Up Equipment Data check the locations for equipment data and the Workspace.
To change the location, click Browse… and select a folder.
Click Continue . The system creates the following folders at this location: AssetLibrary/PackageStore and AssetLibrary/Workspace.
Equipment data location and Continue (click to enlarge)
3.2 Select and Install the dtpkg
In Equipment Data Required Click Select Equipment Data File….
Select the matching .dtpkg file supplied with this software version.
Follow the remaining screens. Wait for the data checks and installation to finish before opening assets.
Select the official equipment data file (click to enlarge)
3.3 Open and Verify
Open Electronic Component → Open Project.
Select the appropriate Group and check that the model list appears.
Select a supplied asset and click OK to open it. Switch to Product to begin creating the APEX board.
Check: MachinePilot launches, equipment data is installed, and the required assets can be opened.
Open Component Project list after equipment data installation (click to enlarge)
Use the APEX example to create a board, import the BOM and link components, then complete Gerber/PNP annotations, the 3D board shape, mount points and product saving.
Before starting: Activate MachinePilot and install the official equipment data. Check that the supplied components can be found in Internal Library.
After extracting the download, keep the QuickStart_Materials folder. The same CSV is used for both BOM and PNP import.
1. Create a Board and Import the BOM
BOM CSV fields and empty values
Use CSV, UTF-8 without BOM, CRLF and comma delimiters. Designator and Part Number require column mapping; Description is optional. Missing row values do not always reject the entire file.
Compare source rows, skipped rows, imported rows and unlinked rows separately. Matched entries are blue; unmatched entries are black. Verify part numbers and actual assets as well as color. Preparing Library mappings reduces unmatched entries, but is not required to retain every BOM row.
Other encodings, direct XLS/XLSX import, case/whitespace matching, embedded comma parsing and repeated imports into an existing BOM are not fully confirmed.
In Create Root, enter a product name, such as APEX_QuickStart and click OK.
Check that Workpart, BOM and Mountpoint appear in the left tree.
New Board / Create Root reference; use APEX_QuickStart for this example (click to enlarge)
1.2 Create a User Component Library
Under the board, select BOM (BOM Behavior) .
In Electronic Component List on the right, click +CREATE.
Enter HelloLibrary and click CREATE. Check that Library switches to the new library.
Create a user library; the screenshot shows TESTLibrary, while this procedure uses HelloLibrary (click to enlarge)
1.3 Import the APEX BOM
At the bottom right, click IMPORT BOM and select QuickStart_Materials/APEX OI Data.csv . Map the source fields as shown below, then complete the import.
Target field
CSV source field
Designator
RefDes
Part Number/PartNo.
PartNo
Description
Description
The list is black at this stage, indicating that the items are not yet linked to HelloLibrary. Link the components next.
2. Match the Supplied Components
2.1 Find a Matching Shape and Assign the Part Number
Select an unlinked BOM item and open Component Library Search.
Switch to Internal Library . Use the CSV Description to check the shape, dimensions and leads, then select the matching supplied component.
On the asset card, click ADD TO HelloLibrary and in Part No. enter the PartNo from that CSV row and finish adding the asset.
Return to HelloLibrary, find the asset by part number and click LINK . Return to the BOM to verify the link.
Repeat for the remaining part numbers. Even when multiple items share a part number, verify the link for each Designator.
Check: Each BOM row has the correct part number, Description and asset, with the expected Linked/Unlinked status.
ADD TO and Part No. field reference; use HelloLibrary and the APEX CSV part numbers (click to enlarge)
3. Import Gerber and Digital Annotation Data
PNP import and position checks
APEX practice data limitation: RY1, RY2, C170 and C174 in APEX OI Data.csv have blank Rz values and do not yet meet PNP requirements. Determine the correct orientations, fill a working copy and validate it; do not assume zero. The file illustrates mappings but is not a verified ready-to-import PNP template.
PNP coordinates are interpreted as mm without inch conversion; Designator, X, Y and RotationZ require values.
Right-click the board root and select Create Link….
Create Top Layer (Gerber) and check that the tree contains Link_GerberTop.
Then create 3D Shape and check that the tree contains Link_Shape.
Reference for creating Gerber and 3D Shape links (click to enlarge)
3.2 Import the Top Gerber Layers
Right-click Link_GerberTop and select Import Gerber Shape…. Open QuickStart_Materials/Gerber_APEX2024. Hold Ctrl to select and open these four top-layer files:
APEX2024 Layer 1 stencil_ 2mil.gbr
APEX2024 Layer 1.gbr
APEX2024 Layer1 mask.gbr
APEX2024 Layer1 silk.gbr
Check the four layers in Link Feature Data. Use Focus Viewport to view the board outline.
APEX top Gerber layers (click to enlarge)
3.3 Create Annotations in a Batch with Import PNP
Select Link_GerberTop and use Import PNP.
Select the same QuickStart_Materials/APEX OI Data.csv.
Map the fields as shown below, review the import preview and complete the batch import.
Check that Designators match the BOM. Verify their positions and rotations on the Gerber.
4. Generate the Board Shape and Adjust Layer Height
4.1 Measure the Board Outline
Click Measure and select two diagonally opposite corners of the board outline. Check the X dimension of 304.8 mm and the Y dimension of 165 mm . If a measurement is negative, use its absolute length.
Diagonal measurement and axis dimensions of the APEX outline (click to enlarge)
4.2 Generate the 3D Board Shape
Select Link_Shape → ParametricShape . Check that Shape Type is Box, enter the dimensions below, then click GENERATE.
Axis
Parameter
Value (mm)
X / Long side
Length
304.8
Y / Short side
Width
165
Z / Board thickness
Height
3.0
Check that the board shape has been generated and its dimensions match the Gerber outline.
Parametric Shape: Length 304.8, Width 165, Height 3.0 mm (click to enlarge)
4.3 Move the Gerber to the Top of the Board
Right-click Link_GerberTop and open Move Link….
This example starts at Z = 0. Check Coord Mode=Offset.
Enter the board thickness as X=0, Y=0, Z=3.0 mm , keep the rotations at 0, then click OK.
Check that the Gerber layers sit on the top surface of the board.
PS: To avoid flickering where the layers overlap the board surface, enter 3.001 mm . Use this instead of 3.0 mm in this step. If you have already moved by 3.0 mm, add only 0.001 mm to the Offset; do not add another 3.001 mm.
Move Link_GerberTop reference; the screenshot shows the optional 3.001 mm offset. Use 3.0 mm for the main procedure (click to enlarge)
5. Mount Points and Product Dimensions
5.1 Create Mount Points Automatically
Right-click the board’s Mountpoint and select Create Mount Point. Check the eight automatically generated corner points and their positions.
Create Mount Point on Mountpoint (click to enlarge)
5.2 Set Workpart Dimensions
Select the board's Workpart and enter the dimensions of the board shape you just created:
Field
Direction
Value (mm)
Width
X
304.8
Length
Y
165
Thickness
Z
3.0
These are Workpart dimensions, not Workspace settings. The 0.001 mm Gerber display offset does not change the modeled board thickness.
Workpart dimension fields; enter the values from the table for this example (click to enlarge)
6. Save and Reopen for Verification
6.1 Save to Library
Select Product → Save to Library to open the save dialog.
Check the current product, Name (for example, APEX_QuickStart), version and save location.
Under Group membership, select ProductCatalog and click +Add and check that the group appears in the table.
Use Capture from 3D view to update the preview, then click OK to save.
After saving, use Product → Open Project to find and reopen this product in the appropriate Group.
Reference for saving the product and adding it to ProductCatalog (click to enlarge)
6.2 Completion Checks
BOM Designators, part numbers and asset links are correct.
The imported annotation positions and rotations match the Gerber.
The board is 304.8 × 165 × 3.0 mm, and the corresponding Workpart dimensions have been entered.
Eight mount points have been created, and the data is retained after reopening.
Continue with machine configuration, simulation and recipe generation.
Use Demo_Single_Board to auto-configure the machine, run a simulation, review Cycle Time and export a recipe. Once familiar with the example, repeat with your own board.
1. Load the Example Board and Machine
Make sure you have installed the official dtpkg package. Use the supplied Demo_Single_Board with the corresponding machine, tools and feeders.
Open Recipe → Create Project and select the appropriate installed machine and Demo_Single_Board.
Check the product name, then click Next to proceed to product assembly.
Machine and board selection in Recipe (click to enlarge)
2. Complete Product Assembly
Follow Product Assembly in that order to set Select Position and Adjust Orientation.
Set Select Attachment Point then use Adjust Conveyor Width to match the board width.
In the 3D view, check the board position, orientation and conveyor width before proceeding to configuration.
Product position, orientation, mount points and conveyor width (click to enlarge)
3. Auto-configure Tools and Feeders
Check the availability, enabled status and lock status of feeder and tool slots.
Click Auto Configure and wait for the calculation to finish.
In Auto Configure Result Review Feeder and Tool recommendations, then click Import . Follow the prompts and wait for accessory installation to finish.
Check that configuration positions show the installed status, all required accessories are present, and Next is available. Continue to the flow and simulation.
Auto Configure entry (click to enlarge) Review and import Auto Configure results (click to enlarge)
4. Run the Simulation and Review Cycle Time
Open Run Simulation . Wait for initialization, then click Start.
Observe tool pickup, travel and insertion. Use Check Collision and the status bar to check the results.
Read and record this run's Cycle Time(C.T.) . Keep the product and configuration conditions as a baseline for comparison.
The displayed time belongs to this simulation run. Other products may produce different results.
Run Simulation and Cycle Time (click to enlarge)
5. Adjust the Sequence and Simulate Again
Return to Flow Editor and check Designator, Feeder Slot, Tool Slot.
Adjust the following as required for the exercise: Pick Seq. and Insert Seq..
Run again: Path Planning/Run Simulation to recalculate using the updated flow.
Click Start . Observe the motion and record the new C.T. Keep the same product and configuration conditions when comparing the results.
Pickup and insertion sequences in Flow Editor (click to enlarge) Simulate again and review timing after adjustments (click to enlarge)
6. Generate and Export the Recipe
In Run Simulation Click Export DB.
In the export dialog, check the coordinate reference, processing mode and product shape information.
Click Browse Select an output folder and enter a .db file name, then save.
Return to the export dialog and complete Export . Check the exported recipe file in the destination folder.
Export DB settings (click to enlarge) Set the recipe file name and location (click to enlarge)
7. Practice with Your Own Board
After completing the example, create a new Recipe Project using the product saved in Step 2. Repeat assembly, auto-configuration, simulation, C.T. review and export. Check the new product name and configuration, and generate a new recipe file.