<p>I am writing an M-code for a new algorithm to reduce vibrations during printing. After a bit of preprocessing, my algorithm spits out the number of steps for each drive. Is there any way I can provide these steps directly to the drives to be executed?</p>
<p>E.g. instead of providing <code>G0 X5</code>I would like to send <code>Some_G_code X400</code> which basically says the x drive should move 400 steps which would result in the same move as <code>G0 X5</code>, assuming 80 steps/mm.</p>

CC BY-SA 4.0
2021-10-13T21:18:59.443Z
Have you tried setting steps per mm to 1?
Mick
CC BY-SA 4.0
2021-10-13T21:28:45.773Z
How is this going to work when you need to be coordinating motions of multiple motors in sync?
R.. GitHub STOP HELPING ICE
CC BY-SA 4.0
2021-10-13T21:36:34.420Z
@Mick I can't do that since I do not want my input (400 in the eg) to go through any segmentation preprocessing etc. I would just like to give it as a command to the stepper drivers.
HDEV5
CC BY-SA 4.0
2021-10-13T21:38:17.170Z
@R..GitHubSTOPHELPINGICE they will be provided to the stepper driver in the same order as to maintain the step time order
HDEV5
CC BY-SA 4.0
2021-10-13T21:43:22.547Z
@HDEV5: Just knowing order lacks sufficient information to control the relative timing. You should probably look at how Klipper does this.
R.. GitHub STOP HELPING ICE
CC BY-SA 4.0
2021-10-13T21:44:40.013Z
@R..GitHubSTOPHELPINGICE Could you provide me a link for reading?
HDEV5
<reprap-firmware>
Manually provide the number of steps to be executed by a drive (RepRap firmware 3.3)
HDEV5
# Manually provide the number of steps to be executed by a drive (RepRap firmware 3.3)

(Asked by: username_0 on 2021-10-13)

I am writing an M-code for a new algorithm to reduce vibrations during printing. After a bit of preprocessing, my algorithm spits out the number of steps for each drive. Is there any way I can provide these steps directly to the drives to be executed?

E.g. instead of providing `G0 X5`I would like to send `Some_G_code X400` which basically says the x drive should move 400 steps which would result in the same move as `G0 X5`, assuming 80 steps/mm.

**Tags:** reprap-firmware
> **Comments:**
> **username_1**: Have you tried setting steps per mm to 1?  
> **username_2**: How is this going to work when you need to be coordinating motions of multiple motors in sync?  
> **username_0**: @Mick I can't do that since I do not want my input (400 in the eg) to go through any segmentation preprocessing etc. I would just like to give it as a command to the stepper drivers.  
> **username_0**: @R..GitHubSTOPHELPINGICE they will be provided to the stepper driver in the same order as to maintain the step time order  
> **username_2**: @HDEV5: Just knowing order lacks sufficient information to control the relative timing. You should probably look at how Klipper does this.  
> **username_0**: @R..GitHubSTOPHELPINGICE Could you provide me a link for reading?  

---

## 0 answers

