@T3P3Tony I will as soon as I get home and post the report. Thank you

Posts made by anthonym
-
RE: Duet mini 5 lulzbot won’t drive extruder
-
RE: Duet mini 5 lulzbot won’t drive extruder
so the issue I am having now it’s extruding way too much if I ask for 10mm I get over 100 my steps per mm are 420 on the aero 2.85 mm with a .5 nozzle.
-
RE: Duet mini 5 lulzbot won’t drive extruder
@droftarts Its seem to be working , I see that now thank you for explaining I really appreciate the help.
-
RE: Duet mini 5 lulzbot won’t drive extruder
@Phaedrux Yes that seems to have fixed it !!
-
RE: Duet mini 5 lulzbot won’t drive extruder
@anthonym Error: in file macro line 26: M92: array too long, max length = 1
-
RE: Duet mini 5 lulzbot won’t drive extruder
@Phaedrux said in Duet mini 5 lulzbot won’t drive extruder:
M98 P"config.g"
Error: in file macro line 27: M566: array too long, max length = 1
-
RE: Duet mini 5 lulzbot won’t drive extruder
@droftarts still does the same thing. I have another stepper I also tried and same thing. if I move over to the x driver it works. Same basically it wont drive e.
-
RE: Duet mini 5 lulzbot won’t drive extruder
@droftarts M350 X16 Y16 Z16 E16: I1 ; configure microstepping with interpolation
M92 X80 Y80 Z80 E420:80 ; set steps per mm
M566 X900 Y900 Z150 E420:150 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z300.00 E120.00: ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z300.00 E250.00: ; set accelerations (mm/s^2)
M906 X1300 Y1300 Z1300 E150: I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout -
RE: Duet mini 5 lulzbot won’t drive extruder
@Phaedrux the motor will turn outside but has no torque can stop it by hand.
-
RE: Duet mini 5 lulzbot won’t drive extruder
@Phaedrux correct and I can hook the motor to another driver and it works fine , Just whatever driver is E wont work I can switch e to driver 1 and wont work , I can run z2 on driver 4 no problem.
-
RE: Duet mini 5 lulzbot won’t drive extruder
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.5 (2022-11-30 19:41:16) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: 98BFS-8396U-D65J0-40KMA-3K03Z-RBNJ0 Used output buffers: 1 of 40 (19 max) === RTOS === Static ram: 103652 Dynamic ram: 98320 of which 12 recycled Never used RAM 39656, free system stack 146 words Tasks: SBC(ready,1.2%,478) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,290) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,341) TMC(notifyWait,0.7%,82) MAIN(running,97.2%,502) IDLE(ready,0.0%,30) AIN(delaying,0.8%,272), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:21:41 ago, cause: power up Last software reset at 2023-03-23 19:14, reason: User, GCodes spinning, available RAM 39656, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 1301325, completed 1301323, timed out 0, errs 0 Step timer max interval 1490 MCU temperature: min 19.1, current 32.8, max 32.9 Supply voltage: min 24.0, current 24.1, 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 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 2921, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 2921, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 2921, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 2920, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 2926, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-03-26 02:39:27 Cache data hit count 2919028547 Slowest loop: 61.18ms; fastest: 0.07ms === 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, segments created 3, maxWait 1081036ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 7, completed 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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 11616, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 6506/0/0 Tx timeouts 0,0,6505,0,0,5109 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 50349/50349 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0f1bc Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.5 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 0.32, max time between full transfers: 59.1ms, max pin wait times: 36.6ms/12.4ms Codes per second: 0.00 Maximum length of RX/TX data transfers: 3276/572 3/25/2023, 7:35:42 PM Connected to 192.168.0.113
-
RE: Duet mini 5 lulzbot won’t drive extruder
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.16 on Wed Mar 22 2023 18:56:16 GMT-0600 (Mountain Daylight Time) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; 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.4 S1 ; physical drive 0.4 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z2:3 E0.4 ; set drive mapping M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z80.00 E80:80.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00:60.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z200.00 E1200.00:200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z100.00 E250.00:100.00 ; set accelerations (mm/s^2) M906 X1300 Y1300 Z1300 E1350:1300 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 X245 Y250 Z200 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io2.in M574 Y1 S1 P"io4.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io4.in M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"io3.out" ; create servo pin 0 for BLTouch M558 P9 C"io3.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height 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 R0.391 K0.323:0.000 D1.74 E1.35 S1.00 B0; 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 R3.215 K0.349:0.000 D6.27 E1.35 S1.00 B0 V24.1 ; 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"out4" Q500 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 H0 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"out3" Q500 ; create fan 1 on pin out3 and set its frequency M106 P1 S1 H0 T45 ; set fan 1 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
-
RE: Diag flashing
diag, usb, 3.3v ,5v. 3 red one green all solid computer just said the devise malfunctioned and windows does not recognize it
-
RE: Diag flashing
@Phaedrux Had it dialed in was producing some great prints, Then just in the middle stopped and could not connect again.
-
RE: Diag flashing
"Error reading device descriptor" This is as far as I get, I can't get past that. That's the one I was working last night before I came back here. my mac or rpi 4 wont see it either usb not recognized with or with a sd card different ports and cables and restart of the machine.
-
RE: Diag flashing
@Phaedrux yes thank you I am working on that now.