Stats

State Not Answered
Replies 3
Subscribers 13
Views 1179
Members are here 0

TCL Code to create a series of schematic symbol with different properties

Hai Community,

I want to create a series of schematic symbol with the different properties.

Like I have created one resistor symbol, or I have taken one resistor symbol from the default libraries of OrCAD Capture, and want to place around 200 resistor in the schematic design. (Same symbol)

The catch is each and every schematic symbol (R1 to R200) should have different properties, like if the R1 has PCB Footprint of Example 0805, then r2 should have different property. Not only one property but multiple properties.

Can it be possible using the TCL coding, if possible can anyone share the TCL code for me please.

Regards,

Rohit Rohan

0 Jeet over 1 year ago

Which different properties you are looking for in the schematic symbol apart from PCB Footprint?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RohitRohan over 1 year ago in reply to Jeet

Like for example if Resistor R1 has properties of PCB footprint, Value, Part number and Resistor R2 should have all the properties of R1 along with an additional property of Manufacture details.

Similarly the properties for R3 might differ from R1 and R2.

Is there any way to use TCL coding to be able to create multiple parts of the same symbol at once and also be able to assign different properties to each part.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 CadAP over 1 year ago in reply to RohitRohan

Hi Rohit,

Yes, it is possible to place multiple instances of the same symbol and change all the property values according to your requirements.

I would like to suggest creating a csv file with the header Ref_Des_NUmber, Property Name, Property Value.

Now read ref_des_number from the schematic and change the property value read from the csv.

Hope it helps .
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

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.