Driver timing for Longs motors DM860a
19 Oct 2019 22:40 #148370
by freddie
Driver timing for Longs motors DM860a was created by freddie
I need help on the driver timing for Longs motors DM860a stepper driver. Thanks
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 17782
- Thank you received: 5909
19 Oct 2019 22:57 #148372
by tommylight
Replied by tommylight on topic Driver timing for Longs motors DM860a
Try step_time and step_space set to 15.000. Or was it step_length ?
Please Log in or Create an account to join the conversation.
20 Oct 2019 14:32 #148408
by freddie
Replied by freddie on topic Driver timing for Longs motors DM860a
I have set the timing the same as Wanti motors DQ542 as listed in the wiki and it works but may not be right. They have similar kits. I have 5050 5050 500 500. The motors are not on the cnc yet so I can't be sure how they will work.
Please Log in or Create an account to join the conversation.
20 Oct 2019 16:12 #148411
by pl7i92
Replied by pl7i92 on topic Driver timing for Longs motors DM860a
15000
10000
8000
5000
this is what i use and get 5000mm/min easy at 0,005mm/step
10000
8000
5000
this is what i use and get 5000mm/min easy at 0,005mm/step
Please Log in or Create an account to join the conversation.
20 Oct 2019 20:43 #148431
by freddie
Replied by freddie on topic Driver timing for Longs motors DM860a
Thanks, I will try those settings.
Please Log in or Create an account to join the conversation.
23 Oct 2019 23:20 #148653
by andypugh
Replied by andypugh on topic Driver timing for Longs motors DM860a
It isn't a "tuning" thing. Either the step pulses are long enough and the system works, or they are not long enough and it doesn't
5000nS is normally long enough, but there is rarely any reason to go less than 15000nS.
5000nS is normally long enough, but there is rarely any reason to go less than 15000nS.
Please Log in or Create an account to join the conversation.
24 Oct 2019 00:02 #148660
by freddie
Replied by freddie on topic Driver timing for Longs motors DM860a
Ok it is becoming clearer to me. I was thinking is might be really critical to the brand of driver. The motors sound good now when testing. will but put on cnc soon. Thanks.
Please Log in or Create an account to join the conversation.
29 Oct 2019 10:03 #149035
by rodw
Replied by rodw on topic Driver timing for Longs motors DM860a
As said, there is no need to push the timings but I think your drivers are more capable than people give them credit for if my experience with the smaller Longs Motor DM542A is anything to go by. I think I got them down as low as 500/1500 without the failing. I don't think you could get away with that with a Gecko.
Please Log in or Create an account to join the conversation.
29 Oct 2019 10:11 #149036
by andypugh
If you need more pulses per second than there is room for with 5000nS step / 5000nS space (and that is 100kHz, or 3000rpm at 10x microstepping) then it is good that the drives can run with shorter timings.
If you were using a Mesa card then the 500nS timing would have been what was actually used. However bear in mind that with a parallel port using reset (doublestep) the on-time is actually the base-thread execution time[1], and that is typically more than 500nS.
[1] Technically the execution time of all functions between parport-write and parport-reset, rounded up to the reset time if required.[2]
[2] Which means that there is a reason not to use too-long timings if using reset, as the "rounding" up is a busy-wait loop, wasting CPU cycles.
Replied by andypugh on topic Driver timing for Longs motors DM860a
I think I got them down as low as 500/1500 without the failing. I don't think you could get away with that with a Gecko.
If you need more pulses per second than there is room for with 5000nS step / 5000nS space (and that is 100kHz, or 3000rpm at 10x microstepping) then it is good that the drives can run with shorter timings.
If you were using a Mesa card then the 500nS timing would have been what was actually used. However bear in mind that with a parallel port using reset (doublestep) the on-time is actually the base-thread execution time[1], and that is typically more than 500nS.
[1] Technically the execution time of all functions between parport-write and parport-reset, rounded up to the reset time if required.[2]
[2] Which means that there is a reason not to use too-long timings if using reset, as the "rounding" up is a busy-wait loop, wasting CPU cycles.
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
Time to create page: 0.106 seconds