Posts made by CrooKID

So, my board will not show any memory containing firmware or DWC. I thin k i may have short-circuited the board somewhere in that i do believe i dropped a tiny piece of tin coated copper stranding wire into the board at some point and then bumped the piece into the perfect possition to short out a critical piece of hardware component. When I tyy to use /access DWC I get an endless loop of nothing as well as no response from terminal. Its been a while since ive had time to conquer this projects desired conclusion and fix the dang thing. I find it difficult to proceed without any help. Thanks.

Re: [Video] Adding a USB Webcam to DWC with a Raspberry Pi

Hello, so i really like the idea of monitoring prints. Im following your advice and using MotionOS setup on an Orange Pi One. I have a Duet2 WiFi board and would really like to utilize the WiFi capabilities of the Duet to carry over the video image to DWC. Any suggestions as to this being possible? Thank you all!

@Phaedrux
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sat Sep 24 2022 19:41:27 GMT-0600 (Mountain Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-242 Y-242 F6000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-242 Y-242 F240 ; move slowly to X and Y axis endstops once more (second pass)
G1 H1 Z-266.5 F240 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sat Sep 24 2022 19:41:27 GMT-0600 (Mountain Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Z-266.5 F6000 ; move Z down until the endstop is triggered
G92 Z-2.5 ; set Z position to axis minimum (you may want to adjust this)

  ; Configuration file for Duet WiFi (firmware version 3.3)

; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sat Sep 24 2022 19:41:26 GMT-0600 (Mountain Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender3" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display

; 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 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M569 P4 S1 ; physical drive 4 matches drive2
M584 X0 Y1 Z2:4 E3 ; set drive mapping
M671 X-27:263 Y115:115 S10 P2 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E130.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z720.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-5 Y-15 Z-3.5 S1 ; set axis minima
M208 X235 Y235 Z250 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F200 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-56.6 Y-3.5 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X20:180 Y20:220 S40 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S150 ; set temperature limit for heater 0 to 150C
M308 S1 P"spi.cs1" Y"rtd-max31865" ; create sensor number 1 as a PT100 sensor in the first position on the Duet 2 daughterboard connector
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 R2.383 K0.432:0.000 D17.52 E1.35 S1.00 B0 V23.8
M143 H1 S375 ; set temperature limit for heater 1 to 275C

; 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 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 S1 H1:0 T45 ; set fan 2 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

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool

What if we could see the mathematics behind the representation of Z in the firmware files in a simple, field variable controller in the DWC. Where using text fields to supply user inputs of the real world numbers that controll the position and show corrections of all things related to Z positioning.

I would like to see this user adjusted model directly change the firmware variables for Z related data. Firmware files such as 'config.g's Z-probe sections Z-probe offset, 'homeall's Z-home position, absolute Z, etc.

Visual representation of the point of extrusion relative to the point at which printing begins on the bed. Everything else that surrounds and determines this in a scalable vector model controlled by the user.!

All-in-all be able to effectively synthasize a visual representation of the machines homing of the z. Maybe in real time have the numbers(variables) change according to the machine movements reguarding homing, probing in real time and as a simulated model using user inputs. Reminds me of the old Adobe flash projects in freshmen year.

@phaedrux
In DWC; Dashboard; Status box; under Sensors; Z-Probe. The output of the probe does not change, ever. I can invert the signal by adding an "!" in front of the "^zprobe.in" and the signal will appear to have been inverted in the Z-Probe Status field. But really thats a superficial readout change. So, having run the static test and hoping that the Duet 2 WiFi board picked up the tip touching the bed is to no avail. This is the second BLTouch I've used/tested with. Swaped the Z-Probe and the GND signals too... nada.

Hello! some issues withthe bltouch not showing any detection. Correct setup in config.g:

M558 P9 C"^zprobe.in" H5 F200 T6000

propper deployment and retraction of the probes solonoid through:

M950 S0 C"exp.heater3"

The wiring is correct and has continuity. Just isnt showing once the tip is drawn back after touching the bed. Anything helps!!!

Im trying to get a bltouch clone to pull from the duet2's expansion header's 5v and grnound pins #1 & #2. The multimeter is reading only +4.75v from the 5v and GND pins. I am using some Crealty 24v fans for the hotend so have pulled a 24v line to the fan power select center pin and have selected the EXTERNAL jumper and a 5v psu as the EXT 5V power source. Blade fuses check out. I'd like to think that locating the 5v regulator will be the imediate solution however I have noticed that at one point all 5, if not 4, board LED indicators were illuminated. Any suggestions or secret documents that would power up the expansion header?

@arhi Finding this Thermistor pin to be the one. As listed in the Hardware and Connections of the https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#physical-connections: EXPANSION HEADER THERM7 (pin 39) e6temp, exp.thermistor7, exp.39 duex.e6temp. Wish I knew basic HTML and make this look like I have a clue.

@arhi Hello! Im looking for something along the similar to your query-- an analog pin for an input signal. Spicificly, I have a PT100 Amp board, temp. sensor that doesnt seem to use a MAX31865 chip. Triangle labs tl pt100 amplifier board. Deduced from their "official" AliExpress website, they state that only a single signal pin is required to recieve the one beseigheded 'signal' of analog discourse. Aside, a mere 5v and a 0v, or grounding pin secures the trios. Simple, right? Well, provided that this windy briefment is sufficient to satisfy any required knowlageable instruction and not interfere with the foreseeable future of the Duet 2 board I hope this might be the first, only informal documentation on attatching one of these things to a Duet 2. Please, anything further is always appreciaed and thank you for you time and responses.

@fickert so where are the follow ups to this general topic? I mean even a GENERAL response ANYWHERE in the forum would suggest some hope for the desk jockeys and neck crackers out there. Honestly, I thought there would be an easily found list, pdf even, at the top of any search engines response to search: DWC keyboard shortcuts. Nothing! Good luck, Im not a programmer by any means what so ever. Thanks.

@phaedrux
I see. I really feel like keeping the warranty active based on the various issues that have arisen in the past. However the time it has taken to resolve those issues has been a bit of another issue. Is there any middle ground we could take that solves the driver without voiding the warranty? I'm a big fan of resolution the 'smart' way, seems to serve better than any dumb way I've ever conceived. I appreciate having people smarter than mine in my corner. Thanks and I appreciate you.

@phaedrux
Yes. I've been working with FPV drones... for some few years now. I can successfully swap out processors consistently. They're about the same exact size as TMC2660 drivers and have roughly 4 times the pins. I feel confident in my work and materials for success. As for the stepper motors, They're a Sanyo stepper, bipolar, 1.8 ohms at each phase. All specs check out and fall within the parameters of the Duet2 board. Hella bummer. Again... BUT-"... try, try, again." Thanks for your alls continued support.

Hello, All! Finally completed dropping in recent Duet 2 WIFI replacement board. Installed motors are new, tested as well as the cables. For the 2nd time I'm hit with the "Error: short-to-ground reported by driver....". This board it is sensing that its Y axis driver is at fault. I break it down to isolate the reported problematic circuit; shut down, detach cabling, power. I begin to test for continuity throughout the component, primarily the driver chip soldering to the board. I compare my findings to results that are consistent across all other non-faulted components, driver chips. My multimeter detects a NON-transient grounding across the chip. This chip isn't holding anything to its own circuits. Every pin seems to connect with every other pin. I can honestly testify to DWC's reporting of a ground short on Driver 1, this "Y" axis driver. Oddly, when DWC is sent command M122 (included at bottom) the entire set of drivers report nothing unusual whatsoever. This Driver chip is the only one off. All others check out consistently.

Given this board has been returned twice already, thank you Filastruder for all your efforts and patience. I know this kind of attention and service is unique to you. I do not really want to sit idly by for another month while this issue is benched with suggestions and checklists, finally given an RMA, sent a shipping label after approvals, packed, sent, huge blank space filled with imagination and informational void, then surprises me at my door step some shiny day in the fortuitous distant future. Takes way to long.

So, I purpose that I order a replacement chip directly, to me, where I can desolder and replace the faulted driver myself, saving both time, energy. That said, how would the Duet's warranty become affected?

6/12/2022, 5:46:35 PM 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-JUNSN-6JKF0-3SJ6R-TVNBT
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 78528 of which 0 recycled
Never used RAM 9684, free system stack 184 words
Tasks: NETWORK(ready,10.2%,243) HEAT(notifyWait,0.0%,332) Move(notifyWait,0.0%,364) MAIN(running,84.1%,466) IDLE(ready,5.7%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:16 ago, cause: reset button or watchdog
Last software reset at 2022-06-11 21:07, reason: User, GCodes spinning, available RAM 9536, 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 20.2, current 21.7, max 22.0
Supply voltage: min 23.9, current 24.1, max 24.3, 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 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-12 17:46:31
Cache data hit count 590318053
Slowest loop: 4.95ms; 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 3.6ms, 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
=== Network ===
Slowest loop: 15.55ms; 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 48:3f:da:a6:83:8a
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 22336
WiFi IP address 192.168.137.2
WiFi signal strength -70dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0!
Thank you guys. All helps, totally green here.

@bergy
Haven't used PrusaSlicer with this machine yet, have in the past and liked it. However this is happening with a spanky shiny new build; firmware, drivers, board. All is fresh from scratch and RepRap config is at the top execution. Everything is handled though DWC including firmware upgrades and transfers. I do appreciate your thoughts.

As for the wiring. the Looms are correct. They are stayed the same as was working before, same motors, setup, all is correct. Man, should the phases hold continuity across the two? Phase 1 (A or B) is in continuity with phase 2 (A or B). So really, any one of the four wires contacts any other three. This is not normal. I think I need to file for an RMA, request requested. Right? Thanks.

@crookid

Update: So, with limited knowledge of driver chips and some confirming knowledge from FPV chips (ESC's) I have deduced that the two phases are in contact of one another on the drivers side. Yes, continuity has been detected and confirmed within drivers 0, 1 & 4. Axis ZA and E0, extruder, seem to be holding their own between their respective phases. I find any sort of explanation a high overstatement. This is something I fail to understand the how, whys, or just about any thing about.

@phaedrux Removed one wire from X connection at board. Home X in DWC. Received this: G28 X
Warning: Driver 0 warning: phase A may be disconnected. The carriage (X stepper, this is an original Ender 3 setup I'm working to get inside an enclosure minded) does try to go down to the endstop but only vibrates fairly rapidly and quite noisily.

I did move the X stepper termination from the X stepper to an identical stepper motor and attempt to home. Just to generate some movement, ID the motor or the board... the swapped motor did the same thing, vibration without turning.

When the printer is without power to the drivers (the 24vdc IN) I can move any component freely, gently always. When 24v is flowing through the motors hold their positions.

Did the link to the video work? I had edited it for time however I could produce the long, drawn out, data hog version of whatever. Let me know. This thing may be at the warrantied time frames limitation very soon. Struggling poor person, 200 buck is a TON of money to me.

@phaedrux Yes the firmware updated recently. From March 28, the first ever software and firmware setup, to April 4th 2022. In April, I updated from 3.2.x to 3.4.0. However the update, the printer was homing fine at the beginning of using the current RepRapFirmware. Also, recently I added a Z-Probe. Initially it was an inductive probe using a voltage divider to bring the Zstop.in to 0 from around 3. It was G92 Z0, G30 S-1 making sure the trigger height was consistent. Well, was not. So I setup an old endstop switch as a viable replacement. Unfortunately this has not yet been tested because of this fundamental issue of kinematics (STEPPER PROBLEM).
The endstop I now have as the Z-Probe is from the Ender 3's factory package, just without the metal lever. The switch has no electronic influence on the signal in that it simply goes from NO to closed, IF I'm correct.

This is a video of homing the x axis from the most recent update of DWC:
https://drive.google.com/file/d/1gQD5vdYzfHeV8nGMgnYxXpspTOY6eONl/view?usp=sharing
Note; the motor does continue to make a slight ticking noise after the loud vibration that sounds until DWC finally reports:
G28 X
Error: Failed to home axes X
After z raises the x-gantry; the loud vibrating sounds for 5sec, the 2nd slight quickly ticking lasts for 1min. These recorded measurements are real-time, the video is edited for time and file size.

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-9P6M2-NW4SJ-6J9DD-3SJ6M-KASVK
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 78800 of which 0 recycled
Never used RAM 9340, free system stack 134 words
Tasks: NETWORK(ready,13.3%,232) HEAT(notifyWait,0.0%,332) Move(notifyWait,0.0%,305) MAIN(running,85.9%,442) IDLE(ready,0.7%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:10 ago, cause: software
Last software reset at 2022-04-11 22:39, reason: User, GCodes spinning, available RAM 9340, 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 31.2, current 33.6, max 34.2
Supply voltage: min 24.0, current 24.2, max 24.3, 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
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-04-11 22:41:30
Cache data hit count 4294967295
Slowest loop: 5.56ms; 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 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 42582ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 5, completed 5, 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 2 -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
=== Network ===
Slowest loop: 15.57ms; 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 f4:cf:a2:e2:20:91
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 23384
  WiFi IP address 192.168.137.26
  WiFi signal strength -66dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 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.10 on Mon Apr 04 2022 02:23:47 GMT-0600 (Mountain Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender 3 Pro" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display

; 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 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M569 P4 S1 ; physical drive 4 goes forwards
M584 X0 Y1 Z2:4 E3 ; set drive mapping
M671 X-27:263 Y115:115 S0.5 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E93.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1200 I50 ; 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 X235 Y235 Z260 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop

; Z-Probe
M558 P5 C"!zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X-53 Y-9 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S150 ; set temperature limit for heater 0 to 150C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; 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
M143 H1 S275 ; set temperature limit for heater 1 to 275C
M308 S2 P"e1temp" Y"thermistor" T100000 B4092 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2 ; create chamber heater output on e1heat and map it to sensor 2
M307 H2 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H2 ; map chamber to heater 2
M143 H2 S275 ; set temperature limit for heater 2 to 275C

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"Part Cooling" S1 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"HE Sink" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H2 T45 ; set fan 2 value. Thermostatic control is turned on

; Tools
M563 P0 S"Hot End" 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

; Miscellaneous
T0 ; select first tool

The stepper motors and or drivers (X,Y,Z,E,Z2) do not sound as they did only moments ago. Same firmware, DWC, same everything. Funny, every driver on the Duet2 WiFi produce this. Tried amp adjustment via config.g, G90, G91. Relative mode slightly lessened the horrifying sound, slightly. Plenty of internet research. WTF. New board too!

@dc42
M587
Failed to retrieve network list: SPI timeout
ok
Error retrieving WiFi status message: SPI timeout
WiFi module is idle
Error retrieving WiFi status message: SPI timeout
Failed to change WiFi mode: SPI timeout

again, and again... how do i go about filing a warranty claim?