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

Scanning Setup with Readpoint

R2ah1ze1l
Hello everyone,

Lets start with the 'light' information:
Leitz: LSPX1H_T
Software: 2015.1
Mach: DEA 15.30.10

The machine allows me a good area in 'Y' to locate my part, it also has 12x slot locations that are put in at a nearly 40º angle to my -A- plane at 30º increments about -B-.

I am trying to get the proper combinations to allow the scanning to remain in the program and NOT drive me crazy when swapping between offline/online programming.

Here's what I do:
Locate the probe with readpoint, perform a quick DCC check to define where part is on table
Move probe to desired -C- location and have part physically rotated.
Perform 1 more quick DCC check to re-define where part is on table.
Now it is a FULL ABC pickup then off to measuring the unit.
All regular points work PERFECT to measure/evaluate, scanning on the other hand.....

When it gets to the point of scanning, production is having to CANCEL the run cycle and regenerate the scan path in order to complete the inspection. This is not acceptable as I'd like this program to be free of user intervention (run at offshift times). Trying to determine what should be my setup approach:
Current Scan parameters:
Exec Mode: Defined
Nominals Method: FindNoms

^This has been what I used to perform my scans and I am begining to think I need to swap them. Next Trial:
Exec Mode: Relearn
Nominals Method: Nominals

Online to Offline is really a seperate topic and I have a work around with it right now, but maybe some of you have already found a method that can be supplied.

Appreciate anyones help, I'm not used to scanning and it drives me BONKERS that scan parameters are not 'sticky' like auto/measured features!


  • in reply to William Johnson 
               ASSIGN/MOVE_IN_X=.25 + 0
              ASSIGN/MOVE_IN_Y=-0.5 + 0
              ASSIGN/MOVE_IN_Z=1.44 + 0
              ASSIGN/MOVE_OUT_X=.25 + 0
              ASSIGN/MOVE_OUT_Y=-0.5 + 0
              ASSIGN/MOVE_OUT_Z=1.44 + 0
              ASSIGN/ST_1=0.3443171 + 0
              ASSIGN/ST_2=0.07 + 0
              ASSIGN/ST_3=1.4825477 + 0
              ASSIGN/ST_S=0.696 + 0
              ASSIGN/SB_1=0.1792544 + 0
              ASSIGN/SB_2=0.07 + 0
              ASSIGN/SB_3=-1.4732385 + 0
              ASSIGN/SB_S=0.376 + 0
              ASSIGN/SLR_H1=.3575422 + 0
              ASSIGN/SLR_L1=0.2082318 + 0
              ASSIGN/SLR_D=0.07 + 0
              ASSIGN/SLR_Z1=1.2746827 + 0
              ASSIGN/SLR_Z2=-1.3159458 + 0
              ASSIGN/SLR_S=24 + 0
              ASSIGN/BSLR_X=0.3545 + 0
              ASSIGN/BSLR_Y=0.3 + 0
              ASSIGN/BSLR_Z=-0.0095 + 0
              ASSIGN/BSTB_X=0 + 0
              ASSIGN/BST_Z=1.6935 + 0
              ASSIGN/BSB_Z=-1.6935 + 0


    Sorry, I was at the character limit count...
  • in reply to Kp61dude!
    I have a point in the program where the probe stops and directs them to rotate the part so it is on X0. Then DCC goes bck and makes a FIRM alignment. The variation I can understand would be I have a long Y axis and the part can be shifted backward/forward from 1 setup to the other. The part is typically located in the same area everytime, so that shouldn't be causing me the hardship I'm seeing. (Atleast I don't believe)
  • in reply to Kp61dude!
    The area being scanned is on an approximate 39deg angle from -A-, and repeats every 30deg about the unit.
  • The area marked in my code with red:

    The scan has been completed, I have extracted the elements needed to know it's center so I could align and perform a deeper check with 4 touches. (Ensure the feature is perp to the face it was milled through)

    Once it crashes, we stop the program, regenerate the paths and restart execution from just before the scan. All systems go for all 12x locations, I just need to get out of needing to stop the program and regenerating the paths, I can't seem to get it though.
  • Once it crashes, we stop the program, regenerate the paths and restart execution from just before the scan. All systems go for all 12x locations, I just need to get out of needing to stop the program and regenerating the paths, I can't seem to get it though.

    Explain your crash.... before the scan even begins, midway, at the end, etc.?
  • The scan finishes execution, then I build some features from the scan itself. Those features are used to align to the center of the scan location so I can take 4 touch points deeper inside just to show perpendicularity of the slot. Normally, on first run after it aligns to the scanned data the first touch point ' PNT_BS01_01' results in a crash.

    PNT_SA_1 =FEAT/POINT,CARTESIAN,YES
    THEO/<0,0.07,0.6658>,<0,-0.6314881,0.7753855>
    ACTL/< 9.1764,0.07,0.6658>,<0,-0.6314881,0.7753855>
    CONSTR/POINT,MID,CIR_SL_01,CIR_SR_01

    Above is typically what I end up seeing the 'actual' adjust to. Once I go through the process of generating the scan paths again, everything runs through fine.

    Another colleague of mine just noted that I should be using NULLFILTER instead of VARIABLE as the DIR1.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement