Automatic printing in V4.1: does this work for everyone?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Automatic printing in V4.1: does this work for everyone?

    This is a question for all you PC-DMIS CMM users: if you go into File/Printing/Report Window Print Setup, and you activate the Printer button, does PC-DMIS automatically send the report to the Printer after you finish a program?

    I could have sworn this worked in V4.0. It does not work for me now anymore in V4.1. After running my programs, nothing prints. Nothing to the printer, file or .DMO file. I have to re-execute in PC-DMIS to make this happen.

    Maybe I stumbled upon a NC specific issue here????


    Thanks for your help, Jan.
    ***************************
    PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
    Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

  • #2
    Works for me in 3.7mr3.

    Comment


    • #3
      Jan,

      It seems to work fine for me in v4.1 Release. I'm not sure if this is the problem, but check File | Printing | Printer Setup. Make sure you have a proper printer defined. This was a new menu item that I believe was added to 4.1. This allows you to more easily switch between printing devices. It may be set to the PC-DMIS PDF Converter by default or something. Also, does your Report window contain data? If you've just opened your part program, your Report will be blank until you redraw the report.
      Jared Hess - Techwriter @ WAI
      [View 2008 Reporting Tutorials Here]

      Comment


      • #4
        I have seen the same issue. I ran 10 different reports today and only one executed properly. On all of the others I ended up doing a partial execute on the last dimension and then it printed.

        v4.1

        Comment


        • #5
          I noticed that it behaves better if the report window is open during execution. If that doesn't solve the problem, close PC-DMIS, then go to your screename file found resident in the WAI folder and delete executegbarstate. Upon opening PC-DMIS a new executegbarstate file will be created. I'm not certain that this will solve the problem but it did for me when I was having problems printing to a PDF.
          sigpic

          James Mannes

          Comment


          • #6
            Originally posted by JaredHess
            Jan,

            It seems to work fine for me in v4.1 Release. I'm not sure if this is the problem, but check File | Printing | Printer Setup. Make sure you have a proper printer defined. This was a new menu item that I believe was added to 4.1. This allows you to more easily switch between printing devices. It may be set to the PC-DMIS PDF Converter by default or something. Also, does your Report window contain data? If you've just opened your part program, your Report will be blank until you redraw the report.

            It is set to the correct printer, but it never produces an automatic print. Also, it never automatically produces a PDF or DMO file, eventhough checked. It seems that PC-DMIS NC Server just does not have the ability anymore to automatically generate reports.

            If I get out of Server and jump into PC-DMIS and execute, I get an automatic hard copy on the printer, a .RTF file and a .DMO file. But that is NOT an automatic process. I need to have this happen automatically from NC Server...

            I am almost certain this worked in V4.0 though.... It seems to me it got fixed out of PC-DMIS.



            Jan.
            ***************************
            PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
            Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

            Comment


            • #7
              Jan,

              What about Insert | Report Command | Print Command and placing it at the end of your part program and setting that up to print out an automatic report? Does that work as a workaround? Anyway, if you suspect this is an NC specific thing, maybe you can post this in the NC forum and get some NC gurus to take a peek at it. Good luck!
              Jared Hess - Techwriter @ WAI
              [View 2008 Reporting Tutorials Here]

              Comment


              • #8
                I think Iron Man nailed it again!

                I tried the print report comand at the end of the program....did not work.
                I set the print option as in the older versions, opened the report window, and executed my program. When execute was complete, report printed fine.

                Thanks James.

                Comment


                • #9
                  Originally posted by JamesMannes
                  I noticed that it behaves better if the report window is open during execution. If that doesn't solve the problem, close PC-DMIS, then go to your screename file found resident in the WAI folder and delete executegbarstate. Upon opening PC-DMIS a new executegbarstate file will be created. I'm not certain that this will solve the problem but it did for me when I was having problems printing to a PDF.

                  I tried what you suggested and it did not seem to work for me.


                  Originally posted by JaredHess
                  What about Insert | Report Command | Print Command and placing it at the end of your part program and setting that up to print out an automatic report? Does that work as a workaround? Anyway, if you suspect this is an NC specific thing, maybe you can post this in the NC forum and get some NC gurus to take a peek at it. Good luck!

                  Tried that too, but it seems to remain a problem.

                  The more I think about it, the more I think you are right. This probably belongs on NC.

                  Just hoped it was a problem for everybody... Nothing like a little cloud....



                  Jan.
                  ***************************
                  PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
                  Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

                  Comment


                  • #10
                    I've been experiencing the same problem.

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X