LOOP reporting ???

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • LOOP reporting ???

    I'm running version 3.73 Still cannot get a true handle on reporting in 4.1 and was told at the user meeting to get used to it because it is not going away
    I am running a program with five loops of the same part. The first page outputs a header with Part number, Serial Number,Date ,Stats, Time, Date but only on the first loop. This info is missing on the next 4 loops. Is there a way to have all this info on each run. These files are exported as an rtf and then dumped into an Excel spreadsheet for mathmatical verification of an optical path. Obviously they have to be the same or you wind up with unreadable data. The reason for the five runs is to try to get an average value for the hits.
    We are very much pushing the 5.8 Micron envolope for the machine. The powers to be on this would love to see it less than 1 micron.

    Get me a new machine. one with that capability (little rant).

    One other thing I have considered is trying to add all the runs into one long report and having only to deal with one excel program. This has not been accepted as of yet. this is a long program takes an hour to run. and another 5 mins to sort the data out so that everything is the same just looking to save time and have consistency. I missed a day last week and I had to try to explain how to run the CMM over the phone to someone. In bed sick and on the Phone for over an Hour. But they didn't put the data in the order that the MAth Gurus wanted it in and I got a long lecture when I got in on Monday.

    I guess they were off Wednesday and Friday I wasn't (more rant).

    Any help would be Greatly appreaciated. I know some of you guys walk on water in the CMM world
    I do too in the winter when it gets hard.
    Thanks
    Lee
    Tolerance challenged ... Living in the world of unseen lines.

    This software isn't buggy its an infestation

  • #2
    Sorry double post
    Tolerance challenged ... Living in the world of unseen lines.

    This software isn't buggy its an infestation

    Comment


    • #3
      Lee, is that a nose-hit?
      Lately, it occurs to me
      What a long, strange trip it's been.

      2017 R1 (Offline programming)

      Comment


      • #4
        I supose you could put a report comment in the loop with that info in it or a variable that captures that info. Here is how to get that info into a variable (credit bitsandmore for this one):

        Code:
        ASSIGN/PART = STR(GETTEXT(191, 1, {FILEHEDR}))
        ASSIGN/REVI = STR(GETTEXT(192, 1, {FILEHEDR}))
        ASSIGN/SERI = STR(GETTEXT(193, 1, {FILEHEDR}))
        ASSIGN/STAT = STR(GETTEXT(194, 1, {FILEHEDR}))
        Craig
        <internet bumper sticker goes here>

        Comment


        • #5
          You can try inserting a page break / print command at the end of each loop.
          I used to be high on life but I built up a tolerance.

          Brown & Sharpe Global Advantage
          PCDMIS CAD++ v2011mr2
          PH10MQ/SP600M


          sigpic

          Comment


          • #6
            Page break does not work yet in 4.1. Will work in 4.2...
            ***************************
            PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
            Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

            Comment


            • #7
              Another incentive to have a current SMA I guess. Mo Money for Hex!
              I used to be high on life but I built up a tolerance.

              Brown & Sharpe Global Advantage
              PCDMIS CAD++ v2011mr2
              PH10MQ/SP600M


              sigpic

              Comment


              • #8
                When you loop like this, how do you differentiate between the different parts data. Is there the equivalent of a "NEWPART" command that I am not aware of?

                I get the idea of entering new info for the Header but does that automatically make the software think that it has a new part?
                Links to my utilities for PCDMIS

                Comment


                • #9
                  When you do a loop the data that is exported has the loop number imbeded in brackets into the dimension ID and the Feature ID

                  DIM LOC1 [1]= LOCATION OF POINT M2PNT1 [1] UNITS=MM


                  DIM LOC1 [4]= LOCATION OF POINT M2PNT1 [4] UNITS=M
                  Tolerance challenged ... Living in the world of unseen lines.

                  This software isn't buggy its an infestation

                  Comment

                  Related Topics

                  Collapse

                  Working...
                  X
                  😀
                  🥰
                  🤢
                  😎
                  😡
                  👍
                  👎