How to Export ODB++ Files from Cadence Allegro: Complete Guide

Exporting ODB++ files from Cadence Allegro requires the ODB++ Inside translator, a separate utility that integrates with Allegro to generate manufacturing-ready output. Unlike some PCB tools where ODB++ export is built directly into the software, Allegro uses this external translator approach, which gives you more control over the conversion process but adds an extra installation step that catches many engineers off guard.

After setting up ODB++ Inside across multiple Allegro installations and troubleshooting various export issues, I have found that understanding the translator architecture and configuration options prevents most problems before they occur. This guide covers everything from installation through advanced export options.

Understanding ODB++ Inside for Cadence Allegro

ODB++ Inside is a free translator developed by Siemens (formerly Mentor Graphics Valor division) that converts Cadence Allegro board files (.brd) to ODB++ format. The translator integrates directly into Allegro’s File menu, making exports straightforward once properly installed.

What ODB++ Inside Includes

Component	Function
BRD2ODB Translator	Converts Allegro .brd files to ODB++
ODB++ Viewer	Visual verification of exported data
Configuration Tools	Parameter customization
Command Line Interface	Batch processing support

The translator outputs ODB++ Version 7 or ODB++Design Version 8, both of which are compatible with modern CAM systems including Frontline Genesis and other manufacturing software.

Supported Allegro Versions

Allegro Version	Support Status
Version 11-16.x	Supported
Version 17.x	Supported
Version 23.10+	Native support available
Version 24.10+	Native support available

Recent Allegro versions (23.10 and later) include native ODB++ export capability, but the ODB++ Inside translator remains useful for older installations and provides additional configuration options.

Installing ODB++ Inside for Cadence Allegro

Before you can export ODB++ files, you must install the ODB++ Inside translator on your system.

Download Location

Download ODB++ Inside from the official ODB++ Design website:

Platform	Download Source
Windows 64-bit	odbplusplus.com/design/download
Linux	odbplusplus.com/design/download

The software is free but requires registration on the ODB++ Design website.

Installation Requirements

Requirement	Specification
Operating System	Windows 64-bit or Linux
Allegro Version	Version 11 or later
Admin Rights	Required for installation
Disk Space	Approximately 500MB

Important: Close all Cadence products before installing ODB++ Inside. Both applications use the Microsoft Visual C++ Redistributable package, and conflicts can occur if Allegro is running during installation.

Environment Variables

The installer creates these environment variables automatically:

Variable	Purpose
ALLEGRO_BRD2ODB	Points to ODB++ Inside installation directory
VALOR_DIR	System and configuration files location
VALOR_HOME	User work directory
VALOR_TMP	Temporary files location

On Windows, the installer typically sets ALLEGRO_BRD2ODB to a path like C:\valor\ODB++Inside. Verify this variable exists after installation by checking your system environment variables.

Step-by-Step ODB++ Export from Allegro

With ODB++ Inside properly installed, exporting from Allegro is straightforward.

Accessing the Export Function

Open your design in Cadence Allegro PCB Editor. Navigate to:

File → Export → ODB++ Inside

Or for newer versions:

File → Export → ODB++Design Inside

A dialog appears asking “Extract net impedance averages?” Select No unless you specifically need impedance data for signal integrity analysis.

Specifying File Options and Output Options

The main export dialog presents several configuration fields:

Field	Description	Recommendation
Input Path	Path to Allegro .brd file	Auto-populated from current design
Output Path	Destination for ODB++ output	Choose accessible location
ODB++ Product Model	Name for output folder/archive	Use descriptive project name

The output path should be a directory where you have write permissions. Avoid paths with spaces or non-ASCII characters, as these can cause export failures.

Selecting Export Options

Option	Output Contents	Use Case
Full	Complete fabrication and assembly data	Standard manufacturing submission
FAB	Fabrication data only	Board fabrication without assembly
ASSY	Assembly data only	Assembly house submission
Partial	User-selected layers and data	Custom requirements

For most manufacturing submissions, select Full to include all necessary data. The Partial option allows selective export of specific layers when you need to send only certain information.

Choosing Output Format

Format	Extension	Notes
Uncompressed	folder	Largest size, browsable structure
Tar gzip	.tgz	Preferred by most CAM software
Zip	.zip	Alternative compressed format

Select Tar gzip (.tgz) for best compatibility with CAM systems like Frontline Genesis. This format creates a single compressed file that manufacturers can import directly.

Running the Translation

Click Begin Translation or Next to start the export process. The translator:

1. Extracts data from the Allegro design
2. Converts geometries and netlist information
3. Generates ODB++ structure
4. Compresses output (if selected)
5. Opens ODB++ Viewer for verification

The process typically completes in seconds to minutes depending on design complexity.

Understanding Export Parameters

ODB++ Inside provides numerous parameters for customizing the export. Access these through the “Show more options” checkbox in the export dialog.

Layer Configuration

The translator reads layer information from Allegro’s Artwork Control Form. Before exporting, verify your artwork is properly configured:

Manufacture → Artwork (or Export → Gerber)

Ensure all layers needed for manufacturing appear in the artwork definition. The ODB++ translator uses this information to determine layer stackup and types.

Additional Parameters – Page 1

Parameter	Function	Default
Include outer layers	Controls outer layer export	Yes
Include inner layers	Controls inner layer export	Yes
Include net names	Embeds net name data	Yes
Symbol tolerance	Tolerance for symbol matching	0.1 mils

Additional Parameters – Page 2

Parameter	Function	Default
Remove EDA data	Strips component/package info	No
Round polygon corners	Applies corner rounding	No
Create signal quality layer	Generates SQ layer	No
Suppress unconnected pads	Removes floating pads	No

Configuration Parameters

Parameter	Function
Component outline source	PlaceBound or Assembly geometry
Pin 1 designation	Naming convention for pin identification
Flexible material names	Materials for flex PCB designs

For most exports, the default parameters work correctly. Modify these only when your manufacturer specifies particular requirements.

Verifying ODB++ Output

After export, the ODB++ Viewer opens automatically to display your converted design.

Using ODB++ Viewer

The viewer provides visual verification of exported data:

View	Purpose
Layer view	Inspect individual layers
Stackup	Verify layer order and types
Components	Check component placement
Nets	Validate connectivity data

Spend time reviewing the output in the viewer before sending to manufacturing. Catching errors at this stage prevents costly manufacturing delays.

Verification Checklist

Check	What to Verify
Layer count	Matches original design
Board outline	Correct shape and dimensions
Drill data	All holes present with correct sizes
Component count	All parts included
Net count	Connectivity preserved

Troubleshooting Common Export Issues

Several issues commonly arise during ODB++ export from Allegro.

“ODB++ Inside is not installed” Error

Cause	Solution
Allegro was open during install	Close Allegro, reinstall ODB++ Inside
Missing environment variable	Verify ALLEGRO_BRD2ODB is set
Permission issues	Reinstall with admin rights

“dml_eda-230001-Internal error”

This error typically occurs when net names exist in properties but not in the current netlist:

Cause	Solution
Stale net_short properties	Remove net_short from orphaned features
Reused design without cleanup	Clear net properties before reuse

“gen_fs-2008-Unable to open output file”

Cause	Solution
No write permission	Choose output path with write access
Path contains spaces	Use path without spaces
Non-ASCII characters	Use ASCII-only path names

Incomplete or Missing Layer Data

Cause	Solution
Artwork not configured	Set up Artwork Control Form first
Layer type mismatch	Verify layer types in artwork
Mixed document/copper data	Edit matrix file before translation

Command Line Export

For batch processing or automation, ODB++ Inside supports command line operation.

Basic Command Syntax

brd2odb [parameters] <full path to input brd file>

Common Command Line Parameters

Parameter	Function
-gui	Launch graphical interface
-i <path>	Input design path
-o <path>	Output path
-job <name>	ODB++ product model name
-gz	Create compressed .tgz output
-log <path>	Log file location

Example Command

brd2odb -i “C:\designs\myboard.brd” -o “C:\output” -job myboard -gz

This exports myboard.brd to ODB++ format, creating compressed output named myboard.tgz.

Useful Resources

Official Documentation

Resource	Source
ODB++ Inside User Guide	odbplusplus.com
Installation Guide	odbplusplus.com/design/download
Cadence Community	community.cadence.com

Download Links

Software	Location
ODB++ Inside (Windows 64-bit)	odbplusplus.com/design/download
ODB++ Inside (Linux)	odbplusplus.com/design/download
ODB++ Viewer	Included with ODB++ Inside

Support Resources

Resource	URL
ODB++ Design Support	odbplusplus.com/support
Cadence Community Forums	community.cadence.com
Siemens EDA Support	siemens.com/eda

Frequently Asked Questions

Do I need to install ODB++ Inside separately from Allegro?

Yes, for most Allegro versions prior to 23.10, you must download and install ODB++ Inside as a separate application. The translator is free but requires registration on the ODB++ Design website. Newer Allegro versions (23.10 and later) include native ODB++ export capability, but many users still prefer ODB++ Inside for its additional configuration options and integrated viewer. Always close Allegro before installing to avoid conflicts with shared Visual C++ components.

What is the difference between ODB++ Version 7 and ODB++Design Version 8?

ODB++ Version 7 is the traditional format supported by most CAM systems worldwide. ODB++Design Version 8 is an enhanced version with additional capabilities for modern manufacturing workflows. Both formats are compatible with Frontline Genesis and other major CAM tools. The translator no longer supports the older Version 6 format to ensure manufacturers receive current, fully-featured data. For most manufacturing submissions, either version works correctly.

Why does my export fail with path-related errors?

ODB++ Inside has strict requirements for file paths. The output path must not contain spaces, non-ASCII characters, or exceed 64 characters for entity names. Additionally, you must have write permissions for the output directory. If you encounter “Unable to open output file” errors, try exporting to a simple path like C:\odboutput and ensure you have administrator rights on the system.

Can I export only specific layers instead of the complete design?

Yes, select the Partial export option in the Export Options field. This opens additional dialogs where you can select specific layers to include in the output. You can also use the FAB option to export only fabrication data (no assembly information) or ASSY to export only assembly data. For most manufacturing submissions, use the Full option to include everything needed for both fabrication and assembly.

How do I verify the ODB++ output before sending to manufacturing?

ODB++ Inside includes an integrated ODB++ Viewer that opens automatically after successful export. Use this viewer to inspect layer data, verify component placement, check the board outline, and validate net connectivity. Compare the layer count, component count, and board dimensions against your original design. If you need additional verification, you can import the ODB++ file into CAM software like CAM350 or Frontline InCAM for more detailed DFM analysis.

Editing the Matrix File

The matrix file controls how layers are mapped and ordered in the ODB++ output. In some cases, you may need to edit this file before translation to correct layer assignments.

When to Edit the Matrix File

Situation	Action Required
Copper mixed with document layers	Separate layer types manually
Incorrect layer order	Reorder in matrix editor
Wrong layer polarity	Change positive/negative setting
Missing drill layers	Add drill layer definitions

Matrix File Structure

Column	Description
Layer Name	Name from Allegro artwork
Context	Board or Misc
Type	Signal, Power, Solder Mask, etc.
Polarity	Positive or Negative
Side	Top, Bottom, or Inner

The translator reads layer information from the films_<product_model>.out file generated during extraction. If layers appear mixed or incorrectly typed, edit the matrix before completing the translation.

Accessing the Matrix Editor

Click Edit Matrix in the ODB++ Inside dialog to modify layer assignments. The editor displays all extracted layers and allows you to change their properties. Save changes before proceeding with translation.

ODB++ Export for Specific Manufacturers

Different manufacturers may have specific ODB++ requirements.

MacroFab Requirements

Requirement	Setting
Archive format	Tar gzip (.tgz)
Net impedance	Select “No” when prompted
BOM format	Separate XLSX file required
Drill settings	Auto Tool Select enabled

MacroFab accepts ODB++ directly and uses the embedded component data for assembly. However, Manufacturer Part Numbers (MPNs) must be supplied in a separate spreadsheet since ODB++ does not include this purchasing information.

General Manufacturer Guidelines

Aspect	Recommendation
Archive format	TGZ preferred over ZIP
Naming convention	Use project name and revision
Layer verification	Review in viewer before sending
Documentation	Include fabrication notes

Always confirm specific requirements with your manufacturer before submitting ODB++ files, as some may have particular preferences for export options or additional documentation needs.

Best Practices for ODB++ Export

Following consistent practices ensures reliable exports every time.

Before Export

Configure your Artwork Control Form with all manufacturing layers properly defined. Run DRC to verify design integrity. Ensure no orphaned net properties exist from previous design iterations.

During Export

Use descriptive product model names that identify the project and revision. Select Tar gzip format for best CAM compatibility. Review additional parameters only when manufacturer requirements dictate changes from defaults.

After Export

Verify output in ODB++ Viewer before delivery. Confirm layer count and board dimensions match your design. Archive the ODB++ output alongside your Allegro source files for future reference.

Exporting ODB++ files from Cadence Allegro becomes straightforward once you have ODB++ Inside properly installed and understand the export options. The integrated viewer provides immediate verification, and the compressed output format works directly with virtually all modern CAM systems.