On 10:44 AM 3/05/2001 -0700, Drew Lundsten said: >The situation where it helps most, for us, is on large backplane designs. >Consider a 20-slot backplane, each slot having a few hundred connections, >many of which are identical (AD31) and others which are unique (RST#_35) but >need to be tied together somewhere, and we do it on the first schematic >sheet. It's easy to make each individual sheet, since they're basically >copies, but when we end up tying together all the RST#_nn lines I want to >see that in the netlist as RST#_CPUOUT rather than some random slave slot's >net label. > >Only Ports Global might be a better scope, but we'd still have to figure out >how to assert one net name over another, wouldn't we? > >Drew Lundsten <[EMAIL PROTECTED]> direct +1.858.882.8828 Drew, I am sorry for being dim but for me if a net is the tied at some point isn't it the same net. So why not call all of then RST#_CPUOUT? My view is that if it is one piece of copper it is one net. Maybe I am not understanding what you wish to achieve. As for Ports Only Global - ports in Protel do not name a net, only imply a connection. I found this when I had a whole bunch of nets with only ports and they ended up with NETxxxxx net names in the netlist - all the nets were correct, just unnamed. So using ports only as global would not help you very much I think. You still need a net name at some point. You might be able to have multiple ports with different names - I have never tried that. So, on the first sheet, you would have multiple ports names and just the one netlabel. On all the other sheets you would use the relevant port name and an annotation rather than a netlabel if you need to put text on the net. I wonder how confused you could make the netlister. I s'pose it might work as it is not that different from a complex heirarchy. Abd ul-Rahman Lomax's comments (paraphrased) "beware those that use a side-effect of a program" comes to mind. It may work now but later it may not due to subtle changes in netlisting code that do not change any "published" behavior but have nasty side-effects on undocumented "features" that used to work. There is an advanced function in the netlister somewhere that allows you to monitor the progress of the netlister. Under Design|Create Netlist... select the Trace Options tab. Maybe there is something there that would allow you to see what is happening when and so work out how the net name is chosen. I have only ever tried to use it once a long time ago (Pre-P99) and I do not recall if it helped at all. Have you tried getting a response direct from Protel support on how you might achieve what you want? all the best, Ian * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/subscrib.html * - or email - * mailto:[EMAIL PROTECTED]?body=leave%20proteledaforum * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Browse or Search previous postings: * http://www.mail-archive.com/[email protected] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
