Page Comparison

A player set up for Simple File Networking will retrieve content and schedule updates from your server at regular intervals. The setup files generated here provide settings for your network and point the player to the web server that it will use for updates. To set up a player for Simple File Networking, navigate to File > Setup BrightSign Unit.

...

• Enable Wireless: Check this box to connect the player to the local network using a wireless connection. In order to use a wireless connection, you must purchase a Wireless Module for your BrightSign player. If the player is connecting to a secured network, enter the following:

  • SSID: Enter the SSID of the wireless network.

  • Security key: Enter the password for the wireless network

• Network Connection Priority: Use the up and down arrows to prioritize either the Wired or Wireless connection. The BrightSign player will always attempt to download and upload using the first option, and will only use the second option if the first is unavailable.

• Time zone: Select the time zone where the player is located.

• Time server:(Optional) Specify the server (using a supported protocol) that the player should use to synchronize its clock. Players use the BrightSign Network time server by default.

...

• Standard Splash Screen: The player will display the BrightSign logo when booting up.

• Custom Splash Screen: The player will display a custom logo when booting up. Click Browse to locate and select the image you wish to use. See this FAQ for image size and format restrictions.

...

...

• Name: Enter a name for the beacon.

• Type: Use the dropdown drop down list to select the beaconing mode/format:

  • iBeacon: A simple beaconing format

    • UUID: A string representation of a UUID, which can be in 16-bit, 32-bit, or 128-bit format. A 16-bit UUID must be exactly four hex digits with no punctuation;  a 32-bit UUID must be exactly eight hex digits with no punctuation; and a 128-bit UUID must be punctuated exactly as follows: "cd7b6f81-f738-4cad-aebf-d2a2ea36d996".

    • Major: An integer specifying the 2-byte Major value (0 to 65535)

    • Minor: An integer specifying the 2-byte Minor value (0 to 65535)

    • TxPower: An integer value that corresponds to the measurement of the Tx power level (in dBm) at 0 meters. The default value is -19, which corresponds to a level of -60dBm at 1 meter. The recommended calibration practice is to measure the RSSI in a circle at 1 meter from the beacon, then add 41 to the average measured signal strength to get the TxPower value: For example, measuring a -65dBm RSSI at 1 meter yields a TxPower value of -24.

  • Eddystone URL: The Eddystone-URL format

    • URL: The URL to encapsulate in the advertisement packet. 

    • TxPower: An integer value that corresponds to the measurement of the Tx power level (in dBm) at 0 meters. The default value is -19, which corresponds to a level of -60dBm at 1 meter. The recommended calibration practice is to measure the RSSI in a circle at 1 meter from the beacon, then add 41 to the average measured signal strength to get the TxPower value: For example, measuring a -65dBm RSSI at 1 meter yields a TxPower value of -24.

  • Eddystone UID: The Eddystone-UID format

    • Namespace: A 10-byte value expressed as 20 hexadecimal digits

    • Instance: A 6-byte value expressed as 12 hexadecimal digits

    • TxPower: An integer value that corresponds to the measurement of the Tx power level (in dBm) at 0 meters. The default value is -19, which corresponds to a level of -60dBm at 1 meter. The recommended calibration practice is to measure the RSSI in a circle at 1 meter from the beacon, then add 41 to the average measured signal strength to get the TxPower value: For example, measuring a -65dBm RSSI at 1 meter yields a TxPower value of -24.

...

• Enable playback logging: Records playback start and end times, zone names, media types, and file names.

• Enable event logging: Records timestamps, state names, zone names, event types, and event data.

• Enable state logging: Records current and last state names, timestamps, and media types.

• Enable diagnostic logging: Records timestamps, firmware and script versions, and the current presentation.

• Enable Variable logging: Records the current and default values of all User Variables in the presentation. This log is only generated when logs are uploaded to a custom log handler URL.

• Upload logs: Check either of the following:

  • On startup: Uploads log files each time the player is powered on.

  • At specific time each day: Uploads log files daily at the specified time. Use the dropdown lists to pick a time.

• Relative URL for log handler: Specify the location on the server where you want logs to be uploaded and parsed.

...