Posts made by NightLonk42

undefined

@dc42 Awesome!

I'm not able to update currently but a couple questions.

Is the Input Shaping plugin be installed by default? Also, will the Input Shaping page be updated to give more detail any time soon?

Thanks!

undefined

@phaedrux said in Board caught on fire:

Wow that is quite spectacular failure.

When and where did you purchase the Duet?

Filastruder in July 2021

@oliof said in Board caught on fire:

Are you running Klipper by chance?

No I am not

@gixxerfast said in Board caught on fire:

Wow, spectacular. Not the sort of thing I'd want to happen to my printer.

Please take this the right way as not trying to cast any shadow on the description here at all only trying to understand would could cause such a major breakdown..

But I would like to ask if you perhaps had heat sinks attached on the driver chips? I see that you have one on the MCU and that usually runs much cooler than the drivers in my experience.

I did have heat sinks on the drivers but they were the tall skinny ones and I was very sure there
wasn't any metal or anything on the bottom. They were fully "covered" on the bottom.

@dc42 said in Board caught on fire:

@nightlonk42 what power supply are you using? The only things I can think of that are likely to blow multiple drivers at the same time in such a spectacular fashion is reversed power supply polarity, or excessive voltage from the PSU.

I'm using a 24V Meanwell and it's been working fine up until now. I did just check the voltage and I'm actually undervolted by a small amount (23.7). Also double checked the polarity and it's fine. It's been working up until last night perfectly.

I also have a other few devices plugged into the PSU (Buck converter for the Pi4, power to Toolboard) and those are fine as well.

undefined

I have zero idea how this has happened as it's been working flawlessly for months up until tonight.

Printer had been off for about a week. Powered on to start a print and INSTANTLY two drivers caught on fire.

Nothing was on the board that would have caused an arc, and I run it using a Pi so settings weren't even loaded in yet. Nothing was upgraded changed swapped etc etc and now I have basically a dead board

Edit: I also verified with a different board that the two steppers that were plugged in had no issues.

Help?

See attached,

undefined

I've been getting some....very odd results when trying to configure the magnetic filament sensor. Any ideas?

The min/max are always at these results, no matter how much prints

Duet3D rotating magnet filament monitor v3 on pin 121.io1.in, disabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 3, mag 132 agc 78, measured sensitivity infmm/rec, min 2147483647% max 2147483647% over 99.1mm

undefined

Looking to compare mine with others as I have a feeling mine are off

Duet Mini 5+

M566 X600.00 Y600.00 Z6.00 E400 P1             ; set maximum instantaneous speed changes (mm/min)
M203 X20000.00 Y20000.00 Z1000.00 E3600       ; set maximum speeds (mm/min)
M201 X10000.00 Y10000.00 Z150.00 E3600        ; set accelerations (mm/s^2)

undefined

Any chance this is a RatRig build?

undefined

@gloomyandy is today's big winner!

G29 S1                                  ; Set Units to Millimeters

When this is commented out it works fine.

RatRig's RepRap firmware page here has this listed. It's the cause of all the issues I've been having. I've contacted them and it should hopefully be fixed soon.

Thank you all soo much for the help! I seriously love this community

undefined

@fcwilt

I do not have a mesh.g but here are all the files I have.

The weirdest thing is this all happens before anything is even homed. Paneldue right away won't connect, and the Z probe is uncontrollable

bed.g

; this script compensates for what the Z offset is
; so if G31 P500 X-30 Y-15 Z1.7 then first probe will be at
; X30 Y20 (when G30 P0 X0 Y5)

M561 ; clear any bed transform

G30 P0 X8 Y20 Z-99999 ; probe near a leadscrew
G30 P1 X263 Y485 Z-99999 ; probe near a leadscrew
G30 P2 X485 Y15 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors

deployprobe.g

; deployprobe.g
; Called to deploy a physical Z probe
;
M280 P0 S10															; Deploy the BLTouch pin

homeall.g

; BLTouch
M280 P0 S160           ; Precautionary alarm release
M280 P0 S90            ; Ensure the pin is raised

G91                     ; relative positioning
G1 H2 Z5 F6000          ; lift Z relative to current position
G1 H1 X-625 Y605 F3600 ; move quickly to X and U axis endstops and stop there (first pass)
G1 H1 X-625 F1800 ; move quickly to X and U axis endstops and stop there (first pass)
G1 H1 Y605 F1800 ; move quickly to X and U axis endstops and stop there (first pass)
G1 H2 Y3 X3 F360       ; go back a few mm
G1 H1 X-625 Y605 F360  ; move slowly to X and U axis endstops once more (second pass)
G1 H1 X-625 F360  ; move slowly to X and U axis endstops once more (second pass)
G1 H1 Y605 F360  ; move slowly to X and U axis endstops once more (second pass)

G90                     ; absolute positioning
G1 X250 Y250 F10000 ; go to first probe point
G30                     ; home Z by probing the bed

G91                    ; relative positioning
G1 Z5 F100             ; lift Z relative to current position
G90                    ; absolute positioning

homex.g

G91               ; relative positioning
;G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X-625 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X2 Y2 F6000    ; go back a few mm
G1 H1 X-625 F360  ; move slowly to X axis endstop once more (second pass)
;G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

homey.g

G91               ; relative positioning
;G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 Y605 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y-5 F6000     ; go back a few mm
G1 H1 Y605 F360  ; move slowly to Y axis endstop once more (second pass)
;G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

homez.g

; BLTouch
M280 P0 S160           ; Precautionary alarm release
M280 P0 S90            ; Ensure the pin is raised

G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G90               ; absolute positioning
G1 X250 Y250 F10000 ; go to first probe point
G30               ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91              ; relative positioning
;G1 Z5 F100       ; lift Z relative to current position
;G90              ; absolute positioning

pause.g

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool v3.3.2 on Sun Sep 19 2021 18:36:33 GMT-0400 (Eastern Daylight Time)
M83            ; relative extruder moves
G1 E-10 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X0 Y0 F6000 ; go to X=0 Y=0

resume.g

; resume.g
; called before a print from SD card is resumed
;
; generated by RepRapFirmware Configuration Tool v3.3.2 on Sun Sep 19 2021 18:36:33 GMT-0400 (Eastern Daylight Time)
G1 R1 X0 Y0 Z5 F6000 ; go to 5mm above position of the last print move
G1 R1 X0 Y0          ; go back to the last print move
M83                  ; relative extruder moves
G1 E10 F3600         ; extrude 10mm of filament

retractprobe.g

; retractprobe.g
; Called to retract a physical Z probe
;
M280 P0 S90													; Retract the BLTouch pin

undefined

Bump

I've gone through my config file a couple times and can't figure out anything that could be causing it.

undefined

@chrishamm said in HeightMap Bug:

@nightlonk42 Please share your config.g and config-override.g if it is present in /sys.

; 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
M552 S1                                 ; enable network
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; disable FTP
M586 P2 S0                              ; disable Telnet

; Wait for the Tool Board
G4 S1  								    ;wait for expansion boards to start

;; Drives
M569 P0.0 S0 D3                         ; physical drive 0.0 goes backwards
M569 P0.1 S0 D3                         ; physical drive 0.1 goes backwards
M569 P0.2 S0 D3                         ; physical drive 0.2 goes backwards
M569 P0.3 S1 D3                         ; physical drive 0.3 goes backwards
M569 P0.4 S1 D3                         ; physical drive 0.4 goes forwards
M569 P121.0 S0 D3                       ; physical drive 0.5 goes backwards
M584 X0.4 Y0.3 Z0.0:0.1:0.2 E121.0      ; set drive mapping
M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation


M92 X160.00 Y160.00 Z1600.00 E412         ; set steps per mm
M906 X1300 Y1300 Z1300 E650 I30           ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                   ; Set idle timeout

M566 X400.00 Y400.00 Z6.00 E3600 P1            ; set maximum instantaneous speed changes (mm/min)
M203 X10800.00 Y10800.00 Z1000.00 E3600.00     ; set maximum speeds (mm/min)
M201 X4000.00 Y4000.00 Z100.00 E300.00        ; set accelerations (mm/s^2)

;; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X510 Y500 Z500 S0                         ; set axis maxima

;; Endstops
M574 X1 S1 P"121.io3.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:250:304.5 Y-4.52:505:-4.52 S15       ; define positions of Z leadscrews or bed leveling screws
M557 X10:480 Y20:480 P5                         ; define 5x5 mesh grid

;; Heaters

; Motherboard CPU
M308 S3 Y"mcu-temp" A"CPU Temp" ; configure sensor 3 as on-chip MCU temperature sensor

; Bed
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed"    ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                     ; create bed heater output on out5 and map it to sensor 0
M307 H0 B0 R0.365 C1124.6 D9.30 S1.00                  ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                ; map heated bed to heater 0
M143 H0 S130                                           ; set temperature limit for heater 0 to 130C

;; HotEnd
M308 S1 P"121.temp0" Y"pt1000"                        ; T1000 sensor 1 (toolboard)
M950 H1 C"121.out0" T1                       	      ; create nozzle heater output on 121.out0 and map it to sensor 1
M307 H1 B0 R2.998 C108.1 D5.56 S1.00 V24.0 	  	      ; disable bang-bang mode for Nozzle Heater and set PWM limit
M143 H1 S350                               	          ; set temperature limit for heater 1

;; Fans
M950 F0 C"121.out2"                                   ; create fan 1 on pin out6 and set its frequency
M106 P0 C"Heatsink Fan" S1 H1 T45                     ; set fan 1 name and value. Thermostatic control is turned on
M950 F1 C"121.out1"                                   ; create fan 0 on pin out3 and set its frequency
M106 P1 C"Print Fan" S0 H-1 Q500                      ; set fan 0 name and value. Thermostatic control is turned off
M950 F2 C"out5"     				                  ; create fan 2 on pin out5 and set its frequency
M106 P2 C"Back Fan" H-1 S255                          ; set fan 2 value

M106 P1 I1 F25000

;; 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
T0						   ; Select tool 0

;; Z-Probe
; BLTouch
M950 S0 C"121.io0.out"                     ; Create a servo pin on io0.out
M558 P9 C"121.io0.in" H10 F240 T10800 A5   ; set Z probe type to unmodulated and the dive height + speeds
G31 P25 X-28.00 Y-13.00 Z2.80              ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed


;Accelerometer
M955 I10 P121.0       ; Accelerometer 121:0 with orientation 10

;; Misc

;M207 S.6 R0 F13300 ;set firmware retraction
M572 D0 S0.1 ; Pressure Advance

M575 P1 S1 B57600                          ; enable support for PanelDue

undefined

RRF 3.4Beta3
Duet 3 Mini 5+
Toolboard V1.1 with BL Touch
Paneldue
RatRig V-Core 3 500

I'm having a really odd issue happening consistently. I've tried two different Duet Mini 5+'s, different SD cards, checked a couple firmware revisions and it's happening on them all. (3.4 betas, and 3.3 stable)

When a G29 is done and a heightmap is saved, everything is fine. The mesh is saved to the system directory and there are no issues printing or viewing it. But if the printer is power cycled my Paneldue will no longer connect to the board, and Z Leveling will no longer function.

9/13/2021, 10:49:13 PM	Error: in file macro line 17: G30: Z probe 0 not found
Error: G0/G1: insufficient axes homed
9/13/2021, 10:49:11 PM	G28
Error: in file macro line 17: G30: Z probe 0 not found

(I originally thought it was an error with the InputShaping plugin that's in testing but after fully deleting it, it is still happening. See https://forum.duet3d.com/topic/24859/inputshaping-plugin-0-1-0-rc7-released-repacked/21?_=1632808845077 for that post)

When deleting the heightmap and power cycling the system everything works fine. It only happens when a heightmap is currently in the system directly and the printer is power cycled.

I've double checked that everything is fully updated to whatever firmware revision I'm using at the time for testing. Any ideas?

undefined

Hello there! Hopefully an easy question

Is a Z homing needed after performing a G32 bed leveling or does firmware auto compensate for this?

Thanks!

undefined

@gloomyandy said in InputShaping-Plugin-0.1.0-rc7 released (repacked):

@nightlonk42 Are you saying that if you do not install the input-shaper plugin (or disable it) that this problem does not happen?

That is correct

undefined



I've tried on the latest RRF beta and 3.3. It's replicated 100% every time.

Duet Mini 5+ Wifi
Toolboard V1.1
BL Touch (in case that matters somehow)~~

```
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0beta3 (2021-08-24 14:08:24) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: GJRQ5-V396U-D65J0-40KM8-K013Z-7VUQA
Used output buffers: 3 of 40 (15 max)
=== RTOS ===
Static ram: 102756
Dynamic ram: 107252 of which 28 recycled
Never used RAM 31676, free system stack 200 words
Tasks: NETWORK(ready,11.8%,253) HEAT(notifyWait,0.0%,372) Move(notifyWait,0.0%,338) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,346) TMC(notifyWait,0.7%,115) MAIN(running,85.4%,428) IDLE(ready,1.2%,29) AIN(delaying,0.8%,266), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:19 ago, cause: software
Last software reset at 2021-09-13 22:57, reason: User, GCodes spinning, available RAM 31388, slot 0
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,0
MCU revision 3, ADC conversions started 19343, completed 19341, timed out 0, errs 0
Step timer max interval 750
MCU temperature: min 43.7, current 44.1, max 44.8
Supply voltage: min 24.0, 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, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 70, reads 988, writes 12, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 70, reads 988, writes 12, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 70, reads 987, writes 12, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 70, reads 987, writes 12, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 70, reads 988, writes 12, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-09-13 22:58:05
Cache data hit count 36845245
Slowest loop: 3.99ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.5ms, 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 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 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 193, received 591, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 237, free buffers 17 (min 16), ts 97/96/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 15.35ms; 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:02:e6:b1
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 2097152, free heap 21408
WiFi IP address 192.168.1.29
WiFi signal strength -35dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 4 0 0 0 0 0 0
```
- -
How to replicate:


* -Install InputShaping Plugin (Currently using latest version as of 9/13/21)

* Start it

*No issues whatsoever with homing or G32 happen at this point. Everything is fine*

* Home Printer

* Run mesh compensation (G29)

*A Height Map is saved* 
(The height map file is what's causing the bug for whatever reason)

* Reboot printer

*Paneldue will no longer connect and is now stuck at connecting*

* Try to Home Printer

*BL Touch will not deploy and the console throws error messages*
 ```
9/13/2021, 10:49:13 PM	Error: in file macro line 17: G30: Z probe 0 not found
Error: G0/G1: insufficient axes homed
9/13/2021, 10:49:11 PM	G28
Error: in file macro line 17: G30: Z probe 0 not found
```

* Delete heightmap.csv

* Reboot printer

*Everything now works as expected again*~~

undefined

Figured it out! It seems to be a software bug related to InputShaper plugin. Posted more info here https://forum.duet3d.com/topic/24859/inputshaping-plugin-0-1-0-rc7-released-repacked

undefined

@jay_s_uk said in Z probe 0 not found and paneldue suddenly not connecting:

@nightlonk42 can't see anything wrong.
You could try removing M574 Z1 S2 from your config and see if that changes anything

Same thing

9/13/2021, 5:47:27 PM Error: in file macro line 9: G30: Z probe 0 not found
Error: G0/G1: insufficient axes homed
9/13/2021, 5:47:25 PM G28
Error: in file macro line 17: G30: Z probe 0 not found

I've also tried to downgrade to RRF 3.3 to see if it made any difference and it has not.

Same odd thing is happening with paneldue, refuses to connect. I even wiped the firmware from it and updated using BOSSA and nothin. Both issues happened at the same time.

Fan control on toolboard works fine, along with heating, temp and the installed limit switch