A Bunch of Noob Questions

[RanDawgg]

I think I have some very basic questions, I'm hoping some of you can help me out.

1. When I measure an OD, PC-DMIS automatically puts circular moves in between each point. However, it still crashes into the part instead of rotating around it properly. Right now, I'm putting clearance moves in between each move to mitigate this (lol).
2. How do you add clearance moves to points in an auto feature? Sometimes there is a spring/clamp in the way. Or is there a way to have the points displayed in the edit window like non-auto features?
3. Is there a way to update nominal values quickly? Like if I wanted to make a section of points all have the same Z value, as opposed to changing them one by one. Calypso has a "feature settings editor" or the "highlight" tool, which was great for this.

These are the ones bugging me right now. Thanks in advance guys. Maybe one day I'll get sent to training...

[louisd]

1. If your equipment is older, (like my old DEA Scirocco, circa 1999 I believe) move/circular does not work. the controller doesn't know how to do it. You could increase your prehit/retract distance for circular moves, or increase point density as a simple workaround for this.
2. Once you have your initial alignment set, you can define a Clearp/Zplus/x inches clearance above your Z level plane/zplus/0 then insert move/clearplane commands into the routine by either typing move/clearplane into the edit window where you want it to be placed, or within the autofeature, there's a checkbox for move/clearplane, which will automatically insert the line into your code once you create the autofeature.
3. You can click within the menu bar EDIT -> Find and Replace -> Replace. works just like any other find and replace tool in excel or word.

[RanDawgg]

Thanks for the reply!
1. The CMM is brand new. It seems strange that it doesn't work, when the machine obviously knows the size of the OD it is measuring.
2. That seems to put a clearance move right before the feature is measured. Is there a way to put clearance moves in between specific points of the auto feature?
3. Looks like I need to read up on this one.

[louisd]

For #1: if the CMM is brand new, you either don't have circular moves turned on within auto-feature creation (another icon you click mid-window), or there's some conflict in the hardware parameters.

For #2: if you want clearance moves between points you can use a constructed circle, add move/clearplane between each hit. for instances like this i switch the constructed circle to polar coordinates and manually change nominals of each hit... (spread the hits 360 divided by # of hits = equal spacing polar angle... to make sure they are equally spaced)

for #3, you can literally just replace the dimensional values that are in blue text within the edit window (these are the theoretical/nominal values and hit target values)

Also for #3 but more advanced: SAVE A COPY of your routine prior to playing with this: you can create an alignment (CTL+ALT+A) before you want to move nominals a set value, then create another where you want the nominal shift to end (recalling your prior alignment)... Then within the move nominal alignment, transform your origin x y or z by a set value, then say no, don't update nominals... Now, delete that alignment and select YES update nominals. Voila every feature within your two alignments just slide over, by your stated value.

[kingsld1]

Never thought about using alignments to shift features. My method of choice has been to use paste with pattern and then delete the original features.

[Jambo The Rambo]

What feature are you using to measure the OD?

[RanDawgg]

I used a measured circle, not an auto circle. It clearly states between each point that there is a circular move, but it just rushes to where the next point is. I also have OD checked within the feature.

[Mike Ruff]

For a measured circle, you can change the MOVE/CIRCULAR to MOVE/CLEARPLANE in between each hit as long as you have a clearplane defined as louisd described above. This will make it come up to

[sealevel]

Here's a question for Q#1.
If using auto-feature, did you let the Demon know its an OD (not ID) ??

[kingsld1]

For question 2, You could use measured features instead of auto featues. You can click right where you want the points to be. Or just take the minimum number of hits and then change the number of hits to what you want and they'll be evenly spaced. You can edit the feature to your hearts content. Insert move points, clear planes,probe rotations, comments. In many ways manual features are as versatile if not more so than auto features

[RanDawgg]

Originally, I thought the "auto features" would be the only set of features I would use (if using a CAD model). Now I'm starting to see that they are all viable.

[Disal]

For#1 - I don't know if this will help you-but for me sometimes i need to set a larger prehit/retract distance for ODs, i had the problem where tip would crash even with circular moves on and this has helped me a lot

[RanDawgg]

I believe I found exactly what I wanted for #2. There is a line of code in the auto feature titled "SHOW CONTACT PARAMETERS=NO". If you make that yes, several other lines of code show up, ending with one that reads "SHOW HITS=NO". If you make that one say yes, then the probe hits are displayed like a measured circle. You can add any positional moves inside here.

As of now, I'm just using clearance moves for #1. It's actually faster than upping the the prehit/retract distance.

Thanks for the help everyone!

[louisd]

huh, if that's the case, that is a newly improved feature. previously you couldn't insert anything within the auto feature hits!

[AndersI]

I think it has been there for quite a while. Note: MOVE points only, don't try to select another tip [angle]!

[constadin]

Here's a question for Q#1.
If using auto-feature, did you let the Demon know its an OD (not ID) ??

Make sure that you have indeed declare it to be an outside circle and not an inside as prementioned

[RanDawgg]

To those that care, 2018 R1 introduced a "To Points Toggle" in the auto feature for Plane, Circle, and Cylinder. This transforms all of the hit points into vector points, and then you can construct those into whatever you need! Pretty cool feature.

https://support.hexagonmi.com/s/article/PC-DMIS-2018-R1-New-AutoFeatures-Point-Selection-for-Constructions-and-Dimensions-1527312552975

[CarbideEVO]

Yeah, I use this feature often for the situations referred to by OP. It's often faster and less cumbersome to switch to points versus trying to use Void Detection

[RanDawgg]

One more noob question. Say I have a datum scheme like this: A datum=Plane, B datum=Circle, C datum=Circle. C datum would constrain the last rotation. Do I have to construct a line from B to C to do this properly? Whenever I select just the circle for the last rotation, it throws the entire rotation off by like 45 degrees. I'm assuming it doesn't work because of the vector direction of C, but doing this method in Calypso works just fine. Just curious! Thanks.

[louisd]

rotating about a line constructed between centroids of B and C is the rock-solid method. I honestly haven't ever attempted anything else.

[Peter Fuller]

In your alignment, select both B and C using the control button on the keyboard and rotate to that. PC-DMIS should handle it properly at that point.

[RanDawgg]

Thanks guys.

[vpt.se]

To those that care, 2018 R1 introduced a "To Points Toggle" in the auto feature for Plane, Circle, and Cylinder. This transforms all of the hit points into vector points, and then you can construct those into whatever you need! Pretty cool feature.

https://support.hexagonmi.com/s/arti...-1527312552975

Thank you. Yes - it is very useful. The idea came from an old VB executable that exploded the feature into vector points. At some point in the Windows update race this executable stopped working. I created the first spawn (PC-DMIS script) and released it on this forum where others contributed with their version of the script. I finally submitted it as a suggestion on the PC-DMIS Idea Center that was liked enough by other users (voting system) so it was introduced as an actual function into PC-DMIS.

[A-machine-insp]

I have noticed that circular moves no longer work once you use To Points Toggle. Is there a way to make circular moves work when using To Points?

[vpt.se]

No, it only handles the actual hits and converts them to points. It was never the intention to include the path between the points/hits.

But, file this as a suggestion at the Idea Center and it might pick up enough traction to be included in a future release!