Purpose of this project is to provide a C++17 library for parsing Cadence's OrCAD Capture binary file formats. This library can be linked to other software for reading/modifying?/writing? OrCAD binary files.
See also the complementary project OpenAllegroParser.
The focus lies on schematics (*.DSN
/*.DBK
) and symbol libraries (*.OLB
/*.OBK
), the second file format is just the extension for its corresponding backup file. Backups should be identical, just with a different file extension.
OrCAD allows exporting its designs to XML files which are easy to read and verify the interpretation of bytes in the DSN
/OLB
-files. E.g. enums are stored as a numeric value which should be the same that is used in the binary formats. However, it seems like not all information is stored in the XML.
The following two XSD files provide a good overview of the XML
file structure, types and much more. They can be used as a reference what features are actually stored in the binary file and which we do already parse and which not.
C:\Cadence\SPB_17.4\tools\capture\tclscripts\capDB\dsn.xsd
C:\Cadence\SPB_17.4\tools\capture\tclscripts\capDB\olb.xsd
- Working on parsing library symbols.
- Improving test coverage.
# Set path to vcpkg
VCPKG_DIR=../vcpkg
# Build
cmake -B build -S . -DCMAKE_TOOLCHAIN_FILE=$VCPKG_DIR/scripts/buildsystems/vcpkg.cmake
cmake --build build
- Compiler with C++17 Support
- CMake >= 2.8.12
- Boost - Program Options
- compoundfilereader
- Magic Enum
- Nameof
./cli/OpenOrCadParser-cli --help
Allowed options:
-h [ --help ] produce help message
-t [ --print_tree ] print container tree
-e [ --extract ] extract binary files from CFBF container
-i [ --input ] arg input file to parse
-o [ --output ] arg output path (required iff extract is set)
./cli/OpenOrCadParser-cli --input file.DSN --extract --output out/
./cli/OpenOrCadParser-cli --input file.DSN --print_tree
orlib2ki (C based OrCAD XML Library to KiCad Converter)
pyorlib2ki (Python based OrCAD XML Library to KiCad Converter)
There are different ways to help this project forward. Some are
- provide test files (manually created or automated via Tcl/Tk),
- help reverse engineering/documenting the file format, or
- implement some unit tests.
In case you don't have access to OrCAD you can get
- OrCAD Viewer free of charge,
- OrCAD Trial with all its functionality for a trial period of 30 days or
- OrCAD Academic Program with all functionality for one semester.
What about OrCAD Lite? It was was replaced with OrCAD Viewer/Trial [1].