@Phaedrux I received my replacement board and now everything works properly. Thank you!

@Phaedrux Sorry about the R parameter... not sure about that one, but removed it anyway with no effect. The mappings are correct. The tool boards appear to be functioning correctly.

I finally got back to the Railcore RRF3x issue and ended up pulling my boards... @Phaedrux mentioned the Duet WiFi was a cloned board... and I think that was the problem. I put in a genuine Duet board I had on hand it is has been working without a hitch. It is POSSIBLE that the very act of the board R&R corrected a wiring issue (intermittent connection) or the like... sometimes it is hard to tell if things are terminated properly. Overall a great learning... nothing gets me from rote knowledge to understanding faster than solving challenging problems - cheers.

p.s. thx to @JoergS5 too for the help!

@fcwilt Only 2 extruders in use on this machine.

@dc42! Thank you for uploading the Sammy Firmware. It was an easy install and it seems to be working.
BTW, it is not part of the ZIP files in the repository, you have to get it manually. Thank you again for everything you do here!!!

@droftarts Thank you for the help! I am printing it as we speak!

I did look at the GitHub post about compiling your own firmware for the Sammy board (purchased from Fliastruder, with the boot loader pre-installed) but either the links are dead or I am faced with the realization I need to spend several months going blind learning how to use the listed dev tools to do something one of you guys has already done, or can do in 15 minutes.
That said, I believe a good call for help in in order!
I am using RRF 3.2 at the moment but will gladly upgrade to the latest stable (3.2.2?) to be able to experiment with this thing.
In exchange, if you help and forward me an address... I will send you a car Hahaha - Thank You!!!

@Phaedrux I received my replacement board and now everything works properly. Thank you!

@Phaedrux Thank you.
No damage to the board... New (but purchased several months back) .

1/28/2021, 5:23:21 PM	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9F6-3SJ6P-KA02G
Used output buffers: 1 of 40 (14 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 63292 of which 76 recycled
Never used RAM 145676, free system stack 128 words
Tasks: Linux(blocked,101) HEAT(blocked,296) CanReceiv(blocked,817) CanSender(blocked,352) CanClock(blocked,352) TMC(blocked,19) MAIN(running,1202) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:15:51 ago, cause: power up
Last software reset at 2021-01-27 20:22, reason: User, Move spinning, available RAM 145492, slot 1
Software reset code 0x0004 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 14.2, current 34.4, max 34.6
Supply voltage: min 23.8, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Driver 0: position 48000, standstill, reads 10707, writes 20 timeouts 0, SG min/max 0/318
Driver 1: position 0, standstill, reads 10707, writes 20 timeouts 0, SG min/max 0/315
Driver 2: position 704000, standstill, reads 10708, writes 19 timeouts 0, SG min/max 0/88
Driver 3: position 0, standstill, reads 10708, writes 20 timeouts 0, SG min/max 0/169
Driver 4: position 0, standstill, reads 10708, writes 20 timeouts 0, SG min/max 0/183
Driver 5: position 0, standstill, reads 10708, writes 20 timeouts 0, SG min/max 0/191
Date/time: 2021-01-28 17:23:22
Slowest loop: 147.61ms; fastest: 0.04ms
=== 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, maxWait 59073ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 28, completed moves 28, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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 3756, send timeouts 0, received 22295, lost 0, longest wait 2ms for reply type 6031, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 2ms ago
RX/TX seq numbers: 33136/33136
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 0.91
Maximum length of RX/TX data transfers: 3092/712

; Duet 3 hardware, 6HC Main board plus 2 tool boards 

; Printer name is set on the R Pi. 

; Networking
;;;M552 P192.168.1.2 S1               	; Use Ethernet with a static IP
;;;M553 P255.255.255.0                	; Netmask
;;;M554 192.168.1.3                  	; Gateway
M586 P1 S0                              ; Disable FTP
M586 P2 S0                              ; Disable Telnet

; Debugging
M111 S0                                 ; Debug off
M929 P"eventlog.txt" S1                 ; Start logging to file eventlog.txt

; General Preferences
M555 P2                           		; Set Marlin-style output
G21                                		; Set dimensions to millimetres
G90                            	    	; Send absolute coordinates...
M83                              		; ...but relative extruder moves

; Kinematics
M669 K1                     			; CoreXY mode

; Leadscrew locations (really, kinematic coupling locations) extracted from CAD model assuming back right build plate corner is (0, 0)
M671 X300:5:152.5 Y316:316:-14 S10 	; Front Left: (300, 316) | Front Right: (5, 316) | Back: (-14, 152.5)


; Axis to driver mapping
M569 P0 S0 D2                  			; Drive 0 direction | X stepper
M569 P1 S0 D2                 	 		; Drive 1 direction | Y Stepper
M569 P2 S0                  			; Drive 2 direction | U Tool Changer Lock
M569 P3 S0 D2                 			; Drive 3 direction | Front Left Z
M569 P4 S0 D2                 			; Drive 4 direction | Front Right Z
M569 P5 S0 D2                 			; Drive 5 direction | Back Z
M569 P20.0 S0 D2						; set tool 2 extruder direction on Hermera Toolboards
M569 P21.0 S0 D2						; set tool 3 extruder direction on Hermera Toolboards

M584 X0 Y1 U2 Z3:4:5        			; X and Y for CoreXY.  U for toolchanger lock. Z has three drivers for kinematic bed suspension. 
M584 E20.0:21.0							; Set Hermera extruder drives up on Hermera Toolboards 

; Axis and motor configuration
M350 X16 Y16 I1                   		; Set 16x microstepping for axes. Use interpolation.
M350 U4 I1                        		; Set 4x for toolchanger lock. Use interpolation.
M350 Z16 I1                     		; Set 16x microstepping for axes. Use interpolation.
M350 E16:16 I1

; Motor Configurations
M906 X2500 Y2500 Z1000 E1250 I30        ; Motor currents (mA) and Idle percentage
M906 U900 I60                           ; Motor currents (mA) and Idle percentage
M201 X600 Y600 Z10 E1000 U1000          ; Accelerations (mm/s^2)
M203 X25000 Y25000 Z400 E4000 U10000   	; Maximum speeds (mm/min)
M566 X700 Y700 Z2 E3000 U200          	; Maximum jerk speeds mm/minute

;M92 X200 Y200                          ; Steps/mm for X,Y with 16 tooth pulleys (preferred). 
M92 X160 Y160                           ; Steps/mm for X,Y with 20 tooth pulleys. 
M92 Z3200				                ; Steps/mm for Z - TR8*4 / 0.9 deg stepper
M92 U11.429                             ; Steps/mm for tool lock geared motor. 
M92 E837:837							; Extruder - 0.9 deg/step
				               	

; Endstops and probes

M574 X1 S1 P"io1.in"                    ; Set homing switch configuration X1 = low-end, S1 = active-high (NC)
M574 Y1 S1 P"io2.in"                    ; Set homing switch configuration Y1 = low-end, S1 = active-high (NC)
M574 U1 S1 P"io3.in"                    ; Set homing switch configuration U1 = low-end, S1 = active-high (NC)
;M574 Z1 S1 P"!io4.in"                  ; Set homing switch configuration Z1 = low-end,  S1 = active-high (NC).  This is used for tool probing, not actual Z height.

M558 K0 P5 C"io4.in" H8 A5 T6000 S0.02  ; Z probe - Set the height of the bed when homing G28.  Combined with content of bed.g as invoked by G32, levels bed. Also used for Mesh. 
                                      	; P5 = Switch, NC
                                     	; C  = Input Connector
					; Hn = dive height
					; A bigger dive height prevents a situation where the bed is out of alignment by more than the dive height
					; on any corner, which can crash the hot-end into the bed while moving the head in XY.
					; Probing speed and travel speed are similarly reduced in case the Z probe isn't connected properly (or
					; disconnects later after moving to a point) giving the user more time to stop.
                                       	; An = Number of times to probe each point. 
                                      	; Tnnn = Travel speed between probe points. 
                                      	; Snnn = Tolerance when probing multiple times. Two readings inside this window and we move on. 
;M558 K1 P5 C"!io4.in"              	; create probe #1 for use with M585, active low


; Set axis software limits and min/max switch-triggering positions. Adjust such that (0,0) lies at the lower left corner of the build plate.
M208 X-5:305 Y-10:365 Z-0.5:220
M208 U0:180

; Temperature sensors
M308 S0 P"0.temp0" Y"thermistor" T10000 B3984 A"Bed" 		; Bed sensor
M308 S1 P"20.temp0" Y"thermistor" T100000 B4725 C7.06e-8	; Hemera sensors and heaters
M308 S2 P"21.temp0" Y"thermistor" T100000 B4725 C7.06e-8	; Hemera sensors and heaters

; Heaters
M950 H0 C"0.out0" T0           							; Bed.  H = Heater 0, C is output for heater itself, T = Temperature sensor (defined above)
M950 H1 C"20.out0" T1									; Hemera sensors and heaters
M950 H2 C"21.out0" T2									; Hemera sensors and heaters

; Further setup for bed
M143 H0 S130                                           	; set temperature limit for heater 0 to 130C
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

; Default heater model
M307 H0 A140 C252 D0.7 S1.0 V24.0 B0       				; Tuned Bed Heater Paramaters, same as report above, also B0 to turn off bang-bang
M307 H1 A452 C235 D11 V24                                                
M307 H2 A452 C235 D11 V24
          												; Default Bed Heater Parameters, before tuning / if config-override.g is missing
; Calibration 28 Oct 2019
;Heater 0 model: gain 139.6, time constant 252.2, dead time 0.7, max PWM 1.00, calibration voltage 24.5, mode PID
;Computed PID parameters for setpoint change: P468.8, I35.594,  D225.7
;Computed PID parameters for     load change: P468.8, I136.631, D225.7


; Hemera fans
M950 F5 C"20.out2+out2.tach" ; Tool 0 hot end fan with tacho
M950 F6 C"20.out1" ; Tool 0 print cooling fan, no tacho
M950 F7 C"21.out2+out2.tach" ; Tool 1 hot end fan with tacho
M950 F8 C"21.out1" ; Tool 1 print cooling fan, no tacho
M106 P5 S255 H1 T50 ; Tool 0 hot end
M106 P6 S0 ; Tool 2 PCF
M106 P7 S255 H2 T50 ; Tool 1 hot end
M106 P8 S0 ; Tool 3 PCF

; Tool definitions
M563 P0 S"Tool 0" D0 H1 F5      		; Px = Tool number, Dx = Drive Number (start at 0, after movement drives), H1 = Heater Number, Fx = Fan number print cooling fan
G10  P0 S210 R160               		; Set tool 0 operating and standby temperatures(-273 = "off")
M572 D0 S0.1  		            		; Set pressure advance on 

M563 P1 S"Tool 1" D1 H2 F6      		; Px = Tool number, Dx = Drive Number (start at 0, after movement drives), H1 = Heater Number, Fx = Fan number print cooling fan
G10  P1 S210 R160               		; Set tool 1 operating and standby temperatures(-273 = "off")
M572 D1 S0.1		            		; Set pressure advance on 


M98  P"/sys/Toffsets.g"                	; Set tool offsets from the bed. In separate file so test macro can invoke. 


; Set up the dock indicator switches on the Hemera tools. These are wired NO so invert the pin (commented out for now).
;M950 J2 C"20.^!io0.in"					; GpIn 2 = tool 0 dock switch
;M950 J3 C"21.^!io0.in"					; GpIn 1 = tool 1 dock switch

M575 P1 B57600 S1

;M98 P"config-user.g"    ; Load custom user config if one exists.

;M501                    ; Load saved parameters from non-volatile memory

;G29 S1

Hello! What does "Driver 0: position 1263870, 837.0 steps/mm, assumed not present" in board 20 mean??? Everything else works but the extruder drive motor is NoOp. This is the 122 dump...

1/27/2021, 6:41:37 PM	M122 B21
Diagnostics for board 21:
Duet TOOL1LC firmware version 3.2 (2021-01-05)
Bootloader ID: not available
Never used RAM 4052, free system stack 38 words
HEAT 90 CanAsync 89 CanRecv 83 TMC 54 MAIN 214 AIN 64
Last reset 01:15:48 ago, cause: power up
Last software reset data not available
Driver 0: position 167400, 837.0 steps/mm, standstill, SG min/max 0/496, read errors 0, write errors 0, ifcnt 43, reads 46048, writes 43, timeouts 0, DMA errors 0
Moves scheduled 10, completed 10, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.1V
MCU temperature: min 18.3C, current 34.0C, max 36.0C
Ticks since heat task active 229, ADC conversions started 4543552, completed 4543551, timed out 0
Last sensors broadcast 0x00000004 found 1 233 ticks ago, loop time 0
CAN messages queued 54464, send timeouts 0, received 59106, lost 0, free buffers 36
1/27/2021, 6:41:17 PM	M122 B20

Diagnostics for board 20:
Duet TOOL1LC firmware version 3.2 (2021-01-05)
Bootloader ID: not available
Never used RAM 4052, free system stack 44 words
HEAT 86 CanAsync 89 CanRecv 83 TMC 60 MAIN 208 AIN 64
Last reset 01:15:28 ago, cause: power up
Last software reset data not available
**Driver 0: position 1263870, 837.0 steps/mm, assumed not present**
Moves scheduled 18, completed 18, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 23.7V
MCU temperature: min 13.1C, current 26.1C, max 26.6C
Ticks since heat task active 4, ADC conversions started 4524398, completed 4524397, timed out 0
Last sensors broadcast 0x00000002 found 1 7 ticks ago, loop time 0
CAN messages queued 54219, send timeouts 0, received 58848, lost 0, free buffers 36

@droftarts

I copied this syntax from the article by @dc42 "Converting the E3D Tool Changer to Duet 3 with Hemera Tools (Part 2). In his piece, he was replacing 2 extruders with 2 Hemera's with Tool Boards.

Is this incorrect?

; Hemera motors
M569 P22.0 S0                 ; set tool 2 extruder direction
M569 P23.0 S0                 ; set tool 3 extruder direction
M584 E3:4:22.0:23.0           ; set extruder drives

@fcwilt Only 2 extruders in use on this machine.

@dc42 Thank you, I did locate the intermittent switch. I should have looked at as a separate issue but I am rather frustrated at the core issue and foolishly assumed they were related.

The core problem I am having is when I am using the Hemera's with the tool boards. If I select a tool, the Hemera heats up as expected. Using the web interface, I select "Extrude/Retract" and specify a set length and feedrate and select it, but instead of the extruder motor running as expected, Drive 1 on the 6HC board runs, causing the entire tool assembly to move diagonally. If I select the opposite, say retract instead of extrude, the same motor runs the opposite way.

I tried to run Tool1 last night and the lock motor ran instead... rather unfortunately. Aside from being quite frustrating, I hate having to have to bother folks in the form with this stuff, but I am now short on ideas and fingernails

Any thoughts?

Hello @Hiroaki... I have had this issue myself a few times. The advice here did solve it; but I had to do it a couple of times. Re-flashing the firmware more than once might be necessary. I also found that in BOSSA, using the setting "erase all" seemed to yield the best results. Good luck to you!