Latest update does not display data long enough. **solved**

[DAP]

I understand why you want to blank the display, my unit is also showing burn in, but the current settings do not display the data long enough for me to read.
I wandered through the settings, but did not find a way to extend the display time to a reasonable value.
How does one adjust the screen blank time?

[admin]

When you talk about the default still picture it shows data for about 3 seconds every minute.
I can increase that a bit, but only dynamic thing displayed there is IP (which does not vary much over time).

When you use the loop functions to scroll through various data patterns, then you can control how long
this is displayed. When you have an individual still picture display script that should be handled like the loops do,
please post the script code here and I can take that as an example how to treat it.

I guess this might be interesting for a broader audience and I am happy to work on your code as an example.

[Mattk]

3 seconds is fine for the purpose and the default display, more of a heartbeat type pulse than anything else and any longer defeats the purpose.

[DAP]

The unit is set to sequence through the measurments. I timed the display, it is 1.5 seconds per page.
It is one of the standard messages set to display every minute

Code: Select all

#new\n#clear\n*clearloop\n*startloop\n*addloop a0 5 300 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 30 13 SYSTEM\\n#color 1\\n#font helvB12\\n#string 0 30 [mbsystem-ip:--]\\n#string 0 47  {*[mbsystem-cpuload1m.2:0]*100*0}% {*[mbsystem-cpuload5m.2:0]*100*0}% {*[mbsystem-cpuload15m.2:0]*100*0}%\\n#string 0 64 {*[mbsystem-uptime.0:0]/86400*t}d {*([mbsystem-uptime.0:0]%86400)/3600*t}h {*([mbsystem-uptime.0:0]%3600)/60*t}m\n*addloop a1 5 300 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 40 13 WIND\\n#color 1\\n#font helvR14\\n#string 0 30 gust\\n#string 50 30 [wind0wind-max5=mph.1:--] mph\\n#string 0 47 avg\\n#string 50 47 [wind0avgwind-act=mph.1:--] mph\\n#string 0 64 dir\\n#string 50 64 [wind0dir-act=endir:]\n*addloop a2 5 300 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 20 13 OUTDOOR\\n#color 1\\n#font helvR14\\n#string 0 30 temp\\n#string 50 30 [th0temp-act=F.1:--] \xb0F\\n#string 0 47 hum\\n#string 50 47 [th0hum-act.0:--] %\\n#string 0 64 dew\\n#string 50 64 [th0dew-act=F.1:--] \xb0F\n*addloop a3 5 300 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 30 13 INDOOR\\n#color 1\\n#font helvR14\\n#string 0 30 press\\n#string 50 30 [thb0seapress-act=inhg.2:--] in\\n#string 0 47 temp\\n#string 50 47 [thb0temp-act=F.1:--] \xb0F\\n#string 0 64 hum\\n#string 50 64 [thb0hum-act.0:--] %\n*addloop a4 5 300 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 40 13 RAIN\\n#color 1\\n#font helvR14\\n#string 0 30 hour\\n#string 50 30 [rain0total-sum60=in.2:--] in\\n#string 0 47 day\\n#string 50 47 [rain0total-sumday=in.2:--] in\\n#string 0 64 24h\\n#string 50 64 [rain0total-sum24h=in.2:--] in\n*addloop a5 5 300 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 30 13 POWER\\n#color 1\\n#font helvR14\\n#string 0 30 temp\\n#string 50 30 [mbsystem-temp=F.1:--] \xb0F\\n#string 0 47 pwr\\n#string 50 47 [mbsystem-watt.2:--] W\\n#string 0 64 volt\\n#string 50 64 [mbsystem-volt.2:--] V\n#show

[admin]

Thanks for the code snippet, which helps me to find and fix another smaller bug in the OLED driver.

Code below does now work as expected. It rolls through the screens one time, then blanks display and starts over when triggered again. You can for example trigger this OLED script every minute or two and have data dispalyed and black periods interchanging.

Code: Select all

*clearloop\n*startloop\n*addloop a0 5 -1 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 30 13 SYSTEM\\n#color 1\\n#font helvB12\\n#string 0 30 [mbsystem-ip:--]\\n#string 0 47  {*[mbsystem-cpuload1m.2:0]*100*0}% {*[mbsystem-cpuload5m.2:0]*100*0}% {*[mbsystem-cpuload15m.2:0]*100*0}%\\n#string 0 64 {*[mbsystem-uptime.0:0]/86400*t}d {*([mbsystem-uptime.0:0]%86400)/3600*t}h {*([mbsystem-uptime.0:0]%3600)/60*t}m\n*addloop a1 5 -1 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 40 13 WIND\\n#color 1\\n#font helvR14\\n#string 0 30 gust\\n#string 50 30 [wind0wind-max5=mph.1:--] mph\\n#string 0 47 avg\\n#string 50 47 [wind0avgwind-act=mph.1:--] mph\\n#string 0 64 dir\\n#string 50 64 [wind0dir-act=endir:]\n*addloop a2 5 -1 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 20 13 OUTDOOR\\n#color 1\\n#font helvR14\\n#string 0 30 temp\\n#string 50 30 [th0temp-act=F.1:--] \xb0F\\n#string 0 47 hum\\n#string 50 47 [th0hum-act.0:--] %\\n#string 0 64 dew\\n#string 50 64 [th0dew-act=F.1:--] \xb0F\n*addloop a3 5 -1 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 30 13 INDOOR\\n#color 1\\n#font helvR14\\n#string 0 30 press\\n#string 50 30 [thb0seapress-act=inhg.2:--] in\\n#string 0 47 temp\\n#string 50 47 [thb0temp-act=F.1:--] \xb0F\\n#string 0 64 hum\\n#string 50 64 [thb0hum-act.0:--] %\n*addloop a4 5 -1 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 40 13 RAIN\\n#color 1\\n#font helvR14\\n#string 0 30 hour\\n#string 50 30 [rain0total-sum60=in.2:--] in\\n#string 0 47 day\\n#string 50 47 [rain0total-sumday=in.2:--] in\\n#string 0 64 24h\\n#string 50 64 [rain0total-sum24h=in.2:--] in\n*addloop a5 5 -1 #clear\\n#font helvB12\\n#color 1\\n#rbox 0 0 126 14 4\\n#color 0\\n#string 30 13 POWER\\n#color 1\\n#font helvR14\\n#string 0 30 temp\\n#string 50 30 [mbsystem-temp=F.1:--] \xb0F\\n#string 0 47 pwr\\n#string 50 47 [mbsystem-watt.2:--] W\\n#string 0 64 volt\\n#string 50 64 [mbsystem-volt.2:--] V\n*addloop a6 3 -1 #clear\n#show\n

Main difference is that "*addloop a0 5 -1" defines that loop screen "a0" should stay for 5 seconds and should be repeated just once "-1". Prior you had "*addloop a0 5 300" which tells to repeat showing this screen through the loops until 300 seconds have passed in total. At the end of the script I added "*addloop a6 3 -1 #clear" which tells that last loop screen should render display blank.

I also removed some unnecessary "new" and "clearall" statements.

When you reboot your MB PRO to get latest 3.3 code, this should work fine now.

[DAP]

It is readable again. Thanks.