7 Replies Latest reply on Jun 29, 2015 4:05 AM by Vincent_Pinto

    Defineing entry port names for Creo 2.0

    lgalantai

      Hi!

       

      I`m trying to make a 3D cabling diagram, from a VeSys wiring design, and I can`t find a way to define a connectors ENTRY_PORT property correctly. Normally, if I export a design to .nwf, the ENTRY_PORT property has a value "EP" (for all pins). I tried to make a property code named ENTRY_PORT, and add it to the connector pins (i was able to do this, but its really slow, and I would have to do it in every design again and again, but...) If I did this, in the .nwf file, the ENTRY_PORT values changed to the ones I defined, but another property with the same name, was added, with the same value. So it seems, VeSys defines the ENTRY_PORT property for the pins somewhere, but I can`t find, where, and how to edit the value of it. The same thing happens with the INTERNAL_LEN property, it has a default value, of "0" and if I add a property to each of the pins with the same name, it appears in the .nwf file duplicated, but in this case, the "original one" remains "0" and the second one has the value, I added. Please see the pictures below, for better understanding.

       

      VeSys exports to .nwf normally like this:

       

      normal nwf.PNG

       

      It should be something like this (I manually overwrote the file, in this format it`s fully compatible with Creo):

       

      shouldbe nwf.PNG

       

      If I define ENTRY_PORT property for each pin:

       

      PIN.PNG

       

      definedentrryport.PNG

       

      So, it would be great to store this ENTRY_PORT information, in the component library, so if I add a library part to a connector it automatically define the entry port names/values. But now, I simply cant find how to edit this parameter. Please help me with this problem!

       

      Regards,

      Lac

        • 1. Re: Defineing entry port names for Creo 2.0
          Vincent_Pinto

          You can create the ENTRY_PORT property in VeSys Components just as you'd create any other property.

           

          In VeSys Components, using the Property Codes dialog, you'd first create a property ENTRY_PORT.  Then, with the Properties for Type Code dialog, you'd assign that ENTRY_PORT property to the Type Code for the component you are working with, say CONN, or CONM, or CONF, or SPL (connector and splice type codes).  The property can now only be assigned to those objects belonging to the Type Code you assigned them to.  Edit the connector or splice component, and in the Properties tab, add the property you just created, and give it a value of the csys name (no spaces) that you intend to be the the entry port in the Creo part.

           

          Once you've done this for all your components, in VeSys Design, after you've done File > Refresh > Library Parts, do Actions > Update > Batch Update Library Parts.  This will bring the newly added property-value pair into the individual instances where you've assigned part numbers.  Look in the Properties tab of one of the instances, and you'll see the prop-value.

           

          Bridge out the nwf file. You'll see that each pin is assigned the same single entry port. We strongly recommend that you use this approach to route multiple wires to a single csys because the Creo plugin does not support wires routed to individual cavities (csys').

           

          INTERNAL_LEN is hardcoded to 0, because the extra length you need is defined as add-ons in the Base tab of the component and will be used in VHarness when you calculate Wire lengths. GROUPING is always ROUND as we don't support RIBBON.

          • 2. Re: Defineing entry port names for Creo 2.0
            lgalantai

            Hi!

             

            Thank you for the fast answer!
            The problem with this solution is, that every pin will have the same ENTRY_PORT value. But for a connector with 10 pins we have to use 10 different ENTRY_PORT (csys`) names/values, in Creo, so it can route the wires to the proper cavity. So the model will have 10 csys` with different names/values, according to the pin number of the additional connector (for example on the picture below you can see the model of a  2pin molex 5557 connector in Creo, we defined the connectors pins as ENTRY_1 and ENTRY_2).

             

            ENTRy_PORT.jpg

            If I manually overwrite the .nwf file (PIN1 ENTRY_PORT ENTRY_1 and same for PIN2 with ENTRY_2), Creo will route the wires to the correct cavities automatically. This is important, because we want to use Creo cabling to make harness designs, from the 3D cabling, using the flatten ability, and the table information will be generated from these connections (I assume, we didn't  try it yet, we're trying to make the VeSys -> Creo Flow work correctly first).
            Is there a possible way to give each pin a different ENTRY_PORT property value?

             

            Lac

            • 3. Re: Defineing entry port names for Creo 2.0
              Vincent_Pinto

              Unfortunately, no; not in the exact way you want it. However, if you are willing to do something slightly differently, then it is possible.

               

              When you assign the ENTRY_PORT to a connector part number, don't give it any value. When you do the Refresh and Update in VDesign, in the connector's Properties tab, you will have ENTRY_PORT with no value.

               

              When you export the nwf, each pin will be given an entry port value equal to the pin name.  This means that you will need to update the csys' in your connector.prt to the pin names of the part number you defined in VComponents.

               

              As indicated earlier, if you use this approach, and you use the Creo plugin to export an xml for use in VHarness, the connectors will not be hooked up to the bundle ends. This is because the network is not connected to a single csys in CREO, because your intention is to route individual wires to individual csys' in CREO.  Also, any PARAMETERs you want to see in your CREO harness will need to be present in the Properties tab of the objects (wires, multicores, splices, and connectors).   And as you are aware, the nwf format does not support nested levels in a multicore.

              • 4. Re: Defineing entry port names for Creo 2.0
                lgalantai

                Hi!

                The solution you've described, would be great, but unfortunately it writes an error, so I can't make it work. The error massage is shown below.

                 

                And yes, I'm aware that the .nwf format has restrictions, but I hope it will work properly anyway.

                 

                Lacproperty_problem.JPG

                • 5. Re: Defineing entry port names for Creo 2.0
                  Vincent_Pinto

                  It could be that the connector part is already assigned to connectors in your VDesign (although I am not sure why that should matter; it ought to be possible to change the value). Can you please unassign the the part number from all instances, do a Save of the design, restart VComponents and try again?

                   

                  If this doesn't work, try deleting the property. Then do a Refresh and Update in VDesign. You can now clear the value in the Properties tab of the instance.

                   

                  For other parts, because you are not interested in routing wires to one csys, you need not create an explicit property at the part level. In VDesign, simply select all of the connectors, splices, right-click, Properties, and in the tab manually create ENTRY_PORT and leave it blank.

                  • 6. Re: Defineing entry port names for Creo 2.0
                    lgalantai

                    I've tried to unassign the connectors from the component, but it didn't worked. Then I made a totally new component, which is not assigned to anything in any way, but it didn't work that way either.

                     

                    But the second solution you've described works, and it's still faster than defining each pin. I will try it in the 3D cabling, and if it works this way, I will mark your answer correct.

                     

                    Thank you,
                    Lac

                    • 7. Re: Defineing entry port names for Creo 2.0
                      Vincent_Pinto

                      Please file an SR for your first para. Something is not right there.