Error when creating a constructed width

  • Filter
  • Time
  • Show
Clear All
new posts

  • Crosby Smith
    started a topic Error when creating a constructed width

    Error when creating a constructed width

    Hello, I am fairly new to the inspection field and am having some trouble with setting up my datums for a part program.

    There are several slots cut out on a rectangular plate, and the distance between the edges of the slots are the datums. So, in an attempt to create a constructed width to use as my datums, I created lines by taking hits along the edge and selected the option for them to projected onto a feature (a plane along the top face of the plate). I have a picture from the program shown below:


    As you can see, the first constructed width was created without a hitch, but the for the second one (from Lin_A1_2 to Lin_A1_4), PC-DMIS gives the error "Surface vectors are not opposed" and refuses to make the feature. I'm not really sure what this means and am hoping someone can help me through this.

    If it helps, here are the directional vectors for each of the four lines:
    I: 0.002825
    J: -0.9999959
    K: -0.000436
    I: -0.9999944
    J: -0.0031568
    K: -0.0011256
    I: 0.0014157
    J: 0.9999989
    K: 0.0004408
    I: 0.9999808
    J: -0.0060896
    K: 0.0011215

    Only the holes in the picture were machined, the datum features were torch cut and the top of the plate was not faced off (i.e. it was rusted over). I know that's not ideal for making datums, but it was how the print said to do it, and the holes were cut after being lined up along those edges. I'm hoping that the error has nothing to do with that fact.

  • Crosby Smith
    commented on 's reply
    Thank you for your help!

  • michaelwildschutz
    On A laser tracker I am not sure but I would start with when you create the lines or planes to input the vectors there in the construction window before you create each one and yes the feature sets would work the same as a width,i use it alot because widths have some issues when being used (they measure fine and report in legacy fine but there are some other issues that are broken or havent been put in place yet in the background of Pc-Dmis) so they dont allways do what you may think they should

    Leave a comment:

  • Crosby Smith
    commented on 's reply
    I used a laser tracker for those measurements, not an ARM, so I'm not sure if/how the hits would have directional vectors... Would the feature set of the two lines behave the same as a constructed width for GD&T purposes? Thank you for your help.

    Edit: I checked the hit target values for the lines, and you were right about the vectors being an issue. I'll try to explore this more on my own.

    Edit #2: I was able to fix the issue for the lines in the photo, but fixing the problem for the whole part will be quite tedious. Is there any way to control or predict what the hit vectors will be during initial measurements?
    Last edited by Crosby Smith; 02-18-2019, 02:17 PM.

  • michaelwildschutz
    we would need to see the vectors for each basic hit for each line those vectors should be opposing(opposite) for line a1_1 and a1_3.and for a1_4 and a1_2....but widths are funny they dont work for everything.I would suggest making a feature set from each set of lines.....

    Leave a comment:

widgetinstance 190 (Related Topics) skipped due to lack of content & hide_module_if_empty option.