Can't place some points in the command line. Invalid point

On 21/06/17 23:16, s0s wrote:

I want to place 32 pads in the package editor. I've calculated all the points, and it would be much faster if I could place them in the command window, because they would be accurate. This link shows it can be done: Cadsoft Eagle how to make parts tutorial - DP (http://dangerousprototypes.com/docs/Cadsoft_Eagle_how_to_make_parts_tutorial)

 

I notice it's when both coordinates are negative. However, the author of the article I linked to suggests making some negative, so that the package will be centered. I can manually place the points, but it's a real pain to get it to be accurate. Does anyone know how to solve this? I have done searches, but I saw no relevant results.

 

Thanks in advance.

 

Sorry, but in your enthusiasm to say when your problem happens, you appear to

have omitted to say what your actual problem is!

The link you referenced gives the following example:

(-1 -2.4)(-.5 -2.4)(0 -2.4)(.5 -2.4)(1 -2.4)(1 2.4)(.5 2.4)(0 2.4)(-.5 2.4)(-1 2.4);

As long as you follow that format (I prefer to add spaces between coordinate

pairs but Eagle probably isn't fussed) then it should work. What are you

actually typing in?

The problem is described in the title of this topic. I can't place some points (when I'm trying to add pads in the package editor). I've added a line to the top of the post above to clarify. When both the x and y coordinate are negative, it refuses to place the pad at that point from the command line.

I attempted exactly what you did, and it did not work. I even tried doing a single point. But again, if both coordinates are negative, it won't do it. I had to waste time manually putting them where I want them.

Hello,

I do this in my scripts regularly and it does work fine for me, but I am using a much newer version of EAGLE.

As you are using a freeware version (linux repos don't have anything newer than v6) I would recommend that you download either the latest v8 version (requires an Autodesk account) from http://cadsoft.io or alternatively if you don't have/want an Autodesk account to run EAGLE then download the most recent v7 version from http://eagle.autodesk.com/eagle/software-versions

At the very least if you don't want to move forward from v6 you should get the very latest v6.6 version which is also available from the Autodesk link above.

So I have just used your failing points list from above and using the package editor from v8.2.2 I executed:

SMD (-1 -2.4)(-.5 -2.4)(0 -2.4)(.5 -2.4)(1 -2.4)(1 2.4)(.5 2.4)(0 2.4)(-.5 2.4)(-1 2.4);

It correctly placed two rows of pads as expected.

Best Regards,

Rachael

On 22/06/17 07:59, rachaelp wrote:

 

I do this in my scripts regularly and it does work fine for me, but I am using

a much newer version of EAGLE.

I do it regularly on V4.16, V5.12 and V7.x and it works fine on all of

them. I doubt V6 was broken.

As you are using a freeware version (linux repos don't have anything newer than v6)

Actually the Gentoo repo has V7.6

I would recommend that you download either the latest v8 version

I wouldn't. The problem is not that V6 is broken so it won't be fixed by

upgrading.

My suspicion is that the OP is mistyping the negative coordinates.

Probably omitting the space.

    (-1.0   -2.0)          will work

    (-1.0-2.0)             is illegal

I put a space in them. In fact, this was the first thing I checked.

Have you tried it one point at a time to see exactly where it thinks the error is?

Both myself and Friedrich have tried the exact command you posted above in different versions of EAGLE and it works for both of us. I'd break it down to try and find the actual point of failure and go from there.

Rob thinks it's not related to EAGLE version as he's used this technique in v4, v5 and v7 and he's probably right, there were a whole bunch of fixes went into v6.6 though so even if you don't want v7 or v8 it's probably worth working with the latest version in the series.

Best Regards,

Rachael

Have you tried it one point at a time to see exactly where it thinks the error is?

Both myself and Friedrich have tried the exact command you posted above in different versions of EAGLE and it works for both of us. I'd break it down to try and find the actual point of failure and go from there.

Rob thinks it's not related to EAGLE version as he's used this technique in v4, v5 and v7 and he's probably right, there were a whole bunch of fixes went into v6.6 though so even if you don't want v7 or v8 it's probably worth working with the latest version in the series.

Best Regards,

Rachael

It works in a different file. I don't know why it wouldn't work before, but I'm done with that now, so I'm not going to worry about it. I'm designing a board now, and it worked in this file, so who knows. I want to thank everyone who sincerely tried to help.