TR_MOV01 Movement interrupted error when scanning

[braulio]

I'm scanning with SP25M sensor several AutoLines and AutoCircles on two cylindrical surfaces (one is an outer surface and the other is an inner surface).
After several parts without fail, it happens that after finishing a certain scan, not always the same one (sometimes is a circular scan, and other times a line scan) the mentioned error arises:
"TR_MOV01 Movement interrupted" and then the command in the execution window is: "Absolute Move to X=...." that corresponds to a ClearPlane move.
I've realised that it usually happens when the movement of the probe after finishing the scan is aligned approximately with the X axis direction.
Is there any known cause for this error?
Thanks in advance.

[JEFMAN]

Maybe a bad vector at the end of the scan ?
Movement (no fly) interrupted due to probe deflection.STATUS Label Error Message no_error : ERROR FLY,S%1,TR_MOV01,Movement Interupted!

Can you post some code ?

[braulio]

Here it is an extract of an AutoLine scan where sometimes the program shows the error:

MOVE/CLEARPLANE
G_0 =FEAT/CONTACT/LINE/ADAPTIVE_LINEAR_SCAN,POLAR,BOUNDED
THEO/<17.5,360,12.5>,<17.5,360,37.5>,<0,0,1>,<1,0,0>, <0 ,1,0>,25
ACTL/<413.149,271.8685,12.5128>,<413.1493,271.8698,37 .4 663>,<0.0003762,0,0.9999999>,<0.9999519,-0.0097998,-0.0003761>,<0.0097998,0.999952,-0.0000037>,24.9534
TARG/<17.5,360,12.5>,<17.5,360,37.5>,<0,0,1>,<1,0,0>, <0 ,1,0>
SHOW FEATURE PARAMETERS=YES
VOID DETECTION=NO
SURFACE1=THICKNESS_NONE,0
SURFACE2=THICKNESS_NONE,0
MEASURE MODE=NOMINALS
RMEAS=NONE,NONE,NONE
AUTO WRIST=NO
GRAPHICAL ANALYSIS=NO
FEATURE LOCATOR=NO,NO,""
SHOW CONTACT PARAMETERS=YES
NUMHITS=9,DEPTH=0
SAMPLE METHOD=SAMPLE_HITS
SAMPLE HITS=0,SPACER=0,INDENT1=0,INDENT2=0
AVOIDANCE MOVE=NO,DISTANCE=0
SHOW HITS=NO
COP_G_0 =COP/DATA,TOTAL SIZE=252,REDUCED SIZE=252,
FINDNOMS=NO,REF,G_0,,
MOVE/CLEARPLANE

[KIRBSTER269]

Don't use the Adaptive Line Scan, been a faulty issue for awhile now. Hexagons solution was "wow that's weird, maybe just use the standard strategy" Their words, not mine. anyways you can already see the difference in your THEO and your ACTL. Sometimes you can recreate and it works, but if it's faulty, I wouldn't use it. Looks like it was a problem when using MM? looks like that anyways. Can't remember, getting old

https://www.pcdmisforum.com/forum/pc...n-lines-2018r1

[A-machine-insp]

I never use the auto line with the adaptive scan. I would use a linear open scan. That is probably your issue as the great KIRBSTER269 said above.

[JEFMAN]

Maybe turning avoidance move on "ON" could help ?
I would avoid re-programming in front of bad news from KIRBSTER269 and A-machine-insp ...
(bad news but good advices !)

[KIRBSTER269]

Have you ever known me to bring good news to the table?

[A-machine-insp]

KIRBSTER269 Nope. Only bad news and sarcasm.

[JEFMAN]

KIRBSTER269 : maybe this one ?

https://www.pcdmisforum.com/forum/of...est-for-jefman

[KIRBSTER269]

LOL, I totally forgot about this Jeffery, Luv to you my brother Thanks for the laugh