no I hadn't tried any of the other schematic tricks that you mention. I
wouldn't be able to use the ports for connections, don't have any, don't
usually use them. Just nets globally.
   Duplicate designators aren't an issue unless they have some manner of
getting past the ERC check for that situation.

   I will be starting again tomorrow morning, thanks for the ideas, more
options at the very least.

Brad Velander
Norsat International

-----Original Message-----
To: Protel EDA Forum
Sent: 02/10/2002 7:24 PM
Subject: Re: [PEDA] P99SE SP6 Problem with Update PCB generating duplicate
nets or ot her errors.

Hi Brad,

I have seen this behaviour before but it was a while ago and I can't
remember how I solved or got around it.

I do have some thoughts or suggestions that may force a solution...

Have you tried changing the net scope to "Only ports global" or "Sheet
symbol/Port connection" in conjuction with "Append sheet numbers to
nets" temporarily allowing it to assign nets to everything, and then
changing it back to "Net labels and ports global" as you need to have

What about temporarily using the largest available schematic workspace
copying all sheets onto the one and netlisting that to see if that fixes
the problem?

I'm not questioning your ability or experience, but do you have any
duplicate designators or the like?  I realise this causes a problem
different to what you describe but who knows?


-----Original Message-----
From: Brad Velander [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 3 October 2002 10:51 AM
To: Protel EDA Forum List Server (E-mail)
Subject: [PEDA] P99SE SP6 Problem with Update PCB generating duplicate
nets or ot her errors.

Hi all,
             I have a layout that is a little different than our norm in
terms of
size and complexity. This seems to be causing some problems that I don't
normally see.

I have four schematic pages in a flat hierarchy. I have used nets and
global, I actually don't have any ports used at all just the netnames.
             When I run the Update PCB I get errors reported for adding
nets that
already exist. If I run the update anyway I get multiple occurrences of
these nets showing up in the PCB netlist manager. The nets involved are
nets where I have used a netname on one sheet to tie a signal to the
intended connection on the other sheet. So yes there are duplicate
(the same netname) within the schematics but they are needed to provide
             What is wrong? How can I fix this?
             The first time that I ran the update, I deleted the
duplications from the preview macros window. On that occasion I also got
access violation near the end of the update process. Looking in the PCB
I discover that the initial components have been placed by the update
function in the upper right corner as usual. However the components
to run right off the page past the 100 inch limit of the database. I am
sure if anything might have been dropped because it ran past the 100
So I move the parts down close to my PCB outline and run update again. I
the same duplicated net error but I do see some net connections being
that obviously weren' t made during the first pass. Possibly because of
access violation near the end of the first update?  This is not a very
design compared to some you guys work on, is this common behaviour
parts out past or at least to the 100 inch limit? Is there a chance that
something is screwed because of this part loading out to or near the 100
inch limit?

             I also just tried running update again for a third time. It
adding 2 more net connections to device pads! Why weren't these added in
either of the two previous updates?

             I am just so leery that something is drastically wrong at
and that I can't trust the database. I hope someone has had similar
experiences and has an answer or advice.

Brad Velander.

Lead PCB Designer
Norsat International Inc.
Microwave Products
Tel   (604) 292-9089 (direct line)
Fax  (604) 292-9010
Norsat's Microwave Products Division has now achieved ISO 9001:2000

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
* To leave this list visit:
* Contact the list manager:
* Forum Guidelines Rules:
* Browse or Search previous postings:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to