Display --> Rule3 --> "Not enough space"

[Nisbo]

Hello,

I have a NodeMCU ESP-32s V1.1 and a GC9A01 Display from here:
https://de.aliexpress.com/item/1005006100703230.html?

Version: tasmota32-display.bin [Tasmota 14.4.0 (release-display)](https://bit.ly/tasmota)

I try to activate Rule3
with the Display settings from here:
https://github.com/arendst/Tasmota/blob/development/tasmota/displaydesc/GC9A01_display.ini

Rule3 :H,GC9A01,240,240,16,SPI,*,*,*,*,*,*,*,*,40 :S,2,1,0,1,80,80 :I EF,0 EB,1,14 FE,0 EF,0 EB,1,14 84,1,40 85,1,FF 86,1,FF 87,1,FF 88,1,0A 89,1,21 8A,1,00 8B,1,80 8C,1,01 8D,1,01 8E,1,FF 8F,1,FF B6,2,00,20 3A,1,05 90,4,08,08,08,08 BD,1,06 BC,1,00 FF,3,60,01,04 C3,1,13 C4,1,13 C9,1,22 BE,1,11 E1,2,10,0E DF,3,21,0c,02 F0,6,45,09,08,08,26,2A F1,6,43,70,72,36,37,6F F2,6,45,09,08,08,26,2A F3,6,43,70,72,36,37,6F ED,2,1B,0B AE,1,77 CD,1,63 70,9,07,07,04,0E,0F,09,07,08,03 E8,1,34 62,0C,18,0D,71,ED,70,70,18,0F,71,EF,70,70 63,0C,18,11,71,F1,70,70,18,13,71,F3,70,70 64,7,28,29,F1,01,F1,00,07 66,0A,3C,00,CD,67,45,45,10,00,00,00 67,0A,00,3C,00,00,00,01,54,10,32,98 74,7,10,85,80,00,00,4E,00 98,2,3e,07 35,0 21,0 11,80 29,14 :o,28 :O,29 :A,2A,2B,2C,01 :R,36 :0,C0,00,00,00 :1,A0,00,00,01 :2,00,00,00,02 :3,60,00,00,03 :D,51 #

But I get Not enough space
This are 814 chars and AFAIK there are 1000 chars allowed.

I already tried Rule3 '' to reset the rule and afterwards the code above again but same message.
I never created any rules by my own.

However Rule3 ? returns

11:27:20.841 CMD: Rule3 ?
11:27:20.847 MQT: stat/tasmota_9FE400/RESULT = {"Rule3":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}

Does "Free":511 mean there are only 511 chars possible instead of 1000 chars ?

Dont know if it is related, I get this running the Display command

09:46:20.925 CMD: Display
09:46:20.931 MQT: stat/tasmota_9FE400/RESULT = {"Display":{"Model":17,"Type":0,"Width":0,"Height":0,"Mode":2,"Dimmer":50,"Size":1,"Font":1,"Rotate":0,"Invert":0,"Refresh":2,"Cols":[16,8],"Rows":2}}

There is no width/height. I assume this is related to the missing Rule3 setting

This is my configuration

I also tried SPI instead of SSPI settings.

I don't want to compile my own Firmware, so I can not enable scripting to test other options from here:
https://tasmota.github.io/docs/Universal-Display-Driver/#step-5-configure-the-displayini-descriptor-file

I tried the display.ini option but dont know if this was correct.
I created a new file with the name display.ini under Tool --> Manage File System and put the content inside this file but still nothing to see on the display with "DisplayText Test" or "Display Dimmer"

Any idea how to solve the issue ?

PS: there is also an IR Receiver attached to the ESP

[sfromis]

The display.ini strategy is what I'd recommend, and just forgetting about the Rule3 path when you already have a file system available.

However your words "put the content inside this file" does not indicate what exactly you did, as small differences can break stuff. Your basic steps of creating the file looks ok, but the content is important, including how you put it there, as some tools will not work well with copy/paste messing with line breaks. And you should not make it one long line in the file.

BTW. There is no concept of "1000 chars allowed" for the rule sets, indeed it is actually 511 chars max, but with compression this will accommodate rule sets of 1000 chars or more with normal rules. However, the display descriptor text has very little repetition, and will not compress much.

When the setup works, you should get boot time messages like this when you have Weblog 3 activated for details:

00:00:00.045 DSP: File descriptor used
00:00:01.652 DSP: ILI9341 initialized

[Nisbo]

I went to
https://github.com/arendst/Tasmota/blob/development/tasmota/displaydesc/GC9A01_display.ini
and used the button "Copy RAW file"

I went to the display.ini

and hit CTRL+V
saved it and rebooted the ESP

I did a reboot and got this

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.016 UFS: FlashFS mounted with 300 kB free
00:00:00.025 CFG: Loaded from File, Count 57
00:00:00.026 FRC: Some settings have been reset (4)
00:00:00.029 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.037 Project tasmota - IR Bridge Version 14.4.0(release-display)-3_1_0(2024-12-11T09:22:00)
00:00:01.000 WIF: Connecting to AP1 XXXXXXXXXX in mode HT40 as tasmota-9FE400-1024...
00:00:02.739 RSL: RESULT = {"Time":"1970-01-01T00:00:02","IrReceived":{"Protocol":"UNKNOWN","Bits":23,"Hash":"0x210A31E8"}}
00:00:03.537 WIF: Connected
00:00:03.792 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115

with Weblog 3 I get this after a reboot

00:00:00.043 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.044 TYA: Active=0
00:00:00.047 DSP: No valid descriptor found
00:00:00.051 SRC: Restart
00:00:00.052 Project tasmota - IR Bridge Version 14.4.0(release-display)-3_1_0(2024-12-11T09:22:00)
00:00:00.253 WIF: Attempting connection...
00:00:01.000 WIF: Connecting to AP1 xxxxxx in mode HT40 as tasmota-9FE400-1024...
00:00:01.075 WIF: IPv4 192.168.178.115, mask 255.255.255.0, gateway 192.168.178.1
00:00:02.850 IRR: RawLen 6, Overflow 0, Bits 3, Value 0x22AE7A29, Decode -1
00:00:02.852 RSL: RESULT = {"Time":"1970-01-01T00:00:02","IrReceived":{"Protocol":"UNKNOWN","Bits":3,"Hash":"0x22AE7A29"}}
00:00:02.950 IRR: RawLen 6, Overflow 0, Bits 3, Value 0xFEAC02E5, Decode -1
00:00:02.952 RSL: RESULT = {"Time":"1970-01-01T00:00:02","IrReceived":{"Protocol":"UNKNOWN","Bits":3,"Hash":"0xFEAC02E5"}}
00:00:03.412 WIF: IPv6 Local fe80::26dc:c3ff:fe9f:e400%st1
00:00:03.500 WIF: Connected
00:00:03.755 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115
00:00:04.032 RTC: UTC 2024-12-14T11:14:37Z, DST 2024-03-31T02:00:00, STD 2024-10-27T03:00:00
12:14:37.000 RTC: Synced by NTP

[sfromis]

First restart, I see a really bad message there.
00:00:00.026 FRC: Some settings have been reset (4)
Tasmota was detecting a boot loop, and scaled back features until able to boot without crashing.

Second restart, another bad message:
00:00:00.047 DSP: No valid descriptor found
Can't see what happened, but here's a way of avoiding the potential copy/paste pitfalls:

tasmota.urlfetch('https://github.com/arendst/Tasmota/raw/refs/heads/development/tasmota/displaydesc/GC9A01_display.ini','display.ini')

However, the descriptor is based on you having hardware SPI configured, not sure why you were even messing around with software SPI, or what your current template is.

[Nisbo]

However, the descriptor is based on you having hardware SPI configured, not sure why you were even messing around with software SPI, or what your current template is.

Not sure what you mean, the SSPI settings ? I just tried this because I found this via google that all examples where using SSPI instead of SPI.
This are the current settings:

I deleted the old display.ini file, rebooted the ESP and ran this command inside the console

tasmota.urlfetch('https://github.com/arendst/Tasmota/raw/refs/heads/development/tasmota/displaydesc/GC9A01_display.ini','display.ini')

result:

13:00:53.734 CMD: tasmota.urlfetch('https://github.com/arendst/Tasmota/raw/refs/heads/development/tasmota/displaydesc/GC9A01_display.ini','display.ini')
13:00:53.736 SRC: WebConsole from 192.168.178.69
13:00:53.738 CMD: Grp 0, Cmd 'TASMOTA', Idx 1, Len 127, Pld -99, Data '.urlfetch('https://github.com/arendst/Tasmota/raw/refs/heads/development/tasmota/displaydesc/GC9A01_display.ini','display.ini')'
13:00:53.744 MQT: stat/tasmota_9FE400/RESULT = {"Command":"Unknown","Input":"TASMOTA .urlfetch('https://github.com/arendst/Tasmota/raw/refs/"}

but no new display.ini file was created (also checked hidden files)

I power cycled the ESP and now I get this log

00:00:00.002 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.011 UFS: FlashFS mounted with 304 kB free
00:00:00.019 CFG: Loaded from File, Count 63
00:00:00.029 QPC: Count 1
00:00:00.030 CFG: CR 413/699, Busy 0
00:00:00.032 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.033 TYA: Active=0
00:00:00.052 CFG: No '*.autoconf' file found
00:00:00.054 BRY: Berry initialized, RAM used 3136 bytes
00:00:00.060 BRY: No 'preinit.be'
00:00:00.063 DSP: No valid descriptor found
00:00:00.068 SRC: Restart
00:00:00.071 Project tasmota - IR Bridge Version 14.4.0(release-display)-3_1_0(2024-12-11T09:22:00)
00:00:00.084 BRY: No 'autoexec.be'
00:00:00.273 WIF: Attempting connection...
00:00:01.001 WIF: Connecting to AP1 XXXXX in mode HT40 as tasmota-9FE400-1024...
00:00:01.080 WIF: IPv4 192.168.178.115, mask 255.255.255.0, gateway 192.168.178.1
00:00:03.445 WIF: IPv6 Local fe80::26dc:c3ff:fe9f:e400%st1
00:00:03.524 WIF: Connected
00:00:03.730 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115
00:00:04.125 RTC: UTC 2024-12-14T12:16:11Z, DST 2024-03-31T02:00:00, STD 2024-10-27T03:00:00
13:16:11.000 RTC: Synced by NTP

[sfromis]

What I posted was not a Tasmota command, but a Berry function call, which you can run in the Berry REPL console. You can also issue short snippets of Berry code (like that function call) from the regular Tasmota console by prefixing it with the command Br.

[Nisbo]

Now the file was created but still
00:00:00.044 DSP: No valid descriptor found