File: 322.htm

package info (click to toggle)
eagle 4.16-5
  • links: PTS
  • area: non-free
  • in suites: etch, etch-m68k
  • size: 36,508 kB
  • sloc: sh: 82; makefile: 32
file content (112 lines) | stat: -rw-r--r-- 4,185 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
<html>
<head>
<title>EAGLE Help: Consistency Check</title>
</head>
<body bgcolor=white>
<font face=Helvetica,Arial>
<hr>
<i>EAGLE Help</i>
<h1><center>Consistency Check</center></h1>
<hr>
In order to use Forward&amp;Back Annotation a board and schematic
must be consistent, which means they must contain an equivalent set of
parts/elements and nets/signals.
<p>
Normally a board and schematic will always be consistent as long as they
have never been edited separately (in which case the message
<i>"No Forward&amp;Back Annotation will be performed!"</i>
will have warned you).
<p>
When loading a pair of board and schematic files the program will check
some consistency markers in the data files to see if these two files are
still consistent. If these markers indicate an inconsistency, you will be
offered to run an <a href=44.htm>Electrical Rule Check</a> (ERC),
which will do a detailed cross-check on both files.
<p>
If this check turns out positive, the two files are marked as consistent
and Forward&amp;Back Annotation will be activated.
<p>
If the two files are found to be inconsistent the ERC protocol file will
be brought up in a text window and Forward&amp;Back Annotation will
<b>not</b> be activated.
<p>
The ERC protocol file contains several sections that list the inconsistencies
found. Each of these sections may or may not be present, depending on which
inconsistencies have been found.
<b>Please do not be alarmed if you get a lot
of inconsistency messages. In most cases fixing one error (like renaming
a part or a net) will reduce the number of error messages you get in the next
ERC run.</b>
<pre>
Parts not found in board:
  IC1
  R7
</pre>
This section lists the names of the <i>parts</i> that are present in the
schematic, but are missing in the board.
<pre>
Elements not found in schematic:
  C33
  D2
</pre>
This section lists the names of the <i>elements</i> that are present in the
board, but are missing in the schematic.
<p>
The following sections are only present if the part and element names have
checked out to be consistent:
<pre>
Parts/Elements with inconsistent packages:
  IC12
  R1
</pre>
This section lists the names of the <i>parts/elements</i> that are
present on both schematic and board, but which have inconsistent packages.
Packages are considered consistent if they contain an equally named set
of pads/smds.
<pre>
Parts/Elements with inconsistent values:
  R55      100k       47k
  C99      10n        10p
</pre>
This section lists the names of the <i>parts/elements</i> that are
present on both schematic and board, but which have different values.
The second column lists the value of the <i>part</i> in the schematic,
the third column lists the value of the <i>element</i> in the board.
<p>
The following sections are only present if the part and element packages
have checked out to be consistent:
<pre>
Pins/Pads with different connections:
  Part   Gate   Pin   Net   Pad   Signal
  IC5    A      2     GND   2     S$42
  R3     R      1     D1    1     D2
</pre>
This section lists the names of the <i>pins</i> and <i>pads</i>
that are connected to different nets/signals in schematic and board.
The <i>Net</i> column contains the net name in the schematic, while
the <i>Signal</i> column gives the signal name in the board. If either of
these two entries is blank, this means that the pin/pad is not connected.
<p>
<b>Making a Board and Schematic consistent</b>
<p>
To make an inconsistent pair of board and schematic files consistent, you
have to manually fix any inconsistency listed in the ERC protocol file.
This can be done by applying editor commands like
<a href=62.htm>NAME</a>,
<a href=97.htm>VALUE</a>,
<a href=70.htm>PINSWAP</a>,
<a href=80.htm>REPLACE</a> etc.
After fixing the inconsistencies you must use the
<a href=44.htm>ERC</a> command again to check the files and
eventually activate Forward&amp;Back Annotation.

<hr>
<table width=100% cellspacing=0 border=0><tr><td align=left><font face=Helvetica,Arial>
<a href=index.htm>Index</a>
</font></td><td align=right><font face=Helvetica,Arial size=-1>
<i>Copyright &copy; 2005 CadSoft Computer GmbH</i>
</font></td></tr></table>
<hr>
</font>
</body>
</html>