sergio
November 22, 2024, 9:31pm
1
Fill out above information and in all cases attach your klippy.log file 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
Hello, very good, I have a configuration problem when I load a model in Mainsaill it loads out of place I attach the image and the printer cfg if necessary, I await instructions, very grateful in advance
…
klippy (2).zip (2.1 KB)
sergio
November 22, 2024, 11:34pm
2
I have attached klippy log and printer.cfg
1 Like
How are your printer settings here:
BTW:
The klippy.log does not seem complete. Did you cut something off?
sergio
November 23, 2024, 11:09am
4
Are you referring to Cura Ultimaquer or Mainsail?
sergio
November 23, 2024, 11:18am
6
klippy (4).log (6.8 KB)
Here you have the klippy.log and the machine configurationprinter (1).cfg (2.4 KB)
In your printer config, the print area is 235 x 235
In your Cura settings you have 330 x 330.
What is the real area of the print bed. That area is decisive for the config and the slicer.
In your klippy.logs there are only error messages, but no config data. Where is that gone?
sergio
November 23, 2024, 11:29am
8
330 Y.330X 400 Z
printer (1).cfg (2.4 KB)klippy (4).log (6.8 KB)
meteyou
November 23, 2024, 12:57pm
9
there are multiple “issues”… your klippy.log doesn’t show a successful start, so mainsail only use “fallbacks”. the fallback for the gcodeviewer is:
min => 0
max => max from the gcode file
so it will be every time at the right/back end of the buildplate as long klipper is not starting, because mainsail cannot read a buildplate size.
next is the wrong axis sizees in your printer.cfg (as @EddyMI3D already wrote above)… so it will be also “out of center”.
sergio
November 23, 2024, 1:14pm
10
I have corrected elprinter.cfg and it follows the decent model. Can you check to see if it is correct???printer (1).cfg (2.4 KB)
meteyou
November 23, 2024, 1:20pm
11
i don’t know what you fixed in this config, but it looks like the exact same wrong printer.cfg as before.
the klippy.log would be always a better option, because we see the “rendered” config. also the serial paths and printer sections looks wrong and multiple time in this config file.
with this config, your printer should not start and i think you should fix that first and when your printer is running, you can double-check the gcodeviewer…
sergio
November 23, 2024, 1:27pm
12
[stepper_x]
[stepper_y]
[stepper_z]
I have modified the maximum positions, paste the detail
meteyou
November 23, 2024, 2:02pm
13
this is a screenshot from the file above:
the file you uploaded is an other/old one…
sergio
November 23, 2024, 5:44pm
14
[quote=“meteyou, post:13, topic:20212”]klippy (4).log (6.8 KB)
type or paste code here [include mainsail.cfg]
[virtual_sdcard]
path: /home/biqu/printer_data/gcodes
on_error_gcode: CANCEL_PRINT
[heater_fan heatbreak_cooling_fan]
pin: PC7
[heater_fan controller_fan]
pin: PB15
[fan]
pin:PC6
[mcu]
serial: //dev/serial/by-id/usb-Klipper_stm32g0b1xx_1A0053000350415339373620-if00
[printer]
kinematics: cartesian
max_accel: 3000
max_z_velocity: 5
max_z_accel: 100
max_velocity: 1000
[stepper_x]
step_pin: PB13
dir_pin: !PB12
enable_pin: !PB14
microsteps: 16
rotation_distance: 40
endstop_pin: ^PC0
position_endstop: 0
position_max: 330
homing_speed: 50
[tmc2209 stepper_x]
uart_pin: PC11
uart_address: 0
run_current: 0.580
stealthchop_threshold: 999999
[stepper_y]
step_pin: PB10
dir_pin: !PB2
enable_pin: !PB11
microsteps: 16
rotation_distance: 40
endstop_pin: ^PC1
position_endstop: 0
position_max: 330
homing_speed: 50
[tmc2209 stepper_y]
uart_pin: PC11
uart_address: 2
run_current: 0.580
stealthchop_threshold: 999999
[stepper_z]
step_pin: PB0
dir_pin: PC5
enable_pin: !PB1
microsteps: 16
rotation_distance: 8
endstop_pin: ^PC2
position_endstop: 0.0
position_max: 400
[tmc2209 stepper_z]
uart_pin: PC11
uart_address: 1
run_current: 0.580
stealthchop_threshold: 999999
[extruder]
step_pin: PB3
dir_pin: !PB4
enable_pin: !PD1
microsteps: 16
rotation_distance: 33.500
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: PC8
sensor_type: EPCOS 100K B57560G104F
sensor_pin: PA0
control: pid
pid_Kp: 21.527
pid_Ki: 1.063
pid_Kd: 108.982
min_temp: 0
max_temp: 250
[tmc2209 extruder]
uart_pin: PC11
uart_address: 3
run_current: 0.650
[heater_bed]
heater_pin: PC9
sensor_type: EPCOS 100K B57560G104F
sensor_pin: PC4
control: pid
pid_Kp: 54.027
pid_Ki: 0.770
pid_Kd: 948.182
min_temp: 0
max_temp: 130
[heater_fan heatbreak_cooling_fan]
pin: PC7
[heater_fan controller_fan]
pin: PB15
[fan]
pin: PC6
[mcu]
#serial: /dev/serial/by-id/usb-Klipper_Klipper_firmware_12345-if00
serial: //dev/serial/by-id/usb-Klipper_stm32g0b1xx_1A0053000350415339373620-if00 #$# - Sergio's information
[printer]
#kinematics: corexy #$# - Sergio's printer
kinematics: cartesian
max_velocity: 300
max_accel: 3000
max_z_velocity: 5
max_z_accel: 100
[board_pins]
aliases:
# EXP1 header
EXP1_1=PB5, EXP1_3=PA9, EXP1_5=PA10, EXP1_7=PB8, EXP1_9=<GND>,
EXP1_2=PA15, EXP1_4=<RST>, EXP1_6=PB9, EXP1_8=PD6, EXP1_10=<5V>
# See the sample-lcd.cfg file for definitions of common LCD displays.
I have removed the tx pin arguments and modified the maximum positions of [stepper_y]
330 X Y 330 Z 400
[stepper_x]
klippy (4).log (6.8 KB)
Sergio,
In our separate conversation I told you EXPLICITLY klippy.log.
This is the most important file and provides the information that will help others help you.
1 Like
Please attach a new klippy.log. This one is 3 days old.
sergio
November 23, 2024, 6:34pm
18
I downloaded it, I just reviewed it and it is indeed from November 20, how do I update it?
I have downloaded it several times and it still appears November 20
And these 111 lines is all you get?
sergio
November 23, 2024, 6:40pm
20
And these 111 lines are all you get? Also tell you that I have system updates, I don’t know if this is why incorrect information is displayed.
