11 Replies Latest reply on Jan 15, 2014 3:08 PM by Richard Doyle

    Blind C'bores?

    James Pare

      Has anyone ever used a c'bore for a screw using a blind hole?

      This seems like a silly mistake

      Altelast default c'bores to through all!

        • Re: Blind C'bores?
          Steve Calvert

          We use them every once in a while when we attach two parts together but don't want a thru hole.  Either with a plastic thread cutting screw or a metal thread cutting screw.

           

          Steve Calvert

          • Re: Blind C'bores?
            Richard Doyle

            Hi James:

            Sticky.jpg

             

            I tested the setting for end condition on c'bores, and the settings will stay - even across multiple sessions.

             

            2014 SP2.0

             

            Richard

            • Re: Blind C'bores?
              Jody Stiles

              Hi James,

               

              The methodology for the persistent end condition is to maintain the setting from Hole Wizard session to Hole Wizard session and from hole type to hole type within the same session.  It appears to be working as intended and seems to cover the needs of the majority of the user base.

               

              With that said, I understand your desire to be able to always have an end condition applied to a specific hole type, in your case Counterbore should always be Through All.  It is something we are aware of and we've gotten this request before where users want to be able to set the default values for every hole type and setting in Hole Wizard.  You can vote for the SPRs noted below (hopefully the links work):

               

              SPR 626164

              SPR 718932

               

              Jody

                • Re: Blind C'bores?
                  James Pare

                  Jody - here's my thoughts

                   

                  1st - the hole condition is not persistent, c'bore a hole (with thru all) ,change to tap a hole, now go back & c'bore is back to blind

                   

                  2nd - I can guarantee the 99% of your users will have to change this setting 99% of the time they use this feature

                   

                  3rd - The c'bore condition is based off either SHCS, BHCS & so on, how is blind even an option for this, it doesn't match up to the hardware?

                   

                  4th - This will lead to mistakes & problems which will cost your customers money to fix, we have already had designers not notice the logic change in 2014 & have put in blind holes where thru holes are required. THIS WILL LEAD TO MISTAKES!

                    • Re: Blind C'bores?
                      Jody Stiles

                      HI James,

                       

                      Several of us tried to reproduce the issue you're having with the end condition not sticking and we can't get it to happen.  We've tried 2014 sp0, sp1, and sp2.  The workflow we are using is as follows:

                       

                      Workflow 1 (happening in a single HW session)

                       

                      1. Start a HW c'bore hole with Thru all end condition
                      2. Change hole type to tapped hole, Thru all end condition is still active (working as expected)
                      3. Change back to c'bore hole, Thru all is still active (working as expected)

                          

                      Workflow 2 (happening in a single HW session)

                      1. Start a HW c'bore hole with Thru all end condition
                      2. Change hole type to tapped hole, Thru all end condition is still active (as expected), change end condition to Blind
                      3. Change back to c'bore hole, Blind is now active (working as expected)

                          

                      Workflow 3 (happening between HW sessions)

                      1. Create a HW c'bore hole with Thru all end condition and place it
                      2. Exit the PropertyManager
                      3. Start a new HW hole, Thru all end condition is still active (working as expected)

                       

                      If different from those listed above, can you reply with the workflow you are using to cause the issue you are seeing?  If you are using one of the above workflows, please submit a bug through your reseller so our tech support team can take an more indepth look at it.

                       

                      And please do vote for the SPRs if they would get you the control you are looking for.