Adjusting Hit Targets - Move Speed

[NCHITEL]

Running 2020 on a Global (slow model).

Was finishing up a program today, and had to adjust two hits hit targets on a plane (X, Y, and Z), just a little bit.

Went to run through the program again to make sure it was all tidied up, and noticed that the machine is now moving at snail speed for that plane - I did adjust the move speed to max speed for that feature with but nothing changed.

What am I missing?

[Mike Ruff]

When you say you "adjusted it to max speed for that feature," what did you do? The MOVESPEED command is either a percentage of max speed (where max speed would be 100) or is the actual value of the movespeed in mm/sec. If you hit F5 and go to the Part/Machine tab, you will see a checkbox called "Display Absolute Speed." If unchecked, it will be in percentage, if checked, it will be the actual value of the movespeed in mm/sec.

[NCHITEL]

When you say you "adjusted it to max speed for that feature," what did you do? The MOVESPEED command is either a percentage of max speed (where max speed would be 100) or is the actual value of the movespeed in mm/sec. If you hit F5 and go to the Part/Machine tab, you will see a checkbox called "Display Absolute Speed." If unchecked, it will be in percentage, if checked, it will be the actual value of the movespeed in mm/sec.

It’s set for 254mm/sec.
Im unsure exactly how fast it’s moving when executed, but if I had to guess it’s less than 10mm/sec.

[Schlag]

You confusing Movespeed ( rapid ) with Touchspeed ( feed rate ) ?

[DAN_M]

MOVEDPEED is the parameter that effects how fast your CMM will move. If you hit F5, you'll see a box that looks like this:
pic group.JPGhttps://www.pcdmisforum.com/image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==

"Display absolute speeds" is where I need your attention.
-If that box is CHECKED, PC DMIS will read MOVESPEED commands in your program as an ABSOLUTE VALUE.
-If that box is NOT CHECKED, PC DMIS will read MOVESPEED commands in your program as a PERCENTAGE OF YOUR CMM'S OVERALL POSSIBLE MOVESPEED AS DETERMINED BY YOUR CMM'S CONTROLLER

If the box is checked, and your movespeed is set to 100, and your CMM is capable of moving 300mm/sec, your CMM will move at exactly 100mm/sec.

If the box is NOT checked, and your movespeed is set to 100, and your CMM is capable of moving 300mm/sec, your CMM will move at exactly 300mm/sec.

Once you have a firm understanding of the two different ways the software gives you to control movespeed (please reach out if you need more help), YOU the programmer now get to decide which one you'll stick with.

My recommendation would be use the absolute value method. As your programs get more advanced, you might want the ability to completely control how fast you're going.
If you're writing basic programs, the percentage method works fine. Just set everything to 90. (just because your car CAN go 140mph doesn't mean you redline the thing all day long, you'll kill it, cmm is the same thing).


The machine moves around at movespeed. It will approach the part to take a datapoint, will stop at the prehit zone for a split second to allow the machine to backlash, will go to the retract zone at touchspeed, then will resume traveling at movespeed until it gets to the next prehit datapoint zone.

[NCHITEL]

You confusing Movespeed ( rapid ) with Touchspeed ( feed rate ) ?

No, I understand the difference between the two - 99% of the program, the CMM is moving at 254mm/sec, even between hits of a feature. As soon as I adjusted the hit targets (2 out of 4), the move speed between the respective hits decreased immensely.

[ogcharliebrown]

If it's just that feature can you just rewrite that part of the program? When I have issues with a feature I'll just rewrite that part of the program.

[Zero_micron_filter]

Sounds to me, like the nuimber one I.T. suggested fix. Re-start PC-DMIS, re-try, if that doesn't work, re-start / re-home the CMM and PC-DMIS. I had an operator fix just that sort of an issue this morning by doing that.

[LaserJay]

Yeah definitely try a restart. When in doubt, close it out. That is always my go to when PCDMIS is doing something unusual that I cant seem to fix.

Funny story that is totally unrelated. We are talking about move speed and it reminded me of this.
I moved to a new company a few years ago and their CMM was running so slow, like slower than a turtle. The programmer that was in there had convinced everyone that that is how fast the CMM needed to run for the best accuracy. No one was there to challenge him because he was the only programmer and only person that knew CMM at all. We finally found out he had actually gone in to the settings editor (Probably a bad idea in the first place unless you really know what you are doing) and governed the CMM to like 5%. Thankfully I was able to get rid of that guy! He would just sit there and cook the clock for 60+ hours a week. Terrible!

[Douglas]

I have found a partial execution after edits can slow speed like that, the next full execution will usually take care of it when so