The Diagnostic Web Server (DWS) allows you to view and modify various settings on a networked BrightSign player. This page will walk you through setting up and using the Diagnostic Web Server.
...
Remote DWS (RDWS): accessible over the Internet with BrightAuthor:connected or a web browser.
Local DWS (LDWS): accessible over the local network with a web browser or the BrightSign Shellshell.
The Remote and Local DWS variants provide nearly the same functionality with a few exceptions noted below.
...
In BrightAuthor:connected, go the the Admin tab and select Setup.
Under Player Settings > Player Configuration, click the box to enable the Local Diagnostic Web Server.
(Optional) Enter a Password for the DWS for additional network security. The Username will always be “admin”.
(Optional) Under Player Settings > Remote Screenshot, click the box to Enable remote screenshots box if you would like the player to take screenshots of the display area. These screenshots are accessible from the Screenshots tab on the DWS.
Specify other player settings as desired and either save the setup to a file location or add the setup to the Setup Library.
...
...
For players Players that are already set up and connected to a BSN.cloud Network, the Diagnostic Web Server Cloud network can be turned on or off in the Properties section of the local DWS Network tab (seeNetwork | Network-DeviceConfigurationhttps://brightsign.atlassian.net/wiki/spaces/DOC/pages/384958995/Network#Player-Configuration).
Advanced Setup
You can also configure the local Diagnostic Web Server using the BrightSign serial command prompt or a custom script.
...
| Code Block |
|---|
nc = CreateObject("roNetworkConfiguration", 0)
rebootRequired = nc.SetupDWS()
if rebootRequired RebootSystem() |
Setting the Password
By default, the DWS is enabled with the player serial number as password. To set a custom password with digest authentication, use the roNetworkConfiguration object:
...
Use the username “admin” and your chosen password when connecting to the DWS.
Using the Local DWS
The Diagnostic Web Server Local DWS user interface consists of several tabs. This section details the information and settings offered by each tab. See Remote Diagnostic Web Server for information about the Remote DWS user interface.
Info
This page provides general information about the player and its current status:
...
Network Configuration: View extensive information about network interface settings.
Network Diagnostics: Run network diagnostics. This process may take some time to complete, especially when certain tests fail.
DNS Lookup: Test the specified DNS address to check whether name resolution is working.
Ping: Ping a device with the specified IP address or DNS name.
Trace Route: Perform a standard traceroute diagnostic on the specified IP/DNS address. Check the Resolve IP Addresses box to resolve the specified DNS name.
Network Neighborhood: Display information on the current network neighborhood.
Network Packet Capture: Allows the capture and collection of live network packet data from the network interfaces connected to the BrightSign player.
Disable Autorun: Force the player to reboot and disable the autorun script when the device restarts. This allows the unit to display the OS version and IP address on screen (if the unit is connected to a local network). If the player has a serial port, you will be able to access the system shell over a null-modem serial cable.
Storage Formatting: Takes you to the Format Storage page, which allows you format storage devices attached to the player.
Storage: Select a storage device. You can only format storage devices that are currently unformatted; storage that already contains content files or autorun scripts cannot be reformatted.
File system: Select a supported file system to use when formatting the storage device.
Telnet/SSH: Allows you to enable Telnet and SSH for your player. This lets you access the BrightSign application console when serial port (the default I/O for the application console) is inaccessible. Not that we do not recommend enabling either Telnet or SSH in a production environment for security reasons. A Port Number can be set for Telnet, and a Port Number and SSH Password can be set for SSH as shown in the image below:
...