MapBoards Pro Description

When MBP starts the length, width, thickness and material type are detemined for each component body in the model. The list of all material and thickness pairings are presented allow the targeted board dimensions to be specified. The initial default dimensions filled in will be a size large enough to fit one component, the largest component for each material type. You will needs to updated these dimensions before you run MBP the first time on a model to match the size of the material you plan to use. The dimensions will persist and be included the next time you run MBP on this model. Selecting Save as Default on the option tab will save the dimensions entered for each material type and thickness pairing and used as defaults by MBP with other models. In this example the dimensions for materials Walnut and Mahogany are large enough to contain all components of their material type.

By default all component bodies are included in the created map. Alternatively you can select which component bodies that you want included in the map.  By selecting a component occurrence or a component body from the browser tree or a body in the design view a second selection table is displayed. The selected component bodies are displayed in this table. This example shows two components selected of type Walnut allowing their quantities and grain direction to be changed while still allowing the entire model to be included in the created map.

A flat pattern of the created map can be exported as a DXF or SVG file with a number of options including kerf thickness.  The DXF file exported is layered as viewed from the top and will include perimeter, cutouts, insets, and labels.  Inset layer names will describe either a depth or depth range. The same view is created with an SVG file export with layers represented as lines with selectable colors and adjustable thicknesses.

You can perform the export as part of the map creation in one step or produce a map first then export the flat pattern with tasks from the map object context menu in the browser tree. Since you can manually rearrange the components on the resulting map you may prefer the stepwise process of creating the map, rearrange the map then export the flat pattern.

The Export DXF and Export SVG tasks provide the same options for export as MBP using the corresponding Map Type options and produces the same results.  The Label Map task will relabel components that have been moved within or between boards. The Label Map options allow you to "play around" with the font type, font size and display units. Advantages of exporting or labeling after the creation of a map:

• allows components to be manually rearranged before export
• can elect to export one board at a time, useful on large models
• label as a separate step, also useful on large models

Save Cutlist is an option available in the options tab when creating a map. The resulting CSV file contains a list of all components included in the map with dimensions and material type. It is sorted by board number, width and length. It can be imported into a spreadsheet program and formated for viewing. You can also easily print labels by importing the CSV file into Avery's online Design and Print utility.  By creating a free account you can save your custom label printing template for reuse. Avery 5160 is good choice for label printing. This video will provide guidance.  Avery Data and Mail Merge

MBP can create a Map Report instead of a Map with bodies by selecting Report as a MapType in the Options tab. You can also create a Map Report after creating a map with bodies. You do so by right clicking on the map object in the browser tree and selecting Map Report. It will generate informative HTML report on the map and components in the model. The resulting HTML can be saved as a PDF or printed. View details on this customizable report here.  Map Report

In order to create a relocatable copy of a body found in a linked component or assembly, without breaking the link, a local copy of that linked component is made from its datafile. The following are best practices when using linked components and assemblies with MBP in order to avoid errors.