6 Replies Latest reply on Aug 19, 2010 8:05 AM by sking

    Ring Terminals and Workflow


      Hello All,


      I have what I wouldn't think would be to unique of a problem.  First of all, we use a lot of ring terminals.  It is not uncommon for one of our harnesses to have over 100 of them  And since VeSys does not support ring terminals natively, I have had to come up with a work around.  First I will detail what that is and the good and bad of it.


      I created a device, called terminal.  Most of our terminals are #10 studs.  We have a habit of putting way too many terminals on a single stud.  The  device is just a circle with a pin every 90 degrees.  I then place a footprint on each of these pins that would call out a connector called term_ring_10.  This connector does not go in the BOM and has one cavity that calls out ring terminals for a #10 stud for all of the different wire sizes..  This works fairly well.


      Next step is we are in the process of trying to pass info to Pro/E to model the harness.  That is where the stumbling block comes in.  When the NWF file for Pro/E is created, it only passes the connectors, not the pins.  Probably because the pins do not get processes until we get to Harness and Cavity Component Management.


      So in my mind, one of two things need to happen.  Cavity Component Management could be added to design or add the ability to export to NWF in the harness package.


      What do you all think?

        • 1. Re: Ring Terminals and Workflow


          I think a picture showing what you have done would be nice. As for the footprint connector, why not define a separate connector for each pin on the device (maybe that is what you did).

          As for the Pro/E question, I will forward this thread to a colleague.



          • 2. Re: Ring Terminals and Workflow



            pic1 is a single terminal post.  There is 4 pins, one each at 0, 90, 180 and 270.  The terminal post has a footprint with a different connector at each pin.  The connector part number is TERM_NO_10, which has all ring terminals for a #10 size post.

            pic2 is the entire terminal strip, which is a composite symbol, made up of 20 of the terminal posts.


            These can be added to a design as either a single post or an entire terminal strip.


            Thanks for the help

            • 3. Re: Ring Terminals and Workflow



              Are you using device connectors or a harness connector?  Maybe we should have a quick WebEx.

              • 4. Re: Ring Terminals and Workflow

                Hey Nuri,


                  I am using these as device connectors.  That way, I do not have to create the harness connector and associate with a harness.  Also, creating the harness connector would take up unnecessary room.

                • 5. Re: Ring Terminals and Workflow

                  Hi Guys


                  Sorry for pushing in - I just wonder if this similar thread might help?




                  It references an admitedly CHS methodology that sounds similar to your suggestions.




                  • 6. Re: Ring Terminals and Workflow

                    Hi Russell,


                      Yes, yes, yes that is exactly how I do it.  I define a dummy connector for a particular size stud on a terminal, do not include the dummy connector in the BOM, and use a device footprint to determine which terminal to call out for that particular wire.  It all works as planned.

                      The downside is that when you export the nwf file to Pro/E, none of those decisions (Cavity Component Management) have been made as you are exporting from design.  All you get are the connectors, not any underlying components.  Now maybe if you could export the nwf from Harness after all decisions have been made.