Date
Votes
5 comments
-
^UD\_$ I would try and swap the player that works well, with a player that doesn't, and see if the problem moves with the player, or stays on the same floor.
If the problems stays, then you are looking at a network related issue.
I'm assuming all players are running the same firmware...
-
Ray Kenyon The problem isn't localized to one player. Publishing to different players in different order has confirmed that.
All are running the same firmware.
-
^UD\_$ It could be a network performance or network configuration issue.
Are you the one configuring the firewall and such?
-
Ray Kenyon Unfortunately no. But I'm wondering if this is the issue:
We were under the impression we need to change the "Time on screen..." setting to 30 secs for the HTML5 page holding the twitter feed. That would hold the page for 30 seconds then start over - to force it to refresh every 30 seconds.
When we had 1 player running, that setting worked fine. It was after we published to the other players that the previous player wouldn't refresh after the latest player was configured.If we left "Time on screen..." at 0, does that mean that the HTML5 page won't refresh?
-
^UD\_$ That makes some sense.
Sounds like a firewall bottleneck, causing the players to timeout, and give up on the pages.
Some web pages do not need to be refreshed, by reloading the page. Try setting to 0, and see if the content refreshes without a page reload.
30 Seconds may be too short, because under some conditions, a page would take more than 30 seconds to load for the first time.
Making friends with IT may be helpful too...
The JavaScript Console, may show you what part of the page is hanging.
Please sign in to leave a comment.