Some nets merged on import from Eagle schematic

Report bugs here
Post Reply
Message
Author
rapeti
Posts: 4
Joined: 09 Mar 2021, 16:50

Some nets merged on import from Eagle schematic

#1 Post by rapeti » 22 Mar 2021, 22:47

Eagle Sch: 9.4.2
DT: 4.1.1.0

Importing an eagle schematic results in some nets being merged. Digging into the issue I noted that all nets that used a <library name="supply2" urn="urn:adsk.eagle:library:372"> part for the power rails were merged. Weather it is correct or not, eagle saved the file with the following:

Code: Select all

<library name="supply2" urn="urn:adsk.eagle:library:372">
	<description>&lt;b&gt;Supply Symbols&lt;/b&gt;&lt;p&gt;
GND, VCC, 0V, +5V, -5V, etc.&lt;p&gt;
Please keep in mind, that these devices are necessary for the
automatic wiring of the supply signals.&lt;p&gt;
The pin name defined in the symbol is identical to the net which is to be wired automatically.&lt;p&gt;
In this library the device names are the same as the pin names of the symbols, therefore the correct signal names appear next to the supply symbols in the schematic.&lt;p&gt;
&lt;author&gt;Created by librarian@cadsoft.de&lt;/author&gt;</description>
	<packages>
	</packages>
	<symbols>
		<symbol name="V+" urn="urn:adsk.eagle:symbol:27026/1" library_version="2">
			<text x="-1.27" y="1.27" size="1.778" layer="96">&gt;VALUE</text>
			<pin name="V+" x="0" y="-2.54" visible="off" length="short" direction="sup" rot="R90"/>
		</symbol>
	</symbols>
	<devicesets>
		<deviceset name="V+" urn="urn:adsk.eagle:component:27074/1" prefix="SUPPLY" library_version="2">
			<description>&lt;b&gt;SUPPLY SYMBOL&lt;/b&gt;</description>
			<gates>
				<gate name="1" symbol="V+" x="0" y="0"/>
			</gates>
			<devices>
				<device name="">
					<technologies>
						<technology name=""/>
					</technologies>
				</device>
			</devices>
		</deviceset>
	</devicesets>
</library>
...
<part name="SUPPLY11" library="supply2" library_urn="urn:adsk.eagle:library:372" deviceset="V+" device=""/>
...
<net name="EXT_+5V" class="0">
	<segment>
		<pinref part="R203" gate="G$1" pin="2"/>
		<pinref part="SUPPLY11" gate="1" pin="V+"/>
	</segment>
</net>
This file being imported resulted in the EXT_+5V net being renamed to V+ net and joined to ALL other nets with the same symbol on it. I didn't pick this error up until the "Check Net Connectivity" failed in layout on the imported Eagle layout. I've double checked in Eagle, and Eagle uses the net name for defining nets, NOT the pin name of the "supply2" part.

Alex
Technical Support
Posts: 3502
Joined: 14 Jun 2010, 06:43

Re: Some nets merged on import from Eagle schematic

#2 Post by Alex » 24 Mar 2021, 09:42

Please send whole schematic file either to DipTrace support or upload on the forum. Some lines from Eagle file can't help us.

rapeti
Posts: 4
Joined: 09 Mar 2021, 16:50

Re: Some nets merged on import from Eagle schematic

#3 Post by rapeti » 24 Mar 2021, 22:13

Thanks for the quick response. I will send the schematic to support as it is business IP.

Post Reply