• 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. Allegro X Capture CIS
  3. Allegro X Platinum 25.1 read only issue with Library.OLB...

Stats

  • State Not Answered
  • Replies 3
  • Subscribers 48
  • Views 719
  • Members are here 0
More Content

Allegro X Platinum 25.1 read only issue with Library.OLB when opening a project

AL202510019453
AL202510019453 3 months ago

Hi to all,

My situation is the following: when opening a project, some libraries I used components from in that project go in lock mode (the .OLBlck file is created on the library path). I don't have any library added to the project. This happens just with specific libraries, not all the ones I'm using components from. And none of the .OLBs are open. Another weird thing is that, if a colleague of mine opens the SAME PROJECT, the library doesn't get locked. I searched around for some time but I cannot find any reason why. Could someone shed some light there?

Thanks in advance.

BR

Alberto

  • Cancel
  • Sign in to reply
Parents
  • Jeet
    0 Jeet 3 months ago

    Have you added the library in project by 'Library > Add file' in Project manager?
    In general, lock for the olb gets created only when we open the project and the library file in associated with that project with the help of Library > Add file. However, lock goes away when we close the project. If we add part from that library on the schematic by 'Place > Part' option, lock will not get generated.
    Can you please check the opj file if there is any entry of the library file there or not where the library file is present ?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • AL202510019453
    0 AL202510019453 3 months ago in reply to Jeet

    Hi Jeet,

    Firstly, thanks for the quick answer!

    Regarding the problem, there is no library file added or present in the project manager.

    I also forgot to mention that the lck file doesn't go away after closing the project in orcad. Only when I entirely close the program.

    BR

    Alberto

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Jeet
    0 Jeet 3 months ago in reply to AL202510019453

    Alberto,

    Can you check for non-hierarchical parts present in your schematic design with 'Implementation Type' as 'Schematic View' and set their 'Implementation Type' as 'None' in the library if it is present.

    If the 'Implementation Type' property of a part is set to 'Schematic View', this part is treated like a "hierarchical part". The tool understands that it has some implementation value, and that is why its 'Implementation' value cannot be 'None'. Therefore, when you open the design file (associated with the library in question) or that particular library (.olb), Capture opens the DEVLIB library internally in order to descend to these parts and creates an olblck file, leading to this error.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Jeet
    0 Jeet 3 months ago in reply to AL202510019453

    Alberto,

    Can you check for non-hierarchical parts present in your schematic design with 'Implementation Type' as 'Schematic View' and set their 'Implementation Type' as 'None' in the library if it is present.

    If the 'Implementation Type' property of a part is set to 'Schematic View', this part is treated like a "hierarchical part". The tool understands that it has some implementation value, and that is why its 'Implementation' value cannot be 'None'. Therefore, when you open the design file (associated with the library in question) or that particular library (.olb), Capture opens the DEVLIB library internally in order to descend to these parts and creates an olblck file, leading to this error.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
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.

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

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