<p>As @towe mentioned, 'no-driver-detected' messages in Octoprint log are harmless if you have TMC2100 motors. After experimenting with RepRap settings I found the correct configuration that works with my hardware. Here is the relevant part of the configuration.</p>
<pre><code>; Drives
M569 P0 S1                                     ; physical drive 0 goes forwards
M569 P1 S1                                     ; physical drive 1 goes forwards
M569 P2 S1                                     ; physical drive 2 goes forwards
M569 P3 S0                                     ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3                               ; set drive mapping
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z100.00 E100.00            ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E300.00        ; set maximum instantaneous speed changes (mm/min)
M203 X48000.00 Y48000.00 Z48000.00 E1500.00    ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z1500.00 E1000.00       ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout
</code></pre>

CC BY-SA 4.0
2021-03-21T16:04:57.460Z
2021-03-21T16:04:57.460Z
Ivan Gankevich
<p>I've upgraded my board to SKR1.4 turbo with RepRap firmware. Heated bed and heated nozzle work, but motors do not move.
OctoPrint reports them as 'no-driver-detected'.</p>
<pre><code>Send: M122
...
Recv: Driver 0: position 67347, no-driver-detected
Recv: Driver 1: position 67347, no-driver-detected
Recv: Driver 2: position 67347, no-driver-detected
Recv: Driver 3: position 0, no-driver-detected
...
</code></pre>
<p>I tried to figure out what is wrong, but did not find good documentation for this combination of hardware.</p>
<p>This is how I setup the drivers.</p>
<ol>
<li>I removed all <em>four</em> jumpers from the board below each driver (MS0, MS1, MS2, RST).</li>
<li>Plugged each driver to the board making sure that the corresponding pins match (GND to GND etc.)</li>
<li>Checked voltage between ground pin of the board and VREF pin of the driver. The voltage was 1.365 V (same for each driver). This is a bit higher than some guides suggest, but the drivers worked perfectly with the old board.</li>
</ol>
<p>Some guides suggest modifying driver timings if the motors do not move, but I was unable to find the right timings for my drivers. What could be wrong in my setup?</p>

CC BY-SA 4.0
2021-03-17T12:53:40.227Z
TMC2100s do not feature UART or SPI communication, so you won't get any results from M122. You'll want to set microstepping with the jumpers. VREF sounds reasonable.
towe
CC BY-SA 4.0
2021-03-18T13:38:34.403Z
@towe Thank you for explaining this strange message! Googling it gives nothing. I realised, that I relied on this message when trying different RepRap configurations. When I have time, I will try them once more with some basic movement commands instead.
Ivan Gankevich
<reprap><skr-v1.4><tmc2100>
TMC2100 stepper motor drivers not detected on SKR 1.4 turbo with RepRap firmware
Ivan Gankevich
# TMC2100 stepper motor drivers not detected on SKR 1.4 turbo with RepRap firmware

(Asked by: username_0 on 2021-03-16)

I've upgraded my board to SKR1.4 turbo with RepRap firmware. Heated bed and heated nozzle work, but motors do not move.
OctoPrint reports them as 'no-driver-detected'.
Send: M122
...
Recv: Driver 0: position 67347, no-driver-detected
Recv: Driver 1: position 67347, no-driver-detected
Recv: Driver 2: position 67347, no-driver-detected
Recv: Driver 3: position 0, no-driver-detected
...

I tried to figure out what is wrong, but did not find good documentation for this combination of hardware.
This is how I setup the drivers.

I removed all four jumpers from the board below each driver (MS0, MS1, MS2, RST).
Plugged each driver to the board making sure that the corresponding pins match (GND to GND etc.)
Checked voltage between ground pin of the board and VREF pin of the driver. The voltage was 1.365 V (same for each driver). This is a bit higher than some guides suggest, but the drivers worked perfectly with the old board.

Some guides suggest modifying driver timings if the motors do not move, but I was unable to find the right timings for my drivers. What could be wrong in my setup?

**Tags:** reprap, skr-v1.4, tmc2100
> **Comments:**
> **username_1**: TMC2100s do not feature UART or SPI communication, so you won't get any results from M122. You'll want to set microstepping with the jumpers. VREF sounds reasonable.  
> **username_0**: @towe Thank you for explaining this strange message! Googling it gives nothing. I realised, that I relied on this message when trying different RepRap configurations. When I have time, I will try them once more with some basic movement commands instead.  

---

## 1 answers

### Answer by username_0 on 2021-03-21. Score: 1

As @towe mentioned, 'no-driver-detected' messages in Octoprint log are harmless if you have TMC2100 motors. After experimenting with RepRap settings I found the correct configuration that works with my hardware. Here is the relevant part of the configuration.
; Drives
M569 P0 S1                                     ; physical drive 0 goes forwards
M569 P1 S1                                     ; physical drive 1 goes forwards
M569 P2 S1                                     ; physical drive 2 goes forwards
M569 P3 S0                                     ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3                               ; set drive mapping
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z100.00 E100.00            ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E300.00        ; set maximum instantaneous speed changes (mm/min)
M203 X48000.00 Y48000.00 Z48000.00 E1500.00    ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z1500.00 E1000.00       ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout


---

