When i try to mill a cirkle or a line. The machine make a smal stop for each raw in prg. I think its some parameter i need to change. Someone who know this issue ?
When i try to mill a cirkle or a line. The machine make a smal stop for each raw in prg. I think its some parameter i need to change. Someone who know this issue ?
If I understand correct:
Your shape on alluminum consists of arcs and straight segments and you want perfect surface without marks where arc is connected to straight line. Right?
hy angorgus use this at the begining of your program : VINPX=0.0 VINPY=0.0 VINPZ=0.0 (VINPA=0.0)
if it doesn't work, then try to check your tolerance parameters / kindly
ps : hy bunny
hello again using vinp=0 may be dangerious, and may lead to interference ( for example when drilling/tapping multiple holes ); try using 0.013, and if you will ever need to deliver something more accurate, then simply lower that value; do you know how vinp works ? do you wish for more explanations ?
for the rest 5%, please share more details / kindly
ps : thank you mr wizard for your lessons
hello again superman you are correct about those g codes
please, there is something that i don't understand; if i change vinp on a :
... lathe, nothing will happen, unless i use g65
... mill, then also real motion will change, even if i don't use g61; so what's the point of using g61 ? i have mill programs without g61, that begin with vinp 0, later change to custom vinp values, then revert to vinp 0, and they work; i know this trick from when mr wizard shared his oslow & ofast soubroutines
as a side note, i wonder why angorgus only hit 95%, and not full 100 / kindly
Why do you have active alarm? Maybe magazine interrupt is on? Please clear alarm. It seems as Superman says- exact stop is active. Did you check for M61? Are we seeing entire program with screen shot?
G94 may be desired on mill as stated.
Best regards,
hello mr wizard please, if i change vinp on :
... lathe, has no effect, unless g65 is used
... mill has immediat effect, even if i dont use g61
maybe at power on, lathe is g64(off), and mill is g61(on) ?
d alarm should have no effect / kindly
sometimes, it does not matter how many variants you test; what matters is the arhitecture; thus it may be possible that, untill a certain point, all testing is nothing but a wild shot
on mills are more tolerance parameters than on a lathe :
... lathe : droop & rapid droop
... mill : in pos width, in pos 2, clamp, cycle , point r , retract , return
g60 is udp / unidirectional positioning, one shot/not modal; i recomand to avoid using it at this stage
about which code is active, 61/64, there may be shown, somewhere, on your screen, which is active; for example, on p300, is in bottom right corner; but i wouldn't look for that, because i have noticed that changing vinp on mills has effect even if there is no 61 inside the code; this means that 61 is power on default, or 61 and vinp are targeting different accuracy functions, and, to test this, simply change approach :
... rough approach : you have a set of codes with different vinp values; put at the begining g61 and run them, then replace g61 with 64 and run them again, maybe you will notice a difference
... direct approach : using file asign & system variables, to record real tolerance and each block duration; when testing codes, there may be differencies easy to spot ( like how you noticed that there is a stop ), but, also, there are those that you can not spot ( for example something faster than your reaction time ); you can really shorten your trials using fwritc vdin and vapa* ( hoping that those can run on your machine )
i have been recently looking into such parameters, by colecting data, pls check attached; 1st task, is to build a code that delivers time decrease, as vinp increases, then use this as a template / kindly
hello for mills, besides vinp, there is also vipb; so far, i have no specific details on how they are being switched but my guess is that there is a similitude to lathes drop and rapid droop / kindlyi have noticed that changing vinp on mills has effect even if there is no 61 inside the code; this means that 61 is power on default, or 61 and vinp are targeting different accuracy functions
Hi
Now i find the solution !!! The NC optional parameter no 2 bit 7 set to 1. standard is 0 No buffering for next raw in program now it´s work perfect !!