troubleshooting Duet2 WiFi Z driver
-
@Phaedrux
purchased through filastruder april 16th -
@Phaedrux
no, but its also not set built completely yet, this was just a bare motor not connected to anything. they are the super whopper motors they work on other outputs using the "M584 X0 Y1 Z3:4:5:6" and running "g1 s2 z100 f3000" -
Please try 400 for the steps per mm with the motor connected to the Z driver just to eliminate any issues arising from using such a high steps per mm (like stalling).
-
is there a way to verify that it took my config.g file with the changed steps? new config.g file. ran code
g91
g1 s2 z100 f3000no movement
new code uploaded through dwc.
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"printer who shall be named" ; set printer nameM667 S1 ; select CoreXY mode
; Network
M551 P ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; 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 Z12.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 -
You can send most gcodes without any parameters in the console and it will report back with the currently used values.
Can you also send M122 and post the result?
-
@Phaedrux
8:25:00 PMM122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N8PS0-7JKDG-3S46S-TV93N
Used output buffers: 3 of 24 (16 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 94168 of which 396 recycled
Exception stack ram used: 332
Never used ram: 10496
Tasks: NETWORK(ready,660) HEAT(blocked,1236) DUEX(suspended,156) MAIN(running,3756) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:10:52 ago, cause: software
Last software reset at 2020-05-19 20:14, reason: User, spinning module GCodes, available RAM 10516 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 8
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 43.1, current 43.7, max 43.8
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2020-05-19 20:24:59
Cache data hit count 2545255665
Slowest loop: 2.94ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 1, completed moves: 1, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 201.13ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi MAC address bc:dd:c2:31:a3:a5
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22824
WiFi IP address 10.0.0.10
WiFi signal strength -76dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
Do you have 4 motors connected, or just the one?
I'm thinking your Z driver may not be working unfortunately.
You say the motors work on 3:4:5:6 but not 2?
And you've tried another motor on 2?
-
@Phaedrux
I have 4 z motors they work on drives 3:4:5:6 when I run the command m584 x0 y1 z3:4:5:6. no matter what I do even with jumpers and running the command m584 x0 y1 z2 I get nothing. just the driver chip gets hot but no movement. -
Understood. Please hang on while we see if DC42 has any other ideas.
-
I agree, I think the Z driver has failed, and I approve a warranty replacement.
-
@dc42 thank you guys for your help!