element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Same page xref
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 9 replies
  • Subscribers 188 subscribers
  • Views 1176 views
  • Users 0 members are here
Related

Same page xref

autodeskguest
autodeskguest over 10 years ago

Now (7.5.0), its difficult to see if a xref is unconnected or connected

somewhere on the same page.

 

A normal XREF looks like "NETNAME/PAGE.XY". If the net is not present

elsewhere, it will only look like "NETNAME". The same happens if there

are other separated instances of the net on the same page. This

generates some difficulties when reading schematics. Yes it will be

picked up in ERC, but on a print, thats not an option. Visual search of

other present instances on a large print is not very reliable.

 

I suggest that xref what has net connections on the same page keep their

location but skip the same page reference. It could look like "NETNAME/XY".

 

It would also look a lot better if all xrefs pointed to the page where

the net is connected to an output/power pin direction (if present), so

that the source of the signal can easily be located.

 

  • Sign in to reply
  • Cancel
Parents
  • autodeskguest
    autodeskguest over 10 years ago

    Am 05.02.2016 um 09:21 schrieb Morten Leikvoll:

    Now (7.5.0), its difficult to see if a xref is unconnected or connected

    somewhere on the same page.

     

    A normal XREF looks like "NETNAME/PAGE.XY". If the net is not present

    elsewhere, it will only look like "NETNAME". The same happens if there

    are other separated instances of the net on the same page. This

    generates some difficulties when reading schematics. Yes it will be

    picked up in ERC, but on a print, thats not an option. Visual search of

    other present instances on a large print is not very reliable.

     

    I suggest that xref what has net connections on the same page keep their

    location but skip the same page reference. It could look like "NETNAME/XY".

     

    It would also look a lot better if all xrefs pointed to the page where

    the net is connected to an output/power pin direction (if present), so

    that the source of the signal can easily be located.

     

    Count me in twice image)

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • autodeskguest
    autodeskguest over 10 years ago

    Am 05.02.2016 um 09:21 schrieb Morten Leikvoll:

    Now (7.5.0), its difficult to see if a xref is unconnected or connected

    somewhere on the same page.

     

    A normal XREF looks like "NETNAME/PAGE.XY". If the net is not present

    elsewhere, it will only look like "NETNAME". The same happens if there

    are other separated instances of the net on the same page. This

    generates some difficulties when reading schematics. Yes it will be

    picked up in ERC, but on a print, thats not an option. Visual search of

    other present instances on a large print is not very reliable.

     

    I suggest that xref what has net connections on the same page keep their

    location but skip the same page reference. It could look like "NETNAME/XY".

     

    It would also look a lot better if all xrefs pointed to the page where

    the net is connected to an output/power pin direction (if present), so

    that the source of the signal can easily be located.

     

    Count me in twice image)

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • dukepro
    dukepro over 10 years ago in reply to autodeskguest

    On 02/05/2016 03:28 AM, Joern Paschedag wrote:

    Am 05.02.2016 um 09:21 schrieb Morten Leikvoll:

    Now (7.5.0), its difficult to see if a xref is unconnected or connected

    somewhere on the same page.

     

    A normal XREF looks like "NETNAME/PAGE.XY". If the net is not present

    elsewhere, it will only look like "NETNAME". The same happens if there

    are other separated instances of the net on the same page. This

    generates some difficulties when reading schematics. Yes it will be

    picked up in ERC, but on a print, thats not an option. Visual search of

    other present instances on a large print is not very reliable.

     

    I suggest that xref what has net connections on the same page keep their

    location but skip the same page reference. It could look like

    "NETNAME/XY".

     

    It would also look a lot better if all xrefs pointed to the page where

    the net is connected to an output/power pin direction (if present), so

    that the source of the signal can easily be located.

     

    Count me in twice image)

     

     

    Eagle devs, Jorge,

     

    Count all my licensed seats in as well.

     

        - Chuck

     

    Attachments:
    1641.att1.html.zip
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 10 years ago in reply to autodeskguest

    Joern Paschedag wrote on Fri, 05 February 2016 08:28

    Am 05.02.2016 um 09:21 schrieb Morten Leikvoll:

    Now (7.5.0), its difficult to see if a xref is unconnected or

    connected

    somewhere on the same page.

     

    A normal XREF looks like "NETNAME/PAGE.XY". If the net is not

    present

    elsewhere, it will only look like "NETNAME". The same happens if

    there

    are other separated instances of the net on the same page. This

    generates some difficulties when reading schematics. Yes it will

    be

    picked up in ERC, but on a print, thats not an option. Visual

    search of

    other present instances on a large print is not very reliable.

     

    I suggest that xref what has net connections on the same page keep

    their

    location but skip the same page reference. It could look like

    "NETNAME/XY".

     

    It would also look a lot better if all xrefs pointed to the page

    where

    the net is connected to an output/power pin direction (if

    present), so

    that the source of the signal can easily be located.

     

    Count me in twice image)

     

     

    Me too.  In fact, I mentioned this and my reasoning back in 2011!

     

    http://www.eaglecentral.ca/index.php/m/140238/3cf92059246dc2169fb27e9111ace4a6/?srch=xref#msg_140238

     

    James.

    --

    James Morrison  ~~~  Stratford Digital

     

    Order your EAGLE license from Stratford Digital at

    http://www.eaglelicenses.com

    --

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

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 10 years ago in reply to autodeskguest

     

    Count me in twice image)

     

    Me too!

     

    Markus

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube