I suspect you can. But I haven't confirmed this before writing.
Your ULP could use the system() command to launch a second silent instance
of eagle to run your CAM job. Worth looking into.
Warren
--
Web access to CadSoft support forums at www.eaglecentral.ca. Where the CadSoft EAGLE community meets.
On 03/19/2013 06:17 PM, Warren Brayshaw wrote:
I suspect you can. But I haven't confirmed this before writing.
Your ULP could use the system() command to launch a second silent instance
of eagle to run your CAM job. Worth looking into.
Warren,
I use this method on every new board I make now. I have gotten rid of
most of my .cam files migrating each project to use "camprep.ulp", which
produces a shell script that gets executed just before the ULP exits. I
wrote this strictly for linux. It probably works on Macs, and Windows
may need some modifications. The shell script produced also launches
"gerbv" to preview the gerber files.
The CAM processor does essentially the same thing, which is why you have
to save the board before running the CAM job. But instead of having
different cam jobs for every project, I have just one ULP that handles it.
camprep.ulp will detect a "-Array" in the board file name, in which case
it assumes that the board is a product of "panelize.ulp" and replaces
layers 25 and 26 with layers 125 and 126 respectively. I have not
tested it with blind or burried vias.
Near the start of the ULP, it calls "fixdrills.ulp" which rounds all the
vias to the nearest mil, and it also saves the board. You can comment
these out if you don't need it.
Bottom line is that it comes without warranty. It's decently commented
and works for me, which meets my requirements. Modify at will to suit
your needs.
Attached is a sample shell script that is produced, and the camprep.ulp.
HTH,
- Chuck
| https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/308/cam.sh | |
| camprep.ulp.zip |
On 03/19/2013 06:17 PM, Warren Brayshaw wrote:
I suspect you can. But I haven't confirmed this before writing.
Your ULP could use the system() command to launch a second silent instance
of eagle to run your CAM job. Worth looking into.
Warren,
I use this method on every new board I make now. I have gotten rid of
most of my .cam files migrating each project to use "camprep.ulp", which
produces a shell script that gets executed just before the ULP exits. I
wrote this strictly for linux. It probably works on Macs, and Windows
may need some modifications. The shell script produced also launches
"gerbv" to preview the gerber files.
The CAM processor does essentially the same thing, which is why you have
to save the board before running the CAM job. But instead of having
different cam jobs for every project, I have just one ULP that handles it.
camprep.ulp will detect a "-Array" in the board file name, in which case
it assumes that the board is a product of "panelize.ulp" and replaces
layers 25 and 26 with layers 125 and 126 respectively. I have not
tested it with blind or burried vias.
Near the start of the ULP, it calls "fixdrills.ulp" which rounds all the
vias to the nearest mil, and it also saves the board. You can comment
these out if you don't need it.
Bottom line is that it comes without warranty. It's decently commented
and works for me, which meets my requirements. Modify at will to suit
your needs.
Attached is a sample shell script that is produced, and the camprep.ulp.
HTH,
- Chuck
| https://community.element14.com/cfs-file/__key/communityserver-discussions-components-files/308/cam.sh | |
| camprep.ulp.zip |