BTT SPI problems from WOWElectronics continued

General Discussion
17

We need to set some ground rules if I, or anybody, am EVER going to be able to help you.

  1. Clearly explain your system. This means list the printer type, main controller type, driver type (which is critical in this case), host type and host to main controller connection.
  2. Include your klippy.log.
  3. Concisely articulate your primary concern and list any observations that you think may be useful - nothing more. NOTE: these three points are what you should have done when you first started this thread in “General Discussion”.
  4. When asked a question, answer it clearly. If you don’t understand what is being asked request an explanation. Don’t go off on a tangent.
  5. When a suggestion is made do that and nothing else. Report your observations and don’t add anything. Always attach the latest klippy.log; if it’s too big to attach then .zip it and attach the compressed file.
  6. Wait for a response. Don’t make any changes until you are instructed to do so.

I’m doing this because the klippy.log you just sent clearly shows that you just added a new printer.cfg file that you got from somewhere.

Here is the original klippy.log you attached, I’ve marked it with “6” as that is the entry in this thread it was posted: klippy_Gene_6.log (161.9 KB)

Here is the second klippy.log you attached, I’ve marked it with “16” as that is the entry in this thread where it was posted: klippy_Gene_16.log (24.9 KB)

Your [mcu] and '[printer]` statements from the first one:

[mcu]
serial = /dev/serial/by-id/usb-Klipper_stm32f429xx_3D004C001050325635383820-if00

[printer]
kinematics = cartesian
max_velocity = 600
max_accel = 10000
max_z_velocity = 5
max_z_accel = 100

Your [mcu] and '[printer]` statements from the second one:

[mcu]
serial = /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
restart_method = command

[printer]
kinematics = cartesian
max_velocity = 500
max_accel = 5000
max_z_velocity = 10
max_z_accel = 200

In the first klippy.log, your stepper_x pins are defined as:

[stepper_x]
step_pin = PF13
dir_pin = PF12
enable_pin = PF14

In the second klippy.log, your stepper_x pins are defined as:

[stepper_x]
step_pin = PC2
dir_pin = !PB9
enable_pin = !PC3

In the first klippy.log, you have [tmc5160 stepper_... statements that we were discussing. In the second klippy.log, there are none.

In the second klippy.log there are a number of [bed mesh,,,] statements that are not present in the first.

I can go on but it’s just going to piss me off even more.

If you actually want help and this is not some perverse form of entertainment for you, then I suggest that you start a new thread in “General Discussion” and follow the guidelines I have set out above to the letter (including providing the information and klippy.log requested) and follow the spirit of the guidelines; that you will make it easy for me or somebody else to help you.

My days of shooting at moving targets from a galloping horse with a blindfold on are over.