PITB fysetc v2, tmc spi 'stepper_x' register GLOBALSCALER

[ejhones]

Basic Information:

Printer Model: voron
MCU / Printerboard: fly-dp5
Host / SBC btt pi2
klippy.log
klippy.log (49.2 KB)
pitb (1).cfg (8.5 KB)

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:

… only reading temps, STEPPER_BUZZ STEPPER=stepper_x → Unable to write tmc spi ‘stepper_x’ register GLOBALSCALER
at 48v or/and 24v same at usb-serial or usb-can conection,
no fans only temp. i tink is wrong pins ? has a way to identify the pins.

[ejhones]

klippy (3).log (189.4 KB)

with update from,

Add spi0e bus for rp2040, used on pitb v2 by fysetc

thank you very much for sharing

I still have the error, I would like to ask the more experienced to analyze the log.
I believe this board is burned.
thanks in advance.

[Sineos]

@ejhones

I still have the error, I would like to ask the more experienced to analyze the log.

Please confirm that you have really pulled this change correctly. The process you needed to follow:

1. Pull in the changes of PR #6683 into your local Klipper
2. Build a new RP2040 firmware
3. Flash the firmware
4. Restart Klipper

On a unrelated sidenote:
You a running 0.8 A stepper motors off a board that is designed in hardware to run steppers up to 6 A.
This means the drivers will be severely limited in controlling the steppers current.

This is not related to the error you are having, but overall the rated current of the drivers should halfway match the rated current of the stepper motors.
As such, products like the PITB can be considered as unsuitable for use in “average” 3D printers.

[ejhones]

klippy (4).log (182.3 KB)

Thank you, yes, very good notification, there are so many variables that we lose in the simplest ones. Note that in the first one I did not update the pitb, but in the second one everything is updated. It is under test, so there is no power to the motors, I think it is broken, there is no fan on the two pins gpio0 and gpio18, and the motors ffffff*f, only temperatures, other connections not tested, I have already tested on USB, USB CAN, on CAN with 3 different CAN boards, all without fan, only temp and endstops. What do you think? I really wanted this to work.

[Sineos]

The version as shown for the mcu PITB indicates that you have not flashed a firmware with the relevant changes from Add spi0e bus for rp2040, used on pitb v2 by fysetc by KoiosLabs · Pull Request #6683 · Klipper3d/klipper · GitHub to your PITB board.

[ejhones]

sorry, I ended up confusing you.
I added the image to reinforce your information,

@ejhones

Note that in the first one I did not update the pitb, but in the second one everything is updated

It’s really very easy to get lost.

ejhoness/FYSETC-PITB/blob/main/V2.0/help2.txt

[Sineos]

There seem to have been some further updates to this Pull Request. Not sure how relevant they might have been as I cannot compare them as they have been force pushed and squashed.

Please update the PITB again from the latest KoiosLabs and flash again.

Attach a new klippy.log if the error persists.

[ejhones]

my pitbv2 board is broken.