xref leabels: question and suggestion

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello,
I have been searching for a solution to a net labeling issue I have. When you have a lot of high pin count ICs (i.e. a micro <-> SRAM, flash, eMMC) sometimes using complete nets everywhere makes a schematic unreadable. We prefer to use the Xref labels because it conveys the same information (i.e. what are the actual connection points) without the messy wires. The problem is that the options for it are very rigid. We also prefer to use ledger size (11" x 17") paper for our schematic sheets, so we can fit a lot of information onto a single page.
The first issue is not displaying connection locations on the same sheet. If your schematic has some connections that look something like below (please note, I am not willing to share more of the schematic. It is for a work project.):
This is taken from sheet one of a two sheet schematic. Both UART1 signals are connected on a separate sheet (sheet 2, column 8, row D). Both SPI0 signals are connected on the same sheet (sheet 1). How do I make it show the same information for connections made on this sheet?
When you look at the properties menus (below) for each type of net label, it's clear that the Allocation settings are what are causing this issue. However, short of creating a custom script/ULP I see no easy way to modify this, and I would rather not have to mess with writing my own scripts/ULPs. It's not that I couldn't figure it out; it's that I feel there really is not a great reason for it being as difficult as it is.
My feature suggestion/request:
I guess ultimately, I just have to wonder why these rules are (and always have been) so rigid. If I have a net connected in eight different locations, and I want to show all seven other locations on the each points' label then I should be able to. If I want to display these connections on the same page, I should be able to. I understand that there are a lot of potential problems that could be caused by this. My response to that is have the "advanced modification of net label allocation" not enabled by default.