Accuracy tuning
- JB-Motoring
- Offline
- Senior Member
Less
More
- Posts: 40
- Thank you received: 0
29 Aug 2019 11:38 #143546
by JB-Motoring
Accuracy tuning was created by JB-Motoring
Hey guys,
I need your help in accuracy tuning.
The servos are tuned well, now. So the F-Error is about 0.0001mm at F10.000mm/min in all axes.
But when it comes to cutting material, let's say a rectangle part of 20*30mm it cuts 20.045*30.045mm
Where is the mistake?
All the bearings ect. are like new- with the original Siemens 810M control it cuts on 0.001mm like programmed.
I hope you guys can help me with that.
Thanks, Joel
I need your help in accuracy tuning.
The servos are tuned well, now. So the F-Error is about 0.0001mm at F10.000mm/min in all axes.
But when it comes to cutting material, let's say a rectangle part of 20*30mm it cuts 20.045*30.045mm
Where is the mistake?
All the bearings ect. are like new- with the original Siemens 810M control it cuts on 0.001mm like programmed.
I hope you guys can help me with that.
Thanks, Joel
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19529
- Thank you received: 6553
29 Aug 2019 12:22 #143550
by tommylight
Replied by tommylight on topic Accuracy tuning
Encoder scale maybe ?
1000 ppr imstead of 1024 ppr ? Or similar, like metric to imperial ballscrews....
1000 ppr imstead of 1024 ppr ? Or similar, like metric to imperial ballscrews....
The following user(s) said Thank You: JB-Motoring
Please Log in or Create an account to join the conversation.
- JB-Motoring
- Offline
- Senior Member
Less
More
- Posts: 40
- Thank you received: 0
29 Aug 2019 13:38 #143556
by JB-Motoring
Replied by JB-Motoring on topic Accuracy tuning
Hey Andy,
The machine has 1250 Imp. Encoders - x4 = 5000 Imp/turn
The motors have 22 teeth, the leadscrews have 44 so the Ratio is 1:2
The leadscrew has a 5 mm thread pitch.
So what I did is calculate 5000 / 5 =1000- that's what stands in my ini file.
Is that wrong?
Greetings
The machine has 1250 Imp. Encoders - x4 = 5000 Imp/turn
The motors have 22 teeth, the leadscrews have 44 so the Ratio is 1:2
The leadscrew has a 5 mm thread pitch.
So what I did is calculate 5000 / 5 =1000- that's what stands in my ini file.
Is that wrong?
Greetings
Please Log in or Create an account to join the conversation.
- pl7i92
- Offline
- Platinum Member
Less
More
- Posts: 1875
- Thank you received: 354
29 Aug 2019 14:32 #143560
by pl7i92
Replied by pl7i92 on topic Accuracy tuning
is there a tool involved in the cutting
so you got the 0,045 offset
so you got the 0,045 offset
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19529
- Thank you received: 6553
29 Aug 2019 16:05 #143572
by tommylight
Replied by tommylight on topic Accuracy tuning
Andy? You mean Tom, right ?
If you are certain the encoders are 1250, that is good, so now you should do that calculation for 5.08mm leadscrew.
But do first check if the tool is compensated as PL7i92 mentioned, he might be on to something as you got the same distance error on both axis despite traveling diferent distances.
If you are certain the encoders are 1250, that is good, so now you should do that calculation for 5.08mm leadscrew.
But do first check if the tool is compensated as PL7i92 mentioned, he might be on to something as you got the same distance error on both axis despite traveling diferent distances.
The following user(s) said Thank You: JB-Motoring
Please Log in or Create an account to join the conversation.
- JB-Motoring
- Offline
- Senior Member
Less
More
- Posts: 40
- Thank you received: 0
29 Aug 2019 17:11 #143580
by JB-Motoring
Replied by JB-Motoring on topic Accuracy tuning
Oh shit, sorry ! I meant tommy / Tom :-D
I think I just saw andy :-D :-D
Sure is there a tool involved, that is also compensated- Same dia like before with the siemens control, now with linux it is driving me crazy :-D
So I need to compensate the error with the new encoder calculation with a pitch of the error +5mm ?
Thank you guys!
I think I just saw andy :-D :-D
Sure is there a tool involved, that is also compensated- Same dia like before with the siemens control, now with linux it is driving me crazy :-D
So I need to compensate the error with the new encoder calculation with a pitch of the error +5mm ?
Thank you guys!
Please Log in or Create an account to join the conversation.
- Todd Zuercher
- Offline
- Platinum Member
Less
More
- Posts: 4957
- Thank you received: 1441
29 Aug 2019 23:55 #143621
by Todd Zuercher
Replied by Todd Zuercher on topic Accuracy tuning
backlash?
The following user(s) said Thank You: JB-Motoring
Please Log in or Create an account to join the conversation.
- JB-Motoring
- Offline
- Senior Member
Less
More
- Posts: 40
- Thank you received: 0
30 Aug 2019 08:39 #143639
by JB-Motoring
Replied by JB-Motoring on topic Accuracy tuning
Oh lord,
I've made a mistake in writing down my actual setup.
The machine has 10mm pitch ball screws- so 1250*4=5000 | 1:2 Ratio = 5000*2 =10.000 | 10mm per turn =10.000/10 =1000 Imp/turn
So the Ini is definitly correct.
What I also have tested so far is set a dial gauge at lets say G54 X0 then moved G0 X250 G0 X0- It shows nearly 0, about 0.004-0.005 overschoot.
So the last part could be a mechanical problem?
What I dont want to understand is, that with the siemens controll, the mill just machined the programmed contour, and why should it now be more worse than before....
Thanks guys!!!
I've made a mistake in writing down my actual setup.
The machine has 10mm pitch ball screws- so 1250*4=5000 | 1:2 Ratio = 5000*2 =10.000 | 10mm per turn =10.000/10 =1000 Imp/turn
So the Ini is definitly correct.
What I also have tested so far is set a dial gauge at lets say G54 X0 then moved G0 X250 G0 X0- It shows nearly 0, about 0.004-0.005 overschoot.
So the last part could be a mechanical problem?
What I dont want to understand is, that with the siemens controll, the mill just machined the programmed contour, and why should it now be more worse than before....
Thanks guys!!!
Please Log in or Create an account to join the conversation.
Time to create page: 0.058 seconds