having problems with Duet 3
-
I have an ender 5 plus and i put the duet 3 in it and I have been at a dead end for about a month trying to figure out what I am doing wrong here are a couple of my config files please any help would be greatly appreciated.
I can get x an y to home
I cant get z to home one moter goes down and the other one goes up
I can not get the bl touch probe to deploy eitherM122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6JKD8-3S46J-9V2UD
Used output buffers: 1 of 40 (23 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 62764 of which 64 recycled
Never used RAM 146216, free system stack 140 words
Tasks: Linux(ready,113) HEAT(blocked,297) CanReceiv(blocked,927) CanSender(blocked,352) CanClock(blocked,354) TMC(blocked,19) MAIN(running,1185) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:42 ago, cause: software
Last software reset at 2021-04-19 22:11, reason: User, Platform spinning, available RAM 146204, slot 2
Software reset code 0x0000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 48.7, current 49.2, max 49.3
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Driver 0: position 0, standstill, reads 44273, writes 20 timeouts 0, SG min/max 0/130
Driver 1: position 0, standstill, reads 44276, writes 17 timeouts 0, SG min/max 0/253
Driver 2: position 0, standstill, reads 44276, writes 17 timeouts 0, SG min/max 0/94
Driver 3: position 0, standstill, reads 44280, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 44277, writes 17 timeouts 0, SG min/max 0/80
Driver 5: position 0, standstill, reads 44283, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-04-19 22:12:34
Slowest loop: 63.82ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 9945ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10, completed moves 10, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 156, send timeouts 367, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 1439/1439
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.62
Maximum length of RX/TX data transfers: 4784/840; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Apr 19 2021 22:10:15 GMT-0700 (Pacific Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 3" ; set printer name; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2:0:4 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X350 Y350 Z400 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io1.in
M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z2 S2 ; configure Z-probe endstop for high end on Z; Z-Probe
M950 S0 C"io5.out" ; create servo pin 0 for BLTouch
M558 P9 C"^!io5.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X3 Y3 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:320 Y15:320 S20 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H T25 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 S1 H1 T25 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out9" Q500 ; create fan 2 on pin out9 and set its frequency
M106 P2 S1 H1 T25 ; set fan 2 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
T0 ; select first tool; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Apr 19 2021 22:10:15 GMT-0700 (Pacific Daylight Time)
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Apr 19 2021 22:10:15 GMT-0700 (Pacific Daylight Time)
M280 P0 S10 ; deploy BLTouch; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Apr 19 2021 22:10:15 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-355 Y-355 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-355 Y-355 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X12 Y12 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@thechainring said in having problems with Duet 3:
I cant get z to home one moter goes down and the other one goes up
...
; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2:0:4 E0.3 ; set drive mappingYou need to reverse the direction of rotation of the Z motor that is going the wrong way. Your M584 command indicates that your Z motors are on drivers 0.2 and 0.4. To change the direction of the motor on driver 0.2, change S1 to S0 in your M569 P0.2 S1 command. Or, if it's the motor connected to driver 0.4 that is going the wrong way, change S1 to S0 in the M569 P0.4 command.
I can not get the bl touch probe to deploy either
The only thing wrong that I spotted with the BLTouch configuration is this line:
M558 P9 C"^!io5.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
It should be:
M558 P9 C"io5.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
However, that will not affect deployment. Are you testing deployment and retraction using M401 and M402? Please post photos showing how you have connected the BLTouch to the Duet. Does the BLTouch do its self-test when you power up the Duet?
-
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.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
-
@thechainring do you have your deployprobe.g and retractprobe.g configured?
M280 P0 S10goes into deployprobe.g
M280 P0 S90goes 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.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
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?
![20210420_085420[2].jpg](/assets/uploads/files/1618934229867-20210420_085420-2-resized.jpg)
![20210420_085331[1].jpg](/assets/uploads/files/1618934247026-20210420_085331-1-resized.jpg)
![20210420_085322[1].jpg](/assets/uploads/files/1618934262672-20210420_085322-1-resized.jpg)
