Hello Guest it is April 25, 2024, 04:22:32 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - norbigazda98

Pages: 1 2 3 »
1
Okay, I will, thanks :)

2
They do it all the time, except maybe when it's so slow that I cannot comprehend.

Or do you mean in the motor tuning?
The x managed 3500-4000, the y and z managed 5000-6000 velocity, and they all worked up to 350-400 acceleration.

3
Yes, 2400 is very reliable velocity.
I set lower acceleration because I didn't trust the higher settings to be fully okay.
When I ran a code it still went off position.

4
Well, I did what you told me to, but I don't understand what you say about the xml file or what should I do with  it.
So I did everything you told me to do and what I could, but the problem still persist.


My settings are on all axes: 2400mm/min velocity and 50mm/sec/sec acceleration, although it didn't skip on 150 and even on 200.
I use 4mm pitch  leadscrew and here are the motors details:
Step Angle (1,8°)   Motor Length (56mm)
Rate Current (2.8A)   Phase Resistance (0.9Ω)   Phase Inductance (2.5mH)   Holding Torque (1.26N.m)   Lead Wire (NO.: 4)
Rotor Inertia (280 g.cm)
Motor Weight (0.68 KG)
I use a 36V5A PSU inverter for the motors. I measured the voltage it produces and it's more than 35.5V all the time. I measured the current that the motors draw and it is never more than 2.9-3A even when all the axes are jogging at full speed.

5
Okay, I will. I'll have time on Wednesday afternoon (gmt+1)

6
Yes, you had it right. Backlash has nothing to do with it.

Basically it steps on almost every line of the code a step more in the positive direction than on the negative on a moving axis, regardless of which axis we are talking about.

But then sometimes it works great for 2-3 whole codes and then it is wrong again.

Do you have any other ideas before I buy a new controller board?

7
No, backlash wasn't enabled until yesterday's evening (in out country). I set z backlash to0.02 and left ever tithing else at 0 and then enabled the backlash and restarted the program.
Today I'll run several programs in the air to test if it really worked.

8
Well, I tried setting Z backlash to 0.02, which is a full step, and running the program in the air, and it didn't lose position.
Before that I tried 0.01, because that is the size of a step while microstepping, but the position losing still occured, although it was quite smaller.

So it seems like the backlash setting solved it, but I didn't have time for running the program long, so I might be wrong.

Do you say that backlash has nothing to do with it and these are false results? If so, then I'll have to buy another motion control board to eliminate that failure possibility.

9
I've been watching the stops and I think that they are too sharp. I mean, the machine stops too fast at the end of motions. It almost clicks when it stops when pulling back up from a drill or a carve path to safe z.

Maybe changing that will help. How can I change the deceleration?

I set acceleration back to 80, but I hope there is an option that sets the sector ration lower while acceleration stays the same.

Does Backlash has something to do with my problem? What is that in the first place?

10
So what you say is I shall buy a motion control board and if it doesn't work then I didn't need to buy it?

Pages: 1 2 3 »