bigtreetech / HermitCrab

68 stars 11 forks source link

Error : "Endstop and stepper must be on the same mcu" while using bltouch #6

Closed grimlokason closed 2 years ago

grimlokason commented 2 years ago

Hello,

I'm getting the following error on fluiddpi : Endstop and stepper must be on the same mcu

My config for my ender 3 with the hermit crab canbus on usb :

# This file contains pin mappings for the stock 2020 Creality Ender 3
# V2. To use this config, during "make menuconfig" select the
# STM32F103 with a "28KiB bootloader" and serial (on USART1 PA10/PA9)
# communication.

# If you prefer a direct serial connection, in "make menuconfig"
# select "Enable extra low-level configuration options" and select
# serial (on USART3 PB11/PB10), which is broken out on the 10 pin IDC
# cable used for the LCD module as follows:
# 3: Tx, 4: Rx, 9: GND, 10: VCC

# Flash this firmware by copying "out/klipper.bin" to a SD card and
# turning on the printer with the card inserted. The firmware
# filename must end in ".bin" and must not match the last filename
# that was flashed.

# See docs/Config_Reference.md for a description of parameters.

[stepper_x]
step_pin: PC2
dir_pin: PB9
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: ^PA5
position_endstop: 0
position_max: 235
homing_speed: 50

[stepper_y]
step_pin: PB8
dir_pin: PB7
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: ^PA6
position_endstop: 0
position_max: 235
homing_speed: 50

[stepper_z]
step_pin: PB6
dir_pin: !PB5
enable_pin: !PC3
microsteps: 16
rotation_distance: 81
endstop_pin: probe:z_virtual_endstop
position_max: 250

[heater_bed]
heater_pin: PA2
sensor_type: EPCOS 100K B57560G104F
sensor_pin: PC4
control: pid
# tuned for stock hardware with 50 degree Celsius target
pid_Kp: 54.027
pid_Ki: 0.770
pid_Kd: 948.182
min_temp: 0
max_temp: 130

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

[printer]
kinematics: cartesian
max_velocity: 300
max_accel: 3000
max_z_velocity: 5
max_z_accel: 100

########################

[mcu HermitCrab]
#canbus_uuid: 0e0d81e4210c
serial: /dev/serial/by-id/usb-Klipper_stm32f072xb_23001D001657434233343820-if00

[adxl345]
cs_pin: HermitCrab: PB12
spi_software_sclk_pin: HermitCrab: PB13
spi_software_mosi_pin: HermitCrab: PB15
spi_software_miso_pin: HermitCrab: PB14
axes_map: y,z,-x
#   The accelerometer axis for each of the printer's x, y, and z axes.
#   This may be useful if the accelerometer is mounted in an
#   orientation that does not match the printer orientation. For
#   example, one could set this to "y,x,z" to swap the x and y axes.
#   It is also possible to negate an axis if the accelerometer
#   direction is reversed (eg, "x,z,-y"). The default is "x,y,z".
#rate: 3200
#   rates: 3200, 1600, 800, 400, 200, 100, 50, and 25

[resonance_tester]
accel_chip: adxl345
probe_points:
    100,100,20  # an example

[extruder]
step_pin: HermitCrab: PA6
dir_pin: !HermitCrab: PA7
enable_pin: !HermitCrab: PA5
microsteps: 16
rotation_distance: 3.45
nozzle_diameter: 0.600
filament_diameter: 1.750
heater_pin: HermitCrab: PA2
sensor_type: EPCOS 100K B57560G104F
sensor_pin: HermitCrab: PA1
control: pid
pid_Kp: 21.527
pid_Ki: 1.063
pid_Kd: 108.982
min_temp: 0
max_temp: 250

[tmc2209 extruder]
uart_pin: HermitCrab: PB0
run_current: 0.650
hold_current: 0.500
stealthchop_threshold: 999999

[fan]
pin: HermitCrab: PA3

[heater_fan hotend_fan]
pin: HermitCrab: PA4
heater: extruder
heater_temp: 50.0

#[neopixel hotend_rgb]
#pin: HermitCrab:PA8
#chain_count: 2
#color_order: GRB
#initial_RED: 0.5
#initial_GREEN: 0.5
#initial_BLUE: 0.5

[bltouch] #https://www.thingiverse.com/thing:4757657
sensor_pin: ^HermitCrab:PB2
control_pin: HermitCrab:PB1
x_offset: -35
y_offset: -6.5
z_offset: 0
probe_with_touch_mode: true

#[bed_mesh]
#speed: 120
#horizontal_move_z: 5
#mesh_min: 10,10
#mesh_max: 190, 185
#probe_count: 5,5

[safe_z_home]
home_xy_position: 120,100 # Change coordinates to the center of your print bed
speed: 50
z_hop: 10                 # Move up 10mm
z_hop_speed: 5

What am i doing wrong ?

grimlokason commented 2 years ago

My bad,

The fluiddpy was not up to date. update done, and new firmware flashed and everything is ok !