Report for Errors and Warnings?

mtakacs · 2006-05-15 19:20:01

Is there a way to setup a Vericut report to report all Errors/Warnings when a file is simulated?

I see this as one of the primary functions of reporting functionality, the ability to create a document that tells you if something is wrong!

Ideally you could capture a picture when and where that error occurs as well. I know you can capture an image at every tool change, It would be great to be able to do that at every warning/error as well.

If this doesn't exist, it should be an enhancement!

Thanks,

Mark-

DaveF · 2006-05-16 14:30:59

Good Idea Mark.

I have not got into reports yet, but I will.

here is a partial answer.

this will create a ShadeCopy image file when an error is detected.

if you can not slerp these jpg's out in a report, it would be a good enhancment.

Auto Error On?When toggled "On", VERICUT automatically saves a ShadeCopy image file when an error is detected.

AutoSave, ShadeCopy tab
Location: File menu > AutoSave

Features on this tab control automatic saving of ShadeCopy image files.

Print Command ? When toggled "Off", sends graphical data to the specified ShadeCopy File. When toggled "On", executes the print command that sends raw graphical image data to the printer.

By default, the ?prshade? command executes the ?prshade? command file containing operating system commands typically used to print images on your computer. If printing fails, correct the entry in the Print Command field, or use an ASCII text editor (NOT a word processor) to edit the ?prshade? command file to have the proper print command for your computer/printer.

Properties ? Opens the File menu > Images > ShadeCopy window to access settings for file formatting and printing.

Auto Save options ? These options control when VERICUT automatically saves ShadeCopy image files. Each selected event causes a file to be saved when that event occurs. Options:

Cutter Change ? Save file when the cutter has been changed.

# of Cuts ? Save file after a specified number of cuts.

File End ? Save file when the end of the tool path file has been reached.

ShadeCopy File ? Use to specify the base name for ShadeCopy image files saved as a result of Auto Save options described above, when the Print Command checkbox is toggled "Off". Enter the \path\file name in the text field or click on Browse and use the Save File selection window to specify the file. The naming convention used for saved files is as described for IP files-see File menu > AutoSave, In Process tab for details.

Auto Error On?When toggled "On", VERICUT automatically saves a ShadeCopy image file when an error is detected.
ShadeCopy File ? Use to specify the base name for ShadeCopy image files automatically saved as a result of errors detected when AutoError On is toggled "On", and the Print Command checkbox is toggled "Off". Enter the \path\file name in the text field or click on Browse and use the Save File selection window to specify the file. The naming convention used for saved files is as described for IP files-see File menu > AutoSave, In Process tab for details.

mtakacs · 2006-05-16 16:25:15

Thanks Dave,

it's definitely a step in the right direction, I can get the shadecopy stuff and the Autosave to work, now I just need to figure out how to get it all to work together in a report. I kinda wish it was all integrated in one tool, and it would be great if I could associate the actual error text with the image of the error.....I also wish the shadecopy function took a screenshot of more of the screen, like the log area at the bottom and maybe the G-code listed out on the screen or something.

Thanks for your help though, I'll report back if I get it to work...

DaveF · 2006-05-16 17:25:41

Mark,

You are on to something here.
I think you should get you nickels worth, and phone this one in to support.
Geno is the report expert, but they are all pretty good.

Reports may just be the right tool to slurp up the data
:wink:

1. a picture of the error
2. the tool definition used
3. how about a sample of the g-code +/- 10 lines :twisted:
4. last few logger info
5. last few log file info.
6. now I?m reaching, a zoomed image as well of the offending area of they part.. window size, ?say 5 times the size of the cutter. to do that, they would need to create a new window, and automate the zoom feature.
:twisted:

when I check other peoples work, I open the logger, open the tool path file, and sometime the status window.
than I do a screen shot of the entire screen using a 3rd party screen shot.

here is another Tip.
I set Vericut to output all operator messages, IE, (MSG, Rough pocket 3) , to the logger.
that way I can go right to the PPRINT in the program, or line on the tree, of the offending cut.

I will bet you can do several things on that list with the Vericut we have today.
8)

VERICUT Users' Forum

#1 2006-05-15 19:20:01

Report for Errors and Warnings?

#2 2006-05-16 14:30:59

Re: Report for Errors and Warnings?

#3 2006-05-16 16:25:15

Re: Report for Errors and Warnings?

#4 2006-05-16 17:25:41

Re: Report for Errors and Warnings?

Board footer