Thank you for the detailed explanation. I understand what you're saying and appreciate that you guys (and gals?) put the forethought in during the R&D phase to avoid issues like these down the road for your customers.

So, back to my problem... do you know if there will be a similar type of "quick (or even automated) disconnect" type system for the duet can-fd ecosystem?

I'm sad to have wasted the money on this turd but such is the nature of the sunk cost fallacy. For that reason, I'd be eager to purchase something similar (or better) that is compatible with the Duet3 can-fd family, and I'm sure I'm not alone, given the size of your loyal and enthusiastic fan base

I have a hermit crab can bus unit that I can't seem get to work (it takes the klipper firmware without issue and appears to respond to the bus query script on my R-Pi, but the script fails to identify it on the bus) and their support never bothers to respond (thanks for the quick replies, btw... very refreshing in comparison).

So, if this is at all a possibility to request as a feature, that would be outstanding and I'd be willing to donate my hermit crab in the name of getting that firmware change created, if it would help at all...?

(it is essentially a paperweight collecting dust at this point, so I'd be happy to donate it in the name of "science" )

@t3p3tony Is the hardware incompatible or the software?
i.e. the btt hermit crab can can be flashed with klipper firmware... would it be possible to flash it with a firmware that is compatible with duet3d in order to achieve quick tool-change ability using duet hardware? that would be the best of both worlds

I am trying to get my Duet2 wifi to control an idex printer and realized I am one stepper driver short with the mainboard.
I ordered the Duex5 expansion but I am not sure if that is the correct approach to simply adding another output (I did search but was a bit confused by the info I was reading on the Duex5, so my apologies for the dumb question.)
Can anyone point me the right direction as far as documentation or a guide to making a Duet2 (wifi) control an idex printer? Need a total of 6 stepper drivers to make it work as intended.

Thanks!

Does anyone know if the Duet3 can connect to (and control) the BTT Hermit Crab and, if so, where I can find any documentation online to help me get that working?

Thank you in advance!

I have tried 3 different cables (which I tested on a duet 3 and transferred a file to it just fine, so it's not a cable issue)
I have also tried every combination of baud rate and flow control imaginable, all with the same result...

M115<CR>
Error: Bad command: [0x11]M115
ok
M115<CR>
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
M115
Error: Bad command: [0x11]M115
ok
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
M997 S1
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write error
ok

So this is a strange one. I have a Duet2 wifi that has been working great for a couple months.
Go away for a couple weeks for work and when I get back, it isn't connected to my wifi network anymore. I go through the steps I followed to headlessly get it online and configured when I set it up about 6 months ago, only now I am getting a strange error about SPI that makes no sense to me and I can't seem to find any relevant info/solutions online.

Please see below and (hopefully) tell me I'm an idiot and the culprit is something silly that I skimmed right over in all the different procedures (upgrade from web, sd card upgrades-a-plenty, firmware reflash with SAM-BA 2.17 which appears to succeed but apparently does not, access point mode... etc)

Any assistance would be greatly appreciated because, at this point, I think I have attempted every procedure / suggestion that exists on the world-wide-information-super-interwebs, and my google-fu isn't 'weak' by any stretch but I have come up empty at the end of my journey.

Thanks in advance

m122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: **********************
Used output buffers: 1 of 24 (12 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 73544 of which 12 recycled
Never used RAM 16984, free system stack 193 words
Tasks: NETWORK(ready,7.5%,517) HEAT(delaying,0.0%,386) Move(notifyWait,0.1%,364) MAIN(running,92.4%,439) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:12:38 ago, cause: power up
Last software reset at 2021-12-20 12:08, reason: User, GCodes spinning, available RAM 12208, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 18.8, current 19.2, max 19.7
Supply voltage: min 1.7, current 1.8, max 1.8, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 0.38ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 30.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is ready with "m122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.19ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

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

m587
Failed to retrieve network list: WiFi module is disabled
ok

m552 s0
ok

m587
Failed to retrieve network list: another SPI transfer is pending
ok

m587 S"ssid" P"password"
Error: M587: Failed to add SSID to remembered list: another SPI transfer is pending
ok

m588 S"*"
Error: M588: Failed to reset the WiFi module to factory settings: another SPI transfer is pending
ok

m552 S1
Turn off the current WiFi mode before selecting a new one
ok

M552 S0
ok

M552 S1
Turn off the current WiFi mode before selecting a new one
ok

M552 S-1
WiFi module stopped
ok

M552 S1
ok

M588 S"*"
Error: M588: Failed to reset the WiFi module to factory settings: another SPI transfer is pending
ok

M589
Error: M589: Failed to retrieve own SSID data: another SPI transfer is pending
ok

M589 S"ssid" P"passworddd" I2.2.2.2

Error: M589: Failed to configure access point parameters: another SPI transfer is pending
ok