Section 't5uid1' is not a valid config, after update

[datendieman]

Hey all,

Just did a klipper update and now it doesnt seem to recognize the "t4uid1" parameter in the config.

Any ideas how to fix this?

Thank you!

[Desuuuu]

This essentially means you are not running my fork anymore.

[datendieman]

This essentially means you are not running my fork anymore.

thanks for the response! for future reference, what is the proper way of updating klipper if I'm running this fork?
I pushed the update button in fluid and it seems to have overwritten the original install.

[Desuuuu]

I'm guessing you could configure Moonraker's updater to use the proper repo. I can't help much more since I'm not using this particular setup though.

[Newcal]

I just reflash the printer with klipper and the modified firmware with your fork and still having the same message

[hieppo]

Instructions are a bit confusing.
I have installed your dgus-display klipper branch and it is running currently. I have build the firmware and the log shows this:
Version: dgus-display-211225-6-g90ebed1f
Preprocessing out/src/generic/armcm_link.ld
Linking out/klipper.elf
Creating hex file out/klipper.bin

I have flashed that to my CR-200B (it uses the same DWIN screen as the CR10S Pro and others)

I tried adding to the Klipper printer.cfg
[t5uid1]
firmware: dgus_reloaded
Klipper firmware would not start complaining section does not recognised.

I then tried:
[dgus_display]
type: t5uid1
uart_bus: usart3
implementation: dgus_printer_menu
volume: 50

This does allow me to boot up klipper and the DWIN screen does go beyond the bootup log (but not Klipper log) and into strange Chinese language and unresponsive.

I did flash the DWIN_SET. But the the final summary shows no update to any BMP. This may be why the screen is not showing properly? Any idea why it did not flash?

I might just found the answer. The CR-200B LCD is a DGUS2 display. Lots of the file names are different and the CFG file is not a T5UID1 but a T5LCFG. There probably some similarity but it is different enough that it will not work straight out without some reworking.

[ratomas108]

Hello,
I have T5L1 display ( Sermoon D1 ). I have to compiled source code in SW ( DGUS_Tool_V8.2.1.14 ). Now it is working. I used original T5L.cfg file, generated new bin files, recompiled icons, buttons, screens.

[hieppo]

Hi could you please provide some steps you did to get the display to work

[ratomas108]

Here are some steps: Desuuuu/klipper#122 (reply in thread). I will write some steps later.

[ratomas108]

1. Download stock FW, source project from Desuuuu.
2. Open stock FW and copy *.HZK and *.CFG files.
3. Open DWprj.hmi file in DGUS Tool.
4. Load *.CFG ( Setting\DGUS - CFG Edit - Open CFG )
5. Generate bin files - File\Generate
   
6. Generate ICL files for 24_icons, 27_buttons, 30_progress_left, 37_progress_right, screens
   Setting\DGUS - ICL Tool - Genereate ICL
   
7. Create your DWIN_SET folder with files:
   3 bin files, 5 icon files ( generated from DGUS Tool ), 1 HZK, 1 CFG file
   
8. Flash FW

[ratomas108]

Files are in your project ...\DGUS-reloaded-Klipper-master\project\DWIN_SET. Check date of *.bin files.

[hieppo]

Found it afterwards so I deleted the message. Anyway, my new DWIN_SET folder will only contain the 10 files you have in step 7? What about all those bmp, wav and ico files that normally seen in a DWIN_SET flash?

[ratomas108]

From BMP files you will create 5 lcon library files. WAV Is not neceseary.

[hieppo]

You've indicate to create 5 icon files where the last one is 000_screens.icl. What image do I select for this? BTW, there are icl files already created with custom Klipper images? Why can't we use them?

[ratomas108]

24_icons - generate from 5 files
27_buttons - generate from 19 files
30_progress_left - generate from 101 files
37_progress_right - generate from 101 files
000_boot - generate from 37 files

Stock FW for my display:

You should create similar files.

[hieppo]

Based on your instructions:

1. I use the CFG from Creality OEM which is T5LCFG.CFG. I copy this file to the new DWIN_SET folder and open it in DGUS tool.

2. I use the HZK file from Creality OEM or Desuuuu stock project? I copy this to the new DWIN_SET folder

3. I open the DWprj.hmi from Desuuuu stock project folder which lists out all the images to the left.

4. File/Generate which will generate the 3 bin files (stored in the project/DWIN_SET folder). I copy it out of there into the new DWIN_SET folder

5. I use ICL Generate 24_icons.icl from the 24_icons folder (5 bmp) under Desuuuu project and copy it to the new DWIN_SET folder

6. I use ICL Generate 27_buttons.icl from the 27_buttons folder (19 bmp) under Desuuuu project and copy it to the new DWIN_SET folder

7. I use ICL Generate 30_progress_left.icl from the 30_progress_left (101 bmp) folder under Desuuuu project and copy it to the new DWIN_SET folder

8. I use ICL Generate 37_progress_right.icl from the 37_progress_right (101 bmp) folder under Desuuuu project and copy it to the new DWIN_SET folder

9. What folder that contains the 37 bmp files do I create 000_boot.icl?

10. What similar files should I create with my stock FW?

The last 2 steps are unknown. The farthest I was able to see after the flash is a black screen instead of the Creality boot screen. Once booted, my screen is black with 4 fuzzy squares. It is definitely different than OEM but it is not definitely functional.

[ratomas108]

Ad 2. Try both.
Ad 9. Generate 000_boot.icl from DWIN_SET folder ( 000_boot ... 250_kill ).
Ad 10. Compare stock FW and your new FW. Structure must be similar.

[hieppo]

When you say to compare with stock FW, what exactly am I comparing? Is There are more *.icl files and they have different names? There is one common ##_control.icl. There are bmp files that have different numbering scheme and names. So I am not sure what to compare to Desuuuu DWIN_SET.

[hieppo]

Hey desuuuu,
Can you provide some starting point on what you used to develop the DWIN_SET file? We have the DGUS tool, we should be able to customize for our specific display based on what ratomas108 was able to achieve to get it to work with his Creality printer.

[ratomas108]

Some information:
Desuuuu/klipper#122 (comment)