SP25 Calibration! (again... yes I searched the forum)

The force values in the parameter settings are global for all modules.

You need to go into the PC-DMIS settings editor and adjust them for the longer SM modules.

RenishawCalibration_SP25SM4_ScanOffsetForce 1&2

You will need to lower the values compared to the parameter settings.

Adjust the values and then perform a calibration.

I recommend doing this at both A0B0 and A90B0 to make sure the values can handle the deflection of the probe under its own weight.

Does this override the option probe settings that are inside a program? 

Ah... found it! 

It's also worth checking the controller setting i mentioned (assuming it's an FDC), although you may need to call the service guy back in to do that and make any changes.  There is a Scan deflection Limit (ScanDeflLimit) which may need to be increased.  It used to default to 0.25 but needs to be greater for modules like the SP25-4.  In the past, I've had to open it up to around 1.0 when long extensions were being used.  The controller discards points that are beyond the maximum deflection limit which then leads to the error you posted - because there are no points for PC-DMIS to analyse.

It's also worth checking the controller setting i mentioned (assuming it's an FDC), although you may need to call the service guy back in to do that and make any changes.  There is a Scan deflection Limit (ScanDeflLimit) which may need to be increased.  It used to default to 0.25 but needs to be greater for modules like the SP25-4.  In the past, I've had to open it up to around 1.0 when long extensions were being used.  The controller discards points that are beyond the maximum deflection limit which then leads to the error you posted - because there are no points for PC-DMIS to analyse.

The tech seemed like he had no idea what could be causing the problem. I'm looking at the FDC stuff, not sure which controller we have now. It's a DEA machine and I know we now have a new controller with no longer uses the RS-232 cables in favor of just one ethernet cable. 

Open a web browser and type 100.0.0.1 into the address bar.  If it's an FDC controller, that should open the FDC control panel.  However, you will not be able to make changes to settings because they require a service password.

Yah that's what we have, however "something" is blocking that address from our system **cough corporate security cough cough**
Although according to IT "there is nothing in our security settings that would EVER block something like that...." 

But somehow the interface worked flawlessly from the tech's laptop... Weird....

Most probably firewall, or a port that needs to be opened up.

I don't see scan deflection limit listed in the help file for the FDC controller and can't get into the controller to look...

But as things have progressed today, we have just slipped deeper and deeper into this *** show the tech left for us.
You see when he left and "things were working" we kept up with that assumption, right up until we realized our machine axes were in the wrong orientation. (Many 4 letter words were spewed because they asked us and we told them what they were)
Soooo we fixed that so Y is X and X is Y. Re-calibrated the probe rack over the weekend (again), started calibrating probes which were now missing the cal sphere despite being "reset."
Seems re-creating the probe builds from scratch was the only thing that would fix it, so now we have started that process, again.

Managment is starting to get a bit grumpy that we are creeping up on 3 weeks behind schedule.