Pad 7 refuses to connect to host when ADXL is enabled

No matter that I do the pad flat out refuses to connect with the host (SV07 Plus) if I have mcu CB1, the ADXL, and Resonance lines active in the config. If I comment them all out the pad will instantly connect and work perfectly. Except the ability to perform IS...

I have reimaged the pad 7 to latest image release and reflashed the MCU, Twice. Tried older versions of Klipper and current. Ran older image versions for the CB1 form BTT Git page, Swapped to my spare main board same issue.
Switched USB ports and tried both methods to com to the MCU

serial: /dev/serial/by-path/platform-5200000.usb-usb-0:1.3:1.0-port0 /dev/serial/by-path/platform-5200000.usb-usb-0:1.3:1.0-port0
And
serial:/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

Same result.

Ensured spidev1.1 is active in the ambianENV.txt file along with overlays=mcp2515 and overlays=spidev1_2.

Checked the switches and flipped to the left. Had the ADXL connected at boot and not connected. Still nothing. just sits there "Klipper reports: STARTUP"

Printer is not ready The klippy host software is attempting to connect. Please retry in a few moments.Printer is not ready The klippy host software is attempting to connect. Please retry in a few moments.

[mcu CB1]
serial:/tmp/klipper_host_mcu

[adxl345]
cs_pin: CB1:none
spi_bus: spidev1.1
axes_map: z,y,-x

[resonance_tester]
accel_chip: adxl345
probe_points: 150, 150, 20
accel_per_hz:75
min_freq:1
max_freq:100
max_smoothing:0.2
hz_per_sec:0.5

Start by reproducing the connection failure with the shown [mcu CB1], [adxl345], and [resonance_tester] configuration, then compare startup behavior with those sections commented out. Use the listed serial paths, SPI settings, and Klipper startup state as the investigation context; done means the Pad 7 connects reliably with ADXL and resonance testing enabled.

Written by the indexing model from the issue text.