gEDA-user: Panelizing methods?

2007-02-01 Thread Lares Moreau
Heya List :)

Any suggestion on the best way of makeing seperations in a panel using only the 
drillholes available on the cheaper PCB services.  I was thinking of placing a 
bunch of .090 holes .100 apart. Then it's a snap and file when the panel gets 
here.

The panel is not uniform, there are 4 different boards on the same panel.

Thoughts?

-Lares


pgphPHYJcsbsM.pgp
Description: PGP signature


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Panelizing methods?

2007-02-01 Thread John Luciani

On 2/1/07, Lares Moreau [EMAIL PROTECTED] wrote:

Heya List :)

Any suggestion on the best way of makeing seperations in a panel using only the drillholes  
available on the cheaper PCB services.  I was thinking of placing a bunch of .090 holes 
 .100 apart. Then it's a snap and file when the panel gets here.


Check with your PCB service to verify that they allow perforations
(and panelizing).
Some don't.

I usually draw silkscreen lines 100-150mils from the edge of the board and
use a bandsaw or a hacksaw.

(* jcl *)


--
http://www.luciani.org


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: SPICE gaf

2007-02-01 Thread Scott Dattalo
Stuart's tutorials on using SPICE with gaf are well written and easy to 
follow. Unfortunately, they need to be updated. Specifically, loading 
the schematics in gEDA/examples/RF_Amp (which are packaged in the 
20061020 gaf release), give warnings like:


Loading schematic [/home/scott/projects/platypus/spice/ex_RF/MSA-2643.sch]
WARNING: Symbol version mismatch on refdes C1 (capacitor-1.sym):
  Symbol in library is newer than instantiated symbol
  Minor version change (file 0.100, instantiated 0.000)

Similar warnings also exist when the schematic is netlisted:

$ gnetlist -g spice-sdb -o MSA-2643.cir MSA-2643.sch


However the netlist encounters an error too (and is probably related to 
the warning):


Found a pin [X2] on component [2] which does not have a label!
Using SPICE backend by SDB -- Version of 12.27.2005
schematic-type = .SUBCKT Q1_MSA26F
ERROR: In procedure :
ERROR: Wrong type argument in position 1: #f

Finally, the SPICE circuit files that are extracted from the RF example 
(and also package in the 20061020 release) fail to run under ngspice 
revision 17 (this version of ngspice is installed by yum -- I don't know 
if this binary had the XSpice option turned on or not). Note, there's a 
hard coded include directive in these examples that one must adjust.


First there's this warning (it appears twice):

Warning -- Level not specified on line (bf=1e6 ikf=5.895e-1 
ise=2.838e-19 ne=1.006   vaf=44 nf=1 tf=5.37e-12 xtf=20 vtf=0.8 
itf=8.872e-1 ptf=22   xtb=0.7 br=1 ikr=4.4e-2 nc=2 var=3.37 nr=1.005 
tr=4e-9   eg=1.17 is=1.79e-17 xti=3 tnom=21 cjc=3.717e-14   vjc=0.6775 
mjc=0.3319 xcjc=4.398e-1 fc=0.8 cje=3.217e-13   vje=0.9907 mje=0.5063 
rb=2.325 irb=3.272e-4 rbm=2.5e-2 kf=1.026e-24)

Using level 1.

And finally, when you run the simulation, there's a convergence error.

1) Has anyone updated the example schematics? I just checked CVS and it 
appears these are 3 years old.

2) Has anyone successfully ran the example SPICE decks under ngspice-17?

I might do (1) -- assuming I can get my setup working.

Thanks,
Scott



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: PCB Silk Screen vs ViewMate

2007-02-01 Thread Ostheller, Joel A.
Well I just successfully tested and signed off on my first gEDA board.
It was a small 5x3 4 layer PCB that I had FAB'd at PCBexpress.com.
Quality wise this board is on par with my last board which was a fairly
complex 16 layer PCB done with Mentor. Hopefully I will never be using
those other programs again =) 

 

Anyways one thing somewhat bothers me and I am sure I just probably did
something wrong. When I view the Silk screen in ViewMate, all the
reference designators are a lot wider then they are when viewed in PCB.
For example, a lower case e in PCB is perfect text, but in ViewMate
there is no hole in the lower case e because the line width is a lot
wider. Now this isn't that big of an issue because you can still make
out everything on the board. But it just makes the silk screen look like
it is out of focus. Oh, and the physical silk screen on the board looks
exactly as it did in ViewMate which is what I expected... 



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: PCB Silk Screen vs ViewMate

2007-02-01 Thread DJ Delorie

 When I view the Silk screen in ViewMate, all the reference
 designators are a lot wider then they are when viewed in PCB.

Known bug.  You can minimize it by making sure the minimum silk screen
is set properly in the board sizes dialog.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: pcb bug(kinda)

2007-02-01 Thread Lares Moreau
PCB version 20060822

:loadVendorFrom()
filename = foo.bar
add a trailing whitespace and it fails.

Is there a better place to post bugs?

-Lares


pgp0KaC1UD1rW.pgp
Description: PGP signature


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: pcb bug(kinda)

2007-02-01 Thread DJ Delorie

 filename = foo.bar
 add a trailing whitespace and it fails.

Unfortunately, spaces are valid characters in unix filenames.

 Is there a better place to post bugs?

There's a sourceforge bug tracker.  Both that and the list have pros
and cons:

list: pro: your bug gets seen.  con: your bug gets lost or forgotten

tracker: pro: your bug gets remembered.  con: you bug might not get seen soon.



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Re: I need to open and print a PCB created in ExpressPCB:What are my options?

2007-02-01 Thread Jeremy Pedersen

I understand how you feel, but with these particular guys at
least...they're very down-to-earth.  Every one of them has shown a
real willingness to help people, even newbies, whenever possible.


Well that's good. I'll be sure to pay close attention to their suggestions.


I've never been a fan of PC
hardware (too slow  cheap-feeling for my taste) so I don't mess
with Linux very much.


I'm limited to x86 hardware because its cheap, so it doesn't matter much to
me if it feels cheap. As for Linux at 13, I can't say I was a very
impressive user. My first memory of running Linux is actually of not running
it. I got a kernel panic on the first try because I didn't know about boot
loaders or about specifying a root= in grub. I know a bit more now, but I
still can't write much more than a basic bash script of a few lines of
assembly. And the PDP-11? Wow, I've only ever read about that thing. :-)


But I've worked with people who
would spend a whole day calculating what I can walk to a bench and
measure in seconds.  THAT is ridiculous.


Yeah. My experience in lab has been that generally the measurements (if
taken properly) are more than accurate enough for troubleshooting and
adjustments. I'm clumsy though, so the calculations (at least the simple
ones) are often faster for me. Breadboarding a full-wave bridge rectifier
takes me 10 to 15 minutes, running the calculations can be done in under 2.
:-/


One other thing to keep in mind.  Hacking on embedded systems will
teach you how to write efficient code, and you can take those skills
right back to big machines at great benefit.  In these days of
Windows morons writing simple programs which require hundreds of
megabytes of RAM...these guys are not programmers.  In the world of
embedded systems, in smaller applications one frequently finds
oneself writing code to run on a system with a few dozen bytes (yes
bytes) of RAM.  And they do *real work*.


That's for sure. Right now we are learning how to program basic stamp
microcontrollers in class, and while I'm not fond of them (they use PBASIC:
a proprietary programming language! Can you believe such a thing?) I can see
how they require efficiency. I write an 820 byte program for one of these
things that would follow a flow chart for troubleshooting diesel engines. It
turned out that by shortening some output messages to the debug terminal and
eliminating some stray CASE statements, the code could be squeezed into 70
bytes! The guy next to me actually didn't use the debug terminal (which
requires a serial port connection to a PC) and managed to get his program
into 20 bytes using dip switches for the simple yes/no questions! I am
uncomfortable in hardware though, so I wasn't willing to use switches. :-(

--
Windows [n.]
A thirty-two bit extension and GUI shell to a sixteen bit patch to an eight
bit operating system originally coded for a four bit microprocessor and sold
by a two-bit company that can't stand one bit of competition.
(Anonymous)

~*~*~*~*~
* JDP :)  *
~*~*~*~*~


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: PCB - grid dots not visible when board is flipped.

2007-02-01 Thread KURT PETERS
I'm sure someone else has noticed this.  I'm using one of the latest CVS 
releases (December-ish) and noticed that the grid dots only show up on one 
side of the board.  Does anyone else notice this?  Is this on the bug 
list?

Regards,
Kurt




___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: PCB - grid dots not visible when board is flipped.

2007-02-01 Thread joeft

KURT PETERS wrote:

I'm sure someone else has noticed this.  I'm using one of the latest 
CVS releases (December-ish) and noticed that the grid dots only show 
up on one side of the board.  Does anyone else notice this?  Is this 
on the bug list?

Regards,
Kurt



This bug has been there for several months.  I looked through the code 
and figured out that it is related to the code that flips the view to 
the solder side.  I believe it is only broken in the GTK hid.  I 
submitted a bug report but I don't think anyone has looked at it yet.


Joe T






___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user





___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: PCB - grid dots not visible when board is flipped.

2007-02-01 Thread DJ Delorie

 This bug has been there for several months.  I looked through the code 
 and figured out that it is related to the code that flips the view to 
 the solder side.  I believe it is only broken in the GTK hid.  I 
 submitted a bug report but I don't think anyone has looked at it yet.

FYI we're looking for a GTK programmer :-)


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: pcb - shell command

2007-02-01 Thread Tom Schouten
hello,

i started using gEDA tools last week to design a small PIC board. 
it looks like a nice suite! finding out gschem uses guile, and 
PCB files are as good as compatible with scheme 'read' made me smile :)

i was wondering though if it is possible to use PCB to directly invoke 
external shell comands, without using them to read or write stuff. basicly 
what i want is to invoke 'make' from PCB, and subsequentally reading in some 
files. i didn't find anything about this in my first read of the PCB doc.

cheers
tom



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: pcb - shell command

2007-02-01 Thread DJ Delorie

 i was wondering though if it is possible to use PCB to directly
 invoke external shell comands, without using them to read or write
 stuff. basicly what i want is to invoke 'make' from PCB, and
 subsequentally reading in some files. i didn't find anything about
 this in my first read of the PCB doc.

It doesn't at the moment, but it would be trivial to add.  Why not try
to add it yourself?  The source file you're interested in is
src/action.c, there's a table at the bottom of actions defined in that
file.  Add one for System() or Shell(), copy one of the smaller
existing actions, and edit as needed.

ActionMessage() is probably a good function to copy from.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: pcb - shell command

2007-02-01 Thread Tom Schouten
On Thu, Feb 01, 2007 at 04:23:45PM -0500, DJ Delorie wrote:
 
  i was wondering though if it is possible to use PCB to directly
  invoke external shell comands, without using them to read or write
  stuff. basicly what i want is to invoke 'make' from PCB, and
  subsequentally reading in some files. i didn't find anything about
  this in my first read of the PCB doc.
 
 It doesn't at the moment, but it would be trivial to add.  Why not try
 to add it yourself?  The source file you're interested in is
 src/action.c, there's a table at the bottom of actions defined in that
 file.  Add one for System() or Shell(), copy one of the smaller
 existing actions, and edit as needed.
 
 ActionMessage() is probably a good function to copy from.
 

indeed.
see attach for the code i've added.
thanks for the fast response!

/* --- 
*/
static const char system_syntax[] =
  System(commandline);

static const char system_help[] = Executes a system command.;

/* %start-doc actions System

This action executes a shell command through the libc call system().
If multiple arguments are given, each argument is executed in turn.

%end-doc */

static int
ActionSystem (int argc, char **argv, int x, int y)
{
  int i;

  if (argc  1)
AFAIL (system);

  for (i = 0; i  argc; i++)
{
system(argv[i]);
}

  return 0;
}



/*

  {System, 0, ActionSystem,
   system_help, system_syntax}
  ,

*/


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: pcb - shell command

2007-02-01 Thread DJ Delorie

   for (i = 0; i  argc; i++)
 {
   system(argv[i]);
 }

Are you sure this is what you want?  I.e. System(make,ls,echo) runs
three commands?  The lesstif GUI allows spaces in its command window,
so :system ls -l tries to run ls then runs -l.

Maybe you should concatenate the arguments with spaces into a single
command line?

Also, you should check the exit code of the command, and fail the
action if the command fails.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: PCB: Polygon segfault

2007-02-01 Thread Hans Nieuwenhuis
Hi,

While designing a board I got a segfault in PCB. I have a design with a polygon 
connected to GND on the component layer and among others the QFN20_4_EP 
footprint on it. This particular footprint has a very small clearance which I 
noted only after I drew the polygon on top of it. 
If I now press F2 and start to pan the board I get a segfault. I think the 
polygon clipping code goes a bit wrong, I see also constant flashing in the 
polygon area.

I attached a small patch which at least fixes the segfault for me for now. I 
have a testfile which gives the segfault, but I don't want to send it to the 
list. Attached is also the backtrace. If one of the developers needs the 
testfile, please let me know, I can send it off-list.

I use the CVS version of PCB from early January.

Thanks,

Hans

Backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912542616624 (LWP 10989)]
0x0045d2b4 in M_POLYAREA_intersect (e=0x7fb45750,
afst=0x17a5c40, bfst=0x10c03d0, add=1) at polygon1.c:848
848   if (a-contours-xmax = b-contours-xmin 
(gdb) bt
#0  0x0045d2b4 in M_POLYAREA_intersect (e=0x7fb45750, 
afst=0x17a5c40, bfst=0x10c03d0, add=1) at polygon1.c:848
#1  0x0045f1dd in poly_AndSubtract_free (ai=Variable ai is not 
available.
) at polygon1.c:1798
#2  0x0045bffb in r_NoHolesPolygonDicer (p=0x1a9c1e0, 
emit=0x43b380 DrawPolygonLowLevel) at polygon.c:1312
#3  0x0045c04c in r_NoHolesPolygonDicer (p=0x17a5c40, 
emit=0x43b380 DrawPolygonLowLevel) at polygon.c:1334
#4  0x0045c014 in r_NoHolesPolygonDicer (p=0x1a5c7a0, 
emit=0x43b380 DrawPolygonLowLevel) at polygon.c:1320
#5  0x0045c014 in r_NoHolesPolygonDicer (p=0x1a4dad0, 
emit=0x43b380 DrawPolygonLowLevel) at polygon.c:1320
#6  0x0045c014 in r_NoHolesPolygonDicer (p=0x19ba240, 
emit=0x43b380 DrawPolygonLowLevel) at polygon.c:1320
#7  0x0045c014 in r_NoHolesPolygonDicer (p=0x1a4dad0, 
emit=0x43b380 DrawPolygonLowLevel) at polygon.c:1320
#8  0x0045c014 in r_NoHolesPolygonDicer (p=0x1a6a8c0, 
emit=0x43b380 DrawPolygonLowLevel) at polygon.c:1320
#9  0x0045c014 in r_NoHolesPolygonDicer (p=0x1aa2cb0, 
emit=0x43b380 DrawPolygonLowLevel) at polygon.c:1320
#10 0x0045c1b6 in NoHolesPolygonDicer (p=0x7471f0, 
emit=0x43b380 DrawPolygonLowLevel, clip=0x7fb46200) at
polygon.c:1370
#11 0x0043bd81 in poly_callback (b=0x7471f0, cl=Variable cl is not 
available.
) at draw.c:2046
#12 0x00467ccb in __r_search (node=0x7474a0, query=0x7fb46200, 
---Type return to continue, or q return to quit---
arg=0x7fb46020) at rtree.c:540
#13 0x00467d46 in r_search (rtree=Variable rtree is not available.
) at rtree.c:626
#14 0x00439c81 in DrawLayerGroup (group=Variable group is not availabl
e.
) at draw.c:905
#15 0x0043cad0 in hid_expose_callback (hid=0x5ccb00, 
region=0x7fb46200, item=Variable item is not available.
) at draw.c:500
#16 0x004780db in ghid_invalidate_all () at hid/gtk/gtkhid-main.c:260
#17 0x2c43f3c0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#18 0x2c44df2c in g_signal_stop_emission ()
   from /usr/lib/libgobject-2.0.so.0
#19 0x2c44f3ec in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#20 0x2c44f7a3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#21 0x2aebaffc in gtk_adjustment_value_changed ()
   from /usr/lib/libgtk-x11-2.0.so.0
#22 0x00481684 in ghid_port_ranges_pan (x=748.27021883920111, y=0, 
relative=1) at hid/gtk/gui-output-events.c:114
#23 0x2c69f4bd in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#24 0x2c6a265f in g_main_context_check ()
   from /usr/lib/libglib-2.0.so.0
#25 0x2c6a290a in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#26 0x2af7a360 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#27 0x00489941 in ghid_do_export (options=Variable options is not 
available.
)
---Type return to continue, or q return to quit---
at hid/gtk/gui-top-window.c:3850
#28 0x0044bedb in main (argc=2, argv=0x7fb46b18) at main.c:777
(gdb) cont
Continuing.
Cannot find user-level thread for LWP 10989: generic error
(gdb) quit
The program is running.  Exit anyway? (y or n) y
Quitting: thread_db_get_info: cannot get thread info: generic error

 

-- 

$ cat .sig /dev/null
--- pcb/src/polygon1.c	2007-01-10 01:41:22.0 +0100
+++ pcb-mod2/src/polygon1.c	2007-02-01 23:57:50.0 +0100
@@ -841,6 +841,10 @@
 
   if (a == NULL || b == NULL)
 error (err_bad_parm);
+
+  if (a-contours == NULL || b-contours == NULL) 
+error (err_bad_parm); 
+
   do
 {
   do


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: PCB - grid dots not visible when board is flipped.

2007-02-01 Thread DJ Delorie

 I think what happened is that when the lesstif version implemented
 the left-right flip (vs.  up-down as it worked previously) there was
 something that didn't propagate back into the GTK code.

It wasn't lesstif, it was that the concept of flipping moved from
the core to the GUI.  Both GUIs needed extra code to implement the
mapping.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: gEDA meeting in Sioux Falls SD

2007-02-01 Thread Jeff VR

Where in the world is Sioux Falls?  And did the subject specify the state of
South Dakota???  Yep there's a few geeks in the Midwest, not just the east
and west coast. :)

Just in case there is anyone on on the mailing list that is in the Sioux
Falls SD area.  I would like to extend an invitation to this meeting who is
entertaining the idea of doing a PCB design with gEDA.  We are meeting at
Colorado Technical University on Feb. 15.  By the way there's pizza and soda
involved.

A couple of months ago I chose gEDA as the tool suite for laying out my
first PCB.  With a little help from people on this message board and a
couple months of free time I was successful!  I don't claim to be an expert
at PCB design or even gEDA.  But I do understand the basic design flow and
can assist someone who needs a little assistance getting started.   For many
people the installation and use of Linux is just a little more than you care
to bight off at one time, so I plan to provide a VMPlayer image at the
meeting.  Again I'm no electrical engineer since my background is Software
Engineering so don't drive 2hrs to get that burning question about
transistor saturation answered.  There may be someone at the meeting that
can answer it but it won't be me.  If your interested and live nearby I
would love to meet someone else who has worked with these tools.

Get the details at:
http://www.siouxland.org/


I apologize if this is a misuse of this message board.

Thanks for your support,
Jeff Van Roekel


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user