Actions
Forum Thread Details
  • Replies 10 replies
  • Subscribers 182 subscribers
  • Views 2357 views
  • Users 0 members are here
Related

Eagle 7.6 and Excellon CAM

matt_compton@trimble.com

I just upgraded to the 7.6 release and when I tried to generate my standard drill files by running CAM job => excellon.cam I get the following error message on my 4 layer board

 

"CAM job doesn't cover the Layer Setup! - MIssing signal layers 1 2 15 16"

 

A quick look at the DRC indicates the layers are setup correctly and in fact, I had a prior successful autoroute. When I try to manually add the layers, it then complains that more than 1 signal layer is active. It does seem to generate the files and they seem reasonable to a quick scan but errors are indicated in the flow

 

When I retreat to Eagle 7.5 the same excellon.cam job works without issue and no errors are generated. Both the Eagle 7.5 and 7.6 installations are on MacOS. Is there a new trick that I need to be aware of to make standard CAM work on 7.6 without error ? The gerber generation went without incident, but the CAM failure for the drill file generation which has worked pretty much forever is  a bit annoying.

Parents

  • Matt Compton wrote on Mon, 23 May 2016 18:48

    "CAM job doesn't cover the Layer Setup! - MIssing signal layers 1 2 15

    16"

     

     

    I got something similar too, when I was doing a 2 layer board on Windows 7.

    It looked like the right layers were selected, so I just assumed this was

    more nanny-ware and kept going.  I checked the resulting drill files, and

    they seemed to have reasonable data in them.

     

    At the time I guessed that somebody had the bright idea of warning you that

    you don't have signal layers selected, but forgot there are other uses for

    the CAM processor than writing data derived from signal layers.  I have no

    idea what that message is really trying to tell me or what I'm supposed to

    do about it.

     

    How do such obvious things get thru testing?

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

  • in reply to autodeskguest

    On 5/24/2016 2:21 PM, Olin Lathrop wrote:

    Matt Compton wrote on Mon, 23 May 2016 18:48

    "CAM job doesn't cover the Layer Setup! - MIssing signal layers 1 2 15

    16"

     

    I got something similar too, when I was doing a 2 layer board on Windows 7.

    It looked like the right layers were selected, so I just assumed this was

    more nanny-ware and kept going.  I checked the resulting drill files, and

    they seemed to have reasonable data in them.

     

    At the time I guessed that somebody had the bright idea of warning you that

    you don't have signal layers selected, but forgot there are other uses for

    the CAM processor than writing data derived from signal layers.  I have no

    idea what that message is really trying to tell me or what I'm supposed to

    do about it.

     

    How do such obvious things get thru testing?

     

     

    Hi Guys,

     

    This error is an oversight on the part of one of our developers. It will

    be fixed shortly, sorry about the annoyance.

     

    hth,

    Jorge Garcia

     

Reply
  • in reply to autodeskguest

    On 5/24/2016 2:21 PM, Olin Lathrop wrote:

    Matt Compton wrote on Mon, 23 May 2016 18:48

    "CAM job doesn't cover the Layer Setup! - MIssing signal layers 1 2 15

    16"

     

    I got something similar too, when I was doing a 2 layer board on Windows 7.

    It looked like the right layers were selected, so I just assumed this was

    more nanny-ware and kept going.  I checked the resulting drill files, and

    they seemed to have reasonable data in them.

     

    At the time I guessed that somebody had the bright idea of warning you that

    you don't have signal layers selected, but forgot there are other uses for

    the CAM processor than writing data derived from signal layers.  I have no

    idea what that message is really trying to tell me or what I'm supposed to

    do about it.

     

    How do such obvious things get thru testing?

     

     

    Hi Guys,

     

    This error is an oversight on the part of one of our developers. It will

    be fixed shortly, sorry about the annoyance.

     

    hth,

    Jorge Garcia

     

Children
  • in reply to autodeskguest

    Jorge Garcia wrote on Thu, 26 May 2016 16:40

    This error is an oversight on the part of one of our developers. It

    will be fixed shortly, sorry about the annoyance.

     

     

    Hi, Jorge.  I can understand mistakes get made.  It happens to everyone, no

    matter how good and careful they are.  I'm not bothered by a bug like that

    happening.

     

    What does bother me is that it seems more and more obvious that you don't

    properly test your product before releasing it.  Since this apparently

    happens every time you use the CAM processor to create drill files, even

    very basic testing should have caught it.

     

    Eagle is a complex program, way too complex for a human to sit down and

    test properly.  You need a good suite of regression tests.  Throwing a new

    version out there to see what users uncover isn't a testing strategy.

     

    So now I'm curious.  How do you test new builds of Eagle?  New release

    candidates?  Do you have automated test suites?

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

  • in reply to autodeskguest

     

    Am 27.05.2016 um 22:33 schrieb Olin Lathrop:

    Jorge Garcia wrote on Thu, 26 May 2016 16:40

    This error is an oversight on the part of one of our developers. It

    will be fixed shortly, sorry about the annoyance.

     

    Hi, Jorge.  I can understand mistakes get made.  It happens to everyone, no

    matter how good and careful they are.  I'm not bothered by a bug like that

    happening.

     

    What does bother me is that it seems more and more obvious that you don't

    properly test your product before releasing it.  Since this apparently

    happens every time you use the CAM processor to create drill files, even

    very basic testing should have caught it.

     

    Eagle is a complex program, way too complex for a human to sit down and

    test properly.  You need a good suite of regression tests.  Throwing a new

    version out there to see what users uncover isn't a testing strategy.

     

    So now I'm curious.  How do you test new builds of Eagle?  New release

    candidates?  Do you have automated test suites?

     

     

    Hi Olin,

     

    as soon as there is a new alpha version made available from the dev

    team we use it internally for testing. And there are as you know beta

    versions that are made publicly available. Everybody can use and test

    them and report back by email or the forum. There are bunch of

    regression tests made before a beta version is released. There is a

    minimum period of time that is reserved for beta testing.

     

    Concerning the CAM job warning:

    It's not so easy to predict how a customer works. I personally would

    use a CAM job for creating manufacturing data that contains all the

    steps for Gerber data and for Excellon data. If I wanted to create

    drill data only, I'ld click "Process section". No warning then.

    Another customer may have one job for drill data that consists of

    one section. I'ld again would click "Process section" (no warning) and

    not "Process job" (with warning) in this situation, but another one

    clicks "Process job".

     

    I think we have to refine the message prompting.....

     

     

    --

    Mit freundlichen Gruessen / Best regards

    Richard Hammerl

      CadSoft Support -- hotline@cadsoft.de

      FAQ: http://www.cadsoft.de/training/faq/

     

  • in reply to autodeskguest

    CadSoft Support wrote on Mon, 30 May 2016 07:46

    It's not so easy to predict how a customer works. I personally would

    use a CAM job for creating manufacturing data that contains all the

    steps for Gerber data and for Excellon data. If I wanted to create

    drill data only, I'ld click "Process section". No warning then.

    Another customer may have one job for drill data that consists of

    one section. I'ld again would click "Process section" (no warning) and

    not "Process job" (with warning) in this situation, but another one

    clicks "Process job".

     

     

    I use the CAM processor differently.  I learned to do it that way from the

    documentation that came with version 4, I think.

     

    Creating the drill files is always the same, so there is one CAM job for

    that.  Creating Gerber files can be different depending on how many layers

    there are.  I suppose I could make one big CAM job and that contains

    everything, then either temporarily delete what isn't relevant or manually

    run only selected sections.  Instead, I have a few different CAM jobs for

    frequent configurations.  This cuts down on mistakes since there is less

    manually to do other than to select the appropriate CAM job to make the

    Gerber files.  For example, I have one for a 2-layer board, another for a

    4-layer board.

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.