On Friday when I tried to run my final check of the display, I noticed the pixels connected to cluster 4 would not turn on. I tried a number of things to troubleshoot (which took more that 10 minutes) before giving up. While sleeping (or trying to) I thought about the board being in server mode. A logon attempt in the morning got me in the board, so I changed the web server option to only run the server on boot up.
The problem I am dealing with now is the pixels are flickering terribly (they don't flicker when running the onboard test function). I'm wondering if something may have happened that is power related that resulted in both problems. I intend on checking the power supply this morning as well as the network cable.
Figured I'd post on here to see if anyone either has had a similar experience, or can provide some other suggestions. If I run them tonight, could I damage the pixels?
I am running the stock firmware on the board btw.
Its a combination of server mode and pixel turn off when no signal recieved - changing settings will fix it.
Theres a few post on it.
I see an option NO n, where if n is non zero the pixels will go dark after no data received. Is this what you're talking about? What should I set this to?
Regards,
BillyT
my current setting for testing is:
Web server: Boot Only with a 300 second time out. (WEB 1)
No Data Timeout: Disabled. (NO 0)
With these settings - cluster 4 will not work for 5 mins after power on as the server is running and you can make changes to the settings - after 5 mins the server switches off and the cluster works. That should cure your flickering issues.
If you need to change settings after 5 mins power off and on the unit.
That's what I had mine set at. I changed the web option back to 3 (boot and no data) and it appears the flickering has stopped. Waiting to hear back from Jim on this.
