I finally got my machine running and I'm ALMOST there with the mesh leveling. I can get it to probe 25 points but the resulting map is obviously not right.

Here are my bed.g and config.g files. I copied most of the important bits from the other threads. The result I get is from clicking the bed compensation button in the GUI. I know I'm missing something obvious but I have no idea what it is.

The printer is a wanhao I3 with a 190x200 bed. I think it has something to do with the grid… Also the deviation between points seems awfully high.

;bed.g taken from another user
M557 X40:180 Y40:180 S28    ; Define grid, edit this

T0                          ; Select tool 0
G91                 ; Relative mode   
G1 Z10 F150            ; Make sure everything clears the bed                     

; ------------ Home Z ---------------------

G90                         ; Absolute mode
G1 X110.5 Y72 Z6 F4000      ; Home at center of bed, my offsets are X-22 and Y44, edit these
M401                        ; Deploy probe
G30                         ; Home Z-axis

;----------- Mesh Level ------------------

G29                         ; Start mesh level
M374                        ; Save results, but this might not be necessary 
M402                        ; Retract probe 

G1 X20 Y20 Z10 F3000        ; Dock position

;config.g
; DuetWIFI config
M111 S0                             ; Debug off
M550 DuetHaoi3                      ; Machine name (can be anything you like)
M551 i3                             ; Machine password (currently not used)
M552 S1                             ; Enable WiFi
M555 P2                             ; Set output to look like Marlin
M575 P1 B57600 S1                   ; Set auxiliary serial port baud rate and require checksum (for PanelDue)

; Movement
G21                                 ; Work in millimetres

M569 P0 S0                          ; Drive 0 goes backwards
M569 P1 S0                          ; Drive 1 goes backwards
M569 P2 S1                          ; Drive 2 goes forwards
M569 P3 S1                          ; Drive 3 goes forwards

M906 X855 Y855 Z670 E1020           ; Set motor currents (mA)
M201 X1000 Y800 Z100 E5000          ; Accelerations (mm/s^2)
M203 X12000 Y12000 Z400 E3000       ; Maximum speeds (mm/min)
M566 X600 Y600 Z18 E20              ; Maximum jerk speeds mm/minute

M574 X1 Y1 Z0 S0                    ; set homing switch configuration (No z switch, use z probe with M558)
M208 X200 Y200 Z180                 ; set axis maxima and high homing switch positions (adjust to suit your machine)
M208 X-8 Y-8 Z-0.5 S1               ; set axis minima and low homing switch positions (adjust to make X=0 and Y=0 the edges of the bed)

M92 X80 Y80 Z400 E96.780                ; set axis steps/mm
M350 X128 Y128 Z128 E128 I1             ; set 16x microstepping with interpolation

G90                                 ; Send absolute coordinates...
M83                                 ; ...but relative extruder moves

; Z-Probe
; M558 P1 X0 Y0 Z1 H3 F200 T5000      ; smart IR Z probe, used for homing Z axis only, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min
; G31 P500 X-45 Y45 Z0.66             ; set threshold and offsets

; BLtouch stuff
M307 H3 A-1 C-1 D-1 ; use pin 3 on header for bltouch
M558 P5 X0 Y0 Z1 H5 F100 T2000  ;  probe type and use probe for homing z *T2000 travel speed*
G31 X-22 Y-44 Z2.18  P25 ; set probe height  ** edit this ** 

; Heaters + Thermistors
M305 P0 T100000 B3950 R4700 H0 L0   ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B4388 R4700 H0 L0   ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction

M307 H0 A193 C719.9 D8.7 B0         ; bed heater settings
M307 H1 A472.7 C214.3 D6.5 B0          ; extruder heater settings

M570 S120                           ; Increase to allow extra heating time if needed

M106 P1 T45 H1
M106 P2 T45 H1                      ; Run Coldend-Fan and electronics fan at 45°C

; T0
M563 P0 D0 H1                       ; tool 0 uses extruder drive 0 and heater 1
G10 P0 S0 R0 X0 Y0                  ; set tool 0 temperatures and offsets

; the end
M556 S100 X0 Y0 Z0                  ; Put your axis compensation here
T0                                  ; Select the first head

RepRapFirmware height map file v1, mean error -0.18, deviation 1.39
xmin,xmax,ymin,ymax,radius,spacing,xnum,ynum
40.00,180.00,40.00,180.00,-1.00,28.00,6,6
 -2.166, -1.154, -0.195,  0.771,  1.697,      0
 -2.196, -1.150, -0.161,  0.810,  1.731,      0
 -2.193, -1.153, -0.155,  0.810,  1.745,      0
 -2.161, -1.118, -0.120,  0.837,  1.780,      0
 -2.161, -1.117, -0.118,  0.844,  1.786,      0
      0,      0,      0,      0,      0,      0

Boy that's super discouraging. That's two bad boards in a row. I used both the default config.g and a config provided by another wanhao user that was linked here. I get sane output from M906 so I guess I won the Duet lottery again.

Your diagnosis seems spot on. The drivers are indeed cold. All steppers are completely idle as if they're not even plugged in.

>>> M906
SENDING:M906
Motor current (mA) - X:855, Y:855, Z:670, E:855:855:855:855:855:855:855, idle factor 30%
Error: Short-to-ground on drivers 0 1 2 3 4
[ERROR] Error: Short-to-ground on drivers 0 1 2 3 4

Error: Over temperature shutdown on drivers 0 1 2 3 4
[ERROR] Error: Over temperature shutdown on drivers 0 1 2 3 4

I made a thread a couple days ago regarding the spotty WIFI on my new Duet WIFI… The good news is the WIFI on my replacement works great. The bad news is the steppers don't work at all. With the previous board I was able to jog the printer using Pronterface, but with this board the steppers are completely disabled.

In an attempt to troubleshoot, I upgraded to 1.19 Beta9 and I'm getting an immediate "short to ground" and "over temp" errors with nothing connected to the board. I did not touch any wiring while the board was powered up and the board has been sitting on the box it came in throughout the setup process. Starting to lose hope here. Reading the forums it seems like failures are extremely rare so I can't believe my luck.

I have a multimeter and basic electronics experience so I can try to identify the fault if you tell me where to probe. The output below is with absolutely nothing connected except USB. When I had it wired up I had all lights and temps were working. Additionally, the lights for the x,y,z stops worked on trigger. It's just the steppers that don't do anything. The output with 1.18 said the steppers were in standstill.

EDIT: I have verified that all 6 stepper headers have no continuity on any pin to power ground. I can't see any solder bridges or physical damage to the board. ???

>>> m122
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (9 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19beta9 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3SJ6Q-TLZMY
Static ram used: 20904
Dynamic ram used: 96392
Recycled dynamic ram: 1488
Stack ram used: 4000 current, 5212 maximum
Never used ram: 7076
Last reset 00:01:36 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 33024 bytes (slot 1)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
[ERROR] Error status: 0

Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 30.7, current 31.3, max 31.5
Supply voltage: min 12.6, current 12.7, max 12.8, under voltage events: 0, over voltage events: 0
Driver 0: stalled temperature-shutdown! short-to-ground standstill
Driver 1: stalled temperature-shutdown! short-to-ground standstill
Driver 2: stalled temperature-shutdown! short-to-ground standstill
Driver 3: stalled temperature-shutdown! short-to-ground standstill
Driver 4: stalled temperature-shutdown! short-to-ground standstill
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.003207; fastest: 0.000031
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
Network state is disabled
WiFi module is disabled
HTTP sessions: 0 of 8
Socket states:  0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
Error: Short-to-ground on drivers 0 1 2 3 4
[ERROR] Error: Short-to-ground on drivers 0 1 2 3 4

Error: Over temperature shutdown on drivers 0 1 2 3 4
[ERROR] Error: Over temperature shutdown on drivers 0 1 2 3 4

Disconnected.

wow thanks for the quick reply. seawest is the name of my 2.4 Ghz network and my seawest 5G is my 5 Ghz network. Both are off of the same ASUS router that sits about 10 feet away. The names are case sensitive and exactly as they're seen from my iphone. My password is alphanumeric and only contains letters and a number.

The thing that makes me suspicious that the board is bad is the fact that I don't see "Duet WIFI" when the board thinks it's in AP mode when using 1.18. Are there any debug commands I can use to test the functionality of the WIFI module itself? I was able to get the board to connect a handful of times and it seemed tied to loading a new WIFI firmware. However, I have tried reloading firmware several times since then and I haven't been able to re-establish a connection.

I WAS able to connect to the "Duet WIFI" SSID but only once. When that occurred I could see my neighbor's APs as well as my own. I was also able to get into the web interface but as soon as I uncommented "M552 S1" and rebooted I had the same problems all over again and could not reconnect.

I just got a Duet Wifi and I'm having a hell of a time with the WIFI setup. I have tried flashing 1.18 stable as well as 1.19 beta 8. I first attempted upgrades via M997 but eventually tried the erase/reset/reload via samba. I have gotten it to connect once or twice but it seems whenever I edit config.g to uncomment M552 S1 it fails to connect again after reboot. I have fiddled with it quite a bit since then and haven't been able to get it to talk to my router again.

I've noticed a couple things

1. when using 1.18 M552 will say that the board is in AP mode but I can't see it in my list of WIFI networks.
2. when it does this it also says hostname is some bunch of gibberish ascii characters
3. when using 1.19 Beta 8 M587 returns the two remembered networks I have configured in my SetNetwork macro however when I do a M552 S1 I get

M587
SENDING:M587
Remembered networks:
seawest
seawest 5G
M552 S1
SENDING:M552 S1
WiFi reported error: no known networks found
Wifi module is idle

I'm starting to think the board is faulty. Is there anything else I can try? It's almost as if the WIFI module is retaining some kind of garbage. Is there a way to purge everything so I'm starting fresh? SD Card, memory, everything?