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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title> pcb-rnd - FAQ </title>
<meta http-equiv="Content-Type" content="text/html;charset=us-ascii">
<!--AUTO head begin-->
<link rel="icon" href="resources/logo16.png">
<!--AUTO head end-->
</head>
<body>
<!--AUTO navbar begin-->
<table border=0 cellspacing=2 cellpadding=10 bgcolor="#eeeeee" width="100%">
<tr>
<th align=center bgcolor="#ccc0cc"> <a href="index.html"> Main </a>
<th align=center bgcolor="#ccc0cc"> <a href="news.html"> News </a>
<th align=center bgcolor="#ccc0cc"> <a href="doc.html">Doc</a> & <a href="faq.html">FAQ</a> & <a href="http://repo.hu/projects/pcb-rnd-aux/pool">pool</a> & <a href="tutorials/">tutorials</a>
<th align=center bgcolor="#ccc0cc"> <a href="support.html"> Support </a>
<th align=center bgcolor="#ccc0cc"> <a href="http://repo.hu/cgi-bin/pcb-rnd-people.cgi">People</a>
<th align=center bgcolor="#ccc0cc"> <a href="http://repo.hu/cgi-bin/pcb-rnd-people.cgi?cmd=events">Events</a> & <a href="http://www.repo.hu/cgi-bin/pcb-rnd-people.cgi?cmd=timeline">timeline</a>
<td align=right width="60%"> <font size="+2"><i>pcb-rnd</i></font> <img src="resources/logo32.png" alt="[pcb-rnd logo]">
</table>
<!--AUTO navbar end-->
<br>
<!--content-->
<h1> pcb-rnd FAQ </h1>
<h2 id="export"> 1. export </h2>
<h3> 1.1. Gerber export not producing excellon drill files </h3>
<p>
That is correct, by default direct gerber export shouldn't
produce excellon files as excellon is a different format. Direct
gerber export also won't produce ps or png files.
<p>
You have two ways getting excellon files:
<ul>
<li> If you need only excellon drill files, you can do a direct export using
the execllon export format; on GUI use the "File/Export layout" menu or
the {f e} key combination and select excellon; on CLI use -x excellon.
Unless you have an CNC router it's unlikely you want drill files only.
<li> What you probably should do instead of direct exporting is CAM
exporting, using "File/Export with CAM job..." or {f c} on the GUI or "-x
cam jobname" on the CLI. The CAM exporter is designed to invoke multiple
export plugins (e.g. gerber and excellon). pcb-rnd is shipped with
preconfigured CAM jobs for the most popular fab houses so you get file
names you can directly upload to them. If you have a fab not yet
supported, please contact me.
</ul>
<p>
<small>
Note: as of 2019, for the transition time, direct exporting to gerber using any of the old
naming styles (e.g. "fixed") will still cross-call the excellon export
plugin and produce the extra (non-gerber) drill files. It will also
generate a bunch of warnings telling you that this feature will be removed
soon. You shouldn't depend on this too much.
</small>
<h2 id="slots"> 2. padstacks </h2>
<h3> 2.1. Intern copper layer shape not rendering </h3>
<p>
Does the padstack has a hole? Does the hole drill through any internal
copper layer (in non-thru-hole case)?
<p>
Internal copper layers are special: there are multiple of them. The padstack
will place the intern shape on any internal copper layer that the padstack's
hole reaches. If the padstack has no hole, no internal layer shape is
rendered, even if it is specified.
<h2 id="slots"> 3. slots (oval holes) </h2>
<h3> 3.1. My slot doesn't show up on screen or in exports </h3>
<p>
Make sure you have the right layer groups and layers set up:
<ul>
<li> a mech layer group with purpose uroute and another with purpose proute for unplated and plated slots
<li> make sure there is a layer in each group that has <i>auto</i> in the comb flags - padstack side effects will land only on auto layers; auto layers are indicated with white hatching in the layer selector's layer color
</ul>
<h2 id="dsn"> 4. DSN format </h2>
<h3> 4.1. There are no holes in padstacks on import </h3>
<p>
The DSN format was originally designed for autorouting; an autorouter doesn't
need to know the geometry of a hole, assuming copper annulus is always around
the hole. Thus old versions of the file format simply does not have a way
to describe holes.
<p>
Some software extended the format and use a <i>hole</i> directive that pcb-rnd
picks up - but if the file does not contain holes, pcb-rnd can't improvise them.
<p>
You can use query() to find offending padstacks and use propset() or
the padstack editor to install the holes.
<h3> 4.2. There are no silk graphics on subcircuits after import </h3>
<p>
The DSN format does not specify silk. There are outline and keepout objects
in the format and pcb-rnd loads them on special purpose documentation layers.
The use of these objects vary from tool to tool - some tools will draw the
bounding box of the part using lines on the outline layer, but other tools
may just draw a large, rectangular filled polygon.
<p>
Use the per subcircuit layer bindings to map them on a board silk layer.
<h3> 4.3. Missing solder mask cutouts and solder paste patterns after import </h3>
<p>
The DSN format does not specify solder mask or paste. Please use the padstack
editor on the affected padstacks.
<h2 id="build"> 5. build/install </h2>
<h3> 5.1. Error while loading shared libraries </h3>
<p>
If the above error message appears and lists librnd-* libs when executing
pcb-rnd, that means your operating system's dynamic loader is unable to
find There are trhee common reasons for this:
<ul>
<li> pcb-rnd is installed from binary and librnd is not installed. Install librnd.
<li> librnd is installed from source to standard installation prefix (/usr or /usr/local); on some systems ldconfig needs to be run after installing new libs from source so that the system's dynamic loader can find the new .so files
<li> librnd is installed from source to a non-standard installation prefix, e.g. installation in home directory or /opt; see <a href="INSTALL.librnd.txt">INSTALL.librnd.txt</a> for the extra steps this setup requires
</ul>
<h2 id="gui"> 6. GUI </h2>
<p>
<h3> 6.1. icons too small </h3>
<p>
If you use a high DPI screen and icon buttons (e.g. in the top left toolbar)
and icons are too small but text buttons and text labels are properly sized,
you need to configure plugins/hid_gtk/icon_scale to 2 or 3, preferrably on
user role and then restart pcb-rnd.
</body>
</html>
|
