having problems with Duet 3
-
okay I have all the axis going the correct direction now
firing for the bl touch i have
white-------------------------------In
black and brown -------------- ground
orange --------------------------- out
red---------------------------------- 5vI changed the m558 line, all the Bltouch does is blink red .
so now how do i get gantry to go to the middle of the bed after i press home.
I plan on buying the duet sensor after i get the printer up and running again so i thought i could do sensorless homing for z if i couldnt get the bl touch working.
-
@thechainring said in having problems with Duet 3:
okay I have all the axis going the correct direction now
firing for the bl touch i have
white-------------------------------In
black and brown -------------- ground
orange --------------------------- out
red---------------------------------- 5vI changed the m558 line, all the Bltouch does is blink red .
Please post a photo so that we can check the BLTouch wiring.
so now how do i get gantry to go to the middle of the bed after i press home.
You have this in your homeall.g file:
G1 X12 Y12 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bedThe G1 X12 Y12 line causes the head to move to X12 Y12 before probing for Z. To make it move to the centre of the bed instead, change it to G1 X175 Y175 instead.
-
-
@thechainring do you have your deployprobe.g and retractprobe.g configured?
M280 P0 S10
goes into deployprobe.g
M280 P0 S90
goes into retractprobe.gThe wiring should be
IO5.in > Z-
IO5.in > S
GND > GND
5V > 5V -
@dhusolo The servo pin needs to be on an OUT pin.
This what I have on my 1LC:
M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch
M558 P9 C"^121.io0.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X20 Y0 Z0 ; set Z probe trigger value, offset and trigger height -
i also need some thing like this in config.g and bed.g
M584 X0.0 Y0.1 Z0.2:0.4 E0.3; two Z motors connected to driver outputs Z and E1
M671 X-20:220 Y0:0 S0.5 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis
M208 X-5:205 Y0:200 ; X carriage moves from -5 to 205, Y bed goes from 0 to 200G28 ; home
M401 ; deploy Z probe (omit if using bltouch)
G30 P0 X20 Y100 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X180 Y100 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
M402 ; retract probe (omit if using bltouch)but wasnt sure if i was supposed to remove lines m401 and m402 and what cordinates i was supposed to use for the cordinates for x and y
-
So I put 2 wire in to my in I05.in ?
@dhusolo said in having problems with Duet 3:
The wiring should be
IO5.in > Z-
IO5.in > S
GND > GND
5V > 5V -
which wire is the servo pin
-
@thechainring Yellow/orange
-
@thechainring said in having problems with Duet 3:
So I put 2 wire in to my in I05.in ?
@dhusolo said in having problems with Duet 3:
The wiring should be
IO5.in > Z-
IO5.in > S
GND > GND
5V > 5VNo, the servo wire should be connected to IO5.out.
-
that is the way i have it wired i found out what my problem was all my fans where 24v i had 4 of the i disconnected 2 and the bl touch started to work i did a test print everything printed very slowly and i assumed it was because of the 2 remaing fans so i unplugged one and my panel due but i also used the slicer from pronterface instead of cura and it printed at normal speeds.
so my next question is do I buy 5v fans instead or 12v fans and should I buy a better power supply then the Stock Meanwell Rsp-500-24?
-
@thechainring said in having problems with Duet 3:
instead of cura
It's very likely that there is some speed settings in the Cura start gcode that is overriding your settings in config.g. Delete the cura start gcode settings and you'll be back to normal.
-
@dc42 yes that was a typo. it's IO5.out thanks
-
I just ordered the toolboard, ir sensor and spider magnum reading through the forums i have came to the understanding that there are some problems with ambient temp readout is there i different sensor i should order to avoid this problem?