hexagon logo
Register Sign in
  • Replies 10 replies
  • Subscribers 223 subscribers
  • Views 221 views
  • Users 0 members are here
Options
Related

Print Command using Variables

Virgil UK
Good Morning users.

I have reviewed other posts but cannot seem to get this to work.
I want to take an input variable and use it to save as a filename to save as a file.
I seem to have assigned the variable to the file path ok. A file is created but with nothing in it.
I am writing to a .RTF file and I am using 2012mr2. Any indicators most appreciated.

Virgil
Attached Files
  • double backslash after RESULTS folder is probably issue

  • Try ASSIGN/PATH="C:\\PCDMIS PROGS\\0_FW47657_T500 HP\\RESULTS"
  • I'm never a fan of assigning variables names like "FILE" and "PATH" - if you were programming in VB (or some other languages), these wouldn't even be allowed as they're reserved keywords. Probably not your issue, the double backslash as indicated by is the way to go, but you never know when it will cause a problem with code working in the background.
  • Also make sure you can print to RTF without a variable, just in case something is wrong with the print command.
  • C1         =COMMENT/INPUT,NO,FULL SCREEN=NO,
            Cavity Number
C2         =COMMENT/INPUT,NO,FULL SCREEN=NO,
            Operator
C3         =COMMENT/INPUT,NO,FULL SCREEN=NO,
            Machine Number
            TRACEFIELD/NO_DISPLAY,LIMIT=15 ; CAVITY : C1.INPUT
            TRACEFIELD/NO_DISPLAY,LIMIT=15 ; OPERATOR : C2.INPUT
            TRACEFIELD/NO_DISPLAY,LIMIT=15 ; DCM : C3.INPUT



Program goes here


ASSIGN/V1=ELAPSEDEXECUTIONTIME()
            COMMENT/REPT,
            "Elapsed Execution Time : " + V1
C15        =COMMENT/YESNO,NO,FULL SCREEN=NO,AUTO-CONTINUE=NO,
            Do you want to output this data
            IF/C15.INPUT=="NO"
            GOTO/PGM_END
            END_IF/
            ASSIGN/ST_TM=SYSTEMTIME("HH-mm-ss")
            ASSIGN/SYS_DT=SYSTEMDATE("MM-dd-yyy'")
            ASSIGN/MTI1="S:\[B][COLOR=#FF0000]FULL PATH NAME GOES HERE[/COLOR][/B]\\"
            ASSIGN/MTI2="[B][COLOR=#FF0000]FILE NAME GOES HERE[/COLOR][/B]"
            ASSIGN/MTI3=CONCAT(MTI2," CAVITY-",C1.INPUT," ",ST_TM," ",SYS_DT)  [B][COLOR=#FF0000]<----<<< Forms System time, date, and Cavity number into a single string[/COLOR][/B]
            ASSIGN/MTI4=CONCAT(MTI1,MTI3) [B][COLOR=#FF0000]<----<<< Creates the path, file name, time, date, and cavity number as a single string [/COLOR][/B]
            PRINT/REPORT,EXEC MODE=END,$
              TO_FILE=ON,APPEND=MTI4,AUTO OPEN REPORT=OFF,$  [B][COLOR=#FF0000]<-----<<< Sends report to a PDF file and will Open the report after each run if AUTO OPEN REPORT is set to YES[/COLOR][/B]
              TO_PRINTER=OFF,COPIES=1,$
              TO_DMIS_REPORT=OFF,FILE_OPTION=INDEX,FILENAME=,$
              REPORT_THEORETICALS=ALL,REPORT_FEATURE_WITH_DIMENSIONS=YES,$
              TO_EXCEL_OUTPUT=OFF,
              PREVIOUS_RUNS=DELETE_INSTANCES
PGM_END    =LABEL/



    This prints to a PDF, but MIGHT be able to be used for an RTF with some tweaking. No Guarantees.
  • Also make sure you can print to RTF without a variable, just in case something is wrong with the print command.

    Thanks for the suggestions. It seems that there could be something wrong when using the print command, it doesn't pick up what I have in my print report, although it will create the file.
    I've changed variable names and tried double backslash to no avail.

    Stuck on this one.





  • Typically when printing, I have two print commands. One at the beginning of the dimensions, followed by a label. This command is empty (as in the print command is there, but it's not set to print anything) This clears the print cache. Then at the end of the dimensions I have a second print command, which is set to print to what have you. It really depends on how you're set up, but I would try something similar. Try printing to an actual printer, etc. Then once you've got something that more or less works, try adding in the variables.
    HTH
  • Good Morning

    I have now managed to print the report to a file.
    To do this I get up my Report Print Options box up, and create a dummy file to write to and tick the 'overwrite' box.
    I keep my inserted print command at the end of the program and it works. I'm happy now but curious to know why I have to do this?

    P.S. Thanks for the help
  • If I understand your question correctly:
    If it's the same as with printing to a printer, PC-DMIS is a little funky when it comes to handling its reports.
    Basically you need the dummy command in there to clear whatever stuff has accumulated on the report, and refresh it.
    Then you have all of your dimensions because you manually tell the report what you want to add to it (which is why you might need to add a report label to it).
    The program will run through, wipe its memory of the report, generate new memory (the dimensions) and slap em on.
  • in reply to InspectorJester
    I have a little script (Kindly donated by ninjabadger) that refreshes the report prior to printing which does the same job as you describe but it is also good if you want to be sure the report you can see is what has been executed.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement