: Stuart,
: For your higher complex designs ruled by constraints, Protel is really
: not the tool for the job.
[ . . . snip . . . ]
: For track length measure, yes Protel can give you a total , section or
: segment track length measure. It is not available in the default menus but
: there is a function in the Protel PCB server called
: "PCB:MeasureSelectedObjects". This can be customized into any menu or
: toolbar. Once this function has been customized into a menu or toolbar,
: select the track(s) segment(s) or a whole route using whatever means you
: prefer, click the new server function instruction and you will get an
: accurate measure of the selected track lengths between the two centroids at
: either end of your selection. And yes, I have even checked it's accuracy on
: corners, miters, arcs, etc., It is as accurate as anybody would need for a
: PCB design. In my use I reassigned the Place Dimension button on the
: Placement Toolbar (which I never used) to the new measure function.
Fair enough. Thanks for the info. I have used Protel for exactly
one design so far, so am not a "power user" of the tool.
But how about attaching routing attributes (MATCHED_LENGTH,
DIFF_PAIR, and the like) using a spreadsheet in Protel? (e.g. Like
ePlanner) Is that possible? (Honest question -- I don't know Protel
well enough.) Attaching routing attributes to nets by
hand in a schematic capture package is fraught with the possibility of
error.
One of my beefs with Protel is that it works best when you hold your
design in a "database", instead of in easily accessible ASCII files.
Therefore, you can't really get at your design info using scripts.
This makes it hard to do stuff like e.g. run Perl scripted checks to
see that all your routing attributes are attached to each and every
critical net.
(Yes, it does give you the option of using ASCII files when you create
a design, but I haven't had that much luck with that mode. Either
Protel doesn't work well that way, or my skills with the program are
not up to snuff. I will note that I am not totally inexperienced
[YMMV], so if I can't get a program to work correctly after hacking
around with it for a while, at least some of the blame belongs to the
program.
)
: Lesson: there are some powerful functions in Protel that are not readily
: visible until you get in under the hood and tinker a little. Their
: documentation should really be improved, but we say that about all software
: these days.
I agree that the package is really great for lower end stuff & am not
slagging off Protel (at least too much. . . . .). The OP
was asking about doing optical port cards, however, which usually
implies being able to handle routing constraints easily.
Stuart