hexagon logo
Register Sign in
  • Replies 36 replies
  • Subscribers 33 subscribers
  • Views 762 views
  • Users 0 members are here
Options
Related

Automate export?

JEC_31
Seeking a way to automate the export process, specifically to IGES.

Ideal would be code that happens at finish of program run.

Next best thing would be a button to click.

Any ideas as to where to start?

Thanks in advance!

- Josh
  • Did you guys not read my post just previous to Cappy's? This IS included in the software. You just need to use the COP functions to do it. Even without the COP functions you can perfom the export easily with only two actions from the operator required.
  • Maybe I am referring to something else, the competitor has an offline viewer (you don't need the CMM software or even a CMM) to view the reports "live" with CAD-model and measured features just as you would with the fullblown software.
  • Maybe I am referring to something else, the competitor has an offline viewer (you don't need the CMM software or even a CMM) to view the reports "live" with CAD-model and measured features just as you would with the fullblown software.

    Now that would be awesome! Sign me up for that enhancement! The balance of this thread is referring to exporting a point cloud of measured points in .iges format automatically as the program executes. This type of file can then be easily imported into any CAD software.
  • Maybe I am referring to something else, the competitor has an offline viewer (you don't need the CMM software or even a CMM) to view the reports "live" with CAD-model and measured features just as you would with the fullblown software.

    Can't you do things like that with DataPage+ ? There's a ReportViewer and a WebReporter as part of that package. Sounds quite a lot like the other brand's things...
  • Did you guys not read my post just previous to Cappy's? This IS included in the software. You just need to use the COP functions to do it. Even without the COP functions you can perfom the export easily with only two actions from the operator required.

    i appologize about that dasalo, i just took a look at the function, this is pretty nice, honestly i didn't even think the commands were available unless you paid for an add on. how does this feature work with looped commands? Also is it a part of some package ie pro/cad/cad++?
  • 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.

    I know this is an oldish thread, but many thanks to you, DeSalo! I'm currently working on a 19 blade impeller, and was able to get it to loop fine and name each scan and dimension, and report them how I liked. However, in as far as reporting, since we are stuck with the customer's prescribed data points, and need to report the deviation from each of those points - and the supplied data is only for Blade 11, our Engineer was having trouble making any use of this data to make adjustments to the whole impeller/machining origin/tool offsets (basically, my report was just 19 iterations of a report for blade 11).

    I had never played with the COP features yet, but your post was a great solution! Also, your detailed description of the buggary with variables/alignments saved me a lot of headachery! (I was expecting the variables used in the scan names that make up the COP features to muck things up for me, but apparently it's just the name of the COP export file name that is variable-averse...?) I was able to export each blade as .igs both from the rotated alignment (for me, as I need each blade's points to match Blade 11's position), and from the non-rotated alignment, so that each blade's points would be in their 'actual position', and import them together into one .igs file for the Engineer to use. Thanks again!
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement