What's new
What's new

Carousel movement failure causing error 626

FS_Engineering

Plastic
Joined
Jul 14, 2021
Location
Boston, MA
Hello all,

I've got a 2006 Haas VF1 SS (15k rpm). It runs great but there is one repetative issue that I cannot figure out.
My post calls for the next operation's tool immediately after it changes from the previous operation tool to the current operation tool. Such as: The program is started, carousel moves to operation 1 tool, it is loaded into spindle, the next command calls for carousel to move to op2 tool, and then it continues on with operation 1. when op1 ends, op2 tool is already positioned and can be swapped immediately. once op2 tool is in the spindle, the carousel moves to op3 tool and waits while the op2 runs. and so on...

Sometimes, at the end of an operation, it throws the 626 error: Tool Pocket Slide Error. What I have figured out is, the error will subsequently be thrown if the carousel, for whatever reason, ignores the "next operation tool" request at the beginning of the current operation. I'm not sure if it ignores it (as it's just doing what it's told) or the error is actually thrown at that point in time and does not present on the screen until the end of the current operation...

This is a snippet of a program that consistently throws the error when the 4th operation (N4) ends and it's supposed to get the tool for the 5th operation (N5, T7). When op3 starts, the machine spindles op 3 tool from the carousel, then moves the carousel to op4 tool, and starts the actual op3. When op3 is done the machine swaps op3 tool for op4 tool and starts op4. Prioir to starting the actual operation 4, the carousel is supposed to move to op5 tool, but it does not. Once op4 is complete (or almost complete), the spindle shuts off and the error code is thrown. sometimes when the error is thrown the current line of code is not quite at the end of the operation, it can be 10-50 lines from the end. So I hit reset, find N5 in the program and hit start, it swaps the tool and runs operation 5.

I suspect it has to do with some timing issue in the parameters such as 62, 306, etc. I've attached a pic of my current parameter settings having to do with the carousel and tool changing. I'm not sure if there's one that's just radiccially wrong and causing this issue.


%
O1000 (NHC OP1_MILLING)
N100 (COMPENSATION-WEAR)
N102 (REV-0.70)
N104 (JUL-14-2021-5:48:13PM)


N106 (TOOL 3 - DIA 12.7)
N108 (TOOL 4 - DIA 4.762)
N110 (T5-COBALT/ChipClearing - 6.7564mm)
N112 (TOOL 6 - DIA 3.175)
N114 (T7-COBALT/ChipClearing - 1mm)


N1 G90 G17 G40 G80 G00
N116 M06 T3 ()
N118 T4
N120 (iRough-contour7)
N122 S4693 M03
..........(operation code using T3 removed)
N15412 M01

N2 G90 G17 G40 G80 G00
N15414 M06 T4 ()
N15416 T5
N15418 (iRest-contour2-1)
N15420 S8961 M03
..........(operation code using T4 removed)
N16188 M01

N3 G90 G17 G40 G80 G00
N16190 M06 T5 (COBALT/ChipClearing - 6.7564mm)
N16192 T6
N16194 (D-drill)
N16196 S453 M03
..........(operation code using T5 removed)
N16208 M01

N4 G90 G17 G40 G80 G00
N16210 M06 T6 ()
N16212 T7........(I have witnessed the T6 tool change and then the carousel NOT moving to T7 for whatever reason)
N16214 (iRough-contour6)
N16216 S10778 M03
..........(operation code using T6 removed)
N16714 M01

....THIS IS WHERE ERROR IS THROWN....

N5 G90 G17 G40 G80 G00
N16716 M06 T7 (COBALT/ChipClearing - 1mm)
N16718 (D-drill1)
N16720 S3500 M03
..........(operation code using T7 removed)
N16744 M06 T3
N16746 M30
%

IMG_5832.jpg
 
I would stage your next tool a little deeper in the code, like maybe when you call tool length or turn on coolant. Give the carousel time to swing the pot up before it starts indexing to your next tool.
 
Interesting. Thank you for the replies! If it is a timing thing then the next issue I'll tackle is changing the post so it places the tool change deeper in the code as you suggested. dont want to have to manually change code for each job.

I've seen that troubleshooting page before. Thank you for posting it again because, the first item under the 626 alarm is, "A tool change was attempted with the pocket already down". Ok, I understand that, but I assumed the machine would be smarter than that! I figured instead of throwing an alarm, it would use logic to say, hey maybe it's performing a tool change, and then wait a few seconds to see if the pocket returned to the up position before throwing the alarm. Instead if the tool change occurs at the beginning of an operation, and before it can finish the tool change it attempts to move pockets, itll throw the alarm? That is unfortunate. I wish there was a timing parameter I could change to pause the pocket move attempt for 2 seconds to allow a current tool change to complete before trying to move pockets etc. I guess if none of the parameters are for a pause before pocket moves, the way around it is to move the pocket move deeper into the code as you said.

I read that linked post, ty again. I'm pretty sure it's not a switch or sensor. I've gone in and blown all debris out from around the sensors and cleaned them with a rag before to try and resolve this issue. And with it occuring repeateadly in certain code on cue makes me think its a logic timing issue. I will reseat the related electrical connectors and see if it has any effect.

Other than that I will look into updating the post to move the pot move to later in the code.

Will update later one. Thank you again for the help!
 








 
Back
Top