Re: [Kicad-developers] PATCH: fix for bug 1659027

[easyw]

Hi Cirilo,

1. Rejection of 3D files with upper-case extensions in Windows

reject 3D files with upper case in windows is not the best behavior imo...
Many manufacturers are using Upper-case extension
i.e.
http://www.tensility.com/3dmodels/54-00011.STEP
Wouldn't be easier accept lower and upper case instead?
Windows is a case insensitive OS

Maurice

On 22-Feb-17 9:10 AM, Cirilo Bernardo wrote:

I have attached a patch to the bug report:

https://bugs.launchpad.net/kicad/+bug/1659027/comments/14

I have tested on Linux and Windows but more testing/comments
appreciated.

Bugs fixed:
1. Rejection of 3D files with upper-case extensions in Windows
2. non-ASCII path bug in fileType() function of 3D plugin
3. non-ASCII path bugs in KiCad's 3D cache object

Notes:

* non-ASCII path bugs are likely present in the other
3D plugins (vrml, x3d, IDF) so I need to have a look at the
code for those and fix the bugs.

* there is a fundamental non-ASCII path bug in OpenCascade
and by extension OCE: on Windows OpenCascade/OCE do
not provide a mechanism for opening files via Windows'
_wfopen() function so only files with a pure ASCII path may
be processed. Some posts on the web suggest that this bug
has been fixed in the latest version of OpenCascade but I
haven't had time to verify this. For the moment, in Windows
only, we cannot use files which have any non-ASCII characters
in the absolute path. Linux is not affected and I have no idea
about OSX.

- Cirilo

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] PATCH: fix for bug 1659027

[easyw]

ok, sorry for the noise :)

On 22-Feb-17 3:16 PM, Nick Østergaard wrote:

Maurice, please reread the email. It was a bug that caused it to not
work with uppercase, this is not the desired behaivour.

2017-02-22 14:52 GMT+01:00 easyw :

Hi Cirilo,


1. Rejection of 3D files with upper-case extensions in Windows


reject 3D files with upper case in windows is not the best behavior imo...
Many manufacturers are using Upper-case extension
i.e.
http://www.tensility.com/3dmodels/54-00011.STEP
Wouldn't be easier accept lower and upper case instead?
Windows is a case insensitive OS

Maurice


On 22-Feb-17 9:10 AM, Cirilo Bernardo wrote:


I have attached a patch to the bug report:

https://bugs.launchpad.net/kicad/+bug/1659027/comments/14

I have tested on Linux and Windows but more testing/comments
appreciated.

Bugs fixed:
1. Rejection of 3D files with upper-case extensions in Windows
2. non-ASCII path bug in fileType() function of 3D plugin
3. non-ASCII path bugs in KiCad's 3D cache object

Notes:

* non-ASCII path bugs are likely present in the other
3D plugins (vrml, x3d, IDF) so I need to have a look at the
code for those and fix the bugs.

* there is a fundamental non-ASCII path bug in OpenCascade
and by extension OCE: on Windows OpenCascade/OCE do
not provide a mechanism for opening files via Windows'
_wfopen() function so only files with a pure ASCII path may
be processed. Some posts on the web suggest that this bug
has been fixed in the latest version of OpenCascade but I
haven't had time to verify this. For the moment, in Windows
only, we cannot use files which have any non-ASCII characters
in the absolute path. Linux is not affected and I have no idea
about OSX.

- Cirilo

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [REQUEST] Remove Wings from Windows Installer

[easyw]

Hi Mario, Cirilo and Kevin.

As Mario and Cirilo already pointed out, STEP format doesn't support 
transparency, reflection, and ambient lighting...
So you can add these properties to your model but when you export it to 
STEP, they all are gone.
This can be done in Rhino, FreeCAD or whatever CAD you may use, STEP 
model will always be without these properties...



I imported an item in to FreeCAD and it came out the wrong size due to the 
units used in the original file. I thought it would be easy to just scale the 
item to the right size in FreeCAD but FreeCAD wouldn't let me do it. I found 
that the only way it might have let scale an object is by scaling a copy of the 
imported object where the copy is linked back to the original version, or 
something like that.
Even something as simple as changing the size of an item was being made 
difficult in FreeCAD.
FreeCAD is a parametric mechanical modeler, so scaling should be not the 
right way to adapt a model...
FreeCAD as you already pointed out has a Clone feature that can be 
scaled... the nice thing is that clone object is linked to its parent 
and if the parent will be changed, the clone will adapt accordingly... 
This is not the only way to scale a model, you can use a GUI macro for 
example.


In general you shouldn't model your part scaled to be aligned to kicad 
internal 3D viewer, you should model your part in mm scaled 1:1 and then 
scale the WRL when exporting. In this way your STEP models will be 
correctly scaled to the real dimensions.


Moreover in FreeCAD the correct way to model a part is starting from 
sketches ... then your model can easily changed simply modifying the 
dimensions of the sketches... this is how a parametric modeler is working.

You can follow many youtube tutorials on-line and get support on FC forum.
FreeCAD can also be scripted to easily create 3D parts and kicad is 
already using most SMD models coming from this method.

https://github.com/KiCad/packages3D/

This is not to force to use FreeCAD at all, but just to pointed out that 
you need to spend some time using a tool before judging.


If you want to have a realistic rendering in kicad, as already pointed 
out, the best way is to model your part in scale 1:1 with mm and from 
there export your wrl part with all the nice properties, scaled 1/2.54
You can also export it not scaled and assign a scale factor inside the 
kicad_mod footprint, so you can avoid the scaling part.


here some tips to create a mechanical library
https://github.com/KiCad/packages3D/blob/master/README.md

Cheers
Maurice







___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Hello & Questions to future Administration of Python Plugins

[easyw]

Hi Simon,

there is already a nice way to call python scripts in kicad through 
Action Plugin (available on dev build)

https://forum.kicad.info/t/howto-register-a-python-plugin-inside-pcbnew-tools-menu/5540
Improving python API would be just great!


I am a Researcher working in the areas of IC Design, (RF-) PCB Design
if you are interested in RF, there is also a branch of kicad that 
implemented some useful features you may interested in

https://github.com/bpkempke/kicad-source-mirror/tree/rf_merge
https://forum.kicad.info/t/rf-aspects-with-kicad/2802/2

BR
Maurice


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Pcbnew Python Interface breakage?

[easyw]

Hi,
I can confirm the same error on windows 10.

I get also an other kind of error in my annular plugin that worked till now

"for pad in module.Pads():
TypeError 'SwigPyObject' object is not iterable"

BR
Maurice

On 06/25/2017 5:46 PM, Simon Küppers wrote:

Hi,
I just updated KiCad on Linux Mint using the Launchpad PPA to test the
new connection algorithm. However, a SWIG error starts to pop up in my
python plugins.
Right now I can produce the error, when calling GetDrawings on the board
object (which worked a few days ago). It looks like the SWIG wrappers
are desynchronized from the C++-code. Is that (at all) possible?

This is the Traceback I get:


Traceback (most recent call last):

  File "/home/sk/.kicad_plugins/action_viafence/viafence_action.py",
line 160, in Run
boardItem = self.boardObj.GetDrawings().GetFirst()

  File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 18508, in
GetDrawings
def GetDrawings(self):return self.m_Drawings

  File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 17803, in 
__getattr__ = lambda self, name: _swig_getattr(self, BOARD, name)

  File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 74, in
_swig_getattr
return _swig_getattr_nondynamic(self, class_type, name, 0)

  File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 69, in
_swig_getattr_nondynamic
return object.__getattr__(self, name)

AttributeError: type object 'object' has no attribute '__getattr__'

Best Regards
Simon

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Pcbnew Python Interface breakage?

[easyw]

Hi Js,
thx with PadsList() the script is fine now...

Do you have any suggestion also for

"for drw in board.GetDrawings():
GetDrawings def GetDrawings(self): return self.m_Drawings File
...
AttributeError: type object 'object' has no attribute '__getattr__'"

reference this action script
https://github.com/easyw/kicad-action-plugins/blob/master/action_menu_move_to_layer.py


thx
Maurice

On 06/26/2017 11:21 AM, reynaud wrote:

Hi,

Python interface is not stable. You can have some changes on daily build
version.
In your case, using PadsList() instead of Pads() should fix your issue.


Le lundi 26 juin 2017 à 10:23 +0200, easyw a écrit :

Hi,
I can confirm the same error on windows 10.

I get also an other kind of error in my annular plugin that worked till now

"for pad in module.Pads():
TypeError 'SwigPyObject' object is not iterable"

BR
Maurice

On 06/25/2017 5:46 PM, Simon Küppers wrote:

Hi, I just updated KiCad on Linux Mint using the Launchpad PPA to
test the new connection algorithm. However, a SWIG error starts to
pop up in my python plugins. Right now I can produce the error, when
calling GetDrawings on the board object (which worked a few days
ago). It looks like the SWIG wrappers are desynchronized from the
C++-code. Is that (at all) possible? This is the Traceback I get:
 Traceback (most recent call last): File
"/home/sk/.kicad_plugins/action_viafence/viafence_action.py", line
160, in Run boardItem = self.boardObj.GetDrawings().GetFirst() File
"/usr/lib/python2.7/dist-packages/pcbnew.py", line 18508, in
GetDrawings def GetDrawings(self): return self.m_Drawings File
"/usr/lib/python2.7/dist-packages/pcbnew.py", line 17803, in 
__getattr__ = lambda self, name: _swig_getattr(self, BOARD, name)
File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 74, in
_swig_getattr return _swig_getattr_nondynamic(self, class_type, name,
0) File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 69, in
_swig_getattr_nondynamic return object.__getattr__(self, name)
AttributeError: type object 'object' has no attribute '__getattr__'
Best Regards Simon ___
Mailing list: https://launchpad.net/~kicad-developers Post to :
kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net> Unsubscribe :
https://launchpad.net/~kicad-developers More help :
https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Pcbnew Python Interface breakage?

[easyw]

Hi,

I solved with a trick
try:
board_drawings=board.GetDrawings()
except:
board_drawings=board.DrawingsList()

for drw in board_drawings:

for one plugin, and with a similar trick for the other;
but your solution is cleaner.

is the
diff --git a/pcbnew/swig/module.i b/pcbnew/swig/module.i
correct?

I see there is a block comment before @line 45
/*
%extend MODULE
...

Applying the patch I cannot make any plugins running
but if I de-comment that block it works...


Thx
Maurice


On 06/26/2017 2:24 PM, Maciej Sumiński wrote:

Hi Maurice,

This is due to the recent commit that enables iterators for DLISTs. We
have forgotten that such change impacts the Python interface.

I propose to keep the old interface, otherwise we will face many reports
when a script works correctly with the stable release, but not with
nightlies.

Would you check if the attached patch fixes the problem? If so, I will
push it.

Regards,
Orson

On 06/26/2017 10:23 AM, easyw wrote:

Hi,
I can confirm the same error on windows 10.

I get also an other kind of error in my annular plugin that worked till now

"for pad in module.Pads():
TypeError 'SwigPyObject' object is not iterable"

BR
Maurice

On 06/25/2017 5:46 PM, Simon Küppers wrote:

Hi,
I just updated KiCad on Linux Mint using the Launchpad PPA to test the
new connection algorithm. However, a SWIG error starts to pop up in my
python plugins.
Right now I can produce the error, when calling GetDrawings on the board
object (which worked a few days ago). It looks like the SWIG wrappers
are desynchronized from the C++-code. Is that (at all) possible?

This is the Traceback I get:


Traceback (most recent call last):

  File "/home/sk/.kicad_plugins/action_viafence/viafence_action.py",
line 160, in Run
boardItem = self.boardObj.GetDrawings().GetFirst()

  File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 18508, in
GetDrawings
def GetDrawings(self):return self.m_Drawings

  File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 17803, in

__getattr__ = lambda self, name: _swig_getattr(self, BOARD, name)

  File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 74, in
_swig_getattr
return _swig_getattr_nondynamic(self, class_type, name, 0)

  File "/usr/lib/python2.7/dist-packages/pcbnew.py", line 69, in
_swig_getattr_nondynamic
return object.__getattr__(self, name)

AttributeError: type object 'object' has no attribute '__getattr__'

Best Regards
Simon

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] 3D models repository

[easyw]

Hi Javier,

atm our 3d script generated library has already a license similar to geda

https://github.com/KiCad/packages3D/wiki/Model-Licencing

Particularly what has been stated there is the freedom to share the 3D 
models embedded in the design (i.e. a full board and step models for 
data interchange but not a single model to build a standalone library)


Please have a look at the License.

We have generated atm n.1295 3D STEP parametric models script generated 
plus n.500 new connectors and it is growing!
I think is the biggest open source 3D electronic-mechanical library 
available all around!

https://forum.freecadweb.org/viewtopic.php?f=24&t=20892&hilit=kicad+collaboration


Best Regards
Maurice

On 06/29/2017 4:21 PM, Javier Serrano wrote:

On Thu, Jun 29, 2017 at 3:28 PM, Simon Richter mailto:simon.rich...@hogyros.de>> wrote:

Hi,

On 29.06.2017 12:18, Javier Serrano wrote:

> I agree the creative side is stronger for symbols than for footprints.
> Copyrightability is, as you well point out, a subject of debate in
> various areas. However, I think the real debate we should have is
> whether we want to make the official libraries permissive or weak
> copyleft.

I'd be completely fine with PD/CC0 for symbols and footprints, because
they need to be available to users without having to check license
compatibility first.

If people are using 3D models for more than nice renderings (e.g. to
determine the cutout from the case), then a permissive license would be
required here as well in order to avoid complications for the
manufacturing files.


Please see my comment below on the paragraphs we proposed.




> I am not sure I understand the argument. There are clearly more risks of
> proprietarization whenever you use a permissive license, because you are
> explicitly giving permission to improve and not share back.

Designing a license that would require people to share library
improvements but not their PCB designs would be difficult.


Wait, what you describe as "difficult" is what the paragraphs we
submitted do. They are written by a lawyer, and I don't see how they
could be misinterpreted. Incidentally, geda does the same, except taking
GPL as a basis instead of CC-BY-SA:

http://wiki.geda-project.org/geda:license

Again, for me the question is: do we want to *explicitly* allow people
to take components of a library, improve them and not share the
improvements back? If yes, CC0. If not, CC-BY-SA with the proposed
paragraphs to clarify that the license provisions do not extend to the
whole schematics, layout or circuit model.

Cheers,

Javier


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] new connectivity algorithm - testers needed

[easyw]

Hi,
I'm having a strange behavior when loading a netlist

with the menu Tools, Load Netlist
if I select to Delete Single Pads Nets, almost all pads will lose their 
connectivity... (you can see in the report that the algo is deleting the 
net connectivity when parsing the pads)

This was not the previous behavior.

tested with today git


thanks for have a look on that
Maurice


On 06/27/2017 9:54 PM, Tomasz Wlostowski wrote:

On 27.06.2017 21:24, Simon Küppers wrote:

Small Bump.

Can anyone shed some light on the new Via Tool? Is it supposed to be not
ready yet? The Track & Via Properties Dialog looks really unfinished and
I cannot modify anything beside Position and Via Size there. Is it
because I am using the Cairo Canvas?


Sorry, I forgot that I left the dialog unfinished. Will fix in a couple
of days...

Tom

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] new connectivity algorithm - testers needed

[easyw]

Hi Orson,

tested with latest commits and now is fine.

thanks a lot
Maurice

On 6/30/2017 9:46 PM, Maciej Suminski wrote:

Hi Maurice,

What revision did you use? Today I fixed it (da051379), so it depends
whether you already have the recent patches. Let me know if there are
still problems.

Regards,
Orson

On 06/30/2017 05:58 PM, easyw wrote:

Hi,
I'm having a strange behavior when loading a netlist

with the menu Tools, Load Netlist
if I select to Delete Single Pads Nets, almost all pads will lose their
connectivity... (you can see in the report that the algo is deleting the
net connectivity when parsing the pads)
This was not the previous behavior.

tested with today git


thanks for have a look on that
Maurice


On 06/27/2017 9:54 PM, Tomasz Wlostowski wrote:

On 27.06.2017 21:24, Simon Küppers wrote:

Small Bump.

Can anyone shed some light on the new Via Tool? Is it supposed to be not
ready yet? The Track & Via Properties Dialog looks really unfinished and
I cannot modify anything beside Position and Via Size there. Is it
because I am using the Cairo Canvas?


Sorry, I forgot that I left the dialog unfinished. Will fix in a couple
of days...

Tom

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] 3D models repository

[easyw]

Public Domain is not the right vision IMO for kicad libraries.
If you release something in public domain, you lose any control and your 
data can be used in closed libraries, improved without giving back any 
result etc.


IMO Geda acted in the right way... the license has an exception for data 
embedded in a design

http://wiki.geda-project.org/geda:license

as per Javier Serrano post:

Again, for me the question is: do we want to *explicitly* allow people to take 
components of a library, improve them and not share the improvements back? If 
yes, CC0. If not, CC-BY-SA with the proposed paragraphs to clarify that the 
license provisions do not extend to the whole schematics, layout or circuit 
model.



Maurice

On 7/1/2017 1:21 AM, Oliver Walters wrote:

Cirilo,

Can we stipulate as part of the license file that any contributors agree 
implicitly that their generated models are released as public domain? 
i.e. don't require explicit release from every contributor, as it is 
inherent to the library LICENSE?


a) If you contribute model / footprint / symbol to KiCad libraries, they 
can be distributed in accordance with [whatever license we choose here]


b) KiCad assumes no responsibility for the accuracy of the model data

c) Library data may be shared freely*

* Here "freely" is the current source of contention. I am all for having 
as permissive a license as possible - I don't see any benefit from 
locking the library down.


Oliver

On Sat, Jul 1, 2017 at 8:25 AM, Cirilo Bernardo 
mailto:cirilo.berna...@gmail.com>> wrote:


On Thu, Jun 29, 2017 at 8:16 AM, Oliver Walters
mailto:oliver.henry.walt...@gmail.com>> wrote:
> Would it be sufficient to drop the "Copyright (C) 2017 KiCad" header?
>

No, because we have no idea who holds copyright. KiCad cannot be a
copyright holder
because it is not a legal entity (person or corporation). We would
need to maintain a text
file which is a register of the copyright holders of each file.  To
complicate things, many
models are generated from parametric scripts.  The scripts themselves
are copyright
material but the models produced is a different matter. If you can get
all script contributors
to agree, then I think it would be best to release the generated
models as Public Domain.
Even this is not so simple because we would need to maintain a
directory with declarations
from script contributors to state that the output of the scripts are
Public Domain. Even
that is not so simple because some jurisdictions may not accept that
mechanism.

- Cirilo

 > On Thu, Jun 29, 2017 at 5:28 PM, Javier Serrano
 > mailto:javier.serrano.par...@gmail.com>> wrote:
 >>
 >> On Thu, Jun 29, 2017 at 3:27 AM, Oliver Walters
 >> mailto:oliver.henry.walt...@gmail.com>> wrote:
 >>>
 >>> Wayne, others,
 >>>
 >>> A lot of input here, thanks everyone.
 >>>
 >>> Based on the suggestions above, my proposal is as follows:
 >>>
 >>>
 >>>


 >>>
 >>> symbols licence file:
 >>>
 >>>
 >>>


 >>> Copyright (C) 2017 KiCad
 >>>
 >>
 >>  I agree with Simon that "KiCad" cannot be the copyright holder.
Imagine
 >> for the sake of argument I need to contact the copyright holder.
Say I would
 >> like to negotiate with him/her a change of licence. I want to
use the
 >> material without being subject to the CC-BY-SA licence, and I am
willing to
 >> pay for it. So I'd like to benefit from some kind of
dual-licensing scheme,
 >> whereby I receive e.g. a copy of a 3D model file with a special
licence just
 >> for me. Only the copyright holder can do that. Now I go to the
file and I
 >> read "Copyright KiCad." Who should I speak to? Who has the right
to do what
 >> I need? That's just an example. For any action where you would
need the
 >> copyright holder to do something, you'd bump against the same
issue. One
 >> could conceivably define KiCad as a valid legal entity, and then
you could
 >> have KiCad be the copyright holder, as the FSF is the copyright
holder of
 >> lots of code, but that's a strategic change to be discussed, I
guess, with
 >> the project leader and the project initiator. Right now, KiCad
cannot be the
 >> holder of any copyright. The same applies, IMHO, to "KiCad
developers."
 >>
 >> Cheers,
 >>
 >> Javier
 >
 >
 >
 > ___
 > Mailing list: https://launchpad.net/~kicad-developers

 > Post to : kicad-developers@lists.launchpad.net

   

Re: [Kicad-developers] [FEATURE] Array 3D models

[easyw]

Hi Oliver,

I'm sorry not to be on your side for this option...

1) for which kind of modules this array is applicable?
I see only pin-headers straight and angled...
for example box headers are not easily done unless you consider to 
manage by the code the box for each model
2) the problem related to the big 3D library dimension will not be 
covered unless for some little family that can be managed by this on the 
fly generator


As I already suggested, the issue with the huge 3D github library can be 
managed in a different way:
1) give the kicad users only a basic 3D library (i.e. most used smd and 
th families)
2) give an option to pcbnew to automatically create a list of the 
missing models needed for a project and collecting only them through a 
wget process...


This will give a very low downloading band need and will not increase 
the need of disk space for having all the 3D library locally, full of 
unwanted models.


Here a conversation of this issue:
https://github.com/KiCad/kicad-library/issues/1532#issuecomment-341707706

my two-cents
Maurice

On 11/06/2017 3:01 PM, Oliver Walters wrote:
To provide an option to reduce the size of the 3D model library, I have 
implemented an "array" feature for 3D models. A module (footprint) can 
reference a single model multiple times, with a dimensional offset 
between each copy.


(Note - just the PinHeader models are currently over 1GB! This feature 
lets you use a single 3D model for all pin headers or similar repetitive 
footprints within a certain series).


Features:

1. Specify repeat count and repeat step in x/y/z axes
2. Save / load implemented. (If no repeat option used, no extra output 
is generated - old files are not touched)

3. Render in 3D viewer
4. Render in raytracing viewer
5. Export to VRML (multiple references to single file)
6. Export to STEP

Notes:

a. An exported STEP file will now be (possibly) much smaller as it 
references a single small object multiple times
b. There were a couple of bugs I found where model offset units were 
incorrectly translated between INCHES and MM


A couple of screenshots:

https://imgur.com/a/EOwPh


Testing:

Wayne verified that the file units for 3D model data are in mm - I 
*think* this means that there was previously a bug regarding 3D model 
offset, where the scaling factor in the file was interpreted as inches 
when exporting (e.g. to STEP)


I believe I have fixed this bug - confirmation would be great.

Cheers,
Oliver


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

[easyw]

Hi,
referring to:
"even if it is "only" for the pin headers, this is close to half of the 
3d library size as of now"
you probably missed the 3d library status...please have a look at recent 
PRs of the 3D library


There are contributors of new models that are afraid to contribute 
because of their model family big size (1G) ...

https://github.com/easyw/kicad-3d-models-in-freecad/pull/115#issuecomment-341058146

The 3D library is growing day by day and it will became bigger and 
bigger I hope... I consider this the best 3D mechanical library 
available ATM


This is not an issue on on-line library size IMO... this is an issue on 
what has to be bundled with the installer and what has to downloaded 
when needed... the all family of models (actual policy) or only the 
model that the project is going to use.


Moreover with the suggested patch, if you want to check a model 
dimensions in MCAD environment, you will need to create a fake board in 
kicad, assign a footprint, generate the step and then open it in 
mechanical sw to see dimensions, instead of just download it from github 
and check if this is fine for your design...


So my suggestion is not to create some exception case for the library, but:
1) find a way to manage what is going to be deployed to the users
2) create a script/code to download what is needed by the project 
itself, if missing...

3) select a 3D library base to be deployed with the main installer

The second point could done by a function to be called inside Kicad or 
pcbnew to create a full list of needed 3D parts for the user kicad project.
Then the function could check automatically if those models are already 
in the users local 3D library and give an option to retrieve with a 
'wget' process the missing models from kicad on-line library.
Finally the downloaded missing models would be placed automatically in 
the right local folder by the function itself.

For example if you need:
'Buttons_Switches_SMD.3dshapes/SW_SP3T_PCM13.step'
your wget could point to:
https://github.com/KiCad/kicad-packages3D/raw/master/Buttons_Switches_SMD.3dshapes/SW_SP3T_PCM13.step
and download it directly, placing it to local configured
'KISYS3DMOD'+Buttons_Switches_SMD.3dshapes/
folder.
This could be even done as a python Action Script for Kicad

Maurice

On 11/06/2017 4:53 PM, Kristoffer Ödmark wrote:
To be fair, as it stands now, even if it is "only" for the pin headers, 
this is close to half of the 3d library size as of now.


The pin headers can now be of an arbitrary size as well. Someone can now 
create a 4x6 pin header for example, and the current footprints can be 
converted to this array system, thus reducing the size.


Arbitrary pin headers are a step up anyway.

This being said, I have not tested the patch yet, but even if it is 
"only" for pin headers, the idea is sound to me.





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

[easyw]

Oliver,

just an other point against it IMO:

If you develop a build on the fly 3D library, in case of update on OCE 
release, you would need to check and probably review all the models 
generated by your scripts...
As I already pointed out on GitHub discussion, STEP are not just 
rendering models... they need to be done with a geometry check to 
guarantee a fine mechanical result.


A static library is just as is... good a and reliable without any need 
to be re-checked or rebuilt once approved...


Why just rework what is done till now and for which kind of advantage or 
optimization?


Still my best option is to decide what to deploy with the Kicad 
installer and a dynamic downloader that will fetch and download only 
what is needed for the project.



Maurice

On 11/6/2017 11:34 PM, Oliver Walters wrote:
Seth, for the STEP export that would be a better idea, I can look into 
how to implement that in the kicad2step tool.


Wayne, if you are completely against this as a feature, then I shan't 
spend any more time on it, but:


1. I think it is a useful feature to have even if it is not the "right" 
way to solve the current 3D library issues. That was only one motivating 
factor. I still think it is useful.
2. In terms of "code clarity" - take a look at the patch set, I don't 
think it will cause any issues for readability.
3. There are some bug fixes and code cleanup that I have performed as 
part of this patch set.
4. If I can use the STEP format array_placement as Seth suggests, then 
the internal representation of the exported STEP file will be improved


Regarding STEP / WRL comparisons - That's a separate issue to what is 
being discussed here. This patch works just as well for .wrl or .step 
models.




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

[easyw]

Oliver,
if you create by script or code or manually an array of single STEP 
models, the resulting array could be not fine in geometric terms also if 
the single model is good...
Please have some deep insight to FreeCAD forum or even OCC forum to see 
how mechanical boolean operation can be insidious ...


So yes, you need to validate all your models if you want to build a 
single part or you will need to build an array of models instead of a 
single STEP models...
Both solutions are not suitable in my opinion and experience in 
mechanical cad.


Maurice

On 11/6/2017 11:54 PM, Oliver Walters wrote:
This patch does *not* generate any models on the fly. It provides the 
ability for users to re-use existing model data (which they are NOT 
forced to use by any means). In the example of pin headers or terminal 
blocks, where each unit is identical, there is no need to re-validate 
each model. It is simply another means of achieving a goal.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [REQUEST] Default library install location

[easyw]

the two a) and b) points are a big issue I think and this configuration 
is normally not present in other installer programs on windows...


In windows a common User Folder is called common doc folder;
the var pointing to C:\Users\Public is %PUBLIC% in recent Windows
https://installmate.com/support/im9/kb/kb50038.htm#commondoc
Then placing the libraries models/modules in i.e. C:\Users\Public\kicad 
folder, will let All Users have access read/write to these folders


I'm not enough familiar in Unix, but I think it would be possible to 
just change folder permission during the installation, so the folder 
'\usr\share\kicad' could remain the default folder, but it will become 
writable by normal users... similar option for osx...

Maurice

On 11/8/2017 2:15 PM, Oliver Walters wrote:

Wayne,

I think you're right that a deeper understanding of how people are using 
and managing the libraries is required.


However, there still seems to be one of two options if KiCad installs 
libs into a location where users cannot write:


a) Users are not able to update the libraries or otherwise edit them
b) Users have to duplicate the library data to somewhere they *do* have 
access and then reassociate all the library tables


I think there is scope for improvement here. I'm not confident enough to 
say *what* that improvement should be.


On Thu, Nov 9, 2017 at 12:12 AM, Wayne Stambaugh > wrote:


What is the purpose of this change?  In what way will it improve the
user experience?  Before we ask the package devs to do a lot of work, we
might want to dig deeper into the library management issue.  I fail to
see how installing and likely duplicating the entire KiCad library in
the user's home folder solves any of the underlying library management
issues in KiCad other than having write access to modify the installed
libraries which has its own set of issues.  In some respects this has
the potential to complicate things even further.  I suspect the real
issue is out library editing and management tools.  I suggest we wait
until Orson pushes the symbol library editor to see if this improves the
library management situation.  Given what I know about it I suspect that
it will improve things significant on the library management side of
things.

Cheers,

Wayne

On 11/8/2017 2:02 AM, Oliver Walters wrote:
 > To the package maintainers:
 >
 > For v5 release, can the default library install path be set to a user
 > directory rather than program directory that may require
administrator
 > rights?
 >
 > e.g. instead of
 >
 > C:\Program Files\KiCad\share\...
 > or
 > /usr/share/kicad/...
 >
 > something like;
 >
 > C:\Users\Oliver\KiCad\...
 >
 > /home/Oliver/KiCad
 >
 > (Not necessarily those paths but something like that).
 >
 > A lot of users are reporting issues with being able to download or
 > modify library files, due to user privileges.
 >
 > How attainable is such a change before v5 release?
 >
 > Thanks,
 > Oliver
 >
 >
 > ___
 > Mailing list: https://launchpad.net/~kicad-developers

 > Post to     : kicad-developers@lists.launchpad.net

 > Unsubscribe : https://launchpad.net/~kicad-developers

 > More help   : https://help.launchpad.net/ListHelp

 >

___
Mailing list: https://launchpad.net/~kicad-developers

Post to     : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [REQUEST] Default library install location

[easyw]

This is even worse.. that way co-workers could (even accidentally) change the 
library without any notice.


different point of view in working strategies...
IMO something that I can change with i.e. the component editor and not 
save unless copied to a different location is a wrong way of working...

but as I said there are many working habits...

M


On 11/8/2017 10:54 PM, Thomas Kindler wrote:

On Wed, November 8, 2017 22:18, easyw wrote:

the two a) and b) points are a big issue I think and this configuration is
normally not present in other installer programs on windows...

In windows a common User Folder is called common doc folder;
the var pointing to C:\Users\Public is %PUBLIC% in recent Windows
https://installmate.com/support/im9/kb/kb50038.htm#commondoc
Then placing the libraries models/modules in i.e. C:\Users\Public\kicad
folder, will let All Users have access read/write to these folders

[..]


This is even worse.. that way co-workers could (even accidentally) change
the library without any notice.


I think there are two use cases:

1) Simple users of KiCAD

   For this use case, the library should be installed in a write-protected
location where only install admins can change them (like it is now).

As a simple user I would expect stable KiCAD releases to come with an
official sanctioned library for that release. Eagle and most other CAD
packages do the same bundling.

Auto-updaters that just update the library will confuse simple users, and
may cause compatibility problems if the library requires new features.

The same goes for automagic copy-on-write features - It's better to just
document how a library can be copied locally and how to override the
official one.


2) Advanced users that want to contribute to the library

   Advanced users should just clone the library using GIT. That way it's
possible to update and send pull requests using a normal, non-magic
workflow.

An option to skip bundled library installation would be nice, but is
optional.


Library overrides could be done using a prioritized search path:

   1. $PROJECT/library# very useful for project-specific things
   2. ~/.KiCAD/library# useful for contributor work
   3. /usr/share/KiCAD/library# default for simple users

Of course, users could insert their own location like a company file server..

best regards,



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [REQUEST] Default library install location

[easyw]

I think it's a far more risky that a user makes accidental changes to the
bundled library. Simple users should not need to touch it, and should
rather copy or make a new part.


so if a user wants to add a missing parts to his/her library he/her 
needs to save it to a different location, close the i.e. fp editor, copy 
with administrative privileges the fp to the Admin folder and restart 
the sw to use it?

I don't think other sw are using this procedure...
This is just my opinion...


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

Oliver,

historically that was in inches for the 3D viewer...
Mario didn't change the file format to avoid breaking any previous 
releases I think, but managed to calculate correctly offset and 
displaying in the 3D viewer and exporter...


I don't know if aligning these parameters to mm inside the kicad_pcb 
file format would worth the breaking back compatibility of boards, 
considering that there are no errors in the 3D viewer nor in the 
exporters...


The only issue is that offset values, as pointed out from JP, are stored 
internally in inches, but in terms of user experience and in the 3D Gui 
everything is displayed and calculated fine right now...


Maurice



On 11/9/2017 11:18 PM, Oliver Walters wrote:

Maurice,

The error is that the offset is stored (file format) in inches but it 
should be mm.


Now that I know that the issue is in the file, I'm happy that the 
internals to KiCad were working well, it just didn't make sense for the 
assumption that units were in mm


On 10 Nov 2017 08:39, "easyw" <mailto:ea...@katamail.com>> wrote:


Hi Oliver,

could you please explain me if the proposed patch/rework is fixing
an issue in 3d visualization and/or exporting or just changing the
fact that ATM the offset is stored in inches, compared to other
values in mm?

I remember that Mario avoided to change the internal kicad_pcb
format, but fixed the displaying of the offset calculating it
correctly and displaying correctly the value in inches or
millimeters, depending on the pcb settings both in the editor or the
model ...

I never noticed a wrong offset in VRML when exporting a board and
parts using the offset...
Nor I noticed a wrong offset in 3D viewer ...

I could say nothing about the step exporter because I use mine and
so I never tested the internal step exporter...

I attached an image of two cubes, the red is 1x1x1mm and the blue is
2x1x0.5mm.
I applied an offset of 1x1x1 in mm to the second one, and the
reciprocal positions are fine; moreover when I select the units to
mm I get the offset displayed in mm, and if I set the unit in
inches, the offset is displayed in inches...

Maurice



On 11/9/2017 9:09 PM, Oliver Walters wrote:

I like 2) or 3) - I think that a major release is a good time to
fix such a bug.

Would you like me to add a patch implementing one of these
options JP?

On 9 Nov 2017 23:33, "Kristoffer Ödmark"
mailto:kristofferodmar...@gmail.com>
<mailto:kristofferodmar...@gmail.com
<mailto:kristofferodmar...@gmail.com>>> wrote:

     Currently the footprints arent compatible anyway i guess, they
     support more than 4.07 footprints do. So option 2 is my
preferred
     solution.

     On 11/09/2017 12:51 PM, jp charras wrote:

         Le 09/11/2017 à 11:12, Kristoffer Ödmark a écrit :

             My 2 cents is that the headaches of storing values
in mixed
             units, without indication of which unit
             they are stored as is a huge drawback for
readability of the
             saved files and for maintainability.

             Also I think the proposed new tag offset is a good
idea,
             since the libraries can be gradually
             updated then. That the files cannot be opened by
previous
             versions is a minor problem, since the
             files cannot be opened by kicad 4.07 anyway already.


         In fact, footprint files can be opened by 4.07 version,
as long
         as they contain no round rect or
         custom pads (should be most of files)


             On 11/09/2017 12:55 AM, Wayne Stambaugh wrote:

                 This requires a file version bump and code that
tests
                 for prior versions
                 before converting the units on read.  At that
point, the
                 file will no
                 longer be compatible with prior version of
KiCad.  I'm
                 not opposed to
                 this but I'm not sure it's worth the headaches
it will
                 cause.

                 On 11/08/2017 03:33 PM, Oliver Walters wrote:

                     What about a controversial idea:

                     Read "at" dimensions as inches, but new
files write
                     "offset" in mm.

                     This preserves read compatibility but fixes the
                     units issue going forward.

         <...>

         There are 3 different things related to 

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

Hi Wayne,
I agree that probably the simplest and clearest solution it would be 
just to switch the reading depending on which version of pcbnew is the file.


In-fact it could be possible also to preserve the existing offset 
without the need to manually adjust the board.
If the pcbnew app would convert and write the present offset when saving 
an old pcbnew release to the new format, everything would be preserved.


This would be very useful not particularly for library footprints, which 
have already offset to (0,0,0) but for complex mechanical boards with 
mezzanine or other mechanical parts added to the pcb with i.e. offset as 
for alignment requirements.
The file format would be maintained with the same parsing, but just the 
reader/writer would fix the difference.


The ironic thing is that the bump in the file format would be created 
for a problem that started from a wrong assumption: that the 3D viewer 
and the exporters would make wrong internal calculation, without just 
testing it.
As already suggested by some of the main new 3D devs, a simple solution 
would have had to just document the offset units for 3D models.


I agree also with you again here :)

I'm not sure it's worth the headaches it will cause


Maurice

On 11/11/2017 2:49 PM, Wayne Stambaugh wrote:

Hold on a second before you prepare a patch.  This would introduce a new
semantic to the coordinate entries in the file format which could be
open to abuse in the future.  I don't want to open up the possibility of
using different units within the file format itself and adding units
token will open the door for that possibility.  I will also be confusing
to readability because all other units are in mm but do not have the
'mm' token except for 3D model offsets.  I would prefer that we do a one
time conversion to mm and bump the file format version rather than add a
new token to the file format.  The parser change would be fairly
straight forward:

if( file_version < VERSION )
 convert_units_from_decimils_to_mm();

The files will still be readable in previous version of kicad.
Obviously users will have to reset the offsets if they are not zero but
this typically isn't a big problem.

On 11/11/2017 03:57 AM, Oliver Walters wrote:

JP,

Yes I will update with a patch.

On 11 Nov 2017 19:45, "jp charras" mailto:jp.char...@wanadoo.fr>> wrote:

 Le 09/11/2017 à 21:48, Oliver Walters a écrit :
 > JP,
 >
 > I think that 3) is the better option, because it preservers PCB
 file compatibility (as long as the
 > offset is zero). Any time the PCB is saved, the (at (xyz 0 0 0))
 gets written.
 >
 > You are also correct that none of the official library footprints
 have a defined offset. This is why
 > i have never encountered this before.

 So I also think 3 is the better option:

 (at (xyz nn mm ll)) is read as position in inches (old files)
 (offset(xyz nn mm ll)) is read as position in mm (new files)

 And the position is written in file only if not 0 (that is the case
 of our footprint files) to avoid
 breaking the compatibility with older Pcbnew version when not
 mandatory, at least for now.

 Could you prepare a patch?
 Thanks.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

Unless a user used custom models or some of the older library models,
the offset will be 0,0,0 so I suspect the issues will be minimal and
will quickly diminish over time.
the issue will be on users that are using manufacturer's models for 3D 
step connectors and having assembly of boards (i.e. mezzanine)
So probably only users which are using intensively kicad for mechanical 
collaboration...


But this could be mitigated if the saving from an old release would 
convert the offset to new units ... Then also in the new format the 
offset would be preserved by the conversion.



The ironic thing is that the bump in the file format would be created
for a problem that started from a wrong assumption: that the 3D viewer
and the exporters would make wrong internal calculation, without just
testing it.


I'll take this one squarely on chin. 

Ah Ah sorry that was not intended :)
I was just saying that the initial patch was proposed with the 
assumption of wrong calculation of 3D offset in 3D viewer and exporters...


Maurice


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

Just a clarification request:

Kicad Stable has version assigned to 4
Previous stable had version assigned to 3

I imagine that next stable would have version assigned to 5...
Am I right in supposing the next numbering release?

If I'm fine, with the proposed patch the new stable release, if assigned 
coherently to actual releases numbering, will fail the check that is in 
this patch; the new parser will then mess up all 3D offsets each time 
the board will be saved/displayed...



+if(m_requiredVersion < 20171114UL)


As I already stated the actual situation has no problem in displaying 
the correct offset in 3D viewer and the exporters are fine...
The only 'issue', if we can say this is an issue, is that the offset is 
assigned to deci-mils and not millimeters inside the footprint...


This is going to open big headaches for which enhancement?
My 2 cents

Maurice



On 11/14/2017 10:55 AM, Oliver Walters wrote:

Wayne,

Please find attached updated patch set. If an old version is detected, 
inches are converted to mm.




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

Hi Orson,

I think you write this assuming the v5 file format will have 
m_requiredVersion set to 5. If I recall correctly, we have decided to 
use dates for file versioning and this method will be kept for v5 and 
later versions, so we should be safe here.


if this the new Version policy I missed, then this is fine.

Thanks for your clarification,

Maurice


On 11/15/2017 3:40 PM, Maciej Suminski wrote:

Hi Maurice,

On 15/11/2017 1:21 PM, easyw wrote:

Just a clarification request:

Kicad Stable has version assigned to 4
Previous stable had version assigned to 3

I imagine that next stable would have version assigned to 5...
Am I right in supposing the next numbering release?

If I'm fine, with the proposed patch the new stable release, if assigned
coherently to actual releases numbering, will fail the check that is in
this patch; the new parser will then mess up all 3D offsets each time
the board will be saved/displayed...


+    if(m_requiredVersion < 20171114UL)


I think you write this assuming the v5 file format will have 
m_requiredVersion set to 5. If I recall correctly, we have decided to 
use dates for file versioning and this method will be kept for v5 and 
later versions, so we should be safe here.



As I already stated the actual situation has no problem in displaying
the correct offset in 3D viewer and the exporters are fine...
The only 'issue', if we can say this is an issue, is that the offset is
assigned to deci-mils and not millimeters inside the footprint...

This is going to open big headaches for which enhancement?
My 2 cents


The solution Oliver has proposed looks solid to me, I do not see any 
potential headache. The patch has a very noble goal of fixing one of the 
biggest KiCad sins - incoherence. I think the reason is good enough to 
commit the patch.


Regards,
Orson


Maurice



On 11/14/2017 10:55 AM, Oliver Walters wrote:

Wayne,

Please find attached updated patch set. If an old version is detected,
inches are converted to mm.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Polygons: should have outline mode to draw Edge.Cuts

[easyw]

Hi Henner,

I know this is outside the KiCad branch, but if you want to manage 
complex board edges including arcs, ellipses or bsplines, you may 
consider useful KiCad StepUp...
Recently I've added a feature to allow the user to design the pcb edge 
in FreeCAD and push it to KiCad_pcb board file.


The collaboration between FreeCAD and KiCad is bi-directional, then 
revisions are possible...

You may have a look at a small tutorial here
https://youtu.be/n44iBpu_YjY
and at the KiCad info forum page
https://forum.kicad.info/t/kicad-stepup-the-sketcher-for-getting-to-blinky/7826

The idea is to manage complex board edges in a mechanical environment to 
be able to check collisions and dimension constraints.


Regards
Maurice

On 11/21/2017 6:42 AM, Henner Zeller wrote:

Hi,
So polygons are very neat as they employ the nice polygon drawing
features we are used to from zone drawing [*1].

A missing feature here is to _not_ have them filled but simply an
outline. Why ? This would be _very_ useful to draw Edge.Cuts.
Currently, the only way is to draw single lines, which are then hard
to adjust later, as they all fall apart into separate lines, and have
to be edited manually.

Now, if that could be drawn with the polygon tool, that would remove a
hge pain having to deal with outlines (and yes, I know the usual
advice to draw that separately and import as DXF. But what if I could
just do simple polygons directly ?).

Also what we could get for almost free then: Chamfers and Fillets. I
like to have boards with rounded corners [*2], but currently this is
of course a torture to do manually and and dread it every time it
comes to that part of the project: draw a rectangle with the line
tool. Do circles in the corners and manually calculate where the
center and the start point is, shorten the lines accordingly to match
the length shorter the radius. Do that on all four corners. That
easily takes several minutes and high concentration. And god forbid
one wants to change that again later ...

Now how wounderful that would be if that could be done with the
Polygon tool and I just choose to have a fillet or camfer. If this is
something nobody is working on yet and if people think this is a good
idea, I might have a look over the Thanksgiving days.

Cheers,
   Henner.


[*1] also see my mail before [All kinds of glitches], Polygons as-is
are currently broken and maybe the concept should be merged with the
zone ?

[*2] 
https://raw.githubusercontent.com/hzeller/quadrigotion/master/img/tmc2660-quad-render.jpg

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

Hi,
first headache symptom...

Testing conditions:
latest KiCad patched
Application: pcbnew
Version: (2017-11-21 revision 8de70f3)-master, release build

If you edit a footprint adding 3D models offset and then export it, it 
will be saved with the new mm convention...
but when re-imported it will be read with deci-mils and displayed with 
wrong convention...
Moreover if the imported footprint will be inserted into the board, the 
footprint will conserve the wrong values...

Those wrong values will be then saved with the new kicad_pcb board

On 11/15/2017 3:40 PM, Maciej Suminski wrote:

Hi Maurice,

On 15/11/2017 1:21 PM, easyw wrote:

Just a clarification request:

Kicad Stable has version assigned to 4
Previous stable had version assigned to 3

I imagine that next stable would have version assigned to 5...
Am I right in supposing the next numbering release?

If I'm fine, with the proposed patch the new stable release, if assigned
coherently to actual releases numbering, will fail the check that is in
this patch; the new parser will then mess up all 3D offsets each time
the board will be saved/displayed...


+    if(m_requiredVersion < 20171114UL)


I think you write this assuming the v5 file format will have 
m_requiredVersion set to 5. If I recall correctly, we have decided to 
use dates for file versioning and this method will be kept for v5 and 
later versions, so we should be safe here.



As I already stated the actual situation has no problem in displaying
the correct offset in 3D viewer and the exporters are fine...
The only 'issue', if we can say this is an issue, is that the offset is
assigned to deci-mils and not millimeters inside the footprint...

This is going to open big headaches for which enhancement?
My 2 cents


The solution Oliver has proposed looks solid to me, I do not see any 
potential headache. The patch has a very noble goal of fixing one of the 
biggest KiCad sins - incoherence. I think the reason is good enough to 
commit the patch.


Regards,
Orson


Maurice



On 11/14/2017 10:55 AM, Oliver Walters wrote:

Wayne,

Please find attached updated patch set. If an old version is detected,
inches are converted to mm.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

I think you just need to patch the footprint editor importer to fix this...

I think this fork for footprint format will add more 'rumors' in 
libraries for something that just worked fine ... (only not to be adding 
a note in the docs that footprint offset were in deci-mils)

Anyway
Alea iacta est

my other 2 cents

On 11/21/2017 10:26 PM, Oliver Walters wrote:

Wayne,

Not sure how you want to handle this but I feel that making a clean 
break and using "offset" for mm solves all the issues associated with 
embedded footprints without version info, as Maurice says above. Let me 
know if want me to implement.


On Wed, Nov 22, 2017 at 8:24 AM, easyw <mailto:ea...@katamail.com>> wrote:


Hi,
first headache symptom...

Testing conditions:
latest KiCad patched
Application: pcbnew
Version: (2017-11-21 revision 8de70f3)-master, release build

If you edit a footprint adding 3D models offset and then export it,
it will be saved with the new mm convention...
but when re-imported it will be read with deci-mils and displayed
with wrong convention...
Moreover if the imported footprint will be inserted into the board,
the footprint will conserve the wrong values...
Those wrong values will be then saved with the new kicad_pcb board

On 11/15/2017 3:40 PM, Maciej Suminski wrote:

Hi Maurice,

    On 15/11/2017 1:21 PM, easyw wrote:

Just a clarification request:

Kicad Stable has version assigned to 4
Previous stable had version assigned to 3

I imagine that next stable would have version assigned to 5...
Am I right in supposing the next numbering release?

If I'm fine, with the proposed patch the new stable release,
if assigned
coherently to actual releases numbering, will fail the check
that is in
this patch; the new parser will then mess up all 3D offsets
each time
the board will be saved/displayed...

+    if(m_requiredVersion < 20171114UL)


I think you write this assuming the v5 file format will have
m_requiredVersion set to 5. If I recall correctly, we have
decided to use dates for file versioning and this method will be
kept for v5 and later versions, so we should be safe here.

As I already stated the actual situation has no problem in
displaying
the correct offset in 3D viewer and the exporters are fine...
The only 'issue', if we can say this is an issue, is that
the offset is
assigned to deci-mils and not millimeters inside the
footprint...

This is going to open big headaches for which enhancement?
My 2 cents


The solution Oliver has proposed looks solid to me, I do not see
any potential headache. The patch has a very noble goal of
fixing one of the biggest KiCad sins - incoherence. I think the
reason is good enough to commit the patch.

Regards,
Orson

Maurice



On 11/14/2017 10:55 AM, Oliver Walters wrote:

Wayne,

Please find attached updated patch set. If an old
version is detected,
inches are converted to mm.


___
Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
More help   : https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>


___
Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
More help   : https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>


___
Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
Post to     : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
More help   : https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHel

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

Hi Wayne,

I'm not sure I understand what the issue is.  Once an offset is changed
to mm when either a footprint in a board or a library is parsed, why
would it not be saved as mm.  If it isn't, then this is a bug.  Once the
footprint offset is converted to mm, there should be no expectation that
it will be correct for older versions of KiCad.  Is there something else
at play here?


this issue is related to the footprint editor...

1) The fp exporter button exports correctly the footprint with offset in mm
2) The fp importer button imports always reading the data as deci-mils 
and multiplies it internally
3) To fix this issue the patch needs to manage the footprint importer 
code to read the values in mm instead of deci-mils.



What if you open the same file again, how can it tell it's in mm or inches?

@Jose ... this is an issue already addressed...
The decision to change offset values to mm will break previous 
footprints that have non zero offset.
But I think this has been considered a 'small' disturb for users when 
the patch has been committed, as stated in a previous mail:

This is not a big issue because the only effects the footprints embedded
in the board.  Users with custom footprint libraries that contain 3D
model offsets will just have to fix the offsets.  I'm guessing this is a
fairly small number of users.

https://lists.launchpad.net/kicad-developers/msg31589.html

M

On 11/22/2017 2:19 AM, Wayne Stambaugh wrote:

I'm not sure I understand what the issue is.  Once an offset is changed
to mm when either a footprint in a board or a library is parsed, why
would it not be saved as mm.  If it isn't, then this is a bug.  Once the
footprint offset is converted to mm, there should be no expectation that
it will be correct for older versions of KiCad.  Is there something else
at play here?

On 11/21/2017 04:26 PM, Oliver Walters wrote:

Wayne,

Not sure how you want to handle this but I feel that making a clean
break and using "offset" for mm solves all the issues associated with
embedded footprints without version info, as Maurice says above. Let me
know if want me to implement.

On Wed, Nov 22, 2017 at 8:24 AM, easyw mailto:ea...@katamail.com>> wrote:

 Hi,
 first headache symptom...

 Testing conditions:
 latest KiCad patched
 Application: pcbnew
 Version: (2017-11-21 revision 8de70f3)-master, release build

 If you edit a footprint adding 3D models offset and then export it,
 it will be saved with the new mm convention...
 but when re-imported it will be read with deci-mils and displayed
 with wrong convention...
 Moreover if the imported footprint will be inserted into the board,
 the footprint will conserve the wrong values...
 Those wrong values will be then saved with the new kicad_pcb board



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

I believe he has a point. The footprint files do not have version 
information so if you load and save a footprint multiple times, the 
"offset" (if non zero) will continuously be multiplied by 2.54x
This is not true if the footprint importer will be patched to read the 
data as mm from now on...



I think there are two ways forward:

1. Revert my patch and live with the file format unit inconsistency
If I could vote, I would vote for this option that will reduce to zero 
the disturb to users...
We would just need to add a note to docs that offset in fp are written 
and read in inches.
The user will never notice that because the sw already does the right 
conversion inside... you could notice this 'inconsistency' only if you 
open the fp in text editor
Footprint editor, 3D viewer, Vrml exporter already were managing 
correctly this 'inconsistency' internally
In more than one year from the new 3D viewer release, I noticed no 
bugs/issues reported on this matter


M


On 11/22/2017 12:16 PM, Oliver Walters wrote:

Wayne,


I believe he has a point. The footprint files do not have version 
information so if you load and save a footprint multiple times, the 
"offset" (if non zero) will continuously be multiplied by 2.54x


I think there are two ways forward:

1. Revert my patch and live with the file format unit inconsistency
2. I can provide a patch for my original idea of writing "offset" 
instead of "at". We make a clean break and "at" is legacy and always 
read as inches. "offset" is new and is mm.


Let me know what you want to do.

Thanks,
Oliver

On Wed, Nov 22, 2017 at 8:25 PM, easyw <mailto:ea...@katamail.com>> wrote:


Hi Wayne,

I'm not sure I understand what the issue is.  Once an offset is
changed
to mm when either a footprint in a board or a library is parsed, why
would it not be saved as mm.  If it isn't, then this is a bug. 
Once the

footprint offset is converted to mm, there should be no
expectation that
it will be correct for older versions of KiCad.  Is there
something else
at play here?


this issue is related to the footprint editor...

1) The fp exporter button exports correctly the footprint with
offset in mm
2) The fp importer button imports always reading the data as
deci-mils and multiplies it internally
3) To fix this issue the patch needs to manage the footprint
importer code to read the values in mm instead of deci-mils.

What if you open the same file again, how can it tell it's in mm
or inches?

@Jose ... this is an issue already addressed...
The decision to change offset values to mm will break previous
footprints that have non zero offset.
But I think this has been considered a 'small' disturb for users
when the patch has been committed, as stated in a previous mail:

This is not a big issue because the only effects the footprints
embedded
in the board.  Users with custom footprint libraries that contain 3D
model offsets will just have to fix the offsets.  I'm guessing
this is a
fairly small number of users.

https://lists.launchpad.net/kicad-developers/msg31589.html
<https://lists.launchpad.net/kicad-developers/msg31589.html>

M


On 11/22/2017 2:19 AM, Wayne Stambaugh wrote:

I'm not sure I understand what the issue is.  Once an offset is
changed
to mm when either a footprint in a board or a library is parsed, why
would it not be saved as mm.  If it isn't, then this is a bug. 
Once the

footprint offset is converted to mm, there should be no
expectation that
it will be correct for older versions of KiCad.  Is there
something else
at play here?

On 11/21/2017 04:26 PM, Oliver Walters wrote:

Wayne,

Not sure how you want to handle this but I feel that making
a clean
break and using "offset" for mm solves all the issues
associated with
embedded footprints without version info, as Maurice says
above. Let me
know if want me to implement.

On Wed, Nov 22, 2017 at 8:24 AM, easyw mailto:ea...@katamail.com>
<mailto:ea...@katamail.com <mailto:ea...@katamail.com>>> wrote:

      Hi,
      first headache symptom...

      Testing conditions:
      latest KiCad patched
      Application: pcbnew
      Version: (2017-11-21 revision 8de70f3)-master, release
build

      If you edit a footprint adding 3D models offset and
then export it,
      it will be saved with the new mm convention...
 

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

Hi Jose,
I have several footprints that use manufacturer's models, where offsets 
and rotations are necessary. I really fail to see the point of breaking 
people's designs and libraries needlessly.
this is probably quite common when a user needs some connector models 
for his/her production, getting the model directly from the manufacturer 
(which is the best option IMO for connectors)...


Then probably a lot of users which are using the dev release and use to 
align STEP models inside KiCad will be affected...

for that reason I was against this change :)
Luckily this change doesn't not affect the boards, but only library models.

Anyway what I could suggest is:
A) use StepUp to align the models to their footprints inside FreeCAD, so 
to have all the offsets assigned to zero... this will help you also in 
having the alignment precise as it can be in a mechanical environment
(I have almost a thousand of 3D manufacturer's models and I only had to 
fix 7 of them)


or:
B) make a script to process your previous 3D libraries and convert 
automatically the offset from deci-mils to mm (luckily kicad has text 
format libraries)


Maurice


On 11/22/2017 3:51 PM, José Ignacio wrote:
I have several footprints that use manufacturer's models, where offsets 
and rotations are necessary. I really fail to see the point of breaking 
people's designs and libraries needlessly.


On Nov 22, 2017 7:07 AM, "Wayne Stambaugh" <mailto:stambau...@gmail.com>> wrote:


What is wrong with just reading the footprint in mm rather than
converting from decimils from now on?  It's only going to be a one time
issue when a user adds a footprint that has not been converted to mm to
a board.

On 11/22/2017 06:16 AM, Oliver Walters wrote:
 > Wayne,
 >
 >
 > I believe he has a point. The footprint files do not have version
 > information so if you load and save a footprint multiple times, the
 > "offset" (if non zero) will continuously be multiplied by 2.54x
 >
 > I think there are two ways forward:
 >
 > 1. Revert my patch and live with the file format unit inconsistency
 > 2. I can provide a patch for my original idea of writing "offset"
 > instead of "at". We make a clean break and "at" is legacy and always
 > read as inches. "offset" is new and is mm.
 >
 > Let me know what you want to do.
 >
 > Thanks,
 > Oliver
 >
 > On Wed, Nov 22, 2017 at 8:25 PM, easyw mailto:ea...@katamail.com>
 > <mailto:ea...@katamail.com <mailto:ea...@katamail.com>>> wrote:
 >
 >     Hi Wayne,
 >
 >         I'm not sure I understand what the issue is.  Once an
offset is
 >         changed
 >         to mm when either a footprint in a board or a library is
parsed, why
 >         would it not be saved as mm.  If it isn't, then this is a
bug.
 >         Once the
 >         footprint offset is converted to mm, there should be no
 >         expectation that
 >         it will be correct for older versions of KiCad.  Is there
 >         something else
 >         at play here?
 >
 >
 >     this issue is related to the footprint editor...
 >
 >     1) The fp exporter button exports correctly the footprint with
 >     offset in mm
 >     2) The fp importer button imports always reading the data as
 >     deci-mils and multiplies it internally
 >     3) To fix this issue the patch needs to manage the footprint
 >     importer code to read the values in mm instead of deci-mils.
 >
 >         What if you open the same file again, how can it tell
it's in mm
 >         or inches?
 >
 >     @Jose ... this is an issue already addressed...
 >     The decision to change offset values to mm will break previous
 >     footprints that have non zero offset.
 >     But I think this has been considered a 'small' disturb for users
 >     when the patch has been committed, as stated in a previous mail:
 >
 >         This is not a big issue because the only effects the
footprints
 >         embedded
 >         in the board.  Users with custom footprint libraries that
contain 3D
 >         model offsets will just have to fix the offsets.  I'm
guessing
 >         this is a
 >         fairly small number of users.
 >
 > https://lists.launchpad.net/kicad-developers/msg31589.html
<https://lists.launchpad.net/kicad-developers/msg31589.html>
 >     <https://lists.launchpad.net/kicad-developers/msg31589.html
<https://lists.launchpad.net/kicad-de

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

This option is in fact a smooth transition for footprints...
but it will break the readability of new boards by previous release of 
kicad... no way back to previous releases, even to be just read...

Which is better then?
Library stuff are quite delicate to be touched IMO...

On 11/22/2017 10:23 PM, Oliver Walters wrote:
Wayne I still have an issue with silently breaking files. Using an 
"offset" parameter (but reading "at" for compatibility) does not break 
anyone's models and there is absolutely no confusion about which is mm 
and which is inches. Incidentally I think "offset" is a better name, it 
implies relative position rather than absolute (but that's neither here 
nor there).


On Thu, Nov 23, 2017 at 7:55 AM, Marcos Chaparro > wrote:


On Wed, Nov 22, 2017 at 11:59 AM, Wayne Stambaugh
mailto:stambau...@gmail.com>> wrote:

Yes, it is a change that will break some users 3D models
but I think the long term benefit outweighs the short term
annoyance.


It will break most of my boards. I won't complain because I
appreciate the effort and I welcome *every* improvement, but be
prepared for some very rough comments out there.

___
Mailing list: https://launchpad.net/~kicad-developers

Post to     : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

I understand this will break "forwards compatibility" if opening a v5 
file from v4. 

and this break will be also 'silent'
Sometimes such changes are unavoidable.point of views ... as I already pointed out I don't remember how many 
times, this changing is started for a wrong assumption: that 3D viewer 
and exporters would have failed in managing the 3D offsets... which is 
wrong... this wrong assumption started a misunderstanding of the issue 
itself.
Moreover the internal representation of a data that was just simple 
correctly managed is a real formal issue and not a user issue...
So, IMO, this was something absolutely avoidable instead of something 
unavoidable...

but this is obviously my point of view...

On 11/22/2017 11:16 PM, Oliver Walters wrote:
I understand this will break "forwards compatibility" if opening a v5 
file from v4. Sometimes such changes are unavoidable.


On Thu, Nov 23, 2017 at 8:44 AM, easyw <mailto:ea...@katamail.com>> wrote:


This option is in fact a smooth transition for footprints...
but it will break the readability of new boards by previous release
of kicad... no way back to previous releases, even to be just read...
Which is better then?
Library stuff are quite delicate to be touched IMO...

On 11/22/2017 10:23 PM, Oliver Walters wrote:

Wayne I still have an issue with silently breaking files. Using
an "offset" parameter (but reading "at" for compatibility) does
not break anyone's models and there is absolutely no confusion
about which is mm and which is inches. Incidentally I think
"offset" is a better name, it implies relative position rather
than absolute (but that's neither here nor there).

On Thu, Nov 23, 2017 at 7:55 AM, Marcos Chaparro
mailto:nitrous...@gmail.com>
<mailto:nitrous...@gmail.com <mailto:nitrous...@gmail.com>>> wrote:

     On Wed, Nov 22, 2017 at 11:59 AM, Wayne Stambaugh
     mailto:stambau...@gmail.com>
<mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>> wrote:

         Yes, it is a change that will break some users 3D models
         but I think the long term benefit outweighs the short term
         annoyance.


     It will break most of my boards. I won't complain because I
     appreciate the effort and I welcome *every* improvement, but be
     prepared for some very rough comments out there.

     ___
     Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
     <https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>>
     Post to     : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
     <mailto:kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>>
     Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
     <https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>>
     More help   : https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>
     <https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>>




___
Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
Post to     : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
More help   : https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>


___
Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
Post to     : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
More help   : https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

[easyw]

I think the master branch already has enough new features to make its
output incompatible with v4. 'Offset' approach seems the easiest and
cleanest solution IMHO.


the 'offset' thing is creating a stopper for kicad 4 release as well as 
i.e. rounded rectangle pad does... kicad 4 just would stop loading the 
board
but the offset is a very 'basic' feature compared to rounded rectangle 
which is extremely rared used...


The new field 'offset' instead of 'at' or eventually the use of both 
depending of the offset values in the descriptor seems top me a big 
headache just to avoid the initial 'inconsistency' of a footprint 
descriptor that had 'deci-mils' for a single internal field, but that 
was just correctly managed by the sw...



Cheers
Maurice



On 11/23/2017 9:05 AM, Maciej Sumiński wrote:

I think the master branch already has enough new features to make its
output incompatible with v4. 'Offset' approach seems the easiest and
cleanest solution IMHO.

Cheers,
Orson

On 11/22/2017 11:16 PM, Oliver Walters wrote:

I understand this will break "forwards compatibility" if opening a v5 file
from v4. Sometimes such changes are unavoidable.

On Thu, Nov 23, 2017 at 8:44 AM, easyw  wrote:



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] kicad_pcb, kicad_mod format change for daily build?

[easyw]

Hi,
recently I have noticed that both kicad_pcb and kicad_mod seems to have 
changed their format.

It have been introduced double quotes for layers pads etc.
Is that necessary or intentional?

Here two related issues links:
footprint
https://github.com/easyw/kicadStepUpMod/issues/13#issuecomment-481160108
pcb
https://forum.kicad.info/t/bad-layer-data-error-when-exporting-step/16322/11

and a small diff example:

(layers
(0 F.Cu signal)
(31 B.Cu signal)

(layers
(0 "F.Cu" signal)
(31 "B.Cu" signal)

Thanks
Maurice

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Monster files wanted

[easyw]

Hi,
please have a look at this board (12 layers)
https://github.com/ciaa/Hardware/blob/master/PCB/ACC/CIAA_ACC/ciaa_acc.kicad_pcb
this is from 'Made with KiCAD' section.

M

On 04/16/2019 11:27 AM, John Beard wrote:

Hi,

Occasionally, there are references made to performance during
processing of very large >8 layer PCBs (and the schematics thereof).
However, I don't have any such PCBs to uses as a reference, and there
are (reasonably, due to the size) none in the demos folder.

I can make faked-up PCBs programmatically fairly easily (it's what was
used in the DRC benchmarks a few weeks ago). But they are not
necessarily representative of real workloads (or at least, cannot be
demonstrated to be so).

So, what are the biggest, meanest, most complex, processor-killing,
resource-hogging, KiCad-crashing bad boys that people know of?
Preferably open-source so they can be shared easily and used for
benchmarking purposes.

Cheers,

John

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Board statistics dialog

[easyw]

  
Hi, 
nice addition indeed... 
You may find someone with the same
needs at the forum

https://forum.kicad.info/t/how-to-get-pin-count-and-board-size-for-assembly/17792

There is a small plugin offering this option ATM,  
listing what Mario
is asking for... 
It would be nice to have it in the main branch.

Maurice 

Il 04.07.2019 16:28 Mário Luzeiro ha scritto: 

> Hi SHuklin!
( is this the romanization of your name? :) )
> 
> This is just my user
feedback:
> That is a cool addition, another feature suggestions would
be to list the components by "Fabrication attributes" "Through
hole"/"Surface mount"/"Virtual" Each footprint has this attribute so I
guess you can easily count it.
> They are important values for
calculation costs of the assembly.
> 
> Mario Luzeiro
> 
>

> From: Kicad-developers on
behalf of Шуклин Александр 
> Sent: 04 July 2019 15:06
> To:
kicad-developers@lists.launchpad.net [3]
> Subject: [Kicad-developers]
[PATCH] Board statistics dialog
> 
> Hi, that's first time I try to
contribute to KiCad and write to Launchpad mailing lists, so please,
don't beat me to hard )))
> I really miss some board statistic dialog,
where you can see quantity of SMD pads, THT pads, board dimensions, all
the stuff, you need for PCB production and assembly. There was also
issue in the bug tracker
> https://bugs.launchpad.net/kicad/+bug/1817232
[4]
> And like guy from bug issue, I moved from Altium Designer and miss
that dialog as well.
> Can you please look at that and commit if you
think it's useful or tell me what to change.
> That's my commit in the
github:
>
https://github.com/jasuramme/kicad-source-mirror/commit/6290375c1d41ddb89d4b08067593f170c7d344c5
[5]
> and branch:
>
https://github.com/jasuramme/kicad-source-mirror/tree/statistic_dialog
[6]
> and there's also patch and dialogs pics in the attachment.
> 
>
___
> Mailing list:
https://launchpad.net/~kicad-developers [7]
> Post to :
kicad-developers@lists.launchpad.net [8]
> Unsubscribe :
https://launchpad.net/~kicad-developers [9]
> More help :
https://help.launchpad.net/ListHelp [10]
  


Con Mobile Open 7 GB a 9 euro/4 sett navighi veloce con 7 GB di Internet e hai 
200 minuti ed SMS a 15 cent. Passa a Tiscali Mobile! http://tisca.li/Open7GB0617

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Arc Adjustment proposal

[easyw]

On 07/10/2019 9:02 PM, Wayne Stambaugh wrote:

Don't forget, this will impact all import from and export to 3rd party
file formats so it's not going to be a trivial change.

Wayne


Then it could be introduced an extra way to define arcs only for tracks, 
leaving the previous definition unaltered for drawings and edges.

The pcb format would be changed only if used Arc tracks in the board.

On 07/10/2019 7:25 PM, Seth Hillbrand wrote:> I'd like to adjust how our 
arcs are handled and stored.  This is part of
the arc tracks work package but is sufficiently tangential that I think 
it bears checking before I implement.


Problem: Arcs are stored in the pcbnew file using center, start point 
and arc angle.  This leaves the end point of the arc subject to rounding 
errors.  This causes problems in STEP export as well as (for the arc 
tracks) connectivity issues as dragging requires point matching, not 
just copper overlap.


The issue on edge STEP export (board edge not closed) is related to the 
following:


On 07/10/2019 10:52 PM, Eeli Kaikkonen wrote:> For what it's worth, in 
normal graphical arcs (especially in edge cuts) the

two endpoints (or start and end) are usually important, the centerpoint
isn't.


This is not true. Generally for mechanical concerns, you should start 
exactly from the centers, which are the anchors of your board.
If you start your design with mechanical constraints in mind, your board 
will not have EdgeCuts issues.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Arc Adjustment proposal

[easyw]

On 07/11/2019 12:05 PM, Dino Ghilardi wrote:

My two cents...

Unfortunatly some times the centers are anchors of the board, other 
times they are not: when the external case is designed by a "fashon 
designer" and you have to put your electronics inside, the board 
outlines can be quite weird, not (totally) under our control and the 
centers of the board outline arcs are not always anchor points. The 
problem is that both the approaches make sense in some situations: 
sometimes you like an "exact" center, some others you like "exact" 
endpoints.


then your fashion design should use a proper CAD to design the board, 
and the EDGE should then imported inside KiCAD i.e. from a svg or a dxf 
file or handled directly with FreeCAD.



Personnally I ran into the "endpoint" problem for some board edges, 
since to close the perimeter of the board for a step export, the arc 
start/endpoint need to be exact, while having an exact arc center was 
not so important (considering also the resolution used in kicad and the 
mechanical tolerances of the real word, an error of some nm in the 
center position should not be a problem).


There is a Snap option in KiCAD to make an end of a segment snapping to 
a selected end point.

You can do this by holding the Alt key while moved an end point.





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Arc Adjustment proposal

[easyw]

On 07/11/2019 1:21 PM, Dino Ghilardi wrote:

On 11/07/19 12:26, easyw wrote:
then your fashion design should use a proper CAD to design the board, 
and the EDGE should then imported inside KiCAD i.e. from a svg or a 
dxf file or handled directly with FreeCAD.


Yes, he should... but he won't: (he's not under my control).


I don't get your user case...
are you receiving
1) a KiCAD pcb board from your fashion designer
or
2) the enclosure for your board, coming from the fashion designer
or
3) the outline of the pcb in external format

The 1) is quite a weird case... your fashion designer should us 
mechanical sw to define the board outlines


The 2) case is totally on your control...
you need to use a mechanical sw to create pcb outline fitting your enclosure

The same for the 3) case, you can fix the file before importing inside 
kicad.


Please have a search for "ECAD MCAD Collaboration" for a deeper insight

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Arc Adjustment proposal

[easyw]

On 07/11/2019 5:17 PM, Jeff Young wrote:


Here’s a footprint I drew recently which was made much harder by Kicad’s focus 
on arc centre points:



This is exactly an example that should be done in a mechanical CAD and 
imported later in KiCAD (i.e. as DXF).


Complex mechanical object should be addressed with mechanical CAD, not ECAD.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Arc Adjustment proposal

[easyw]

Don't get me wrong... I don't say KiCad has not to be improved.

I just say that complex mechanical objects have to be designed and 
checked in a mechanical environment.


And that is exactly what we have done with the KiCAd libraries...
Most of footprints are designed using scripts and are checked using a 
mechanical sw.


I agree that a new user should find a decent drawing editor, but when 
he/she gets experienced, the right direction is toward a MCAD/ECAD 
collaboration.


All commercial ECADs do it already, even with the entry level products.
So mechanical collaboration should be strongly suggested IMO.

Maurice


On 07/11/2019 6:51 PM, Jon Evans wrote:

I strongly disagree with this mindset.
It feels like saying that because KiCad is currently bad at something, it
should always be bad at something and users should just use a different
tool because KiCad will never be good at it.
If we have the developer interest to make KiCad good at drawing things, why
not do so?
It doesn't help that the available FOSS MCAD tools are (in my opinion) much
less capable relative to their commercial competitors than KiCad is
relative to commercial ECAD tools.

-Jon

On Thu, Jul 11, 2019 at 12:16 PM easyw  wrote:



On 07/11/2019 5:17 PM, Jeff Young wrote:


Here’s a footprint I drew recently which was made much harder by Kicad’s

focus on arc centre points:




This is exactly an example that should be done in a mechanical CAD and
imported later in KiCAD (i.e. as DXF).

Complex mechanical object should be addressed with mechanical CAD, not
ECAD.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] MOD_VIRTUAL flag

[easyw]

  
Virtual is also used to show/hide mechanical models (like i.e.
enclosures etc.)

https://forum.kicad.info/t/feature-request-add-opacity-property-for-3d-models-enclosures/8799

https://forum.kicad.info/t/virtual-schematic-component/3558/4
https://lists.launchpad.net/kicad-developers/msg23414.html

Il
22.07.2019 06:03 Jeff Young ha scritto: 

> This flag tells us that
there's no physical object for a pick-n-place machine. But is it also
true that there's no corresponding symbol in the schematic, or are there
some virtual footprints that would have a symbol?
> 
> What about some
microwave elements, for instance? Do they have symbols?
>
___
> Mailing list:
https://launchpad.net/~kicad-developers [1]
> Post to :
kicad-developers@lists.launchpad.net [2]
> Unsubscribe :
https://launchpad.net/~kicad-developers [3]
> More help :
https://help.launchpad.net/ListHelp [4]
  


Con Mobile Open 7 GB a 9 euro/4 sett navighi veloce con 7 GB di Internet e hai 
200 minuti ed SMS a 15 cent. Passa a Tiscali Mobile! http://tisca.li/Open7GB0617

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Fwd: Re: [PATCH] Fix for 3D model offset

[easyw]

just a side note on this thread:
this latest patch is messing up all the previous offset values in boards 
that a user, which had the latest and previous patched pcbnew, opened 
and saved ...
And obviously this mess is happening in a 'silent' way, without any 
warning message for the user which will find all the offset multiplied 
by 25.4...

IMO this is just a bigger headache than what I even thought it may have been


On 12/01/2017 4:17 PM, Wayne Stambaugh wrote:

On 12/01/2017 06:31 AM, jp charras wrote:

Le 30/11/2017 à 13:43, Oliver Walters a écrit :

Rebuilt and attached

On Thu, Nov 30, 2017 at 7:53 PM, jp charras mailto:jp.char...@wanadoo.fr>>
wrote:


  Message transféré 
 Sujet : Re: [Kicad-developers] [PATCH] Fix for 3D model offset
 Date : Thu, 30 Nov 2017 09:43:05 +0100
 De : jp charras mailto:jp.char...@wanadoo.fr>>
 Répondre à : KiCad Developers mailto:kicad-developers@lists.launchpad.net>>
 Pour : Oliver Walters mailto:oliver.henry.walt...@gmail.com>>

 Le 30/11/2017 à 08:38, Oliver Walters a écrit :
 > JP, Wayne,
 >
 > Any update on how we want to handle this?


Looks good to me now.

Wayne, do you want me to commit these patchs?



Please commit this patch when you get a chance.  The reason it took me
so long to pull the trigger on this is that I was trying to think of a
better way to handle it.  I can not really think of a better solution so
we will have to live with it unless someone else has a better idea.
It's best to make the change so everyone will get their complaining over
with now rather than later.  I think for version 6, I would like to
revisit the footprint file format given some of its limitations but I'm
going to hold off on that until after the new schematic file formats are
done.

Thanks,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Selection filtering, and other missing GAL functionality

[easyw]

it would be possible to add 'Vias' to selection filtering?
That would be useful for deleting a Via stitching zone, without touching 
tracks


Thx

On 03/08/2018 12:03 AM, Tomasz Wlostowski wrote:

On 07/03/18 23:59, Jeff Young wrote:

Drag Footprint.


Working on that :)

Don't expect miracles, but basic P&S footprint dragging should be in
early V6.

Tom



On 7 Mar 2018, at 22:20, Jon Evans  wrote:

Hi all,

As part of preparing a new 6.0 roadmap, I want to make sure we have all 
functionality that only exists in Legacy mode captured on Launchpad so we don't 
forget about it.  José just reminded me that Legacy mode in PcbNew has some 
selection filtering features that don't exist in GAL, so selection filtering is 
one case where I don't think we currently have a launchpad bug (or at least 
it's not easily searchable or tagged with missing-gal-tool).

Are there others besides this? (and printing, obviously)
Some stuff about polygon behavior I think?

-Jon
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] official web page

[easyw]

Hi Wayne,

I've done a first kicad StepUp starting guide...

it is an asciidoc with some images

I attached the adoc+images in 7z format

is it fine or should I do something else to add it to the doc repository?

thank you
Maurice

On 05/08/2015 14.27, Wayne Stambaugh wrote:

Maurice,

I think Marco is currently on vacation.  The new documentation format is
asciidoc.  You can use git to clone the current documentation at
https://github.com/ciampix/kicad-doc.  Information on how to use
asciidoc can be found at http://www.methods.co.nz/asciidoc/

Wayne

On 8/5/2015 8:23 AM, easyw wrote:

@Marco

what could I do to prepare a small tutorial for the kicad stepup script?
do you accept libre-office file or pdf file?
I'm sorry but I'm new to the doc side :)

thank you
Maurice

On 17/07/2015 15.12, Wayne Stambaugh wrote:

On 7/17/2015 3:36 AM, Mário Luzeiro wrote:

Excellent!

Do you (all) think should be nice to have a small step tutorial /
explanation how can someone reproduce identical results for another
boards?


Yes.  Any help we can provide our users is a good thing.  Something like
this should be added to the user documentation either as part of the
Pcbnew manual or as a stand alone tutorial.  I don't have a preference
one way or another so I'll leave that decision to our documentation
experts.



Mario Luzeiro
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] official web page

[easyw]

Hi Wayne,

sorry 7z will not be attached...

ok I'm trying with plain text

I've done a first kicad StepUp starting guide...

it is an asciidoc with some images (to put in images/ dir)

I attached the adoc+images

is it fine or should I do something else to add it to the doc repository?

thank you
Maurice

On 05/08/2015 14.27, Wayne Stambaugh wrote:

Maurice,

I think Marco is currently on vacation.  The new documentation format is
asciidoc.  You can use git to clone the current documentation at
https://github.com/ciampix/kicad-doc.  Information on how to use
asciidoc can be found at http://www.methods.co.nz/asciidoc/

Wayne

On 8/5/2015 8:23 AM, easyw wrote:

@Marco

what could I do to prepare a small tutorial for the kicad stepup script?
do you accept libre-office file or pdf file?
I'm sorry but I'm new to the doc side :)

thank you
Maurice

On 17/07/2015 15.12, Wayne Stambaugh wrote:

On 7/17/2015 3:36 AM, Mário Luzeiro wrote:

Excellent!

Do you (all) think should be nice to have a small step tutorial /
explanation how can someone reproduce identical results for another
boards?


Yes.  Any help we can provide our users is a good thing.  Something like
this should be added to the user documentation either as part of the
Pcbnew manual or as a stand alone tutorial.  I don't have a preference
one way or another so I'll leave that decision to our documentation
experts.



Mario Luzeiro


Kicad StepUp starter Guide
==
:Author:Maurice
:Email:     https://launchpad.net/~easyw
:Author Initials: MEW
:Date:  August 2015
:Revision:  1.1
:website: http://sourceforge.net/projects/kicadstepup/
:docname: readme-kicadStepUp.adoc

kicad StepUp: a new approach to export kicad board and modules in STEP AP214 
(with colors).
With kicad StepUp it is possible to export the 3D board and modules in STEP
for MCAD interchange and create the 3D wrl libraries. +

link:http://sourceforge.net/projects/kicadstepup/[kicadStepUp at sourceforge] +
link:http://bazaar.launchpad.net/~easyw/kicad-stepup/trunk/files/[kicadStepUp 
at lauchpad]

.OverView
**
to run the demo:

in Linux:
change dir to the folder in which you have extracted the demo +
./launch-kicad_StepUp-demo.sh

in windows:
change dir to the folder in which you have extracted the demo +
launch-kicad_StepUp-demo.bat

the demo comes with a kicad project, along with all needed STEP and wrl 
modules, just to be used just out of the box +
(*NB* use the script from inside the dir)

here there is also a link of the script in action... +
link:http://youtu.be/Ukd47VXYzQU[YouTube Kicad StepUp demo video]

*requirements:*
kicad 2015 stable or latest dev release, freecad 0.15
**

Introduction

Kicad StepUp allows the user to modeling the 3D modules starting from FreeCAD
(instead of using Wings3D), creating models in STEP AP214 and rendering the
pcb board and components in native STEP AP214.

Designing in kicad native 3d-viewer will produce a fully aligned STEP version
with the same view of kicad 3d render. +
Now you will have the two words with the same appearance; one can design in 
kicad EDA and transfer the artwork to MCAD (FreeCAD) smoothly

*WYSIWYG from EDA to MCAD*

.kicad StepUp in Kicad 3d-viewer
image::images/hackrf-one-stepup-kicad-3d-viewer.png[]

.kicad StepUp in MCAD Catia
image::images/hackrf-one-stepup-catia-assembly.png[]

Basic How To '(using kicad StepUp the easiest way)'
---

*(not changing the way you use kicad)*

*1.* just copy the STEP 3d models in the same folder in which there are your 
wrl 3d models and
   use the same name of the wrl model name (e.g. r_0603.wrl => r_0603.step) +
*2.* go to your board folder and copy the script kicad_StepUp.FCMacro and the 
config file ksu-config.cfg
   inside that folder, edit the config file ksu-config.cfg with e.g. notepad 
changing your model prefix to your KISYS3DMOD path +
*3.* export from kicad pcbnew the IDF model of the board +
*4.* run the script from command line or from a bash/batch file +
/freecad  
ksu-config.cfg kicad_StepUp.FCMacro +
'(e.g. freecad mypcb.emn ksu-config.cfg kicad_StepUp.FCMacro)' +
*just watch the script assembly your 3D board with 3D models :)*

How To '(using kicad StepUp the best way)'
--

*(getting the best from STEP models)*

*1.* just copy the STEP 3d models in the same folder in which there are your 
wrl 3d models +
*2.* export the STEP models, scaled 1/2.54 to wrl with the same name of the 
STEP model
(e.g. r_0603.wrl => r_0603.step); in this way your 3D board in kicad pcbnew 
3d-viewer and in FreeCAD workbench will look perfectly aligned +
*3.* go to your board folder and copy the script kicad_StepUp.FCMacro and the 
config file ksu-config.cfg
 

Re: [Kicad-developers] official web page

[easyw]

Hi Wayne,

sorry again ... I don't know why but I cannot attach also images...

ok I'm trying with adoc in plain text
and images with links


I've done a first kicad StepUp starting guide...

it is an asciidoc with some images (to put in images/ dir)

I attached the adoc+images links
image 1
http://www.kicad-pcb.org/download/attachments/589828/hackrf-one-stepup-kicad-3d-viewer.png
image 2
http://www.kicad-pcb.org/download/attachments/589828/hackrf-one-stepup-catia-assembly.png
image 3
https://raw.githubusercontent.com/easyw/kicad-3d-models-in-freecad/master/reference-block-imported.jpg

is it fine or should I do something else to add it to the doc repository?

thank you and sorry again for the 3 mails...
Maurice

On 05/08/2015 14.27, Wayne Stambaugh wrote:

Maurice,

I think Marco is currently on vacation.  The new documentation format is
asciidoc.  You can use git to clone the current documentation at
https://github.com/ciampix/kicad-doc.  Information on how to use
asciidoc can be found at http://www.methods.co.nz/asciidoc/

Wayne

On 8/5/2015 8:23 AM, easyw wrote:

@Marco

what could I do to prepare a small tutorial for the kicad stepup script?
do you accept libre-office file or pdf file?
I'm sorry but I'm new to the doc side :)

thank you
Maurice

On 17/07/2015 15.12, Wayne Stambaugh wrote:

On 7/17/2015 3:36 AM, Mário Luzeiro wrote:

Excellent!

Do you (all) think should be nice to have a small step tutorial /
explanation how can someone reproduce identical results for another
boards?


Yes.  Any help we can provide our users is a good thing.  Something like
this should be added to the user documentation either as part of the
Pcbnew manual or as a stand alone tutorial.  I don't have a preference
one way or another so I'll leave that decision to our documentation
experts.



Mario Luzeiro



Kicad StepUp starter Guide
==
:Author:Maurice
:Email: https://launchpad.net/~easyw
:Author Initials: MEW
:Date:  August 2015
:Revision:  1.1
:website: http://sourceforge.net/projects/kicadstepup/
:docname: readme-kicadStepUp.adoc

kicad StepUp: a new approach to export kicad board and modules in STEP AP214 
(with colors).
With kicad StepUp it is possible to export the 3D board and modules in STEP
for MCAD interchange and create the 3D wrl libraries. +

link:http://sourceforge.net/projects/kicadstepup/[kicadStepUp at sourceforge] +
link:http://bazaar.launchpad.net/~easyw/kicad-stepup/trunk/files/[kicadStepUp 
at lauchpad]

.OverView
**
to run the demo:

in Linux:
change dir to the folder in which you have extracted the demo +
./launch-kicad_StepUp-demo.sh

in windows:
change dir to the folder in which you have extracted the demo +
launch-kicad_StepUp-demo.bat

the demo comes with a kicad project, along with all needed STEP and wrl 
modules, just to be used just out of the box +
(*NB* use the script from inside the dir)

here there is also a link of the script in action... +
link:http://youtu.be/Ukd47VXYzQU[YouTube Kicad StepUp demo video]

*requirements:*
kicad 2015 stable or latest dev release, freecad 0.15
**

Introduction

Kicad StepUp allows the user to modeling the 3D modules starting from FreeCAD
(instead of using Wings3D), creating models in STEP AP214 and rendering the
pcb board and components in native STEP AP214.

Designing in kicad native 3d-viewer will produce a fully aligned STEP version
with the same view of kicad 3d render. +
Now you will have the two words with the same appearance; one can design in 
kicad EDA and transfer the artwork to MCAD (FreeCAD) smoothly

*WYSIWYG from EDA to MCAD*

.kicad StepUp in Kicad 3d-viewer
image::images/hackrf-one-stepup-kicad-3d-viewer.png[]

.kicad StepUp in MCAD Catia
image::images/hackrf-one-stepup-catia-assembly.png[]

Basic How To '(using kicad StepUp the easiest way)'
---

*(not changing the way you use kicad)*

*1.* just copy the STEP 3d models in the same folder in which there are your 
wrl 3d models and
   use the same name of the wrl model name (e.g. r_0603.wrl => r_0603.step) +
*2.* go to your board folder and copy the script kicad_StepUp.FCMacro and the 
config file ksu-config.cfg
   inside that folder, edit the config file ksu-config.cfg with e.g. notepad 
changing your model prefix to your KISYS3DMOD path +
*3.* export from kicad pcbnew the IDF model of the board +
*4.* run the script from command line or from a bash/batch file +
/freecad  
ksu-config.cfg kicad_StepUp.FCMacro +
'(e.g. freecad mypcb.emn ksu-config.cfg kicad_StepUp.FCMacro)' +
*just watch the script assembly your 3D board with 3D models :)*

How To '(using kicad StepUp the best way)'
--

*(getting the best from STEP models)*

*1.* just copy t

[Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi to all,

I have updated the kicad StepUp script (v 0.5.1.3) with all the 
following features:

- added messages on missing emn files
- added messages on missing models
- added path to adapt your KISYS3DMOD
- added blacklist for unwanted modules
- added messages on blacklisted modules
- added display version
- added pcb color attribute
- added bounding box option
- added bounding box white list to leave real model on connector or 
peripheral models

- added auxorigin, base origin, base point placement option
- added vrml models z-rotation angle
- added virtual models option
- added fusion export option (NB it could be heavy in case of a lot of 
small objects)

- added saving in FreeCAD format, export to STEP
https://sourceforge.net/projects/kicadstepup/files/kicad_StepUp_v0.513.zip

and, may be the most important thing, I added a pdf starter guide
kicadStepUp-starter-Guide.pdf
http://sourceforge.net/projects/kicadstepup/files/kicadStepUp-starter-Guide.pdf

And, thank to the work of hyOzd
https://bitbucket.org/hyOzd/freecad-macros/

I managed to create and export parametric models in STEP and VRML (kicad 
compatible)

The repository
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator
now has the scripts to generate:
- all gullwings ICs
- all dip ICs
- chip resistors
- chip capacitors
and more is coming ...
(hyOzd and me are going to team up to build more parametric models)

I uploaded also some STEP models for QFP, SOIC, SSOP, TSSOP and SOT ICs, 
chip Resistors and chip Capacitors

(in sub dirs generated_cap, generated_res, generated_dip, generated_gw)

All the models are STEP AP214 3D models fully colored and automatically 
generated by a script with a parameters file that can be compiled just 
adding mechanical dimensions of the object to be create.


I take attention in the creation process to obtain STEP models without 
geometry problems.

I tested myself the models for geometry problems and they seems fine!
I will be happy if someone with MCAD commercial software could check if 
they are fine too with his sw.


thank you
Maurice

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Cleaner entry of arc angles

[easyw]

Hi Blair,
WxSmith from code blocks seems to be actively developed and up to date...
Maurice


On 13 August 2015 12:23:39 CEST, Blair Bonnett  wrote:
>Hi Wayne et al,
>
>Coming back to this after no reply in four months to the patch I posted
>to
>the wxFormBuilder tracker (see my other email to the list about the
>future
>of wxFB).
>
>
>On 14 May 2015 at 01:03, Wayne Stambaugh  wrote:
>>
>> I was looking at this patch and I like the idea of entering arc
>angles
>> in degrees instead of deci-degrees.  I'm sure most users will
>appreciate
>> it.  However, the wxSpinCtrl hack needs to be replaced by using a
>> wxSpinCtrl when creating the dialog with wxFormBuilder. 
>wxFormBuilder
>> v3.5 supports wxSpinCtrl.
>
>
>Sorry, I didn't explain the issue very clearly.
>
>The wxSpinCtrl widget only handles integer inputs. This would mean that
>either the user still inputs deci-degrees, or the angular resolution is
>limited to whole degrees.
>
>wxWidgets > 2.9 has an extra widget, wxSpinCtrlDouble, which returns a
>double value. This is ideal for inputting degrees.
>
>However, wxFormBuilder doesn't know that wxSpinCtrlDouble exists, and
>therefore we cannot place it directly in a dialog through wxFB.
>
>My patch (which doesn't apply cleanly anymore BTW) proposes using a
>wxSpinCtrl from within wxFB as a placeholder. The actual dialog class,
>which inherits from the base class created by wxFB, replaces this with
>a
>wxSpinCtrlDouble.
>
>
>> This is kind of polishing that I would like
>> to see make it into the stable release.
>
>If you're OK with my proposed method, then I'll go through and change
>all
>existing dialogs which input angles to match, and post a patch
>accordingly.
>
>Blair
>
>
>
>
>___
>Mailing list: https://launchpad.net/~kicad-developers
>Post to : kicad-developers@lists.launchpad.net
>Unsubscribe : https://launchpad.net/~kicad-developers
>More help   : https://help.launchpad.net/ListHelp

-- 
Sent from Mobile___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Lorenzo, have you tried the script? Could you please send me a feed back? 
Thank you
Maurice

On 13 August 2015 08:59:35 CEST, Lorenzo Marcantonio 
 wrote:
>On Thu, 13 Aug 2015 01:37:40 +0200,
>easyw  wrote:
>> All the models are STEP AP214 3D models fully colored and
>automatically
>> generated by a script with a parameters file that can be compiled
>just
>> adding mechanical dimensions of the object to be create.
>
>Nice! I do the same with the footprints (from long before the
>wizards... in perl:P)
>
>The good thing is that finally vendors are providing models for
>'important' stuff, like connectors...
>
>-- 
>Lorenzo Marcantonio
>Logos Srl

-- 
Sent from Mobile___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos,
I don't have this issue (normally I use smd, so mm are a huge gap)

1) could you please send me a sample board to check why you get an 
offset? (it is enough a bare pcb plus 1 or 2 STEP model)

I would like to check if the 3D model is correctly aligned ...
Is your pcb rotated?

I noticed that if the pcb is rotated inside kicad, the exported idf file 
seems to be rotated not exactly around its center... but I'm not sure if 
that is your case...


Please consider that I don't use FC 0.14 because has old routines for 
exporting STEP models, so I could not rely on it, and FC 0.16 is still 
in beta version.. I would suggest to use the latest stable release FC 
0.15 for best result (the only I tested/developed on the script).


Anyway I just tested it on FC 0.16 on win and pcb and models are 
perfectly aligned (I checked importing wrl side by side with the 
generated STEP board + models)


2) I added aux origin and base point to let people decide where place 
its board and components, inside MCAD.
So it is possible to pre-align the PCB and STEP models with the 
mechanical assembly.
I also added the option to fuse all the part in a single block, to 
facilitate the insertion in the MCAD assembly.


3) regarding the model generator, probably you are missing CadQuery 
Module (it has to be added to the Mod dir to FreeCAD)
It is written in README.txt as requirement, but may be I should clarify 
better that the script is based on cadquery freecad module.

https://github.com/jmwright/cadquery-freecad-module/
I checked the generator in FC 0.16 (windows) and it works fine.

Moreover you can download some already generated models at:
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw/qfp
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw/soic
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw/ssop
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw/tssop
These 3D models are already correctly aligned to be used with the script

thank you for your feedback

Maurice

On 13/08/2015 21.04, Marcos Chaparro wrote:

Hi Maurice,
I tried it and it works. I keep forgetting the final "/" in the KISYS3DMOD
path. The only issue I see is that the pcb and the modules have an offset
of a couple of mm. I guess thats why you added auxorigin, base origin, base
point placement option.

I couldn't test the model generator, give me the following error:

marcos@bluestreak:~/electronica/Mrk
industries/tools/kicad/libs/kicad-3d-models-in-freecad/cadquery/FCAD_script_generator$
freecad make_gw_export_fc.py all
FreeCAD 0.14, Libs: 0.14R3702 (Git)
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2011
   #   ###   
   ##  # #   #   #
   # ##     # #   #  #   #
     # # #  # #  #  # #  #   #
   # #      ## # #   #
   # #   ## ## # #   #  ##  ##  ##
   # #       ### # #    ##  ##  ##

Exception while processing file: make_gw_export_fc.py [No module named
Gui.Command]
File format not supported: all

Thats freecad 0.14, but 0.16 from git reports the same error. I'm
using Python 2.7.10

Thanks!



Marcos

On Thu, Aug 13, 2015 at 1:49 PM, Lorenzo Marcantonio <
l.marcanto...@logossrl.com> wrote:


On Thu, 13 Aug 2015 15:27:33 +0200,
easyw  wrote:

Hi Lorenzo, have you tried the script? Could you please send me a feed
back?


Don't have here a machine juicy enough to run freecad since I'm on
vacation; not that the one at works has a serious OpenGL stack:P (intel
hd on a laptop...)

Will try when back to the office

--
Lorenzo Marcantonio
Logos Srl

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] PATCH: restore Meter option to VRML export + other changes

[easyw]

I Cirilo,

I tested the release 6091, and I noticed that there is the new Grid 
reference point, which is a nice feature.


It would be possible to display in the exporting dialog, instead of 'X 
ref: 0, Y ref: 0' the actual base point of the board?


In this way it would be compatible with old IDF export...

I mean if the user wants to place the IDF pcb at X=0, Y=0 he has only to 
put 0 on the X ref and Y ref fields; if not the IDF pcb will be exported 
as in previous versions to the center of the pcb coordinates in kicad.


I know it would be possible to insert the mid value of the board, but it 
should be calculate manually, getting values from the pcb edges of the 
board.
Putting in the dialog fields as default the the center of the pcb 
coordinates in kicad will avoid that operation and do not change the way 
it was exported in previous versions.


I'm asking that because in this way kicad StepUp chain will keep working 
as in previous versions...


I mean I can change myself the value of the pcb IDF position, but this 
would be done discriminating which version of pcbnew is used... before 
6091 or after.


thank you
Maurice

On 13/08/2015 03.10, Cirilo Bernardo wrote:

The attached patch implements the following changes:

1. Restores a "Meter" output option to the VRML export

2. Adds a "Grid Reference Point" to the VRML export; this
allows a user to specify the (X,Y) coordinate which will be
the origin point on the output. Previous behavior was to
guess a point at the center of the board, but a user-specified
value is more useful and was planned though never implemented.

3. Adds a "Grid Reference Point" to the IDF export; this
is similar in purpose to the corresponding VRML export feature.

 From my perspective the addition of the Grid Reference Point
is the last minor improvement to the VRML and IDF export
code. Except for bug fixes I have no intention of making any
further changes to those export codes until after the post-
release 3D refactoring.

Despite the size of the patch, the changes are minor. The bulk
of the patch is due to wxFormBuilder's autogenerated code.

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] PATCH: restore Meter option to VRML export + other changes

[easyw]

Hi Cirilo,

may be a wxradiobox Manual Offset '- enable'  '* disable' would be fine...

thank you again
Maurice

On 14/08/2015 00.01, Cirilo Bernardo wrote:

I could make the unit choice "auto", "mm", "in" where auto = guess at board
center,
but I'm not comfortable with that since "auto" is not a unit and is not
selecting a unit.
Another alternative is to add a button to enable/disable the manual offset
entry but
I have a feeling that will make the GUI look ugly/uglier. I will think
about it more.

- Cirilo


On Fri, Aug 14, 2015 at 7:35 AM, easyw  wrote:


I Cirilo,

I tested the release 6091, and I noticed that there is the new Grid
reference point, which is a nice feature.

It would be possible to display in the exporting dialog, instead of 'X
ref: 0, Y ref: 0' the actual base point of the board?

In this way it would be compatible with old IDF export...

I mean if the user wants to place the IDF pcb at X=0, Y=0 he has only to
put 0 on the X ref and Y ref fields; if not the IDF pcb will be exported as
in previous versions to the center of the pcb coordinates in kicad.

I know it would be possible to insert the mid value of the board, but it
should be calculate manually, getting values from the pcb edges of the
board.
Putting in the dialog fields as default the the center of the pcb
coordinates in kicad will avoid that operation and do not change the way it
was exported in previous versions.

I'm asking that because in this way kicad StepUp chain will keep working
as in previous versions...

I mean I can change myself the value of the pcb IDF position, but this
would be done discriminating which version of pcbnew is used... before 6091
or after.

thank you
Maurice


On 13/08/2015 03.10, Cirilo Bernardo wrote:


The attached patch implements the following changes:

1. Restores a "Meter" output option to the VRML export

2. Adds a "Grid Reference Point" to the VRML export; this
allows a user to specify the (X,Y) coordinate which will be
the origin point on the output. Previous behavior was to
guess a point at the center of the board, but a user-specified
value is more useful and was planned though never implemented.

3. Adds a "Grid Reference Point" to the IDF export; this
is similar in purpose to the corresponding VRML export feature.

  From my perspective the addition of the Grid Reference Point
is the last minor improvement to the VRML and IDF export
code. Except for bug fixes I have no intention of making any
further changes to those export codes until after the post-
release 3D refactoring.

Despite the size of the patch, the changes are minor. The bulk
of the patch is due to wxFormBuilder's autogenerated code.

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp






___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marco ...
could you please send me a frontal image of the board ('Fit Image'), so 
I could replicate a similar edge to check the routine that identify the 
center of pcb?
Or better just the kicad file with only the edge? (No netlist nor 
components, text etc)?


Thank you
Maurice



On 13/08/2015 22.44, Marcos Chaparro wrote:

Hi Maurice,
I can't share those files, but the pcb has a complicated outline that has
many arcs.

Here is a screenshot after alignment. Its probably not the average kind of
pcb.
[image: Inline image 1]

It was displaced some mm along the x axis.

Thanks for the tips, I'll try'em





154132280


Marcos

On Thu, Aug 13, 2015 at 5:01 PM, easyw  wrote:


Hi Marcos,
I don't have this issue (normally I use smd, so mm are a huge gap)

1) could you please send me a sample board to check why you get an offset?
(it is enough a bare pcb plus 1 or 2 STEP model)
I would like to check if the 3D model is correctly aligned ...
Is your pcb rotated?

I noticed that if the pcb is rotated inside kicad, the exported idf file
seems to be rotated not exactly around its center... but I'm not sure if
that is your case...

Please consider that I don't use FC 0.14 because has old routines for
exporting STEP models, so I could not rely on it, and FC 0.16 is still in
beta version.. I would suggest to use the latest stable release FC 0.15 for
best result (the only I tested/developed on the script).

Anyway I just tested it on FC 0.16 on win and pcb and models are perfectly
aligned (I checked importing wrl side by side with the generated STEP board
+ models)

2) I added aux origin and base point to let people decide where place its
board and components, inside MCAD.
So it is possible to pre-align the PCB and STEP models with the mechanical
assembly.
I also added the option to fuse all the part in a single block, to
facilitate the insertion in the MCAD assembly.

3) regarding the model generator, probably you are missing CadQuery Module
(it has to be added to the Mod dir to FreeCAD)
It is written in README.txt as requirement, but may be I should clarify
better that the script is based on cadquery freecad module.
https://github.com/jmwright/cadquery-freecad-module/
I checked the generator in FC 0.16 (windows) and it works fine.

Moreover you can download some already generated models at:

https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw/qfp

https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw/soic

https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw/ssop

https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw/tssop
These 3D models are already correctly aligned to be used with the script

thank you for your feedback

Maurice


On 13/08/2015 21.04, Marcos Chaparro wrote:


Hi Maurice,
I tried it and it works. I keep forgetting the final "/" in the KISYS3DMOD
path. The only issue I see is that the pcb and the modules have an offset
of a couple of mm. I guess thats why you added auxorigin, base origin,
base
point placement option.

I couldn't test the model generator, give me the following error:

marcos@bluestreak:~/electronica/Mrk

industries/tools/kicad/libs/kicad-3d-models-in-freecad/cadquery/FCAD_script_generator$
freecad make_gw_export_fc.py all
FreeCAD 0.14, Libs: 0.14R3702 (Git)
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2011
#   ###   
##  # #   #   #
# ##     # #   #  #   #
  # # #  # #  #  # #  #   #
# #      ## # #   #
# #   ## ## # #   #  ##  ##  ##
# #       ### # #    ##  ##  ##

Exception while processing file: make_gw_export_fc.py [No module named
Gui.Command]
File format not supported: all

Thats freecad 0.14, but 0.16 from git reports the same error. I'm
using Python 2.7.10

Thanks!



Marcos

On Thu, Aug 13, 2015 at 1:49 PM, Lorenzo Marcantonio <
l.marcanto...@logossrl.com> wrote:

On Thu, 13 Aug 2015 15:27:33 +0200,

easyw  wrote:


Hi Lorenzo, have you tried the script? Could you please send me a feed
back?



Don't have here a machine juicy enough to run freecad since I'm on
vacation; not that the one at works has a serious OpenGL stack:P (intel
hd on a laptop...)

Will try when back to the office

--
Lorenzo Marcantonio
Logos Srl

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp








___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-develope

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos, thank you for the board...

1. I had a quick look and I see the position prob...
IDF import in FreeCAD, with this complex edge board, adds a rotation and 
probably the center of rotation is not fine ... I' m going to investigate a bit 
more if this depend on import or export or on my calculations...

2. about the rendering of wrl model SIL7, which version of FC did you use to 
export it?
I tried your wrl in kicad and is not well displayed, then I exported the STEP 
model to wrl in FC 0.15 and the rendering is fine...
I will post the wrl model when I'll be back home.

Thank you again for your feedback

Maurice

On 14 August 2015 01:59:39 CEST, Marcos Chaparro  wrote:
>This should work, see attached a test board
>
>[image: Inline image 1]
>
>The SIL7 model is awful, somehow it looks ok in freecad and really bad
>in
>kicad.
>
>
>
>Marcos
>

-- 
Sent from Mobile

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] PATCH: fix broken workflows due to recent changes in IDF exporter

[easyw]

Hi Cirilo,

I tried the patch in windows 8 64, and I have the following problems:
if I click to Auto Adjust,
1. I got not only X,Y ref and Units disabled but also the other objects 
in the dialog and the check box remains unchecked
(I cannot click on OK, Cancel until I click to kicad main window, not 
the dialog nor the pcbnew)
3. after retrning to the dialog I can click OK, but the export still 
consider X,Y ref values...


I forced in dialog_export_idf.cpp the option to get 
   GetBoard()->ComputeBoundingBox( true );
to simulate the Auto Adjust checked,
then the export returns to the standard old way...

thank you for support
Maurice

On 14/08/2015 10.32, Cirilo Bernardo wrote:

The attached patch adds an option to use a user-specified grid reference
for the IDF export (new behavior) or an automatically calculated reference
point (legacy behavior). This change was made to accommodate requests
for the legacy behavior; apparently my new improved features have broken
people's workflows again. :)

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] PATCH: fix broken workflows due to recent changes in IDF exporter

[easyw]

Hi Cirilo,

the patch works fine in win 8/64

thanks a lot! :)

Maurice

On 15/08/2015 01.48, Cirilo Bernardo wrote:

OK, once more ...
The attached patch (export_idf_20150815_B.patch) adds an option
for the legacy Grid Reference behavior of the IDF exporter. I believe
that this time I am using the wxWidgets events dispatcher as
intended so the code should not only be prettier but it should also
work correctly.

Please test and report success or problems.

I've tested on Debian Linux and it works for me.

- Cirilo


On Fri, Aug 14, 2015 at 10:04 PM, easyw  wrote:


Hi Cirilo,

I tried the patch in windows 8 64, and I have the following problems:
if I click to Auto Adjust,
1. I got not only X,Y ref and Units disabled but also the other objects in
the dialog and the check box remains unchecked
(I cannot click on OK, Cancel until I click to kicad main window, not the
dialog nor the pcbnew)
3. after retrning to the dialog I can click OK, but the export still
consider X,Y ref values...

I forced in dialog_export_idf.cpp the option to get
GetBoard()->ComputeBoundingBox( true );
to simulate the Auto Adjust checked,
then the export returns to the standard old way...

thank you for support
Maurice


On 14/08/2015 10.32, Cirilo Bernardo wrote:


The attached patch adds an option to use a user-specified grid reference
for the IDF export (new behavior) or an automatically calculated reference
point (legacy behavior). This change was made to accommodate requests
for the legacy behavior; apparently my new improved features have broken
people's workflows again. :)

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp






___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D viewer is unusably slow (> 30 minutes) to open this board

[easyw]

It seems related to fill zone rendering in 3d-viewer...
Disabling fill zone in 3d-viewer the board comes up fast...

On 14 August 2015 23:27:46 CEST, Kristian Nielsen  
wrote:
>I discovered that for one of my boards, the 3d viewer has become
>basically
>unusably slow:
>
>  https://github.com/knielsen/pcb_pov3d
>
>I reproduced this on bzr revision 6091 as follows:
>
>  git clone g...@github.com:knielsen/pcb_pov3d.git
>  cd pcb_pov3d/
>  pcbnew pcb_pov3d.kicad_pcb
>
>Choose "View" -> "3D Viewer". This makes KiCAD hang for more than 30
>minutes
>for me (window completely unresponsive) before the 3D view pops up and
>things start working again. This used to take only around 2-3 seconds.
>
>This makes the viewer mostly unusable for this board. The board is of
>medium
>complexity, I wonder if the problem will also show on other boards.
>
>I tracked down the two commits that caused this performance regression:
>
>1.
>http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/5889
>
>---
>Bzr revision 5889
>commit 24170f558816f9661e9e198ecdc40f84772f583b
>Author: Tomasz Włostowski 
>Date:   Mon Jul 6 15:15:48 2015 +0200
>
>Fixes to SHAPE_POLY_SET slitting/fracturing algo, some speed
>optimization.
>---
>
>Before this commit, the viewer comes up in seconds. After this commit,
>it
>takes more than one minute.
>
>2.
>http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/5999
>
>---
>Bzr revision 5999
>commit 63b35f40a7210a8240a609888ac7e28606c44172
>Author: Tomasz Wlostowski 
>Date:   Mon Jul 27 21:45:57 2015 +0200
>
>Removed all dependencies on boost::polygon except for bitmap2component.
>Replaced almost all instances of CPOLYGONS_LIST with SHAPE_POLY_SET.
>---
>
>With this commit, the time to open the 3D viewer for this board goes up
>to
>more than 30 minutes.
>
>The code seems to spend most of its time in this stack trace
>(abbreviated;
>full trace at the end of the mail):
>
>  Thread 1 (Thread 0x7fe966833a80 (LWP 16451)):
>#0  0x7fe9521ed483 in
>ClipperLib::PointInPolygon(ClipperLib::IntPoint const&,
>ClipperLib::OutPt*) () from /kvm/kicad/bin/_pcbnew.kiface
>#1  0x7fe9521ed5f5 in
>ClipperLib::Poly2ContainsPoly1(ClipperLib::OutPt*, ClipperLib::OutPt*)
>() from /kvm/kicad/bin/_pcbnew.kiface
>#2  0x7fe9521f475e in ClipperLib::Clipper::JoinCommonEdges() ()
>from /kvm/kicad/bin/_pcbnew.kiface
>#3  0x7fe9521f92ea in ClipperLib::Clipper::ExecuteInternal() ()
>from /kvm/kicad/bin/_pcbnew.kiface
>#4  0x7fe9521f31ce in
>ClipperLib::Clipper::Execute(ClipperLib::ClipType,
>ClipperLib::PolyTree&, ClipperLib::PolyFillType,
>ClipperLib::PolyFillType) [clone .part.287] () from
>/kvm/kicad/bin/_pcbnew.kiface
>#5  0x7fe9521a3649 in
>SHAPE_POLY_SET::booleanOp(ClipperLib::ClipType, SHAPE_POLY_SET const&)
>() from /kvm/kicad/bin/_pcbnew.kiface
>#6  0x7fe951ed68ec in EDA_3D_CANVAS::buildBoard3DView(unsigned int,
>unsigned int, REPORTER*, REPORTER*) () from
>/kvm/kicad/bin/_pcbnew.kiface
>#7  0x7fe951ed3ba6 in EDA_3D_CANVAS::CreateDrawGL_List(REPORTER*,
>REPORTER*) () from /kvm/kicad/bin/_pcbnew.kiface
>#8  0x7fe951ed4823 in EDA_3D_CANVAS::Redraw() () from
>/kvm/kicad/bin/_pcbnew.kiface
>
>It seems this code is looping over very large vectors. Eg. I saw
>m_Joins.size()==14207 in the outer loop of Clipper::JoinCommonEdges()
>and
>m_PolyOuts.size()==9756 in the inner loop (and then a third nested loop
>within that in Poly2ContainsPoly1()). I wonder if something in my board
>causes excessive long lists to be generated? Or if it is hitting some
>case
>that causes an O(n**3) complexity from three nested loops?
>
>I can take a closer look at the code or run some profiling, but I
>wanted to
>provide this info now, in case someone who knows the code has some
>idea. I
>saw there was already some discussion around these commits and
>elimiation of
>boost::polygon. Hopefully some way can be found to improve the
>performance
>of the new code to something a bit closer to what it was before.
>
>I suppose if KiCAD can get stuck for many minutes opening the 3D
>viewer,
>most users would think it has gotten completely stuck (I know I did, at
>first), which is not very good, obviously.
>
>Hope this helps,
>
> - Kristian.
>
>
>Full GDB stack trace of where the code seemed to be spending its time,
>for
>completeness:
>
>Thread 1 (Thread 0x7fe966833a80 (LWP 16451)):
>#0  0x7fe9521ed483 in
>ClipperLib::PointInPolygon(ClipperLib::IntPoint const&,
>ClipperLib::OutPt*) () from /kvm/kicad/bin/_pcbnew.kiface
>#1  0x7fe9521ed5f5 in
>ClipperLib::Poly2ContainsPoly1(ClipperLib::OutPt*, ClipperLib::OutPt*)
>() from /kvm/kicad/bin/_pcbnew.kiface
>#2  0x7fe9521f475e in ClipperLib::Clipper::JoinCommonEdges() ()
>fro

Re: [Kicad-developers] Helping out with Kicad

[easyw]

Hi Marco,

I'm trying to prepare some doc for kicad StepUp script using asciidoc, 
but I cannot create a pdf conserving clickable hyperlinks...


Here the query I posted (without a reply) at asciidoctor.org

http://discuss.asciidoctor.org/conserving-clickable-hyperlinks-on-pdf-tc3669.html

with all explanations about the method I tried...

Could you please give me some help?

thank you
Maurice


On 15/08/2015 18.57, Marco Ciampa wrote:

On Fri, Aug 14, 2015 at 08:18:15AM -0400, Lance Doiron wrote:

Kicad Team,

I am an EE by training and have a passion for open source anything. I am
currently designing an open source motor drive for teaching the DIY hacker
crowd about how PID loops, motor control etc works. I see that Kicad has
potential, and also that Kicad has very few people working on it to make it
better.

I would like to help fix Kicad bugs, which is something only a handful of
crazy nut jobs have said before. I have programmed in Java and python
before, and dabbled in C++. I am not totally inept when it comes to
algorithmic coding, however I am not well versed in how OS programs run or
interact with the OS. If somebody who is working on Kicad is willing to
trade a little bit of hand holding for another person on board to help make
Kicad the next Ubuntu for PCB design, I am willing to help.


[...]

Welcome aboard Lance!
Seeing the premises you can start with this bug:

https://bugs.launchpad.net/kicad/+bug/1391533

it does not affect the GUI but just the search algorithm that is wrong
and it should be not so difficult to fix (I hope).

regards & good work!

--


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| GNU/Linux User  #78271 |
| FSFE fellow   #364 |
++


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] PATCH: fix broken workflows due to recent changes in IDF exporter

[easyw]

Hi to all,

would it be possible to commit Cirilo's patch?

thank you
Maurice

On 15/08/2015 01.48, Cirilo Bernardo wrote:

OK, once more ...
The attached patch (export_idf_20150815_B.patch) adds an option
for the legacy Grid Reference behavior of the IDF exporter. I believe
that this time I am using the wxWidgets events dispatcher as
intended so the code should not only be prettier but it should also
work correctly.

Please test and report success or problems.

I've tested on Debian Linux and it works for me.

- Cirilo


On Fri, Aug 14, 2015 at 10:04 PM, easyw  wrote:


Hi Cirilo,

I tried the patch in windows 8 64, and I have the following problems:
if I click to Auto Adjust,
1. I got not only X,Y ref and Units disabled but also the other objects in
the dialog and the check box remains unchecked
(I cannot click on OK, Cancel until I click to kicad main window, not the
dialog nor the pcbnew)
3. after retrning to the dialog I can click OK, but the export still
consider X,Y ref values...

I forced in dialog_export_idf.cpp the option to get
GetBoard()->ComputeBoundingBox( true );
to simulate the Auto Adjust checked,
then the export returns to the standard old way...

thank you for support
Maurice


On 14/08/2015 10.32, Cirilo Bernardo wrote:


The attached patch adds an option to use a user-specified grid reference
for the IDF export (new behavior) or an automatically calculated reference
point (legacy behavior). This change was made to accommodate requests
for the legacy behavior; apparently my new improved features have broken
people's workflows again. :)

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp






___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] PATCH: fix broken workflows due to recent changes in IDF exporter

[easyw]

Hi Cirilo,

I managed to take care also of the pcb position in kicad StepUp scrip
I added a flag, so the user can decide if use the old automatically 
calculated reference point (legacy behavior), or the new Xref,Yref one.


I'm going to add some notes on the starting guide and in the script user 
gui, to let users discriminate the right choice. It would affect only 
who has already tested the script ...


You are right, rarely one gets any feedback from users, until they get 
troubles :)


Thank you again for your effort and the IDF export

Maurice

On 18/08/2015 01.15, Wayne Stambaugh wrote:

Cirilo, is this patch ready to be committed.  I have not had time to
test it.

Cheers,

Wayne

On 8/14/2015 7:48 PM, Cirilo Bernardo wrote:

OK, once more ...
The attached patch (export_idf_20150815_B.patch) adds an option
for the legacy Grid Reference behavior of the IDF exporter. I believe
that this time I am using the wxWidgets events dispatcher as
intended so the code should not only be prettier but it should also
work correctly.

Please test and report success or problems.

I've tested on Debian Linux and it works for me.

- Cirilo


On Fri, Aug 14, 2015 at 10:04 PM, easyw mailto:ea...@katamail.com>> wrote:

 Hi Cirilo,

 I tried the patch in windows 8 64, and I have the following problems:
 if I click to Auto Adjust,
 1. I got not only X,Y ref and Units disabled but also the other
 objects in the dialog and the check box remains unchecked
 (I cannot click on OK, Cancel until I click to kicad main window,
 not the dialog nor the pcbnew)
 3. after retrning to the dialog I can click OK, but the export still
 consider X,Y ref values...

 I forced in dialog_export_idf.cpp the option to get
GetBoard()->ComputeBoundingBox( true );
 to simulate the Auto Adjust checked,
 then the export returns to the standard old way...

 thank you for support
 Maurice


 On 14/08/2015 10.32, Cirilo Bernardo wrote:

 The attached patch adds an option to use a user-specified grid
 reference
 for the IDF export (new behavior) or an automatically calculated
 reference
 point (legacy behavior). This change was made to accommodate
 requests
 for the legacy behavior; apparently my new improved features
 have broken
 people's workflows again. :)

 - Cirilo




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos,

it took me a bit but I managed to align the board.
Now the script can manage also circular board, board with arcs and pcb 
rotated inside pcbnew.


I also made an update for the board position for the new IDF exporting grid.
http://sourceforge.net/projects/kicadstepup/files/kicad_StepUp_v0.519.zip/download
NB this version will put the board at the right position only if IDF is 
exported to Xref=0;Yref=0 (pcbnew version > 6091)


I added a starter guide (adoc and pdf) both for kicad StepUp
http://sourceforge.net/projects/kicadstepup/files/kicadStepUp-starter-Guide.pdf/download
and for FreeCAD script generator.
http://sourceforge.net/projects/kicadstepup/files/FC-script-generator-starter-Guide.pdf/download

I patched also the scripting to generate 3D models in STEP, to be 
execute correctly also in linux (cadquery freecad module has been 
updated too).

(I tested the scripts in ubuntu but it should work also in debian)

Please have a look :)

Maurice


On 14/08/2015 16.02, Marcos Chaparro wrote:

Thanks Maurice,
the board edge is actually a footprint, and it was rotated 180° in
kicad_pcb file, I don't know if that matters.

About 2), you're right, freecad 0.14 messed up the vrml export. I tried
with 0.16 and it looks perfect. I'm on a debian box, the stable freecad
version for us is 0.14, in order to get 0.15 I had to compile it, and since
it was the same effort as getting the bleeding edge I compiled 0.16.

I keep forgetting that gmail's inline images are not shown here, the
screenshot in my last mail was this one (thanks Mario)
www.paltatech.com/files/offset.png

Thanks



Marcos

On Fri, Aug 14, 2015 at 5:46 AM, easyw  wrote:


Hi Marcos, thank you for the board...

1. I had a quick look and I see the position prob...
IDF import in FreeCAD, with this complex edge board, adds a rotation and
probably the center of rotation is not fine ... I' m going to investigate a
bit more if this depend on import or export or on my calculations...

2. about the rendering of wrl model SIL7, which version of FC did you use
to export it?
I tried your wrl in kicad and is not well displayed, then I exported the
STEP model to wrl in FC 0.15 and the rendering is fine...
I will post the wrl model when I'll be back home.

Thank you again for your feedback

Maurice

On 14 August 2015 01:59:39 CEST, Marcos Chaparro 
wrote:

This should work, see attached a test board

[image: Inline image 1]

The SIL7 model is awful, somehow it looks ok in freecad and really bad
in
kicad.



Marcos



--
Sent from Mobile





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marco,

1) could you please send me also the board with only these 3 modules 
(usb, qfn, pogo_pin)? (no net, just edge and 3 modules would be fine)

it would be easier check the probs

2) fusion with color is possible in FC 015 and 016 ... I'm going to send 
the X2QFN-12 fused with color asap ... wich command do you use?

Part, Make a union of several parts?

3) to align the objects I've done a small FC macro... it is not complete 
to be deployed with the stepup script, but is usable and makes the 
alignment easy...

I will send it asap

4) could you please send me also a copy of the trouble pcb edge (no net 
no modules), to check if the problem is in kicad exporting to IDF or in 
importing IDF from FC


thank you
Maurice

On 19/08/2015 17.13, Marcos Chaparro wrote:

About the USB connector, don't follow the original part from the
manufacturer, it took me a while to align it.

Here is the step and vrml of that connector. Its the same manufacturer
step, but aligned.
http://www.paltatech.com/files/USB-C.zip
and the connector footprint:
http://www.paltatech.com/files/USB-C-DX07S.kicad_mod

The IDF export is not the problem, trying with a simpler outline
generates the pcb okay but the parts are still rotated.

Regards


Marcos

On Wed, Aug 19, 2015 at 11:44 AM, Marcos Chaparro mailto:nitrous...@gmail.com>> wrote:

Hi Maurice,
I just compiled the latest kicad version and the script says
IDF board has to be exported to Xref=0; Yref=0
pcbnew version >=6091
IDF board has NOT to be exported to real placement
pcbnew version < 6091

Anyway, the board is perfectly aligned now, thanks!

I'm using kicad Version: (2015-08-18 BZR 6103)-product release build
and freecad 0.16

I do have a question, the tutorial says "assure that your STEP
module is fused to just one solid object". I see it failing with
multi part obejcts, but I don't know how to fuse a part properly in
freecad.

A boolean operation between parts (union) creates a "fusion" object
that loses color information.
Going through "make compound" in the part workbench seems to be the
right way to do it, but the script is still not happy with the
generated step file and in freecad you can see its not a single object.

See attached an example of a part that I can't fuse together
(X2QFN). I think there are no coplanar faces in the part.


Also, pogo_pin.step looks fine to me in freecad, but when it is
added to a board using the script it gets rotated. Its also attached
http://www.paltatech.com/files/pogo_pin_in_freecad.png
http://www.paltatech.com/files/USB-C_3dviewer.png
http://www.paltatech.com/files/USB-C_stepup.png

The usb connector that is also rotated is here

http://www.jae.com/z-en/product_en.cfm?l_code=EN&series_code=DX07&product_number=DX07S024JJ2R1300

I'm also having throubles exporting the pcb to IDFv3 of this
particular board, maybe this is related to these rotation issues. I
should ask cirilo later about this.

Thanks





Marcos

On Tue, Aug 18, 2015 at 7:17 PM, easyw mailto:ea...@katamail.com>> wrote:

Hi Marcos,

it took me a bit but I managed to align the board.
Now the script can manage also circular board, board with arcs
and pcb rotated inside pcbnew.

I also made an update for the board position for the new IDF
exporting grid.

http://sourceforge.net/projects/kicadstepup/files/kicad_StepUp_v0.519.zip/download
NB this version will put the board at the right position only if
IDF is exported to Xref=0;Yref=0 (pcbnew version > 6091)

I added a starter guide (adoc and pdf) both for kicad StepUp

http://sourceforge.net/projects/kicadstepup/files/kicadStepUp-starter-Guide.pdf/download
and for FreeCAD script generator.

http://sourceforge.net/projects/kicadstepup/files/FC-script-generator-starter-Guide.pdf/download

I patched also the scripting to generate 3D models in STEP, to
be execute correctly also in linux (cadquery freecad module has
been updated too).
(I tested the scripts in ubuntu but it should work also in debian)

Please have a look :)

Maurice



On 14/08/2015 16.02, Marcos Chaparro wrote:

Thanks Maurice,
the board edge is actually a footprint, and it was rotated
180° in
kicad_pcb file, I don't know if that matters.

About 2), you're right, freecad 0.14 messed up the vrml
export. I tried
with 0.16 and it looks perfect. I'm on a debian box, the
stable freecad
version for us is 0.14, in order to get 0.15 I had to
compile it, and since
it was the same effort as getting the bleeding edge I
   

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos and Cirilo,

1) DXF can be fully supported only if the DXF is in R12 version
With R12 version and the recent patch of Marco Hess (already committed), 
it is possible to import also ellipses


As Cirilo pointed out, opening the file with LibreOffice and then saving 
it (better in R12 version) will solve the problem.


I suggested a patch to add to the DXF import menu the info:
 (R12 fully supported, units mm)
so users will have this info immediately...
[ documentation is not always read by users :) ]
https://lists.launchpad.net/kicad-developers/msg18735.html

but the patch was not committed

Anyway about the reworking of Marco's board...
DXF is fine now...

2) STEP models orientation depends only of the use of FreeCAD 0.16 
develop version (which not reliable nor suggested also from FreeCAD 
developers)

If you open your models in FC 015 and save them everything will be fine.

3) fusion with colors works also in FC016...
I'm going to send you a screenshot of what I do to fuse with colors...

I'm almost done ... I will send you the models correctly oriented and 
fused in single part...


I will strongly suggest you to build a copy of FC015, so to avoid errors 
or mechanical probs.


keep in touch
Maurice


On 19/08/2015 18.52, Marcos Chaparro wrote:

Hi Maurice,




1) could you please send me also the board with only these 3 modules (usb,
qfn, pogo_pin)? (no net, just edge and 3 modules would be fine)
it would be easier check the probs



You'll find the design files here
https://github.com/paltatech/std-mainboard

In my computer the 3D files are in
/usr/local/share/kicad/modules/packages3d/walter/step/


2) fusion with color is possible in FC 015 and 016 ... I'm going to send

the X2QFN-12 fused with color asap ... wich command do you use?
Part, Make a union of several parts?



I'm using part->make compound (in part workbench)
or part->boolean->union (also in part workbench)




4) could you please send me also a copy of the trouble pcb edge (no net no
modules), to check if the problem is in kicad exporting to IDF or in
importing IDF from FC



Also included in the github repo. The outline was imported from a DXF file
generated with freecad. The 3Dviewer displays it correctly, but I think the
error is in the DXF importer because "Global spread and place" -> "spread
out footprints not already on board" didn't detect the outline, so it
probably has a disconnected segment somewhere and 3DViewer is flexible
enough to display it despite the errors

Thanks






thank you
Maurice

On 19/08/2015 17.13, Marcos Chaparro wrote:


About the USB connector, don't follow the original part from the
manufacturer, it took me a while to align it.

Here is the step and vrml of that connector. Its the same manufacturer
step, but aligned.
http://www.paltatech.com/files/USB-C.zip
and the connector footprint:
http://www.paltatech.com/files/USB-C-DX07S.kicad_mod

The IDF export is not the problem, trying with a simpler outline
generates the pcb okay but the parts are still rotated.

Regards


Marcos

On Wed, Aug 19, 2015 at 11:44 AM, Marcos Chaparro mailto:nitrous...@gmail.com>> wrote:

 Hi Maurice,
 I just compiled the latest kicad version and the script says
 IDF board has to be exported to Xref=0; Yref=0
 pcbnew version >=6091
 IDF board has NOT to be exported to real placement
 pcbnew version < 6091

 Anyway, the board is perfectly aligned now, thanks!

 I'm using kicad Version: (2015-08-18 BZR 6103)-product release build
 and freecad 0.16

 I do have a question, the tutorial says "assure that your STEP
 module is fused to just one solid object". I see it failing with
 multi part obejcts, but I don't know how to fuse a part properly in
 freecad.

 A boolean operation between parts (union) creates a "fusion" object
 that loses color information.
 Going through "make compound" in the part workbench seems to be the
 right way to do it, but the script is still not happy with the
 generated step file and in freecad you can see its not a single
object.

 See attached an example of a part that I can't fuse together
 (X2QFN). I think there are no coplanar faces in the part.


 Also, pogo_pin.step looks fine to me in freecad, but when it is
 added to a board using the script it gets rotated. Its also attached
 http://www.paltatech.com/files/pogo_pin_in_freecad.png
 http://www.paltatech.com/files/USB-C_3dviewer.png
 http://www.paltatech.com/files/USB-C_stepup.png

 The usb connector that is also rotated is here

http://www.jae.com/z-en/product_en.cfm?l_code=EN&series_code=DX07&product_number=DX07S024JJ2R1300

 I'm also having throubles exporting the pcb to IDFv3 of this
 particular board, maybe this is related to these rotation issues. I
 should ask cirilo later about this.

 Thanks







___
Mailing list: https://launchpad.net/~kicad-developers
Post to : ki

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marco,
attached design-mod2.zzp (renamed to attach the file containing scripts, 
... just rename it to .zip)

the file has:
1) the right DXF and the corresponding IDF file
2) the XQFN module fused with colors
3) the USB-C and pogo_pin correctly oriented
4) a FC file with a reference block to help in orienting modules
USB-C-with-reference-block.fcstd
(just import the block in the file you are working with and you will
 have the right point to align the model)
5) some bash files to:
- launch-kicad_StepUp-dxf-marco.sh
- launch-kicad_StepUp-dxf-marco-config.sh
  this file uses the ksu-config file to get all the settings
- launch-kicad_StepUp-dxf-marco-config-fusing.sh
  this file will lauch kicad_StepUp script with a config that will
  generate a fused with colors board+models
- launch-kicad-edge-dxf-marco-project.sh
  this file will launch the kicad pro file to enables path to
  correctly display vrml models
  (I changed path to './shapes' for the edge-dxf-marco board)
6) I see you have changed the module prefix inside kicad_StepUp file...
the right place is the ksu-config.cfg file
(it let you set more features)

to solve orientation prob I just reopened the STEP models you send me in 
FC015 and saved them... orientation became fine... there should be 
something wrong in FC016


Please let me know if you get the file and if everything now is fine.

Thank you
Maurice

On 19/08/2015 23.37, Marcos Chaparro wrote:

Thanks Cirilo,
opening the dxf generated by FreeCAD with LibreCAD and then exporting to
DXF from LibreCAD worked.

This screenshot is the result of the StepUp script:
http://www.paltatech.com/files/DXF_workaround.png

Maurice, I managed to fuse the objects using part->union. After the fusion
the colors get messed up, but I discovered that you can edit each face
color to fix them with right click->set colors, so I'm doing it that way
for now.

Now I only have to discover why the connector and pins are rotated.

Regards








Marcos

On Wed, Aug 19, 2015 at 5:57 PM, Cirilo Bernardo 
wrote:





Hi Marcos,

  If there is a problem with the DXF import which leaves an
unconnected segment then the IDF exporter will not be
able to create a board since it will not know how to repair
the bad outline.  If you can use LibreCAD to create the
outline and use only circular arcs and line segments the
results may be better. There have been a few discussions
recently about FreeCAD producing DXF files which do not
import well in KiCad.

- Cirilo





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Helping out with Kicad

[easyw]

Hi Nick and all,
the new static site is good...
I noticed that in 3d-viewer screenshot the are no 3D-modules ... I think 
it would be nice to add a screenshot with 3D shapes, to give an idea of 
the 3D realistic mode.


In the site I also miss a section that it was in the classic site: 
'External Tools'

and particularly
'Maurice's kicadStepUp, which allows exporting kicad 3D board and 
components to STEP AP214' :)

and the screenshots
http://www.kicad-pcb.org/display/KICAD/KiCad+EDA+Software+Suite?preview=/589828/16973826/hackrf-one-stepup-kicad-3d-viewer.png
http://www.kicad-pcb.org/display/KICAD/KiCad+EDA+Software+Suite?preview=/589828/16973825/hackrf-one-stepup-catia-assembly.png

do you think this section will be added to the new site?

Maurice


On 20/08/2015 17.34, Nick Østergaard wrote:

http://test.kicad-pcb.org
Den 20/08/2015 15.43 skrev "Wayne Stambaugh" :


Is there a link to new static html kicad website?  I would like to take
a look at it.

Cheers,

Wayne

On 8/20/2015 9:00 AM, Miguel Angel Ajo wrote:

We can gather statistics from the logs, we used to do it... I need to
remember
where.

If you move to google analytics, then, EU laws force you to send a cookie
notice to the user at least once before calling google analytics api,
which will
track via cookies all around any sites the user visit which also have
analytics...

BTW, I wanted to say: awesome work with the static site, it's looking
impressive.

And, it's served by nginx, yes. It has a frontend with cherokee as a
reverse proxy
just for IP sharing purposes, but I'd eventually remove that to make
administration
easier.

Mark Roszko wrote:

Good news we are generating the new site as static html. Shouldn't
have any load issues then assuming you run it under nginx or lighttpd.
   ^^


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] kicad footprint plugins wizard in windows

[easyw]

Hi,

I don't know where to place the python plugins file (e.g. qfp_wizard.py) 
in windows...


in linux the right place is ~/.kicad_plugins
but I don't know the right place in windows...
I tried with the Nick pre-built windows files
http://www2.futureware.at/~nickoe/kicad-product-r6097.b384c94-x86_64.exe
putting the script in
C:\KiCad-test\lib\kicad\plugins
but it didn't worked

I can't find any help in docs...

thanks
Maurice

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad footprint plugins wizard in windows

[easyw]

Hi Nick,

I found that the right path in windows is:
C:\KiCad\bin\scripting\plugins
where C:\KiCad is the main installation dir

I also found that in windows the script has a problem
When I make a qfp footprint (e.g. QFP 64) I get this error:
one of invalid character 'tab space'
because of the footprint name in library with a space 'QFP 64'
This error comes out when I try to associate a wrl models to the 
footprint I created.

This error has the same behavior also for BGA and DIP footprints

Thanks for the script... it saves a lot of time! :)
Maurice


On 22/08/2015 14.34, easyw wrote:

Hi,

I don't know where to place the python plugins file (e.g. qfp_wizard.py)
in windows...

in linux the right place is ~/.kicad_plugins
but I don't know the right place in windows...
I tried with the Nick pre-built windows files
http://www2.futureware.at/~nickoe/kicad-product-r6097.b384c94-x86_64.exe
putting the script in
C:\KiCad-test\lib\kicad\plugins
but it didn't worked

I can't find any help in docs...

thanks
Maurice

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos,

could you please confirm me that the only issues you get where related 
to import a non compatible DXF file and using FreeCAD 016 for generating 
STEP files?


I'm going to update the kicad StepUp starter guide and I would like to 
add this feedback results.


Thank you
Maurice

On 20/08/2015 03.33, Marcos Chaparro wrote:

Yup, FreeCAD 0.16 was the problem, I got so used to kicad's bleeding edge
being so stable that I expected too much from FreeCad latest build.
Compiling and re-saving everything solved the rotation issue.

http://www.paltatech.com/files/StepUp_mint.png

Tomorrow I'll try to send more feedback

Thanks Maurice



Marcos

On Wed, Aug 19, 2015 at 8:33 PM, easyw  wrote:


Hi Marco,
attached design-mod2.zzp (renamed to attach the file containing scripts,
... just rename it to .zip)
the file has:
1) the right DXF and the corresponding IDF file
2) the XQFN module fused with colors
3) the USB-C and pogo_pin correctly oriented
4) a FC file with a reference block to help in orienting modules
 USB-C-with-reference-block.fcstd
 (just import the block in the file you are working with and you will
  have the right point to align the model)
5) some bash files to:
 - launch-kicad_StepUp-dxf-marco.sh
 - launch-kicad_StepUp-dxf-marco-config.sh
   this file uses the ksu-config file to get all the settings
 - launch-kicad_StepUp-dxf-marco-config-fusing.sh
   this file will lauch kicad_StepUp script with a config that will
   generate a fused with colors board+models
 - launch-kicad-edge-dxf-marco-project.sh
   this file will launch the kicad pro file to enables path to
   correctly display vrml models
   (I changed path to './shapes' for the edge-dxf-marco board)
6) I see you have changed the module prefix inside kicad_StepUp file...
 the right place is the ksu-config.cfg file
 (it let you set more features)

to solve orientation prob I just reopened the STEP models you send me in
FC015 and saved them... orientation became fine... there should be
something wrong in FC016

Please let me know if you get the file and if everything now is fine.

Thank you
Maurice

On 19/08/2015 23.37, Marcos Chaparro wrote:


Thanks Cirilo,
opening the dxf generated by FreeCAD with LibreCAD and then exporting to
DXF from LibreCAD worked.

This screenshot is the result of the StepUp script:
http://www.paltatech.com/files/DXF_workaround.png

Maurice, I managed to fuse the objects using part->union. After the fusion
the colors get messed up, but I discovered that you can edit each face
color to fix them with right click->set colors, so I'm doing it that way
for now.

Now I only have to discover why the connector and pins are rotated.

Regards








Marcos

On Wed, Aug 19, 2015 at 5:57 PM, Cirilo Bernardo <
cirilo.berna...@gmail.com>
wrote:





Hi Marcos,

   If there is a problem with the DXF import which leaves an
unconnected segment then the IDF exporter will not be
able to create a board since it will not know how to repair
the bad outline.  If you can use LibreCAD to create the
outline and use only circular arcs and line segments the
results may be better. There have been a few discussions
recently about FreeCAD producing DXF files which do not
import well in KiCad.

- Cirilo










___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad footprint plugins wizard in windows

[easyw]

Hi Nick,
I'm talking about the New Footprint wizard ...

please consider also to add the scripts to the installer...
so it will be already available for all users, without any action to do...

the scripts afflicted by this minor bug are:
qfp_wizard.py
sdip_wizard.py
bga_wizard.py

and the fix is:
qfp_wizard.py (line 50):
def GetValue(self):
-return "QFP %d" % self.parameters["Pads"]["*n"]
+return "QFP-%d" % self.parameters["Pads"]["*n"]
(eliminating the space before %d e.g. with a minus character)

the same for BGA and DIP
bga_wizard.py (line 59):
-return "BGA %d" % pins
+return "BGA-%d" % pins

sdip_wizard.py (lines 131, 180):
name = "xIP"

-return "%s %d" % (name, self.parameters["Pads"]["*n"])
+return "%s-%d" % (name, self.parameters["Pads"]["*n"])

def GetValue(self):
-return "%s %d" % ("SOIC", self.parameters["Pads"]["*n"])
+   return "%s-%d" % ("SOIC", self.parameters["Pads"]["*n"])

thank you
Maurice

On 22/08/2015 23.32, Nick Østergaard wrote:

Ok, thank you for the information. Consider adding the path to the
docs if we actually describe the python console. I don't even rember
if we do.

But which script are you talking about? Do you have a fix for it?

2015-08-22 22:21 GMT+02:00 easyw :

Hi Nick,

I found that the right path in windows is:
C:\KiCad\bin\scripting\plugins
where C:\KiCad is the main installation dir

I also found that in windows the script has a problem
When I make a qfp footprint (e.g. QFP 64) I get this error:
one of invalid character 'tab space'
because of the footprint name in library with a space 'QFP 64'
This error comes out when I try to associate a wrl models to the footprint I
created.
This error has the same behavior also for BGA and DIP footprints

Thanks for the script... it saves a lot of time! :)
Maurice



On 22/08/2015 14.34, easyw wrote:


Hi,

I don't know where to place the python plugins file (e.g. qfp_wizard.py)
in windows...

in linux the right place is ~/.kicad_plugins
but I don't know the right place in windows...
I tried with the Nick pre-built windows files
http://www2.futureware.at/~nickoe/kicad-product-r6097.b384c94-x86_64.exe
putting the script in
C:\KiCad-test\lib\kicad\plugins
but it didn't worked

I can't find any help in docs...

thanks
Maurice

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad footprint plugins wizard in windows

[easyw]

Hi JP,

The changes are fully working.
thanks for committing.

PS
I see you added a bar code generator to fp wizard...
Do you think it would possible to add also an option for exposed pad in 
qfp/qfn footprint?

thank you
Maurice

On 23/08/2015 14.46, jp charras wrote:

Le 23/08/2015 00:03, easyw a écrit :

Hi Nick,
I'm talking about the New Footprint wizard ...

please consider also to add the scripts to the installer...
so it will be already available for all users, without any action to do...

the scripts afflicted by this minor bug are:
qfp_wizard.py
sdip_wizard.py
bga_wizard.py

and the fix is:
qfp_wizard.py (line 50):
 def GetValue(self):
-return "QFP %d" % self.parameters["Pads"]["*n"]
+return "QFP-%d" % self.parameters["Pads"]["*n"]
(eliminating the space before %d e.g. with a minus character)

the same for BGA and DIP
bga_wizard.py (line 59):
-return "BGA %d" % pins
+return "BGA-%d" % pins

sdip_wizard.py (lines 131, 180):
 name = "xIP"

-return "%s %d" % (name, self.parameters["Pads"]["*n"])
+return "%s-%d" % (name, self.parameters["Pads"]["*n"])

 def GetValue(self):
-return "%s %d" % ("SOIC", self.parameters["Pads"]["*n"])
+return "%s-%d" % ("SOIC", self.parameters["Pads"]["*n"])

thank you
Maurice


I committed yours changes. Please test the rev 6114

Thanks.




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos,
thank you for the feedback.
The screenshot is very nice!

1) For fusion object, it is strange, I don't have prob in conserving 
colors neither in FC015, nor in FC016 both in win and linux...

but I'm on ubuntu and I used the ubu repos

2) To scale a part there is already a small macro in the demo project;
the file name is kicad_StepUp_vrml_export.FCMacro
and there is also a bash file
launch-kicad_StepUp-step-to-vrml-example.sh

The script has to be cleaned up a bit...
anyway it works... NB after exporting the VRML file, do not save the FC 
STEP file or you'll get it scaled too :)


3) I'm going to complete a new macro named 'move_rotate_scale' (which is 
not included at the moment), so it would be easier to manage 
manufacturer models to align and generate vrml scaled models.

When it si ready I will let you know

4) Please also have a look at:
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator
there are script to generate parametric STEP and scaled VRML for SOIC, 
DIP, QFP, Resistor chips and Capacitor chips
there are some configuration files in which you only need to add 
dimensions as in the datasheet, then the model 3D will be generated.

There a re also some already generated examples at:
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_cap
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_dip
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_res

and a mini starter guide
https://github.com/easyw/kicad-3d-models-in-freecad/raw/master/cadquery/FCAD_script_generator/FC-script-generator-starter-Guide.pdf
I've added a colored pinmark and some more models.

Could you please give me a feedback also on those scripts/models.
Maurice


On 23/08/2015 17.14, Marcos Chaparro wrote:

Hi Maurice,
the issues were related to using freecad 0.16 and non compatible DXF files
(Freecad 0.15 and 0.16 produced an incompatible dxf file that was fixed
re-exporting it using librecad in R14 format, later you told me that R12 is
better but I didn't try.

The final woraround for fusing parts and maintaing the color correctly was
to make the top level fused part 100% transparent It seems that when I
export the fused part freecad exports all the parts inside the fusion too,
and the object surfaces have all 2 faces, one from the fused and one from
the original, and the colors get messed up. Forcing the fused part
transparent it still exports duplicated faces but since one is transparent
it doesn't bother me. Maybe it a dependency issue when compiling FC15 and
this doesn't happen in a stable FC installation.

BTW, now it is *much* easier to import 3D parts from the manufacturers 3D
models
http://www.paltatech.com/files/STEP_import.png

I'll share the footprints when I get some free time, have to organize them
and make a repo for it. Oh and I have to learn to scale the parts by
1/2.54. How do you scale them? it seems MCAD don't like to just shrink a
part.
There is an Draft.scale() function call in your script, does it work with
raw STEP files?

Regards






Marcos

On Sat, Aug 22, 2015 at 5:26 PM, easyw  wrote:




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos,

I had a prob in syncing github files...
now they should be synchronized.
https://github.com/easyw/kicad-3d-models-in-freecad/archive/master.zip

You need also to download the latest version of CadQuery Module
https://github.com/jmwright/cadquery-freecad-module/archive/v0.2.0.zip

Just delete the old CadQuery Mod in FreeCAD and use the new one.
(CadQuery 0.1.8 has been recently updated to fully support these new 
features)


I just tried and it seems fine now.

thank you again for your feedback.

Maurice

On 24/08/2015 01.26, Marcos Chaparro wrote:

VRML scaling works great using
freecad your_part.step  kicad_StepUp_vrml_export.FCMacro


The parametric generator gives me the following error:

FC Version
['0', '15', 'Unknown', 'Unknown', 'Unknown']FC Version 015
/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery
exists
FC Version
['0', '15', 'Unknown', 'Unknown', 'Unknown']FC Version 015
/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery
exists
CadQuery 0.1.8
CadQuery is a parametric scripting language for creating and traversing
CAD models
Author: David Cowden
License: LGPL
Website: https://github.com/dcowden/cadquery

Opened
/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery/Examples/Ex000_Introduction.py

Executed
/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery/Examples/Ex000_Introduction.py
Ex000 Closed
Dock adjusted
Exception while processing file: make_gw_export_fc.py [__new__() takes
exactly 25 arguments (24 given)]
File format not supported: SOIC_8

It was called from the command line with FreeCAD make_gw_export_fc.py SOIC_8




Marcos

On Sun, Aug 23, 2015 at 4:09 PM, easyw mailto:ea...@katamail.com>> wrote:

Hi Marcos,
thank you for the feedback.
The screenshot is very nice!

1) For fusion object, it is strange, I don't have prob in conserving
colors neither in FC015, nor in FC016 both in win and linux...
but I'm on ubuntu and I used the ubu repos

2) To scale a part there is already a small macro in the demo project;
the file name is kicad_StepUp_vrml_export.FCMacro
and there is also a bash file
launch-kicad_StepUp-step-to-vrml-example.sh

The script has to be cleaned up a bit...
anyway it works... NB after exporting the VRML file, do not save the
FC STEP file or you'll get it scaled too :)

3) I'm going to complete a new macro named 'move_rotate_scale'
(which is not included at the moment), so it would be easier to
manage manufacturer models to align and generate vrml scaled models.
When it si ready I will let you know

4) Please also have a look at:

https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator
there are script to generate parametric STEP and scaled VRML for
SOIC, DIP, QFP, Resistor chips and Capacitor chips
there are some configuration files in which you only need to add
dimensions as in the datasheet, then the model 3D will be generated.
There a re also some already generated examples at:
    
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_cap
    
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_gw
    
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_dip

https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator/generated_res

and a mini starter guide

https://github.com/easyw/kicad-3d-models-in-freecad/raw/master/cadquery/FCAD_script_generator/FC-script-generator-starter-Guide.pdf
I've added a colored pinmark and some more models.

Could you please give me a feedback also on those scripts/models.
Maurice



On 23/08/2015 17.14, Marcos Chaparro wrote:

Hi Maurice,
the issues were related to using freecad 0.16 and non compatible
DXF files
(Freecad 0.15 and 0.16 produced an incompatible dxf file that
was fixed
re-exporting it using librecad in R14 format, later you told me
that R12 is
better but I didn't try.

The final woraround for fusing parts and maintaing the color
correctly was
to make the top level fused part 100% transparent It seems that
when I
export the fused part freecad exports all the parts inside the
fusion too,
and the object surfaces have all 2 faces, one from the fused and
one from
the original, and the colors get messed up. Forcing the fused part
transparent it still exports duplicated faces but since one is
transparent
it doesn't bother me. Maybe it a dependency issue when compiling
FC15 

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos,

I've built FC 015 and FC 016 in debian following all the advices from FC 
site and it seems there are still some issues in fusing objects and 
conserving colors.

I tried some workaround without positive results.

So at the moment, I consider the script to generate parametric models 
fully working in FC 015 under windows and ubuntu.
Anyway users can download colored models from the repository, or just 
build the models under a virtual box with ubuntu.


kicad StepUp script is instead fully working in windows, ubuntu and 
debian.


Thank you for your feedback.
Maurice

On 24/08/2015 17.00, Marcos Chaparro wrote:

Les look for input from other users, most of them will use precompiled
binaries.

I compiled freecad using 2 commands

$ cmake -DFREECAD_USE_EXTERNAL_PIVY=1 -DCMAKE_BUILD_TYPE=Release .
$ make

Its probably a dependency issue on my side, and i don't have the time to
dig too deep into this.

Thanks!
On Aug 24, 2015 10:05 AM, "easyw"  wrote:


Hi Marcos,

I think is related to the problems you have in fusion objects with colors
...

it could be a setting in FreeCAD but I have to investigate better...

I attached the parameter-generated QFP100 3D STEP/VRML model placed on a
parameter-generated footprint (from qfp_wizard.py)
As you can see there are all colors ...

Here there are the models files that should be showed with colors

https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.FCStd

https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.step

https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.wrl

Could you please post me the way in which you have built FC from source?
(like the command line history)

thanks
Maurice


On 24/08/2015 14.21, Marcos Chaparro wrote:


Hi Maurice,
it works now.

Should the models have the correct colors?

See attached what I see:


Marcos

On Mon, Aug 24, 2015 at 6:41 AM, easyw  wrote:

Hi Marcos,


I had a prob in syncing github files...
now they should be synchronized.
https://github.com/easyw/kicad-3d-models-in-freecad/archive/master.zip

You need also to download the latest version of CadQuery Module
https://github.com/jmwright/cadquery-freecad-module/archive/v0.2.0.zip

Just delete the old CadQuery Mod in FreeCAD and use the new one.
(CadQuery 0.1.8 has been recently updated to fully support these new
features)

I just tried and it seems fine now.

thank you again for your feedback.

Maurice


On 24/08/2015 01.26, Marcos Chaparro wrote:

VRML scaling works great using

freecad your_part.step  kicad_StepUp_vrml_export.FCMacro


The parametric generator gives me the following error:

FC Version
['0', '15', 'Unknown', 'Unknown', 'Unknown']FC Version 015
/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery
exists
FC Version
['0', '15', 'Unknown', 'Unknown', 'Unknown']FC Version 015
/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery
exists
CadQuery 0.1.8
CadQuery is a parametric scripting language for creating and traversing
CAD models
Author: David Cowden
License: LGPL
Website: https://github.com/dcowden/cadquery

Opened


/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery/Examples/Ex000_Introduction.py

Executed


/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery/Examples/Ex000_Introduction.py
Ex000 Closed
Dock adjusted
Exception while processing file: make_gw_export_fc.py [__new__() takes
exactly 25 arguments (24 given)]
File format not supported: SOIC_8

It was called from the command line with FreeCAD make_gw_export_fc.py
SOIC_8




Marcos



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad footprint plugins wizard in windows

[easyw]

Hi Marco,

I still cannot find any mention to the path and any howto to use the 
very useful footprint wizard.


I went in the .adoc file and the only mention to the wizard I found is in:
Pcbnew_managing_libs.adoc
but is a mere description of the wizard button
Line 74: | image:images/icons/module_wizard.png[]
Line 75: | Create a module using a wizard

Please consider that
=== Using the Footprint Library Table Wizard
is a different (Library) wizard from the footprint wizard I'm talking 
about, which is a wizard to generate a parameter footprint with python 
scripts


Thank you
Maurice

On 24/08/2015 12.05, Marco Ciampa wrote:

On Sat, Aug 22, 2015 at 02:34:11PM +0200, easyw wrote:

Hi,

I don't know where to place the python plugins file (e.g.
qfp_wizard.py) in windows...

in linux the right place is ~/.kicad_plugins
but I don't know the right place in windows...
I tried with the Nick pre-built windows files
http://www2.futureware.at/~nickoe/kicad-product-r6097.b384c94-x86_64.exe
putting the script in
C:\KiCad-test\lib\kicad\plugins
but it didn't worked

I can't find any help in docs...


If this is still missing, please file an error report on kicad-doc bug.

--


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| GNU/Linux User  #78271 |
| FSFE fellow   #364 |
++


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Help menu in KiCad

[easyw]

Hi Marco,

I also found that the installer do not install the python scripts needed 
by 'new footprint wizard' menu in footprint editor.

these python files should be located inside the bin dir
(e.g. "C:\Program Files\KiCad\bin\scripting\plugins")

Maurice

On 29/08/2015 00.39, Marco Hess wrote:


Just tried the latest windows r6132 build and the help menu still says
'Help file 'kicad' could not be found.'

Just not sure if these help menu's are expected to work 'yet'?

Also, the help documents that are installed in the windows package at
'C:\KiCad\share\doc\kicad\help\en' appear to be at least a year old?


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad footprint plugins wizard in windows

[easyw]

Hi,

Here is the patch vs revision 6132 for adding exposed pad to qfp_wyzard

I added the exposed pad option and changed name from QFP to QFP/QFN.
I used the function PadLineArray because I couldn't find the apis doc...
anyway it should be fine.
I assigned 0 to exposed pad pin number...
please let me know if it is fine or if I should change it to maxpin 
number +1.


Thank you,
Maurice

On 23/08/2015 17.29, jp charras wrote:

Le 23/08/2015 16:41, easyw a écrit :

Hi JP,

The changes are fully working.
thanks for committing.

PS
I see you added a bar code generator to fp wizard...
Do you think it would possible to add also an option for exposed pad in
qfp/qfn footprint?
thank you
Maurice


Yes, I think this is a good idea.




--- qfp_wizard-old.py   2015-08-29 21:25:33.516578500 +0200
+++ qfp_wizard.py   2015-08-29 21:14:59.912787800 +0200
@@ -24,10 +24,10 @@
 class QFPWizard(HelpfulFootprintWizardPlugin.HelpfulFootprintWizardPlugin):

 def GetName(self):
-return "QFP"
+return "QFP/QFN"

 def GetDescription(self):
-return "QFP Footprint Wizard"
+return "QFP/QFN Footprint Wizard"

 def GenerateParameterList(self):
 self.AddParam("Pads", "n", self.uNatural, 100)
@@ -41,6 +41,9 @@
 self.AddParam("Pads", "package width", self.uMM, 14)
 self.AddParam("Pads", "package height", self.uMM, 14)

+self.AddParam("Pads", "epad width", self.uMM, 0.0)
+self.AddParam("Pads", "epad length", self.uMM, 0.0)
+
 def CheckParameters(self):

 self.CheckParamInt("Pads", "*n", is_multiple_of=4)
@@ -57,6 +60,9 @@
 pad_length = self.parameters["Pads"]["pad length"]
 pad_width = self.parameters["Pads"]["pad width"]

+epad_length = self.parameters["Pads"]["epad length"]
+epad_width = self.parameters["Pads"]["epad width"]
+
 v_pitch = pads["vertical pitch"]
 h_pitch = pads["horizontal pitch"]

@@ -99,6 +105,17 @@
 array.SetFirstPadInArray(3*pads_per_row + 1)
 array.AddPadsToModule(self.draw)

+#epad
+if epad_length!=0 and epad_width!=0:
+e_pad = PA.PadMaker(self.module).SMDPad(
+epad_width, epad_length, shape=pcbnew.PAD_SHAPE_RECT)
+epadPos = pcbnew.wxPoint (0, 0)
+array = PA.PadLineArray(e_pad, 1, 1, False,
+epadPos)
+array.SetFirstPadInArray(0)
+array.AddPadsToModule(self.draw)
+
+
 lim_x = pads["package width"] / 2
 lim_y = pads["package height"] / 2
 inner = (row_len / 2) + pad_pitch
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Marcos,

I updated the script with very minor improvements (most cosmetics).
http://sourceforge.net/projects/kicadstepup/files/latest/download

I improved also the doc
http://sourceforge.net/projects/kicadstepup/files/kicadStepUp-starter-Guide.pdf

and most of all I added the move-rotate-scale.FCMacro (it is inside the 
kicad_stepup latest zip file)


I think you should find this macro very useful to position/align the 
position of manufacture's model to the right position/orientation, and 
to scale the vrml model to inch for kicad 3d-viewer


It is a GUI macro with some nice buttons; just do some click and your 
model will be aligned as required.


Maurice

PS the repository for parametric generated STEP and VRML models is 
growing...

we have now:
QFN and Molded QFN ICs,
SOIC, SSOP, MSOP, TSSOP, SOT, QFP, LQFP, TQFP ... (GullWings in general),
DIP ICS,
Chip Capacitors,
Chip resistors,
pin-strip headers



On 25/08/2015 01.50, Marcos Chaparro wrote:

Debian didn't package FC 0.15 because of these unmet dependencies:
https://release.debian.org/migration/testing.pl?package=freecad

I was looking for a package maintener email to ask about this and ran into
that page. Debian users should sit and wait or get hands on the code to
make it work. I guess FreeCAD should have a more strict dependency check.

Thanks Maurice for all your support, I'll use your tools a lot :)


Marcos

On Mon, Aug 24, 2015 at 6:02 PM, easyw  wrote:


Hi Marcos,

I've built FC 015 and FC 016 in debian following all the advices from FC
site and it seems there are still some issues in fusing objects and
conserving colors.
I tried some workaround without positive results.

So at the moment, I consider the script to generate parametric models
fully working in FC 015 under windows and ubuntu.
Anyway users can download colored models from the repository, or just
build the models under a virtual box with ubuntu.

kicad StepUp script is instead fully working in windows, ubuntu and debian.

Thank you for your feedback.
Maurice


On 24/08/2015 17.00, Marcos Chaparro wrote:


Les look for input from other users, most of them will use precompiled
binaries.

I compiled freecad using 2 commands

$ cmake -DFREECAD_USE_EXTERNAL_PIVY=1 -DCMAKE_BUILD_TYPE=Release .
$ make

Its probably a dependency issue on my side, and i don't have the time to
dig too deep into this.

Thanks!
On Aug 24, 2015 10:05 AM, "easyw"  wrote:

Hi Marcos,


I think is related to the problems you have in fusion objects with colors
...

it could be a setting in FreeCAD but I have to investigate better...

I attached the parameter-generated QFP100 3D STEP/VRML model placed on a
parameter-generated footprint (from qfp_wizard.py)
As you can see there are all colors ...

Here there are the models files that should be showed with colors


https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.FCStd


https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.step


https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.wrl

Could you please post me the way in which you have built FC from source?
(like the command line history)

thanks
Maurice


On 24/08/2015 14.21, Marcos Chaparro wrote:

Hi Maurice,

it works now.

Should the models have the correct colors?

See attached what I see:


Marcos

On Mon, Aug 24, 2015 at 6:41 AM, easyw  wrote:

Hi Marcos,



I had a prob in syncing github files...
now they should be synchronized.
https://github.com/easyw/kicad-3d-models-in-freecad/archive/master.zip

You need also to download the latest version of CadQuery Module
https://github.com/jmwright/cadquery-freecad-module/archive/v0.2.0.zip

Just delete the old CadQuery Mod in FreeCAD and use the new one.
(CadQuery 0.1.8 has been recently updated to fully support these new
features)

I just tried and it seems fine now.

thank you again for your feedback.

Maurice


On 24/08/2015 01.26, Marcos Chaparro wrote:

VRML scaling works great using


freecad your_part.step  kicad_StepUp_vrml_export.FCMacro


The parametric generator gives me the following error:

FC Version
['0', '15', 'Unknown', 'Unknown', 'Unknown']FC Version 015
/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery
exists
FC Version
['0', '15', 'Unknown', 'Unknown', 'Unknown']FC Version 015
/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery
exists
CadQuery 0.1.8
CadQuery is a parametric scripting language for creating and
traversing
CAD models
Author: David Cowden
License: LGPL
Website: https://github.com/dcowden/cadquery

Opened



/home/marcos/life/Downloads/FreeCAD-releases-FreeCAD-0-15/Mod/CadQuery/Examples/Ex000_Introduction.py

Execu

Re: [Kicad-developers] kicad StepUp update and STEP repository of parametric models

[easyw]

Hi Mario,

thank you for your feedback

now the file should be fine
Maurice

On 30/08/2015 15.43, Mário Luzeiro wrote:

Hi Maurice,

I cannot open the
kicadStepUp-starter-Guide.pdf

on linux in any program. it says the file is corrupted or invalid...

Mario Luzeiro

From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
easyw [ea...@katamail.com]
Sent: 30 August 2015 15:39
To: Marcos Chaparro; KiCad Developers
Subject: Re: [Kicad-developers] kicad StepUp update and STEP repository of 
parametric models

Hi Marcos,

I updated the script with very minor improvements (most cosmetics).
http://sourceforge.net/projects/kicadstepup/files/latest/download

I improved also the doc
http://sourceforge.net/projects/kicadstepup/files/kicadStepUp-starter-Guide.pdf

and most of all I added the move-rotate-scale.FCMacro (it is inside the
kicad_stepup latest zip file)

I think you should find this macro very useful to position/align the
position of manufacture's model to the right position/orientation, and
to scale the vrml model to inch for kicad 3d-viewer

It is a GUI macro with some nice buttons; just do some click and your
model will be aligned as required.

Maurice

PS the repository for parametric generated STEP and VRML models is
growing...
we have now:
QFN and Molded QFN ICs,
SOIC, SSOP, MSOP, TSSOP, SOT, QFP, LQFP, TQFP ... (GullWings in general),
DIP ICS,
Chip Capacitors,
Chip resistors,
pin-strip headers



On 25/08/2015 01.50, Marcos Chaparro wrote:

Debian didn't package FC 0.15 because of these unmet dependencies:
https://release.debian.org/migration/testing.pl?package=freecad

I was looking for a package maintener email to ask about this and ran into
that page. Debian users should sit and wait or get hands on the code to
make it work. I guess FreeCAD should have a more strict dependency check.

Thanks Maurice for all your support, I'll use your tools a lot :)


Marcos

On Mon, Aug 24, 2015 at 6:02 PM, easyw  wrote:


Hi Marcos,

I've built FC 015 and FC 016 in debian following all the advices from FC
site and it seems there are still some issues in fusing objects and
conserving colors.
I tried some workaround without positive results.

So at the moment, I consider the script to generate parametric models
fully working in FC 015 under windows and ubuntu.
Anyway users can download colored models from the repository, or just
build the models under a virtual box with ubuntu.

kicad StepUp script is instead fully working in windows, ubuntu and debian.

Thank you for your feedback.
Maurice


On 24/08/2015 17.00, Marcos Chaparro wrote:


Les look for input from other users, most of them will use precompiled
binaries.

I compiled freecad using 2 commands

$ cmake -DFREECAD_USE_EXTERNAL_PIVY=1 -DCMAKE_BUILD_TYPE=Release .
$ make

Its probably a dependency issue on my side, and i don't have the time to
dig too deep into this.

Thanks!
On Aug 24, 2015 10:05 AM, "easyw"  wrote:

Hi Marcos,


I think is related to the problems you have in fusion objects with colors
...

it could be a setting in FreeCAD but I have to investigate better...

I attached the parameter-generated QFP100 3D STEP/VRML model placed on a
parameter-generated footprint (from qfp_wizard.py)
As you can see there are all colors ...

Here there are the models files that should be showed with colors


https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.FCStd


https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.step


https://github.com/easyw/kicad-3d-models-in-freecad/blob/master/cadquery/FCAD_script_generator/generated_gw/soic/soic_8_39x49_p127.wrl

Could you please post me the way in which you have built FC from source?
(like the command line history)

thanks
Maurice


On 24/08/2015 14.21, Marcos Chaparro wrote:

Hi Maurice,

it works now.

Should the models have the correct colors?

See attached what I see:


Marcos

On Mon, Aug 24, 2015 at 6:41 AM, easyw  wrote:

Hi Marcos,



I had a prob in syncing github files...
now they should be synchronized.
https://github.com/easyw/kicad-3d-models-in-freecad/archive/master.zip

You need also to download the latest version of CadQuery Module
https://github.com/jmwright/cadquery-freecad-module/archive/v0.2.0.zip

Just delete the old CadQuery Mod in FreeCAD and use the new one.
(CadQuery 0.1.8 has been recently updated to fully support these new
features)

I just tried and it seems fine now.

thank you again for your feedback.

Maurice


On 24/08/2015 01.26, Marcos Chaparro wrote:

VRML scaling works great using


freecad your_part.step  kicad_StepUp_vrml_export.FCMacro


The parametric generator gives me the following error:

FC Version
['0', '15', 'Unknown', 'Unknown', 'Unknown']FC Vers

Re: [Kicad-developers] kicad footprint plugins wizard in windows

[easyw]

Hi,

I attached a patch that is implementing epad and thermal vias on qfp_wizard.

the script is almost completed ...
I have three kind of questions:
1) how could I eliminate front silk on thermal via (pads)? I couldn't 
find a class to do it
2) is there a way to reduce solder Mask on bottom layer for vias?  I 
couldn't find a class to do it
3) in which order the Parameters list is created? I don't know how to 
put similar inputs close each others

 (e.g. epad thermal w pitch, epad thermal l, epad solder paste ratio)

I used as reference the microchip qfn 64 as in:
http://www.microchip.com/mymicrochip/filehandler.aspx?ddocname=en012702
http://ww1.microchip.com/downloads/en/PackagingSpec/0049BY.pdf
at page 397,398
64-Lead Plastic Quad Flat, No Lead Package (MR) – 9x9x0.9 mm Body [QFN]
With 7.70 x 7.70 Exposed Pad [QFN]

than you
Maurice

On 30/08/2015 20.27, jp charras wrote:

Le 30/08/2015 19:21, nnn a écrit :

It may be better to make exposed pad as array of smaller pads for better
application of solder paste. This will also allow to easily change the
pad into array of tht pads for improved power dissipation. Below - how I
did it in C (full code here:
https://github.com/michal777/KiCad_Footprint_Generator). I think exposed
pad should be numbered max+1 because sometimes there are more exposed pads.


Exactly one exposed pad not on solder paste (but on solder mask) + this
array of pads on solder paste.

Keep the same pad name for all of them, and make them optional in wizard.

--- qfp_wizard-old.py   2015-08-29 21:25:33.516578500 +0200
+++ qfp_wizard.py   2015-08-31 14:54:31.031976300 +0200
@@ -24,22 +24,33 @@
 class QFPWizard(HelpfulFootprintWizardPlugin.HelpfulFootprintWizardPlugin):
 
 def GetName(self):
-return "QFP"
+return "QFP/QFN"
 
 def GetDescription(self):
-return "QFP Footprint Wizard"
+return "QFP/QFN Footprint Wizard"
 
 def GenerateParameterList(self):
-self.AddParam("Pads", "n", self.uNatural, 100)
+self.AddParam("Pads", "n", self.uNatural, 64)
 self.AddParam("Pads", "pad pitch", self.uMM, 0.5)
-self.AddParam("Pads", "pad width", self.uMM, 0.25)
-self.AddParam("Pads", "pad length", self.uMM, 1.5)
-self.AddParam("Pads", "vertical pitch", self.uMM, 15)
-self.AddParam("Pads", "horizontal pitch", self.uMM, 15)
-self.AddParam("Pads", "oval", self.uBool, True)
+self.AddParam("Pads", "pad width", self.uMM, 0.3)
+self.AddParam("Pads", "pad length", self.uMM, 0.9)
+self.AddParam("Pads", "vertical pitch", self.uMM, 8.9)
+self.AddParam("Pads", "horizontal pitch", self.uMM, 8.9)
+self.AddParam("Pads", "oval", self.uBool, False)
+
+self.AddParam("Pads", "package width", self.uMM, 9)
+self.AddParam("Pads", "package height", self.uMM, 9)
+
+self.AddParam("Pads", "epad width", self.uMM, 7.5)
+self.AddParam("Pads", "epad length", self.uMM, 7.5)
+self.AddParam("Pads", "epad thermal w pitch", self.uMM, 1.0)
+self.AddParam("Pads", "epad thermal l pitch", self.uMM, 1.0)
+self.AddParam("Pads", "epad solder paste ratio", self.uNatural, 0.8)
+
+self.AddParam("Pads", "epad thermal via diam", self.uMM, 0.3)
+self.AddParam("Pads", "epad thermal via size", self.uMM, 0.5)
+
 
-self.AddParam("Pads", "package width", self.uMM, 14)
-self.AddParam("Pads", "package height", self.uMM, 14)
 
 def CheckParameters(self):
 
@@ -57,6 +68,16 @@
 pad_length = self.parameters["Pads"]["pad length"]
 pad_width = self.parameters["Pads"]["pad width"]
 
+epad_length = self.parameters["Pads"]["epad length"]
+epad_width = self.parameters["Pads"]["epad width"]
+
+epad_th_pitch_w = self.parameters["Pads"]["epad thermal w pitch"]
+epad_th_pitch_l = self.parameters["Pads"]["epad thermal l pitch"]
+epad_paste_ratio = pads["*epad solder paste ratio"]
+
+epad_th_via_dm = self.parameters["Pads"]["epad thermal via diam"]
+epad_th_via_sz = self.parameters["Pads"]["epad thermal via size"]
+
 v_pitch = pads["vertical pitch"]
 h_pitch = pads["horizontal pitch"]
 
@@ -99,6 +120,39 @@
 array.SetFirstPadInArray(3*pads_per_row + 1)
 array.AddPadsToModule(self.draw)
 
+#epad
+if epad_length!=0 and epad_width!=0:  #there is exposed pad
+e_pad = PA.PadMaker(self.module).SMDePad(
+epad_width, epad_length, shape=pcbnew.PAD_SHAPE_RECT)
+epadPos = pcbnew.wxPoint (0, 0)
+array = PA.PadLineArray(e_pad, 1, 1, False,
+epadPos)
+#array.SetFirstPadInArray(0)
+array.SetFirstPadInArray(pads["*n"]+1)
+array.AddPadsToModule(self.draw)
+
+epad_width_part_size_w = epad_th_pitch_w*epad_paste_ratio  #size 
of one part of exposed pad
+epad_width_part_size_l = epad_th_pitch_l*

Re: [Kicad-developers] kicad footprint plugins wizard in windows

[easyw]

Hi JP,

here is the patch with one exposed pad not on solder paste (but on 
solder mask) + this array of pads on solder paste.
the same pad name for all of them, and pads optional in wizard 
(assigning epad subdivision to 0 epad array won't be generated;

 assigning epad width or lenght to 0, epad  won't be generated).

Maurice

On 30/08/2015 20.27, jp charras wrote:

Le 30/08/2015 19:21, nnn a écrit :

It may be better to make exposed pad as array of smaller pads for better
application of solder paste. This will also allow to easily change the
pad into array of tht pads for improved power dissipation. Below - how I
did it in C (full code here:
https://github.com/michal777/KiCad_Footprint_Generator). I think exposed
pad should be numbered max+1 because sometimes there are more exposed pads.


Exactly one exposed pad not on solder paste (but on solder mask) + this
array of pads on solder paste.

Keep the same pad name for all of them, and make them optional in wizard.

--- qfp_wizard-old.py   2015-09-03 15:04:44.826058400 +0200
+++ qfp_wizard.py   2015-09-03 15:13:51.682393300 +0200
@@ -24,22 +24,29 @@
 class QFPWizard(HelpfulFootprintWizardPlugin.HelpfulFootprintWizardPlugin):

 def GetName(self):
-return "QFP"
+return "QFP/QFN"

 def GetDescription(self):
-return "QFP Footprint Wizard"
+return "QFP/QFN Footprint Wizard"

 def GenerateParameterList(self):
-self.AddParam("Pads", "n", self.uNatural, 100)
+
+self.AddParam("Pads", "n", self.uNatural, 64)
 self.AddParam("Pads", "pad pitch", self.uMM, 0.5)
-self.AddParam("Pads", "pad width", self.uMM, 0.25)
-self.AddParam("Pads", "pad length", self.uMM, 1.5)
-self.AddParam("Pads", "vertical pitch", self.uMM, 15)
-self.AddParam("Pads", "horizontal pitch", self.uMM, 15)
-self.AddParam("Pads", "oval", self.uBool, True)
+self.AddParam("Pads", "pad width", self.uMM, 0.3)
+self.AddParam("Pads", "pad length", self.uMM, 0.9)
+self.AddParam("Pads", "vertical pitch", self.uMM, 8.9)
+self.AddParam("Pads", "horizontal pitch", self.uMM, 8.9)
+self.AddParam("Pads", "oval", self.uBool, False)
+self.AddParam("Pads", "package width", self.uMM, 9)
+self.AddParam("Pads", "package height", self.uMM, 9)
+self.AddParam("Pads", "epad width", self.uMM, 7.5)
+self.AddParam("Pads", "epad length", self.uMM, 7.5)
+self.AddParam("Pads", "epad subdivision h", self.uNatural, 2)
+self.AddParam("Pads", "epad subdivision v", self.uNatural, 2)
+self.AddParam("Pads", "Name prefix QFP/QFN", self.uString, 'QFN')
+self.AddParam("Pads", "epad solder paste ratio", self.uNatural, 0.8)

-self.AddParam("Pads", "package width", self.uMM, 14)
-self.AddParam("Pads", "package height", self.uMM, 14)

 def CheckParameters(self):

@@ -47,16 +54,24 @@
 self.CheckParamBool("Pads", "*oval")

 def GetValue(self):
-return "QFP_%d" % self.parameters["Pads"]["*n"]
+return "%s_%d" % (self.parameters["Pads"]["*Name prefix QFP/QFN"], 
self.parameters["Pads"]["*n"])

 def BuildThisFootprint(self):

 pads = self.parameters["Pads"]

+module_prefix = pads["*Name prefix QFP/QFN"]
 pad_pitch = pads["pad pitch"]
 pad_length = self.parameters["Pads"]["pad length"]
 pad_width = self.parameters["Pads"]["pad width"]

+epad_length = self.parameters["Pads"]["epad length"]
+epad_width = self.parameters["Pads"]["epad width"]
+epad_subd_l = pads["*epad subdivision h"]
+epad_subd_w = pads["*epad subdivision v"]
+
+epad_paste_ratio = pads["*epad solder paste ratio"]
+
 v_pitch = pads["vertical pitch"]
 h_pitch = pads["horizontal pitch"]

@@ -99,6 +114,29 @@
 array.SetFirstPadInArray(3*pads_per_row + 1)
 array.AddPadsToModule(self.draw)

+#epad
+if epad_length!=0 and epad_width!=0:  #there is exposed pad
+e_pad = PA.PadMaker(self.module).SMDePad(
+epad_width, epad_length, shape=pcbnew.PAD_SHAPE_RECT)
+epadPos = pcbnew.wxPoint (0, 0)
+array = PA.PadLineArray(e_pad, 1, 1, False,
+epadPos)
+array.SetFirstPadInArray(pads["*n"]+1)
+array.AddPadsToModule(self.draw)
+
+if epad_subd_l!=0 and epad_subd_w!=0:
+#if we want epad
+epad_width_part_size_w = epad_width / epad_subd_w  #size of 
one part of exposed pad
+epad_width_part_size_l = epad_length / epad_subd_l
+epad_paste = PA.PadMaker(self.module).SMDPad(
+epad_width_part_size_w*epad_paste_ratio, 
epad_width_part_size_l*epad_paste_ratio, shape=pcbnew.PAD_SHAPE_RECT)
+
+array_epad = PA.PadThermalArray(epad_paste, epad_subd_l, 
epad_subd_w,
+epad_width_part_size_l, 

[Kicad-developers] [PATCH] QFN with exposed pad - kicad footprint plugins wizard

[easyw]

Hi,

I attached a patch for exposed pad on qfp_wizard.
There is one exposed pad not on solder paste (but on solder mask) + one 
array of pads on solder paste.
the same pad name for all of them, and pads optional in wizard 
(assigning epad subdivision to 0 epad array won't be generated;

 assigning epad width or lenght to 0, epad  won't be generated).

Could please someone tells me if there is something to change or wrong 
in that ...

it seems not to be considered / committed

PS I changeg the subject because it is not related only to windows but 
is fine for linux and osx too.


than you
Maurice

On 30/08/2015 20.27, jp charras wrote:

Le 30/08/2015 19:21, nnn a écrit :

It may be better to make exposed pad as array of smaller pads for better
application of solder paste. This will also allow to easily change the
pad into array of tht pads for improved power dissipation. Below - how I
did it in C (full code here:
https://github.com/michal777/KiCad_Footprint_Generator). I think exposed
pad should be numbered max+1 because sometimes there are more exposed pads.


Exactly one exposed pad not on solder paste (but on solder mask) + this
array of pads on solder paste.

Keep the same pad name for all of them, and make them optional in wizard.



--- qfp_wizard-old.py   2015-09-03 15:04:44.826058400 +0200
+++ qfp_wizard.py   2015-09-03 15:13:51.682393300 +0200
@@ -24,22 +24,29 @@
 class QFPWizard(HelpfulFootprintWizardPlugin.HelpfulFootprintWizardPlugin):

 def GetName(self):
-return "QFP"
+return "QFP/QFN"

 def GetDescription(self):
-return "QFP Footprint Wizard"
+return "QFP/QFN Footprint Wizard"

 def GenerateParameterList(self):
-self.AddParam("Pads", "n", self.uNatural, 100)
+
+self.AddParam("Pads", "n", self.uNatural, 64)
 self.AddParam("Pads", "pad pitch", self.uMM, 0.5)
-self.AddParam("Pads", "pad width", self.uMM, 0.25)
-self.AddParam("Pads", "pad length", self.uMM, 1.5)
-self.AddParam("Pads", "vertical pitch", self.uMM, 15)
-self.AddParam("Pads", "horizontal pitch", self.uMM, 15)
-self.AddParam("Pads", "oval", self.uBool, True)
+self.AddParam("Pads", "pad width", self.uMM, 0.3)
+self.AddParam("Pads", "pad length", self.uMM, 0.9)
+self.AddParam("Pads", "vertical pitch", self.uMM, 8.9)
+self.AddParam("Pads", "horizontal pitch", self.uMM, 8.9)
+self.AddParam("Pads", "oval", self.uBool, False)
+self.AddParam("Pads", "package width", self.uMM, 9)
+self.AddParam("Pads", "package height", self.uMM, 9)
+self.AddParam("Pads", "epad width", self.uMM, 7.5)
+self.AddParam("Pads", "epad length", self.uMM, 7.5)
+self.AddParam("Pads", "epad subdivision h", self.uNatural, 2)
+self.AddParam("Pads", "epad subdivision v", self.uNatural, 2)
+self.AddParam("Pads", "Name prefix QFP/QFN", self.uString, 'QFN')
+self.AddParam("Pads", "epad solder paste ratio", self.uNatural, 0.8)

-self.AddParam("Pads", "package width", self.uMM, 14)
-self.AddParam("Pads", "package height", self.uMM, 14)

 def CheckParameters(self):

@@ -47,16 +54,24 @@
 self.CheckParamBool("Pads", "*oval")

 def GetValue(self):
-return "QFP_%d" % self.parameters["Pads"]["*n"]
+return "%s_%d" % (self.parameters["Pads"]["*Name prefix QFP/QFN"], 
self.parameters["Pads"]["*n"])

 def BuildThisFootprint(self):

 pads = self.parameters["Pads"]

+module_prefix = pads["*Name prefix QFP/QFN"]
 pad_pitch = pads["pad pitch"]
 pad_length = self.parameters["Pads"]["pad length"]
 pad_width = self.parameters["Pads"]["pad width"]

+epad_length = self.parameters["Pads"]["epad length"]
+epad_width = self.parameters["Pads"]["epad width"]
+epad_subd_l = pads["*epad subdivision h"]
+epad_subd_w = pads["*epad subdivision v"]
+
+epad_paste_ratio = pads["*epad solder paste ratio"]
+
 v_pitch = pads["vertical pitch"]
 h_pitch = pads["horizontal pitch"]

@@ -99,6 +114,29 @@
 array.SetFirstPadInArray(3*pads_per_row + 1)
 array.AddPadsToModule(self.draw)

+#epad
+if epad_length!=0 and epad_width!=0:  #there is exposed pad
+e_pad = PA.PadMaker(self.module).SMDePad(
+epad_width, epad_length, shape=pcbnew.PAD_SHAPE_RECT)
+epadPos = pcbnew.wxPoint (0, 0)
+array = PA.PadLineArray(e_pad, 1, 1, False,
+epadPos)
+array.SetFirstPadInArray(pads["*n"]+1)
+array.AddPadsToModule(self.draw)
+
+if epad_subd_l!=0 and epad_subd_w!=0:
+#if we want epad
+epad_width_part_size_w = epad_width / epad_subd_w  #size of 
one part of exposed pad
+epad_width_part_size_l = epad_length / epad_subd_l
+epad_paste = PA.PadMaker(self.module).SMDPad(
+

Re: [Kicad-developers] official web page

[easyw]

Hi Wayne,
regarding kicad StepUp script,
please have a look at this comment...
https://forum.kicad.info/t/kicad-stepup-new-exporter-for-3d-mcad-feedbacks-are-welcome/1048/13

I've improved the script and tested it quite heavily...
Please consider that the script does not touch any kicad file, it only 
reads the data and generates the STEP model followings the data read.


I know that now you all are focused on the stable release, so I'm not 
asking to add the script to kicad, but I'm thinking it would be nice and 
may be useful to MCAD users, to add just a mention that it is possible 
to convert kicad board in STEP through the script, as in the starter 
guide that I have done in asciidoc.


May be under http://kicad-pcb.org/help/documentation/
just after 'IDF exporter' section
and/or in the manual.

Thank you for considering that,
Maurice


On 10/08/2015 16.02, Wayne Stambaugh wrote:

Maurice,

The 7z archive attachment in you original email looks find to me.  All
of the image files appear to be correct.  Before we include the step up
script documentation in the KiCad documentation we need to include
script in KiCad.  Would those who have tested this script, please
comment on whether or not it is ready to be added to the KiCad source.
It would be nice to have some step support for the stable release but
only if it's ready.

Cheers,

Wayne




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] official web page

[easyw]

Wayne,

thank you for your reply.

I already noticed that there is the link
  http://kicad-pcb.org/help/external-tools/

What I'm missing are the 2 images that I made with hackrf-one in kicad 
3d-viewer and in MCAD Catia.

Those images were been included in old kicad web site.
http://confluence.kicad-pcb.org/download/attachments/589828/hackrf-one-stepup-kicad-3d-viewer.png
http://confluence.kicad-pcb.org/download/attachments/589828/hackrf-one-stepup-catia-assembly.png

I was thinking if you may consider to put those images also in the new 
web site, just under the video of the 3d-viewer

http://kicad-pcb.org/discover/3dviewer/
where the web page says:
 'Export a realistic rendering of your project as a picture or a MCAD 
hierarchical assembly.'


The two images show how Kicad can provide 3D data transfer from ECAD 
system to the MCAD world.


Thank you again for your attention.

Maurice

On 08/09/2015 00.42, Wayne Stambaugh wrote:

Maurice,

It's already mentioned here: http://kicad-pcb.org/help/external-tools/.

Is this what your looking for or did you have something else in mind?

I haven't had a chance to use this yet but it sounds really interesting
so it will be near the top of my list of things to include during the
next development cycle.

Thanks,

Wayne

On 9/6/2015 6:17 PM, easyw wrote:

Hi Wayne,
regarding kicad StepUp script,
please have a look at this comment...
https://forum.kicad.info/t/kicad-stepup-new-exporter-for-3d-mcad-feedbacks-are-welcome/1048/13


I've improved the script and tested it quite heavily...
Please consider that the script does not touch any kicad file, it only
reads the data and generates the STEP model followings the data read.

I know that now you all are focused on the stable release, so I'm not
asking to add the script to kicad, but I'm thinking it would be nice and
may be useful to MCAD users, to add just a mention that it is possible
to convert kicad board in STEP through the script, as in the starter
guide that I have done in asciidoc.

May be under http://kicad-pcb.org/help/documentation/
just after 'IDF exporter' section
and/or in the manual.

Thank you for considering that,
Maurice


On 10/08/2015 16.02, Wayne Stambaugh wrote:

Maurice,

The 7z archive attachment in you original email looks find to me.  All
of the image files appear to be correct.  Before we include the step up
script documentation in the KiCad documentation we need to include
script in KiCad.  Would those who have tested this script, please
comment on whether or not it is ready to be added to the KiCad source.
It would be nice to have some step support for the stable release but
only if it's ready.

Cheers,

Wayne





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] dxf: import 4 arcs

[easyw]

Hi Marcos and Marco,

please find attached the dxf that I did from scratch using 4 arcs in 
LibreCAD

I copied manually the path from palta2.dxf, then exported in dxf R12
The result is fine in kicad and I get a closed path also for Edge cuts.

in kicad there are 4 arcs
  (gr_arc (start 178.564202 123.937945) (end 153.273203 83.107373) 
(angle -26.04011298) (layer Edge.Cuts) (width 0.1))
  (gr_arc (start 156.68577 88.642784) (end 162.837792 90.749678) (angle 
-140.5586133) (layer Edge.Cuts) (width 0.1))
  (gr_arc (start 196.246745 102.229265) (end 162.837792 90.749678) 
(angle -22.2858684) (layer Edge.Cuts) (width 0.1))
  (gr_arc (start 148.500893 105.004408) (end 137.915937 98.354967) 
(angle -215.4739741) (layer Edge.Cuts) (width 0.1))


If you search inside palta2.dxf you find POLYLINE that are not supported 
by kicad


attached a comparison of dxf files

I suspect that the problem is when exporting dxf from FreeCAD...
I had some trouble with a different board path exported from FreeCAD...
In FreeCAD you cannot select which version of dxf you want to use, if I 
remember correctly...


Maurice







On 09/09/2015 07.43, Marco Hess wrote:

Definitely a problem with the DXF importer I would say as the resulting
data in the PCB file are just  straight line segments:

   (gr_line (start 42.68541 28.017695) (end 52.25 35.66) (layer
Edge.Cuts) (width 0.1))
   (gr_line (start 27.328145 43.265288) (end 42.68541 28.017695) (layer
Edge.Cuts) (width 0.1))
   (gr_line (start 50.392159 49.187096) (end 27.328145 43.265288) (layer
Edge.Cuts) (width 0.1))
   (gr_line (start 52.25 35.66) (end 50.392159 49.187096) (layer
Edge.Cuts) (width 0.1))

Marco

On 09-Sep-15 14:58, Marco Hess wrote:

Hi Marcos,

Apologies, but I did not see your original email where you said you
tried the R12 format alreayd.

I tried it as well and and it indeed seems to do something strange
with just connecting the end points of the circles or something.

Regards,

Marco

On 09-Sep-15 14:29, Marco Hess wrote:

KiCad DXF import for those kind of segments don't work very well. You
need to re-export the DXF in a DXF R12 format.

You can do that easily by opening the DXF in LibreCAD and then
reexporting in R12 format.

See http://docs.kicad-pcb.org/Pcbnew/Pcbnew.html#_creating_a_board

Section 6.1.2 and 6.1.3.

Cheers,

Marco


On 09-Sep-15 14:24, Marcos Chaparro wrote:


Seems that is kind of Berzier Curve, not few arcs. Probably
that shape needs to

split to single arcs before import.


Um, I don't know if its converted to a bezier curve, but I'm sure I
made it from 4 arcs, see attached.


___
Mailing list:https://launchpad.net/~kicad-developers
Post to :kicad-developers@lists.launchpad.net
Unsubscribe :https://launchpad.net/~kicad-developers
More help   :https://help.launchpad.net/ListHelp


--
Marco Hess
Through IP Pty. Ltd. - AUSTRALIA
www.through-ip.com   |marco.h...@through-ip.com
p: +61 407 78 55 66 | f: +61 8 8121 6191


___
Mailing list:https://launchpad.net/~kicad-developers
Post to :kicad-developers@lists.launchpad.net
Unsubscribe :https://launchpad.net/~kicad-developers
More help   :https://help.launchpad.net/ListHelp




___
Mailing list:https://launchpad.net/~kicad-developers
Post to :kicad-developers@lists.launchpad.net
Unsubscribe :https://launchpad.net/~kicad-developers
More help   :https://help.launchpad.net/ListHelp


--
Marco Hess
Through IP Pty. Ltd. - AUSTRALIA
www.through-ip.com   |marco.h...@through-ip.com
p: +61 407 78 55 66 | f: +61 8 8121 6191



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

(kicad_pcb (version 4) (host pcbnew "(2015-08-31 BZR 6138)-product")

  (general
(links 0)
(no_connects 0)
(area 135.950638 82.089985 196.296746 123.987946)
(thickness 1.6)
(drawings 4)
(tracks 0)
(zones 0)
(modules 0)
(nets 1)
  )

  (page A4)
  (layers
(0 F.Cu signal)
(1 In1.Cu signal)
(2 In2.Cu signal)
(31 B.Cu signal)
(32 B.Adhes user)
(33 F.Adhes user)
(34 B.Paste user)
(35 F.Paste user)
(36 B.SilkS user)
(37 F.SilkS user)
(38 B.Mask user)
(39 F.Mask user)
(40 Dwgs.User user)
(41 Cmts.User user)
(42 Eco1.User user)
(43 Eco2.User user)
(44 Edge.Cuts user)
  )

  (setup
(last_trace_width 0.3048)
(user_trace_width 0.508)
(user_trace_width 0.762)
(trace_clearance 0.254)
(zone_clearance 0.508)
(zone_45_only no)
(trace_min 0.254)
(segment_width 0.15)
(edge_width 0.15)
(via_size 0.9652)
(via_drill 0.508)
(via_min_size 0.889)
(via_min_drill 0.508)
(user_via 1.397 0.889)
(user_via 1.778 0.889)
(uvia_size 0

Re: [Kicad-developers] dxf: import 4 arcs

[easyw]

I still consider that a message to be added as warning in the import 
dialog saying "use R12 dxf version without polyline" would be useful



On 09/09/2015 18.31, LordBlick wrote:

In response to a message written on 09.09.2015, 17:56, from easyw:

A good solution is to open palta2.dxf, select the object and explode
it (I'm
using LibreCAD 2.0.8 in windows: Select object, Menu Modify Explode)



Seems that is kind of Berzier Curve, not  few arcs. Probably that shape
needs to split to single arcs before import.

I told you so… ;) Polyline in fact is a simple kind of Quadratic Bézier -
control point is opposite on the symmetric line to arc center, but is
closely
related to it.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Future, more flexible D_PAD class

[easyw]

It would also be nice to have a thermal via/pad class, without solder 
mask and silk screen, visible/available also to python scripting...
that would improve footprint wizard to create QFN footprints with 
exposed pad and thermal vias.

https://kicad-info.s3-us-west-2.amazonaws.com/original/1X/7f92d064882d899930f1893523dc2989569ab87e.PNG
https://kicad-info.s3-us-west-2.amazonaws.com/original/1X/a4a86bb5ce6e365bd1f37f751a4c6299cf9cde87.PNG

Maurice

On 09/09/2015 13.56, LordBlick wrote:

My few thoughts on class D_PAD.
D_PAD class should be also replacement for VIAs(or VIA should be
subclass of
D_PAD instead TRACK) and only container of:
- so many as needed copper shapes(actual simple ones plus closed
berzier, poly
etc.) with LSETs each (no need to differ pads to SMD, STD, CONN, NPTH
etc. those
legacy attributes can be redesigned as some presets) NPTH easily not
contains
any shape. In addition, class MODULE(FOOTPRINT in future?) should include
information on whether an item is SMD or not.
- so many as needed drills. From few oval drills you can combine most of
needed
drill shapes. This has the advantage that you do not need to create an
additional program for CNC milling machines, because everything is
contained in
the drilling file.

Also probably there is no reason for just now to keep D_PAD as MODULE class
sub-element only(both canvases allows direct pad edit). Allowing free pad
placing gives more possibilities in designing boards. 1-pad footprints
are some
non-flexible, archaic way, which causes the necessity to modify the list of
BOM/positions items each time after generating.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] dxf: import 4 arcs

[easyw]

I just added

AddMenuItem( submenuImport, ID_GEN_IMPORT_DXF_FILE,
 _( "&DXF File (R12 best supported (no polylines), units mm)" ),

to my import menu in
menubar_pcbframe.cpp

That is an easy reminder each time I use import dxf function :)

On 09/09/2015 22.52, LordBlick wrote:

In response to a message written on 09.09.2015, 20:53, from easyw:

I still consider that a message to be added as warning in the import
dialog
saying "use R12 dxf version without polyline" would be useful

Maybe: „Polyline detected, try to explode/split it in LibreCAD/qcad and
save in R12 dxf version"

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] official web page

[easyw]

Hi Nick,

I pulled it.
Please feel free to let me know if you think I should change something.

Thank you
Maurice

On 09/09/2015 14.22, Nick Østergaard wrote:

Hi Easyw

I think they will fit fine on the 3d-viewer page. But we would need to
be able to distinguish your kicad stepup script and the VRML only
models. I think it could be explained under the video with a few
sentences. Feel free to make a pull request with that and the images.

2015-09-09 0:45 GMT+02:00 easyw :

Wayne,

thank you for your reply.

I already noticed that there is the link
   http://kicad-pcb.org/help/external-tools/

What I'm missing are the 2 images that I made with hackrf-one in kicad
3d-viewer and in MCAD Catia.
Those images were been included in old kicad web site.
http://confluence.kicad-pcb.org/download/attachments/589828/hackrf-one-stepup-kicad-3d-viewer.png
http://confluence.kicad-pcb.org/download/attachments/589828/hackrf-one-stepup-catia-assembly.png

I was thinking if you may consider to put those images also in the new web
site, just under the video of the 3d-viewer
http://kicad-pcb.org/discover/3dviewer/
where the web page says:
  'Export a realistic rendering of your project as a picture or a MCAD
hierarchical assembly.'

The two images show how Kicad can provide 3D data transfer from ECAD system
to the MCAD world.

Thank you again for your attention.

Maurice


On 08/09/2015 00.42, Wayne Stambaugh wrote:


Maurice,

It's already mentioned here: http://kicad-pcb.org/help/external-tools/.

Is this what your looking for or did you have something else in mind?

I haven't had a chance to use this yet but it sounds really interesting
so it will be near the top of my list of things to include during the
next development cycle.

Thanks,

Wayne

On 9/6/2015 6:17 PM, easyw wrote:


Hi Wayne,
regarding kicad StepUp script,
please have a look at this comment...

https://forum.kicad.info/t/kicad-stepup-new-exporter-for-3d-mcad-feedbacks-are-welcome/1048/13


I've improved the script and tested it quite heavily...
Please consider that the script does not touch any kicad file, it only
reads the data and generates the STEP model followings the data read.

I know that now you all are focused on the stable release, so I'm not
asking to add the script to kicad, but I'm thinking it would be nice and
may be useful to MCAD users, to add just a mention that it is possible
to convert kicad board in STEP through the script, as in the starter
guide that I have done in asciidoc.

May be under http://kicad-pcb.org/help/documentation/
just after 'IDF exporter' section
and/or in the manual.

Thank you for considering that,
Maurice


On 10/08/2015 16.02, Wayne Stambaugh wrote:


Maurice,

The 7z archive attachment in you original email looks find to me.  All
of the image files appear to be correct.  Before we include the step up
script documentation in the KiCad documentation we need to include
script in KiCad.  Would those who have tested this script, please
comment on whether or not it is ready to be added to the KiCad source.
It would be nice to have some step support for the stable release but
only if it's ready.

Cheers,

Wayne





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] HeeksCAD and HeeksCNC: Possible KiCad cousins?

[easyw]

Hi Jean-Paul,
for 3D modeling and CAD interchange please have a look at kicad StepUp 
script and FreeCAD...

http://sourceforge.net/projects/kicadstepup/
http://freecadweb.org/

you can get your pcb and parts in full colors and in STEP and VRML format

FreeCAD is free and heavily maintained and its support for STEP AP214 is 
highly reliable and it is based on OCE, which is used also from high-end 
MCAD products.
Heeks CAD is quite long time it is not updated and the STEP format is 
only AP203, not the latest, with colors, AP214


Maurice

On 21/09/2015 23.52, Jean-Paul Louis wrote:

I have no knowledge of Heeks products.

For my 3D needs when designing an enclosure, I use OpenSCAD that does 
everything I need and is free and maintained.

Just my $0.02,
Jean-Paul
AC9GH



On Sep 21, 2015, at 4:37 PM, Cirilo Bernardo  wrote:

When I checked HeeksCAD more than 2 years ago it was no longer maintained.
If anyone thinks it can be useful they can always write a plugin after the 3D
refactoring work is done. I don't really know what value it could be though; the
current thinking is that STEP integration will be done via a plugin and OCE.

- Cirilo


On Tue, Sep 22, 2015 at 5:54 AM, timofonic timofonic  
wrote:
Hello.

I found the following HeeksCAD and HeeksCNC projects: https://github.com/Heeks

What do you think about it? Could it become interesting to KiCad? They both use 
WxWidgets too.

Kind regards.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Crazyflie 2.0 quadcopter: 3D screenshots

[easyw]

It looks great!

but the best part is that I used all 3D models starting from STEP models 
(most of them generated in parametric way through my scripts) and for 
the motors, propellers and shield I just used the STEP/MCAD models that 
are included with the crazyflie-electronics project!


So starting from MCAD models, converting the 3d models with FreeCAD in 
VRML and using kicad Step Up script to generate the pcb assemblies, it 
is possible to have a native 3D pcb mechanical and electrical design!


ECAD meets MCAD also in kicad!

And the nice part is that you don't have to get a modified version of 
kicad to reach this result.
You need just to substitute Wings3D as 3D modeler with FreeCAD (or any 
MCAD STEP and VRML capable sw) and use kicad StepUp script (in 
conjunction with FreeCAD) to put the two worlds in contact!
It is just a simple command line command that launches the script to 
generate the pcb assemblies with the FreeCAD python scripting interface!


When you have the assemblies in STEP, MCAD world is in your hands! :)
and obviously ... everything is open source

On 23/09/2015 23.08, Mário Luzeiro wrote:

An inspiring work example!
How does it look if you add shadows?

From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
easyw [ea...@katamail.com]
Sent: 23 September 2015 21:26
To: KiCad Developers
Subject: [Kicad-developers] Crazyflie 2.0 quadcopter: 3D screenshots

Hi,

when I saw Crazyflie 2.0 quadcopter I said: that's really awsome! ...
but it was missing the 3D :)



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D model relative path dialog

[easyw]

It would be much better to substitute relative path with ${KIPRJMOD} to make 
the 3D model path portable with the project

On 27 September 2015 13:46:28 CEST, Simon Wells  wrote:
>When you add a 3d model for a footprint
>
>If the model file is inside the KISYS3DMOD directory then it is
>automatically made relative path
>If the model file is outside the KISYS3DMOD directory then you get a
>dialog
>as to whether it should
>be relative or not,
>
>If the model file is not in the KISYS3DMOD directory it seems like a
>bad
>idea to make the model
>have a relative path because if you move either the KISYS3DMOD
>directory or
>the model it
>requires changing the path, whereas if its absolute then you only need
>to
>update the path if you
>move the model file.
>
>I have created a branch with a patch to remove the dialog and if theres
>consensus then i will submit
>a merge request with it. (the branch is
>lp:~xzcvczx/kicad/relpath-dialog)
>
>
>
>
>___
>Mailing list: https://launchpad.net/~kicad-developers
>Post to : kicad-developers@lists.launchpad.net
>Unsubscribe : https://launchpad.net/~kicad-developers
>More help   : https://help.launchpad.net/ListHelp

-- 
Sent from Mobile___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D model relative path dialog

[easyw]

@nick:
that was me
http://www.mail-archive.com/kicad-developers%40lists.launchpad.net/msg15357.html

On 27/09/2015 18.56, Nick Østergaard wrote:

A suggestion I have have somewhere before is to use theese variables
in the path. So i you want ti projecet relaive use KIPRJMOD if you
want "global" models, use the KISYS3DMOD variable, and make it easy
for the user to enter even with browsing.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Packaging the python footprint wizards for the release

[easyw]

Hi,
there is also a patch for wizard plugins to make the QFN/QFP with 
exposed pad and paste pads...

http://www.mail-archive.com/kicad-developers%40lists.launchpad.net/msg15109.html

at the moment has not been committed...


On 29/09/2015 17.59, Bernhard Stegmaier wrote:

Thanks a lot, found it now!
And I don’t believe it… it even seems to work without any problems (well, just 
created the default QFP and changed pads from oval to rectangular…).

I’ll post a patch for OS X in the next couple of days to make paths 
consistently pointing to *only* the one “scripting/plugins” inside the 
application bundle where the footprint plugins are delivered right now.


Regards,
Bernhard


On 29 Sep 2015, at 17:45, Nick Østergaard  wrote:

It is not well documented, I guess partly becaue the plugins was never
found on a default installation.

But see http://docs.kicad-pcb.org/en/images/Modedit_top_toolbar.png
this is in the footprint editor.

It is the 7th icon from the left. The chip package with a small paper
on it. Although the icon has changed to a star and a some tools.

2015-09-29 17:40 GMT+02:00 Bernhard Stegmaier :



On 29 Sep 2015, at 10:49, Brian Sidebotham  wrote:

See the comments about stdout not being open for python:
https://github.com/KiCad/kicad-source-mirror/blob/master/scripting/kicadplugins.i#L43

Just open a new file to direct stdout to temporarily while you're
debugging/testing:
http://stackoverflow.com/questions/4675728/redirect-stdout-to-a-file-in-python#answer-4675744

Best Regards,

Brian.


Thanks for the tip… worked.

I need some help, though:
I changed the paths and I verified that all of the python wizards/plugins are 
loaded fine.
All paths are correct, python seems to load the plugins via __import__ just 
fine (there seems to be a valid object when doing a print on it), no other 
errors.
But, I just don’t find those plugins anywhere in pcbnew… :(

Maybe I am just blind, but where are they supposed to be?
If they should appear in the menu, where are the menu entries created?

I don’t know if related, I did not notice that before:
When opening the Tools menu I always get an OS X wxWidgets assertion about 
invalid checked/unchecked menu items which obviously are created wrong (at 
least for OS X)… maybe those are the ones I am missing?


Regards,
Bernhard
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Packaging the python footprint wizards for the release

[easyw]

I did the same solution with thermal pads at the end of August
http://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg15033.html
but the problem with thermal pads is that python APIs do not let you 
have pads without Front Silk and Front and Bottom Solder Mask

that is not acceptable in the footprint...
the only solution at the moment is a workaround, saving the module and 
editing manually the pads...
so then I made the simpler version of QFN/QFP with only exposed pad and 
paste pads...



On 29/09/2015 21.26, nats wrote:

Hi,
I did a code for QFN handling via/thermal pad/solderpaste.
I think inductiveload (on IRC) merged it cleanly with the QFP generator.
I post it here, maybe there are some interesting part in it.

https://github.com/natsfr/kicad-components/blob/master/python_plugins/qfn_wizard.py


Le 29/09/2015 18:30, easyw a écrit :

Hi,
there is also a patch for wizard plugins to make the QFN/QFP with
exposed pad and paste pads...
http://www.mail-archive.com/kicad-developers%40lists.launchpad.net/msg15109.html


at the moment has not been committed...


On 29/09/2015 17.59, Bernhard Stegmaier wrote:

Thanks a lot, found it now!
And I don’t believe it… it even seems to work without any problems
(well, just created the default QFP and changed pads from oval to
rectangular…).

I’ll post a patch for OS X in the next couple of days to make paths
consistently pointing to *only* the one “scripting/plugins” inside
the application bundle where the footprint plugins are delivered
right now.


Regards,
Bernhard


On 29 Sep 2015, at 17:45, Nick Østergaard  wrote:

It is not well documented, I guess partly becaue the plugins was never
found on a default installation.

But see http://docs.kicad-pcb.org/en/images/Modedit_top_toolbar.png
this is in the footprint editor.

It is the 7th icon from the left. The chip package with a small paper
on it. Although the icon has changed to a star and a some tools.

2015-09-29 17:40 GMT+02:00 Bernhard Stegmaier
:



On 29 Sep 2015, at 10:49, Brian Sidebotham
 wrote:

See the comments about stdout not being open for python:
https://github.com/KiCad/kicad-source-mirror/blob/master/scripting/kicadplugins.i#L43


Just open a new file to direct stdout to temporarily while you're
debugging/testing:
http://stackoverflow.com/questions/4675728/redirect-stdout-to-a-file-in-python#answer-4675744


Best Regards,

Brian.


Thanks for the tip… worked.

I need some help, though:
I changed the paths and I verified that all of the python
wizards/plugins are loaded fine.
All paths are correct, python seems to load the plugins via
__import__ just fine (there seems to be a valid object when doing a
print on it), no other errors.
But, I just don’t find those plugins anywhere in pcbnew… :(

Maybe I am just blind, but where are they supposed to be?
If they should appear in the menu, where are the menu entries created?

I don’t know if related, I did not notice that before:
When opening the Tools menu I always get an OS X wxWidgets
assertion about invalid checked/unchecked menu items which
obviously are created wrong (at least for OS X)… maybe those are
the ones I am missing?


Regards,
Bernhard
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Packaging the python footprint wizards for the release

[easyw]

Hi Wayne,
please reconsider to leave the python wizard installed
The wizard is giving:
BGA, DIP/SIP, QFP, Circular array and BarCode just out of the box.

May be they are improvable (exposed pad, thermal vias etc), but at this 
state they are fully usable (without any crash or prob) and much faster 
then standard footprint editor.
Moreover, if you do not include them you get a wizard button in pcbnew 
footprint editor for nothing...




On 30/09/2015 14.30, Wayne Stambaugh wrote:

Thanks for the update.  I'll leave the python examples uninstalled until
we can confirm that they are not broken.  I don't think it's all that
important for the stable release.  Users can always look at the python
plugins to get an idea of how the python scripting works.

On 9/30/2015 3:59 AM, Miguel Angel Ajo wrote:

I agree with JP here, QFP and QFN may be separate wizards. If there are
common parts, feel free to use inheritance from a common base to reuse
code.

About naming: footprint generators sound better, or whatever, at that
time I was following an industry leader on naming it..., but I agree
footprint generator is more clear for the task.

About including our scripting examples, I wouldn't, those are not tested
with the current codebase, and likely to be broken because of C++
interface changes.

Sorry for my slow response,
best regards,
Miguel Ángel.


jp charras wrote:

Le 30/09/2015 01:25, Wayne Stambaugh a écrit :

JP,

Your name is on the initial commit for qfn_wizard.py.  I don't have time
to figure out these patches should be included.  Do these patches make
sense?  Let me know so I can make a decision on whether or not to commit
them.

Thanks,

Wayne



These patches make sense, I used them to fix bugs in our footprint
wizard dialog issues, and issues in some pythons scripts (mainly usage
of print command which created python exceptions when stdout was never
read, especially on Windows).

But do not commit them. Reasons:
- I am thinking the wizard to create a QFN should be an other wizard
than the QFN wizard.
The thermal pad needs many parameters, useless for a QFN without thermal
pad.
- The wizard to create a QFN with thermal pad needs refinements, before
being committed

I'll have a look at that later.




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Call for help, no programming experience required.

[easyw]

and using FreeCAD VRML models (instead of Wings3D models) you have also 
MCAD models to be used for the MCAD exporting/viewing


here there is a video of the FreeCAD VRML models and FreeCAD STEP models 
that shows how KiCad is ready for MCAD world! (just now with the stable 
release)

https://www.youtube.com/watch?v=XmNGdqkKbpM

I've done a self contained project that displays the 3d-viewer in kicad 
as the 3d MCAD view in FreeCAD or whatever MCAD software you want to use :)


On 01/10/2015 22.24, Wayne Stambaugh wrote:

The only down side is that as improvements are made to the 3D models,
they would not be visible.  I hope at some point in the future our 3D
models could be improved (some of material properties are very wrong)
now that FreeCAD exports vrml files that the 3D viewer can use.  I would
think the demos should track the latest and greatest to show case
KiCad's capabilities.

The "everything" project archive sounds interesting but it should be
discussed outside this bug report.

On 10/1/2015 4:15 PM, Chris Pavlina wrote:

It's a right shame we don't have any standalone project archive format
that holds *everything*. That would be *very* useful for this sort of
thing, as well as just generally making sure projects can always be opened.

I wonder if there is any developer interest in that besides me. It's
definitely on my list of things I'd like to work on post-release, but I
don't have much time lately...

On Oct 1, 2015 3:52 PM, "nnn" mailto:nnn4...@o2.pl>> wrote:

 Why not to add 3d files (from some old revision of library) to
 projects folder and use paths relative to KIPRJMOD? If demos will
 refer to some special revision of library with 3d models they will
 break each time the models are moved or renamed.


 W dniu 01.10.2015 o 16:20, Wayne Stambaugh pisze:

 I just committed a fix for broken 3D model link in the interf_u demo
 https://bugs.launchpad.net/kicad/+bug/1500956.  While I was at it, I
 looked at the rest of the demos that have board files and they are
 broken (one partially) as well.  Here is an opportunity for
 someone to
 help out the project and no programming experience is require.
 All you
 need to know is how to associate 3D models with footprints in
 Pcbnew and
 how to use bzr to create branch and a patch (well documented many
 places).  If someone has time to do this before the stable
 release, it
 really would be nice if our demos showed off the 3D models.

 Thanks,

 Wayne

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp



 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Call for help, no programming experience required.

[easyw]

I would prefer that the orientation and scaling match footprint so the
user doesn't have to change anything by default.  In other words, the
scaling is always 1 and the offsets and rotation angles are always 0.


that is exactly what I do with my 3D models in VRML and STEP for kicad 
StepUp

the lib of 3D parametric models is done in that way:
https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator


On 02/10/2015 00.23, Wayne Stambaugh wrote:

On 10/1/2015 5:03 PM, Cirilo Bernardo wrote:

I think in general VRML models suffer from a somewhat random (0,0,0)
reference
and even the orientation is typically 1 of 4 common orientations.  This
is due in
part from the habits of whoever created the model and in part from the
modeling
software used. We will see more such problems when we have the capability to
use more types of models.  The only scheme I can think of so far which may
help with this issue is to have an optional file alongside each 3D model
file to
provide information needed to put the model into a nominal position. For
models
not at (0,0,0) such a scheme would also save people from typing the same
information into the VRML scale/rotation/translation box all the time.
The down
sides of course are these extra files and the fact that if 2 files have
the same
name but different (0,0,0) someone will have to remember to edit the
positioning
file. The file is not intended to replace the scale/rotation/translation
within KiCad
but to transparently add to it. The model manager can make this happen
without
additional user interaction. Unfortunately this scheme can only help to
create the
nominal position - whatever a user decides that must be. It doesn't help
at all
if footprints change their (0,0) reference between projects, which is
the case for
the newer THT footprints in the KiCad libraries.

Changes so far which can cause problems:
schematic symbols:
+ many changed size and the location of connection points
+ Diodes were made consistent so K is always Pin 1 (which I think should
have
been the case even for THT since K is the marked pin)
+ Orientations may have changed

footprints:
+ (0,0) reference for THT components has changed; I'm not familiar at
all with
the orientation of SMT footprints so I can't say if they've changed,
but some
rules were put in place to ensure a consistent orientation. I suspect
the (0,0)
position remains the 'center of body' since that's what's required by
placing
machines, but I haven't been following the changes.


Has anyone checked if the position files are correct for THT footprints
with the pin 1 reference points at 0,0?  If this breaks user's position
files used for pick & place, this is *really* bad and I would consider
this a potential stable release blocker.  Someone needs to confirm this
so we can make a decision.


+ Orientation has changed for many THT components

VRML models:
+ many have changed orientation
+ many have changed (0,0,0)


I would prefer that the orientation and scaling match footprint so the
user doesn't have to change anything by default.  In other words, the
scaling is always 1 and the offsets and rotation angles are always 0.



We should definitely provide big red warning signs for users telling them of
the potential problems and reminding them that they should archive all
existing projects before switching if they make use of the kicad libraries.

- Cirilo


On Fri, Oct 2, 2015 at 6:24 AM, Wayne Stambaugh mailto:stambau...@gmail.com>> wrote:

 The only down side is that as improvements are made to the 3D models,
 they would not be visible.  I hope at some point in the future our 3D
 models could be improved (some of material properties are very wrong)
 now that FreeCAD exports vrml files that the 3D viewer can use.  I would
 think the demos should track the latest and greatest to show case
 KiCad's capabilities.

 The "everything" project archive sounds interesting but it should be
 discussed outside this bug report.

 On 10/1/2015 4:15 PM, Chris Pavlina wrote:
 > It's a right shame we don't have any standalone project archive format
 > that holds *everything*. That would be *very* useful for this sort of
 > thing, as well as just generally making sure projects can always be 
opened.
 >
 > I wonder if there is any developer interest in that besides me. It's
 > definitely on my list of things I'd like to work on post-release, but I
 > don't have much time lately...
 >
 > On Oct 1, 2015 3:52 PM, "nnn" mailto:nnn4...@o2.pl> 
<mailto:nnn4...@o2.pl
 <mailto:nnn4...@o2.pl>>> wrote:
 >
 > Why not to add 3d files (from some old revision of library) to
 > projects folder and use paths relative to KIPRJMOD? If demos will
 >

Re: [Kicad-developers] 3D refactor update

[easyw]

Hi Cirilo,

I'm not very familiar with building kicad in linux... (I do my most 
testing in windows)
could you please post the commands to build only the test program 
'test3dmm' after downloading your branch?


I think it would be useful to add the ability to switch on and off some 
3D models (similar to what it can be done in pcbnew for layers) to e.g. 
display or not mechanical enclosures directly in 3d-viewer...


something similar to what I do with virtual model in my branch
as in the mailing list message
https://lists.launchpad.net/kicad-developers/msg18079.html
it is possible to show or not models that are marked as virtual, so to 
enhance mechanical collaboration.

https://lists.launchpad.net/kicad-developers/pngmiJa_et4ei.png
https://lists.launchpad.net/kicad-developers/pngBxSJOlsdSm.png

thanks
Maurice

On 05/10/2015 09.27, Cirilo Bernardo wrote:

The 3D refactor branch now has some (very bare) file selector code. The
features
which testers/devs can play with so far include:

+ quickly change the file selector's directory using a drop-down list:
this should
make browsing for files less painful

+ select the file filter for the types of model you're interested in;
the dummy
plugin pretends to support VRML, X3D, IDF, IGES, and STEP so those are
the options testers would see at the moment in addition to the All Files
wildcard.

  + edit the 3D model search path list from within the file selector

Testers may notice a large blank space in the 3D file selector's window;
this
space will eventually be filled with a preview of the model being browsed if
a plugin supports rendering of the model. The large bottom box on this page
will also eventually feature in the '3D Model Settings' tab within
pcbnew (minus
the file selector menus) thus providing a consistent interface to adjust the
offset/rotation/scale of models.

Any feedback would be appreciated. Keep in mind that at the moment this only
serves to demonstrate what things might look like in the future; do not
expect
any actual interaction with any other part of kicad at this stage.

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[easyw]

Hi Cirilo,

thanks for the info
... I will try to build test3dmm only program...

If I can get it in linux, then I will try to build it also in win, and 
if I succeed I will give you some feedback and tips for mswin :)


Maurice


On 08/10/2015 12.18, Cirilo Bernardo wrote:

Hi Maurice,

  The instructions are in the README file in the 3dv directory. You will
need a build environment which can build KiCad though and I know nothing
about how to set that up on MSWin, which is why I ask if there are any
devs who can help on OSX and MSWin. :)  I'm only working on a refactor
to allow better management of the models and also to make it easier to
add exporters and plugins to support more model formats. Mario Luzeiro
is working more on 3DViewer and the renderer.

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[easyw]

Hi Cirilo,
here some feedback in mswin:

first I had an error on building with dlfcn.h
then I solved adding dlfcn.c and dlfcn.h from
https://github.com/dlfcn-win32/dlfcn-win32
and changing
#include 
to
#include "dlfcn.h"

but then I have this file missing:
#include 

and I cannot find a correspondent in mswin...
may be someone of the dev could help?

thank you
Maurice

On 08/10/2015 12.31, easyw wrote:

Hi Cirilo,

thanks for the info
... I will try to build test3dmm only program...

If I can get it in linux, then I will try to build it also in win, and
if I succeed I will give you some feedback and tips for mswin :)

Maurice


On 08/10/2015 12.18, Cirilo Bernardo wrote:

Hi Maurice,

  The instructions are in the README file in the 3dv directory. You will
need a build environment which can build KiCad though and I know nothing
about how to set that up on MSWin, which is why I ask if there are any
devs who can help on OSX and MSWin. :)  I'm only working on a refactor
to allow better management of the models and also to make it easier to
add exporters and plugins to support more model formats. Mario Luzeiro
is working more on 3DViewer and the renderer.

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp