TechNote mg529885: Borders Quick Start has a video on borders.ini that shows how to update border properties.
↧
Re: how to edit the border Property in Dxdesigner ??
↧
Wire and Terminal Weights
How can wire and terminal weights be handled in Capital Harness XC & Capital Library? What are the Units of Measure?
↧
↧
Re: Wire and Terminal Weights
Weights are set in Capital Library within the Extra tab of a component in the field Weight.
There are no "Units of Measure" assigned. Each company will determine what the units are (e.g. grams or ounces) and then simply enter a number.
When you run a report, you then take the number reported to mean XXX grams or XXX ounces.
Default reports are found under the Tools menu. You can modify those available.
If you are running version 2014.1 then you can use the Report Builder to create your own report.
Details about modifying default reports or creating your own can be found within the help system or the user guides found within the following directory:
C:\MentorGraphics\Capital\docs\pdfdocs
Regards,
Pat
↧
Re: What exactly does the demonstration mode in PADS Layout limit? (PADS 9.5)
Christian Cziezerski:
I suppose demonstration mode means I cannot use any of the following functions:
- cannot EDIT or NEW in the library (however, right-click an object and 'Save to Library' seems to work)
Not quite - there is more capability, when used in the right order.
In Logic & Layout, you can harvest any Decal/Part to the Library, from a large design, as you say.
( You can also harvest a cluster, if you want to, by delete of other items until inside the demonstration mode limits.)
If you then use File New to remove the over-size design, then you now can Edit and New in the library, and change that Saved item.
The only step you need the key for, is to replace the modified decal into a larger design.
You can check the decal, in a smaller design.
In Logic & Layout, you can also Develop and Test Scripts, in demonstration mode.
Demonstration mode can also test/confirm a netlist flow will import into Layout OK, so is good for a SCH hand-over check..
(common errors here are missing PCB footprints )
↧
Different width/gap on the same layer for Differential Pair
HI,
I'm currently making some small modifications to already existing PCB layout in Pads Layout 9.4 (I'm editing it with Pads Layout 9.5).
I suppose that I have a ES edition.
For some specific reasons I have to route my differential pairs out of the connector between two pads (pad gap diff_trace+ gap diff_trace- gap pad).
Normally my width and gap for diff pair is bigger, however when routing out from the connector I have to make the traces and gap smaller to do it (I can live with
impedance mismatch - rs422 diff pair).
I can't solve how to do it, there are some settings to make different width/gap for different layers (of course to account for controlled diff pair impedace).
However I would like to do it on the same layer.
Do you have any suggestions ?
Best,
Pawel
↧
↧
Re: Different width/gap on the same layer for Differential Pair
The only way I know how to do this on a single layer is with differential pin pairs. If you don't have those, you can create them with a dummy pin added to each net. Virtual pins won't work; it has to be a real part. As I'm thinking about it, it can be a part with two pins. Make the pins surface mount without soldermask or solder paste and the same size as the wider net width and spaced per your requirements. If it needs to survive ECO forward and back annotation, then the parts need to be added to the schematic too. Place them where the trace/space needs to change. Make sure the unroutes are in the correct order (use the reschedule command in Router if necessary), and then create the differential pin pairs with the values you need. It's a fair amount of extra work, but it should work.
↧
Re: I want to modify the Part List Exclude in the Property Definition Editor in PADS 9.5
No you cannot change this behaviour, the Part List Exclude option is used by the software to perform the exclusion, this works in conjunction with Forward to PCB to control items appearing in either PCB and/or Parts Lists or both.
↧
Re: Property Value of part is Chinese,Load selected Component will have problem
You should contact your local Customer Support representative to get this logged with Mentor.
↧
Re: xDX Designer - Shortcut Keys to Quickly Open/Close Schematic Tabs
You can close all tabs from the menus - Windows - Close All, you cannot open all tabs with any shortcut.
↧
↧
Re: DxDesigner - How to Select a Group of Parts and Move or Cut
Use Area Select by dragging the mouse around the parts, you can change the behaviour between full fence mode and Overlap by using the Alt key (in VX.1) or select on part and use the Shift key whilst doing the area select (again in VX.1). Alternatively use the Selection Filter to limit selection (pre-VX.1 releases). If in doubt, look up the help.
↧
Re: Packager coughing up rippers
Another solution is to edit the local symbol and to set the attribute "Forward To PCB" to false. After that, the packager runs through without problems (at least with my projects).
↧
Re: DxDesigner - Copy a Component's Part Number to Windows Clipboard
Select the Part Number on the symbol directly in the schematic (from 7.9.4 onwards) by triple click of the mouse so that the text is clearly highlighted, then use the context menu to copy to the clipboard.
↧
Re: I want to modify the Part List Exclude in the Property Definition Editor in PADS 9.5
Hi Robert,
Could I add a user option to perform the same exclusion? we want to use DNP instead of Part list Exclude. The text is smaller and easier to place on a busy schematic.
Thanks
↧
↧
Re: DXF to copper pour outline
Or, if you are not concerned about outside corner radius, you could create a single copper path around the perimeter. For example, a 2mm wide path 1.5mm inside the border. (extra .5mm space for copper to edge clearance). This is what I do for edge banding for shield via stitching.
↧
Re: I want to modify the Part List Exclude in the Property Definition Editor in PADS 9.5
You could use a property called DNP in combination with Part List Exclude to achieve what you want, make Part List Exclude invisible. Alternatively if you don't mind the parts being in the Parts List with a DNP property that can also be achieved, but using an alternative to actually exclude the part from the part list would only be possible with post-processing of the Part Lister output.
↧
Re: I want to modify the Part List Exclude in the Property Definition Editor in PADS 9.5
So the real easy solution is to just use the Part list Exclude option, hide the property (Part list exclude) and show the Value (True) either under or on the symbol
↧
Error on generation of Cadence Allegro 15.Xx netlist generated from DX designer
Hi,
I have designed the schematics in dx designer. Now I am generating the cadence allegro compatible netlist but I am having below error.
***********************************************************************************************************************************************
pcb: Note 6057: design sym CONNECTOR:CONN_3N-1: VALUE=CONN,ELEC: Bad property value
pcb: Error 6034: Illegal character
pcb: Error 6079: design sym ICS:PACKETENG_560_8: PINSWAP=(SPARE_8,SPARE_7,SPARE_6,SPARE_5,SPARE_4,SPARE_3,SPARE_2,SPARE_1,SPARE_12,SPARE_11,SPARE_10,SPARE_9): Hetero device property conflict
pcb: Error 6079: design sym ICS:PACKETENG_560_12: PINSWAP=(NC_30,NC_29,NC_28,NC_27,NC_58,NC_26,NC_57,NC_25,NC_56,NC_24,NC_55,NC_23,NC_54,NC_22,NC_53,NC_21,NC_52,NC_20,NC_51,NC_50,NC_19,NC_18,NC_49,NC_17,NC_48,NC_16,NC_47,NC_15,NC_46,NC_14,NC_45,NC_13,NC_44,NC_12,NC_43,NC_11,NC_42,NC_9,NC_10,NC_41,NC_8,NC_40,NC_7,NC_6,NC_5,NC_4,NC_3,NC_2,NC_1,NC_39,NC_38,NC_37,NC_36,NC_35,NC_34,NC_33,NC_32,NC_31): Hetero device property conflict
*******************************************************************************************************************************
I have attached xls and high lighted errors with yellow color.
These are the known error as dx designer help it self provides the solution as given below
========================
PCB-6034
Message: Illegal character [character].
Cause: The attribute value indicated in the following message contains the illegal character shown.
Solution: Fix the attribute value, enable automatic fixups, add a GENVAL fixup, or change the PCB configuration file to allow this character. PCB Configuration File: CHKVAL _NAME_CHK, CHKVAL _LIST_CHK, GENVAL.
===============================================
But I dont know how to implement the solution in design.
I tried to solve by searching value "CONN,ELEC" in design and yes this is symbol name of connector. So do I need to change the name of symbol ? Because there are lots of instance are there.
Please suggest a better solution.
-
Thanks,
mahesh
↧
↧
Re: Partlister case sensitive?
Which Verification? DxDataBook? Maybe those fields are set to annotate but not load, if they aren't loaded during the verification step the values aren't compared thus they "match" regardless of case or actual value.
What data is case sensitive? Property names, property values? 10m is different from 10M and I would expect them to be separated. Which columns do you have set as Primary? How do you have other columns set for Display? And many more questions. This issue would be better served as an Service Request to Customer Support. We may be able to get your partlist to look like you want even though it doesn't directly do what you want.
↧
Re: Anyone else migrating from Logic to xDxDesigner?
Sorry to dredge up an old post, but this is relevant:
LOTS of fixes in v1.1 !
All of the graphical errors are fixed. Migration is much smoother. It still assigns pin names to the symbol, not the part, so if you use the same symbol for multiple parts with different pin names in Logic, it will create a new symbol in xDx.
Now if I can figure out how to get it to bring over the part attributes I assigned in Logic. I tried editing the .cnv file, no luck.
↧
Re: netlister updating PKG_TYPE
I you don't want the PCB Interface to backannotate the PKG_TYPE values back to DxDesigner modify the configuration file in the BeginAttPassList section. Look for PKG PKG_TYPE and add the keyword DontBackAnno. So in the configuration file it will look something like this
BeginAttPassList
Specific
|BeginOatAtts
COM REFDES
COM $OBJNAME
COM PADS_ID
COM SYMTAG
COM PKG_LOCK
NET PADS_ID
PIN #
NET $OBJNAME
|EndOatAtts
PIN PINTYPE
PKG DEVICE
PKG PKG_TYPE DontBackAnno
↧