@Danal I got it! my white wire had a bad crimp.

How do you enable stealthchop 2? I have RRF 3.1 on a duet 2 wifi. I would like to reduce the noise by using stealth chop. I tried the following and it did not work: M569 P0:1:2:3:4 D3

Thanks!

Jordan

@oliof Thanks for that tip. I will give that a shot. I just want the screen to function. It will never be my main interface

Hi all. I hope you are well.

The reason I am writing is to find out if there is a way to use a TFT3.5 inch, which is the stock size screen for my Two Trees Sapphire Plus. I am wondering if this is possible, and if so, what manufacturer should I use?

Thanks!

@macguyver yes, I do

@Phaedrux I will share shortly.

@oliof I am getting the full on car crash sound movement...

Howdy all,

I hope y'all are doing better than my beloved Texas is fairing in this pandemic.

I am writing because I have just setup my Duet 2 Wifi to run latest version of RRF3 on my Two Trees Sapphire CoreXY. I am having some interesting issues with the homing.

First off, I want to use sensorless, because I like to use stall detection. The trouble I am having is that, I have never set up a CoreXY before, and I really cannot find much documentation regarding the Duet's sensorless homing and CoreXY.

I understand that the longer belts means that it is more difficult for the drivers to interpret stalls, but surely, sensorless homing can at least work.

I have the same home.g (includes all, x, y, and z) files that I have on my CR-10, which works flawlessly. I have my stalld-homing.g macro setup to reduce motor current and everything. (Inlcuding stalld-printing.g at the end of home files).

Do I need to have my print carriage move significantly quicker than on a cartesian machine? No homing file has any move with a F parameter lower than 3600.

Thanks,

Jordan.

@Kolbi Your github is great!

@Kolbi Awesome! I will certainly check it out

@Kolbi you guys are rock stars. Thank you so much. I will make sure that this info is out there for everyone else.