hexagon logo
Register Sign in
  • Replies 11 replies
  • Subscribers 222 subscribers
  • Views 181 views
  • Users 0 members are here
Options
Related

Automate "export XYZ" file

Virgil UK
Hi folks.
I have about 30 parts that need to be run which equates to about 80 measurement points per part. Design have said that they want the resultts in XYZ format so after each part had been run I manually export the data to a XYZ file.
Is there anyway to code this into the program?

Thanks,.
Virgil.
Parents
  • Sounds great! MR. Hines, could you post code so I have a clue how to get it to work? Would appreciate. Thanks!

    This is the code I use to call the program: 

    EXTERNALCOMMAND/NO_DISPLAY, WAIT ; C:\PCDMISW 3.7V4\WIZARDS\PARSER\PCD_PARSER.EXE


    This version of calling the command will open a dialog box that lets you input a job number and part/serial number (both required). There are also a couple of command line parameters that I have coded into the program to automate the process a bit. There is a /j: and /p: that you can use to pass the job number and part number. 

    EXTERNALCOMMAND/NO_DISPLAY, WAIT ; "C:\PCDMISW 3.7V4\WIZARDS\PARSER\PCD_PARSER.EXE /j:38151 /p:AA_"+C1.INPUT


    I use this a lot for storing the data from my cap studies. If you are going to use the command line parameters you need to make sure you include the quotes the way I have them and also no spaces in the parameter.

    I often use: 

    V1         =LOOP/START, ID = YES, NUMBER = 0, START = 1, SKIP = ,
               OFFSET: XAXIS = 0, YAXIS = 0, ZAXIS = 0, ANGLE = 0
 
[I]code[/I]
[I]code[/I]
[I]code[/I]
 
EXTERNALCOMMAND/NO_DISPLAY, WAIT ; "C:\PCDMISW 3.7V4\WIZARDS\PARSER\PCD_PARSER.EXE /j:[I]your_job_number[/I] /p:"+V1
LOOP/END


    Honesly I didn't write this for distribution so I have no idea what sort of errors you may run into. This is my VB compiled version of the code I posted in the "My solution to .CSV output" thread.

    for some reason the code tags aren't working correctly and seperating the external command line. Those should all be one line of code.
Reply
  • Sounds great! MR. Hines, could you post code so I have a clue how to get it to work? Would appreciate. Thanks!

    This is the code I use to call the program: 

    EXTERNALCOMMAND/NO_DISPLAY, WAIT ; C:\PCDMISW 3.7V4\WIZARDS\PARSER\PCD_PARSER.EXE


    This version of calling the command will open a dialog box that lets you input a job number and part/serial number (both required). There are also a couple of command line parameters that I have coded into the program to automate the process a bit. There is a /j: and /p: that you can use to pass the job number and part number. 

    EXTERNALCOMMAND/NO_DISPLAY, WAIT ; "C:\PCDMISW 3.7V4\WIZARDS\PARSER\PCD_PARSER.EXE /j:38151 /p:AA_"+C1.INPUT


    I use this a lot for storing the data from my cap studies. If you are going to use the command line parameters you need to make sure you include the quotes the way I have them and also no spaces in the parameter.

    I often use: 

    V1         =LOOP/START, ID = YES, NUMBER = 0, START = 1, SKIP = ,
               OFFSET: XAXIS = 0, YAXIS = 0, ZAXIS = 0, ANGLE = 0
 
[I]code[/I]
[I]code[/I]
[I]code[/I]
 
EXTERNALCOMMAND/NO_DISPLAY, WAIT ; "C:\PCDMISW 3.7V4\WIZARDS\PARSER\PCD_PARSER.EXE /j:[I]your_job_number[/I] /p:"+V1
LOOP/END


    Honesly I didn't write this for distribution so I have no idea what sort of errors you may run into. This is my VB compiled version of the code I posted in the "My solution to .CSV output" thread.

    for some reason the code tags aren't working correctly and seperating the external command line. Those should all be one line of code.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement