Correct way to set Steps Per mm for X and Y

droftarts

@developeralgo222 If the step rate is limiting the top speed, yes, you need to reduce the step per mm rate. Reduce the number of steps per rotation on the driver, then adjust M92 the corresponding amount. Yes, this will allow for faster speeds, at the expense of some accuracy between steps. 100 steps per mm (so 1000 steps per revolution) would be 1 step per 100th of a mm, so if that's the accuracy you are looking for, reduce it down to that. Top speed limited by the step rate should correspondingly increase up to roughly 200000/100 = 2000mm/s, or 120000mm/min.

For jerk and acceleration, most calculators will show the acceleration ramp for any particular move. Obviously, short moves may not hit top speed. Jerk is generally not modelled, but is best kept low ie between 5-10mm/s (300-600mm/min), but can depend on the weight of the axes and torque of the motors.

Whether jerk, acceleration and speed are achievable (or cause skipping steps) is really down to testing, and 'smoothness' is largely down to personal preference, though things like mid-band resonance (see https://www.geckodrive.com/support/mid-band-instability/) in the motors can cause issues at specific speeds. Generally you want to find the maximum jerk/speed/acceleration before step loss or motor stall, and probably leave a 20% safety margin. Unfortunately this is very difficult to calculate, because it depends on so many different variables, some inherent and specific to your machine. The Thomson Linear calculator gives some indication what accelerations and top speeds are suitable for ballscrews.

Ian

developeralgo222

@droftarts

i managed to test X & Y with the following configs. Because i modified the External Drivers dip switch settings to 10000 pulses/rev for testing

TESTING for Speed, Acceleration and Jerk for X & Y axis

NEMA 34 Stepper 1.8° Motor = 200 pulses/rev
Ballscrew Pitch = 10 mm/rev
HSS86 Driver microstep setting for X & Y axis with NEMA 34 , 8.0 N.m = 10,000 pulses/rev
This gives (10000 pulses/rev ) / (10mm/rev) = 1000 pulses/mm but that's too high so Duet3 config is set to 100 steps/mm i.e M92 X100 Y100 . This results in 10:1 ratio on the openPnP side ( 10mm move on OpenPnP == 1 mm move on actual machine ). Not sure if i need to set OpenPnP side differently from what's on Duet for this ?
On OpenPnP side i have X & Y Axis steps/mm set to the same as Duet3 Config.g at 100 steps/mm

Results:

Works ok with Max speeds = 1500 mm/s ==> 90000 mm/min but i need to find out how to have OpenPnP movement synced with Duet's so that 1mm move on OpenPnP == 1mm move on Machine axis itself.
It's fast and smooth no jerking . Not sure if to drop down to 1000 pulses/rev on the driver from 10000 pulses/rev in order to have 1:1 ratio between OpenPnP & Duet settings.
With microstepping at 1000 pulses/rev on HSS86 Driver. its a a little jerky and stalls the motor or error the drive with any feed rate abovet 6000 mm/min

M569 P0.0 S0 T2.5:2.5:2.5:2.5           ;  2.5us timings between pulses for X-axis
M569 P0.1 S0 T2.5:2.5:2.5:2.5           ;  2.5us timings between pulses for Y-axis
.
.
.
M350 Z16 U16 V16 W16 A16 B16 C16 D16 'G16 I1         ; configure microstepping with interpolation.
M92 X100.00 Y100.00 Z20.00 U20.00 V20.00 W8.888 A8.888 B8.888 C8.888 D8.888 'G8.888     ; set steps per mm . Ballscrew Pitch = 10mm/rev. 
M566 X900000.0 Y900000.0 Z900.0 U900.0 V900.0 W900.0 A900.0 B900.0 C900.0 D900.0 'G900.0  P1     ; set maximum instantaneous speed changes (mm/min) and use Jerk policy 1
M203 X90000.00 Y90000.00 Z24000.00 U24000.00 V24000.00 W3600000.00 A3600000.00 B3600000.00 C3600000.00 D3600000.00 'G3600000.00    ; set maximum speeds/feedrate (mm/min)
M201 X5000.00 Y5000.00 Z2000.00 U2000.00 V2000.00 W180000.00 A180000.00 B180000.00 C180000.00 D180000.00 'G180000.00     ; set accelerations (mm/s^2)
M906 Z1360.0 U1360.0 V1360.0 W560.0 A560.0 B560.0  C560.0 D560.0 'G560.0  I100        ; set motor currents (mA) and motor idle factor in per cent

droftarts

@developeralgo222 said in Correct way to set Steps Per mm for X and Y:

This gives (10000 pulses/rev ) / (10mm/rev) = 1000 pulses/mm but that's too high so Duet3 config is set to 100 steps/mm i.e M92 X100 Y100 .

You've gone the other way, with MORE steps per revolution, so you need MORE pulses per second. You would set M92 X1000 Y1000. Not sure what you mean by "but that's too high". Your max speed will be more limited than before.

If 1000 pulses/rev is jerky, try 1600 pulses/rev, ie 200 full steps per revolution * 8 microsteps (1000 pulses/rev gives 5 microsteps between full steps). M92 X160 Y160.

Ian

developeralgo222

@droftarts

Do you mean setting steps /mm on Duet to 1000 steps/mm ? i.e
M92 X1000 Y1000 ? as you said it will limit the speed. i think my problem is that it seems 100 steps/mm ( 1000 pulses/rev) is fine . But when i enter that value on the X & Y axis on the OpenPnP side its on 10:1 ratio . That is 10mm move on the OpenPnP software /Duet DWC console actually moves machine X & Y 1 mm physically i.e 10:1 ratio. That creates a few issues with OpenPnP configuration , it assumes 1:1 relation in steps/mm that is configured on Duet3 as it uses it for other movements like backlash calculations etc

droftarts

@developeralgo222 Set M92 to whatever you set the driver pulses/rev to, divided by 10. eg 10,000 pulses/rev = M92 X1000, 3,600 pulses/rev = M92 X360, 1,000 pulses/rev = M92 X100. Then it should be a 1:1 relationship. You can't cheat the numbers to get performance, because you always have to send the step pulses to the motor, it's just the scaling that will be wrong.

I don't know why OpenPNP changes to a 10:1 relationship when it drops low, you'll have to ask them.

Ian

developeralgo222

@droftarts
Fantastic thanks for that clarification. So from your explanation it implies that the Higher "steps/mm" number on Duet M92 Xnnn Ynnn ===> The Lower the speed /Feedrate (Limited Speed) ?

developeralgo222

@droftarts

Can you confirm . I just tested with Duet DWC Console ( Not involving OpenPnP at all)

HSS86 Driver is set to 10000 pulses/rev == (10000 pulses/rev ) / 10 mm/rev = **Maximum Possible/allowed of 1000 pulses/mm at 10000 pulses/rev HSS86 Driver setting **

Test 1: M92 X1000 Y1000 get 1:1 relation with Max Speed = 200 mm/s == 12000 mm/min before stall/skip

G1 H2 X100 F12000

Test 2: M92 X100 Y100 get 10:1 relation with Max Speed = 2000 mm/s == 120000 mm/min before stall/skip

G1 H2 X100 F120000

This seems to indicate that the HSS86 Driver set value using DIP Switch to 10000 pulses/rev == 1000 pulses/mm is simply maximum reference value allowed at that setting as per the Ballscrew Pitch.

So if you configure something like M92 X50 Y50, i.e 50 steps/mm on Duet then Duet will send that along to the driver and since the driver is expecting 10000 pulses/rev == 1000 pulses/mm, it takes that (1000 pulses(steps)/mm ) / 50 steps/mm = 20 . i.e every measurement on Duet in relation to X & Y axis motor movements will be in 20:1 ratio as per this example where 200mm on Duet will move 10 mm on actual Machine

G1 H2 X200 F100000

At first i thought it was Duet /OpenPnP but i just realized its not. The ratio occurs depending on what Duet/OpenPnP send to the HSS86 external driver and the HSS86 Driver calculates the measurement ratio for moving the motor

Since i am able to configure a lower value of M92 X100 Y100 and it works fine and sends that lower steps/mm value from Duet DWC to the driver towards the motor creating 10:1 ratio measurement.

This test outcome is a surprise to me.

droftarts

@developeralgo222 I think it's doing exactly what I'd expect it to do. The Duet doesn't know how you have set the driver pulses/rev. If you set it to 10000, and M92 X100 Y100, and command 100mm, it will send 100 (steps per mm) * 100 (mm), so 10000 steps. So the driver will move one revolution, ie 10mm of the ballscrew. As far as the Duet is concerned, it moved 100mm, and the speed and acceleration calculations will be based on that. Whatever is reported in DWC is x10 overstated. What are you struggling with here? The driver is not calculating "the measurement ratio for moving the motor", it's just moving how many steps it receives.

Ian

developeralgo222

@droftarts
I think you clearly explained it to me . i was struggling to understand the link & calculations as to why if i sent a command of 100mm and i have HSS86 Driver with 10000 pulses/rev and M92 X100 Y100 configured . what was going on .

That's clearly explained now i see why i was getting all confused about the command and the steps/mm calculations

Thanks so much for explaining that clearly

developeralgo222

@droftarts ,

Thanks for your help. Here is what i have adjusted them to

M569 P0.0 S0 T2.5:2.5:2.5:2.5           ;  2.5us timings between pulses for X-axis
M569 P0.1 S0 T2.5:2.5:2.5:2.5           ;  2.5us timings between pulses for Y-axis
.
.
.
M350 Z16 U16 V16 W16 A16 B16 C16 D16 'G16 I1         ; configure microstepping with interpolation.
M92 X100.00 Y100.00 Z80.00 U80.00 V80.00 W8.888 A8.888 B8.888 C8.888 D8.888 'G8.888     ; set steps per mm . Ballscrew Pitch = 10mm/rev. 
M566 X900.0 Y900.0 Z900.0 U900.0 V900.0 W900.0 A900.0 B900.0 C900.0 D900.0 'G900.0  P1     ; set maximum instantaneous speed changes (mm/min) and use Jerk policy 1
M203 X51000 Y51000 Z6000 U6000 V6000 W3600000.00 A3600000.00 B3600000.00 C3600000.00 D3600000.00 'G3600000.00    ; set maximum speeds/feedrate (mm/min)
M201 X5000.00 Y5000.00 Z2000.00 U2000.00 V2000.00 W180000.00 A180000.00 B180000.00 C180000.00 D180000.00 'G180000.00     ; set accelerations (mm/s^2)
M906 Z1360.0 U1360.0 V1360.0 W560.0 A560.0 B560.0  C560.0 D560.0 'G560.0  I100        ; set motor currents (mA) and motor idle factor in per cent

As concerns Jerk , Duet measurement are in mm/min but openPnP are in mm/s^3

in order to convert that into mm/s^3 for OpenPnP do i just need to take Duet's config value and multiply by (60 * 1/S^3 )

i.e 900 mm/min = 900 x 60 mm/s =54000 mm/s x (1/s^2) = 54000 mm/s^3

is this correct assumption ? or Both Duet & OpenPnP must have be synchronized by having same Value ?

From this config is there anything you think might be a little out of place i.e Too high or too low