@fcwilt It's connected to PWM1 on the Duex board, but I just found that my White and Orange wires were swapped, so that has it fixed. Thanks for coming to my aid
Best posts made by tomasro
-
RE: Newly installed Duex5, BLTouch no longer working
-
RE: Driver 1 Phase A short to ground...but when it's disconnected?
@phaedrux @dc42 I removed the Duex board, and replugged the power, drivers and ribbon cable...and now it works. Thank you for your diagnostic help!!!!!
Latest posts made by tomasro
-
RE: Driver 1 Phase A short to ground...but when it's disconnected?
@phaedrux @dc42 I removed the Duex board, and replugged the power, drivers and ribbon cable...and now it works. Thank you for your diagnostic help!!!!!
-
RE: Driver 1 Phase A short to ground...but when it's disconnected?
@dc42 The Lugs on the VIN for the DUEX board were not loose, but I was able to tighten them down (multimeter reads 24V). Fuse has continuity.
I plugged the ribbon cable back in and the BLTouch gets power, and does a self test on power up, but the z motors don't lower for the X or Y homing (which they should) and they don't raise the bed for a bed homing.
-
RE: Driver 1 Phase A short to ground...but when it's disconnected?
UPDATE: I disconnected the Duex5 board, and moved the end stops to the Duet board, so now the only thing that would be connected to the Duex5 board is the BLTouch servo and the 4 z motors.
The short to ground error has gone away.
Any clues??
-
Driver 1 Phase A short to ground...but when it's disconnected?
I'm ALMOST at my wits end with this...
Duet reports:
-Filament out (filament is loaded)
-X and Y axis are homed (they aren't)
-Driver 1 Phase A and B short to ground (happens when Driver 0 and 1 are connected or not)Synopsis: The printer was printing great, then started having these issues. I replaced the Duet2Wifi but nothing changed. Then the problem went away after replacing the CoreXY motors. Then it was printing great, but today the same problem came about.
Side note and possibly unrelated: I have a 3/8" thick 500mmx500mm bed with a 600w silicon heating pad that takes a while to heat up, and occasionally the Duet will report that it's heating too slow. I've PID tuned the bed (as seen in the config file), but I can usually get past it with a fault reset.
Could someone point me in a direction that doesn't involve pulling out what remaining hair I have? Thanks in advance
Config.g:
; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.4 on Fri Oct 22 2021 23:28:40 GMT-0700 (Pacific Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"R2D Cube" ; set printer name M669 K1 ; select CoreXY mode M912 P0 S-8.2 ;calibrate MCU temperature ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S0 ; physical drive 0 goes backwards M569 P1 S0 ; physical drive 1 goes backwards M569 P3 S1 ; physical drive 3 goes forwards M569 P5 S0 M569 P6 S0 M569 P7 S0 M569 P8 S0 ; Disable unused stepper drivers M569 P2 R-1 M569 P4 R-1 M569 P9 R-1 M584 X0 Y1 Z5:6:7:8 E3 ; set drive mapping M671 X-40:515:-40:515 Y37:37:430:430 S5 ; leadscrews at left front, right front, left rear, right rear M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z808.00 E402.00 ; set steps per mm M566 X900.00 Y900.00 Z100.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z6000 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z250 E250.00 ; set accelerations (mm/s^2) M906 X900 Y900 Z800 E800 I1 ; set motor currents (mA) and motor idle factor in per cent M84 S10 ; Set idle timeout ;Pressure Advance M572 D0 s0.02 ; Axis Limits M208 X0:455 Y0:400 Z0:420 ; Endstops M591 P2 C"!duex.e2stop" S1 D0 ; filament monitor connected to E0 endstop M591 D0 ; display filament sensor parameters for extruder drive 0 M574 X1 S1 P"!duex.e3stop" ; configure switch-type (e.g. microswitch) endstop for low end on X M574 Y1 S1 P"!duex.e4stop" ; configure switch-type (e.g. microswitch) endstop for low end on Y ;M574 X1 S3 ;M574 Y1 S3 ;M574 Z1 S2 ; testing stall control for homing ;M915 P0:1 S3 R0 F0 H400 ; Z-Probe M950 S0 C"duex.pwm1" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H10 F600 T10000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X35 Y35 Z1.3 ; set Z probe trigger value, offset and trigger height M557 X72:490 Y35:440 S50 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 R0.221 C451.3 D2.62 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"e0temp" Y"thermistor" T100000 B4725 C7.060000e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 ;M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M307 H1 R3.422 K0.381:0.000 D1.69 E1.35 S1.00 B0 V24.6 M143 H1 300 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1.0 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency ;M106 P2 H2:3 L0.15 X1 B0.3 T30:70 ; set fan 2 value M106 P2 H-1 S1 ;T30 M950 F3 C"e1heat" Q250 M106 P3 H-1 S0 ; 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 ;Temp Sensor trigger ;M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as on-chip MCU temperature sensor ;M308 S4 Y"drivers-duex" A"DRIVERS-DUEX" ; configure sensor 3 as temperature warning and overheat flags on the TMC2660 on Duex ; Custom settings are not defined T0;
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9X6JA-JUNSW-6J1FG-3SD6P-1AMVU Used output buffers: 3 of 24 (17 max) === RTOS === Static ram: 23868 Dynamic ram: 74856 of which 0 recycled Never used RAM 13356, free system stack 184 words Tasks: NETWORK(ready,13.2%,232) HEAT(notifyWait,0.0%,332) Move(notifyWait,0.0%,364) MAIN(running,83.8%,440) IDLE(ready,2.9%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:00:34 ago, cause: software Last software reset at 2022-06-01 11:18, reason: User, GCodes spinning, available RAM 13284, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 25.8, current 26.5, max 26.8 Supply voltage: min 24.3, current 24.5, max 24.8, 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: 1 queued, 1 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2022-06-01 11:18:41 Cache data hit count 1218411468 Slowest loop: 18.76ms; fastest: 0.19ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.3ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, 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 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 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: no filament === Network === Slowest loop: 19.09ms; fastest: 0.00ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 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 48:3f:da:a6:82:fa WiFi Vcc 3.39, reset reason Power up WiFi flash size 2097152, free heap 24160 WiFi IP address 192.168.1.200 WiFi signal strength -43dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0
-
RE: Drivers over temp, but sensors read 0
@cosmowave No. It's not that the endstop gets inverted. It's like the board is gets glitched.
Would anyone recommend heatsinks on the back of the board?
-
RE: Drivers over temp, but sensors read 0
@cosmowave I must not have been clear: The end stop monitor showed that the x and y endstops were triggered, and yet the carriage was in the middle of the bed (nowhere near the endstops)
Also, the heater temperature went up to 2000C according to the thermister. It was a straight line up on the chart. And the filament sensor triggered, even though there was filament loaded
Something VERY weird is going on here
-
RE: Drivers over temp, but sensors read 0
@dc42 The console reported drivers 1 and 2 were over temp. Also, the board was misreading the X and Y axis to be homed, when the printhead was away from the home position
-
Drivers over temp, but sensors read 0
I experienced a weird error last night where the drivers skipped steps and then stopped, reporting they were over temp. I have a sensor mapped to the driver temperature and it was reading 0.
I shut down the machine for the night and came back in the morning and it was fine, but I am clueless as to what to do about this. It is the second time it's happened and I have active cooling to the backside of both my Duet Wifi and Duex5 boards.
Specs:
Duet Wifi 1.01 & Duex5 0.10
Quad Z motors on drivers 5, 6, 7 and 8
80mm fan active above 30 degreesm122 @1AM === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4S8-6JKDD-3SD6S-KP8HY Used output buffers: 3 of 24 (11 max) === RTOS === Static ram: 23876 Dynamic ram: 75272 of which 12 recycled Never used RAM 15256, free system stack 184 words Tasks: NETWORK(ready,13.9%,236) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) MAIN(running,85.1%,441) IDLE(ready,1.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:37 ago, cause: software Last software reset at 2021-11-06 00:59, reason: User, GCodes spinning, available RAM 12048, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 21.2, current 24.7, max 24.9 Supply voltage: min 24.5, current 24.6, max 24.9, 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, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-11-06 01:00:52 Cache data hit count 3495336090 Slowest loop: 8.42ms; fastest: 0.17ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.2ms, 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 -1 -1, chamberHeaters = -1 -1 -1 -1 === 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 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Filament sensors === Extruder 0 sensor: no filament === Network === Slowest loop: 15.48ms; 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 --- WiFi Vcc 3.38, reset reason Turned on by main processor WiFi flash size 4194304, free heap 22040 WiFi IP address 192.168.1.200 WiFi signal strength -46dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 4 0 0 0 0 0 0
m122@ 1PM === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.0 or 1.01 + DueX5 Board ID: 08DAM-999TL-MQ4S8-6JKDD-3SD6S-KP8HY Used output buffers: 3 of 24 (24 max) === RTOS === Static ram: 23876 Dynamic ram: 75816 of which 320 recycled Never used RAM 11548, free system stack 124 words Tasks: NETWORK(ready,14.2%,236) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,304) DUEX(notifyWait,0.0%,24) MAIN(running,85.7%,441) IDLE(ready,0.0%,29), total 100.0% Owned mutexes: === Platform === Last reset 04:22:11 ago, cause: power up Last software reset at 2021-11-06 00:59, reason: User, GCodes spinning, available RAM 12048, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 24.2, current 24.4, max 25.1 Supply voltage: min 24.5, current 24.6, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/12/8, gc cycles 0 Driver 0: position 400, ok, SG min/max 70/142 Driver 1: position -400, ok, SG min/max 60/137 Driver 2: position 4040, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0, standstill, SG min/max 8/1023 Driver 6: position 0, standstill, SG min/max 33/1023 Driver 7: position 0, standstill, SG min/max 63/1023 Driver 8: position 0, standstill, SG min/max 18/1023 Driver 9: position 0, standstill, SG min/max not available Driver 10: position 0 Driver 11: position 0 Date/time: 2021-11-06 13:33:04 Cache data hit count 4294967295 Slowest loop: 8.06ms; fastest: 0.17ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.7ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 15691834ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 14, completed moves 13, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === 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, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by HTTP HTTP is idle in state(s) 2 15, running macro 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Filament sensors === Extruder 0 sensor: ok === DueX === Read count 4, 8.54 reads/min === Network === Slowest loop: 203.74ms; fastest: 0.08ms Responder states: HTTP(2) 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 1 WiFi firmware version 1.26 WiFi MAC address --- WiFi Vcc 3.38, reset reason Turned on by main processor WiFi flash size 4194304, free heap 23752 WiFi IP address 192.168.1.200 WiFi signal strength -46dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 4 0 0 0 0 0 0 0
; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.4 on Fri Oct 22 2021 23:28:40 GMT-0700 (Pacific Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"R2D Cube" ; set printer name M669 K1 ; select CoreXY mode M912 P0 S-8.2 ;calibrate MCU temperature ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S0 ; physical drive 0 goes backwards M569 P1 S0 ; physical drive 1 goes backwards M569 P3 S1 ; physical drive 3 goes forwards M569 P5 S0 M569 P6 S0 M569 P7 S0 M569 P8 S0 M584 X0 Y1 Z5:6:7:8 E3 ; set drive mapping M671 X-40:515:-40:515 Y37:37:430:430 S5 ; leadscrews at left front, right front, left rear, right rear M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z808.00 E402.00 ; set steps per mm M566 X900.00 Y900.00 Z100.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z6000 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z250 E250.00 ; set accelerations (mm/s^2) M906 X900 Y900 Z800 E800 I1 ; set motor currents (mA) and motor idle factor in per cent M84 S10 ; Set idle timeout ; Axis Limits M208 X0:455 Y0:405 Z0:420 ; Endstops M591 P2 C"!duex.e2stop" S1 D0 ; filament monitor connected to E0 endstop M574 X1 S1 P"!duex.e3stop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin !xstop M574 Y1 S1 P"!duex.e4stop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin !ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"duex.pwm1" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H10 F600 T10000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X35 Y35 Z1.7 ; set Z probe trigger value, offset and trigger height M557 X72:490 Y35:440 S100 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 R0.221 C451.3 D2.62 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"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 ;M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M307 H1 B0 R2.107 C262.7:238.2 D6.31 S1.00 V24.6 M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1.0 H1 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 ;Temp Sensor trigger M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as on-chip MCU temperature sensor M950 F2 C"fan2" Q100 ; create fan 2 on pin fan2 and set its frequency ;M106 P2 H2:3 L0.15 X1 B0.3 T30:70 ; set fan 2 value M106 P2 H2:3 S1 T30
-
RE: Printer locked up
@jay_s_uk So why would it report drivers over temp when it shows 0?
-
RE: Printer locked up
@tomasro I turned the machine off overnight and now the driver are working, but they still don't return a temperature from the sensor.