Actions
Forum Thread Details
  • Replies 13 replies
  • Subscribers 179 subscribers
  • Views 1718 views
  • Users 0 members are here
Related

Gateswap across schematic   sheets

autodeskguest

I just discovered GATESWAP only works within the current schematic sheet.

I am using a quad opamp.  IC10A and IC10B are on schematic sheet 9, and

IC10C and IC10D on sheet 10.  Now that I'm placing parts on the board, I

want to swap IC10A <> IC10D and IC10B <> IC10C.

 

In the schematic editor, I went to sheet 9 and entered "gateswap ic10a

ic10d".  This resulted in the rather unhelpful pop "Can't swap gate IC10A

and IC10D".  Why can't these gates be swapped?  I checked the swaplevel of

each gate.  No, they are all set to 1.  Maybe the gate names need to be

enclosed in apostrophies?  No, that didn't help.  Upper case?  No, that

wasn't it either.

 

Then I tried "gateswap ic10a ic10b".  That worked.  OK, maybe I had a small

typo.  Using up-arrow, I got the previous command back and carefully

changed only the B to a D.  Now its back to "Can't swap gate IC10A and

IC10D".  It must be that gate A and D are on different sheets, but that's

not intuitive at all.

 

I got around this by moving all of the sheet 10 contents to the side of

sheet 9, doing the gateswaps, then moving the sheet 10 content back to

sheet 10.

 

Am I missing something?

 

If not, then here are my suggestions:Allow GATESWAP to work across

schematic sheets when entered as a command.

 

Fix the GATESWAP error dialog to explain why it can't swap the gates as

requested (incompatible swap level, different numbers of pins, no such

gate, not allowed on Tuesday afternoons, etc).

 

If you don't do #1, at least mention this limitation in the GATESWAP help

page.

 

 

--

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

 

Parents

  • Olin Lathrop wrote:

    I just discovered GATESWAP only works within the current schematic sheet.

     

    It is clear why "gateswap (x1 y1) (x2 y2)" won't work across sheets

    (at least the clickety-click way, and the command line version would

    require an extended coordinate syntax), but ...

     

    ... I can't see any reason why "gateswap gate1 gate2" should pose any

    implementation problems.

     

     

    Disclaimer: I'm using 6.6, don't know if 7.x allows it.

    --

     

    Lorenz

     

  • in reply to autodeskguest

    On 11/10/2016 2:17 AM, Lorenz wrote:

    Olin Lathrop wrote:

    I just discovered GATESWAP only works within the current schematic sheet.

     

    It is clear why "gateswap (x1 y1) (x2 y2)" won't work across sheets

    (at least the clickety-click way, and the command line version would

    require an extended coordinate syntax), but ...

     

    ... I can't see any reason why "gateswap gate1 gate2" should pose any

    implementation problems.

     

    Under the current Hierarchy implementation there is the possibility for

    ambiguity with the command line syntax.

     

    Disclaimer: I'm using 6.6, don't know if 7.x allows it.

    Just to clarify it still doesn't allow it.

     

    I'm of the opinion that a gateswap in the board would be most useful.

    Usually you decide to swap a gate because you are on the layout and

    realize using a different gate would simplify your routing task.

     

    The problem I see is that I can't think of what the user interface for

    that would be like. Now in current V7 we have to deal with how hierarchy

    is implemented and that confuses a lot of things.

     

    Do you guys have any ideas? If we can have a suggestion of what should

    be implemented then that gives direction for the devs. How would you

    guys want this to work?

     

    Best Regards,

    Jorge Garcia

     

  • in reply to autodeskguest

    Jorge Garcia wrote on Thu, 10 November 2016 12:24

    ... I can't see any reason why "gateswap gate1 gate2" should pose

    any

    implementation problems.

     

    Under the current Hierarchy implementation there is the possibility for

     

    ambiguity with the command line syntax.

     

     

    I haven't used hierarchy, so don't understand the issue.  What about

    hierarchy makes "IC1A", for example, ambiguous?  Is it that there can be a

    IC1 in each of several sub-blocks?  If so, then that must cause trouble for

    various other commands too.  How do those commands deal with it?

     

    Quote:

    I'm of the opinion that a gateswap in the board would be most useful.

    Usually you decide to swap a gate because you are on the layout and

    realize using a different gate would simplify your routing task.

     

     

    True, but I don't think I'd blindly swap gates without looking in the

    schematic to make sure there aren't any issues.  Once there, I'd probably

    do the gate swap there.  If it only worked in the board, I could live with

    it though.

     

    In the example that prompted this, I was doing component placement and

    realized routing would be simplified by swapping some opamps of a quad

    opamp chip around.  That's probably a pretty normal case for wanting to

    swap gates.  However, it never even occurred to me to try doing this in the

    board.  I didn't know it wouldn't work, but I wanted to see what exactly I

    was swapping in the schematic, and that's where I attempted to do the swap.

    Doing it in the board seems awkward, but, again, I could live with it.

     

    Quote:

    The problem I see is that I can't think of what the user interface for

     

    that would be like. Now in current V7 we have to deal with how

    hierarchy

    is implemented and that confuses a lot of things.

     

    Do you guys have any ideas?

     

     

    I need to understand more about hierarchy and why that causes trouble

    before making any suggestions.  Please explain.

     

    --

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

     

Reply
  • in reply to autodeskguest

    Jorge Garcia wrote on Thu, 10 November 2016 12:24

    ... I can't see any reason why "gateswap gate1 gate2" should pose

    any

    implementation problems.

     

    Under the current Hierarchy implementation there is the possibility for

     

    ambiguity with the command line syntax.

     

     

    I haven't used hierarchy, so don't understand the issue.  What about

    hierarchy makes "IC1A", for example, ambiguous?  Is it that there can be a

    IC1 in each of several sub-blocks?  If so, then that must cause trouble for

    various other commands too.  How do those commands deal with it?

     

    Quote:

    I'm of the opinion that a gateswap in the board would be most useful.

    Usually you decide to swap a gate because you are on the layout and

    realize using a different gate would simplify your routing task.

     

     

    True, but I don't think I'd blindly swap gates without looking in the

    schematic to make sure there aren't any issues.  Once there, I'd probably

    do the gate swap there.  If it only worked in the board, I could live with

    it though.

     

    In the example that prompted this, I was doing component placement and

    realized routing would be simplified by swapping some opamps of a quad

    opamp chip around.  That's probably a pretty normal case for wanting to

    swap gates.  However, it never even occurred to me to try doing this in the

    board.  I didn't know it wouldn't work, but I wanted to see what exactly I

    was swapping in the schematic, and that's where I attempted to do the swap.

    Doing it in the board seems awkward, but, again, I could live with it.

     

    Quote:

    The problem I see is that I can't think of what the user interface for

     

    that would be like. Now in current V7 we have to deal with how

    hierarchy

    is implemented and that confuses a lot of things.

     

    Do you guys have any ideas?

     

     

    I need to understand more about hierarchy and why that causes trouble

    before making any suggestions.  Please explain.

     

    --

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

     

Children
No Data