Config for FLSUN SuperRacer #73
-
Hello, I am trying to get this working on an FLSUN SuperRacer delta printer. The supplied screen is a DWIN DMG48320C035 The printer has a clone SKR 1.3 board (LPC1768 / smoothieware) The screen is connected (4-wires) to the "TFT" port just above the "AUX-1" port in the lower center of this image: I have followed the instructions below for adding the custom Klipper build and re-creating the printer firmware. During the make menuconfig I chose "UART1 (on P0.16 / P0.15)" I flashed the screen with the DWIN_SET folder from the link below - which seemed successful (10 "download" files and "SD Card Process... END !" message) However when powering the printer on the screen remains blank - no Klipper logo. I added this to my printer.cfg file: Is there any way I can confirm, from Putty or the Klipper web GUI, that the Desuuuu version of Klipper is running? I appreciate any suggestions. There are quite a few other people in the SR Facebook group who have switched from Marlin to Klipper, or considering it, and retaining some screen functionality would be great. Thank you, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Looking it up online, that DWIN display is T5L based not T5UID1. Probably that's why it didn't work. I'm also looking forward to a way to easily add suport for different UART TFTs in Klipper (T5UIC1, T5L1). Desuuuu's been working lately on a sort of UART passthrough that would ease the process of porting theses kind of displays in Klipper. |
Beta Was this translation helpful? Give feedback.
-
The touchscreen firmware only works with 480x272 T5UID1 screens. This touchscreen is a T5L one (from what I can tell), with a different resolution as well. It will not work. As to determining whether you're running this fork or not: if the |
Beta Was this translation helpful? Give feedback.
The touchscreen firmware only works with 480x272 T5UID1 screens. This touchscreen is a T5L one (from what I can tell), with a different resolution as well. It will not work.
As to determining whether you're running this fork or not: if the
[t5uid1]
section in your configuration doesn't just make Klippy crash on startup, you are running this fork.