Hi
My star probe suddenly stops in the middle of the program. It looses connection. I have to touch it a little and control Z again to make it work. My probe is not heavy and i use blue cap module.
After calibrating the probe it stops doing that but then in few days it will again starts stopping randomly while checking a part.
On the bottom of the module can you verify if the pins are protruding at all? Image below is the pins I am referencing. I know I have seen some of these pins protrude a bit. Usually when someone new is using the CMM and goes too hard in Z onto a part, pushing the probe tip back into the module a little. I do know that you are using blue, which is the light force module. Are you getting false triggers as well with the star probe? Or just unseating?
Hey William. Thanks for your response. My module pins looks fine to me. They are just very old now. Hence the bad appearance.
1. How long is the probe build?
2. What size probes are on the build?
3. How fast are your movespeeds?
4. Do you have flymode on (will smooth out abrupt shifts in stored inertia on the sensor, during movement)?
Per Renishaw, the star probe build on a 6way cannot exceed 42mm long, and it's recommended to only be 30mm long.
Last big question, have you explored the PI200 switch settings regarding trigger delays (HALT, PDAMP, & debounce)?
Note: this is for the OLD PI200-2 "box shaped" black and orange TP20 / TP200 controller. If it's a newer flattter, with aluminum top/bottom case it's the PI200-3, and the config switches are completely different.
(Renishaw "PI-200 install manual H-1000-5029-05-B.pdf", then there's the "PI-200-3 install manual H-1000-7542-03_ig.pdf")
If you exhaust all these variables, you can ask hexagon to disable all probe trigger detections while traversing with the "move" command (it's a FDC setting, I don't recall which one). Big word of caution, this can cause really significant damage to the system if you crash the machine with this active.
