I have been trying to get a report out using the SI tool to provide info
for an SDRAM interface. I have IBIS models and some results look useful.
All the same I am going nuts trying to sort out some less than well
documented aspects of the process. An SI report (Menu ReportsSI) tells me
that I
This came up not so long ago.
Protel has problems with certain traces when they contain loops in the paths
etc.
Otherwise in the signal integrity module, you should be able to select the
nets and get a list of the components on the net. From that you can change
the component model used.
It
any fool can write ISO procedures badly, for ISO to work well for a
company then the procedures must be written in such a way as to help the
company in doing its business rather than hindering it!
Dennis Saputelli wrote:
i told my story before but ...
i had a board once put on hold and
In favour of GOOD documents how about;
Why
Are
No
Knowledge
Ever
Retained
Chris Lowe
Bevan Weiss
[EMAIL PROTECTED]To:
My apologies, I jumped the gun earlier and sent in error.
I have carefully inspected the routes and no sign of loops anywhere. The
analyzer seems to have particular problems with T networks. I have cured
one instance of this by removing the route, deleting the net, creating a
new net and
On Mon, 09 Jun 2003 13:33:37 +0100, Chris Lowe wrote:
any fool can write ISO procedures badly, for ISO to work well for a
company then the procedures must be written in such a way as to help the
company in doing its business rather than hindering it!
Shame having a fool writing the
I have to agree with you here. All the same I don't really care what the
managers do with our engineering docs so long as the documents are
effective and assist the work. At the same time, dealing with suppliers
whose service has been limp, I have been able to get a lot of leverage and
a hot line
