hexagon logo

Questions about DCC Alignment and looping correct procedure

So, maybe this is a stupid question, or I'm thinking too much into it, idk. So, I'm still using that same program that I was tinkering with in my last post. I have 2 parts on the 2 table, and I am using 2 probes to inspect them both. Probe 1 inspects part 1, when it's finished it comes down in Y -11.5 inches, and then does the same exact routine on the second part. It goes up in Z+, changes probes, then inspects part 1 for smaller holes, goes up, then back down in Y -11.5 inches to catch the holes on the second part. My question is.... should the DCC part of the program be extended for the second probe as well? What I'm trying to say, is after the probe changes to start inspecting holes, do I need to do another DCC alignment on the first part again to make sure the comp isn't using the second parts variables? I haven't used looping at all so I'm worried that some of the data from part 1 will get screwed up or transposed onto part 2. Also, with looping, you just set the offsets in x,y, z, or rotate it or whatever you want to do.... Does it create another alignment for the second part?? It's own separate alignment? Or does the second part literally just drive off of the first parts coordinates, just shifting it down or over or whatever (which imo is SUPPPPPPPER risky) because all you are doing is just shifting the movements down without actually accounting for where the second part really is. You might be able to get away with that if you are using a perfect setup/ground pins, yadda yadda...but...??? I must be thinking too hard about this problem. But I really do want to know the *why* and what is under the hood of the machine, not just accepting "that's the way it is" just because. Thank you for your time!
Parents
  • At the start of a loop you should recall an alignment that is a rough local alignment of the first part or fixture, robust enough to eliminate any inconsistencies in part orientation in your setup.

    You can even start your loop with a super prudent prehit/retract of 0.500" and slow move/touchspeeds to make sure you're not hammering probes into parts (and have a few mins to spare per run).


    --You control how the loop references alignments at start of loop. Your current alignment at the loop start command is what it will offset from... so if that's recall startup only... it will recall startup then offset whatever you prescribe it. if you have a readpoint alignment, then loop, you will be offsetting from that readpoint.
  • I *think* I'm doing that. The first 2 alignments (manual and the first DCC) are aligned to the first part. I just checked and...somehow the 3rd alignment (2nd DCC alignment) is aligned to the SECOND part...which confuses the heck out of me because I don't even have a model to click on to select the second part for alignment... Did the loop shift the alignment too by -Y11.5 inches??? I don't know how it works so I can't explain it. Can the loop actually shift alignments??
Reply
  • I *think* I'm doing that. The first 2 alignments (manual and the first DCC) are aligned to the first part. I just checked and...somehow the 3rd alignment (2nd DCC alignment) is aligned to the SECOND part...which confuses the heck out of me because I don't even have a model to click on to select the second part for alignment... Did the loop shift the alignment too by -Y11.5 inches??? I don't know how it works so I can't explain it. Can the loop actually shift alignments??
Children
No Data