I've started using this, but it only works correctly in MDI. When testing in a live program, it crashes. The #32 and #33 variables are populated differently between MDI and my program. Would this be...
Type: Posts; User: quadtard
I've started using this, but it only works correctly in MDI. When testing in a live program, it crashes. The #32 and #33 variables are populated differently between MDI and my program. Would this be...
We have a group of older Mitsui Seiki HU40A horizontals, 3 of them have Fanuc 15M controls. One of the controls was reflashed with an old parameter file, and now the control is limiting the program...
Thanks for the reply, but that still didn't work.
Software is the same, and the service tech told me there is a way to set it back, but legally he can't say. That doesn't change the fact that the machine was purchased in 2008 before those rules...
Here's the back story. We had a Haas SL10(2008 model) lose its memory and lost all parameters. The company had no backup of the parameters, so we had a service tech come in to restore the parameters....
I need to reset my Z ref position, but I don't even know how to turn on Parameter Write. This is a M730MB controller with MAPPS. I think I may have found the correct Parameter, but if someone could...
I am deburring a through cross hole on an Okuma LT300 using the upper A turret. In Mastercam X6, I have profiles for my chamfers and am using C-axis contour toolpath feature. The issue that I'm...
Yeah, I understand using G140 and G141, the main issue just boiled down to having an M00 in the program on B side that didn't sync up with A side. Got that fixed and now everything is running...
I had a couple minutes between production to run through my program in machine lock, and everything read through. Will run tomorrow and see if I get my desired results.
Checked through it again, and it is reason #6. Look ahead is seeing an M0(for an operator to check a drill) on the B-turret before A-turret is finished. I will time out the toolpaths on A-turret and...
Yeah, I agree that its a mismatch in rotation commands, because that's essentially what I want. We are probably just going to get our applications guy from Gosiger in here and let them pick it apart...
It was either 1215-02 or 2472-01, pretty sure 1215. Basically alarmed under machine lock when verifying the program. The alarm happens when A-turret is at the main spindle with M110 active using live...
Throughout the majority of A-turret work(on C1), C-axis is clamped. It's near 50/50 live/stagnant for B-turret on C2.
Surely it does. I've seen LT's do multi-op work before. It's got to be more of a spindle sync m command issue or something, right?
Newbie to Okumas and multi-turret/spindle combos. We have a near permanent job on our LT300. Currently, we have all live tooling in the A-turret, and a combination of stagnant and live tooling in the...
Yeah, full reboot.
After removing a flash drive from the machine today to load a program, it is now stuck in remote jog mode. However, we don't have the auxiliary remote handle option. I am not able to switch between...
Got it figured out. I had the THEN statements in brackets, when I shouldn't have.
%
O3001(...)
N2
/#500=0 (PALLET COUNT RESET)
I verified that the machine does indeed have Macro B enabled. Turned bit 0 of 6006 to 1, and it still gives "PS0004:address not found" when approaching those conditions. The code stops short of...
I could use block delete to decide whether I would want to reset the pallet count. Regardless, I would want the initial reset to be at the front of the program.
That way, I can leave block delete...
Thanks angelw, I checked that bit, and it appears it is factory set to 0 on most i controls. Once we get another break in production, I will try it out to see if it gets the desired results.
That's what I'm wanting. Since it's an indefinite loop the loop (N1) occurs after the count reset. With block delete on, I can allow it to reset the count after 30.
BTW, I just editted the...
Maybe this approach:
%
O3001(PART)
N2
#500=0 (PALLET COUNT RESET)
I am aware my program shows changes at 3, 5, and 7. That was just to dry run and see if it worked.
No, I'd prefer it to count up, and at say 10 pallets, move on to tool2, at 20 move on to tool3, then at 30, either end the program, or loop back to a count reset based on the block delete.
Basically:
Reset Pallet Count
Call Tool #/Offset # Based on Pallet Count
M0 (Allow for pallet change confirmation)
Pallet A
Pallet Count +1
(24 work offsets calling subprogram)
By number of pallet changes.
I am working on a production program for a GX 480 APC. Fanuc Oi-MD controller.
Essentially, I am trying to run tool life management without reading a tool change. We tried to set up TLM before, but...
Yep, I found it. It took care of it. Thanks.
ok, so I just need to find the setting.