Connecting reprapdiscountLCD2004 to SKR mini E3 V2

General Discussion
1

Hi all! I’ve just installed klipper to tyr it and i’m having problems setting up the display. My printer is a homemade cartesian with a brand new SKR mini e3 v2. I’ve copied the sample-lcd.cfg lines to my printer.cfg

[display]
lcd_type: hd44780
rs_pin: EXP1_4
e_pin: EXP1_3
d4_pin: EXP1_5
d5_pin: EXP1_6
d6_pin: EXP1_7
d7_pin: EXP1_8
encoder_pins: ^EXP2_3, ^EXP2_5
click_pin: ^!EXP1_2
#kill_pin: ^!EXP2_8

[output_pin beeper]
pin: EXP1_1

And these are the pin map

[board_pins]
aliases:
** # EXP1 header**
** EXP1_1=PB5, EXP1_3=PA9, EXP1_5=PA10, EXP1_7=PB8, EXP1_9=,**
** EXP1_2=PA15, EXP1_4=, EXP1_6=PB9, EXP1_8=PB15, EXP1_10=<5V>**

The problem that klipper never starts, it fails with the error pin EXP1_4 is reserved for .
I’ve been trying to remove the <> and use RST but it says that the MCU doesnt have a pin called RST, I’ve been looking into the code where the exception is launched and obviously y compares the pin name with the reserver ones array, and that’s is also what i wanted to askl, what does reserved meanN If someone could help me to understand better the pins functionality and configuration I would
klippy.log (13.0 KB)
appreciate it!

2

Strange. Does it change when you swap the blocks, i.e.

[board_pins]
aliases:
    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=PB15, EXP1_10=<5V>

[display]
lcd_type: hd44780
rs_pin: EXP1_4
e_pin: EXP1_3
d4_pin: EXP1_5
d5_pin: EXP1_6
d6_pin: EXP1_7
d7_pin: EXP1_8
encoder_pins: ^EXP2_3, ^EXP2_5
click_pin: ^!EXP1_2
#kill_pin: ^!EXP2_8

[output_pin beeper]
pin: EXP1_1
3

Same result.

Recv: // pin EXP1_4 is reserved for <RST>
Recv: //
Recv: // Once the underlying issue is corrected, use the "RESTART"
Recv: // command to reload the config and restart the host software.
Recv: // Printer is halted
Recv: // Klipper state: Not ready
Recv: !! pin EXP1_4 is reserved for <RST>
4

Please attach your printer.cfg file.

5

printer.cfg (2.8 KB)

6

You could try this, delete the RST pin in your printer config and repeat above steps. You might not need this pin to get started. Good luck!

7

Do you mean delete from the display config? If thats the case, this pin is needed to setup the display. If you mean delete this pin from other place, could you tell me what place? jaja

8

Other thing that makes me think is the pin name. First of all I don’t know what for a <> reserved pin is used or how you determine that “X” pin is reserved, because for example, if I set up the pin alias to RST and not to <RST>, Klipper says that this mcu doesn’t have a pin named RST, but if you look at the chip pinout pinout, pin number 7 is NRST, and not RST, so I don’t know if this is related with this error! I also tried naming the pin NRST but nothing changes!

9

v0.11.0-41-g9b60daf6-dirty

Your Klipper version is marked as dirty. This only happens if you have modifications to the source outside of Klipper mainline. What did you change?

10

I stepped back, since Sineos answered faster.

11

I believe I changed nothing! I just installed everything using kiauh. Full clean installation.

12

Short reply, I don`t understand what reserved pins are used for? Yes, i’m from Argentina XD.

13

Make sure you have a pristine Klipper that is not marked as dirty. Would be wasted time, if such a modification is causing the troubles you are having.
All your config is pretty standard and the pin aliases in this form are there since ages. Currently for me it is not obvious, why it should cause errors.

14

I’m an absolute beginner with Klipper. I guess Sineos means something like this, https://www.reddit.com/r/klippers/comments/t9nogq/klipperscreen_update_always_dirty/ so there is something important you may have changed.

15

Any suggest about how could I check that? Because I just cloned kiauh, follow the installation steps, and generated the bin for the SKR mini according to the sample.cfg. That’s all…

16

Basically quite simple: Klipper checks if the installed sources match with the given Github revision. If there is a mismatch, the local repository is marked as dirty.
This typically means that:

  • Unsupported extras have been installed
  • Klipper source files have been manually altered
  • Something else corrupted the local repository

Unless this is fixed, the experienced users here typically will not assist any further as it could well be that the issue is originating from the modification and to chase such is a waste of time

I do not use kiauh so I can’t really tell what this might be. Possibly some “extras”

1 Like
17

Okk, i understand! I really appreciate your help. I’ll just uninstALL and try to reinstall everything again!

18

When installing I used debian script, but maybe should it be Ubuntu? Im running linuxliteos

19

It doesn’t matter which OS you have running on your PC, when installing Klipper. Windows, Linux ,or Mac. Anyway :wink:

PS: Funny, first time I stumbled over linuxliteos https://www.linuxliteos.com/ But since it’s using Xfce, why don’t you use Xubuntu? Way bigger community!

1 Like
20

Hard to tell. There are subtle differences between the different Linux flavors. When the script runs without error, then it is fine.