Maybe it can be implemented as not a new library format, but through
enhancements to the existing workflow and new symbol format.
If there was an ability to
a) filter symbols in eeschema that have a valid footprint that can be found
in the footprint library.
b) run a dfm check that flags symbols
One thing I liked from Eagle was the list of sheets as thumbnails to
allow for visual recognition.
Regards
Russell Oliver
On Sat, 4 May 2019 at 10:20, Andrew Lutsenko wrote:
>
> Hi Brian,
>
> There already is an easier way to navigate sheets than what you describe:
>
ation between SKIDL and KiCad
> > once the Python API is more
> > stable and it is possible to interact with the schematic using Python).
>
> This is probably the best course of action. Once the schematic and
> symbol library code is swigged out to Python, integrating functiona
] https://www.youtube.com/watch?v=WErQYI2A36M
Regards
Russell Oliver
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https
/install.nsi#L647
Regards
Russell Oliver
On Tue, 12 Mar 2019 at 21:30, Nick Østergaard wrote:
>
> https://github.com/KiCad/kicad-winbuilder/issues/53#issuecomment-337167911
>
> tir. 12. mar. 2019 11.07 skrev Russell Oliver :
>>
>> To cut down the download size, can there be
To cut down the download size, can there be a nightly package built
that doesn't contain the library, module and 3d files? just enough to
overwrite the program files.
Regards
Russell Oliver
On Mon, 11 Mar 2019 at 06:00, Mark Roszko wrote:
>
> AFAI CERN has private cluster using Ceph th
I don't know if this approach is what is being proposed but the way I
envisage it working is to have the ability to set a list of default fields
at a project level, which you could also set as your default for new
projects. Not necessarily adding to the list of default fields currently
hard coded
Updated patch, which also should fix rotations for rectangles. This should
be a complete fix for the reported bug.
On Sat, Mar 31, 2018 at 11:07 PM Russell Oliver <roliver8...@gmail.com>
wrote:
> No I won't have time to.
>
> There is still the issue of Eagle rectangles with a r
was unclear. The change in the LSET makes sense. But it looks like
>> you are not setting the solderpaste margin when the solderpaste layer is
>> enabled. I think you need to handle both the case where the paste is
>> enabled and where it is disabled.
>>
>> -S
>
Will the new schematic file format embed subsheets? Or keep them in
separate files on disk?
On Thu, 29 Mar 2018 15:44 Andy Peters, wrote:
>
>
> On Mar 28, 2018, at 7:34 PM, Seth Hillbrand
> wrote:
>
> Hi All-
>
> I'm working on a bug in renaming
ever, currently, if there is no e.cream setting,
> the local solderpaste margin gets set. In your patch, if the setting is
> missing, that doesn't happen.
>
> Is this your intention?
>
> -S
>
> 2018-03-27 5:06 GMT-07:00 Russell Oliver <roliver8...@gmail.com>:
>
>> This fixes the
This fixes the issue where the cream setting is ignored when setting the
layer set for the pad, but the bug report also mentions that the rotation
for rectangles are ignored during import. They rectangle is niavely
converted to a polygon.
Hi All,
As a follow up to the CvPCB save button discussion, I recently got a some
feedback from my friend who is a daily user of Kicad. In his telling he
recently managed to design a circuit, export the netlist, design and the
board and export gerbers and exit kicad without saving the schematic
d-Edit version only, right? I don’t think we allow editing of
> pins at all in the schematic, do we?
>
> On 21 Mar 2018, at 21:48, Russell Oliver <roliver8...@gmail.com> wrote:
>
> Just thinking that another tab showing the list of pins and their
> properties would be a
Just thinking that another tab showing the list of pins and their
properties would be a good addition to this also. If you can copy and paste
into the grid
On Wed, 21 Mar 2018 23:34 Wayne Stambaugh, wrote:
> Jeff,
>
> Looks good to me. I prefer the in place editing so go
sically a dialog of eeschema rather
> than a separate program, so I guess it makes sense to write changes
> immediately to the in-memory schematic, and mark it as unsaved for the user
> to consciously hit the save button later if desired.
>
> -Jon
>
> On Tue, Mar 20, 2018 at 1:52
I second Bernhard's comments.
I think it shouldn't seem like a separate program, just another dialog of
eeschema that takes the what you see is what you get approach.
As long as the footprint references are valid the schematic should be
updated when the dialog is closed, and marked modified if
> > and the values.
> > If you have a property named "TOLERANCE" with value "10%", you can check
> the value box and get a
> > label saying "10%",
> > or check both boxes to get a label saying "TOLERANCE=10%"
> >
> > -Jon
>
n Sun, Mar 11, 2018 at 11:56 AM, Nick Østergaard <oe.n...@gmail.com>
> wrote:
>
>> Den 8. mar. 2018 22.39 skrev "Russell Oliver" <roliver8...@gmail.com>:
>>
>> As a follow up to the road map discussion I saw a forum post asking if it
>> was possible to
hich seamlessly creates a "linked" text object as you describe when you
> choose "show". This is a really nice system.
>
> -Jon
>
>
> On Thu, Mar 8, 2018, 16:39 Russell Oliver <roliver8...@gmail.com> wrote:
>
>> As a follow up to the road map
>From what I am reading John your call for acting on the files on disk
instead of memory is a call for a clear demarcation of actions that need to
be irrevocable and require the project data to be consistent.
In my opinion this doesn't necessarily require separate programs, just
consistent checks
Forgive my ignorance but why would storing the clearance for each track
segment (if required to by design intent) conflict with a sophisticated
design rule management system?
As a general approach shouldn't KiCad allow freedom of design when the
intention of the designer is clear?
Russell
On
2018, at 11:49 AM, Russell Oliver <roliver8...@gmail.com>
> wrote:
> >
> > In terms of automatically arranging components a force directed graph
> algorithm may work quite nicely, especially if the algorithm is seeded with
> the layout of components on the schematic.
>
n ERCs to make sure you don't have missing bypass caps, DRC to make
> sure they are close enough to the power pin in the layout, etc)
>
>
>
> On Mon, Mar 5, 2018 at 1:49 PM, Russell Oliver <roliver8...@gmail.com>
> wrote:
>
>> In terms of automatically arranging compo
In terms of automatically arranging components a force directed graph
algorithm may work quite nicely, especially if the algorithm is seeded with
the layout of components on the schematic.
A simplistic version would be to just arrange components on board sheet as
to their position on the
roblems reported. I am going to merge the branch during the weekend.
>
> Cheers,
> Orson
>
> 1.
> https://code.launchpad.net/~orsonmmz/kicad/+git/kicad/+
> ref/eagle_import_fixes
>
> On 02/26/2018 12:10 PM, Russell Oliver wrote:
> > Awesome,
> >
> > I'm excite
changes, I have almost finished the refactor to use
> KiWay mail. I will test the patches a bit and given no extra issues
> appear, I will push them to the master branch.
>
> Regards,
> Orson
>
> On 02/25/2018 10:30 PM, Russell Oliver wrote:
> > Just wondering what approach
Just wondering what approach we are going to use for v5? Global labels or
my latest matching algorithm?
Kind Regards
Russell
On 25 Feb 2018 08:43, "Russell Oliver" <roliver8...@gmail.com> wrote:
> Hi Orson,
>
> I looked at the Kicad project from the and I don't see
, which should only occur when there are multiple sheets in
the original Eagle schematic.
Russell
On Tue, Feb 20, 2018 at 9:55 AM Maciej Suminski <maciej.sumin...@cern.ch>
wrote:
> Hi Russell,
>
> On 02/19/2018 08:25 PM, Russell Oliver wrote:
> > Hi Orson,
> >
&g
more thing I should fix.
>
> To sum up: I am going to merge your patch and apply necessary
> KIWAY_PLAYER interface fixes. There are still two issues to address:
> - global labels in the Arduino test project
> - unassigned timestamps in pcbnew (I think for multisheet schematics)
>
>
like your input
> before we merge this just in case you see something that I am missing.
>
> Russell, if we decide to merge this patch please fix you coding policy
> violations. You are using K curly brace placement.
>
> On 02/18/2018 06:48 AM, Russell Oliver wrote:
> > A
f
> > imported schematics.
> >
> > I am not sure if netlist updater is able to link a symbol and its
> > corresponding footprint when sheetpath is not complete, but if that is
> > the case then your other idea could be a better solution here.
> >
> > Best regards,
a symbol and its
corresponding footprint when sheetpath is not complete, but if that is
the case then your other idea could be a better solution here.
Best regards,
Orson
On 02/17/2018 12:18 AM, Russell Oliver wrote:
> Hi all,
>
> Sorry I didn't get to it sooner. Been busy at a new job.
>
>
tlemen,
>>>
>>> What is the status of this bug fix? I know there was some discussion
>>> about this patch. Do we have path forward on this yet? I would like to
>>> get this into rc1 if possible.
>>>
>>> Thanks,
>>>
>>> Wayne
&g
Please find the attached patch for this issue.
On Tue, Feb 13, 2018 at 2:34 AM Maciej Sumiński <maciej.sumin...@cern.ch>
wrote:
> Hi Russell,
>
> On 02/11/2018 05:41 AM, Russell Oliver wrote:
> > Hi All,
> >
> > I've discovered the cause of a problem when importi
Updated patch.
On Tue, Feb 13, 2018 at 9:41 AM Wayne Stambaugh <stambau...@gmail.com>
wrote:
> On 02/12/2018 05:21 PM, Russell Oliver wrote:
> > So a file created on disk in the project folder that is then added as a
> > path in the project specificatio
>
> Wayne, what do you think? Is it acceptable that we add a reserved
> keyword "empty" to indicate an empty worksheet layout for a project? If
> so, we need to implement it both for pcbnew and eeschema.
>
> Regards,
> Orson
>
> On 02/11/2018 12:24 AM, Russell Oliver
Hi All,
I've discovered the cause of a problem when importing Eagle Projects and
getting the schematic and boards synced.
Currently when importing an Eagle schematic, labels for nets that are only
found one Eagle sheet are imported as local KiCad labels. This preserves
the visual design of the
This fixes an issue i found during some testing. Small labels are added to
connect segments sharing the same net name in the eagle schematic. These
were placed in the middle of a wire, but other wires may cross at this
point without being connected by a junction. When the netlist is created
the
he past. We recently fixed a print bug where a zero
> diameter circle was causing pages not to print.
>
> On 2/7/2018 7:45 AM, Russell Oliver wrote:
> > Hi Orson,
> >
> > I'm completely fine with any simplifications and style changes.
> >
> > With regards to t
n remove it to avoid confusion.
>
> Regards,
> Orson
>
> On 02/03/2018 01:27 AM, Russell Oliver wrote:
> > Attached is a patch that adds an empty layout using the same method as
> the
> > SetDefaultLayout function, which is then called by the Eagle schematic
> > p
.
Kind Regards
Russell
On 6 Feb 2018 03:18, "jp charras" <jp.char...@wanadoo.fr> wrote:
Le 05/02/2018 à 06:07, Russell Oliver a écrit :
> Copies project files into a new directory with the project name replaced
in each file name if
> preset. Uses the same set of extensions
Copies project files into a new directory with the project name replaced in
each file name if preset. Uses the same set of extensions as the archive
project feature to filter the files.
0001-Add-a-menu-item-to-save-a-project-under-a-new-name.patch
Description: Binary data
Fixes the bug by removing a line that deleted the imported footprint
templates every time the plugin init function is called.
0001-Fix-empty-footprints-when-using-Eagle-libraries.patch
Description: Binary data
___
Mailing list:
Attached is a patch that adds an empty layout using the same method as the
SetDefaultLayout function, which is then called by the Eagle schematic
plugin to leave only the imported frame visible.
https://bugs.launchpad.net/kicad/+bug/1729722
Kind Regards
Russell
Hi All,
Just a query for Michael: can your parser be modified to include references
to dialog variables, ie while writing an expression for y axis position,
using the label posx or something would refer to the value currently within
that text box?
Kind Regards
Russell
On 24 Nov 2017 06:54, "jp
Hi Lachlan,
I was the main developer of the Eagle schematic import plugin and I know
the layout of the Pcbnew Eagle import code pretty well. So If you can
describe further the errors you are seeing that would be great, even if its
just links to the original Eagle files and screen shots of the
Thanks everyone for your input. I'll revert patch and move to creating the
IO_ERROR exceptions for unimportable items.
As an aside, is there a particular reason why polygons are not editable in
the footprint editor? Even if they were restricted to non-copper?
Regards
Russell
On Tue, Sep 26,
Hi Orson,
Please find attached a small patch that handles multiple pad connections.
Regards
Russell
On Sat, Sep 23, 2017 at 11:03 AM Russell Oliver <roliver8...@gmail.com>
wrote:
> Hi,
>
> Maciej : I had a look at the rounding issue and I couldn't find an
> obvious reason
Hi,
Maciej : I had a look at the rounding issue and I couldn't find an obvious
reason for it.
It might be due to the translation of all components to the middle of the
sheet, but I round that off to the nearest 100mil.
I'll take a look at that pin mapping problem, I think your solution of
com>
wrote:
> Russell,
>
> Is this patch still valid now that JP merged his custom pad work or does
> it need to be reworked to support custom pads? I would like to get all
> of the Eagle changes into master for the stable 5 branch.
>
> Thanks,
>
> Wayne
>
> On
anded in 4.0.x yet (if
> it ever will…).
> We have to use a custom wxWidgets for MacOS anyway, so this shouldn’t be a
> reason for not using the selector.
>
>
> Regards,
> Bernhard
>
> > On 14. Sep 2017, at 14:05, jp charras <jp.char...@wanadoo.fr> wrote:
> >
>
Hi All,
Below is a link to the patch hosted on Dropbox.
https://www.dropbox.com/s/ig6mp9os0bzyev7/eagle-import.patch?dl=0
Kind Regards
Russell Oliver
On Wed, Sep 13, 2017 at 11:09 PM Kaspar Emanuel <kaspar.eman...@gmail.com>
wrote:
> Hi Russ,
>
> wouldn't mind giving this a go
nd giving this a go but I don't see any attachments.
>
> Cheers,
>
> Kaspar
>
>
> On 13 September 2017 at 01:48, Russell Oliver <roliver8...@gmail.com>
> wrote:
>
>> Hello Everyone,
>>
>> Please find attached a combined patch set which adds Eagle s
Montoro for the initial plugin layout and Orson
for his guidance and code review over the past few months.
Kind Regards
Russell Oliver
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe
in PosX field: "-c1/2 "
> and PosY: "-1.5*e" in order to place the first pad.
>
> - Michael
>
>
> On Thu, Aug 31, 2017 at 3:58 PM, Tomasz Wlostowski <
> tomasz.wlostow...@cern.ch> wrote:
>
>> On 31.08.2017 15:27, Russell Oliver wrote:
>&
Thanks everyone for your input.
First off, I too think it will get the most usage in the footprint editor,
specifically when calculating the position and size of a pad from cryptic
datasheet dimensions. I chose the schematic value entry dialog simply
because its a small target. But even having
>
>
> > The second is matching the Eagle tValues and bValues layers with the
> > kicad Fabrication layers instead of the silkscreen layers, to match
> > current standard Kicad practive for component values.
>
> I would think users will expect any object to import to the same layer
> that they are
Hi All,
Attached is a patch that does some minor code changes in the PcbNew Eagle
plugin which solves a few issues I encountered while testing the eagle
schematic plugin and project import feature.
The first was that some footprints such as Wifi trace antennas use graphic
lines to form the
Hi Liyoubu,
Currently the process for accepting contributions is through patches sent
to the mailing list for review.
More information can be found at
http://kicad-pcb.org/contribute/developers/#_submitting_patches
Kind Regards
Russell
On 13 Aug 2017 11:05, "liyoubdu" wrote:
Hi Heikki,
Do you know which commit or release that you started developing the
features from? I'll see if i can recreate the necessary git history.
Regards
Russell
On Sat, May 27, 2017 at 4:34 PM Heikki Pulkkinen wrote:
> And that menu structure is what it is. It is there
Hi Tomasz,
Attached is an updated patch to align more with the coding policy.
Regards
Russell
Regards
Russell Oliver
On 29 April 2017 at 02:45, Russell Oliver <roliver8...@gmail.com> wrote:
> Hi Tom,
>
> I'll check it against the code style rules to see what
. Going
forward is the use of the VECTOR2I type preferred for coordinates?
Regards
Russell
On Sat, Apr 29, 2017 at 2:33 AM Tomasz Wlostowski <tomasz.wlostow...@cern.ch>
wrote:
> On 28.04.2017 18:26, Russell Oliver wrote:
> > Hello All,
> >
> > For the purpose of accuratel
Hi All,
I was looking through the roadmap for Kicad 5 and saw that work is being
done on the new schematic format. I was wondering if the draft
specification is available anywhere and whether I could assist in
developing it.
Regards
Russell Oliver
Hi all,
As a crazy thought related to having the board capture orphan pads under an
parent footprint, conceptually what about a pcb being represented as a
hierarchy of footprints.
>From what I understand most elements of a board can be included in
footprints except for tracks. If tracks could
65 matches
Mail list logo