Automate export?

Thanks, DaSalo!

I have never gotten the SendKeys to work at all, but it has been some time since I last tried...

You could try AutoIt - http://www.autoitscript.com/site/autoit/ - you compile a script into an .exe, and call that .exe from PC-DMIS in an external_command.

If you have CAD++ with the Cloud Of Points module the solution to this is extremely simple:

1)You populate a COP feature with all of the stuff that you want to have exported automatically
2)You create a COP operator of type "Export"
3)In the COP operator dialog select your COP feature, set the file type, and set the file name.

When the program executes it will bundle all of your features into the COP and export them as specified in the COP operator. Simple as that.

The only trick to this is that in 2013MR1 there is a bug in the file name field for the COP operator that prevents you from using variables in the file name. You can put variables in there and it will work correctly until you close the program. When you reopen the program the variables will have been replaced with whatever the last value was and the field will just be dumb text. The solution is to just let it be dumb text, save the file out to a standard location with a standard name, and then use a File/Move command to move the file to a path and name of your choice. The file/move command will accept variables without an trouble so you can just use this to rename the file and place it wherever you want.

Another bug 2013MR1: The alignment fields in the COP feature and COP operator dialogs don't seem to stick. You can set an alignment but if you close and reopen the dialog it will always default back to the currently active alignment. The solution is to just recall the alignment you want to use for the export right before the COP commands.

Problem solved! .IGES export is now fully automated.

DaSalo - I pray that you filed a report for the shortcomings you have found?

I'm very sorry to tell you that, as of now, your prayers have gone unanswered. I'll try to get around to it but my focus is on finding solutions not on reporting problems. If I can't find a work around then I report it. If I can find an easy workaround I usually leave it to those with more time on their hands. I know that isn't the ideal attitude but I'm buried in work and something's got to give.


Update: Tickets have been submitted for both issues.

I will be trying this soon.

I've implemented it on several programs in both 2013MR1 and 2012MR1 and it works like a charm.

I found a copy of the IGES file definition and i created my own utility. If you are only putting points in the iges file it's pretty easy to pull the hits of each feature and place it in the IGES file. With a little more work you could put lines, circles, etc. into the file.

I would share my code with you if I could, but it is proprietary info...

but if you would like a copy of the IGES file definition, or any help writing the utility I am more that willing to help. just send me a PM.

-Cappy

I found a copy of the IGES file definition and i created my own utility. If you are only putting points in the iges file it's pretty easy to pull the hits of each feature and place it in the IGES file. With a little more work you could put lines, circles, etc. into the file.

I would share my code with you if I could, but it is proprietary info...

but if you would like a copy of the IGES file definition, or any help writing the utility I am more that willing to help. just send me a PM.

-Cappy

This stuff should be provided for free by Wilcox - if you ask me. I know a strong competitor that has very good software for this particular thing, incorporated into their METROLOGy software...

This stuff should be provided for free by Wilcox - if you ask me. I know a strong competitor that has very good software for this particular thing, incorporated into their METROLOGy software...

+1

Sent from my SCH-I545 using Tapatalk 4