Stats

  • Locked Locked
  • Replies 6
  • Subscribers 164
  • Views 15115
  • 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

DE HDL part number not changed

archive

Hi All,

This one is related to a part number problem or I don't understand the behaviour of Design Entry. I attached some of the views of some windows.
 
The problem is about the resistor ( In this case its R125) part number.  I modify the 22 ohm resistor to 40 ohm resistor As I always did in the right way by selecting it from the library ( with the use of part table file). It changes to 40 ohm thats OK. But I realized from the BOM that this 40 ohm resistor part number is not changed although its value and the other attributes are changed. 
Part_number is a KEY property defined in the library.
And when I want to MODIFY or REPLACE this part again it changes but doesn't change its part number.  When I look at the part manager R125 it shows that it has a part number which is correct.
 
The winning value doesn't change.
 
how can I overcome this issue?

Thank you for your helps
AhmetOzsoy


Originally posted in cdnusers.org by AhmetOzsoy
  • archive

    Have you recompiled the design before running the BOM or part manager tool? (Export physical.) That'll do it every time.


    Originally posted in cdnusers.org by vealmic@uk.ibm.com
  • archive

    Yes Ihave tried to EXPORT PHYSICAL and also expand .. everyway I have. But  I couldn't manage to solve. I guess this problem might be an extreme case. I don't know why this happens.
    Thank you all.


    Originally posted in cdnusers.org by AhmetOzsoy
  • archive

    OK, long shot, becasue I don't know how the replace works. Make sure the property you're trying to change is a soft property eg. $LOCATION rather than the hard property LOCATION.

    Two more courses of action 1/ Delete and re-add the correct part.
    2/ Raise an SR !!


    Originally posted in cdnusers.org by vealmic@uk.ibm.com
  • archive

    Thanks for your answers.

    I have opened an SR for this event but actually they don't pay much attention to that case. And I said OK this one may be an extra case just related to me and they closed the case.
     
    Yes you are right I could delete and put a new one but there are more resistors that has the same problem. Actually in the library definition of resistor  there are no other tricks or special things defined.

    Again thank you for your answers.
    Best regards
    Ahmet


    Originally posted in cdnusers.org by AhmetOzsoy
  • archive

    Hi Ahmet,

    If you are not happy with the status of the SR with Cadence then please don't let them close it until you have some sort of resolution. In this case Cadence will almost certainly need a testcase to look at the problem - this is by far the best way for them to give you an accurate answer/solution to your problem.

    One last suggestion - is there an existing pcb layout for this design?

    I ask this because removing the OPF view may cure this - BUT this is not something that is too be done lightly. The PART_NUMBER property is stored on the schematic (schematic value) and in the OPF (Occurence Property File) which is generally used in hierarchial designs. It looks like the OPF is not being updated with the new PART_NUMBER value. If there's no hierarchy specific properties in the design and a pcb is not yet done then removing the OPF may be an option.

    I would try this on a archived copy of the design first to see if this resolves the problem - BUT I'll go back to my first statement here, this is something that Cadence can do for you in an SR of they have a testcase to work from

    Andy


    Originally posted in cdnusers.org by andrewjw
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.