Fysetc portable input shaper adxl345: spi must be on same muc

General Discussion
1

Basic Information:

Printer Model: ender 3 s1
MCU / Printerboard: stock, f401
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

i did all what in the web, but still get this…

image
image1920×1080 373 KB

i did like this: GitHub - FYSETC/FYSETC-PortableInputShaper: Portable Input Shaper(PIS)

see also this file:
klipper.txt (54.5 KB)
change to .uf2

also i included pis.cfg in mainsail

image
image1920×1080 236 KB

what to do?

2

Where is the original Klippy.log?
Please attach this and not any other formats or logs.
Your attachment is the firmware if I’m not wrong.

The FYSETC-link has the SPI-bus commented out. Did you check this as well?
What happens if you change it to

spi_bus: PIS:spi1a

?
I have similar accelerometers where I did not have any issues in the past. And it has the spi_bus commented out as well

3

Actually there are two issues:


[adxl345]
...
spi_bus: spi1a
spi_software_sclk_pin: PIS:gpio10
spi_software_mosi_pin: PIS:gpio11
spi_software_miso_pin: PIS:gpio12
...

[resonance_tester]
accel_chip: adxl345 usbadxl
  1. You are mixing hardware SPI and software SPI. The Fysetc works only with software SPI → remove spi_bus: spi1a
  2. You have not assigned a unique name to the chip, but you try to access the chip under an unique name → modify accel_chip: adxl345 usbadxl to accel_chip: adxl345
1 Like
4

I tried to comment in and out, nothing happen…

5

This is usb, why remove it? This is the original file from fysetc…
But if you think it will help, I’ll try. I want to understand why?

6

If you want to access it via its custom name you have to declare the name before:

[adxl345 usbadxl]

And then you can access it with

[resonance_tester]
accel_chip: usbadxl

Or keep the defaults like @Sineos suggested.

7

Understand. I’ll check and reply if working or not.
Why their default file like this i don’t know…

8

image
image1920×1080 236 KB

i dont have red error in mainsain page, but i have this…

image
image1920×1080 314 KB

9

What kind of cable are you using and how long is it?
The description in the console already points you towards a solution.

10

data cable
1 meter

11

You mean an USB-C to USB-A cable or what? Is it shielded or just cheap?

12

Isn’t it SPI wiring to the chip? That’s what it looks like from the screen shots.

1 Like
13

This is an odd error for this type of device.

Typically, it would occur when there is a wiring problem between the ADXL chip and the MCU that controls it.
In the case of the “integrated” ADXLs, i.e. the ADXL is on the same board as the controlling MCU, this should be pretty much impossible unless the board is defective.

14

You are right. I must have been too sleepy already. :frowning:
The PCB is connected as a separate MCU via the USB cable and not the accelerometer itself.
Maybe its a problem on the PCB then? Bad soldering or anything like that?

15

So what to do?

16

I cannot think of any other reason but a defect board.

17

I put down in printer.cfg the include pis.cfg
Instead of top of the file, it seems to work…
And reflashed the pis and numpy on raspberry pi…

1 Like
18

Interesting. Thanks for sharing your solution.

In fact, moving around the settings should have no impact (I’m using numerous such includes since I have a ton of different IMUs), so I would guess the update of the rest could have made the difference.

In any case, it is valuable to know that this could cause the Invalid adxl345 id (got 0 vs e5) error.

19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.