- All Categories
- Installation Help
- Boot-up Issues
- Display Issues
- Audio Issues
- Time Synchronization
- Singlewire InformaCast Help
The AND devices should automatically register with InformaCast when powered up on the network. If they do not:
1) Verify the InformaCast SLP parameters.
On the InformaCast server, from the Admin –> Network Parameters –> SLP Parameters page:
– check that Publish Configuration File Service is set to Yes
– check that SLP Scope is set to Berbee Applications
– check that the URL of Configuration File Server is set to http://10.10.6.241:8081/InformaCast/resources where 10.10.6.241 is the IP address of the InformaCast server
2) Verify the devices are finding the configuration file.
From the device’s web server, view the Device Status –> Configuration Information page (/config). An SLP DA announcement for the InformaCast server should appear in the top half:
SLP DA Advertisement received from ‘10.10.6.241’. Reported DA with scope list ‘Berbee Applications’ at ‘10.10.6.241’. Scope list matched our scope (‘Berbee Applications’). DA checked for service ‘InformaCastConfiguration’ and it reported 1 url(s):
In the bottom half of the Configuration Information page, the InformaCastSpeaker.cfg file should show as retrieved:
failed to retrieve from server: ‘IPSpeaker2046f90301d1.xml’
failed to retrieve from server: ‘IPSpeaker2046f90301d1.cfg’
failed to retrieve from server: ‘InformaCastSpeaker2046f90301d1.cfg’
failed to retrieve from server: ‘IPSpeaker.xml’
failed to retrieve from server: ‘IPSpeaker.cfg’
config file retrieved: ‘InformaCastSpeaker.cfg’
server used for all new files
The speaker configuration file resides on the InformaCast server: In Windows: C:\Program Files (x86)\SingleWire\InformaCast\webapp\resources\ In Linux: /usr/local/singlewire/InformaCast/web/resources/
By default, the filename is InformaCastSpeaker.cfg. Editing this file will change the settings on all ANetD devices that register to this instance of InformaCast, unless a MAC-specific configuration file also exists in the same directory, e.g., InformaCastSpeaker2046f9034d2f.cfg, in which case the MAC-specific file takes priority over the general file. An aggregate speaker configuration file can also be added to include settings unique to each device on the network, such as SIP extension assignment, default volume settings, etc. See the Gen 2 Configuration Summary document in the Documents section for details on syntax and available settings.
If the ANetD device finds a valid speaker configuration file on the InformaCast server, the speaker settings pages are then made inaccessible from the device’s web server pages. This is a security feature. All speaker settings should be modified using the configuration file as detailed in the Gen 2 Configuration Summary document in the Documents section.
If access to the Speaker Settings pages is required, the configuration file(s) on the InformaCast server can be renamed temporarily to an unrecognized format that the device will no longer detect (i.e., InformaCastSpeaker.cfg.sav). Reboot the device and allow up to 5 minutes for the Speaker Settings link to return to the device’s web page.
The speaker firmware file(s) should be placed in the same directory as the speaker configuration file(s) on the InformaCast server: In Windows: C:\Program Files (x86)\SingleWire\InformaCast\webapp\resources\ In Linux: /usr/local/singlewire/InformaCast/web/resources/
Add or modify the following lines in the speaker’s configuration file to reference the new firmware file:
Reboot the speakers and they will update to the desired firmware release. Do not interrupt the update process. The speaker may reboot 2 or 3 times and it may take up to five minutes for the update to complete.
See the Firmware Versions section to download the latest releases.
ANetD devices can trigger pre-programmed behavior based on an audio and/or text message’s specified priority level. These actions include activation of one or more of the three LED flashers, message text color changes, display brightness changes and activation of the general purpose output, used for interfacing with external devices such as a strobe.
1. Configure the desired priority behavior(s) on the ANetD devices. Sign up or log into the ANetD customer portal in order to download the Gen 2 Configuration Summary document for details on configuring Priority actions on ANetD devices. This configuration information is also available in App Note 40.
2. In order to take advantage of these priorities with Singlewire’s InformaCast software, InformaCast version 9.0.1 or newer must be installed: Click here to update InformaCast if needed.
3. Next, InformaCast can be configured to match the priority range of ANetD devices. The default range of priority levels in InformaCast is only 1-3. Log into the InformaCast server and go to the Admin, Broadcast Parameters page. Set the number of priority levels to 100 and click the Update button to save the new setting.
4. When creating InformaCast messages, the Message Priority field in the Audio tab can now be utilized to activate the configured priority actions on the targeted ANetD devices. The default level is 50; 1 is the highest priority, 100 is the lowest.
For Technical Support, call 608.661.1140, Option 2 or visit Online Support Request. For Sales Support, please click here.
1002 Deming Way
Madison, WI 53717
PO Box 46218
Madison, WI 53744-6218
Phone – (608) 661-1140 – Option 1
Email /Contact – www.singlewire.com/talkwithus
With a valid network connection, a valid NTP time server setting (including by default), and the correct time zone setting, you should never see incorrect time.
The most common reason results from the wrong time zone setting. Configure the time zone in the device’s web server (see the bullet point above under “General Questions” on how to access the web server).
The second most common cause results when the device cannot find the NTP server, or a lost network connection, in which case the clock will free-run, and thus drift over time. You can check the device’s logs to check for this situation (see question below). You should also see #1 above on NTP settings.
If you use ClockWise Campus or a PC as your NTP server, verify and correct the computer clock if needed. The updated time will reflect on associated endpoints within a minute.
If the device is running older firmware (1.4.0001 or older), and the NTP server rejects the NTP request, the incorrect time can display based on the last data exchange with the failing NTP server. Often this failure mode will show up as the device reporting the incorrect time and resetting to the same incorrect time every 20-60 minutes. Update the device firmware to the latest version to fix this and/or change your NTP servers to use a known good server. We recommend the following NTP servers:
It generally defaults to once an hour, but you can set the rate on the Device Settings → General Settings web server page.
You can synchronize a device’s internal clock in a number of ways, including use of an NTP server, as well as registration to some application servers (such as InformaCast), and some SIP servers.
Direct from the factory, the unit arrives programmed to receive its time from an Internet NTP time server, and its time zone is set to Chicago time.
The time zone must be set appropriately for the location of the unit. Some standard timezone names available in the USA include the following:
When not using a configuration file, find the time zone setting on the Device Settings –> General Settings page, along with the NTP server configuration.
When “registering” your unit with certain software packages (see Device Settings –> Server Settings page) the unit’s time will set automatically via the server registration process, and this time may take precedence over the use of NTP for configuring the time. The registered server’s time is considered of a higher precedence because synchronized events coming from the server should occur at a specific time at the endpoint.
Without a server configured as described above, or when your server type does not set the time on the unit, we advise configuration of the primary (and secondary) NTP server settings. The device may automatically find additional NTP servers via DHCP option 42. In the case of available servers via DHCP option 42, you do not need to configure the unit for other NTP servers, unless you prefer other NTP servers.
If the network configuration does not allow access the internet, you may need to provide internal (i.e. intranet-based) NTP servers for use by the unit. You can configure ClockWise Campus as an NTP server if convenient, especially in cases where MS Windows time does not always closely synchronize with the outside world. When using ClockWise Campus as an NTP server, Windows may block use of the standard NTP port, in which case you can use a secondary port available via the ClockWise Campus settings page. You must use an explicit port number (by appending a colon and the port number after the NTP server address) in the unit’s settings when using a non-standard NTP port.
You may also use a SIP server to set the time on the unit. Some SIP servers will send the time in the SIP registration response. However, the time from the SIP server is not available at a sub-second accuracy as with NTP, and therefore the time from NTP servers configured will take precedence over the use of SIP server time.
This issue generally occurs because the PC running ClockWise Campus (or other third-party software) does not not have the precisely correct time, and thus generates the sounds at a slightly different time compared to the devices’ displayed time. Possible solutions to this issue include: Set the PC Time: You can correct the PC time via several methods:
Method 1 – Use Internet Time: Click the time display in Windows, click the “Change Date and Time Settings” link, and select the “Internet Time” tab. Verify that the setting shows the PC will synchronize with an Internet time server, and check that it successfully synchronized recently. Note: this option is not available for PCs part of a Windows domain.
Method 2 – NetTime App: If you cannot use the option above, you can install NetTime, a free third-party application, which will synchronize the PC time periodically with an Internet time server: http://www.timesynctool.com/
Method 3 – Set Manually: You can also set the time manually, if you don’t have an Internet connection, or need to update it quickly. Make sure the PC time comes very close to the correct time (i.e. the time displayed on ANetD devices, or some other accurate reference). Usually, you can use this method by clicking the time display in Windows, clicking the “change date and time settings” link, and then setting time. Avoid this method unless necessary, as the PC clock will drift out of sync over days or weeks.
Check “Sync” on the Main Header in ClockWise Campus: ClockWise Campus needs to run as administrator on the PC for this option to work. Enabling this feature causes ClockWise Campus to tell Windows to update its time to Internet time (this feature forces the first method above periodically). This option may not work in all configurations of Windows (usually related to Windows permissions restrictions).
Configure the ANetD Device to Use ClockWise Campus’s Internal NTP Server: ClockWise Campus includes a built-in NTP server. To use it, go to the ANetD device’s Device Settings –> General web page, and change the primary NTP server to your PC’s IP address at port 8090 (the default NTP port for ClockWise Campus, which you can change to any port in ClockWise Campus settings). For example, for a PC with an IP address of 10.10.6.93, set the NTP server, primary field to “10.10.6.93:8090”. If using configuration files, set the NTPConfig tag to point to the ClockWise Campus NTP server, as follows:
Sync the AND Device’s Time Directly to the PC: Before using this option, realize that ANetD devices, usually very accurate, get their own time from an external NTP server. Enabling this feature will forego that functionality, and cause them to lock to your PC instead, regardless of the accuracy of your PC time. This option could prove advantageous if you want precise sound synchronization. However, for accurate time, you will need to ensure your PC keeps accurate time (possibly by the other methods discussed above). Method 1 – Point Devices to PC: Go to the ANetD device’s Device Settings –> Servers web page. Change the Server 1 URL to your PC’s IP address (adding the port 8089). For example, for a PC with an IP address of 10.10.6.93, change the Server 1 field to “http://10.10.6.93:8089”. Also, change the Server Type to “AND” or “AND_Exempt”. If using configuration files, add the ClockWise Campus PC address to the Servers tag as follows (replacing the example address with your PC’s IP address):
Method 2 – Easy Configuration: Right-click on a device in the ClockWise Campus Endpoints tab, and select “Perform Easy Configuration” from the context menu. ClockWise Campus will perform all the necessary configuration of the device(s) selected. This method only works on installations that do NOT use a config file.
Use ClockWise Campus Ping: Similar to above, this option syncs ANetD devices to the PC time (regardless of accuracy, but benefits in keeping devices synchronized with ClockWise Campus events). To enable this option, go to the device’s web page to access Device Settings –> General to make the NTP servers field blank, and go to Device Settings –> Servers to make the Server URL fields blank. Note: this method will not work correctly if multiple PCs on the same network have ClockWise Campus installed. Use a SIP Server: Configure a SIP server in Device Settings –> SIP of the ANetD device’s web page. Make sure to set the NTP settings field to blank in Device Settings –> General, and set the timezone field correctly. The device will get the time from the SIP server.