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
  • Rather than dissect this let's go to the heart of your question. From there you can decide what you need to do to suit your needs.
    "Does it create another alignment for the second part?? It's own separate alignment?" No, not unless you tell it to
    " Or does the second part literally just drive off of the first parts coordinates, just shifting it down or over or whatever" Yes
  • , ok I'm super sorry for being overly confusing, I'll try to describe the part without talking too much because a lot of it really doesn't matter, this has something to do with loops or parameter settings or something I'm not thinking of. So, basically, this program that I've got hashed out came from a program where I was just running one part. I then wanted it to come down in Y -11.5 inches and identically inspect another part of the same part number. (the final program will have who-knows-how-many, I will have to just adapt to our situations at the time) It starts with a 4mmx20 probe, I do a basic manual alignment the first time I've opened this program from another part number. I then turn a loop on, start at 1, end at 2, shift down in y -11.5 inches. Then, I do 2 DCC alignments on the first part a rough one, then a finer one. Then, it's measuring time. I measure all the features of part 1 with the 4mm x 20 mm probe. It then does what I tell it to: go down in -Y by 11.5 inches and perform the exact routine it just did. Awesome, that works fine! After the second part is done, it goes up maybe 3 or 4 inches in Z+, goes over in X+ and then to me the operator so I can change probes to a 1MMx40MM probe that I have to use to measure super small holes (.100 in diameter, and I have to change probes out manually with the magnetic lock until we get a tool changer). The program then does an auto-cal probe routine that I have set up with some parameter settings to just probe one tip : A0,B0. It then, goes up and over to the first part again to do it's thing with the second probe, measuring small holes basically. After the first part, it goes up in Z a small amount, perhaps 1 or 2 inches, then goes down in Y- 11.5 inches once again. It inspects the second parts tiny holes, and then goes up, over in X+, and back to me so I can change it back to the original probe. At that time, I swap probes, and it does an automatic recalibration with the first probe. The reason for that is so if I want to take the two parts off the table and throw 2 new parts up there, all I have to do is just start it from the DCC point again. I hope this helps because I feel like I'm getting so close to a solution. This forum and you people really help out!!! Btw, the reason I'm asking all of this is because I'm getting the looping to work right....it's measuring the first part with probe 1, the second part with probe 1, doing a tool change and recalibration, then inspecting parts 1 and 2 with the second probe. Changing, recalibrating and ending.. Just find, there are no crashes. It's just that when I run one part by itself, the part is perfect, and when I put two up there, it's throwing some of my holes OT.... I can't write a program that is going to throw good parts out as OT. That's why I'm inquiring about the alignment changing because of looping or in general just the parameters.
Reply
  • , ok I'm super sorry for being overly confusing, I'll try to describe the part without talking too much because a lot of it really doesn't matter, this has something to do with loops or parameter settings or something I'm not thinking of. So, basically, this program that I've got hashed out came from a program where I was just running one part. I then wanted it to come down in Y -11.5 inches and identically inspect another part of the same part number. (the final program will have who-knows-how-many, I will have to just adapt to our situations at the time) It starts with a 4mmx20 probe, I do a basic manual alignment the first time I've opened this program from another part number. I then turn a loop on, start at 1, end at 2, shift down in y -11.5 inches. Then, I do 2 DCC alignments on the first part a rough one, then a finer one. Then, it's measuring time. I measure all the features of part 1 with the 4mm x 20 mm probe. It then does what I tell it to: go down in -Y by 11.5 inches and perform the exact routine it just did. Awesome, that works fine! After the second part is done, it goes up maybe 3 or 4 inches in Z+, goes over in X+ and then to me the operator so I can change probes to a 1MMx40MM probe that I have to use to measure super small holes (.100 in diameter, and I have to change probes out manually with the magnetic lock until we get a tool changer). The program then does an auto-cal probe routine that I have set up with some parameter settings to just probe one tip : A0,B0. It then, goes up and over to the first part again to do it's thing with the second probe, measuring small holes basically. After the first part, it goes up in Z a small amount, perhaps 1 or 2 inches, then goes down in Y- 11.5 inches once again. It inspects the second parts tiny holes, and then goes up, over in X+, and back to me so I can change it back to the original probe. At that time, I swap probes, and it does an automatic recalibration with the first probe. The reason for that is so if I want to take the two parts off the table and throw 2 new parts up there, all I have to do is just start it from the DCC point again. I hope this helps because I feel like I'm getting so close to a solution. This forum and you people really help out!!! Btw, the reason I'm asking all of this is because I'm getting the looping to work right....it's measuring the first part with probe 1, the second part with probe 1, doing a tool change and recalibration, then inspecting parts 1 and 2 with the second probe. Changing, recalibrating and ending.. Just find, there are no crashes. It's just that when I run one part by itself, the part is perfect, and when I put two up there, it's throwing some of my holes OT.... I can't write a program that is going to throw good parts out as OT. That's why I'm inquiring about the alignment changing because of looping or in general just the parameters.
Children
No Data