¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

3D modeling doesn't work

caa_bayonne
 

Hello,

I'm usign kicad on ubuntu linux 5.10. I have wings3d 0.98.29
installed, but 3d doesn't work.

I tried to create a link /usr/bin/wings -> /usr/bin/wings3d, but it
won't help. KiCAD doesn't provide any clue on what is wrong, and I
don't know what to do.

Can anybody help me?

Thanks,

Camilo A. Arboleda


Re: Zone and DRC problems

alfy4860
 

sounds like a problem with your netlist. If they all highlight, thats
usually when they are all the same net, or none part of a net.

did you export your netlist from the schematic?
No I started directly from a new board and placed the parts with 'add
module' tool
I can't think how this could go wrong, but it seems your problem is
that nothing is connected.
Yes I think that too

When I place modules on the board they seems to be tied together
because when i highlight a pad all the pads of all modules are
highlighted !

Is there a way to start a board without schematic and keeping DRC
functions ?


I Think my zone problems comes form the same cause

I will try to make a new design but with schematic first and compare
the result

Alain


Re: Offset adjust to compensate for pad spacing error in fine pitch components.

Ian bell
 

JPD Borgna wrote:
JPD Borgna wrote:
By sending a .pl file i violated the mail policy, sorry.
Now i send the file as .perl. :-D :-P
Saludos, Juan Pablo.
On a general adim note, if anyone has files to share with other group members, please use the group files section rather than attachments to group emails.

Thanks

Ian (group moderator)

--
Ian T-Bell
aka RuffRecords
aka RedTommo
www.geocities.com/ruffrecords


Re: Offset adjust to compensate for pad spacing error in fine pitch components.

JPD Borgna
 

JPD Borgna wrote:

By sending a .pl file i violated the mail policy, sorry.
Now i send the file as .perl. :-D :-P

Saludos, Juan Pablo.

Hi all, I hope that with this we can leave te "case closed":

With the attached script and this parameters: ./pqgen.pl 52 2 pq208 197 0 1000 100
I created a "ruller" for compare with the kicad package.
According to a datasheet from Xilinx PK007 (v1.2) June 18, 2004 about the PQFP (PQ208/PQG208) Package
the space betwen pads should be 19.68503937 in mills of inches, i used 197 (rounding) for this ruller.
When comparing on the screen this ruller with the package that comes with kicad i can see that the pads are not
perfect, the differences varies from pad to pad, and some in the middle ar ok.
So (lucky me!) i think the package will work with no problems.
From here to 2 to 3 weeks (:-P) im going to have a board designed with this package. Then ill tell you the real
thing: if it works or im fired....
Ive also attached a board with two modules, the one in the component has the pads from the ruller, the one
in the solder side is the one wich comes with kicad.


Saludos, Juan Pablo.

--
Juan Pablo Daniel Borgna -- Tcnico Electrnico
INTI-Electrnica e Informtica
Direccin: Avenida General Paz 5445 entre Albarellos y Constituyentes
CC157 (CP B1650KNA) San Martn, Bs. As., Argentina TE:+(5411)4724-6200


Re: Offset adjust to compensate for pad spacing error in fine pitch components.

JPD Borgna
 

Hi all, I hope that with this we can leave te "case closed":

With the attached script and this parameters: ./pqgen.pl 52 2 pq208 197 0 1000 100
I created a "ruller" for compare with the kicad package.
According to a datasheet from Xilinx PK007 (v1.2) June 18, 2004 about the PQFP (PQ208/PQG208) Package
the space betwen pads should be 19.68503937 in mills of inches, i used 197 (rounding) for this ruller.
When comparing on the screen this ruller with the package that comes with kicad i can see that the pads are not
perfect, the differences varies from pad to pad, and some in the middle ar ok.
So (lucky me!) i think the package will work with no problems.
From here to 2 to 3 weeks (:-P) im going to have a board designed with this package. Then ill tell you the real
thing: if it works or im fired....
Ive also attached a board with two modules, the one in the component has the pads from the ruller, the one
in the solder side is the one wich comes with kicad.


Saludos, Juan Pablo.

--
Juan Pablo Daniel Borgna -- T¨¦cnico Electr¨®nico
INTI-Electr¨®nica e Inform¨¢tica
Direcci¨®n: Avenida General Paz 5445 entre Albarellos y Constituyentes
CC157 (CP B1650KNA) San Mart¨ªn, Bs. As., Argentina TE:+(5411)4724-6200





Archivo adjunto: pqgen.pl
Un archivo adjunto a este email ha sido removido
debido a que el nombre del archivo no est¨¢ permitido.

Archivo adjunto: tests.zip/tests.cache.lib
Un archivo adjunto a este email ha sido removido
debido a que el nombre del archivo no est¨¢ permitido.


Re: Zone and DRC problems

ryan williams
 

alfy4860 wrote:
On a previous board, everywhere I clic to add a net I get an arrow
when DRC is on. But I tried a new one with only 2 resistors and its
works. Now I have to find why it doesn't works on the other board.
sounds like a problem with your netlist. If they all highlight, thats usually when they are all the same net, or none part of a net. did you export your netlist from the schematic? I can't think how this could go wrong, but it seems your problem is that nothing is connected. that will give the arrows when you try to draw a trace on them.

-ryan


Re: Building with Visual Studio

 

--- In kicad-users@..., "yajeed2000" <djsbriscoe@t...> wrote:

Hi Phil,
Lit window productions does wxVisualSetup, a tool that integrates
wxWidgets into .NET 2003.
This maybe useful to you.

David.
David,

Thanks for the link. I will definitely check it out. It would be
great to be able to compile Kicad on Windows with Visual Studio.

Regards,

Phil


Re: Building with Visual Studio

yajeed2000
 

Hi Phil,
Lit window productions does wxVisualSetup, a tool that integrates
wxWidgets into .NET 2003.
This maybe useful to you.

David.
--- In kicad-users@..., "Phil Covington" <p.covington@g...>
wrote:

Hello,

Has anyone on the group been successful in building the Kicad source
with any version of Visual Studio? If no one has done it yet, I may
try to see how difficult it would be to create a VS project for Kicad.

I have been using Kicad for a few weeks now and I am impressed.

Regards,

Phil Covington


Re: Offset adjust to compensate for pad spacing error in fine pitch components.

yajeed2000
 

Hi,
I've found out in the module editor that the pins in this package are
not spaced evenly.I've opened the file libcms.mod which is an
editable
text file.Under the entry for the PQFP208 module the line POS 5030 -
6100
indicates the centroid of pad 1, and so on for each pin.There needs
to
be a spacing of 0.02 inches (200) between pads.So for pin 2 the line
reads POS 4830 -6100 (5030-4830 = 200). From pin 3 the spacing varies.
I've created a small console C++ (standard template stuff) program to
calculate for me the correct numbers to replace in the libcms.mod
file.Problem is there are 208 pins to edit this way.
It is much easier editing this text file than using the module editor
to move the pads by hand.
If anyone could come up with a find and replace program to do the
work
it would be great.Even better would be a utility to place pins
automatically at a fixed distance on each module/pcb package.
Hope this info is useful.

David.
--- In kicad-users@..., "yajeed2000" <djsbriscoe@t...>
wrote:

Hi,
I am trying to print out several square 28 x 28 208 pin quad flat
packages using a standard laser printer.
However when printed the pads do not line correctly with actual
component pins.There is a small error in the spacing of the pins
that
is caused either by the printer (paper stretch)or in Kicad.
It would be useful if some kind of VERY SMALL offset adjustment (X
and
Y direction)could be introduced in the print dialog.
Alternatively could anyone suggest a way of correcting this error.
Thanks.

David


Re: Zone and DRC problems

alfy4860
 

Thank you for your relpy Ryan
hi,

for your DRC problem. it is hard to say without knowing more about your
problem. The small arrow comes up when you try to make a connection,
draw a trace, or place a via in some way that disagrees with the design
rules. The only way I have been able to reproduce the problem you
describe is to put moduldes too close together, or set your
clearance to
far apart. I strongly reccomend that you leave DRC on and find your
problem or else you will likely end up with boards that have errors.
On a previous board, everywhere I clic to add a net I get an arrow
when DRC is on. But I tried a new one with only 2 resistors and its
works. Now I have to find why it doesn't works on the other board.



the zone tool will include a net on the zone if that net is selected. I
often set the zones to connect with ground. Do this by selecting the
net
highlight tool and clicking on a pad from that net. to deselect a net
just click somewhere else on the board. do this just before creating a
zone/fill.
For this point, when i clic on a pad/net to highlight it, all the
board is highlihted and it doesnt mofify the problem when I fill the
zone Highlighted or not. sorry

Alain
-ryan


Feature request - Editable Power

microsuffer
 

I would like to see the power pin fields editable. It seems a bit
restrictive to prohibit that. The alternative now, cluttering up a
library with design specific power symbols is a nuisance. Power pins
should be like resistors, modifiable as needed to produce different
power nets.

Regards,

Charlie H.


Building with Visual Studio

 

Hello,

Has anyone on the group been successful in building the Kicad source
with any version of Visual Studio? If no one has done it yet, I may
try to see how difficult it would be to create a VS project for Kicad.

I have been using Kicad for a few weeks now and I am impressed.

Regards,

Phil Covington


Re: Zone and DRC problems

ryan williams
 

alfy4860 wrote:
Hello,
I am new Kicad user.
I try to desing my first little board and have 2 problems
First: When DRC check is on I cannot place any wire on the board
and a little arrow is on the pad where the wire starts.
When DRC is off all works fine but I would like to use the DRC function.
Second: I can't understand how works zone tool
Sometime it works fine and sometime the wires are included into it
I don't know why and I didn't find some information into the doc.
hi,

for your DRC problem. it is hard to say without knowing more about your problem. The small arrow comes up when you try to make a connection, draw a trace, or place a via in some way that disagrees with the design rules. The only way I have been able to reproduce the problem you describe is to put moduldes too close together, or set your clearance to far apart. I strongly reccomend that you leave DRC on and find your problem or else you will likely end up with boards that have errors.

the zone tool will include a net on the zone if that net is selected. I often set the zones to connect with ground. Do this by selecting the net highlight tool and clicking on a pad from that net. to deselect a net just click somewhere else on the board. do this just before creating a zone/fill.

-ryan


Zone and DRC problems

alfy4860
 

Hello,
I am new Kicad user.
I try to desing my first little board and have 2 problems
First: When DRC check is on I cannot place any wire on the board
and a little arrow is on the pad where the wire starts.
When DRC is off all works fine but I would like to use the DRC function.

Second: I can't understand how works zone tool
Sometime it works fine and sometime the wires are included into it
I don't know why and I didn't find some information into the doc.

Thank you

P.S.
I am french speaking and apologize for my bad english.
Alain


Re: Feature request: 3D view export

jim_e_meech
 

Hello All,
I strongly agree with Eriks suggestion that 3d export would be a very
usefull addition to Kicad.
Currently I use Eagle as my PCB tool at work. There are many aspects
of KICAD that I feel are more intuitive and easier to learn than in
Eagle. The 3d viewer in Kicad is a more usefull tool than the EAGLE
add on 3D script ( I was very impressed with this also)
The abilty to export a 3d model so that I can use in soild works
would be a very large plus point for Kicad.
I would very much like to be able to export additional fields from
componants to the bill of materials. I like to record manufacturer,
vendor and our store part number info at the time I create a
componant.I do not like the system in Eagle where I have to correlate
my BOM to an external data base. This can be prone to errors.
One feature of Eagle that I miss in Kicad, is the ability to higlight
a net within the schematic and see it highlighted on the board.
I should imagine this would be a fairly dificult feature to implement.
A simpler implemantation could be a netlist browser that allows you
to select and highlight a net on the board directly from the netlist.
I have used a schematic / pcb package with this feature, which proved
most usfull in checking the layout.

I would like to thank the author for writing such a fine program and
making it freely available.


Best Regards

Jim Meech













--- In kicad-users@..., "generalizt"
<erik.sundkvist@i...> wrote:

Hi folks,

I have been on the list for a while (passively) and use Kicad since
a
few weeks for a semi-professional project. So far it's pure
spare-time, but if it turns out well, it could be transformed into
full-time ;-)

Kicad is the perfect tool for me, since it is very easy to get
started
with and has most of the features needed. Also I like that it is
very
easy to add new parts to the libraries.

Anyway, while working towards a complete embedded product, there is
always mechanics design to consider, and a nice feature would be to
export the 3D view of the populated PCB in a format that can be
imported into a 3D CAD package like SolidWorks or Pro-Engineer. For
this purpose I think a VRML export would do just fine. Since VRML is
already used for importing 3D models of components, and all the
vertex
data is already present in the 3D view, exporting to VRML should be
quite quick to implement. Is anybody else having similar thoughts?

Regards,
Erik Sundkvist


Re: Feature request: 3D view export

R. Michael Sharkey
 

On Sunday 06 November 2005 06:19 am, generalizt wrote:
Anyway, while working towards a complete embedded product, there is
always mechanics design to consider, and a nice feature would be to
export the 3D view of the populated PCB in a format that can be
imported into a 3D CAD package like SolidWorks or Pro-Engineer. For
this purpose I think a VRML export would do just fine. Since VRML is
already used for importing 3D models of components, and all the vertex
data is already present in the 3D view, exporting to VRML should be
quite quick to implement. Is anybody else having similar thoughts?
Yeah, I've always wished I could even just test stacking multiple KiCAD
assemblies within the 3D viewer. Yeah, an export that would just allow me to
use an external application would be perfect.

--
Regards,

Mike Sharkey


Bradford, Ontario
CANADA


Feature request: 3D view export

generalizt
 

Hi folks,

I have been on the list for a while (passively) and use Kicad since a
few weeks for a semi-professional project. So far it's pure
spare-time, but if it turns out well, it could be transformed into
full-time ;-)

Kicad is the perfect tool for me, since it is very easy to get started
with and has most of the features needed. Also I like that it is very
easy to add new parts to the libraries.

Anyway, while working towards a complete embedded product, there is
always mechanics design to consider, and a nice feature would be to
export the 3D view of the populated PCB in a format that can be
imported into a 3D CAD package like SolidWorks or Pro-Engineer. For
this purpose I think a VRML export would do just fine. Since VRML is
already used for importing 3D models of components, and all the vertex
data is already present in the 3D view, exporting to VRML should be
quite quick to implement. Is anybody else having similar thoughts?

Regards,
Erik Sundkvist


Guidelines for libraries

vincent_bregeault
 

Hi everyone,

As Kicad is already usable, I think people will start building
libraries of there own. Why not coordinating the work to have a big
but logic set of base libraries ?
This requires having 'guidelines' for library builders on Kicad's web
site, and of course, that the base libraries conforms to these guidelines.

For example:
- When to use invisible supply, and when visible ?
- Should the pins of a component (in a schematic) be ordered by
functionnality, of by pin order ?
- How should the pins be numbered ? I think of 7805, which are named
VI, GND, VO, instead of 1,2,3, which would allow reusing the packages
without having to copy it and change the names of the pads
- What should be the default pad size ?
- How to organize the libraries ? There are already overlaps between
'microcontrollers' and 'microchip 1&2', and the 'special' library is
already quite big, it is not very simple to find something in it.

I think you have much more ideas to add to this post.


Re: Offset adjust to compensate for pad spacing error in fine pitch components.

Pedro Mart¨ªn del Valle
 

Hi,

My experience is:

1. When I print directly to the printer, I never get the rigth footprint
draws. Even when I have printed the pdf-footprints included in the kicad
package. Same results either with Linux or Windows and with 3 different
printers.

2. If I plot (trazar in Spanish) the files to a .ps file and afterwards I
print the file (I have used Konqueror) the result is OK.

3. If I read the Gerber files with the manufacturer drilling machine
programmes, the result is OK. I do not know which programme it uses. My
Gerber files were generated with the Linux Kicad version and the drilling
programme runs under Windows.

Regards,

Pedro.

yajeed2000 wrote:
Hi,
I've uploaded it to the test print plot folder.
I've been using Ghostview to veiw and print the files to a HP laserjet
colour printer (a new one at work, so its not worn out).
Can people please try this file and let me know if it has the same
problem.


Hi there!
Ive printed it with a lexmark laser printer using linux and ghostview and
put my spartan2-pq208 on top of the printed page and (with a magnifiying
glass) saw that the pads are OK!

Im interesed in this tests too because ive just send my board (wich uses?
this) to the factory for made some prototypes. If any one else can test
them, please!!

Saludos, Juan Pablo.

Thanks,

David.
--- In kicad-users@..., Ian bell <ianbell@u...> wrote:


yajeed2000 wrote:


Hi,
I am trying to print out several square 28 x 28 208 pin quad flat
packages using a standard laser printer.
However when printed the pads do not line correctly with actual
component pins.There is a small error in the spacing of the pins


that


is caused either by the printer (paper stretch)or in Kicad.
It would be useful if some kind of VERY SMALL offset adjustment


(X and


Y direction)could be introduced in the print dialog.
Alternatively could anyone suggest a way of correcting this error.
Thanks.

David



Could you post a copy of one that has this problem to the files
section of the group? That way others can try rpinting it see if it


is


just a problem at your end or a general Kicad problem.

Ian
--
Ian T-Bell
aka RuffRecords
aka RedTommo
www.geocities.com/ruffrecords










Please contribute your symbols and modules to the library folder in the
group files section. Yahoo! Groups Links



Re: Offset adjust to compensate for pad spacing error in fine pitch components.

Tonamiben
 

yajeed2000 wrote:

Hi,
I've uploaded it to the test print plot folder.
I've been using Ghostview to veiw and print the files to a HP laserjet
colour printer (a new one at work, so its not worn out).
Can people please try this file and let me know if it has the same
problem.

Thanks,
I tried it with Acrobat distiller on an WinXP and Ricoh laser printer, my screen resolution is 1280X1024
On paper and on screen I see a discrepancy of spacing between pads. On screen it range from 55 to 62 pixels
spacing between pads.

One that is use to work with postscipt may analyse the coordinate and calculate if there is also a discrepancy there.
Maybe the file is OK and it is only a rounded coordinate that is printed or layed on screen.
Maybe it's a good idea to look at the coordinates inside the gerber file also?

Benoit