Inspect program freeze

[Moran Oran]

Hello, I was wondering if anyone using Inspect has ran into a issue with the software freezing / routine not starting. It seems like it happens at least once a shift on one of our shop floor CMM's.

The error message we get "The PCDLRN.Application14.1 add-on is executing a routine. Either stop or finish the execution before closing Inspect.".

I was thinking the operators were spamming the programs and maybe it was trying to run more than one, but I had it pop up on me.

Any idea what this add on is or if I need it to run Inspect?

We are running MR1 2019 *Fixed I was thinking our last version we were running*

[JacobCheverie]

Hello, I was wondering if anyone using Inspect has ran into a issue with the software freezing / routine not starting. It seems like it happens at least once a shift on one of our shop floor CMM's.

The error message we get "The PCDLRN.Application14.1 add-on is executing a routine. Either stop or finish the execution before closing Inspect.".

I was thinking the operators were spamming the programs and maybe it was trying to run more than one, but I had it pop up on me.

Any idea what this add on is or if I need it to run Inspect?

We are running MR2 2019

So you're running PC-DMIS 2019 R2? Because Inspect won't have the ability to handle that until Inspect 4.1

PCDLRN application is PC-DMIS itself. Do any of your programs have loops that it is getting caught up on? I would examine the individual program(s) that it is freezing for and see if something funny is going on in them. It sounds like PC-DMIS is running a program in the background that won't end.

[Moran Oran]

No loops are in the programs, we never had this issue until we upgraded from 2017.

it looks like it might be getting hung up when its taking temp comp at the start of the program. When I have the coding up thats where it is stopping. Normally when weve been having this issue we will reboot the entire PC and it will run normally for a few hours with no issues.

The operators definitely like the 2017 version of Inspect better than this upgrade.

[Moran Oran]

Forgot the version of our Inspect is 3.2 . Also this is only happening on one of our 3 shop floor machines. 2 of the machines are running the exact same programs just on different sides of the cell.


Also apologizes we are running R1. R2 was our 2017 version! Sorry

[AndersI]

Maybe the temperature sensor is damaged on that particular machine, so it takes a long time (or forever) to read the temperature? That could be verified by swapping the sensors of two machines, and see if the problem follows the sensor.

[Moran Oran]

Maybe the temperature sensor is damaged on that particular machine, so it takes a long time (or forever) to read the temperature? That could be verified by swapping the sensors of two machines, and see if the problem follows the sensor.

I will give that a try, would there be any issues if the machines have different controllers? I know the one having the issue is using the older model controller. Least thats what the calibration tech said on why its so much slower than our other machines on move speeds.

[AndersI]

Maybe it's so old it can't even read part temperature?

[Moran Oran]

No because it used to work on the old 2017 with no issues. The machine is only around 3 years old.