Actions
Forum Thread Details
  • Replies 7 replies
  • Subscribers 187 subscribers
  • Views 686 views
  • Users 0 members are here
Related

re-touch:More than 16 layers

autodeskguest

With the project I am working on, I'm starting to feel some pain about

the lack of more than 16 layers. I know I can most likely virtualize

some inner gnd-only layers (cloning the gerbers) but I'd like to ask

about the plans for this feature.

 

At the same time I know there are some challenges for the ones that work

with that many layers. First of all I'm thinking about polygon

processing speeds causing reluctance to do ratsnest until absolutely

necessary, but when doing power routing, it will need frequent fill

tests, but even doing ratsnest on a single net takes time. I wish this

function became more "live", so airwires would appeare instantly as you

place a via. My gut feeling as a programmer is that this is possbile to

speed up alot.

 

 

Parents

  • On 09.05.2016 17:54, Jorge Garcia wrote:

    As you mention here, the users that require more than 16 layers

    generally use another tool. Getting them to switch to EAGLE even if it

    did support the appropriate design elements would not be a given. It

    goes back to figuring out a way to include these factors into the

    decisions for feature implementations.

     

    I'm going to think about this for a bit. If anyone has any ideas I'm all

    ears.

     

    I think you have the potential to grab new users simply by pricing.

    Afaik there is no tools that allows >16 layers even near Eagle's cost. I

    don't know (care) if KiCad can do this, but I definitely do not trust it

    when it comes to large designs. Of course I'm tempted to have a go at

    it, but now the time doesnt allow that. Even if I did look into

    alternate tools, it would have to be as open as eagle when it comes to

    data user-processing, wich eagle rules with the ULP.

     

     

Reply

  • On 09.05.2016 17:54, Jorge Garcia wrote:

    As you mention here, the users that require more than 16 layers

    generally use another tool. Getting them to switch to EAGLE even if it

    did support the appropriate design elements would not be a given. It

    goes back to figuring out a way to include these factors into the

    decisions for feature implementations.

     

    I'm going to think about this for a bit. If anyone has any ideas I'm all

    ears.

     

    I think you have the potential to grab new users simply by pricing.

    Afaik there is no tools that allows >16 layers even near Eagle's cost. I

    don't know (care) if KiCad can do this, but I definitely do not trust it

    when it comes to large designs. Of course I'm tempted to have a go at

    it, but now the time doesnt allow that. Even if I did look into

    alternate tools, it would have to be as open as eagle when it comes to

    data user-processing, wich eagle rules with the ULP.

     

     

Children
No Data