initial setup, no motor movement or endstop triggering.
-
@deltajegga said in initial setup, no motor movement or endstop triggering.:
@dc42 thats how i have them. even if i short the 3.3 and stp pins at the board, nothing happens.
Wrong pins. You need to short the STP and ground pins (the outer 2 pins of the 3).
-
interesting, im confused. did i miss that somewhere on the endstop page?
-
ok, i switched the wires to the outer pins and that got the leds working properly. but i still get a homing failed error.
-
Are the motors moving now?
Did you change the M574 line to S1 (Active high) now? -
just so i have this straight i saw this on some page but i cant remember which one.
S0 is no switch
S1 is NO
S2 is NC right?
i switched it to S1 and still get home error. -
Nope, from the wiki:
https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_Set_endstop_configuration
Snnn Endstop type: 0 = active low endstop input, 1 = active high endstop input, 2 = Z probe, 3 = motor load detection
-
oh ok, thanks. so ive got the xyz endstops working, but the bltouch is displayed on the machine properties page as E0 yes. would this stop the motors from moving?
-
@deltajegga said in initial setup, no motor movement or endstop triggering.:
oh ok, thanks. so ive got the xyz endstops working, but the bltouch is displayed on the machine properties page as E0 yes. would this stop the motors from moving?
BLTouch should not be connected to E0, it should be connected to the Z probe connector. if correctly wired and configured, it should give you a Z probe reading of 0 when not active.
Common things that prevent motors moving:
- Not setting the currents. Send M906 to check that they are set.
- Not having VIN power applied.
- Having VIN power applied, but the voltage is too low. The M122 diagnostic report includes a "power good" indication.
- Trying to do regular moves before the printer has been homed. You will get error messages in the GCode Console if that is the reason. If you want to allow regular movement before homing, you can send M564 H0 or include that in config.g.
-
ok, so ive updated to 2.02 and have got everything working, i think my main problem was in you're wiki you link to betrue3d site and his information is not up to date, so i was going back and forth and mixed a bit from the old way with the new way. but after just following you're guide i got everything working and have got it to run a mesh compensation.
-
@deltajegga Which link in which wiki? That should be fixed.
-
https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/
the define probe type section got me the first time. it says to use P5 for probe type. -
@deltajegga P5 will still work, and is required for older firmware versions. But P9 is preferred.
