I created a program for a touch probe. Ran great. Changed the program on my offline key so it would work with the CWS. It works fine until the sensor has to take a Z depth in a narrow slot. Then it will read "Outside Travel Limits" even though all the coordinates in the THEO and TARG are the exact coordinates it needs to be. This is using PC-DMIS 2016. Now this is happening with all older z depth programs that were proven to function just fine. Programs ran 100 times now start to get "Outside Travel Limits" when it measures in a narrow slot or a surface that is like 2 mm wide. This is using PC DMIS 2016
I wrote a quick Z depth program on my 2013 offline key to see if that errors out. It does not. So im thinking there is a parameters setting that somehow carried over from the touch probe to the white light sensor in the 2016 software. Its like it thinks there is a Ruby too big for the slot and errors out even though its a white light sensor. For what I have seen, all settings are identical from the 2013 software to the 2016 software.
I have not tried to calibrate it. It is reading X, Y, and Z locations just fine. But I will try that tomorrow morning to see if it resets anything.
Any ideas what is happening here?
I wrote a quick Z depth program on my 2013 offline key to see if that errors out. It does not. So im thinking there is a parameters setting that somehow carried over from the touch probe to the white light sensor in the 2016 software. Its like it thinks there is a Ruby too big for the slot and errors out even though its a white light sensor. For what I have seen, all settings are identical from the 2013 software to the 2016 software.
I have not tried to calibrate it. It is reading X, Y, and Z locations just fine. But I will try that tomorrow morning to see if it resets anything.
Any ideas what is happening here?