Quantcast
Channel: PTC Community: Message List
Viewing all articles
Browse latest Browse all 11560

Re: Problem with jumper wire in NWF (neutral wire file) in WF4

$
0
0

Hi Mike...

 

There's a bit of a tweak you can use in your plan of having two pins. You could call one pin "Pin 1" and call the second one "Pin Jumper". It's little known outside of those using Creo Schematics but you're not limited to giving pins numeric names. You can call a pin "jumper" then your attach statement would read:

 

NEW WIRE W7-1_BLK18 18BLK

ATTACH   +CIF-RKS2    1    +CIT-RKS2    Jumper

 

I added some spaces so you can see the 4 parameters used for the attach command more clearly. Also, you do not need to put double quotes around your pin names. It's a minor point but anything you can do to simplify the NWF and the creation of it saves time.

 

If you decide to call your jumper pin jumper that kind of makes the NWF file easier to read later. It sort of "self-comments" what you're trying to do.

 

On a unrelated note... I have a new tool I've been writing and testing. It's an NWF creation tool. Right now it's still in the development phase. The intent is for you to create your commonly used spools and connectors and save them to a database (through the tool interface). You can define them on the fly, too but I assume most people would want to save their common objects for reuse later. Then, you create a new harness "project" by pulling in the connectors and spools you need and then specifying the From/To connector information. The From/To data can be entered manually from the interface or read in from Excel, Access, Word, Mentor Graphics, or a text file. As a last step, you export an NWF file and use that as your logical reference in Creo. This would be for people who don't use Creo Schematics obviously.

 

Would this be something you'd be interested in trying out? As soon as I have some beta code to test, I'll need some people familiar with NWF's to test the tool to insure it's generating the anticipated output. Once I get the NWF part working, I'm going to add support for XML, too. That would be a better interface option but I want to dig through Creo Schematics to make sure I can output the same data it can export. This isn't a replacement of Schematics. Instead. it's a tool to assist the majority of people who do not use it but still want to autoroute in Creo Cabling without the hassle of learning or editing an NWF.

 

Let me know your thoughts!

 

Thanks,

-Brian


Viewing all articles
Browse latest Browse all 11560

Trending Articles