hexagon logo

Anyone else have issues with "Move Increment" command?

Hi,

I'm currently running PCDMIS 2022.2.  I moved from 2011MR1 to this version in one fell swoop.  My question is, does anyone know if anything has changed since 2011 that causes the software to not play well with back-to-back "Move Increment" commands?

I utilized these commands back-to-back for years on 2011 and NEVER had an issue.  In 2022 it would appear that PCDMIS is executing the back-to-back commands simultaneously.

For example:

MoveIncrement (0,0,-.500)

MoveIncrement (.125,0,0)

moves like this " \ " rather than like this " L "

Thanks!

Parents Reply Children
  • the other reason for changing to point over increment is I work in sheet metal, and when first hit part (as in, new tool, never before made parts) if the part is bad enough (and often they are) moving incrementally from where the probe ends after a touch could have crash potential.  Say the part is under-bent by 10mm (it happens) so you have to increase the prehit/retract to be able to measure the point (instead of 3), then there is an extra 7mm of retract before it starts the incremental move.