@Notepad Thank you very much, that is quite helpful. I will start getting things on order.

I am really new to these boards, so some of my questions I am sure have been answered before.
As stated above the firmwares for the PI 4 and the 6HC are not matching. I have tried every different combinations.
Here is my procedure:

1. First I am unable to connect to the pi through SSH (do not know why yet)
2. I am using raspberry pi imager to move the file "image_2024-09-19-DuetPi-arm64.zip"
   a. I have added to the cmdline.txt file
3. I am using DWC to upload the the 6HC file name: "DuetSoftwareFramework-3.5.4.zip"

That has been my process below is what I get out of M122 when sent from the DWC
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.02 or later (SBC mode)
Board ID: 0JD2M-9P9DA-F0PSD-6J1F6-3S46Q-14SM2
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 153252
Dynamic ram: 65240 of which 0 recycled
Never used RAM 132180, free system stack 219 words
Tasks: SBC(resourceWait:,0.5%,486) HEAT(notifyWait,0.0%,371) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,343) TMC(notifyWait,7.3%,92) MAIN(running,92.3%,1126) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:29:17 ago, cause: power up
Last software reset time unknown, reason: HardFault undefInstr, GCodes spinning, available RAM 132328, slot 0
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00010000 ICSR 0x0044a803 BFAR 0x00000000 SP 0x20423f48 Task CanR Freestk 622 ok
Stack: 400e0c00 5a000013 00000000 00000000 204241d8 00481675 004aa808 21070000 20423fdc 00000003 20423fdc 204354a8 0048257d 00000003 00453523 2042ac48 0000fddc 204354a8 00449f63 204354a8 878541e5 dfff8386 7e7dffff ffff797f ffffffff ffffffff ffffffff
Error status: 0x00
Step timer max interval 134
MCU temperature: min 35.4, current 42.9, max 43.2
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.3, max 12.5, under voltage events: 0
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, mspos 8, reads 29935, writes 0 timeouts 0
Driver 1: standstill, SG min n/a, mspos 8, reads 29935, writes 0 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 29935, writes 0 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 29935, writes 0 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 29936, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 29936, writes 0 timeouts 0
Date/time: 2024-12-24 16:43:01
Slowest loop: 0.90ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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 8187, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 8187/0/0
Tx timeouts 0,0,8187,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 2481/2481
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ab5c
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.3 (2024-09-19 12:16:06, 64-bit)
HTTP+Executed:

Executing M122
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.39, max time between full transfers: 40.6ms, max pin wait times: 32.5ms/4.7ms
Codes per second: 0.29
Maximum length of RX/TX data transfers: 3380/272

@mikeabuilder Thanks, I have heard nothing but great things about Duet3d

@Notepad Thank you very much, that is quite helpful. I will start getting things on order.

Hello my name is Daryl. (Larry is just fine, thank you)
I am in the process of building a 4 cubic foot 3d printer. I am looking for the best controller on the market. I have multiple hot zones, all motors except for extruder will be Nema 23 (minimum 285ozin). X,Y and Z will be Ballscrews for more accuracy. There will be two Z motors. I have .25 temperedglass on top of 4- 12x12x.25 Aluminum plate, which is setting on top of more layers including a silicone layer.
Well that just part of the build, but one of my main questions is whether Duet3d can support multiple heat zones, and have enough processing power to run fast and keep accuracy at the same time. I know it can handle the motors with its built in drivers. Can someone let me know what type of speed they are running, keeping accuracy. Also what hot end do you recommend.

Thank you