Here is one for you guys, I need to output data from PC-DMIS to an excel or other type of file where it will automatically average the results from a run of three parts and chart those results. The higher ups want real time data without paying for datapage+ or another SPC software such as QC Calc. Keep in mind I am by no means even a beginner let alone an expert with VB scripting.
You can export the output in various ways, either by exporting it to Excel (from within PC-DMIS, easiest) or have Excel fetch the values from your partprogram (harder). You have the PCD2EXCEL wizard to help you with the export, which will automate the export to Excel, but you would need something in your Excel workbook that does the rest - a macro perhaps?
Is there any advantage to having Excel fetch values? Is the difference simply that it can be done after the fact instead of in real-time when the CMM program is executing?
You can export the output in various ways, either by exporting it to Excel (from within PC-DMIS, easiest) or have Excel fetch the values from your partprogram (harder). You have the PCD2EXCEL wizard to help you with the export, which will automate the export to Excel, but you would need something in your Excel workbook that does the rest - a macro perhaps?
Doesn't the PCD2EXCEL wizard append the file by creating a new worksheet each time it updates? Like I said I know very little about visual basic or creating macros. If you can point me in the right direction I may be able to figure it out though. In the mean time I will try to make something work with the PCD2EXCEL.
Is there any advantage to having Excel fetch values? Is the difference simply that it can be done after the fact instead of in real-time when the CMM program is executing?
In my opinion, coding within the Excel VBA editor feels a bit more robust and you get more perks (autocomplete, syntax help, etc.).
Is there any advantage to having Excel fetch values?
Not really, rather the reverse. If you use PCD2Excel, it's Wilcox' responsibility that the exported data are correctly input in Excel and they (supposedly) know how to do it. If you write an Excel macro of your own, it's your own responsibility,
and you have to figure out how to get the correct data from all the different dimensions. I've done it, and it's not an easy task (adding FCF dimensions more than doubled the size of the macro).
The plus with writing your own importer in Excel is that you can (hopefully) fix it when you find a bug. With PCD2Excel you'll have to wait...
Edit to add: Of course, if you are trying to fill a custom form in Excel it will be much easier to do it all from Excel.
Not really, rather the reverse. If you use PCD2Excel, it's Wilcox' responsibility that the exported data are correctly input in Excel and they (supposedly) know how to do it. If you write an Excel macro of your own, it's your own responsibility, and you have to figure out how to get the correct data from all the different dimensions. I've done it, and it's not an easy task (adding FCF dimensions more than doubled the size of the macro).
The plus with writing your own importer in Excel is that you can (hopefully) fix it when you find a bug. With PCD2Excel you'll have to wait...
Edit to add: Of course, if you are trying to fill a custom form in Excel it will be much easier to do it all from Excel.
Er, just where do you get that idea, that Wilcox is responsible for it? Read your contract, they are not responsible for ANYTHING, for example:
Step translator that didn't translate correctly, thus making a cad file that was wrong
Screwing up updates so that your machine is no longer using the table map after installing, and NOT telling you that you have to turn it back on
Why would you even think that they have any responsibility for anything?
