Have a question about CadSoft EAGLE?  Ask our Expert, Jorge!

I have generated output files for fab house but all layers are mis aligned from IPC? Can you please help me to figur out the issue.

On 09/06/2013 05:45 AM, Hafiz Muhammad Mujahid wrote:

I have generated output files for fab house but all layers are mis

aligned from IPC? Can you please help me to figur out the issue.

Refer to my post in this newsgroup on 26-Mar-2013 titled "Re: Gerber

files and Pick and place file".

This will identify the problem and show you how to fix it.

HTH,

    - Chuck

On 9/6/2013 8:14 AM, Chuck Huber wrote:

On 09/06/2013 05:45 AM, Hafiz Muhammad Mujahid wrote:

I have generated output files for fab house but all layers are mis

aligned from IPC? Can you please help me to figur out the issue.

 

Refer to my post in this newsgroup on 26-Mar-2013 titled "Re: Gerber

files and Pick and place file".

 

This will identify the problem and show you how to fix it.

 

HTH,

     - Chuck

 

Thanks Chuck,

Additionally, it important to make sure that in a CAM job all of the

tabs have the pos. coords check box in the same state. It doesn't matter

if it's checked or unchecked as long as all of the tabs have it set the

same way.

Best Regards,

Jorge Garcia

On 09/10/2013 04:55 PM, Jorge Garcia wrote:

On 9/6/2013 8:14 AM, Chuck Huber wrote:

On 09/06/2013 05:45 AM, Hafiz Muhammad Mujahid wrote:

I have generated output files for fab house but all layers are mis

aligned from IPC? Can you please help me to figur out the issue.

 

Refer to my post in this newsgroup on 26-Mar-2013 titled "Re: Gerber

files and Pick and place file".

 

This will identify the problem and show you how to fix it.

 

HTH,

     - Chuck

 

 

Thanks Chuck,

 

Additionally, it important to make sure that in a CAM job all of the

tabs have the pos. coords check box in the same state. It doesn't

matter if it's checked or unchecked as long as all of the tabs have it

set the same way.

Jorge,

Wouldn't it make sense, then, to make the pos. coords. check box a

property of the job and not each section?

Maybe it's time to move away from the .ini format to an XML format for

.cam files.  While the dev's are at it, they can break out combined

properties, such as the Flags value, into individual boolean properties.

Perhaps this is better suited for the suggest forum.

    - Chuck

My question lays in the autorouting and/or wiring algorithm. Can you describe for me, in great detail, how the autorouting system works? Where is the file that handles this? Would you explain the major points of that as well? How does the entire EAGLE program determine the best/shortest route to lay wires? This is a question of efficiency.

Thanks again!

I'm doing a layout that has a circular array of LEDs packed tightly together in an approximately 320 degree circle.  Based on the size of the board (really small) and the number of LEDs (really large), there is a need for precision device placement.  I use a script to place the LEDs exactly where they need to be.  All the LEDs origins are centered on a circle.  I've got the syntax for device placement, radial orientation, and rotation mastered.

The script works fine for placing the LEDs in their appropriate position and that hasn't presented a problem.However, there's one thing that I have not been able to discover by reading the Eagle documentation nor by experimentation.  I need to be able to orient the LED cathodes so that they are all pointing radially inward.  Is there any way to force device orientation (i.e. make certain that it's the LED cathodes and not the anodes that point radially inward) based on pad or pin name or some other attribute?

I've been able to accomplish this by "pre-orienting" all the LEDs on an unrouted area of the board and then run the script.  What I mean by this is that I'll manually move all the LEDs to some arbitrary area of the board and orient them so that their cathodes all point to the right and then run the script.  The script places the LEDs exactly where they need to be with the desired cathode orientation.  If I flipped the LEDs so that the cathodes all pointed left during my "pre-orienting", the cathodes all wind up facing radially outward.  So, the device placement rules are at least consistent.  However, this is a pretty kludgy way to accomplish something I'd like to be able to do entirely via script.

Is there a way to do this via script?

Bill Krueger wrote:

I'm doing a layout that has a circular array of LEDs packed tightly

together in an approximately 320 degree circle.  Based on the size of

the board (really small) and the number of LEDs (really large), there is

a need for precision device placement.  I use a script to place the LEDs

exactly where they need to be.  All the LEDs origins are centered on a

circle.  I've got the syntax for device placement, radial orientation,

and rotation mastered.

you are aware of the posibility to use polar coordinates and/or

relative coordinates (online_help/Editor_Commands/Command_Syntax)?

The script works fine for placing the LEDs in their appropriate position

and that hasn't presented a problem.However, there's one thing that I

have not been able to discover by reading the Eagle documentation nor by

experimentation.  I need to be able to orient the LED cathodes so that

they are all pointing radially inward.  Is there any way to force device

orientation (i.e. make certain that it's the LED cathodes and not the

anodes that point radially inward) based on pad or pin name or some

other attribute?

 

I've been able to accomplish this by "pre-orienting" all the LEDs on an

unrouted area of the board and then run the script.  What I mean by this

is that I'll manually move all the LEDs to some arbitrary area of the

board and orient them so that their cathodes all point to the right and

then run the script.  The script places the LEDs exactly where they need

to be with the desired cathode orientation.  If I flipped the LEDs so

that the cathodes all pointed left during my "pre-orienting", the

cathodes all wind up facing radially outward.  So, the device placement

rules are at least consistent.  However, this is a pretty kludgy way to

accomplish something I'd like to be able to do entirely via script.

rotating parts can be accomplished using the rotate command.

     mark (center_x center_y)

     move part_name (P radius angle)

     rotate angle part_name

(see online_help/Editor_Commands/Command_Syntax, ../mark, ../move,

../rotate, ../add )

--

Lorenz

Thanks, I am aware of the various co-ordinate system options in eagle and I am using polar co-ordinates. My script already does exactly what you describe.  Using polar co-ordinates, the script moves the device and places the LEDs on a circle or radius r and angle theta  ..., and rotates the device.  That part works just fine.

However, this doesn't answer the question I'm asking. Let's assume that pin 1 of the LED package I want to place is the cathode & pin 2 is the anode.  What I also need to guarantee is that pin 1, the cathode, points radially inward once the device is already placed and rotated correctly.

As I mentioned, I can pre-orient all the LEDs in an unused area by pointing all the cathodes in one direction and then run the script.  Eagle is consistent in the way it places the LEDs on the board once that's done.  However, if I don't orient all the LEDs cathode orientation consistently before running the script, Eagle will orient some of the LEDs with cathodes pointing inward and some with cathodes point outward depending on the cathode orientation before I ran the script.  So I do have away around this issue, but I was hoping for something that didn't require manual tweaking before running the script.

What I'm asking is there a way to guarantee the cathode/anode orientation using a script command?  I wasn't able to find anything in the documentation that describes how that might be done via a script.

Bill Krueger wrote:

Thanks, I am aware of the various co-ordinate system options in eagle

and I am using polar co-ordinates. My script already does exactly what

you describe.  Using polar co-ordinates, the script moves the device and

places the LEDs on a circle or radius r and angle theta  ..., and

rotates the device.  That part works just fine.

 

However, this doesn't answer the question I'm asking. Let's assume that

pin 1 of the LED package I want to place is the cathode & pin 2 is the

anode.  What I also need to guarantee is that pin 1, the cathode,

points radially inward +once the device is already placed and rotated

correctly+.

 

As I mentioned, I can pre-orient all the LEDs in an unused area by

pointing all the cathodes in one direction and then run the script. 

Eagle is consistent in the way it places the LEDs on the board once

that's done.  However, if I don't orient all the LEDs cathode

orientation consistently before running the script, Eagle will orient

some of the LEDs with cathodes pointing inward and some with cathodes

point outward depending on the cathode orientation before I ran the

script.  So I do have away around this issue, but I was hoping for

something that didn't require manual tweaking before running the script.

 

What I'm asking is there a way to guarantee the cathode/anode

orientation using a script command?  I wasn't able to find anything in

the documentation that describes how that might be done via a script.

scripts are not able to access data from the board.

For that you need an ULP.

--

Lorenz

Thank you Lorenz.  I'd suspected that scripting had a limit I was encountering.  Looks like I'll have to research ULP.