Skip to main content
M
MIke21-Visitor
1-Visitor
February 21, 2014
Question

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

  • February 21, 2014
  • 2 replies
  • 3715 views

How should a jumper wire in a connector be formated in a NWF? WF4 tells me that the same wire cannot be routed to the same entry port. For every other wire in the wirelist one round designated entry port works find when autorouting, but the jumper wire fails. This is my NWF format for the jumper wire (this format works for every other wire):

NEW CONNECTOR +CIT-RKS2

PARAMETER MODEL_NAME 16087-C

PARAMETER REF_DES +CIT-RKS2

PARAMETER NUM_OF_PINS 1

PARAMETER ENTRY_PORT ENTRY1

PARAMTER GROUPING ROUND

NEW WIRE W7-1_BLK18 18BLK

ATTACH +CIT-RKS2 " " +CIT-RKS2 " "

Its seems as if I need a mutiple entry port format of some sort.

    2 replies

    B
    BrianMartin13-Aquamarine
    13-Aquamarine
    February 24, 2014

    Hi Mike...

    The round entry port should be fine. I would take a closer look at the attach statement in this one. I don't understand the syntax of the "+" signs and the " " (empty double quotes). It's typically:

    ATTACH <From Connector Ref Des> <From Pin> <To Connector Ref Des> <To Pin>

    Your statement seems to be saying the connector name is "+CIT-RKS2" which is something I didn't even know was possible. I didn't think you could use a "+" in the name of a connector. More importantly, there is no pin information at all. If you're jumpering between pin 1 and pin 2, then add those pin names. If this is some kind of weird internal jumper, I'd make up a pin name for them. You can't jump from one pin to the same exact pin... (that's obviously not a jumper) but you can from pin to pin. The problem here (as far as I can tell) is that you have no pins at all.

    Let me know if that makes sense.

    Thanks!

    -Brian

    A
    Anonymous
    February 26, 2014

    "PARAMETER NUM_OF_PINS 1"

    The problem seems to be you can't have a jumper going from the only pin on the connector to itself. The connector is defined as having just one pin.

    Brian

    A different Brian, trying to learn from the Ninja Master

    M
    MIke21-VisitorAuthor
    1-Visitor
    February 26, 2014

    Thanks guys for your suggestions. To re-state my issue. This format works for every wire except a jumper wire in the same connector. The connector name +XXXXX is allowed. If I add multiple pins to a connector then I have to specify the pin # in my wire list for all pins in that connector. It would seem that there should be a way to specify a jumper wire without adding the pin # detail for every other pin. Which leads me to my only issue which is WF4 cabling will fail this wire when attempting to autoroute. It has no problem with reading ATTACH +CIT-RKS2 "" +CIT-RKS2 "" in the NWF. So I believe I will just have to manually route the jumper wires and be done with it..

    B
    BrianMartin13-Aquamarine
    13-Aquamarine
    February 26, 2014

    Hi Mike...

    How did you come up with the format for "Attach" that you're using. Some people manually route wires and then export them as an NWF. Then, they open the NWF, figure out what format Pro/E wants for the NWF, and then mimic that format in their own NWFs.

    The reason I'm asking is that in over 20 years of doing cabling and working with NWF's, I've never seen that empty pin "" configuration. I still believe this is why you're having the problem. If I don't want to mess with numerous pins, I just define ONE pin. Every connector gets at least ONE pin. I've never used a connector without one. When you go to redefine a connector and view the pin information, what does it say if there are no pins specified? I'm really curious because this is something totally foreign to me... and I thought I'd seen everything there was to see with an NWF.

    Right now you have a process that includes using no pin information. That works for you- and I understand that. If you were to try one single pin, that pin would be the same for every connector so there's really no difference in writing ATTACH +CIT-RKS2 1 +CIT-RKS2 1 or ATTACH +CIT-RKS2 "" +CIT-RKS2 ""

    If that works, maybe we have a bug... or maybe the bug is that the 'no pin' configuration works when it should be generating an error?

    Thanks...

    -Brian

    Terms & ConditionsAccessibility statement