This worked! It was the homing issue G92. Thank you!

@droftarts Apologies for that, I am fairly new to this. Below is an updated output from the diagnostic command, and attached is the config.g file.

M122 B71.0
Diagnostics for board 71:
Duet M23CL firmware version 3.5.2 (2024-06-10 13:23:16)
Bootloader ID: SAME5x bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 45108, free system stack 202 words
Tasks: EncCal(1,nWait 6,0.0%,469) Move(3,nWait 7,0.0%,174) CLSend(3,nWait 6,0.0%,147) HEAT(2,nWait 6,0.0%,117) CanAsync(5,nWait 4,0.0%,66) CanRecv(3,nWait 1,0.0%,79) CanClock(5,nWait 1,0.0%,64) TMC(4,nWait 6,0.0%,397) MAIN(1,running,97.5%,303) IDLE(0,ready,0.0%,29) AIN(2,nWait 2,2.5%,255), total 100.0%
Owned mutexes:
Last reset 00:05:30 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, not tuned/calibrated, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -15/4, peak Rx sync delay 185, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 11.9, current 11.9, max 11.9
V12 voltage: min 10.4, current 10.4, max 10.5
MCU temperature: min 26.3C, current 26.5C, max 26.7C
Last sensors broadcast 0x00000000 found 0 8 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 2674, send timeouts 0, received 1670, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Closed loop driver 0 mode: closed loop, pre-error threshold: 2.00, error threshold: 4.00, encoder type rotaryAS5047, position -5801
Encoder reverse polarity: no, full rotations -1, last angle 10583, minCorrection=0.0, maxCorrection=0.0, agc 66, mag 4695, no error
Tuning mode: 0, tuning error: 0x2, collecting data: no
Control loop runtime (us): min=5726621, max=1, frequency (Hz): min=750000, max=0

config.g

; Default config.g template for DuetPi
; Replace this with a proper configuration file (e.g from https://configtool.reprapfirmware.org)

; Display initial welcome message
; M291 P"Please go to <a href=""https://www.duet3d.com/StartHere"" target=""_blank"">this</a> page for further instructions on how to set it up." R"Welcome to your new Duet 3!" S1 T0

G4 S2 ; Wait for expansion boards to start


; Setup X axis motor
M569.1 P70.0 T3 ; Assign magnetic encoder
M569 P70.0 D4 S1 ; Assign closed loop control and forward movement
M584 X70.0 ; Set motor to X axis control
M906 X1000 ; Set current limit

; Setup Y axis motor
M569.1 P71.0 T3 ; Assign magnetic encoder
M569 P71.0 D4 S1 ; Assign closed loop control and forward movement
M584 Y71.0 ; Set motor to Y axis control
M906 Y1000 ; Set current limit

; Setup V axis motor
M569.1 P74.0 T3 ; Assign magnetic encoder
M569 P74.0 D4 S1 ; Assign closed loop control and forward movement
M584 V74.0 ; Set motor to X axis control
M906 V1000 ; Set current limit

M17 ; Allow motors to move

I just realized that the other two motors I setup were 2407B00010 but this one that is not working is 2402B00021. I can't find on Google how this makes a difference (they look identical).

I am facing an issue getting a new M23CL motor to calibrate/move. I have attached pictures with the sequential commands I ran on this motor.

Following these same commands, I successfully set up two other motors using the same cables/connectors/setup, just swapping out the motor.

I've powered things up/down a few times, I updated the firmware of the mainboard (3.5.2) and of the motor (3.5.2), and tried resetting CAN on the motor; none to any avail.