Help required for Klipper error with Ender 3 and BTT RRF Main Board

[DesP]

Hi all

I have purchased a second hand Ender 3 printer with a BTT E3 RRF Main board that has been flashed with klipper.

The printer has a BL Touch installed.

I have set up a Raspberry Pi 4b with MainsailOS and connected it to the printer. I am using a printer.cfg provided by the seller (he would not sell the rpi) that has been modified slightly to cater for different path.

Initially the printer.cfg had a significant number of errors that I gradually fixed with formatting, but as soon as they were fixed a batch of errors came up with lines in the "DO NOT EDIT" section. Note that the line numbers in the error are not the same as in printer.cfg. These are the lines under the [bed_mesh_default]

Not that the printer does not move at all when I turn it on, but I can see an led lit in the BL Touch.

I have attached a copy of the printer.cfg file and the image of the error message.

Any assistance in the direction I can take to resolve this issue will be greatly appreciated.

Thanks

DesP

 

printer.cfg

[mvdveer]

For a new build (reflashed SD card as you did), you need to delete everything under the 

#*# <---------------------- SAVE_CONFIG ---------------------->
#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.
#*#
#*# [extruder]
#*#
#*# [bltouch]
#*# z_offset = 1.961
#*#
#*# [bed_mesh default]
#*# version = 1
#*# points =
#*# -0.028750, 0.017500, 0.073750, 0.098750, 0.175000
#*# -0.043750, -0.017500, 0.006250, 0.026250, 0.055000
#*# -0.052500, -0.021250, 0.005000, 0.010000, 0.038750
#*# -0.010000, 0.005000, 0.016250, 0.015000, 0.047500
#*# 0.061250, 0.001250, 0.016250, 0.008750, 0.037500
#*# x_count = 5
#*# y_count = 5
#*# mesh_x_pps = 2
#*# mesh_y_pps = 2
#*# algo = lagrange
#*# tension = 0.2
#*# min_x = 10.0
#*# max_x = 190.0
#*# min_y = 10.0
#*# max_y = 190.0

file, as this refers to values saved previously for the printer. (on the old SD card configuration). After you have tuned your printer, this area will be populated again. The error occurs because Klipper has not done a bed mesh as yet (on the new SD card) and does not know the position of the bltouch.

It also important to delete this as your Z-Offset will be different to what is saved here.

This is what it should look like:

#*# <---------------------- SAVE_CONFIG ---------------------->
#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.
#*#

Restart and See what happens. If there are errors after that - post them here and I will walk you through it.

For initial startup of your printer, use the following guide:

Klipper configuration checks

Once you have all this tuned then use the Ellis Print Tuning guide to tune the printer.

Start there and see what happens

[DesP]

Hi Dave

Apologies if I lead you astray. The printer I purchased came with the BTT mainboard flashed with the Klipper firmware. I did not flash it myself.

However, I will go through the steps you have suggested as something may have altered during the time.

Will try today and post the results.

Regards

DesP

[mvdveer]

7 minutes ago, DesP said:

Hi Dave

Apologies if I lead you astray. The printer I purchased came with the BTT mainboard flashed with the Klipper firmware. I did not flash it myself.

However, I will go through the steps you have suggested as something may have altered during the time.

Will try today and post the results.

Regards

DesP

The klipper data is stored on the Rapsi Pi SD card, not the BTT mainboard. The mainboard get's flashed with the firmware,so that it can talk to klipper, but the printer configurations are stored on the SD card. As you reflashed the SD card with mainsail,

Quote

I have set up a Raspberry Pi 4b with MainsailOS and connected it to the printer

all that data is lost and klipper is looking for something that was previously saved there and cannot find it as it is a new SD card. 

With regards the mainboard, you may get an error that the "mcu firmware" may be redundant, which means you will have to reflash the BTT board. (we'll cross that bridge if it happens)

But for now, delete everything under that heading, restart and let's see what happens.

Happy to explain over the phone as we both are in Oz. DM me with your number and I'll call you if you want. 

[DesP]

 

Hi Dave

Removed everything under the line 

#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.

 

The following resulted.

So deleted the comment from ‘z_offset: 0 line’ in [bltouch]

This is the content of the [gcode_macro m600]

[gcode_macro m600] description: Pauses the current print. Usage: M600 [B<beeps>] [E<pos>] [L<pos>] [R<temp>] [U<pos>] [X<pos>] [Y<pos>] [Z<pos>] gcode:   PAUSE B="{0}" P=2   {% for k in params|select("in", "EXYZ") %}     {' '~k~'="'~params[k]~'"'}   {% endfor %}   UNLOAD_FILAMENT   {% if 'U' in params %}     LENGTH={params.U}   {% endif %}   BEEPS="{params.B|default(10)|int}"   {% if 'R' in params %}     M109 S{params.R}   {% endif %}

 

[DesP]

 

Hi Dave

No, just deleted the comment character

Des

[DesP]

Hi Dave

Found problem with the gcode_macro m600. The [Z<pos>] should have been part of the line above.

Now corrected.

Error now is with [board_pins] section

[board_pins]
aliases:
# EXP1 header
EXP1_1=PE8, EXP1_3=PE7, EXP1_5=PB2, EXP1_7=PB1, EXP1_9=<GND>,
EXP1_2=PE9, EXP1_4=<RST>, EXP1_6=PE10, EXP1_8=PE11, EXP1_10=<5V>
 

Should this be all one line?

[mvdveer]

what screen do you have connected