| blob | f0c85770c847a04be19dd2bcd676b37b6a419ee3 |
5 <head>
12 <link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php" title="geda Wiki" />
15 <link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php" />
16 <link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda" />
17 <link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gschem" />
18 <link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gschem" />
22 </head>
23 <body>
30 <li class="level1"><div class="li"><span class="li"><a href="#general" class="toc">General</a></span></div>
32 <li class="level2"><div class="li"><span class="li"><a href="#i_found_a_bug_what_can_i_do_about_it" class="toc">I found a bug! What can I do about it?</a></span></div></li>
33 </ul>
34 </li>
35 <li class="level1"><div class="li"><span class="li"><a href="#gschem_usage" class="toc">Gschem usage</a></span></div>
37 <li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_a_component" class="toc">How do I move a component?</a></span></div></li>
38 <li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_components_without_dragging_a_tail_of_connectet_nets" class="toc">How do I move components without dragging a tail of connectet nets?</a></span></div></li>
39 <li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_size_of_the_text_on_a_symbol" class="toc">How do I change the size of the text on a symbol?</a></span></div></li>
40 <li class="level2"><div class="li"><span class="li"><a href="#how_do_i_unlock_a_locked_component" class="toc">How do I unlock a locked component</a></span></div></li>
41 <li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic" class="toc">How can I get refdes automatically numbered when I draw a schematic?</a></span></div></li>
42 <li class="level2"><div class="li"><span class="li"><a href="#what_is_a_bus_and_how_do_i_use_it" class="toc">What is a Bus and how do I use it?</a></span></div></li>
43 <li class="level2"><div class="li"><span class="li"><a href="#how_can_i_change_key_bindings_in_gschem" class="toc">How can I change Key Bindings in gschem?</a></span></div></li>
44 <li class="level2"><div class="li"><span class="li"><a href="#what_are_the_mouse_bindings_in_gschem" class="toc">What are the mouse bindings in gschem?</a></span></div></li>
45 <li class="level2"><div class="li"><span class="li"><a href="#can_gschem_do_hierarchical_designs_with_sub_sheets" class="toc">Can gschem do hierarchical designs with sub sheets?</a></span></div></li>
46 </ul>
47 </li>
48 <li class="level1"><div class="li"><span class="li"><a href="#gschem_symbols" class="toc">gschem symbols</a></span></div>
50 <li class="level2"><div class="li"><span class="li"><a href="#what_s_this_business_about_heavy_vs._light_symbols" class="toc">What's this business about heavy vs. light symbols?</a></span></div></li>
51 <li class="level2"><div class="li"><span class="li"><a href="#i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid" class="toc">I am using a symbol out of the library. How come it's not aligned to the grid?</a></span></div></li>
52 <li class="level2"><div class="li"><span class="li"><a href="#is_there_an_explicit_no_connect_symbol_that_i_can_should_place_in_the_schematic_to_prevent_gnetlist_from_thinking_i_ve_forgotten_a_connection" class="toc">Is there an explicit "no connect" symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?</a></span></div></li>
53 <li class="level2"><div class="li"><span class="li"><a href="#how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic" class="toc">How do I promote an invisible symbol attribute into the schematic?</a></span></div></li>
54 <li class="level2"><div class="li"><span class="li"><a href="#what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit" class="toc">What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?</a></span></div></li>
55 <li class="level2"><div class="li"><span class="li"><a href="#is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it" class="toc">Is there a specification or manual for creating gschem symbols? Where is it?</a></span></div></li>
56 </ul>
57 </li>
58 <li class="level1"><div class="li"><span class="li"><a href="#gschem_configuration_customization" class="toc">Gschem configuration/customization</a></span></div>
60 <li class="level2"><div class="li"><span class="li"><a href="#how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory" class="toc">How do I configure my local gafrc to find my local symbol directory?</a></span></div></li>
61 <li class="level2"><div class="li"><span class="li"><a href="#how_can_i_change_the_default_size_of_floating_text" class="toc">How can I change the default size of floating text?</a></span></div></li>
62 <li class="level2"><div class="li"><span class="li"><a href="#how_can_i_have_a_different_background_color_other_than_black" class="toc">How can I have a different background color other than black?</a></span></div></li>
63 <li class="level2"><div class="li"><span class="li"><a href="#each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it" class="toc">Each time I start gschem, the log message window is shown. Can I disable it?</a></span></div></li>
64 </ul>
65 </li>
66 <li class="level1"><div class="li"><span class="li"><a href="#printing_output" class="toc">Printing/Output</a></span></div>
68 <li class="level2"><div class="li"><span class="li"><a href="#how_do_i_print_schematics_from_the_command_line" class="toc">How do I print schematics from the command line?</a></span></div></li>
69 <li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_color_postscript_png_output" class="toc">How can I get color postscript/PNG output?</a></span></div></li>
70 <li class="level2"><div class="li"><span class="li"><a href="#how_can_i_get_black_and_white_postscript_png_output" class="toc">How can I get black and white postscript/PNG output?</a></span></div></li>
71 <li class="level2"><div class="li"><span class="li"><a href="#how_can_i_insert_schematics_into_my_latex_document" class="toc">How can I insert schematics into my LaTex document?</a></span></div></li>
72 <li class="level2"><div class="li"><span class="li"><a href="#how_can_i_split_postscript_output_over_multiple_pages" class="toc">How can I split Postscript output over multiple pages?</a></span></div></li>
73 </ul>
74 </li>
75 <li class="level1"><div class="li"><span class="li"><a href="#gschem_installation_run-time_problems" class="toc">Gschem installation/run-time problems</a></span></div>
77 <li class="level2"><div class="li"><span class="li"><a href="#gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around" class="toc">Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?</a></span></div></li>
78 <li class="level2"><div class="li"><span class="li"><a href="#after_installation_gschem_does_not_work_what_could_be_wrong" class="toc">After installation gschem does not work!? What could be wrong?</a></span></div></li>
79 <li class="level2"><div class="li"><span class="li"><a href="#add_components_offers_no_symbols_what_can_i_do_about_it" class="toc">"Add Components" offers no symbols! What can I do about it?</a></span></div></li>
80 <li class="level2"><div class="li"><span class="li"><a href="#i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0" class="toc">I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension "RENDER" missing on display "localhost:10.0".'</a></span></div></li></ul>
81 </li></ul>
82 </div>
83 </div>
90 </div>
91 <!-- SECTION "General" [1-24] -->
92 <h2><a name="i_found_a_bug_what_can_i_do_about_it" id="i_found_a_bug_what_can_i_do_about_it">I found a bug! What can I do about it?</a></h2>
94 <ol>
96 </li>
97 <li class="level1"><div class="li"> Ask on the <a href="http://www.geda.seul.org/mailinglist/index.html" class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html" rel="nofollow">geda-user mailing</a> list if there is a work around, or has been dealt with in the bleeding edge version of gEDA/gaf. Note, that you must subscribe to the geda-user e-mail list before you can post to this list.</div>
98 </li>
99 <li class="level1"><div class="li"> See whether the issue is already in the <a href="http://sourceforge.net/tracker/?group_id=161080&atid=818426" class="urlextern" title="http://sourceforge.net/tracker/?group_id=161080&atid=818426" rel="nofollow">bug tracking system of geda/gaf</a>. If not, file a bug report. Make sure to give all information necessary to reproduce the bug and add the version of gEDA/gaf that contains the bug.</div>
100 </li>
101 <li class="level1"><div class="li"> Finally, as with all open source projects, you may flex your programming muscles and try to fix the bug yourself. Please file a patch of the changes you had to make to the BTS of geda/gaf. The patch will be gladly accepted to improve the next release of gEDA/gaf.</div>
102 </li>
103 </ol>
105 </div>
106 <!-- SECTION "I found a bug! What can I do about it?" [25-946] -->
110 </div>
111 <!-- SECTION "Gschem usage" [947-974] -->
112 <h2><a name="how_do_i_move_a_component" id="how_do_i_move_a_component">How do I move a component?</a></h2>
115 <p>
116 This is no longer an issue; moving a component can be done using the left mouse button – the method most familiar to Windows users. In versions equal to or later than 20060824, do this:
117 </p>
118 <ol>
119 <li class="level1"><div class="li"> Select the component by clicking it with the left mouse button. The component will highlight.</div>
120 </li>
121 <li class="level1"><div class="li"> Drag the component (using the left mouse button) to the place you want it.</div>
122 </li>
123 </ol>
125 <p>
126 This is probably what you are already used to doing.
127 </p>
129 <p>
130 For folks with older versions of gschem, here are three ways to easily move components with gschem:
131 </p>
133 <p>
134 One:
135 </p>
136 <ol>
137 <li class="level1"><div class="li"> Grab the component with the middle mouse button. The component will follow the cursor around as you move it.</div>
138 </li>
139 <li class="level1"><div class="li"> To place the component, release the middle mouse button. The component will stay where you placed it.</div>
140 </li>
141 </ol>
143 <p>
144 Two:
145 </p>
146 <ol>
147 <li class="level1"><div class="li"> Select the component by clicking it with the left mouse button. The component will highlight.</div>
148 </li>
149 <li class="level1"><div class="li"> Hit the “M” key on the keyboard. The component will now follow the cursor around as you move it.</div>
150 </li>
151 <li class="level1"><div class="li"> To place the component, click the left mouse button. The component will stay where you placed it.</div>
152 </li>
153 </ol>
155 <p>
156 Three:
157 </p>
158 <ol>
159 <li class="level1"><div class="li"> Select the component by clicking it with the left mouse button. The component will highlight.</div>
160 </li>
161 <li class="level1"><div class="li"> Click the right mouse button. A pop-up menu will appear.</div>
162 </li>
163 <li class="level1"><div class="li"> With the left mouse button, click on the “move” option in the pop-up menu.</div>
164 </li>
165 <li class="level1"><div class="li"> Click on the component with the left mouse button. The component will now follow the cursor around as you move it.</div>
166 </li>
167 <li class="level1"><div class="li"> To place the component, click the left mouse button. The component will stay where you placed it.</div>
168 </li>
169 </ol>
171 </div>
172 <!-- SECTION "How do I move a component?" [975-2543] -->
173 <h2><a name="how_do_i_move_components_without_dragging_a_tail_of_connectet_nets" id="how_do_i_move_components_without_dragging_a_tail_of_connectet_nets">How do I move components without dragging a tail of connectet nets?</a></h2>
176 <p>
177 Type [or] to toggle this behaviour. That is, the “o” key followed by the “r” key. The status window will report if the toggle command was performed. The command can also be accessed via the Options menu.
178 </p>
180 </div>
181 <!-- SECTION "How do I move components without dragging a tail of connectet nets?" [2544-2828] -->
182 <h2><a name="how_do_i_change_the_size_of_the_text_on_a_symbol" id="how_do_i_change_the_size_of_the_text_on_a_symbol">How do I change the size of the text on a symbol?</a></h2>
184 <ol>
186 </li>
187 <li class="level1"><div class="li"> Right click → down symbol (or do Hierarchy → down symbol). This takes you to the symbol editor.</div>
188 </li>
190 </li>
192 </li>
194 </li>
196 </li>
198 </li>
199 <li class="level1"><div class="li"> Right click → up (or Hierarchy → Up). Now you are back in the schematic editor.</div>
200 </li>
201 <li class="level1"><div class="li"> With the symbol still selected do Edit → Update component (or use the keyboard shortcut “ep”). If this doesn’t work, just delete the symbol and reload it.</div>
202 </li>
203 </ol>
205 <p>
206 More generally, you can use this procedure to edit anything on a symbol. (Substitute “Edit Text” for your desired edit, of course.)
207 </p>
209 </div>
210 <!-- SECTION "How do I change the size of the text on a symbol?" [2829-3619] -->
211 <h2><a name="how_do_i_unlock_a_locked_component" id="how_do_i_unlock_a_locked_component">How do I unlock a locked component</a></h2>
214 <p>
215 When a component is locked it cannot be selected with the middle mouse button; however it is selectable using a window select. To window select a component, click and hold the left mouse button and drag the mouse to create a rectangular region containing the component to be unlocked. Execute the command <strong><em>Edit</em></strong> <strong>→</strong> <strong><em>unLock</em></strong> to unlock the component.
216 </p>
218 </div>
219 <!-- SECTION "How do I unlock a locked component" [3620-4033] -->
220 <h2><a name="how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic" id="how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic">How can I get refdes automatically numbered when I draw a schematic?</a></h2>
223 <p>
224 Edit the system-gschemrc file or place the following into a gschemrc file (either <strong><code>~/.gEDA/gschemrc</code></strong> or a <strong><code>gschemrc</code></strong> file in the local directory where you invoke gschem):
225 </p>
227 (load (string-append gedadata "/scheme/auto-uref.scm")) ; load the autonumbering script
228 (add-hook! add-component-hook auto-uref) ; autonumber when adding a component
229 (add-hook! copy-component-hook auto-uref) ; autonumber when copying a component
230 </pre>
232 <p>
233 Please substitute $YOUR_INSTALL_PATH by the path where geda is installed.
234 </p>
236 </div>
237 <!-- SECTION "How can I get refdes automatically numbered when I draw a schematic?" [4034-4645] -->
238 <h2><a name="what_is_a_bus_and_how_do_i_use_it" id="what_is_a_bus_and_how_do_i_use_it">What is a Bus and how do I use it?</a></h2>
241 <p>
242 A ‘bus’ is purely decoration. The netlister ignores it. The netname= attribute does actual work of connecting points together–this is what gnetlist reads and transforms into your netlist. It is not possible to connect to a discrete line or ‘bit’ on a bus because, again, the bus is merely a graphical entity.
243 </p>
245 <p>
246 Some users have found it helpful to organize their nets by incorporating a bus name into the net name. For example “net=busA:1” may be added to each busripper to aid in sorting out the nets.
247 </p>
249 </div>
250 <!-- SECTION "What is a Bus and how do I use it?" [4646-5201] -->
251 <h2><a name="how_can_i_change_key_bindings_in_gschem" id="how_can_i_change_key_bindings_in_gschem">How can I change Key Bindings in gschem?</a></h2>
254 <p>
255 Key accels are determined by configuration files read on start-up. The default key bindings are set in the file system-gschemrc. If you want to change them, it is recommended to copy and modify the corresponding keymap section to a local config file ($HOME/.gEDA/gschemrc, or $PWD/gschemrc). The modified section will override the the definitions given in system-gschemrc.
256 </p>
258 </div>
259 <!-- SECTION "How can I change Key Bindings in gschem?" [5202-5628] -->
260 <h2><a name="what_are_the_mouse_bindings_in_gschem" id="what_are_the_mouse_bindings_in_gschem">What are the mouse bindings in gschem?</a></h2>
263 <p>
264 By default you get:
265 </p>
266 <ul>
268 </li>
269 <li class="level1"><div class="li"> Middle mouse button is either move object (just hold down the middle button over an object and move the mouse) or copy object (ALT key held down while holding down the middle button over object and move the mouse).</div>
270 </li>
272 </li>
273 </ul>
275 <p>
276 You can change the middle button by adding the following to a gschemrc file:
277 </p>
278 <pre class="code">(middle-button "action") ;default binding, move or copy an object</pre>
280 <p>
281 or:
282 </p>
283 <pre class="code">(middle-button "stroke") ;draw mouse gestures/strokes (must install libstroke to enable</pre>
285 <p>
286 or:
287 </p>
290 <p>
291 You can change the right button by adding the following to a gschemrc file:
292 </p>
295 <p>
296 or:
297 </p>
298 <pre class="code">(third-button "mousepan") ;use the mouse to pan around the schematic</pre>
300 <p>
301 For more information on these options, please see the <code>${install_prefix}/share/gEDA/system-gschemrc</code> file.
302 </p>
304 </div>
305 <!-- SECTION "What are the mouse bindings in gschem?" [5629-6711] -->
306 <h2><a name="can_gschem_do_hierarchical_designs_with_sub_sheets" id="can_gschem_do_hierarchical_designs_with_sub_sheets">Can gschem do hierarchical designs with sub sheets?</a></h2>
309 <p>
310 Yes. Sub sheets are represented by special symbols on the top level schematic. You can find an example for a hierarchical design in the doc section of gschem (<code>geda-doc/examples/gTAG/gTAG.sch</code>). Currently, there is no way to automatically build a sub sheet symbol from an actual sub sheet. The sub sheet symbol has to be drawn manually. Any patches or external scripts that get the job done would be greatly appreciated.
311 </p>
313 <p>
314 A source attribute attached to the sub sheet symbol gives the path to the sub sheet file. The pins of the symbol correspond to ports from top sheet to sub sheet. These ports should correspond to a refdes of a port symbol on the sub sheet. The port symbols in the default library of geda are <code>in-1.sym</code> and <code>out-1.sym</code>. Use the hierarchy menu to navigate within the hierarchy of sub sheets. Alternatively, you can navigate with the page manager.
315 </p>
317 <p>
318 To convert a hierarchy to a netlist just call gsch2pcb on the top level schematic. By default, net names and refdes’s of components are strictly local to the subsheet. They get the sub sheet symbol refdes as a prefix when inserted into the net list. You can even use multiple instances of a sub sheet symbol without undue short cuts. Whether or not net names and refdes’s are mangled and thus local to the sub sheet can be configured in the config file gnetlistrc. Copy the corresponding lines from <code>system-gnetlistrc</code> to <code>gnetlistrc</code> in the current working directory or to <code>$HOME/.gEDA/gnetlistrc</code>. A convenient configuration is to make nets delivered by power symbols global while ordinary nets remain local to the sub sheet. This can be achieved with “hierarchy-netattrib-mangle” enabled.
319 </p>
321 </div>
322 <!-- SECTION "Can gschem do hierarchical designs with sub sheets?" [6712-8449] -->
326 </div>
327 <!-- SECTION "gschem symbols" [8450-8479] -->
328 <h2><a name="what_s_this_business_about_heavy_vs._light_symbols" id="what_s_this_business_about_heavy_vs._light_symbols">What's this business about heavy vs. light symbols?</a></h2>
331 <p>
332 This nomenclature arose from a discussion which frequently appears on the geda-user and geda-dev mailing lists. A light symbol is one which contains very few built-in attributes in the symbol itself. It requires that the user attach almost all attributes at the schematic level (e.g. using either gschem or gattrib). A heavy symbol is one which contains many attributes (such as package footprints, SPICE model names, etc.) built into the symbol file itself. A heavy symbol therefore requires very little attribute attachment at the schematic level – you just place it and you’re done.
333 </p>
335 <p>
336 The debate between proponents of heavy and light symbols is very detailed and involved. Briefly, proponents of heavy symbols believe that they provide better integration between gschem and PCB since the important layout attributes (such as <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">footprint name</a>) are already built into the symbol. This is considered a good thing for new users (noobs) who just want to design a simple board and don’t appreciate or don’t care about the zillions of variations that even a simple resistor might have (e.g. different footprint, TCR, precision, material composition, etc). Proponents of light symbols prefer to deal with attributes at the schematic level because they believe it to be more flexible. They are quick to point out that a library of heavy symbols will quickly grow into the thousands of parts with grotesquely long names trying to distinguish between the different variations of the part. They also point out that the utility “gattrib” is the preferred tool for dealing with attributes at the schematic level (i.e. in the .sch file).
337 </p>
339 <p>
340 GEDA/gaf, as default configured, uses light symbols, although it can be configured to use heavy symbols. For further information, you may read these dicussions from the geda-user mailing list:
341 </p>
343 <p>
344 <a href="http://archives.seul.org/geda/user/Jun-2005/msg00001.html" class="urlextern" title="http://archives.seul.org/geda/user/Jun-2005/msg00001.html" rel="nofollow">http://archives.seul.org/geda/user/Jun-2005/msg00001.html</a>
345 </p>
347 <p>
348 <a href="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html" class="urlextern" title="http://archives.seul.org/geda/dev/Oct-2005/msg00043.html" rel="nofollow">http://archives.seul.org/geda/dev/Oct-2005/msg00043.html</a>
349 </p>
351 </div>
352 <!-- SECTION "What's this business about heavy vs. light symbols?" [8480-10608] -->
353 <h2><a name="i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid" id="i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid">I am using a symbol out of the library. How come it's not aligned to the grid?</a></h2>
356 <p>
357 The symbols in the symbol library, like those available at the <a href="http://www.gedasymbols.org/" class="urlextern" title="http://www.gedasymbols.org" rel="nofollow"> gedasymbols</a> website are contributed by users just like you. Some people use different grid settings than other people (e.g. 50mil vs. 100mil). If you discover a symbol which seems to be off the grid, try reducing your grid spacing, move the symbol so that it sits on <strong>your</strong> grid, then revert to your preferred grid settings.
358 </p>
360 <p>
361 Yes, the gEDA docs suggest that you use a 100mil grid spacing. But everybody likes to do things their own way, and there is no overall symbol dictator to enforce the rules on contributed symbols. Therefore, you just need to be aware of this possibility.
362 </p>
364 </div>
365 <!-- SECTION "I am using a symbol out of the library. How come it's not aligned to the grid?" [10609-11382] -->
366 <h2><a name="is_there_an_explicit_no_connect_symbol_that_i_can_should_place_in_the_schematic_to_prevent_gnetlist_from_thinking_i_ve_forgotten_a_connection" id="is_there_an_explicit_no_connect_symbol_that_i_can_should_place_in_the_schematic_to_prevent_gnetlist_from_thinking_i_ve_forgotten_a_connection">Is there an explicit "no connect" symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?</a></h2>
369 <p>
370 Answer: misc → nc-left, nc-right, nc-top, nc-bottom.
371 </p>
373 <p>
374 Caution: occassionally this may create a net called “no_connect” (or “NC??") which may lead to no-connect pins being connected together in gnetlist – which you probably _don’t_ want to happen.
375 </p>
377 <p>
378 If you want an entire symbol to be graphical (no elec. connections) , add a “graphical=1” attribute. The netlister will ignore these symbols entirely.
379 </p>
381 </div>
382 <!-- SECTION "Is there an explicit no connect symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?" [11383-11952] -->
383 <h2><a name="how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic" id="how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic">How do I promote an invisible symbol attribute into the schematic?</a></h2>
386 <p>
387 Most attributes living in the symbol do not get promoted to the schematic unless they are visible. To promote invisible symbol attributes, look for the following keywords in the system-gschemrc file:
388 </p>
393 <p>
394 Add to your gschemrc file:
395 </p>
398 <p>
399 and you will get all the attributes promoted. The “keep-invisible” keyword will keep hidden those attributes that are hidden in the symbol file.
400 </p>
402 </div>
403 <!-- SECTION "How do I promote an invisible symbol attribute into the schematic?" [11953-12572] -->
404 <h2><a name="what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit" id="what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit">What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?</a></h2>
407 <p>
408 In the past, digital logic circuits often hid the power pin, and attached power nets using an attribute inside the symbol. Modern thought is that this is a bad practice (although religious wars still occasionally rage about this topic).
409 </p>
411 <p>
412 It’s marginally OK for an old logic circuit which is all 5V TTL to have hidden power and GND pins. If you only have +5V on your board, then hiding the power pin can simplify your schematic somewhat. However, few designers design such circuits nowadays; 5V TTL (and 5V CMOS) are rapidly becoming antique technologies.
413 </p>
415 <p>
416 It’s always been unacceptable to hide the power pins on analog chips. First, analog often has multiple power connections (VCC, VEE) which need to be explicitly drawn out. Second, good design practice is to place decoupling caps on each and every power pin. Sometimes one places an inductor in series with power also. Since these should be drawn into the schematic, it is best done by attaching them to an explicit power pin. Therefore, one should never use hidden power pins for analog symbols.
417 </p>
419 <p>
420 New logic circuits often use multiple supplies for different chip sections (OVDD, DVDD, etc). It is also typical to have several logic families on a single board (5V, 3.3V etc.). Therefore, it’s best to explicitly place and wire the power pins on the symbol. Hidden power pins are a recipe for disaster since you can all too easily misconnect a 5V part to a 3.3V power net, for example.
421 </p>
423 <p>
424 To paraphrase Nancy Reagan: Just say “no” to hidden power pins.
425 </p>
427 <p>
428 That said, it may still be useful to detach the power pins from the functional part of the symbol. To do so, define a seperate power symbol and give it the same <a href="http://geda.seul.org/wiki/geda:glossary" class="wikilink1" title="geda:glossary">refdes</a> as the functional part. A run of gsch2pcb will treat the siblings properly as one single component. As neither gschem nor gsch2pcb explicitely know that the component is only complete with both symbols defined, you have to check yourself. With this workaround, you can draw all power related circuitry in one corner of the schematic where it does not interfere with the signal nets. In many cases this is advantageous with analog circuits.
429 </p>
431 </div>
432 <!-- SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [12573-14829] -->
433 <h2><a name="is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it" id="is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it">Is there a specification or manual for creating gschem symbols? Where is it?</a></h2>
436 <p>
437 Yes. It is the <a href="geda_scg.html" class="wikilink1" title="geda:scg">Symbol Creation Guide</a>.
438 </p>
440 </div>
441 <!-- SECTION "Is there a specification or manual for creating gschem symbols? Where is it?" [14830-14970] -->
442 <h1><a name="gschem_configuration_customization" id="gschem_configuration_customization">Gschem configuration/customization</a></h1>
445 <p>
446 Gschem is configurable in more ways than can be describe here. Look at “system-gschemrc” for suggestions what else can be done.
447 </p>
449 </div>
450 <!-- SECTION "Gschem configuration/customization" [14971-15148] -->
451 <h2><a name="how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory" id="how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory">How do I configure my local gafrc to find my local symbol directory?</a></h2>
453 <ol>
454 <li class="level1"><div class="li"> Create a project directory, for example ${HOME}/myproj.</div>
455 </li>
456 <li class="level1"><div class="li"> Place the symbols you want to use into ${HOME}/myproj/symbols.</div>
457 </li>
459 </li>
460 <li class="level1"><div class="li"> In gafrc, put this line: <pre class="code"> (component-library "./symbols") </pre>
461 </div>
462 </li>
463 <li class="level1"><div class="li"> Run gschem from your project directory ${HOME}/myproj. That is, do this to run gschem:<pre class="code">cd ${HOME}/myproj
464 gschem myschematic.sch</pre>
465 </div>
466 </li>
467 </ol>
469 <p>
470 Points to remember:
471 </p>
472 <ul>
473 <li class="level1"><div class="li"> The guile stuff which processes your RC file doesn’t understand or expand shell wildcards like "~" or ${HOME}. It does understand "." as the current working directory, and it does understand absolute file paths. If you want to do something tricky, you can try to use Scheme functions to get directory information.</div>
474 </li>
475 <li class="level1"><div class="li"> Make sure gafrc lives in your main project directory. </div>
476 </li>
477 <li class="level1"><div class="li"> Run all gEDA programs from your main project directory. </div>
478 </li>
479 <li class="level1"><div class="li"> Run the programs from the command line in a terminal shell – don’t use any whizzy, shiny desktop icons to run gschem (if you have them) since you won’t know what directory gschem is starting in, and gschem might not find gafrc.</div>
480 </li>
481 <li class="level1"><div class="li"> The key is: start gschem in the same directory as where your gafrc lives.</div>
482 </li>
483 </ul>
485 </div>
486 <!-- SECTION "How do I configure my local gafrc to find my local symbol directory?" [15149-16402] -->
487 <h2><a name="how_can_i_change_the_default_size_of_floating_text" id="how_can_i_change_the_default_size_of_floating_text">How can I change the default size of floating text?</a></h2>
490 <p>
491 Put
492 </p>
495 <p>
496 into your gschemrc and replace “10” with your favorite size.
497 </p>
499 </div>
500 <!-- SECTION "How can I change the default size of floating text?" [16403-16561] -->
501 <h2><a name="how_can_i_have_a_different_background_color_other_than_black" id="how_can_i_have_a_different_background_color_other_than_black">How can I have a different background color other than black?</a></h2>
504 <p>
505 Edit the system-gschemrc file and near the top you will find lines like:
506 </p>
508 ; Start of color section
509 ;
510 ; Load up a color scheme has a light (almost white) background
511 ; Comment out the first line and comment in the second line for a
512 ; dark (black) background. The dark background is the original look.
513 ;
517 <p>
518 Comment out the <strong><code>darkbg</code></strong> line (with a ;) and comment in the <strong><code>lightbg</code></strong> line. This will give you a light background instead of a black background. It also adjust all the other colors to be compatible with a light background.
519 </p>
521 <p>
522 If you want more control over the colors, please edit <strong><code>${prefix}/share/gEDA/gschem-darkbg</code></strong> or <strong><code>${prefix}/share/gEDA/gschem-lightbg</code></strong> or create your own file and load it in the <strong><code>system-gschemrc</code></strong> file.
523 </p>
525 <p>
526 A dark background is preferred by many users.
527 </p>
529 </div>
530 <!-- SECTION "How can I have a different background color other than black?" [16562-17597] -->
531 <h2><a name="each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it" id="each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it">Each time I start gschem, the log message window is shown. Can I disable it?</a></h2>
534 <p>
535 In the system-gschemrc file, you will find the following section:
536 </p>
538 ; log-window string
539 ;
540 ; Controls if the log message window is mapped when gschem is started up
541 ; Possible options:
542 ; startup - opened up when gschem starts
543 ; later - NOT opened up when gschem starts
544 ; (can be opened by Options/Show Log Window)
545 ;
549 <p>
550 Comment out the <strong><code>startup</code></strong> line (with a ;) and comment in the <strong><code>later</code></strong> line, or add the following line to your gschemrc file:
551 </p>
554 </div>
555 <!-- SECTION "Each time I start gschem, the log message window is shown. Can I disable it?" [17598-18260] -->
559 </div>
560 <!-- SECTION "Printing/Output" [18261-18290] -->
561 <h2><a name="how_do_i_print_schematics_from_the_command_line" id="how_do_i_print_schematics_from_the_command_line">How do I print schematics from the command line?</a></h2>
564 <p>
565 Running the script <strong><code>gschem-print.scm</code></strong> will create the Postscript file that is specified on the command line.
566 </p>
568 <p>
569 The command line below creates a Postscript file from a schematic file (replace MY_SCH with the name of your schematic and GEDA_SCHEME_DIR with the name of the directory where your gEDA scheme files are installed):
570 </p>
573 <p>
574 The <code>bash</code> script below, which I name <strong><code>gschem-print</code></strong>, creates a Postscript file for each schematic file that is specified on the command line and then outputs each Postscript file to the default printer:
575 </p>
578 # gschem options
579 # -oPS_FILENAME output to Postscript file PS_FILENAME
580 # -sSCRIPT_FILENAME run script SCRIPT_FILENAME
581 # -p autoplace windows
583 for name in $*
584 do
586 gschem -p -o$base.ps -sGEDA_SCHEME_DIR/gschem-print.scm $base.sch
587 lpr -P$PRINTER $base.ps
588 done</pre>
590 </div>
591 <!-- SECTION "How do I print schematics from the command line?" [18291-19288] -->
592 <h2><a name="how_can_i_get_color_postscript_png_output" id="how_can_i_get_color_postscript_png_output">How can I get color postscript/PNG output?</a></h2>
595 <p>
596 Edit the <strong><code>system-gschemrc</code></strong> file or place the following into a <strong><code>gschemrc</code></strong> file (either <strong><code>~/.gEDA/gschemrc</code></strong> or a <strong><code>gschemrc</code></strong> file in the local directory where you invoke gschem):
597 </p>
601 <p>
602 To control the background of the PS output, change the following line in either gschem-darkbg (for the default black colored background) or gschem-lightbg (for the alternative light colored background):
603 </p>
604 <pre class="code">(output-color-background 16 "black" "null" "0 0 0" 0 0 0)</pre>
606 <p>
608 </p>
610 <p>
611 To control the background of the <acronym title="Portable Network Graphics">PNG</acronym> output, change the following line in either gschem-darkbg (for the default black colored background) or gschem-lightbg (for the alternative light colored background):
612 </p>
613 <pre class="code">(background-color 0 "grey94" "null" "1 1 1" 255 255 255)</pre>
615 <p>
616 The 255 255 255 are the RGB components for the background color of the <acronym title="Portable Network Graphics">PNG</acronym> image.
617 </p>
619 </div>
620 <!-- SECTION "How can I get color postscript/PNG output?" [19289-20420] -->
621 <h2><a name="how_can_i_get_black_and_white_postscript_png_output" id="how_can_i_get_black_and_white_postscript_png_output">How can I get black and white postscript/PNG output?</a></h2>
624 <p>
625 For black and white PS output, place the following into a gschemrc file:
626 </p>
629 <p>
630 For black and white <acronym title="Portable Network Graphics">PNG</acronym> images, place the following into a gschemrc file:
631 </p>
634 </div>
635 <!-- SECTION "How can I get black and white postscript/PNG output?" [20421-20786] -->
636 <h2><a name="how_can_i_insert_schematics_into_my_latex_document" id="how_can_i_insert_schematics_into_my_latex_document">How can I insert schematics into my LaTex document?</a></h2>
638 <ol>
639 <li class="level1"><div class="li"> Print the schematic to a file. This will be generic postscript (*.ps).</div>
640 </li>
641 <li class="level1"><div class="li"> Convert the postscript file to epsi with the tool ps2epsi. This is a script from the ghostscript suite.</div>
642 </li>
643 <li class="level1"><div class="li"> Include usepackage{graphicx} to the preamble of your latex document. Use the command <strong>includegraphics</strong> to place your schematic.</div>
644 </li>
645 </ol>
647 <p>
648 A simple example:
649 </p>
651 \usepackage{graphicx}
652 \begin{document}
653 \begin{image}
654 \includegraphics[width=100mm]{ModulPID.epsi}
655 \end{image}
656 \end{document}</pre>
658 </div>
659 <!-- SECTION "How can I insert schematics into my LaTex document?" [20787-21355] -->
660 <h2><a name="how_can_i_split_postscript_output_over_multiple_pages" id="how_can_i_split_postscript_output_over_multiple_pages">How can I split Postscript output over multiple pages?</a></h2>
663 <p>
664 gschem does not provide this functionality internally, however there is a program called “poster” which does exactly this. It can be downloaded from either <a href="http://www.gnu.org/directory/poster.html" class="urlextern" title="http://www.gnu.org/directory/poster.html" rel="nofollow">here</a> (GNU) or <a href="http://printing.kde.org/downloads/" class="urlextern" title="http://printing.kde.org/downloads/" rel="nofollow">here</a> (KDE Print).
665 </p>
667 </div>
668 <!-- SECTION "How can I split Postscript output over multiple pages?" [21356-21699] -->
669 <h1><a name="gschem_installation_run-time_problems" id="gschem_installation_run-time_problems">Gschem installation/run-time problems</a></h1>
672 </div>
673 <!-- SECTION "Gschem installation/run-time problems" [21700-21752] -->
674 <h2><a name="gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around" id="gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around">Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?</a></h2>
677 <p>
678 This bug emerged in mid 2006 for users of Fedora Core 5 (and other linux distributions that use glib 2.10.x). The bug has been fixed by the developers; the latest versions of gEDA/gaf (i.e. Oct 2006 and beyond) shouldn’t have this problem.
679 </p>
681 <p>
682 If you happen to have an older version of gEDA/gaf, you can work around this bug by setting the environment variable G_SLICE to “always-malloc”. Specifically, before you run gschem, do this:
683 </p>
685 <p>
686 bash:
687 </p>
690 <p>
691 csh:
692 </p>
695 </div>
696 <!-- SECTION "Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?" [21753-22407] -->
697 <h2><a name="after_installation_gschem_does_not_work_what_could_be_wrong" id="after_installation_gschem_does_not_work_what_could_be_wrong">After installation gschem does not work!? What could be wrong?</a></h2>
700 <p>
701 If you run gschem and you get a window without a menu bar, no colors, and the program terminates when you press a key with the following message:
702 </p>
705 <p>
706 Or you get errors like this:
707 </p>
708 <pre class="code">Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULL’ failed.
709 Gtk-CRITICAL : file gtkpixmap.c: line 97 (gtk_pixmap_new): assertion `val != NULL’ failed.
710 Tried to get an invalid color: 0
711 Tried to get an invalid color: 7
712 Tried to get an invalid color: 0
715 <p>
716 then gschem is not finding an rc file. There are two required rc files. The first is <strong><code>system-gschemrc</code></strong> and the second is <strong><code>system-commonrc</code></strong>.
717 </p>
718 <ul>
719 <li class="level1"><div class="li"> The system-gschemrc rc file should be installed when you install gschem and typically resides in <strong><code>${prefix}/share/gEDA/system-gschemrc</code></strong>. <strong><code>${prefix}</code></strong> is where you installed gschem (usually <strong><code>/usr</code></strong> or <strong><code>/usr/local</code></strong> or <strong><code>$HOME/geda</code></strong>). This file can also be installed in /etc/gEDA (the .debs packages do this).</div>
720 </li>
721 <li class="level1"><div class="li"> The system-commonrc rc file should be installed when you install the symbol library for gEDA/gaf. It resides in <strong><code>${prefix}/share/gEDA/system-commonrc</code></strong>. This file can also be installed in <strong><code>/etc/gEDA</code></strong> (the .debs packages do this). This file is not loaded directly by gschem. It is loaded by a “(load …)” in the system-gschemrc rc file.</div>
722 </li>
723 </ul>
725 <p>
726 Make sure these file are installed. The gschem.log file (which is created everytime you run gschem) holds valuable debugging information which should help in determining what is wrong. Check this file for where gschem is looking for the rc files.
727 </p>
729 <p>
730 Also, some older releases of gEDA/gaf had some bugs when the rc files were installed in other locations (other that <strong><code>${prefix}/share/gEDA</code></strong>), so please upgrade to a more current release.
731 </p>
733 </div>
734 <!-- SECTION "After installation gschem does not work!? What could be wrong?" [22408-24331] -->
735 <h2><a name="add_components_offers_no_symbols_what_can_i_do_about_it" id="add_components_offers_no_symbols_what_can_i_do_about_it">"Add Components" offers no symbols! What can I do about it?</a></h2>
738 <p>
739 Make sure that at least one of your config files contains a valid path to a symbol library. At startup, gschem checks for the following config files (on a Debian system):
740 </p>
741 <ol>
742 <li class="level1"><div class="li"> system gafrc file: <code>/etc/gEDA/system-gafrc</code></div>
743 </li>
745 </li>
747 </li>
748 <li class="level1"><div class="li"> system gschemrc file: <code>/etc/gEDA/system-gschemrc</code></div>
749 </li>
751 </li>
753 </li>
754 </ol>
756 <p>
757 All of these config files may or may not append paths to the library search list. If a config file conatins the command
758 </p>
761 <p>
762 the library search path will be emptied. Order is obviously important, as this command will erase any previously appended paths.
763 </p>
765 </div>
766 <!-- SECTION "Add Components offers no symbols! What can I do about it?" [24332-25135] -->
767 <h2><a name="i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0" id="i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0">I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension "RENDER" missing on display "localhost:10.0".'</a></h2>
770 <p>
771 If you are getting into the remote machine by doing:
772 </p>
775 <p>
776 and afterwards you get the Xlib RENDER message, then try using:
777 </p>
780 <p>
781 The latter enables trusted X11 forwarding.
782 </p>
784 </div>
785 <!-- SECTION "I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension RENDER missing on display localhost:10.0.'" [25136-] --></div>
786 </body>
787 </html>