Jump to content

‘CNC manual’ window?


---
 Share

Recommended Posts

When running parts via Autorun, a ‘CNC manual’ window randomly opens after some measurement plans have finished running.

323_78b53daaf60fdd184dcad17264eabab1.png

I believe that the measurement plan is reloaded when this appears. Any external PCM files named ‘inspection_start_pcm’ are also executed automatically when this appears (this causes problems for us).

As I mentioned, the window appears randomly (not after every run). It happens on multiple machines, and after several different measurement plans.

We are running CALYPSO 2015 , ServicePack 2, Version 6.0.08 (09.10.2015).

Can anyone tell me what causes this and how to prevent it from happening?
Link to comment
Share on other sites

I have never seen this screen. You described it's behavior as random, not every run. And you said that it involves several different programs. Is it always occuring with the same programs or is that random as well?
Link to comment
Share on other sites

Richard, the window shows up randomly after a run in Autorun for any of our programs.

inspection_start_pcm.txt:
————————————————————-
chr_Side1=getRESULTS()+”\Side1__chr.txt”
fet_Side1=getRESULTS()+”\Side1__fet.txt”
hdr_Side1=getRESULTS()+”\Side1__hdr.txt”

if fileExists(chr_Side1) then
deleteFile(chr_Side1)
endif

if fileExists(fet_Side1) then
deleteFile(fet_Side1)
endif

if fileExists(hdr_Side1) then
deleteFile(hdr_Side1)
endif

clearParameter(“chr_Side1”,”fet_Side1”,”hdr_Side1”)
————————————————————————

(Window shows up after programs with absolutely no PCM code as well.)
Link to comment
Share on other sites

I have been working with a German friend of mine on this. Owen, I think has provided a valuable clue.

Paul, what kinds of machines do you have Calypso running on?
Link to comment
Share on other sites

If the behavior only occurs when you use Autorun, then the first thing I would try is to build a new .arn file with a single part program that you know was running when the problem occured. Test that and if the problem disappears, add another program and test that. If the problem shows up, then you can look at the program. There's a trigger someplace that's getting pulled, sometimes.
Link to comment
Share on other sites

 Share

×
×
  • Create New...