找回密码
 注册
关于网站域名变更的通知
查看: 13435|回复: 68
打印 上一主题 下一主题

Capture-Allegro最好的设计习惯

    [复制链接]

该用户从未签到

跳转到指定楼层
1#
发表于 2009-8-14 10:08 | 只看该作者 回帖奖励 |倒序浏览 |阅读模式

EDA365欢迎您登录!

您需要 登录 才可以下载或查看,没有帐号?注册

x
本帖最后由 John-L 于 2009-8-14 10:10 编辑
0 K, Y* Q& T$ I" N; Z. A
5 T) ~6 J8 ?2 v做到下面的要求,allegro NET-IN就轻松多了:2 G: j) R7 z& R8 [, k$ V
7 C4 ~0 V0 M: u1 G
Best practices for Capture-Allegro
( d! v' ~/ i$ CBest practices for preparing a library for Capture-Allegro PCB Editor# ]6 j, v4 L3 Q/ H- \3 u! i2 N
flow; S( i# F' z1 q* u! s
􀂃 Limit part and pin names to 31 characters" F# k5 F) l$ {- ^# v* u; {" U
􀂃 Use upper case characters for part/symbol names, part references& p4 S- ~, Z. b: P4 @+ a5 k
designators, and pin names7 w% h) w% w9 T" t: p6 e
􀂃 Do not use special characters to assign part names, references. @' o' h0 H5 z1 C/ U
designators, and pin names
! o4 H+ E# ]/ u% ~, M􀂃 Do not use duplicate pin names for pins other than power pins
" @1 U! t6 J8 z7 p& G& X  j- J4 @􀂃 For multiple power pins with the same pin names, do not make some* w1 ~- U- b: w) k  ^
pins visible and other invisible
: W: X1 w$ |0 x" V􀂃 Do not use "0" as a pin number
/ q$ o; R7 j( `1 a2 {* R& [8 \, eBest practices for Capture design for Allegro PCB Editor
- m/ K/ |$ d9 m4 v􀂃 While defining a net list alias or a net name% h, O/ `/ `8 l. Y3 z4 z2 a. d
• Keep the maximum length of a net name or alias up to 31
9 G7 k# Q- o5 Jcharacters
2 i$ q+ S+ ]1 }& j7 W" S• Do not use lower case or special characters in a net name& e/ H0 {+ \  o; k$ y! X! y
􀂃 Avoid using "Power Pins Visible" property at design level* R- W6 Q, i( |
􀂃 Use net to connect pins) ]' p* A1 G1 P, n8 Q3 H
• Leave room for assigning a net name. Pin-to-pin connection
# I& J! q' y8 r: v' \. O/ ]: f4 xchanges the net name when a user moves a component
* x& Z- a- v& F9 h􀂃 Run the Capture DRC command before generating Allegro PCB Editor8 n6 F0 q5 V4 E: ^$ c( m
netlist
, S; l4 L7 }8 o4 |9 X4 J􀂃 Set path for Allegro PCB Editor footprint before running Netrev) H7 m6 s+ R% E" |6 y
Best practices for smooth back annotation
1 B" {) a# N- f5 p$ [$ r8 w- k􀂃 Do not change design name, hierarchical block names, or reference
5 y# l+ H3 z+ d# V/ }designators in Capture after board files creation
) n1 L( B* a- ?$ b, H􀂃 Do not edit a part from schematic in Capture after board file
2 h! F, _& c# W1 p% A/ B5 ycreation. r8 h( V; s4 H. w; o
􀂃 Do not replace cache as it changes the Source library name and part) X$ C9 d0 p7 {4 ~
name, in capture
" B# v7 v/ U, p( G3 U" d& }6 q􀂃 Do not change the values of component definition properties in: |9 R$ M, d3 I- Y) D3 J
capture after board files creation. S( w! e7 G$ K
􀂃 Do not change Design file/root schematic/hierarchical block names2 Z9 Y( M5 Y5 E1 J% {- I
in Capture after board file creation" C; ?# ?$ k$ }. R2 |3 V/ N. Z
􀂃 Do not add or delete components to or from the schematic design
( k+ t+ W" `9 i9 A/ qimmediately after the board file creation. Add or delete components: ^# y: p+ U& r
after finishing the back annotation process
' ?) h$ r' Y* K  L6 G' \* U0 L- 2 -; ]2 s# j2 Z, R+ b
􀂃 Do not add any additional components in Allegro PCB Editor. Instead,
3 J% \8 a6 i/ n! V2 H! Y% nadd components in Capture and take them to Allegro PCB Editor+ g  \8 Q" t, I& }- w$ T# R
􀂃 Do not add, rename, or delete a net in Allegro PCB Editor
# m2 \/ ^3 L  [/ ~$ ~: Q; U􀂃 Do not change the format for reference designators for parts in1 g1 i, r( K% E- |6 l4 _, l  |: s
Allegro PCB Editor as <Alphabet(s)><Numeric><Alphabet(s)> or
. \, K* V+ Y2 _><Alphabet(s)>-<Alphabet(s)>* e5 ~3 v% x5 S( c! L1 [9 Z" T
&#1048707; Run Allegro PCB Editor Dbdoctor before running Back annotation by
, b: F& C5 P. E4 Tselecting the Database Check command from the Tools menu in Allegro
  V/ g6 b' \: @2 e! wPCB Editor
. l: h+ t  n; |* Q5 @&#1048707; Make backups of the original design before updating the design with
+ m( D- L# \* k. P0 w, k& |+ g- tthe swap information in Capture, k0 s# f. A2 l7 M. A9 H
&#1048707; Back annotate the design immediately after making the board file.
3 P" e( D  i- z! |  s9 tThough it does not a mandatory step, back annotating the design2 s. c8 N/ e0 D0 k3 D: P. ~9 j
before placing components helps avoid problems in back-annotation
& q, V9 H' s0 ]- |at a later stage.
2 t1 y, S4 U& U' l6 d. y; }0 oIf back annotation at this stage generates an empty swap file, you
% q3 Z( D; w" k) B1 u" W2 lcan proceed with placing and routing the board file. In case any
. L8 h) ]+ {8 [problems are detected, you must correct them in the design file and
. u4 n. O, P2 e& M, agenerate the board file again until an empty swap file is generated.

Best practices for Capture-Allegro.pdf

24.21 KB, 下载次数: 1431, 下载积分: 威望 -5

该用户从未签到

推荐
发表于 2019-11-7 14:19 | 只看该作者
一直不明白电源脚默认都是隐藏,有什么好处?1048707; Avoid using "Power Pins Visible" property at design level&

该用户从未签到

推荐
发表于 2013-10-15 23:48 | 只看该作者
英文版的  看不懂 請問有中文版的嗎?

该用户从未签到

推荐
发表于 2019-11-5 15:50 | 只看该作者
做工程需要规范,学习下,谢谢!

该用户从未签到

2#
 楼主| 发表于 2009-8-14 10:11 | 只看该作者
不知道为什麽COPY出来会有"&#1048707"之类的东东

该用户从未签到

3#
发表于 2009-8-15 07:16 | 只看该作者
很好哦

该用户从未签到

4#
发表于 2009-8-15 13:56 | 只看该作者
谢谢分享

该用户从未签到

5#
发表于 2009-8-15 14:24 | 只看该作者
努力争取

该用户从未签到

6#
发表于 2009-8-16 09:43 | 只看该作者
不错: v9 b0 O8 c1 d- \% b% p& u6 P; O+ I
好东西

该用户从未签到

7#
发表于 2009-8-17 08:46 | 只看该作者
好东西 大家分享

该用户从未签到

8#
发表于 2009-8-17 09:58 | 只看该作者
7# dabing715 . n) g& s6 M* \" ]2 g  v) C  `4 p
打开学习一下,谢啦1

该用户从未签到

9#
发表于 2009-8-17 10:08 | 只看该作者
谢谢分享!

该用户从未签到

10#
发表于 2009-8-18 22:45 | 只看该作者
谢谢楼主

该用户从未签到

11#
发表于 2009-8-19 08:16 | 只看该作者
TKS~~~

该用户从未签到

12#
 楼主| 发表于 2009-8-28 14:25 | 只看该作者
自己顶一顶。
$ ?( Q  K1 V6 _看见好多人调网表有问题。
9 j+ z% ~- X, u5 h6 P) M" A养成良好习惯很重要。

该用户从未签到

13#
发表于 2009-12-16 17:25 | 只看该作者
很好

该用户从未签到

14#
发表于 2009-12-16 20:13 | 只看该作者
学习了

该用户从未签到

15#
发表于 2009-12-16 20:50 | 只看该作者
学习了!顶起来!
您需要登录后才可以回帖 登录 | 注册

本版积分规则

关闭

推荐内容上一条 /1 下一条

EDA365公众号

关于我们|手机版|EDA365电子论坛网 ( 粤ICP备18020198号-1 )

GMT+8, 2025-9-22 02:55 , Processed in 0.140625 second(s), 28 queries , Gzip On.

深圳市墨知创新科技有限公司

地址:深圳市南山区科技生态园2栋A座805 电话:19926409050

快速回复 返回顶部 返回列表