BTT MINI12864 V2.0 chrashes Klipper

Basic Information:

Printer Model: Anycubic Chiron (mostly Stock)
MCU / Printerboard: Trigorilla 0.0.2
klippy.log
klippy (2).zip (1.4 MB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). 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

Describe your issue:

My problem is as follows,

I have bought the BTT MINILCD V2.0 for my printer and would like to put it into operation.

Unfortunately, I always get an error message when I restart the firmware. I have attached a picture of the error message.

Here is an excerpt from my Printer.cfg

[board_pins]
mcu: mcu
aliases:
  # Common EXP1 header found on many "all-in-one" ramps clones
  EXP1_1=PC0, EXP1_3=PH0, EXP1_5=PA1, EXP1_7=PA5, EXP1_9=<GND>,
  EXP1_2=PC2, EXP1_4=PH1, EXP1_6=PA3, EXP1_8=PA7, EXP1_10=<5V>,
  # EXP2 header
  EXP2_1=PB3, EXP2_3=PC6, EXP2_5=PC4, EXP2_7=PL0, EXP2_9=<GND>,
  EXP2_2=PB1, EXP2_4=PB0, EXP2_6=PB2, EXP2_8=PG0, EXP2_10=<RST>


######################################################################
# BigTreeTech mini12864 (with neopixel backlight leds)
######################################################################
[display]
lcd_type: uc1701
cs_pin: EXP1_3
a0_pin: EXP1_4
rst_pin: EXP1_5
contrast: 63
encoder_pins: ^EXP2_5, ^EXP2_3
click_pin: ^!EXP1_2
## Some micro-controller boards may require an spi bus to be specified:
#spi_bus: spi
## Alternatively, some micro-controller boards may work with software spi:
#spi_software_miso_pin: EXP2_1
#spi_software_mosi_pin: EXP2_6
#spi_software_sclk_pin: EXP2_2
[output_pin beeper]
pin: EXP1_1

[neopixel btt_mini12864]
pin: EXP1_6
chain_count: 3
color_order: RGB
initial_RED: 0.05
initial_GREEN: 0.05
initial_BLUE: 0.05

If I comment out the lines under [display] the printer works again and the lines with Neopixels work perfectly and I can change the colors as I like.
I hope it’s a simple error and I’m just blind and don’t see it

You are running an unofficial Klipper version on your board and in combination with the Klipper running on the host (which looks suspicious as well), it is creating strange errors.

Thanks for the quick answer.

Hmm ok I try to do a fresh reinstall on the MCU.

Please don’t throw stones at me but my host is the Sonic Pad, I thought last year that would be the solution to all my problems but it’s rather different, I’ll probably have to get a Pi soon :slight_smile:

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