Duet Ethernet won't detect new accelerator board

Before you get lost in the text below, I want to squeeze in a thanks for reading this and hope you can find errors (otherwise my board is bad).

I've been following the instructions to set up an Adafruit LIS3DH accelerometer on my DuetEthernet. I've been running 3.3 up till now, then installed 3.4b3. I have a temp daughterboard so made my cable according to that (along with some grumbling because I could NOT find the daughterboard pinout anywhere so had to do it the hard way with a DMM. )

When I manually attempt to run M955 P0 C"spi.cs4+spi.cs3" S1000 to set up an accelerometer, I get 'accelerometer not found on specified port'.
After double-checking my wire routing, I put an oscilloscope on all the pins of the temp daughterboard's Output connector. There is regular bus data going on, including activity on CS1 and CS2 when the PT100 sensors are read. But CS3 and CS4 don't change when I send the M995 command. I hope my Duet board isn't damaged! It might be the firmware, see below.

Getting the new firmware up (3.4b3) has been an uncertain process. I finally got the latest firmware to bootup without a wifi-error AFTER I discovered the .json editor, which is how I got the board to bootup.
Problems:
...3.4b3 web control is not showing either tool on the dashboard, just the bed. the temp graph however has three heaters in the legend (I have a dual extruder). so something is broken.

I am not familiar with the .json thing except to know it is text config file similar to the role of .xml, so I don't know what the role of the .json files are, maybe data for a bootloader?
The only way I could find to configure 3.4b3 for a Duet Ethernet was to use the editing tool but that also forces you to make an entire config file and I want to keep my original + neccessary edits. I did select to 'reuse' my original config.g file but the result had problems and I still crafted the config.g file by hand.

Config.g file is attached, along with config.json file. Below is the diagnostic report form the Duet board.


M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6JKDD-3SN6J-TVWHG
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 69888 of which 584 recycled
Never used RAM 20068, free system stack 150 words
Tasks: NETWORK(ready,26.0%,231) HEAT(delaying,0.1%,330) Move(notifyWait,0.1%,317) MAIN(running,73.9%,503) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:05:09 ago, cause: software
Last software reset at 2021-09-10 21:02, reason: User, GCodes spinning, available RAM 20308, 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
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 32.7, current 33.2, max 36.0
Supply voltage: min 24.1, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 150194, standstill, SG min/max not available
Driver 1: position 150194, standstill, SG min/max not available
Driver 2: position 150194, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, 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: 2021-09-10 22:07:28
Cache data hit count 4294967295
Slowest loop: 22.02ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.0ms, write time 8.7ms, max retries 0
=== Move ===
DMs created 83, maxWait 171ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1, completed moves 1, hiccups 130458, 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 = 0 -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 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 66.95ms; fastest: 0.02ms
Responder states: HTTP(2) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

I suggest you post at [forum.duet3d.com] because that's where our support engineers will read your post. Include photos of the accelerometer wiring.

Have you allowed for the fact that the daughter board routes CS3 and CS4 from the underside to the positions corresponding to CS1 and CS2 on the top?

The json file is only used if you want to re-import the configuration to the online tool. It is not used by the firmware.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

thanks for the Saturday morning reply! I will repost on the other forum as you suggest.
Yes, I accounted for the remapping of CS3 and CS4 on top of CS1 and CS2. Actually, I didn't rely on remapping, too dumb to realize why that was even mentioned so I ended up tracing the Input to Output connectors by hand (with DMM).