PIN is not a valid PIN name on MCU

General Discussion
1

Basic Information:

Printer Model: Voron 2.4 R2 pro plus (Formbot kit)
MCU / Printerboard: BTT Manta m8p + cb1 and EBB SB2209 (RP2024)
Host / SBC
klippy.log

Hello everyone,

It’s me again. After two hours of troubleshooting, I’m turning to you again.

I currently have the following error message:
Pin ‘PC10’ is not a valid pin name on mcu ‘mcu’

I checked and the pin fits:

X Stepper on Motor1 (B Motor)

[stepper_x]
step_pin: PE2
dir_pin: PB4
enable_pin: !PC11
microsteps: 16
rotation_distance: 40
full_steps_per_rotation:200 #set to 400 for 0.9 degree stepper
endstop_pin: EBBCan:gpio24
position_min: 0
##--------------------------------------------------------------------

position_endstop: 350
position_max: 350

##--------------------------------------------------------------------
homing_speed: 25 #Max 100
homing_retract_dist: 5
homing_positive_dir: true

Make sure to update below for your relevant driver (2208 or 2209)

[tmc2209 stepper_x]
uart_pin: PC10
interpolate: True
run_current: 0.8
sense_resistor: 0.110
stealthchop_threshold: 0

…
klippy.log (260.6 KB)

2

Take it easy. Posting three topics for the same problem won’t help :wink: Old men, don’t rush. You’ll probably get an answer in the end.

3

What options did you use for make config when you were flashing the Klipper Firmware to your Manta M8P?

I presume you’re using the internal CAN bus, so it should look something like:

image
image786×533 52.2 KB

4

From your log:

[mcu]
serial = /tmp/klipper_host_mcu

[mcu EBBCan]
canbus_uuid = afc0a134dc27

[mcu CB1]
canbus_uuid = 500ab1cfdcda

Reason for your error:

  • Your [mcu] is defined as “host MCU” but should be your Manta board and either be connected via CAN (have a canbus_uuid) or via USB-serial and have a board’s serial
  • Your [mcu CB1] is effectively your “host MCU” and should be connected via serial = /tmp/klipper_host_mcu but is defined as “real” MCU with a canbus_uuid
5

Thanks for the feedback. And yes, it looks exactly the same

6

Thanks for the feedback

Sorry, I don’t get it (mechanical engineer has no idea about software and programming, that has just been confirmed)

I’ve tried several configurations and nothing has worked.

I currently have the error:
mcu ‘EBBCan’: Unable to connect

Can you perhaps tell me what needs to be in my printer.cfg, my manta-m8p-v1.1.cfg and my btt-ebb-sb2209.cfg regarding the mcu. I’ve attached the log again.

Or did I do something wrong when flashing?

Or do you know someone in Germany, in the Ingolstadt or Regensburg area, who can help me? I would then drive over with my printer, I am so desperate right now

klippy.log (502.9 KB)

7

Since I do not know what you have built and what you intended to built:

  1. Read through Klipper Architecture / Ecosystem to get some understanding how Klipper works
  2. Get the general config here for the Manta: GitHub - bigtreetech/Manta-M8P
    • Note that there are different version of the M8P - choose the correct one
  3. Get the general config for the EBB here: EBB/EBB SB2209 CAN (RP2040)/sample-bigtreetech-ebb-sb-rp2040-canbus-v1.0.cfg at master · bigtreetech/EBB · GitHub
  4. Follow the setup instructions for Klipper here: Installing Klipper with KIAUH
    • Build the respective firmwares according to the connection scheme you want to use (FOLLOW CLOSELY the instructions on top of the cfg files)
    • For the EBB only CAN is applicable
    • For the M8P both USB or CAN could be applicable - You need to choose one according to your wiring
    • Assuming you go by CAN only, obtain your canbus_uuid according to CANBUS - Klipper documentation
  5. Flash both boards with their respective firmware
  6. The representation of the M8P and EBB in your printer.cfg should finally look like (still assuming CAN only):
    [mcu] # This is the M8P
canbus_uuid: 4b94c57be78e #YOURS WILL BE DIFFERENT - CHANGE IT  TO MATCH

[mcu EBBCan]
canbus_uuid: 2f0b1ce14660 #YOURS WILL BE DIFFERENT - CHANGE IT  TO MATCH
  7. Forget about the serial = /tmp/klipper_host_mcu. You likely do not need it, and if you will know.
8

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