hexagon logo
Register Sign in
  • Replies 36 replies
  • Subscribers 33 subscribers
  • Views 737 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
Parents
  • One more thing about this process: for whatever reason PC-DMIS has been very finicky about passing variables to this script. Not sure why. In order to successfully pass the values I had to reassign the variables right before the script is called. These variables are all read in from an external document at the top of the program and then the value is passed again to another PC-DMIS variable which is then passed to this script. I have no idea why that extra pass off is necessary. Perhaps there is some type conversion happening there for some reason, although there should be no reason that any of these would be seen as anything other than strings. Anyhow, if you do it like this it will work every time: 

    $$ NO,
            *****************************************
            Export IGES
            *****************************************
            ASSIGN/PN1=PN
            ASSIGN/OP1=OP
            ASSIGN/SN1=SN
            ASSIGN/RPTTIME1=RPTTIME
            ASSIGN/RPTDATE1=RPTDATE
            ASSIGN/IGS1=IGS
            ASSIGN/DIRECT="\\Results\\IGES\\"
CS3        =SCRIPT/FILENAME= C:\BLADERUNNER\SCRIPTS\IGS_EXPORT.BAS
            FUNCTION/Main,SHOW=YES,ARG1=PN1,ARG2=OP1,ARG3=SN1,ARG4=RPTTIME1,ARG5=RPTDATE1,ARG6=IGS1,ARG7=DIRECT,,
            STARTSCRIPT/
Reply
  • One more thing about this process: for whatever reason PC-DMIS has been very finicky about passing variables to this script. Not sure why. In order to successfully pass the values I had to reassign the variables right before the script is called. These variables are all read in from an external document at the top of the program and then the value is passed again to another PC-DMIS variable which is then passed to this script. I have no idea why that extra pass off is necessary. Perhaps there is some type conversion happening there for some reason, although there should be no reason that any of these would be seen as anything other than strings. Anyhow, if you do it like this it will work every time: 

    $$ NO,
            *****************************************
            Export IGES
            *****************************************
            ASSIGN/PN1=PN
            ASSIGN/OP1=OP
            ASSIGN/SN1=SN
            ASSIGN/RPTTIME1=RPTTIME
            ASSIGN/RPTDATE1=RPTDATE
            ASSIGN/IGS1=IGS
            ASSIGN/DIRECT="\\Results\\IGES\\"
CS3        =SCRIPT/FILENAME= C:\BLADERUNNER\SCRIPTS\IGS_EXPORT.BAS
            FUNCTION/Main,SHOW=YES,ARG1=PN1,ARG2=OP1,ARG3=SN1,ARG4=RPTTIME1,ARG5=RPTDATE1,ARG6=IGS1,ARG7=DIRECT,,
            STARTSCRIPT/
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement