How to automatically save PiWeb report as PDF before executing cncBreak()?

[[Se...]]

Hello, everyone !😀

I want to do the following in CALYPSO:

1. When a specific Result Element is reached,

2. Save the results of all characteristics measured up to that point as a PiWeb PDF automatically to this folder:

3. After saving, run cncBreak() to stop CNC and wait for the operator.
   Right now, I already use cncBreak() in the Formula and it works.
   But I don’t know how to add the automatic PDF save before the break.
   Could someone please give me an example PCM code for this?
   
   Thanks in advance!

[[Ma...]]

Wouldn't be better a different approach? Like mini plans, or running from characteristics?

[[Se...]]

Please sign in to view this quote.

Hello,
Currently, our system is connected to a conveyor, so we are only responsible for calling up the program.
Therefore, we would like to know how to automatically save the PiWeb reporter PDF up to the point before the CNCBREAK command is executed.
If there are alternative approaches, could you please provide an example?

[[An...]]

Could consider using endInspection() instead of cncBreak() to get the report? Should still redlight the machine, but more gracefully & still generate the reports from whatever was measured & evaluated.

[[Ch...]]

I agree with Andrew endInspection() is likely best here.

 

 There is also this to specify which Characteristics to report, in case the above does a full report and that is no desired : 

setElementsForProtocol() //Set characteristics to be printed in protocol

and some more helpful commands, although these are listed under 'custom printout' :  EDIT : These do not appear to be for PiWeb, a lot more info in the help file though for this.

//Flexible printout controlled by PCM
defineProtocol("#name","Pres for r&d")
defineProtocol("#type","presentationProtocol")
defineProtocol("#medium","pdf")
defineProtocol("#elements","allCFOutTol")

defineProtocol("#name","To me")
defineProtocol("#type","compactProtocol")
defineProtocol("#medium","ps")
defineProtocol("#elements","allCF")

defineProtocol("#name","For trouble shooting")
defineProtocol("#type","compactProtocol")
defineProtocol("#medium","screen")
defineProtocol("#elements","allME")

//Possible to set order:
defineProtocol("#order","likeList")
defineProtocol("#order","alphabetic")
defineProtocol("#order","rangeOfTolAndDev")

 

Edited September 2

[[Se...]]

Please sign in to view this username.

 

Please sign in to view this username.

 

Sorry, I didn’t explain it clearly before.

I first tried using endInspection().
But since our setup is not just Calypso and it is connected to the conveyor app, ending with endInspection() makes the conveyor think the result is OK, even when it is actually NOK.

That’s why I had to use cncBreak() instead.

 

So I am looking for a way to use cncBreak().

Is there a way to save the results into the folder C:\ACCURA\RESULTS_PDF

Edited September 2

[[Ch...]]

I'd suggest contacting Zeiss they have more and more solutions for automation and cases like this. 

[[Ch...]]

otherwise you would need to evaluate what has been run up to the stop ( will this be different every time ?? ), then you will need to probably set a VARiable to the inspection results (good/bad/other), then do cncBreak().

 

 

[[Se...]]

Please sign in to view this quote.

Hellp, 

Please sign in to view this username.

I just came back from vacation, and I have a question regarding my setup.

In the first picture, if the X, Y, Z or Dia value is NOK, the 5th RESULT element will be executed.
Before this RESULT element runs, I would like to save the current results as a PDF in the Postsetting step, and then execute cncBreak().

Is there a way to achieve this workflow: NOK → save PDF → cncBreak?

Thank you in advance for your help!

Edited September 15

[[Ch...]]

I'll check, are you using old custom report or PiWeb ?? edit: I see above you mention PiWeb, may be a bit more challenging, I'll still research.

if you;re using old custom report, the above commands might help.

Edited September 15

[[Ch...]]

Also for reference, I know you said endInspection() doesn't work for your application but there seems to be these variables for endInspection():

endInspection("WITH_DATA_OUTPUT")
endInspection("NO_DATA_OUTPUT")

 

[[Ch...]]

Hmm, seems possible with PCM but is obviously undocumented and would likely require 'executeCode'.

PiWeb looks like it requires initalization/syncronization etc.

I'd suggest asking Zeiss for a solution or one of the PCM wizards here.

PCM is likely in this area : Zeiss.Calypso.OMMeasProt multiOutput but also Zeiss.PiWeb.OMPiWebCMM.

 

[[Se...]]

Please sign in to view this quote.

I’ve tried multiple times, but I still haven’t been able to solve this problem.