Invalid ads1220 reset state

[strangelove]

Basic Information:

Printer Model: Homebrew CARTESIAN, based on AnetA6
MCU / Printerboard: BTT Octopus 1.1
Host / SBC: Octoprint

I want to use a load cell witch is also used by Anycubic printers in my setup. I’m using a Ads1220 to read out the cell.

The Printer crashes with

Internal error during ready callback: Invalid ads1220 reset state (got [0xff, 0xff, 0xff, 0xff] vs [0x0, 0x0, 0x0, 0x0]).
This is generally indicative of connection problems
(e.g. faulty wiring) or a faulty ADS1220 chip.

This was an also an issue in a previous topic :

How to use two SPI busses with CB1 on Manta M8P

Reversed MOSI/MISO and got: Klipper meldet: SHUTDOWN Internal error during ready callback: Invalid ads1220 reset state (got [0xff, 0xff, 0xff, 0xff] vs [0x0, 0x0, 0x0, 0x0]). This is generally indicative of connection problems (e.g. faulty wiring) or a faulty ADS1220 chip. Reversed MOSI/MISO again and keeps the same. May I’ve roasted my ADS already?

It was said then that this was a bug and should be fixed in the newest commit, but im using the newest one.

What is further interesting is that everything works fine if i have a clock missmatch from 8MHz instead of the intended 12MHz, but this then causes other issues:

Strange behavior on XY-movement after update

Basic Information: Printer Model: Homebrew coreXY, heavily based on HevOrt MCU / Printerboard: BBT Octopus 1.1 klippy.log Hi, i’m new here, this is my first topic, english is not my mother language, so I’d like to ask for your patience. My issue started with an update of MCU Firmware, coming from v0.10.x-xx and went to v0.12.0-98. I’m on MainsailOS and performed the updating, compiling and flashing with KIAUH. It took some runs but after some fiddling it carried out and i have the same v…

So my question is if this is some issue with spi communication e.g. noise or misconfiguration, or still indeed a bug.

Thanks in Advance!

[cardoc]

Welcome to the forum!

Please review the template form for new issues.

A klippy.log is essential begin to understand what is going on.

[EddyMI3D]

@strangelove

Host / SBC: Octoprint

BTW: OctoPrint is the frontend you use
SBC stands for Single Board Computer - like Raspberry Pi etc.

Depending on how you installed OctoPrint, you can find the klippy.log here:

• On a OctoKlipper install:/tmp/
• On a KIAUH install: /home/pi/printer_data/logs/

[strangelove]

klippy.log (63.0 KB)

[cardoc]

@strangelove

What is further interesting is that everything works fine if i have a clock missmatch from 8MHz instead of the intended 12MHz, but this then causes other issues:

This is really outside my sphere of expertise but while waiting for better advice I’d slow down the SPI data rate and see if that helps. Your ads1220 is running at 20 Hz, spi_speed = 128000 should be more than enough,

[strangelove]

Good call, but unfortunatly i tried it already without sucess