LCD Does Not Turn Off on PR4100


#22

liberty610, thank you for your reply. I too am on the latest firmware and have had the same results for the past 3 FW updates. I also get a mix of replies that it works fine for and others that have the same issue as we have.


#23

Yea, I am not sure why, but since I upgraded to my pr4100 about a year ago, it has never turned the LCD completely off. On my EX4, I could turn it off, but since I have had the pr4100, the GUI menu option only dims it. I don’t mind that it is on honestly. Makes no difference to me as the unit is in a room full of gear with blinking/power LED lights everywhere. But I am an enthusiast geek, and when something does not seem to work like it is suppose to, I go into tinker mode and try to find out why haha.


#24

I am with you 100% on this.


#25

Works on for me on 2.31.149 firmware

image


#26

Huh… congrats then! I am on that same firmware version. All it does is dim the LCD. It does not turn it off like yours is showing.


#27

I’m also unable to turn it off via the UI… but when fiddling with the wdlcd_sub_daemon it was suddenly turned off. I’ll do a few more tests and debugging.


#28

I would be interested in hearing your findings. It isn’t a big deal to me that it doesn’t turn off, I just know that it supposed to, and because it doesn’t it kind of bothers the tinkering geek in me ha.


#29

I tested my PR4100 at home (without any apps) and toggling the LCD works fine here, both via the UI as with these commands:

kill $(pidof wdhws)                    # stop wdhws
echo -ne 'BKL=00\r' > /dev/ttyS2       # disable backlight
/opt/wd/bin/wdhws -config=/etc/wd/sprite-wdhw.xml   # restart wdhws

I’m 99.9% sure that this doesn’t work on my PR4100 unit at work … More news on Monday.


#30

Thanks for the update!


#31

Using exactly the same commands on my other PR4100 at work has no effect on the display.
This is what I get in a screen session on /dev/ttyS2

> STA
STA=6c
> VER
VER=WD BBC v01
> LN1=Dim the light
ACK             # line 1 shows the message
> BKL=00
ACK             # but nothing happens

I suspect that this is a hardware problem, likely a batch of motherboards with a missing resistor near the MCU.