ODB++ 官方文档

所需积分/C币:47 2019-01-11 10:27:31 1.9MB PDF
收藏 收藏 3

odb++ 官方文档,适合参考。官网下载需要注册比较麻烦
Charts 20 Chapter 4 Job Entity database steps(See Chapter 5) 25 symbols(system and User Symbols 25 ttrlist(Attribute List) 25 features (Symbol Features) 25 matrix Job Matrix) .26 misc (Miscellaneous) .......28 attrlist (Attributes Used in Job 非.番非·非非·非非非音··非鲁看音 28 last_save Last Time Job Saved).............. 29 userattr(User Attributes) 29 wheels( Gerber Wheel Templates) .,,,,,,31 attrlist(Attributes values)............. dcodes(Wheel Codes Definition) 31 forms(Work Forms) ..,,,,,,,,,,,,,,,,,,,,.,,,32 dat/files/<file_name>(Image File)...... ..32 dat/hdr Data header) 33 def/hdr(Definition Header)................ 33 <help_ name>(Help Text) ,,,,,38 <pixmap_name>(Pixmap Field File).............38 flows (Job Process Charts) ...,,,,,,,,..39 dat/hdr(Data header) 39 dcf/hdr ( dcfinition Header)................ 40 fonts(Fonts uscd in Job).............. 43 standard(Standard Font)............. 43 stackups (Stackups) 44 attrlist(Attribute List) 44 fill_table(Prepeg Combinations) 45 material (Material Specifications 47 stackup(Build)............. 51 np(Impedance In 53 Input ............. 55 output ···+···· .........55 snapshot(Measurement Information)) 55 user ..56 extension 02020801 ODB++ 3 Chapter 5 Job>steps Entity stephdr(step header) 57 attrlist(Attribute List)........ ····:::·······;.·:· 59 ayers(See Chapter 6) 59 netlists(Netlists )............. ,,,,,,,.59 cadet/netlist(CADnet 59 refnet/ netlist(Reference).................62 curnct/netlist(Current) 看鲁非·非 62 profile (Outlinc shape of Step) 63 bom( Bill of materials) .....,....64 bom .64 files(Source Files) 67 eda(Electronic Design Automation) ..,,,,,,67 data ..67 net_prp(Nct Type Clearances Records) 77 chk( checklists)(See Chapter 7) 78 ct(Scc Chapter 8) 78 reps reports) .,,,,,,,,,,,,,,,,,,,,,,78 Chapter 6 Job>steps>layers Entity attrlist(Attribute List 81 features ······ ········ 81 components 90 components2 .92 tools (Drill Tools 94 camtek 95 cdr14s$ tp main(CDR|4 Main step,)"∴…,∵· attrlist(Attribute List) 98 cdrhdr(CDrl4 Header) dD非 .99 ..,,,104 crd14-stp_pos(CDr14 Positive Step 104 crd14_stpncg(CDR14 Negative Step) 104 clone_<step_name>(S&R Exclusion Zones 105 Ipd (Layer Production Data) 105 mania(MaNIA Automatic Optical Inspection) 106 notes(Electronic Job Notes)................ 108 relations( Connections between Features)..........108 02020801 ODB++ 4 Chapter 7 Job>steps>chk( checklists) def/hdr( Definition header)....….….114 res/hdr(Results Header report/tags(Report Tags) port/text(Text Report l18 disp display records for measurements) mcas(Mcasurcments) .120 Chapter& Job>Steps>et(Electrical Test) < etset name>/hdr......,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,123 csplit_name>/hdr ................... 124 <split name>/mapping ···· ...,....∴..126 < split_name>/ net ext,………128 <split name>/pin rules .128 dapter_top(bot)/desc.,.….….….…130 pins /<pin_name> 132 Chapter 9 Symbol definition Standard Symbols ..,,,,135 Round ....,135 Squ 135 Rectangle .,,,,,,,,,,,,,135 Rounded rectangle 136 Chamfered Rectangle..................136 Oval 136 137 Octagon 137 Round donut ··.:···:···:··· ,,,,,,,,,137 Square donut 138 Horizontal hexagon 138 Vertical Hexagon 138 Butterfly...…….….…139 Square Butterfly 139 Triangle .139 Half oval 140 Round Thermal rounded) .....,.....,,,,140 Round Thermal (Square) 140 Square Thermal.... ,,,,,,,,,,141 Square Thermal(Open Corners) .141 Square-Round Thermal D ..,141 02020801 ODB++ 5 Rectangular Thermal ...142 Rectangular Thcrmal(Open Corners) 142 Ellipse.....,......, ..,,,,,,,,,,,,,,.,,,142 Moire 143 Hole 143 143 Rotated standard Symbols ···· ··· 143 Chapter 10 System Attributes Appendix a Frequently Asked Questions 02020801 ODB++ 6 Chapter 1 Overview Introduction This book contains the full description of the odb++ Cad CAM/dfm data exchange format. ODB++ is widely accepted as a practical de-facto standard within the electronics industry as an efficient way to move printed circuit bare board, assembly and test data on the manufacturing-engineering level within design/manufacturing supply chains. It is designed as a simple yet comprchensive description of all entities needed in the manufacturing of a printed circuit board Originally defined by Valor, ODB++ is now fully used by 3rd-party tool providers within the industry; Valor is committed to a policy of openly supporting any and all organizations to successfully implement the odb++ format Intended readers This book is intended for anyone interested in implementing the odB++ format for CAD/CAM applications and for interfacing to logistical supply-chain processes. This specification forms a part of the information kit supplied to members of valor's“ Open Systems Alliance” ODB++ versions The versioning system assigns a version number to each entity in the odb++ database. This allows updates to be made to cach entity separately without affecting other entities. Whenever any entity is updated a comprehensive ODB++ version number is assigned and set on the front cover of this document Version Number format Each entity has a file called <entity_name. ver saved next to it(such as steps. ver)where the file contains the version number in the following syntax <maJor>. <minor> Where <major> is one character(A, B,c..). a change in <major> means orward compatibility is not retained (newer versions of an ODB++ database ns cannot be read by older versions of the application software) Where <minor> is two digits (01, 02, 03.. 99).A change in <minor> mear that forward compatibility is retained Recent Updates This section lists the changes made to ODb++ and to the documentation since February 2000 02020801 Last Update: July 11, 2002 12: 41 pm ODB++ 7 Chapter 1 Overview Conventions and Terminology February 2000 <job_name>/steps/<step_name>/stephdr Two new fields added(AFFECTING BOM AFFECTING BOM CHANGED ). See stephdr(Step Header ) "on page 57 <job name>/steps/<step name>/eda/data Two new fields added to the Pin Record Structure(<etype> <mtype>). See Job>Steps>et(Electrical Test) "on page 123 <job_name>/steps/<step_ name>/netlists/cadet/netlist New parameters added to the Netlist (x, e ,& by ). See"netlists(Netlists "on page 59. <job_ name>/steps/<step name>/layers/<layer_name>/components2 New Job Entity. The components file describes the original eda data for a component, while the component s2 file represents component data after processing with Assembly Merge(BOM Merge, Library Merge and Board Merge) Seecomponents2" on page 92 <job_name>/steps/<step_name>/netlists/cadnet/netlist The following parameters have been appended [xke>]and [by > See"netlists(Netlists " on page 59 September 2000 <job name>/steps/<step name>/chk/<checklist name>/ actions/<action num>/res/ sres/layer_name>/meas New symbols for <ftype> and <fsym>. See"meas(Measurements "on page 120 <job name>/ steps/<step name>/eda/data New net Attributes. See"Job>Steps>et(Electrical Test)"on page 123 <job_name>/steps/<step_ name>eda/net_prp New net type clearances. See"<job_ name>/steps/<step_name>/eda/ net_prp” on page77. Conventions and Terminology Entity Core Definitions Data entities marked as"core"contain data that form an essential part of modelling the Printed Circuit Assembly (including all aspects of the PCB bare-board). In essence, core" entities contain all the information necessary for Cam systems to prepare PCB fabrication and assembly operations Supplementary Non-core entities(supplementary) are included in the ODb++ format to support certain CaM and dfM functions specific to certain solutions vendors. These supplementary entities are open to all, and are maintained in accordance with the specification, in thc same way as the"core"entities 02020801 ODB++ 8 Chapter 2 Design Principles File System Chapter2 Design Pi rinciple File system hi gerar ODB++ ndard file system structure a job in ODb++ i ed by stand-alone directory tree that can be transferred between systems without any loss f dat The advantages of a directory tree compared to one large file are apparent when a job is being read from disk or saved to disk. The flexible tree structure allows onl a small part of the job to be read/saved, avoiding the overhead of reading and writing a large file When a job tree has to be transferred to another system standard tar' and compression utilities can be used to convert a directory tree into one flat file Mandatory /Optional files The following list specifies the files that are mandatory, while those not mentioned are optiona For the job j。b/ matrix/ matri% For each Step defined in the Matrix Gob/steps/<step name>,stephdr For each Layer defined in the Matrix Gob/steps/<step name>/layers/<layer name>/features or Gob/steps/<step name>/layers/<layer name>/features. Z There are also links between files that are implicitly defined in the ODB++ definition which create dependencies between one file and another. For example the /<step name>/layers/comp top/components file contains links to /stepname /eda/data Legal Entity Names Job name Layer name Attribute name Step name Symbol name Attribute string ODB++ entity names must follow thesc rules 02020801 ODB++ 9 Chapter 2 Design Principles Readable a scll files The length of any name should not exceed 64 characters. However,user attribute strings(not names) are determined by the MAx LeN, MIN len fields in the <job name>/misc/userattr Job File(see" <job name>/misc/ userattr” on page29) Use only the following lower case letters (a through z) digits co through 9) punctuation-dash(-), underscore(_), dot(.)and plus(+ Names must not start with dot (.) with the exception of attributes which can start with() Readable ascilfiles All files in ODB++ are readable ascII files. This concept provides the advanced user with the capability to read database files for understanding. In contrast, binary databases which are still used in older systems prevent the user from reading database files directly and require a special extraction program to retrieve all or part of the database In all files, the character specifies a comment. Lines which start with this character are ignored by the system and are only used for readability. The linc separator can be cither <CR> or <CR><LF>, depending on operating system and platform Units of measurement All units are imperial units (inches, mils) Large File compression One of the reasons vendors have chosen binary databases in the past was the need to conserve space on hard disks. Modern compression techniques are available today and provide excellent compression ratios, especially for ASCll files with repetitive patterns. Large files in ODB++ are saved in standard UNIX compress format. The compression is optional, and any reader of ODB++ database should expect some files to be in either compressed format( Z suffix) or without compression. The files which are potentially compressed are clearly identified in the following material u fule Many of the files in ODB++ have an attached hidden file which provides information about them The name of the attached file is 卫ame>。s1m The file contains the following information Size size of the data file 02020801 ODB++ 10

试读 127P ODB++ 官方文档
立即下载 低至0.43元/次 身份认证VIP会员低至7折
关注 私信 TA的资源
ODB++ 官方文档 47积分/C币 立即下载
ODB++ 官方文档第1页
ODB++ 官方文档第2页
ODB++ 官方文档第3页
ODB++ 官方文档第4页
ODB++ 官方文档第5页
ODB++ 官方文档第6页
ODB++ 官方文档第7页
ODB++ 官方文档第8页
ODB++ 官方文档第9页
ODB++ 官方文档第10页
ODB++ 官方文档第11页
ODB++ 官方文档第12页
ODB++ 官方文档第13页
ODB++ 官方文档第14页
ODB++ 官方文档第15页
ODB++ 官方文档第16页
ODB++ 官方文档第17页
ODB++ 官方文档第18页
ODB++ 官方文档第19页
ODB++ 官方文档第20页

试读结束, 可继续阅读

47积分/C币 立即下载 >