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

Capture-Allegro最好的设计习惯

    [复制链接]

该用户从未签到

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

EDA365欢迎您登录!

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

x
本帖最后由 John-L 于 2009-8-14 10:10 编辑 , n, i1 C. w( ^8 \- o1 ]. W

' i4 W7 M* I2 w! u: P8 X做到下面的要求,allegro NET-IN就轻松多了:, h% d: J( ]7 P6 f# T: H; [

' e6 `" ~2 M4 y+ p( rBest practices for Capture-Allegro
  @' l+ L8 Y+ sBest practices for preparing a library for Capture-Allegro PCB Editor! `/ x6 J  `0 G! D7 p
flow2 H& F0 L) |2 T* ?* g
􀂃 Limit part and pin names to 31 characters
# o# G0 {5 K# u8 U0 w􀂃 Use upper case characters for part/symbol names, part references
/ c7 Q( Y; ]  V- Pdesignators, and pin names% g/ k  s! }3 U( A; \$ ?- a2 _
􀂃 Do not use special characters to assign part names, references
0 m' w- @1 G/ ?8 i2 |) e1 hdesignators, and pin names
$ `4 Q- F: k3 b. o& q" z8 k' Y􀂃 Do not use duplicate pin names for pins other than power pins
. G3 n. ]0 n' b􀂃 For multiple power pins with the same pin names, do not make some0 k1 u! u1 V" v  [( E( s
pins visible and other invisible
+ R- I% S3 |' i3 C' u, F/ f􀂃 Do not use "0" as a pin number
6 T8 Y6 o& S1 t- F) x6 VBest practices for Capture design for Allegro PCB Editor
1 _4 C3 w, @- E( i9 `! @􀂃 While defining a net list alias or a net name+ E1 p2 M" ~( E* p
• Keep the maximum length of a net name or alias up to 31
. {% Y! Z. x1 a; Scharacters
! n) w& x/ w% X• Do not use lower case or special characters in a net name
  i* O; T1 {) P􀂃 Avoid using "Power Pins Visible" property at design level& b. k, \! H5 [& C2 H1 T6 o7 R- R
􀂃 Use net to connect pins$ O; D! O. `- G- I) e1 Z
• Leave room for assigning a net name. Pin-to-pin connection
2 c" r0 L( t- N0 ^  Cchanges the net name when a user moves a component# `: `. y+ i) s
􀂃 Run the Capture DRC command before generating Allegro PCB Editor
/ o; V2 S( R* X* E' r) ^netlist- b" X3 [- G, T" h2 D' `/ |
􀂃 Set path for Allegro PCB Editor footprint before running Netrev
( h. W" G" h: V1 A( D8 }; XBest practices for smooth back annotation5 Q0 Z3 M+ h) K5 N9 X! l7 w0 b# x) f) x
􀂃 Do not change design name, hierarchical block names, or reference7 m+ ?4 \& j( O2 d8 t9 q% t/ ^
designators in Capture after board files creation
# r8 M6 S& v+ H􀂃 Do not edit a part from schematic in Capture after board file& N$ ^9 D/ S4 m6 ?  }& G" L
creation
- _6 f4 g7 Q; c2 A! \􀂃 Do not replace cache as it changes the Source library name and part  W' r5 t+ u( y' ]' E
name, in capture
6 B2 w: t' N& i0 W􀂃 Do not change the values of component definition properties in
0 H: `) Z' j7 D7 y. t2 `, Acapture after board files creation6 w+ s* ]# u2 e, P$ I
􀂃 Do not change Design file/root schematic/hierarchical block names; d: y- b. N/ A' x
in Capture after board file creation
2 j& _# m0 H, Q, i1 s9 C" c. [􀂃 Do not add or delete components to or from the schematic design# H* [8 M2 S& V2 T/ G# d/ k
immediately after the board file creation. Add or delete components; R* W0 m4 t1 h) G, n
after finishing the back annotation process: t  A) u$ L* [" Y, |9 P3 @% e
- 2 -
. X+ k  `& [" v- q) s& b􀂃 Do not add any additional components in Allegro PCB Editor. Instead,5 h  ^( k; ]$ Z3 O, ?, K- t: z
add components in Capture and take them to Allegro PCB Editor5 A' ~. v1 a% P: S! V
􀂃 Do not add, rename, or delete a net in Allegro PCB Editor
; U  H8 `& |* L* ]. n7 R" t􀂃 Do not change the format for reference designators for parts in
* O& Z1 e' Q! \Allegro PCB Editor as <Alphabet(s)><Numeric><Alphabet(s)> or
8 k; N8 v2 O8 `4 z3 l% P><Alphabet(s)>-<Alphabet(s)># P6 o) q4 b" q! R, F/ ]$ ~9 {" N
&#1048707; Run Allegro PCB Editor Dbdoctor before running Back annotation by
  |, y8 H, m. \selecting the Database Check command from the Tools menu in Allegro9 |! ]; d/ g$ l. V/ G2 X1 {
PCB Editor, n* v1 _6 V/ i/ C. h% _
&#1048707; Make backups of the original design before updating the design with
+ T3 j5 R! X+ Ithe swap information in Capture
2 Z# I# ~# e1 b: i2 t  q, U&#1048707; Back annotate the design immediately after making the board file." n+ P+ \% R9 }/ Z
Though it does not a mandatory step, back annotating the design) R' \6 q$ H3 `& c
before placing components helps avoid problems in back-annotation
" T6 M) k; i4 [6 k% U( Eat a later stage.& n4 B8 q0 [" }/ b
If back annotation at this stage generates an empty swap file, you
' O  q, O7 n& h6 _can proceed with placing and routing the board file. In case any
' h. n9 g. [2 n6 |  |problems are detected, you must correct them in the design file and
7 K; w1 v  C( \9 f' O% X, G* t+ hgenerate 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 | 只看该作者
不错
& Z0 b. D$ ~. }好东西

该用户从未签到

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

该用户从未签到

8#
发表于 2009-8-17 09:58 | 只看该作者
7# dabing715 ! d& o. Q4 x) [, q4 a9 M
打开学习一下,谢啦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 | 只看该作者
自己顶一顶。" Z3 R) k- f6 Z( `- r1 {
看见好多人调网表有问题。+ v; y& h7 K1 z; |5 u! x: Y+ D
养成良好习惯很重要。

该用户从未签到

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-10-12 05:03 , Processed in 0.140625 second(s), 28 queries , Gzip On.

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

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

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