Please forgive my basic question, we have recently decided to change over to pc-dmis and I am releatively new. We are currently taking the .rtf in a txt format file and reading them into a 3rd party reporting software called 3DGDM. Obtaining the output files in PC-dmis seems very combersum. Sometimes it saves one program run and other times it will take multipul runs. Our current work around is, when we finish a run we shut down the reporting window and reopen it clicking on the button to "view report mode" and it loads only the last part run. Is there an easier way? and how could we obtain all of the part runs into one file? If we had a bad run how could we delete the one file and not mess up the entire run. Thanks.
Please forgive my basic question, we have recently decided to change over to pc-dmis and I am releatively new. We are currently taking the .rtf in a txt format file and reading them into a 3rd party reporting software called 3DGDM. Obtaining the output files in PC-dmis seems very combersum. Sometimes it saves one program run and other times it will take multipul runs. Our current work around is, when we finish a run we shut down the reporting window and reopen it clicking on the button to "view report mode" and it loads only the last part run. Is there an easier way? and how could we obtain all of the part runs into one file? If we had a bad run how could we delete the one file and not mess up the entire run. Thanks.
Howdy! Welcome to the [-]workmare[/-] forum!
I see from your profile that you are running version 2010 MR2. Which version of pc-dmis you are running is a valuable piece of information you should include in most of your posts, as the answer can differ dramatically depending on which you are using. Other information that is often helpful is type of CMM, type of controller, type of probe, sketch or drawing & actual code copy/paste from the edit window into html code tags.
With the report window open in pc-dmis there are two icons in the header are at least partially causing what you are seeing. One is last execution mode the other is report mode. It is also possible to tell pc-dmis to append the report to a file rather than creating a unique file for each run. File>Printing>Report Window Print Setup> there is a radio button for append. I have never used this myself, so maybe someone else will chime in with specific tips. Also pressing the F1 key brings up the help files. If you do that with a window open, it will automatically navigate to what it guesses is the most relevant section to that window. There is also a search function, both in the help files and this forum.
Any partial execute will append the executed commands in the report. There is a File/Reset Execute List to allow users to clear prior executes from the list in order to perform a partial (execute from cursor) type of thing. Execute (Ctrl+Q) will automatically clear the list since the execute starts at the beginning.
Any partial execute will append the executed commands in the report. There is a File/Reset Execute List to allow users to clear prior executes from the list in order to perform a partial (execute from cursor) type of thing. Execute (Ctrl+Q) will automatically clear the list since the execute starts at the beginning.
I like that, now if I could just clear everything but the header....
I don't do this type of reporting myself (appending multiple runs to one report file), but the default templates that came with the software (v3.5, 4.2, 2009, 2011, all had pretty much same stuff) were of very littel use to me. I struggled to make one that is more useable for what I inspect through the in-software template editor, but whenever I upgrade I have to re-do this work, posting the template file into the program folder does not work. Also, as many time as I've tried to set it as the default report it never takes, I always have to open the reporting window and select it as the default every time I write a program. I had a software guru in from Hexagon about a year ago to solve an unrelated issue, but while he was there I brought this up and he had no idea what to do about it, so I've pretty much accepted it as unavoidable. It seems strange (being inspection software and all) but apparently pc-dmis is not friendly when it comes to reporting data in any way other than how it is already set up to do so. I know this isn't what you want to hear, but the truth won't really set you free (that's a lie, too).
Settings editor - "FileMan" , "DefaultReportTemplate" - to set what your default report template should be. (Before V4.0 there was no report template). You would need to copy your template to each version of pcdmis you require it to be the default template. Assuming you are installing to different directories.
I don't do this type of reporting myself (appending multiple runs to one report file), but the default templates that came with the software (v3.5, 4.2, 2009, 2011, all had pretty much same stuff) were of very littel use to me. I struggled to make one that is more useable for what I inspect through the in-software template editor, but whenever I upgrade I have to re-do this work, posting the template file into the program folder does not work. Also, as many time as I've tried to set it as the default report it never takes, I always have to open the reporting window and select it as the default every time I write a program. I had a software guru in from Hexagon about a year ago to solve an unrelated issue, but while he was there I brought this up and he had no idea what to do about it, so I've pretty much accepted it as unavoidable. It seems strange (being inspection software and all) but apparently pc-dmis is not friendly when it comes to reporting data in any way other than how it is already set up to do so. I know this isn't what you want to hear, but the truth won't really set you free (that's a lie, too).
Before you open Pcdmis (otherwise make sure it isnt running), go into the install folder and change the default report template name (add a letter or number like A or 1) then change the name of your updated report template to what the default was originally and then see if that fixes your problem.
