after uninstalling klipper from the mainsailos image and then reinstalling this fork I get this error

Moonraker can't connect to Klippy!
Please check if the Klipper service is running and an UDS (Unix Domain Socket) is configured.

SAMPLE_RETRACT_DIST= doesn't work, wont affect how high probe is rising after probing

as the title suggest, I'm having some issue attempting to get the screen working, and so far, its just black for me. any suggestiuons?

Hi, i got my flsun SR with t5l1 dgus2. Is there any chance to get it working? After uploading t5uid1 files it does not see most files.

Sorry if it's not a good place for this

"unknown command: config_ds18b20" in fluidd ui console after add klipper ds18b20 sensor section

First of all, thanks for putting this together. One of the biggest hangups I had with Klipper is the lack of machine control, and your updates helped get my touchscreen working with it.

However, I've had to revert my recent changes to my printer (Ender 5 Plus with Silent board) as I wasn't getting the same quality as I was with stock hotend/silent board firmware and I needed to print some items.

As part of this I wanted to revert the touch screen display changes as well. I have tried clearing out the MicroSD card and copying the DWIN_SET files from the most recent Creality Silent board firmware release. I get the proper main screen image, but none of the buttons are responsive, and there are no temperatures displayed.

Any thoughts on what I might need to do to revert the display update and getting it functional again? Would including the optional T5UID1.cfg file from the wiki (https://github.com/Desuuuu/DGUS-reloaded-Klipper/wiki/Flashing-the-firmware) help here, or is that specific to your updates? (It's binary, so I'm not certain what it actually does)

Thank you!

Ran into this issue yesterday (and now have seen others posting about it on some facebook groups). Looks like there is conflict between the USARTx_IRQHandler function in src/stm32/serial.c and src/stm32/serial_t5uid1.c . I got around it by renaming the function and its usage in serial.c to USARTx_IRQHandler2 although I'm sure that isn't the correct solution.

I'm running Klipper on an Ender 5 Plus and under the Move controls the up / down arrows for Z axis are inverted. On fluidd there's an option to Invert Z control on Settings > Tool. I was wondering if there's a similar configuration setting here?

Thanks for this great firmware!

Hello. Can you make support for this sensor?

https://duet3d.dozuki.com/Wiki/Duet3dFilamentMonitor_LaserVersion

Hi, there is a request on the klipper repo:
Klipper3d#5004

Is it possible to start a PR for T5UID1 touchscreen support there?
Thanks for looking into it.

I had upgraded to the test version, with dgus, and it just had too many issues, so I reverted back to the master branch, flashed the screen and did make menuconfig. I got the error:

'Error loading kinematics 'corexy''

I deleted and unistalled everything, re-did everything, now I get:

'Error loading module 'motion''

tail of klipper log:

'=======================
Config error
Traceback (most recent call last):
File "/home/pi/klipper/klippy/klippy.py", line 157, in _connect
self._read_config()
File "/home/pi/klipper/klippy/klippy.py", line 143, in _read_config
m.add_printer_objects(config)
File "/home/pi/klipper/klippy/toolhead.py", line 600, in add_printer_objects
File "/home/pi/klipper/klippy/toolhead.py", line 256, in init
self.kin = mod.load_kinematics(self, config)
File "/home/pi/klipper/klippy/kinematics/corexy.py", line 100, in load_kinematics
return CoreXYKinematics(toolhead, config)
File "/home/pi/klipper/klippy/kinematics/corexy.py", line 12, in init
self.rails = [ stepper.PrinterRail(config.getsection('stepper_x')),
File "/home/pi/klipper/klippy/stepper.py", line 269, in init
elif default_position_endstop is None:
File "/home/pi/klipper/klippy/stepper.py", line 339, in add_extra_stepper
mcu_endstop.add_stepper(stepper)
File "/home/pi/klipper/klippy/stepper.py", line 211, in PrinterStepper
g1, g2 = [float(v.strip()) for v in gear.split(':')]
File "/home/pi/klipper/klippy/klippy.py", line 120, in load_object
raise self.config_error("Unable to load module '%s'" % (section,))
Error: Unable to load module 'motion_report'
webhooks client 3043645440: New connection
webhooks client 3043645440: Client info {'program': 'Moonraker', 'version': 'v0.7.1-60-gfdfab66'}'

Then I installed from the official repo, and it works now, except I get that stupid heater error.

can update support klipper to last version ?

I have been able to get the M73 Progress plugin working, and the TFT reports the elapsed time and percentage, but I've noticed there isn't any support for the R parameter, which would show the remaining time estimate. Could support for this be added?

P.S. Would be nice if there was a little more documentation on adjusting the preheat temperatures and modifying the TFT firmware, e.g. that DGUS tool 7.30 is required

Hi,

Apologies if this is not the right place to raise this - maybe there is a Discord?

I followed the guide to install your modified Klipper and DGUS repos on my Ender-6: https://3dprintbeginner.com/how-to-install-klipper-on-creality-ender-6/

The install went well and everything is working as expected, apart from not seeing any progress on the DGUS screen, presumably since Klipper is not sending M73 updates. I have [display_status] in the config, and I read somewhere this should be enough to trigger this in Klipper - am I missing something or is M73 not working in your fork as expected?

I am a dev so happy to look into a bug fix PR if you want to point me in the right direction...

Cheers
Tim

Now it's in alphabetic order. Almost unusable with few dozens almost same name files.

I have been looking through your MCU code changes to try to appreciate what would be involved in porting your screen support to additional MCUs in Klipper. On the surface it looks like it might not be that involved, but I am probably being naive due to my extremely limited coding experience. I am tempted to tinker with it a bit, but would likely need a lot of hand holding.

I basically just threw-in the towel on the Creality control board due to its substantial limitations and rather poor design. I have an SKR E3 Mini v2 and also a Duet 3 Mini 5+ on the way as potential replacements. I think I will settle on the Duet since I am a bit of a freak when it comes to electronics design and quality. Coincidentally someone just got Klipper working on the Duet 3 Mini 5+ and I would love to have the native display working with it.

Are you on the Klipper Discord channel by any chance?

Are you aware of any issues with

git checkout desuuuuklipper/master

I seem to get this error now:

error: pathspec 'desuuuuklipper/master' did not match any file(s) known to git

Both branches (dgus-reloaded being the older firmware, previously on the master branch) are now up-to-date.

MCU code compiles but I haven't really tested Klippy for now. I'll be testing the dgus-display branch soon.

I don't plan on keeping support for the dgus-reloaded branch for much longer, so I suggest moving on to the newer version if possible.

Originally posted by @Desuuuu in #103 (comment)

Hello. Installs your mod. All fine exept moving axes. Icon doesnt toucheble

klippy (2).log

Dear Desuuuu
I have done so many times in so many ways the installation and every time I get this massage:

Everything works perfekt i can controll the printer via webinterface until I add this [t5uid1]
firmware: dgus_reloaded to the printer.cfg. This is why I think there is an issue. I have flashed the screen firmware and the klipper Logo is shown.
Maybe you could help me I would really appreciated that I am about to give up...

look at this line in the log there is the problem.
File "/home/pi/klipper/klippy/extras/t5uid1/t5uid1.py", line 341, in _build_config
"t5uid1_ping oid=%c", cq=cmd_queue)
File "/home/pi/klipper/klippy/mcu.py", line 685, in lookup_command
return CommandWrapper(self._serial, msgformat, cq)
File "/home/pi/klipper/klippy/mcu.py", line 392, in init
self._cmd = serial.get_msgparser().lookup_command(msgformat)
File "/home/pi/klipper/klippy/msgproto.py", line 300, in lookup_command
raise error("Unknown command: %s" % (msgname,))
error: Unknown command: t5uid1_ping
Build file /home/pi/klipper/klippy/../.config(2039): Thu Mar 25 18:50:50 2021

Mainsail diesnt display the flow or speed.

When a print is cancelled either from the touch screen or from Octoprint / Fluidd or such, the print progress screen remains on the printer touch screen. A manual DGUS_PRINT_END needs to be issued from the terminal to remove the screen. I am not sure if this is the right place for it, but I believe [t5uid1_var __status_abort] in klippy/extras/t5uid1/dgus_reloaded/vars_in.cfg should be issuing DGUS_PRINT_END automatically.

Cannot use with SKR2 mainboard. Error "pin PA2 is reserved for t5uid1"

PA2 is used for TH0 on this board.

Is there a way to change the default pin??

https://cdn-3d.niceshops.com/upload/file/BIGTREETECH_SKR_2_user_manual.pdf

It also not react to SET_DISPLAY_TEXT command or renamed M117.

P.S.
While experementing with status messages I somehow get screen bootlops few times with "DPM: Error during 'home' menu update: Timeout waiting for write acknowledgement" in log. Can't reproduce yet, but may be some bug in display message code.

P.P.S.
Screen crashed again with "DPM: Error during message callback: Invalid value". It happened when idle in minute or two after i did something. Still no idea what exactly caused crash exept status message related.

How to update Desuuu to last version Klipper ?

I noticed that sometimes i cant go back to home screen. Navigating in menu works fine but last back button don't react.
May be because i start print from webui with menu open.
dgus-display branch

nvm

When doing something like probe bed I get:
probe at 104.000,141.000 is z=1.
So all usefil digits clipped.

Hi Desuuuu,

Thanks for the amazing port.
My printer come with a DWIN DMT48320C035_06W touchscreen, which is also running on DWIN T5UID1 UI.
But the resolution is different, it's 480x320.

Will this port work for that resolution?

The extruders max temperature shown on the touchscreen, doesn't match extruder max_temp in the printer.cfg file.

Great project! I'm a fan 😃👍

There was some changes to how Mainsail was calculating flow, depending on new klipper commits. mainsail-crew/mainsail#339

I can see that snapshot is reasonably up to date. Is it safe to use?

And thanks man ... Me and my CR10S Pro V2 love what you have done!

Abort/pause/resume dont work on the touchscreen

First of all I wanted to send a HUGE thank you and congratulations for creating the best looking and most usable interface for the CR-10S Pro. Your work, without any doubt, provides the most functional and professional looking touch interface for the printer.

I initially started with your Marlin port, but just recently decided to try Klipper and I may stick with it for good based on what I have seen so far. I have gone through complete setup and optimization of my CR-10S Pro with both firmware flavours and I have several suggestions - this is one of them. But please be gentle with me as I am new to Klipper and I also don't know much about Python.

In my opinion, your manual level code in __level_manual_point should follow the Klipper configuration values, if they are defined by the user in printer.cfg. Specifically, location 1 (data == 1) should use [safe_z_home] location and movement parameters if they have been defined, and locations 2 through 5 should use the [bed_screws] locations. In absence of user defined values within printer.cfg, the code should default to the currently defined values.

While exploring Klipper with your excellent display support for CR-10S Pro I decided to give Fluidd a try. Fluidd requires inclusion of [display_status] in printer.cfg, which loads klippy/extras/display_status, which in turn defines M73 gcmd. This conflicts with definition of M73 that is also found in klippy/extras/t5uid1/t5uid1.py, resulting in "gcode command M73 already registered" warning during Klipper start. It would be awesome if both could be used at the same time.

Using the dgus-display branch, I experienced a failure very shortly into my first print (after switching branches).
The log of the crash and surrounding dumps can be found here: https://gist.github.com/dkabot/a2cab71991dff3a91445c3cc5d4a2ddf

The underlying error is a TypeError in dgus_status.py on line 79: The variable finish_at_naive at this point contains a tuple that the code is trying to change a value in:
https://github.com/Desuuuu/klipper/blob/dgus-display/klippy/extras/dgus_status.py#L79
Tuples are immutable, so this fails and causes a swift crash of Klippy and print failure before finishing the first layer.
Nowhere else in the file does this appear to occur; everything either assigns the whole tuple as a value or simply None.

I've worked around this locally by simply changing the line to assign a new tuple constructed from the values of the existing one, but I am not a primarily Python developer and cannot speak as to if this is a proper solution:

self.finish_at_naive = (self.finish_at_naive[0], self.finish_at_naive[1] + pause_duration)

I did a make and got a couple of Warnings from the build.
Build Kconfig config file

configuration written to /home/pi/klipper/.config

Creating symbolic link out/board
Compiling out/src/sched.o
Compiling out/src/command.o
Compiling out/src/basecmd.o
Compiling out/src/debugcmds.o
Compiling out/src/initial_pins.o
Compiling out/src/gpiocmds.o
Compiling out/src/stepper.o
Compiling out/src/endstop.o
Compiling out/src/adccmds.o
Compiling out/src/spicmds.o
Compiling out/src/thermocouple.o
Compiling out/src/i2ccmds.o
Compiling out/src/pwmcmds.o
Compiling out/src/lcd_st7920.o
Compiling out/src/lcd_hd44780.o
Compiling out/src/buttons.o
Compiling out/src/tmcuart.o
Compiling out/src/spi_software.o
Compiling out/src/neopixel.o
Compiling out/src/sensor_adxl345.o
Compiling out/src/avr/main.o
Compiling out/src/avr/timer.o
Compiling out/src/avr/gpio.o
Compiling out/src/avr/adc.o
Compiling out/src/avr/spi.o
Compiling out/src/avr/i2c.o
Compiling out/src/avr/hard_pwm.o
Compiling out/src/avr/watchdog.o
Compiling out/src/avr/serial.o
Compiling out/src/generic/serial_irq.o
Compiling out/src/avr/serial_t5uid1.o
Compiling out/src/generic/t5uid1_irq.o
src/generic/t5uid1_irq.c: In function ‘t5uid1_timeout_event’:
src/generic/t5uid1_irq.c:90:49: warning: integer overflow in expression [-Woverflow]
t->timer.waketime += timer_from_us(TIMER_MS * 1000);
^
src/generic/t5uid1_irq.c: In function ‘reset_timer’:
src/generic/t5uid1_irq.c:102:58: warning: integer overflow in expression [-Woverflow]
t->timer.waketime = now + timer_from_us(TIMER_MS * 1000);
^
Building out/compile_time_request.o
Version: 7b7b44b-20201231_030251-octopi
Linking out/klipper.elf
Creating hex file out/klipper.elf.hex

Installed clean, unmodified test branch, and latest release from accompanying DGUS_Menu firmware. Config options register fine, but shortly after "Ready" there's an e-stop and shutdown due to "Internal error during ready callback: Timeout waiting for write acknowledgement". klippy.log attached.
klippy.log

Forks of Klipper can apparently only be properly parsed by the update manager in moonraker if a git tag is present according to a conversation with the developer.
I'm not sure if thats feasible with you setup for auto-updates, but maybe you can look into it.

DGUS command not showing and I cant figure out why I have it set to stm32f103 and nothing.

I tried move z to 0.15. I can type 0.1 but when i press 5 it become 01.5

I just cant compile it for SKR Mini E3 V3 with "Enable DGUS T5UID1 screen option" enable. I'm getting a bunch of error whatever serial port i choose:

pi@fluiddpi:/klipper $ make
Creating symbolic link out/board
Building out/autoconf.h
Compiling out/src/sched.o
Compiling out/src/command.o
Compiling out/src/basecmd.o
Compiling out/src/debugcmds.o
Compiling out/src/initial_pins.o
Compiling out/src/gpiocmds.o
Compiling out/src/stepper.o
Compiling out/src/endstop.o
Compiling out/src/trsync.o
Compiling out/src/adccmds.o
Compiling out/src/spicmds.o
Compiling out/src/thermocouple.o
Compiling out/src/i2ccmds.o
Compiling out/src/spi_software.o
Compiling out/src/sensor_adxl345.o
Compiling out/src/lcd_st7920.o
Compiling out/src/lcd_hd44780.o
Compiling out/src/buttons.o
Compiling out/src/tmcuart.o
Compiling out/src/neopixel.o
Compiling out/src/pulse_counter.o
Compiling out/src/stm32/watchdog.o
Compiling out/src/stm32/gpio.o
Compiling out/src/generic/crc16_ccitt.o
Compiling out/src/generic/armcm_boot.o
Compiling out/src/generic/armcm_irq.o
Compiling out/src/generic/armcm_reset.o
Compiling out/src/generic/timer_irq.o
Compiling out/src/stm32/stm32f0_timer.o
Compiling out/src/stm32/stm32g0.o
Compiling out/src/stm32/gpioperiph.o
Compiling out/src/stm32/stm32f0_adc.o
Compiling out/src/stm32/stm32f0_i2c.o
Compiling out/src/stm32/spi.o
Compiling out/src/stm32/stm32f0_serial.o
Compiling out/src/generic/serial_irq.o
Compiling out/src/stm32/t5uid1/serial.o
src/stm32/t5uid1/serial.c: In function 't5uid1_USARTx_IRQHandler':
src/stm32/t5uid1/serial.c:50:27: error: 'USART_TypeDef' {aka 'struct '} has no member named 'SR'; did you mean 'ISR'?
uint32_t sr = USARTx->SR;
^
ISR
src/stm32/t5uid1/serial.c:51:15: error: 'USART_SR_RXNE' undeclared (first use in this function); did you mean 'USART_ISR_RXFF'?
if (sr & (USART_SR_RXNE | USART_SR_ORE))
^~~~~~~~~~~~~
USART_ISR_RXFF
src/stm32/t5uid1/serial.c:51:15: note: each undeclared identifier is reported only once for each function it appears in
src/stm32/t5uid1/serial.c:51:31: error: 'USART_SR_ORE' undeclared (first use in this function); did you mean 'USART_ISR_ORE'?
if (sr & (USART_SR_RXNE | USART_SR_ORE))
^~~~~~~~~~~~
USART_ISR_ORE
src/stm32/t5uid1/serial.c:52:32: error: 'USART_TypeDef' {aka 'struct '} has no member named 'DR'; did you mean 'RDR'?
t5uid1_rx_byte(USARTx->DR);
^~
RDR
src/stm32/t5uid1/serial.c:53:14: error: 'USART_SR_TXE' undeclared (first use in this function); did you mean 'USART_ISR_TXFE'?
if (sr & USART_SR_TXE && USARTx->CR1 & USART_CR1_TXEIE) {
^~~~~~~~~~~~
USART_ISR_TXFE
src/stm32/t5uid1/serial.c:53:44: error: 'USART_CR1_TXEIE' undeclared (first use in this function); did you mean 'USART_CR1_TXFEIE'?
if (sr & USART_SR_TXE && USARTx->CR1 & USART_CR1_TXEIE) {
^~~~~~~~~~~~~~~
USART_CR1_TXFEIE
src/stm32/t5uid1/serial.c:45:22: error: 'USART_CR1_RXNEIE' undeclared (first use in this function); did you mean 'USART_CR1_RXFFIE'?
| USART_CR1_RXNEIE)
^~~~~~~~~~~~~~~~
src/stm32/t5uid1/serial.c:57:27: note: in expansion of macro 'CR1_FLAGS'
USARTx->CR1 = CR1_FLAGS;
^~~~~~~~~
src/stm32/t5uid1/serial.c:59:21: error: 'USART_TypeDef' {aka 'struct '} has no member named 'DR'; did you mean 'RDR'?
USARTx->DR = data;
^~
RDR
src/stm32/t5uid1/serial.c: In function 't5uid1_enable_tx_irq':
src/stm32/t5uid1/serial.c:45:22: error: 'USART_CR1_RXNEIE' undeclared (first use in this function); did you mean 'USART_CR1_RXFFIE'?
| USART_CR1_RXNEIE)
^~~~~~~~~~~~~~~~
src/stm32/t5uid1/serial.c:66:19: note: in expansion of macro 'CR1_FLAGS'
USARTx->CR1 = CR1_FLAGS | USART_CR1_TXEIE;
^~~~~~~~~
src/stm32/t5uid1/serial.c:66:31: error: 'USART_CR1_TXEIE' undeclared (first use in this function); did you mean 'USART_CR1_TXFEIE'?
USARTx->CR1 = CR1_FLAGS | USART_CR1_TXEIE;
^~~~~~~~~~~~~~~
USART_CR1_TXFEIE
src/stm32/t5uid1/serial.c: In function 't5uid1_init':
src/stm32/t5uid1/serial.c:76:35: error: 'USART_BRR_DIV_Mantissa_Pos' undeclared (first use in this function); did you mean 'USART_CR2_DIS_NSS_Pos'?
USARTx->BRR = (((div / 16) << USART_BRR_DIV_Mantissa_Pos)
^~~~~~~~~~~~~~~~~~~~~~~~~~
USART_CR2_DIS_NSS_Pos
src/stm32/t5uid1/serial.c:77:37: error: 'USART_BRR_DIV_Fraction_Pos' undeclared (first use in this function); did you mean 'USART_CR2_DIS_NSS_Pos'?
| ((div % 16) << USART_BRR_DIV_Fraction_Pos));
^~~~~~~~~~~~~~~~~~~~~~~~~~
USART_CR2_DIS_NSS_Pos
src/stm32/t5uid1/serial.c:45:22: error: 'USART_CR1_RXNEIE' undeclared (first use in this function); did you mean 'USART_CR1_RXFFIE'?
| USART_CR1_RXNEIE)
^~~~~~~~~~~~~~~~
src/stm32/t5uid1/serial.c:78:19: note: in expansion of macro 'CR1_FLAGS'
USARTx->CR1 = CR1_FLAGS;
^~~~~~~~~
In file included from out/board-generic/board/armcm_boot.h:4,
from src/stm32/t5uid1/serial.c:8:
src/stm32/t5uid1/serial.c:41:23: error: 'USART3_IRQn' undeclared (first use in this function); did you mean 'USART1_IRQn'?
#define USARTx_IRQn USART3_IRQn
^~~~~~~~~~~
src/ctr.h:36:22: note: in definition of macro 'DECL_CTR_INT'
(REQUEST), { args }, 0 }
^~~~
out/board-generic/board/armcm_boot.h:10:58: note: in expansion of macro 'CTR_INT'
DECL_CTR_INT("DECL_ARMCM_IRQ " __stringify(FUNC), 1, CTR_INT(NUM))
^~~~~~~
out/board-generic/board/armcm_boot.h:14:9: note: in expansion of macro 'DECL_ARMCM_IRQ'
DECL_ARMCM_IRQ(FUNC, (NUM));
^~~~~~~~~~~~~~
src/stm32/t5uid1/serial.c:79:5: note: in expansion of macro 'armcm_enable_irq'
armcm_enable_irq(t5uid1_USARTx_IRQHandler, USARTx_IRQn, 0);
^~~~~~~~~~~~~~~~
src/stm32/t5uid1/serial.c:79:48: note: in expansion of macro 'USARTx_IRQn'
armcm_enable_irq(t5uid1_USARTx_IRQHandler, USARTx_IRQn, 0);
^~~~~~~~~~~
make: *** [Makefile:64: out/src/stm32/t5uid1/serial.o] Error 1

In comparison compile for SKR E3 V2 works without any problems.

was running KevinOConnor/klipper without any issues on my CR-10S Pro. Decided to try your firmware for the touchscreen. installed as per instructions, first the screen, then cloned your fork and flashed the printer. added touchscreen section to my existing printer.cfg, klipper wont start. unknown config object 'gcode_macro' i tried removing all gcode_macro reference from printer.cfg but that doesnt help. klippy.log attached.

klippy.log

Please consider updating to Klipper 0.10.0. There ate lots of new features and improvements (e.g. rawparams variable for gcode).

Thank you!

I've been maintaining a fork of this fork that does automatic daily snapshots of the main klipper repo; there were some changes today that prevent the dgus display from initializing and functioning. Not sure why, no obvious reason from examining the changes, but reverting the changes from that day fixes it.

Ideally the dgus code would be made compatible with the upstream changes, as they identified some potential issues with the old code

Mainsail doesn't detect this version of klipper

Had the display running with Octoprint front-end and decided to try Fluidd.

When I copied my config to Fluidd, I get the error

Section 't5uid1' is not a valid config section Once the underlying issue is corrected, use the "RESTART" command to reload the config and restart the host software. Printer is halted

Once I comment that out, the printer talks to Fluidd, but I (obviously) do not have a working screen.

I get this error, on my Ender 6, which is Creality board 2.3.1, when selecting USART1, I believe it's PA9/PA10:

Interface usart1 reserved for serial - can't reserve for uart_bus[usart1]

I'm sure it's the same as I chose for the firmware before upgrading it. I tried every other connection, but they all just give me the normal trying to connect error.

I'm attempting to use Fluidd with your configuration (with touchscreen support) but upon launching the Fluidd UI I'm encountering the error "Section 't5uid1' is not a valid config section". I am not able to proceed forward without removing the config section which will disable touchscreen functionality.

I'm using the CR10SProV2 config.

it does action:resume instead of RESUME.

I think this is because the sd card isnt considered active when the print is paused, as it checks printer.virtual_sdcard.is_active

I am going to test fixing this by removing that check on my fork. will report back!

When I have done make menuconfig and try to do a make I get this error:

pi@octopi:~/klipper $ make
  Creating symbolic link out/board
  Building out/autoconf.h
  Compiling out/src/sched.o
  Compiling out/src/command.o
  Compiling out/src/basecmd.o
  Compiling out/src/debugcmds.o
  Compiling out/src/initial_pins.o
  Compiling out/src/gpiocmds.o
  Compiling out/src/stepper.o
  Compiling out/src/endstop.o
  Compiling out/src/adccmds.o
  Compiling out/src/spicmds.o
  Compiling out/src/thermocouple.o
  Compiling out/src/i2ccmds.o
  Compiling out/src/pwmcmds.o
  Compiling out/src/lcd_st7920.o
  Compiling out/src/lcd_hd44780.o
  Compiling out/src/buttons.o
  Compiling out/src/tmcuart.o
  Compiling out/src/spi_software.o
  Compiling out/src/neopixel.o
  Compiling out/src/sensor_adxl345.o
  Compiling out/src/avr/main.o
  Compiling out/src/avr/timer.o
  Compiling out/src/avr/gpio.o
  Compiling out/src/avr/adc.o
  Compiling out/src/avr/spi.o
  Compiling out/src/avr/i2c.o
  Compiling out/src/avr/hard_pwm.o
  Compiling out/src/avr/watchdog.o
  Compiling out/src/avr/serial.o
  Compiling out/src/generic/serial_irq.o
  Compiling out/src/avr/serial_t5uid1.o
src/avr/serial_t5uid1.c:13:6: error: #error "The serial port selected for the T5UID1 screen is already used"
     #error "The serial port selected for the T5UID1 screen is already used"
      ^
make: *** [Makefile:64: out/src/avr/serial_t5uid1.o] Error 1
pi@octopi:~/klipper $

I can't figure if I am doing something wrong or if this is a bug so I hope to get help here...
My printer is a Creality Ender 5 Plus.

Hey, Thanks for putting your time into creating this! I was wondering if you could add support to the Ender 3 V2 dwin display. It's a color non touch TFT display based on the T5UIC1 mcu and it's controlled by a rotary encoder.
Here are some images of the display, some specs of the T5UIC1 and the datasheet of the DMT48270C043_04WN (which is the closest I could find to the E3V2 display model: DMT48270C043_04WNZ11)

T5UIC1_appplication_guide.pdf

DMT48270C043_04WN_datasheet.pdf

Any guiding into modifying the existing code to fit this display would be much appreciated as well. 😊
Thanks!!!