Problem duet3 mini5+ - Z axis don't move
-
hi
i install my new duet 3 mini
I have a problem with my Z engine
they don't want to work
I have an error Error: short-to-ground reported by driver (s) 0 1
attached my config.g
when I check my running motor (M906) I have
M906
Motor current (mA) - X: 1800, Y: 1800, Z: 0, E: 800: 800, idle factor 40% (however the motor current is correctly configured in my config.g
I use the M906 Z1800 command to reconfigure the motor current
after I
m906
Motor current (mA) - X: 1800, Y: 1800, Z: 1800, E: 800: 800, idle factor 40%
and the Z does not move yet (even with the M564 h0 command)
I checked my motors that work and exchange the outputs between X / Y and Z1 / Z2 on the duet
the Z does not always want to chew unlike the X and Y which works; Configuration file for Duet 3 Mini 5+ (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 15 2021 14:53:03 GMT+0200 (heure d’été d’Europe centrale) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M669 K1 ; select CoreXY mode ; Drives M569 P0.0 S0 ; physical drive 0.0 goes forwards X M569 P0.1 S0 ; physical drive 0.1 goes forwards Y M569 P0.2 S0 ; physical drive 0.2 goes forwards Z1 M569 P0.3 S0 ; physical drive 0.3 goes forwards Z2 M569 P0.4 S1 ; physical drive 0.4 goes forwards E0 ;M569 P121.0 S1 ; physical drive 121.0 goes forwards E1 toolboard M584 X0.0 Y0.1 Z0.2:0.3 E0.4:121.0 ; set drive mapping M350 X16 Y16 Z16:16 E16:16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z800.00:800.00 E420.00:420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00:60.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00:180.00 E1200.00:1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00:20.00 E250.00:250.00 ; set accelerations (mm/s^2) M906 X1800 Y1800 Z2000:2000 E800:800 I40 ; 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 X300 Y300 Z300 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io0.in" ; configure active-high endstop for low end on X via pin io0.in M574 Y1 S1 P"io1.in" ; configure active-high endstop for low end on Y via pin io1.in M574 Z1 S2 ; configure active-high endstop for low end on Y via pin io1.in M574 Z1 S1 P"io2.in" ; Z-Probe M558 P8 C"^io5.in"H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 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 B1 S1.00 ; enable 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"spi.cs2" Y"rtd-max31865" ; configure sensor 1 as thermocouple via CS pin spi.cs1 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 M308 S2 P"121.temp0" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin 121.temp0 M950 H2 C"121.out0" T2 ; create nozzle heater output on 121.out0 and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H2 S280 ; set temperature limit for heater 2 to 280C ; Fans M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency M106 P1 S1 H2 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D1 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 M563 P1 D2 H2 F0 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power lossM122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: T7YM3-4296U-D65J0-40KMD-3Z03Z-Z3S2N Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 98732 Dynamic ram: 95468 of which 48 recycled Never used RAM 50968, free system stack 200 words Tasks: Linux(ready,79) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,106) MAIN(running,519) IDLE(ready,20) AIN(blocked,269) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:08:36 ago, cause: software Last software reset at 2021-05-17 15:07, reason: User, none spinning, available RAM 50484, slot 1 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 Supply voltage: min 0.0, current 23.8, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 72, reads 8095, writes 11, timeouts 71, DMA errors 0, failedOp 0x71 Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 72, reads 8154, writes 11, timeouts 12, DMA errors 0, failedOp 0x06 Driver 2: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 72, reads 8166, writes 11, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 72, reads 8164, writes 11, timeouts 1, DMA errors 0, failedOp 0x6a Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 59, reads 8166, writes 11, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-05-17 15:16:04 Cache data hit count 1242889852 Slowest loop: 1.27ms; fastest: 0.08ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, 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, chamberHeaters = -1 -1 === 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 4622, send timeouts 4619, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16 === SBC interface === State: 4, failed transfers: 0 Last transfer: 3ms ago RX/TX seq numbers: 18375/18375 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x10eec 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.72 Maximum length of RX/TX data transfers: 2896/860can the board be dead?
can i test something to confirm it?
thanks -
@bast said in Problem duet3 mini5+ - Z axis don't move:
M584 X0.0 Y0.1 Z0.2:0.3 E0.4:121.0 ; set drive mapping
Did you remap drivers?
M584 X0.0 Y0.1 Z0.2:0.3 E0.4:121.0 ; set drive mapping
-
@tecno yes
i try to remap driver like
M584 X0.2 Y0.3 Z0.0:0.3 E0.1:121.0stepper XY working on 0.2/0.3 but not Z1/Z2 on 0.1/0.0
-
Check all wires to Z motors
-
@tecno
wiring is good
i test it with news motor ,same problem
test
plug new motor
when i start it washe is not engaged
I perform an M564 H0 (move without homing)
when I move 50mm the motor engages but does not move
I check the motor current
m906
Motor current (mA) - X: 1800, Y: 1800, Z: 0, E: 800: 800, idle factor 40%
there is none on Z
j execute the command
M906 Z1800
and the error
05/17/2021, 16:59:47 Error: short-to-ground reported by driver (s) 0 1
and moreover he is no longer engaged
I do not understand why the current is not configured via the config.g and that as soon as I give it an instruction it goes into error ... -
As i can see you use 2 Z-Axis motors and RR FW 3.2.2
I had strange behavior when i declared two values for M92, M201, M203, M566 and M906 until i switched to single value.
So for experiment - try to use only one value for Z in these.example:
M92 X80.00 Y80.00 Z800.00 E420.00:420.00 -
M350 X16 Y16 Z16:16 E16:16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z800.00:800.00 E420.00:420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00:60.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00:180.00 E1200.00:1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00:20.00 E250.00:250.00 ; set accelerations (mm/s^2) M906 X1800 Y1800 Z2000:2000 E800:800 I40 ; set motor currents (mA) and motor idle factor in per centYou must only define the Z values once for the single axis rather than for each drive. It's only for the exruder axis that they must each be defined. Remove the second values for Z.
-
