[St...] Posted June 3 Share Posted June 3 We are currently using autorun and autosaving the reports to a folder on the server. I would like to be able to skip saving the reports from parts that are out of tolerance. Is there a way I can only save the good reports? Link to comment Share on other sites More sharing options...
[Ma...] Posted June 4 Share Posted June 4 You can use naming of protocols and batch file to remove with a name in it. Here is thread about it viewtopic.php?p=24263#p24263 Link to comment Share on other sites More sharing options...
[Ky...] Posted June 4 Share Posted June 4 Hello all, To add to what Martin said, if you really want to delete, or at least move, all the reports that are not in spec, it will likely require some fancy batch file work, at least if you don't have PCM. I'm not terribly good with batch files, but I can give a general outline of what I would do in this situation: 1. As Martin said, define the name for the output using the name for output files menu (here is a knowledge base article covering it, in addition to what Martin sent: https://portal.zeiss.com/knowledge-base?id=587888). 2. You can use PCM in one of the formula menus that will be run in the program (for instance, in the comment of a feature or something) to save the actual value of this using the "systemCall" function and a batch file (I did test "systemCall" without PCM and it works for me, but as always, you'll have to test it before hand, and that might change in different versions). 3. At the end, you can do something similar to step 2 and save the "inspectionTolerancState()" value to a file. This value will be either "inTolerance" or "outOfTolerance". 4. In a specifically named batch file (see https://portal.zeiss.com/knowledge-base?id=522725 to find which one), you can have it read those two files made in steps 2 and 3 and delete or remove the file as needed. It is a fair bit of work and is only a brief outline, but this is probably the most robust way I can think of doing it, assuming no PCM (if you do have PCM, you can do it all in a PCM file run at the run of the program, see that last knowledge base article for what to name it. Our level three programming class (I think it's still called "expert" in the portal) actually covers things like this and is in fact the inspiration for it. I hate to sound like I'm in sales, but if things like this interest you, perhaps you can look into it? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in