sparkfun / SparkFun_Eagle_Settings

The Eagle settings SparkFun uses for board designs

Home Page:https://www.sparkfun.com/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Sparkfun_Panelizer fails on Eagle 9.5.2

Gilbert54 opened this issue · comments

I tried running the ulp directly from the .brd file in Eagle. Initially I get a complaint that the script doesn't know what board color to use, but after that it seems to run quietly. But I can't find the result.
It does create a folder "Production" in my project folder with a file "ordering_instructions", but that's all it does. I get no error message, not notification that it did the job or where to look for results.
Can you help. My Eagle version is 9.5.2.

BTW:

  1. against better judgement, Eagle is installed in C:\EAGLE 9.5.2. My preference would be to put in in the "Program Files (x86)", but I kept the default installer setting to avoid the risk for issues with wrong paths.
  2. related to this, the ulp script fails to find "C:\Eagle.ulp". Not sure which part of the program is generating this error (Eagle .exe or the sparkfun ulp), but it doesn't make sense to have an ulp file in the root directory. I looked for eagle.ulp in the Eagle 9.5.2 program folder (and subfolders). It doesn't seem to exist at all. I looked for the string "Eagle.ulp" in the panelizer ulp, but drew a blank as well.

Thanks for trying out the panelizer! We use it multiple times a day, but there's some quirks because we really built it for us, not a general tool.

I recommend running the ULP from the brd window. I see now there are some confusing comments at the top of the ULP (I'll remove).

  • The panelizer tries to ID the board color based on Logos (do I see the SparkFun logo? The SparkX logo? Or the LilyPad logo?). Don't worry if it throws that warning, the ordering instructions.txt will just have 'Red' as the default color.
  • The location of eagle.exe shouldn't matter. I have it in C:\Eagle v.v.v.
  • The location of eagle.ulp does sort of matter. I believe the panelizer loads eagle.ulp (aka your default settings) once the panel is opened up. So it's ok if eagle.ulp is not found; it just won't load your eagle settings like key assignments and layer colors.

Here's how it works for me:
image

And a couple seconds later:

image

And there should be a "XYZ-Panel.brd" file created in the 'Production' subfolder.

Thanks for trying out the panelizer! We use it multiple times a day, but there's some quirks because we really built it for us, not a general tool.

I recommend running the ULP from the brd window. I see now there are some confusing comments at the top of the ULP (I'll remove).

* The panelizer tries to ID the board color based on Logos (do I see the SparkFun logo? The SparkX logo? Or the LilyPad logo?). Don't worry if it throws that warning, the ordering instructions.txt will just have 'Red' as the default color.

* The location of eagle.exe shouldn't matter. I have it in C:\Eagle v.v.v.

* The location of eagle.ulp does sort of matter. I believe the panelizer loads eagle.ulp (aka your default settings) once the panel is opened up. So it's ok if eagle.ulp is not found; it just won't load your eagle settings like key assignments and layer colors.

Here's how it works for me:
image

And a couple seconds later:

image

And there should be a "XYZ-Panel.brd" file created in the 'Production' subfolder.

hi @nseidle. is it possible for u to remote to my computer. i do face this same issue.

image

FYI, my board size is 85mm x 37 mm. thus i intended to create panel of 2 boards. top & bottom. but the ulps don't succeed but giving the errors.

image

looking forward for your reply. best regards.

Maybe this has been address elsewhere, but I haven't seen it myself: I can run the .ULP to completion and it generates the Gerbers and panel .brd file. But the part numbers are not preserved in the copies, they are replicated with new part numbers. I really want the same R1, R2, C1 etc. to appear in each tiled PCB. I saw one graphic here where that was done apparently correctly, yet the panellizer ulp here does not do that. How come?

Hi @asgard42 ,

We use the panelizer to replicate our PCBs for pick and place production. For PnP to work correctly, each component needs to have an individual identity. Our machines would not be able to cope if there were multiple R1's on a panel. Also, we do not normally include the component IDs (tNames) in our silk layer, so, for us, this isn't a problem. If you repeat the component IDs in the tPlace layer, you should be good to go.

Best wishes,
Paul