Nooo....not again...!!!!!!!!
-
Hi,
after mount my new corexy and wiring (Duet 3 mini + expansion x2, i have star do initial probes....
With the results, one of 3 motors of Z axis not work.... i sended M122, with these results
V-Core 3 25/1/2022 11:23:12 m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: YHY31-G096U-D65J0-40KMU-3F03Z-R26JL Used output buffers: 3 of 40 (11 max) === RTOS === Static ram: 102724 Dynamic ram: 106088 of which 0 recycled Never used RAM 34892, free system stack 204 words Tasks: NETWORK(ready,11.8%,216) HEAT(notifyWait,0.0%,366) Move(notifyWait,0.1%,338) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.8%,116) MAIN(running,85.0%,412) IDLE(ready,1.4%,29) AIN(delaying,0.8%,273), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:17 ago, cause: power up Last software reset at 2022-01-25 11:21, reason: User, GCodes spinning, available RAM 34892, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,1 MCU revision 3, ADC conversions started 17785, completed 17785, timed out 0, errs 0 Step timer max interval 751 MCU temperature: min 18.8, current 21.8, max 21.8 Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, assumed not present Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 1152, writes 10, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 1152, writes 9, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 1152, writes 9, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 1152, writes 10, timeouts 0, DMA errors 0 Driver 5: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 1151, writes 10, timeouts 0, DMA errors 0 Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 1152, writes 9, timeouts 0, DMA errors 0 Date/time: 2022-01-25 11:23:11 Cache data hit count 34568681 Slowest loop: 10.40ms; fastest: 0.12ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.3ms, 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 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 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 USB is idle in state(s) 0 Aux is assembling a command 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 158, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 89/0/0 Tx timeouts 0,0,88,0,0,68 last cancelled message type 4514 dest 127 === Network === Slowest loop: 18.25ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address f0:08:d1:03:80:36 WiFi Vcc 3.40, reset reason Power up WiFi flash size 2097152, free heap 23680 WiFi IP address 192.168.1.20 WiFi signal strength -30dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0if you see the log, say the Driver in position 0 its not present, when was connected the Z motor that not turns. Photo to board:
What options i have? i can do some more tests? Or as it seems, is damage definitive?
I am not having luck with Duet boards... these 0 meters of filament extruded... first time i power on, the third Duet... The truth is that I don't know if it came like that... or if it was damaged during assembly, and if it was damaged during assembly... how?
-
@peirof can you post your config?
-
@jay_s_uk sure
Drivers in 0.1, 0.2, and 0.3 controls Z
; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"V-Core 3" ; set printer name M669 K1 ; CoreXY G29 S1 ; Set Units to Millimeters ; Network M587 S"PT_2" P"a1b2c3d4" M552 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ;Panel Due M575 P1 B57600 ; Drives M569 P0.0 S0 D3 ; physical drive 0.0 goes forwards M569 P0.1 S0 D3 ; physical drive 0.1 goes forwards M569 P0.2 S0 D3 ; physical drive 0.2 goes forwards M569 P0.3 S1 D3 ; physical drive 0.3 goes forwards M569 P0.4 S1 D3 ; physical drive 0.4 goes forwards M569 P0.5 S1 D3 ; physical drive 0.5 goes forwards M584 X0.4 Y0.3 Z0.6:0.1:0.2 E0.5 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z800.00 ; set steps per mm M906 X1000 Y1000 Z800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout M566 X400.00 Y400.00 Z6.00 E120.00 P1 ; set maximum instantaneous speed changes (mm/min) M203 X10800.00 Y10800.00 Z1000.00 E3600.00 ; set maximum speeds (mm/min) M201 X3000.00 Y3000.00 Z100.00 E3600.00 ; set accelerations (mm/s^2) ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X410 Y400 Z400 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io0.in" ; configure active high endstops M574 Y2 S1 P"io1.in" ; configure active high endstops M574 Z1 S2 ; configure Z-probe endstop for low end on Z M671 X-4.5:200:304.5 Y-4.52:405:-4.52 S5 ; define positions of Z leadscrews or bed levelling screws M557 X20:380 Y20:380 P5 ; define 5x5 mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0 M307 H1 B0 R3.161 C199.4 D11.35 S1.00 V24.0 M950 H0 C"out0" T0 ; create bed heater output on out5 and map it to sensor 0 M307 H0 B0 R0.776 C301.3 D5.65 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S110 ; set temperature limit for heater 0 to 110C ;; Run Bed PID Tune!! Bellow is an example for a 300x300 bed ;; M307 H0 A303.1 C356.7 D1.4 S1.00 V24.0 B0 ; Fans M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency M106 P0 C"Ventilador Hotend" S0 H1 T45 L255 ; set fan 0 name and value. Thermostatic control turned on for Hotend M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency M106 P1 C"Ventilador Capa" S0 H-1 L255 ; set fan 1 name and value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F1 ; 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 M950 H1 C"out1" T1 ; create nozzle heater output on out2 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S250 ; set the maximum temperature in C for heater ; EVA 2 / BMG / E3D V6 M92 E830 ; set extruder steps per mm, 0.9 angle/step (LDO Pancake) M906 E800 ; set extruder motor current (mA) and idle factor in per cent M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 A"Hotend" ;; Run Heater PID Tune!! ;; M307 H1 A751.5 C196.6 D4.7 S1.00 V23.9 B0 ; BLTouch M950 S0 C"io2.out" ; Create a servo pin on io7 M558 P9 C"io2.in" H5 F240 T10800 A5 ; set Z probe type to unmodulated and the dive height + speeds G31 P25 X-28.00 Y-13.00 Z0.90 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed T0 ; Pressure Advance M572 D0 S0.10 -
@peirof theres probably some default mapping somewhere that maps driver 0 to something else.
Try addingU0.0to your M584 and see if the problem goes away -
@peirof said in Nooo....not again...!!!!!!!!:
M584 X0.4 Y0.3 Z0.6:0.1:0.2 E0.5
According to that, you have drivers 6,1 and 2 of the main board controlling Z. Drivers 0 isn't connected to anything.
-
@peirof said in Nooo....not again...!!!!!!!!:
Drivers in 0.1, 0.2, and 0.3 controls Z
Looking at your config.g, that's definitely not true. There, you map Z with
M584to 0.6, 0.1 and 0.2. In the "Drives" section above,M569 P0.6 S0 D3is missing, i.e. drive 0.6 is not defined.And, as a side note: try to keep your gcodes in sync with the comments. "physical drive 0.3 goes forwards" is just the opposite of what the gcode does. Same is true for drives 0.4 and 0.5. With "S1" they go backwards.
-
@infiniteloop no.... These is edited config.g,for following use duet, but by default its connected to 0.1,for check it is stepper problem I have connected to 0.6
-
@peirof Don't confuse me (and don't be confused yourself): the first Z-stepper was originally connected to 0.0 (not 0.1 - that's the second of three steppers for Z). As you ran into problems with port 0.0, you switched to 0.6. Now, you still have to add the
M569gcode to match your actual assignment. -
forgive the error, I have corrected the error, Driver 0.0 DOES work.
What was the error, that I have started to assign the engines with M569 in 0.1, and it was 0.0
the repaired config.g (extract):
; Drives M569 P0.0 S0 D3 ; physical drive 0.0 goes forwards spare test M569 P0.1 S0 D3 ; physical drive 0.1 goes forwards M569 P0.2 S0 D3 ; physical drive 0.2 goes forwards M569 P0.3 S1 D3 ; physical drive 0.3 goes forwards M569 P0.4 S1 D3 ; physical drive 0.4 goes forwards M569 P0.5 S1 D3 ; physical drive 0.5 goes forwards M584 X0.4 Y0.3 Z0.0:0.1:0.2 E0.5 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolationthx, and sorry
-
@peirof No reason to be sorry. The main thing is to not getting confused - that are just gcodes
-
Does that photo show chunks missing from the driver chip and a missing resistor?
