Command Argument Out of Limit Emergency Error

I can't read the message in lower left clearly but it looks like it might have the text PRBPIN followed by an offset matrix. If this is the case then I agree with the Hexagon rep. It seems like you might have an invalid probe offset matrix in the controller and every time the controller tries to boot it reads in that invalid matrix and throws this error. You could try renaming the folder that contains all of your probe files so that PCDMIS can't see any of them when it starts up. If that doesn't do it then either the last used matrix is stored in the registry, in the controller, or both. One way or another they need to get cleared/reset. This is pure speculation mind you. This might not be the problem at all but it's the best guess I have based on what I can see in the screenshot.

If you open the debug file in some software that will let you search the text you can just search for the error message, or a piece of it. It will be in there somewhere. Then look upwards and you will see what was happening in the loading process at that time. If this type of troubleshooting is outside of your comfort zone I suggest you call in a technician from Hexagon to get it sorted out. Watch how they go about it, ask lots of questions, and you'll be in a better position next time something comes up.

I can't read the message in lower left clearly but it looks like it might have the text PRBPIN followed by an offset matrix. If this is the case then I agree with the Hexagon rep. It seems like you might have an invalid probe offset matrix in the controller and every time the controller tries to boot it reads in that invalid matrix and throws this error. You could try renaming the folder that contains all of your probe files so that PCDMIS can't see any of them when it starts up. If that doesn't do it then either the last used matrix is stored in the registry, in the controller, or both. One way or another they need to get cleared/reset. This is pure speculation mind you. This might not be the problem at all but it's the best guess I have based on what I can see in the screenshot.

If you open the debug file in some software that will let you search the text you can just search for the error message, or a piece of it. It will be in there somewhere. Then look upwards and you will see what was happening in the loading process at that time. If this type of troubleshooting is outside of your comfort zone I suggest you call in a technician from Hexagon to get it sorted out. Watch how they go about it, ask lots of questions, and you'll be in a better position next time something comes up.