[deadlykitten]

most toolpaths are a row of geometrical entities : lines & arches; let's simplify and consider that there are only lines; now, let's simplify even more, and consider that there are only 2 lines, perpendicular : one among x, and other among y, and each line's length is 100; coordinates :
... line 1 : point A(0,0) point B(100,0)
... line 2 : point B(100,0) point C(100,150)

in reality, when machine will begin to cut line 2, it won't be at point B, but a bit before it; machining, cutting, is not about absolute values, but about relative values; for example, if the machine will begin cutting line 2 when being at coordinate:
... (99.998,0), thus at B-0.002, thus in a vecinity of 0.002 arround B, then i guess you will be satisfied
... (90,0), thus in a vecinity of 10 arround B, then i guess you will have questions

vinp is a parameter for vecinity :
... vinpx : for x axis
... vinpz : for z axis
and so on, there is a vinp for each axis, including rotary axis ( for example when having a 4th axis or a trunion ), and others

if you need to machine a dimension that is tolerated at 0.005, then it may be better to use vinp<0.005, but also, okuma machines are pretty steady in their own

your vinp value was too small, thus making the machine to lose time, by performing suplimentary check, thus machine was moving at a precision that was too much for your parts

for mills, lowest vinp is 0.001, and highest is between 1 and 10; vinp 0 doesn't mean that accuracy is at it's best, but that accuracy control is no longer done via parameter input from operator, thus, if you use vinp 0, then you no longer control the accuracy, but leave it to the cnc to decide on lathes, vinp 0 will actually trigger the best accuracy (<1um), while accuracy control mode is no longer toogled by vinp<>0, but by g code (65 64) / kindly

[angorgus]

most toolpaths are a row of geometrical entities : lines & arches; let's simplify and consider that there are only lines; now, let's simplify even more, and consider that there are only 2 lines, perpendicular : one among x, and other among y, and each line's length is 100; coordinates :
... line 1 : point A(0,0) point B(100,0)
... line 2 : point B(100,0) point C(100,150)

in reality, when machine will begin to cut line 2, it won't be at point B, but a bit before it; machining, cutting, is not about absolute values, but about relative values; for example, if the machine will begin cutting line 2 when being at coordinate:
... (99.998,0), thus at B-0.002, thus in a vecinity of 0.002 arround B, then i guess you will be satisfied
... (90,0), thus in a vecinity of 10 arround B, then i guess you will have questions

vinp is a parameter for vecinity :
... vinpx : for x axis
... vinpz : for z axis
and so on, there is a vinp for each axis, including rotary axis ( for example when having a 4th axis or a trunion ), and others

if you need to machine a dimension that is tolerated at 0.005, then it may be better to use vinp<0.005, but also, okuma machines are pretty steady in their own

your vinp value was too small, thus making the machine to lose time, by performing suplimentary check, thus machine was moving at a precision that was too much for your parts

for mills, lowest vinp is 0.001, and highest is between 1 and 10; vinp 0 doesn't mean that accuracy is at it's best, but that accuracy control is no longer done via parameter input from operator, thus, if you use vinp 0, then you no longer control the accuracy, but leave it to the cnc to decide on lathes, vinp 0 will actually trigger the best accuracy (<1um), while accuracy control mode is no longer toogled by vinp<>0, but by g code (65 64) / kindly

Hi

I test 0,015 this not work. 0,005 is 95%..Is it not possible to get 100% no stop at all ?

Krg
GG

[deadlykitten]

hy, something is fishy, because 0.015 should work much faster than 0.005

0.005 - duration 1
0.015 - duration 2
0.150 - duration 3

in reality, duration 3 < duration 2 < duration 1, while, in your case, this is not happening

please, provide more data, or something, so to see what you see; what type of control do you have ? pls share testing program / kindly

[angorgus]

Hi

I have test 0.005 and 0.015. 0.005 is working with very very smal stop. 0.015 is not working. I get smal stop.

Krg
GG

[deadlykitten]

pls share your test program

[angorgus]

pls share your test program

Hi

See my program

[deadlykitten]

G95 S1000 F50 may be too much for vinp testing; that is close to rapid speed, and it may be possible that you are not even getting close to that feed during cutting

try this toolpath in xy plane : _|?|_|?|_|?|, no rad comp, keep things simple, be sure that you reach programmed feed, like for example, if line length is 100, then use a feed that will execute each line in 10 seconds; let's try S1000 F0.4, that's 400mm/min, so 100mm will execute in 1/4minutes; play with feeds, and vinp, but within a normal range

another simple toolpath in xz plane : |_|, z segment 100, x segment loooong, like close to max travel, and execute this in rapid; changing vinp should definetly show how 0.001 is slower than 0.1

sometimes it may be hard to spot a time difference, so a time system variable should help; try VC1=VDIN[1000]; if vdin does not work, then i don't know what does

you should look for a simple code, that will show how increasing vinp leads to less time duration / kindly