On 3/6/2018 4:18 PM, Robbert Lagerweij wrote:
> Op 5-3-2018 om 18:49 schreef Wayne Stambaugh:
>> All kidding aside, I was told by a very highly skilled board designer
>> not to waste our time with auto-routers because no one actually uses
>> them except for the simplest designs with lots of free bo
Op 5-3-2018 om 18:49 schreef Wayne Stambaugh:
> All kidding aside, I was told by a very highly skilled board designer
> not to waste our time with auto-routers because no one actually uses
> them except for the simplest designs with lots of free board space and
> few or no routing restrictions. Th
There is an option in pcbnew to delete all tracks already...
2018-03-06 9:13 GMT+01:00 Ingo Kletti :
>
> Am 05.03.2018 um 19:07 schrieb Andy Peters:
>
>> I'm guessing auto-routers appeal to hobbyists rather than professionals.
>>>
>>
>> How many questions on forums do you see from hobbyists askin
Am 06.03.2018, 09:13 Uhr, schrieb Ingo Kletti :
Since they also ignored all advice and documentation on design rules and
component placement, these layouts are a complete mess.
Apparently, many students believe that computers who beat chess world champions
are also able to autoroute and even
Am 05.03.2018 um 19:07 schrieb Andy Peters:
I'm guessing auto-routers appeal to hobbyists rather than professionals.
How many questions on forums do you see from hobbyists asking about how to
autoroute, or wondering if the results from the autorouter are good?
A great deal of my day job is
I didn't mean to infer that the final location of a part would be
determined by the schematic, just the initial placement of parts in pcbnew
when the netlist is first read. Similar to the spread out all components
tool. A starting point.
I can also imagine a tool that would try to minimise the ove
> On Mar 5, 2018, at 11:49 AM, Russell Oliver 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.
>
> A simplistic version would be to just
So it is already implemented in the legacy canvas:
-Global spread and place -> Spread out All Footprints
-Autoroute -> Automatically Route All Footprints
Well, two clicks instead one just one.
I'm with Wayne: no effort should be added to autorouting as there are
plenty of features to sort out.
The "spring" constants in a force directed graph algorithm could be set by
a user given priority or even by the length of schematic wires.
On Tue, 6 Mar 2018 05:53 Jon Evans, wrote:
> In many commercial tools you can use some or another feature to mark up
> the design at the schematic level with
In many commercial tools you can use some or another feature to mark up the
design at the schematic level with what components "go together".
Then that information is used during PCB placement, the first-pass arrange
of components when you start designing a board can place those components
together
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 schemati
> On Mar 5, 2018, at 10:49 AM, Wayne Stambaugh wrote:
>
> I was thinking one level of abstraction higher where I just input my
> design requirements and it spits out a schematic, full simulation to
> match the design requirements, and a completed board layout. That would
> make my job a *lot*
One thing that may be of more interest to board designers is an
automatic footprint placement algorithm that minimizes the number of air
wire crossings. Not so much to place the footprints but to orient them.
A few years ago someone proposed using a chemical reaction stability
algorithm where the
Yes, I have also heard that from my hard-core board design colleagues. No
one uses auto-routers anymore, they instead use interactive routers that
have gotten very good lately.
We should continue to push the KiCad interactive (PNS) router to add
capabilities (multi-net routing, via array styles,
I was thinking one level of abstraction higher where I just input my
design requirements and it spits out a schematic, full simulation to
match the design requirements, and a completed board layout. That would
make my job a *lot* easier. ;)
All kidding aside, I was told by a very highly skilled b
Ha!
Sounds like a job for Alpha Zero to me.
-S
2018-03-05 9:09 GMT-08:00 Tomasz Wlostowski :
> Ladies and gentlemen, there's a lot of work for us ahead!
>
> https://www.reddit.com/r/AskElectronics/comments/
> 815fz2/what_eda_is_really_the_best_out_there_for_macos/
>
> Cheers,
> Tom
>
>
Actually the second point in that post is a gem (rerouting of tracks when
you move a component) It is a feature of some super-high end packages
(Xpedition, Allegro I think) but missing from lots of paid tools (Altium,
Zuken, etc).
It's on my list of things I want to add to KiCad at some point (if
Ladies and gentlemen, there's a lot of work for us ahead!
https://www.reddit.com/r/AskElectronics/comments/815fz2/what_eda_is_really_the_best_out_there_for_macos/
Cheers,
Tom
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad
18 matches
Mail list logo