Last Updated: May 22, 2017
BrightSign players support setting their time using the HTTP and SNTP time protocols. While SNTP requires port 123 to be open to set the time, HTTP does not.
See this FAQ to learn how to set different time protocols on BrightAuthor:connected or this FAQ for BrightAuthor.
Time Configuration Workflow
The BrightSign player makes multiple attempts to connect to the time server at startup. If an attempt is successful, the player will set its clock and then communicate with the time server every 12 hours to recalibrate it.
If the initial attempt fails, and the response takes less than 8 seconds, the player tries again immediately. If the response takes longer than 8 seconds, the unit waits 2 minutes to try again. Each time there's a failure taking less than 8 seconds, the player waits a little longer to retry.
A change to a player's time server settings through the BSN.cloud causes the player to check the time server as soon as it downloads the updated sync file during the next point of communication between the BSN.cloud and the player.
- A time of 88:88 indicates that the time is not set properly on the player.
- Setting the time via HTTPS is also supported. If the player is accessing the time server through a proxy server, then HTTP should be used because it will honor the proxy settings.
- SNTP is a simplified implementation of the Network Time Protocol (NTP). SNTP interoperates with standard NTP servers.
- The default clock-update interval of 12 hours can be modified using the roNetworkConfiguration object in BrightScript.