Thanks for the fast reply! The mesh grid line was exactly what I needed (M557)! I just had to tweak the radius down because I have a smaller bed.

For the Z probe, I figured out my problem. I was putting the gcode in for REPRAP 2.X, and I'm on 3.0 For anyone that ever comes across this looking for this answer, after plugging into the probe instead of E0, this is the line that made my probe work:

M558 P5 C"^zprobe.in" H5.0 F120 T6000

Also, after doing the autocalibration, I figured out how to do individual rod lengths for X/Y/Z, to adjust for slight discrepancies in rod length you just put it in as "L210:210:211" instead of "L210.33", I assume for X Y Z respectively (still testing that).

Now that I think I have everything figured out, I am really digging my Duet board. To think I almost got a hold of another 8bit noisy marlin board. No more juggling SD cards or dragging a USB cable and compiling every time I want to adjust or print something.

@Phaedrux That fixed it! I didn't expect it to, since I thought the newest firmware files simply bundled both the main firmware and wifi firmware, but I am happy to report I was wrong.

Thank you so much. I was dreading trying to figure out how to fix the board if the wifi was bad.

As the title says, I had this board setup and working great on firmware 3.0 and 3.1, but I updated to 3.1.1 and the printer sat for a bit waiting for a new fan, but when I went to test the new fan, the status lights were on but no wifi connection. Is my wifi module bad? If so is it possible to replace the module via soldering since my board is drastically out of warranty?

What I've tried:
The erase button and installing fresh 3.1.1 with freshly generated config.
Erase and install 3.0.0
Configuring wifi by gcode
Checking it wasn't acting like it's own access point

I can connect by USB, but what I get for the following commands:

M115:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.0 ELE
CTRONICS: Duet WiFi 1.0 or 1.01 FIRMWARE_DATE: 2020-01-03b3

M552:
WiFi module is being started (never running, always started)

M587
Error: Failed to retrieve network list (With WIFI both on/off)

M587 S"SSID" P"password"
Error: Failed to add SSID to remembered list

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.0 or
1.01
Board ID: 08DAM-999TL-MQ4S4-6J9F6-3S46L-TNHVY
Used output buffers: 3 of 24 (13 max)
=== RTOS ===
Static ram: 30516
Dynamic ram: 91208 of which 12 recycled
Exception stack ram used: 320
Never used ram: 9016
Tasks: NETWORK(ready,1888) HEAT(blocked,1240) MAIN(running,3736) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 00:39:16 ago, cause: power up
Last software reset time unknown, reason: Hard fault, spinning module GCodes, av
ailable RAM 9152 bytes (slot 2)
Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041f003 BFAR
0xe000ed38 SP 0x2001ff74 Task 0x5754454e
Stack: 0044b753 0047bb90 6000000f 00000000 20003d50 e000ed04 00026d36 a5a5a5a5 0
0451eaf 00000000 00000000 e000ed04 00455efd a5a5a5a5 200055dc a5a5a5a5 10000000
e000ed04 20003d50 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 33.0, current 33.3, max 33.5
Supply voltage: min 12.3, current 12.4, max 12.4, under voltage events: 0, over
voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 3080553735
Slowest loop: 0.22ms; fastest: 0.11ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets
0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0
, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0
, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 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 ===
Slowest loop: 0.22ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8

• WiFi -
  Network state is starting
  WiFi module is disabled
  Failed messages: pending 0, notready 0, noresp 0
  Socket states: 0 0 0 0 0 0 0 0

Thanks for the fast reply! The mesh grid line was exactly what I needed (M557)! I just had to tweak the radius down because I have a smaller bed.

For the Z probe, I figured out my problem. I was putting the gcode in for REPRAP 2.X, and I'm on 3.0 For anyone that ever comes across this looking for this answer, after plugging into the probe instead of E0, this is the line that made my probe work:

M558 P5 C"^zprobe.in" H5.0 F120 T6000

Also, after doing the autocalibration, I figured out how to do individual rod lengths for X/Y/Z, to adjust for slight discrepancies in rod length you just put it in as "L210:210:211" instead of "L210.33", I assume for X Y Z respectively (still testing that).

Now that I think I have everything figured out, I am really digging my Duet board. To think I almost got a hold of another 8bit noisy marlin board. No more juggling SD cards or dragging a USB cable and compiling every time I want to adjust or print something.

Hello everyone. Normally I google/power my way through problems on my own, but this I just can't quite figure out what I need to do. I kind of killed the junk motherboard in my FLSUN Kossel (basically Anycubic Kossel), and I thought why not use the Duet Wifi 1.0 board I have sitting around which has never been used. I have it printing surprisingly well for no autocalibration, but I know at least with Marlin that improves quality tremendously.

The "Delta Calibration (G32)" moves to several points in the Z=5.65 plane, but it never actually probes the bed. It seems like it does not think I have a probe.

This printer has a simple endstop switch in the effector, so when the nozzle pushes on the bed it clicks the switch. I think I have it set right? It is plugged into the E0 Stop and the corresponding ground. Config.g probe lines:

M558 P4 X0 Y0 Z0 H3 F300 T12000
G31 X0 Y0 Z0.65 P500

I also get "No valid grid" for mesh compensation, but I am less worried about that and more worried about delta calibration.

If it helps, this is my bed.g file:

; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 10 points, 7 factors, probing radius: 80, probe offset (0, 0)
G30 P0 X0.00 Y80.00 Z-99999 H0
G30 P1 X69.28 Y40.00 Z-99999 H0
G30 P2 X69.28 Y-40.00 Z-99999 H0
G30 P3 X0.00 Y-80.00 Z-99999 H0
G30 P4 X-69.28 Y-40.00 Z-99999 H0
G30 P5 X-69.28 Y40.00 Z-99999 H0
G30 P6 X0.00 Y40.00 Z-99999 H0
G30 P7 X34.64 Y-20.00 Z-99999 H0
G30 P8 X-34.64 Y-20.00 Z-99999 H0
G30 P9 X0 Y0 Z-99999 S7

Oh, one last thing, I can't find any way to adjust individual diagonal rod length to correct for one dimension being shorter than the other for 6 sided calibration objects. As far as I can tell, RepRap doesn't have an adjustment for that like Marlin does. Am I stuck with slightly off dimensions?