• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. Problems implementing master capture.ini

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 169
  • Views 16958
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems implementing master capture.ini

scottm7
scottm7 over 10 years ago

I'm running Allegro Design Entry CIS v16.6-S039 and having problems implementing a master capture.ini file.  I downloaded the CIS admin tool and used SetMasterIniPath.exe.  I've verified that this added a registry key to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cadence Design Systems\MasterSettingsFile.  Note that this is a different location than in the documentation which specifies HKEY_LOCAL_MACHINE\SOFTWARE\Cadence Design Systems\MasterSettingsFile which I've also manually entered into the registry.

My master capture.ini file currently only has a single entry while I experiment as seen below:

[Part Management]
Configuration File=J:\Configuration_Files\CIP-E V5.0 CIS DB.DBC

I expect this entry to replace the existing entry in my capture.ini file located at C:\Users\<username>\AppData\Roaming\SPB_Data\cdssetup\OrCAD_Capture\16.6.0 but it does not.  Can anyone help me debug what is wrong?

  • Cancel
  • steve
    steve over 10 years ago
    There is a slightly better app that will help you with this. It's available on the OrCAD Capture Marketplace and is a free app called Capture INI Manager. Might be a better tool to help you. http://www.orcadmarketplace.com/t60p-topic/ProductDetails/tabid/93/ProductID/20/Default.aspx
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • scottm7
    scottm7 over 10 years ago

    Thanks Steve.  I'll try that.  This brings up a different issue though.  I have users in multiple locations around the world.  To eliminate performance problems, I'm implementing database replication.  The main reason I wanted to use a master capture.ini file was to easily reconfigure all of these users to use their local replication server just by clicking on a batch file that would change the registry key to point to the correct mater capture.ini file.  Is there any way to automate loading and configuring this tcl script into Capture or will it have to be done manually on each users PC?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • B Bruekers
    B Bruekers over 10 years ago

    With the TCL based master ini sourcing you do not need to do anything in the registry. 

    You need to add an enviroment variable to the system, "CDS_SITE"  and the value should point to the (network) directory where the TCL files are located. 

    This document describes how to do it:

    http://www.nordcad.dk/download/Teknik/e-service/138/capture_165_inimanagement_us.pdf

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Wimmer
    Wimmer over 10 years ago

    Hi,

    I would say the best way to get the users setup to read the tcl file is to place it in
    C:\Users\<username>\AppData\Roaming\SPB_Data\cdssetup\OrCAD_Capture\16.6.0\tclscripts\capAutoLoad
    this will make capture load the TCL at startup.

    We use the following to make sure that the capture.ini file is only overwritten if it is placed in one of the default location so that users can setup test env. with capture.exe -i <somepath to test capture.ini>

    if { [info commands COrCapIniLoader_loadINI] !=  "COrCapIniLoader_loadINI" } {
    puts "The current version of capIniMgr works with Orcad Capture Version 16.5-s036 or higher for 16.5 release and 16.6-s006 or higher for 16.6 release"
    } else {
        package require capIniMgr
        
        set lcdsroot1 $::env(CDSROOT)
        append lcdsroot1 {\tools\capture\capture.ini}
        
        set lcdsroot2 $::env(USERPROFILE)
        append lcdsroot2 {\cdssetup\OrCAD_Capture\16.6.0\Capture.ini}
        
        set lcdsroot3 $::env(HOME)
        append lcdsroot3 {\cdssetup\OrCAD_Capture\16.6.0\Capture.ini}
        
        set lCurrentIni [GetIniPath]
        regsub -all {/} $lCurrentIni {\\} lCurrentIni
        
        if { ([string equal -nocase $lcdsroot1 $lCurrentIni] == 1) || ([string equal -nocase $lcdsroot2 $lCurrentIni] == 1) || ([string equal -nocase $lcdsroot3 $lCurrentIni] == 1) } {
        set lcdssite1 $::env(CDS_SITE)
        append lcdssite1 {\OrCAD_Capture\master_capture.ini}
        capIniLoad $lcdssite1
        }
    }

    We normally place the controlling capture_master.ini and the tcl on the shared cds_site, so it only reads from one place and there for is easy to manage.

    but if you would like it locally you could place it some were locally.

    e.g.

    change

    set lcdssite1 $::env(CDS_SITE)
    append lcdssite1 {\OrCAD_Capture\master_capture.ini}
    to
    set lcdssite1 $::env(USERPROFILE)
    append lcdssite1 {\AppData\Roaming\SPB_Data\cdssetup\OrCAD_Capture\master_capture.ini}
    and place the master_capture.ini in
    %userprofile%\AppData\Roaming\SPB_Data\cdssetup\OrCAD_Capture
    and give it the following content.

    [Part Management]
    Configuration File=J:\Configuration_Files\CIP-E V5.0 CIS DB.DBC

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Wimmer
    Wimmer over 10 years ago

    That is correct, but that is not the latest of our documentation.

    http://www.nordcad.dk/download/Teknik/e-service/138/Capture_IniManagement_EN.pdf

    This version would be the latest and most up to data version.

    With a working download so no need to run a installer.

    But there is a batch file to set CDS_SITE and copy out the files.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information