Skip to main content
aoler12-Amethyst
12-Amethyst
March 16, 2011
Question

Pro/CABLING - WildFire 5 - User Feedback Requested.

  • March 16, 2011
  • 15 replies
  • 4768 views

PTC & the Routed Systems Technical Committee is looking for Feedback about the NEW Cabling in WildFire 5.


Please provide us with feedback (positive & negative) so future enhancements can be made.


Remember, this is just for WildFire 5 Cabling.


Thanks!


Aron Oler
Routed Systems T/C Chair


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

15 replies

Show previous replies
JimBarrettSmith5-Regular Member
5-Regular Member
March 16, 2011
Ok guys this was exactly what I was looking for a good healthy debate on
the changes and it is the purpose of the meeting, to find out what
assumptions were incorrect.



I was under the impression that you were all following the approved top
down techniques and this is why in wildfire 4.0 we designed the convert
to offset option. I watched customers use the offset command and it
pained me to see how long it took them. Thus we came up with the idea
of "convert to offset" which allowed a user to place locations down very
quickly by selecting on surfaces and creating lots of references. Then
when the harness was complete you were able to delete the references and
have cabling design automatically create the offset locations for you in
the exact location where you wanted them.



The attached movie shows the functionality.



And to be clear I hear and understand your complaint and will address it
but I would be interested if anyone could quantify why the method in the
movie is deemed unacceptable either in time or in time and picks
especially if you are using top down design techniques



Thanks

Jim




swschultz1-Visitor
1-Visitor
March 16, 2011
I personally can't say that I know of any customers that are following some
officially "approved" set of top down design methodologies. In the field
requirements for what really works for TDD can and normally are quite
different than some set of procedures developed in a lab.



Best Regards,



Scott W. Schultz

Principal Consultant

3D Relief Inc.

3700 Willow Creek Drive

Suite 200

Raleigh, NC 27604

(919)259-0610


glfgy7411-Visitor
1-Visitor
March 16, 2011
When and if Lockheed goes to 4.0, this sounds perfect!!!! Great addition....

JeffND1-Visitor
1-Visitor
March 16, 2011
Jim,



I use the insert offset location a lot, to tweak the harness. Very often,
the harness only needs slight adjustment to go around a component. So I
like to start with adding a location at the exact spot where the harness
is currently, and then just slightly alter the dims, to tweak the harness
to route around some component.



Setting the default to 0,0,0 would be bad.



I do also use the top down methodology with copy geoms. I leave them as
copy geoms within a skeleton. I have had good luck with this practice.
Must make sure to set copy geoms as independent.



Regards,
Jeff Roeber

Applied Engineering


dbowles4-Participant
4-Participant
March 16, 2011
Jim,

I was not speaking of Routing the paths of cables via offset csys. But
the ability to add a location via
csys for such oddities as a needed service loop or even to keep the bundle
from deforming over a long stretch.
And when adding such a location in free space keeping the xyz location
given from the default csys.
I do not ever use copy geoms in skeletons, because of the dependencies
(even when set as independent) always create independent surfaces.
Currently working WF 4 just keeping a heads up for WF 5. Looks like the
function is still in place from your video.


Douglas K. Bowles
Advanced Systems Harn/Des
520-665-7082 Office
520-490-9395 Cell
-


PRIVACY ACT NOTICE: This communication may contain privileged or other
Official information. If you are not the intended recipient or believe
that you have received this communication in error, please reply to the
sender indicating that fact and delete the copy you received. It is a
violation of Federal Law to print, copy, retransmit, disseminate, or
otherwise use this information without prior authorization.


Terms & ConditionsAccessibility statement