Angles

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Angles

    2 measured lines should be 20°. PC-DMIS shows, when I add the dimension, the nominal of 20° however when this is output onto the report the dimension is either 270°, 70°, sometimes 340° and shown OOT.

    I cannot for the life of me get this to just report the plain old 20°.

    I've gone about every aspect I can think of to get this to just report the 20°. I've offset my alignment 22.5°, 45°, 67.5°, 90°, 112.5°, 135°, 157.5°, 180°, changed line directions, to / from, flipped work planes, 2D & 3D... everything I can possibly think of and it just won't report 20°.

    PC-DMIS CAD++ 2018 R2
    Jesse Krook

  • #2
    when you get 340 , try clicking the supplemental box

    Comment


    • YGOLORTEM
      YGOLORTEM commented
      Editing a comment
      Not it. Like I said, I've tried everything.

  • #3
    Hit F5, then go to Dimension tab, on the bottom right change it to "0 to 360".

    Comment


    • #4
      Originally posted by bfire85 View Post
      Hit F5, then go to Dimension tab, on the bottom right change it to "0 to 360".
      That's what I keep it set at. When I switched it to ± 180° it switched from 290° to -70°.

      When I dimension this the nominal automatically populates to 20° but when it's reported I get everything in 20° increments from 90° and 270° except 20°. That's why I rotated my alignment looking for that sweet spot. It just won't give me 20°
      Last edited by YGOLORTEM; 06-16-2020, 04:47 PM.
      Jesse Krook

      Comment


      • #5
        Check your workplanes as well.

        Comment


        • #6
          Originally posted by acgarcia View Post
          Check your workplanes as well.
          That was my next suggestion.

          Comment


          • #7
            Maybe try reversing one of the lines?

            Angle dimensions are probably the least intuitive of all PCDMIS dimensioning.


            B&S CHAMELEON/PCDMIS CAD++ V2011

            There are no bugs, only "UNDOCUMENTED ENHANCEMENTS!"

            sigpic

            Comment


            • #8
              Another way I've done it in the past and I'm thinking this was done in V3.7MR4


              Code:
              WORKPLANE/XPLUS
              P1 =FEAT/CONTACT/VECTOR POINT,CARTESIAN
              THEO/<1.93,0.168,1.687>,<0,-0.9890159,0.1478094>
              ACTL/<1.93,0.168,1.687>,<0,-0.9890159,0.1478094>
              TARG/<1.93,0.168,1.687>,<0,-0.9890159,0.1478094>
              SNAP=YES
              SHOW FEATURE PARAMETERS=NO
              SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=NO,DISTANCE=0
              SHOW HITS=NO
              P2 =FEAT/CONTACT/VECTOR POINT,CARTESIAN
              THEO/<1.93,0.182,1.779>,<0,-0.9890159,0.1478094>
              ACTL/<1.93,0.182,1.779>,<0,-0.9890159,0.1478094>
              TARG/<1.93,0.182,1.779>,<0,-0.9890159,0.1478094>
              SNAP=YES
              SHOW FEATURE PARAMETERS=NO
              SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=NO,DISTANCE=0
              SHOW HITS=NO
              P3 =FEAT/CONTACT/VECTOR POINT,CARTESIAN
              THEO/<1.93,0.195,1.87>,<0,-0.9890159,0.1478094>
              ACTL/<1.93,0.195,1.87>,<0,-0.9890159,0.1478094>
              TARG/<1.93,0.195,1.87>,<0,-0.9890159,0.1478094>
              SNAP=YES
              SHOW FEATURE PARAMETERS=NO
              SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=NO,DISTANCE=0
              SHOW HITS=NO
              LIN1 =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
              THEO/<1.93,0.168,1.687>,<0,0.1478115,0.9890155>
              ACTL/<1.93,0.168,1.687>,<0,0.1478115,0.9890155>
              CONSTR/LINE,BF,2D,P1,P2,P3,,
              OUTLIER_REMOVAL/OFF,3
              FILTER/OFF,WAVELENGTH=0
              F1 =GENERIC/NONE,DEPENDENT,CARTESIAN,OUT,$
              NOM/XYZ,<1.93,0.168,1.687>,$
              MEAS/XYZ,<LIN1.X,LIN1.Y,LIN1.Z>,$
              NOM/IJK,<0,0,1>,$
              MEAS/IJK,<0,0,1>,$
              DIAMETER/0,0,$
              ANGLE/8.5,RAD2DEG(ATAN(LIN1.J/LIN1.K)),$
              DISTANCE/0,0
              Xcel & MicroVal Pfx & Global 37mr4 thru 2012mr1sp3
              Contura Calypso 5.4

              Lord, keep Your arm around my shoulder and Your hand over my mouth. Amen.

              Comment


              • #9
                Are these constructed lines with just 2 points? if so, try reversing the order on 1 of the lines. Like if pnt1 and pnt2 make the line, flip it to where pnt2 is selected first and then pnt1.

                Comment


                • #10
                  It doesn't do a good job of giving complementary angles, just supplementary. Rotate to one of the lines, then ask for the angle of the other to either the X or Y axis.

                  EDIT: Example

                  Code:
                  LIN1 =FEAT/LINE,CARTESIAN,UNBOUNDED
                  THEO/<0,0,0>,<1,0,0>
                  ACTL/<0,0,0>,<1,0,0>
                  MEAS/LINE,2,ZPLUS
                  HIT/BASIC,NORMAL,<0,0,0>,<0,1,0>,<0,0,0>,USE THEO=YES
                  HIT/BASIC,NORMAL,<2,0,0>,<0,1,0>,<2,0,0>,USE THEO=YES
                  ENDMEAS/
                  LIN2 =FEAT/LINE,CARTESIAN,UNBOUNDED
                  THEO/<0,0,0>,<0.3420201,0.9396926,0>
                  ACTL/<0,0,0>,<0.3420201,0.9396926,0>
                  MEAS/LINE,2,ZPLUS
                  HIT/BASIC,NORMAL,<0,0,0>,<-0.9396926,0.3420201,0>,<0,0,0>,USE THEO=YES
                  HIT/BASIC,NORMAL,<0.684,1.8794,0>,<-0.9396926,0.3420201,0>,<0.684,1.8794,0>,USE THEO=YES
                  ENDMEAS/
                  DIM DIM_1= 2D ANGLE FROM LINE LIN1 TO LINE LIN2 ,$
                  GRAPH=OFF TEXT=OFF MULT=10.00 OUTPUT=BOTH
                  AX MEAS NOMINAL +TOL -TOL DEV OUTTOL
                  A 70.0000 70.0000 0.0004 0.0004 0.0000 0.0000 ----#----
                  A1 =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
                  ALIGNMENT/ROTATE,XPLUS,TO,LIN2,ABOUT,ZPLUS
                  ALIGNMENT/END
                  DIM DIM_2= 2D ANGLE TO LINE LIN1 FROM YAXIS ,$
                  GRAPH=OFF TEXT=OFF MULT=10.00 OUTPUT=BOTH
                  AX MEAS NOMINAL +TOL -TOL DEV OUTTOL
                  A 20.0000 20.0000 0.0004 0.0004 0.0000 0.0000 ----#----
                  Last edited by RandomJerk; 06-17-2020, 10:23 AM.

                  Comment


                  • #11
                    Originally posted by dwade View Post
                    Another way I've done it in the past and I'm thinking this was done in V3.7MR4


                    Code:
                    WORKPLANE/XPLUS
                    P1 =FEAT/CONTACT/VECTOR POINT,CARTESIAN
                    THEO/<1.93,0.168,1.687>,<0,-0.9890159,0.1478094>
                    ACTL/<1.93,0.168,1.687>,<0,-0.9890159,0.1478094>
                    TARG/<1.93,0.168,1.687>,<0,-0.9890159,0.1478094>
                    SNAP=YES
                    SHOW FEATURE PARAMETERS=NO
                    SHOW CONTACT PARAMETERS=YES
                    AVOIDANCE MOVE=NO,DISTANCE=0
                    SHOW HITS=NO
                    P2 =FEAT/CONTACT/VECTOR POINT,CARTESIAN
                    THEO/<1.93,0.182,1.779>,<0,-0.9890159,0.1478094>
                    ACTL/<1.93,0.182,1.779>,<0,-0.9890159,0.1478094>
                    TARG/<1.93,0.182,1.779>,<0,-0.9890159,0.1478094>
                    SNAP=YES
                    SHOW FEATURE PARAMETERS=NO
                    SHOW CONTACT PARAMETERS=YES
                    AVOIDANCE MOVE=NO,DISTANCE=0
                    SHOW HITS=NO
                    P3 =FEAT/CONTACT/VECTOR POINT,CARTESIAN
                    THEO/<1.93,0.195,1.87>,<0,-0.9890159,0.1478094>
                    ACTL/<1.93,0.195,1.87>,<0,-0.9890159,0.1478094>
                    TARG/<1.93,0.195,1.87>,<0,-0.9890159,0.1478094>
                    SNAP=YES
                    SHOW FEATURE PARAMETERS=NO
                    SHOW CONTACT PARAMETERS=YES
                    AVOIDANCE MOVE=NO,DISTANCE=0
                    SHOW HITS=NO
                    LIN1 =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
                    THEO/<1.93,0.168,1.687>,<0,0.1478115,0.9890155>
                    ACTL/<1.93,0.168,1.687>,<0,0.1478115,0.9890155>
                    CONSTR/LINE,BF,2D,P1,P2,P3,,
                    OUTLIER_REMOVAL/OFF,3
                    FILTER/OFF,WAVELENGTH=0
                    F1 =GENERIC/NONE,DEPENDENT,CARTESIAN,OUT,$
                    NOM/XYZ,<1.93,0.168,1.687>,$
                    MEAS/XYZ,<LIN1.X,LIN1.Y,LIN1.Z>,$
                    NOM/IJK,<0,0,1>,$
                    MEAS/IJK,<0,0,1>,$
                    DIAMETER/0,0,$
                    ANGLE/8.5,RAD2DEG(ATAN(LIN1.J/LIN1.K)),$
                    DISTANCE/0,0
                    When doing this shouldn't the IJK values of the generic feature match those of the actual line?

                    Code:
                    LIN1 =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
                    THEO/<1.93,0.168,1.687>,<0,0.1478115,0.9890155>
                    ACTL/<1.93,0.168,1.687>,<0,0.1478115,0.9890155>
                    CONSTR/LINE,BF,2D,P1,P2,P3,,
                    OUTLIER_REMOVAL/OFF,3
                    FILTER/OFF,WAVELENGTH=0
                    F1 =GENERIC/NONE,DEPENDENT,CARTESIAN,OUT,$
                    NOM/XYZ,<1.93,0.168,1.687>,$
                    MEAS/XYZ,<LIN1.X,LIN1.Y,LIN1.Z>,$
                    NOM/IJK,<0,0.1478115,0.9890155>,$
                    MEAS/IJK,<LIN1.I,LIN1.J,LIN1.K>,$
                    DIAMETER/0,0,$
                    ANGLE/8.5,RAD2DEG(ATAN(LIN1.J/LIN1.K)),$
                    DISTANCE/0,0
                    I appreciate all the input from everyone however when I said I've done everything I truly mean I HAVE DONE EVERYTHING. (ie: workplanes, reversing lines, aligning to lines....so on and so forth)

                    I believe DWADES code is likely to be the answer once I get a couple of bugs worked out of the code.
                    Last edited by YGOLORTEM; 06-30-2020, 06:52 AM.
                    Jesse Krook

                    Comment


                    • dwade
                      dwade commented
                      Editing a comment
                      I've never had an issue with the angles not working correctly using the code I posted

                    • YGOLORTEM
                      YGOLORTEM commented
                      Editing a comment
                      10-4 I have to give it a shot

                    • YGOLORTEM
                      YGOLORTEM commented
                      Editing a comment
                      Thank you dwade

                  • #12
                    To work around this, you could..

                    1) Measure the lines. Stick with the 270° option. Lets say you call it ANGL1. Switch output to NONE.
                    2) Make a generic cone and force the measured value for it's angle to be "270-(ANGL1.MEAS)". Then report the angle of the generic cone and THAT will be your angle between the two lines. Make sure the output is turned back on for this dimension so it shows up on your insp rpt.
                    Last edited by DAN_M; Yesterday, 08:32 AM.

                    Comment


                    • YGOLORTEM
                      YGOLORTEM commented
                      Editing a comment
                      Makes sense I'll give it a try

                    • DAN_M
                      DAN_M commented
                      Editing a comment
                      I have done this many times (today being one of them). Works every time. Goodluck!

                    • YGOLORTEM
                      YGOLORTEM commented
                      Editing a comment
                      Thank you DAN_M

                  Related Topics

                  Collapse

                  • Sl33stak
                    Dimensioning angles
                    by Sl33stak
                    Question,

                    I have a report that dimensions angle in Deg,Min,Sec.

                    I have an engineer that wants ONE of those dimension changed...
                    03-27-2006, 11:21 AM
                  • JoBLOCK
                    Weird dim in my report
                    by JoBLOCK
                    Any one knows how to get rid of those last 2 lines in my report, I only have this in one particular program and I have no clue of what it is and how to...
                    02-09-2010, 09:36 AM
                  • Probe_101
                    Can someone help?
                    by Probe_101
                    2018r2 offline the report window will not scroll past the first page. I have resarted the computer and PC-DMIS. I open the same file in 2018r1 and the...
                    02-23-2019, 09:44 AM
                  • grandpaal56
                    reporting line angles
                    by grandpaal56
                    I am currently running v4.2 MR1. I am reporting the angle of some lines around a circle. I am using constructed 2D lines from the center of the circle...
                    07-23-2014, 09:51 AM
                  • BWilliams
                    Report Information
                    by BWilliams
                    I have been messing around with my report templates, trying to change the logo (which I finally got it to work) but ever since my PPAP report will not...
                    04-26-2007, 02:51 PM
                  Working...
                  X