Can anyone tell me if you can write into the program code to automatically export measured results into a pointcloud (.iges format) once a program has run. I know how to do it manually once I have measured a part but was hoping there is a way to include it in the programming so it doesn't get forgotten each time a part is measured.
It is possible to do this if you have CAD++. You need to have a license for the COP(Cloud Of Points) commands. You create a COP feature that references the features containing the points you want to export ( it can only be points. Lines, planes, etc. won't export). Next you create a COP operator command with the subtype "export". Choose .iges as your file type and select a path. One trick here is that the path field has a bug in it (at least in 2013MR1 it does) that prevents you from using variables to define the export path. To get around this you can just export to a static path and file name and then use a "Move" command to rename the file and place it wherever you want (if you need to append a serial number, time stamp, etc). The final piece of the puzzle is to go up to the top of your program and create a COP operator with subtype "Empty" and reference your COP feature. So now when the program runs it will empty any old data from the point cloud, measure all of your features, collect the new measured data in the point cloud feature, and then export it in .iges format. I've been using this method in every program for years now without a single problem.
It is possible to do this if you have CAD++. You need to have a license for the COP(Cloud Of Points) commands. You create a COP feature that references the features containing the points you want to export ( it can only be points. Lines, planes, etc. won't export). Next you create a COP operator command with the subtype "export". Choose .iges as your file type and select a path. One trick here is that the path field has a bug in it (at least in 2013MR1 it does) that prevents you from using variables to define the export path. To get around this you can just export to a static path and file name and then use a "Move" command to rename the file and place it wherever you want (if you need to append a serial number, time stamp, etc). The final piece of the puzzle is to go up to the top of your program and create a COP operator with subtype "Empty" and reference your COP feature. So now when the program runs it will empty any old data from the point cloud, measure all of your features, collect the new measured data in the point cloud feature, and then export it in .iges format. I've been using this method in every program for years now without a single problem.