Import the pads logic schematic to pads Layout

 

August 23 th, 2012

The following describes how to import a schematic diagram Into a PCB File and find a more convenient and convenient operation method:

1> open the schematic file to be processed, and use pads layout to create an empty PCB File and open it;
2> in pads logic, execute tools> layout netlist> Design> ECO to PCB;
3> if an error is found during the import process, an error report file with the. Err suffix will be generated and automatically opened;
4> If the import process is correct, no error report will be generated, and the components are encapsulated at the coordinate origin of the new PCB File.

 

Then there is another problem. during the design process, after updating the electrical connection of the schematic to the PCB file, if you need to change the package of the components in the schematic, how can I encapsulate the changed components and synchronize them to the PCB? The details are as follows:

1> in pads logic, execute, tools-> layout netlist-> Preferences tab-> compare PCB decal assignment;

2> then, on the design tab, run the "ECO to PCB" command, and then update the first encapsulation form in the encapsulation list of the component attributes in the PCB element encapsulation.

 

 

 

August 22th, 2012

Today, I made a summary and found that many domestic electronics companies use pads to draw PCB, so I decided to learn pads.
 

 

 

 
After drawing a simple schematic in pads logic, we want to import the component encapsulation and electrical network to pads layout for component layout and wiring.
 

However, when the "pads layout rules (. ASC)" file is exported from the logic schematic, it becomes stuck and cannot be imported into the router.
 

 
The procedure is as follows: choose File> export> pads layout rules and save the file successfully.
 

 
Next, open the router and import the components and networks. As a result, the system imports the data n + 1 times. The original position in the router does not show the components normally.
 

 the operation procedure is as follows: menu file-> Import-> XXX. then, the following content is displayed in the information output box: 

  D: \ pads projects \ layout_session.log 

    reading file --     S: \ pads \ MCU. ASC     -- version 9. 0. *     ** no errors found **  

 
Although the system prompts that no error is found, there is no component at the PCB File origin. Failed!
 

After searching for the Internet for a long time, I finally found a solution. The original article is as follows:
 

 
1. Check the DRC to see if there is any electrical connection error. If there is no error, proceed to the next step;
 

 
2. generate a network table. 3. make sure that the PCB packages of all components in your schematic diagram exist in layout. If some original components are not encapsulated, you must first create an encapsulation Library Based on datasheet or physical objects. 4. import the network table generated by logic after confirming that all PCB packages exist. after the import is successful, set the wiring rules and then wiring. 6. when wiring, pay attention to the influence of components and various signals.
 

The procedure is as follows:
 

 
Draw a schematic in the logic software and open the menu tool> layout netlist> to save the XXX. ASC file.
 

 
Then, the system displays a XXX. Err result file. The detailed results are described in the file.
 

If there is no error, you can enter the router for component layout.
 

 
The procedure is as follows: choose File> Import> XXX. ASC. Then, an ASCII. Err error message text file is displayed, showing the following content:
 
  
Reading file -- S: \ pads \ MCU. ASC * bad * connection * ASCII data format, nets must contain more than one pin. signal + 12 vwarning: deleting signal + 12 V ** input warnings found **
 
 
 
 
Then, a prompt box is displayed in the router. The information is as follows:
 
Warning: improper data found in file X: \ XXX. ASC may be ignored.
 
 
 
 
At this point, a component appears at the router origin.
 
The meaning of the error message remains to be learned.