Remote control mobile app setup: Difference between revisions
(EOL) |
|||
(58 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
< | <div style="font-size:84%">'''[http://www.ChimeMaster.com Home] > [[Chime_Master_Help|Help]] > [[Installation_documentation|Installation]] > [[Installation_documentation#Software|Software]]'''</div><br /> | ||
Our new [[Remote_AX|Advanced eXperience Remote]] is now available! Call 800-344-7464 for upgrade information. | |||
* If you are using one of our [[Advanced_eXperience|AX touchscreen products]], the following instructions '''do not apply''' to you. | |||
This is | == End of Life Notice == | ||
* This application is no longer available in the mobile app stores. | |||
* Our current remote control for Advanced eXperience (AX) ringing systems replaces the Church Bell Remote app described below. | |||
Call 800-344-7464 for upgrade information. | |||
=== | == Setup Management Suite on host PC == | ||
Requirements: | |||
* Chime Master 2200 series bell ringing system | |||
* A license code for the Premium Management Suite option | |||
* PC running Windows operating system | |||
* [[Setup_.NET|.NET framework]] 2.0 or greater installed | |||
* LAN or WLAN connection to the PC with WiFi access | |||
* USB cable to connect the bell ringing system to the PC | |||
=== Outline === | |||
The Church Bell Remote mobile app requires that you have a networked PC running Management Suite connected to the USB port of your bell system. You must [[Install_Management_Suite|install and configure]] Management Suite on the host PC before setting up the mobile app on your phone or tablet. | |||
# Download the Management Suite installation files from: [http://www.chimemaster.com/downloads/ www.chimemaster.com/downloads] | |||
# Do not connect the bell system to the PC USB port until after you install the software. | |||
# Disable third party [[Install_Management_Suite#Antivirus issues|antivirus]] programs on the PC during Management Suite installation. | |||
# Install .NET if it is not on the PC already | |||
# Run the installer (as administrator if possible). | |||
# Plug the bell system into the USB port of the PC and ''wait'' for the drivers to load. | |||
# Set up the desktop icon to run Management Suite as an administrator (see below). | |||
# Start Management Suite. You may be warned that the program wants to make changes to you computer. This is normal for server software. | |||
# Test functionality of Management Suite by launching the local Remote Control screen on the PC. You should see a copy of the carillon front panel display. Close the Management Suite Remote Control window. | |||
# Apply your license code to Management Suite and close the program. | |||
# Set up the Windows Firewall to allow incoming data from the remote control port (TCP 6777). | |||
# Restart Management Suite. The splash screen should indicate that it is licensed to support the mobile apps. | |||
# Open the [[Administration_MS#Mobile_App_Host|Administration]] program from the Management Suite menu. | |||
# Enable the mobile app server and restart Management Suite. | |||
# Open the Administration screen and write down the host IP address for later entry in the mobile app. Add separate users for each mobile device. Remember the login credentials for each. | |||
# Close the Administration program, and restart the Management Suite. It must be running at the main menu for the mobile app to connect to the bell system. | |||
=== Video script === | |||
==== Download and install Management Suite ==== | |||
We are going to set up the Chime Master Church Bell remote mobile app. | We are going to set up the Chime Master Church Bell remote mobile app. | ||
First we will set up the Management Suite | First we will set up the Management Suite ([https://help.chimemaster.com/dl/ChimeMasterMSuite507-F0118.zip download-link]) on our host PC. Click the link and the file will begin to download. | ||
We have removed the instruction to disconnect the system during installation. Also if Windows has been installed from a downloaded upgrade, .NET will not be installed. If .NET is not installed, see [[Setup_.NET|.NET Setup]]. | |||
Also temporarily disable any third-party antivirus software before running the installer. | Also temporarily disable any third-party antivirus software before running the installer. | ||
Line 21: | Line 59: | ||
Agree to the EULA. next next next.. The software requires the .NET framework which is usually already a part of newer Windows systems. ... and close. | Agree to the EULA. next next next.. The software requires the .NET framework which is usually already a part of newer Windows systems. ... and close. | ||
( strikethrough - connect the bell system to the host PC and) Wait for the drivers to install for the Millennium+ carillon. A notification that it is "ready to use" will appear when it is finished or you can click on the device setup icon to watch its progress. (Do not attempt to start the program until driver installation is complete - this may take a few minutes.) | |||
==== Start and setup Management Suite ==== | |||
Right click the desktop start icon. Notice that the default action in bold is to OPEN. Select properties at the bottom of this context menu, click the advanced button and check RUN AS ADMINISTRATOR. OK OK continue ... | Right click the desktop start icon. Notice that the default action in bold is to OPEN. Select properties at the bottom of this context menu, click the advanced button and check RUN AS ADMINISTRATOR. OK OK continue ... | ||
Line 29: | Line 69: | ||
Let's launch Management Suite to make sure it is functional. When we launch the Remote screen, we should see a copy of the bell system's display. Close the remote screen, and notice that the menu only shows the functionality included with the free version of Management Suite. | Let's launch Management Suite to make sure it is functional. When we launch the Remote screen, we should see a copy of the bell system's display. Close the remote screen, and notice that the menu only shows the functionality included with the free version of Management Suite. | ||
We can key in our license code to unlock the premium features by right clicking over the menu and selecting LICENSING | ===== Licensing ===== | ||
We can key in our license code to unlock the premium features by right clicking over the menu and selecting [[Install_Management_Suite#Licensing_for_premium_features|LICENSING]] | |||
In addition to support for the mobile app - the premium license supports | In addition to support for the mobile app - the premium license supports | ||
Line 38: | Line 80: | ||
After the license has been accepted, Management Suite must be restarted for the premium features to be registered. | After the license has been accepted, Management Suite must be restarted for the premium features to be registered. | ||
In windows 10, Setup the | ===== Firewall setup ===== | ||
In windows 10, Setup the Windows Firewall by searching for FIREWALL and launching Windows Firewall advanced. see our [[Install_Management_Suite#Configure_Windows_Firewall|installation instructions]] for other versions of windows. | |||
Select Inbound Rules from the the left column, then New Rule from the actions window on the right. | Select Inbound Rules from the the left column, then New Rule from the actions window on the right. | ||
Line 44: | Line 88: | ||
The new rule is for a ''Port'' - not a program - it is a TCP port 6 7 7 7. | The new rule is for a ''Port'' - not a program - it is a TCP port 6 7 7 7. | ||
The rule allows the connection to the port and is applicable for all types of connections. We'll name it | The rule allows the connection to the port and is applicable for all types of connections. We'll name it | ||
Launch management suite and open the ADMINISTRATOR options panel. | Chime Remote | ||
===== Setup the remote server host ===== | |||
Launch management suite and open the [[Administration_MS|ADMINISTRATOR options panel]]. | |||
To support the mobile remote app, we need to enable the host server when we start management suite. For this setting to take effect, we have to restart the management suite. | To support the mobile remote app, we need to enable the host server when we start management suite. For this setting to take effect, we have to restart the management suite. | ||
After restarting Management Suite, open the ADMINISTRATOR options again. Make a note of the App Host Address. This is the address of this PC on the local area network. | After restarting Management Suite, open the ADMINISTRATOR options again. Make a note of the [[Administration_MS#Setting_up_the_mobile_app|App Host Address]]. This is the address of this PC on the local area network. | ||
After we connect the mobile app to the network it will be able to reach the bell system host PC at this address. '''Note''' that this address probably will eventually change by itself unless it is made ''static''. Your IT person can make this happen. | After we connect the mobile app to the network it will be able to reach the bell system host PC at this address. '''Note''' that this address probably will eventually change by itself unless it is made ''static''. Your IT person can make this happen. | ||
Next we will add User Accounts for those who will be logging into the bell system using mobile apps on their phones and tablets. You should set up a separate user for each phone or tablet that will be used. | Next we will add [[Administration_MS#Mobile_App_User_Permissions|User Accounts]] for those who will be logging into the bell system using mobile apps on their phones and tablets. You should set up a separate user for each phone or tablet that will be used. | ||
First add Father Russ and set his password to rusty. We will trust him to do the right thing with access to all functions at all times. | First add Father Russ and set his password to rusty. We will trust him to do the right thing with access to all functions at all times. | ||
Line 66: | Line 114: | ||
We have to leave the management suite running with the main menu up at all times in order for the remote app to connect to the bell system. You can lock the PC while remaining logged in to prevent others from accessing the bell system through the PC's keyboard and display. | We have to leave the management suite running with the main menu up at all times in order for the remote app to connect to the bell system. You can lock the PC while remaining logged in to prevent others from accessing the bell system through the PC's keyboard and display. | ||
== Setup mobile app == | |||
Requirements: | |||
* Apple or Android tablet or phone | |||
* Internet connection to Play or App store | |||
* Local WiFi connection to same network as host PC (Internet optional) | |||
=== Outline === | |||
# Connect phone or tablet to the Internet | |||
# Find and install Church Bell Remote Control from the [https://itunes.apple.com/us/app/church-bell-remote/id673198843 App Store] or [https://play.google.com/store/apps/details?id=com.chimemaster.churchbellremote Play Store] | |||
# Connect phone or tablet to the local church WiFi network (Internet connectivity is optional) | |||
# Add host with IP address from host Management Suite setup notes | |||
# Login to the user given permissions in Management Suite setup | |||
# Test functionality | |||
=== Video script === | |||
==== Install the remote control app ==== | |||
Next we will set up the mobile app on the phone or tablet. | Next we will set up the mobile app on the phone or tablet. | ||
Line 72: | Line 139: | ||
We have to connect the phone to the Internet either through 4G or the church wifi network to get the app installed from the App Store or Play Store. | We have to connect the phone to the Internet either through 4G or the church wifi network to get the app installed from the App Store or Play Store. | ||
Launch the Store and search for CHURCH BELL REMOTE. Find the Chime Master Church Bell Remote | Launch the [https://itunes.apple.com/us/app/church-bell-remote/id673198843 App Store] or [https://play.google.com/store/apps/details?id=com.chimemaster.churchbellremote Play Store] and search for CHURCH BELL REMOTE. Find the Chime Master Church Bell Remote. | ||
Tap the INSTALL button. | Tap the INSTALL button. | ||
The app will install automatically after it downloads, then we will exit the store. | The app will install automatically after it downloads, then we will exit the store. | ||
==== Connect the phone to your WiFi ==== | |||
At this point, we need to be sure that we are connected to a wifi access point that is on the same local area network as the host PC that is running Management suite | At this point, we need to be sure that we are connected to a wifi access point that is on the same local area network as the host PC that is running Management suite | ||
Then launch the app from the | ==== Setup the app ==== | ||
Then launch the app from the app icon button. | |||
The EULA is easy to agree with, and a reminder will pop up that we need to finish setting up our link to the host PC in the Settings menu. We are reminded again in the display at the top of the app. | The EULA is easy to agree with, and a reminder will pop up that we need to finish setting up our link to the host PC in the Settings menu. We are reminded again in the display at the top of the app. | ||
===== Add the host server ===== | |||
Tap the Settings button - then HOSTS - then ADD, to create a new link. | Tap the Settings button - then HOSTS - then ADD, to create a new link. | ||
Line 95: | Line 168: | ||
The selected host will be displayed next to Host here in the settings menu and also in the gray area at the top of the remote screen. | The selected host will be displayed next to Host here in the settings menu and also in the gray area at the top of the remote screen. | ||
==== Connecting and logging in ==== | |||
It may take a few seconds to make the connection. The connection timing can be lengthened in the SETTINGS menu if errors occur. | It may take a few seconds to make the connection. The connection timing can be lengthened in the SETTINGS menu if errors occur. | ||
Line 102: | Line 177: | ||
We will log in as Mike, remembering to capitalize his name the way we entered it in the User Accounts window of Management Suite. | We will log in as Mike, remembering to capitalize his name the way we entered it in the User Accounts window of Management Suite. | ||
After authentication, you will see the remote control buttons that are enabled for the user who is logged in. | After authentication, you will see the [[Church_Bell_Remote#Monitor_Level_and_Active_Zones|remote control buttons]] that are enabled for the user who is logged in. | ||
==== Using the remote ==== | |||
Tapping Monitor (plus) will turn up the inside speaker. After a tap on Peal the blue status line will indicate when we can tap PLAY to begin ringing. | Tapping Monitor (plus) will turn up the inside speaker. After a tap on Peal the blue status line will indicate when we can tap PLAY to begin ringing. | ||
Tap the STOP button when you want the bells to stop. (they will stop after a pre-programmed time anyway). The bell system indicates that it received an Operator Cancel and when the bells have finished ringing out, it indicates that it is in Standby mode awaiting our next command. | Tap the STOP button when you want the bells to stop. (they will stop after a [[Settings_MS_SixSS#Edit_Remote_Buttons|pre-programmed]] time anyway). The bell system indicates that it received an Operator Cancel and when the bells have finished ringing out, it indicates that it is in Standby mode awaiting our next command. | ||
Tapping the selection entry button opens an edit window for selection entry. Tap this window for the keyboard. | Tapping the selection entry button opens an edit window for selection entry. Tap this window for the keyboard. | ||
Line 114: | Line 191: | ||
Tap selection entry again to close the entry screen. | Tap selection entry again to close the entry screen. | ||
Tap the | Tap the back button (or home button) to close the remote control screen. This will log you out of the bell system. | ||
To remove the app from memory, tap | To [[Church_Bell_Remote#Exiting_the_App|remove the app from memory]], tap recent apps button and swipe the apps off of the screen. | ||
When you launch the remote the next time, you will not have to type anything to log in. It should be ready to go, so long as your phone is connected to the church WiFi and the correct host has been selected. | When you launch the remote the next time, you will not have to type anything to log in. It should be ready to go, so long as your phone is connected to the church WiFi and the correct host has been selected. | ||
== Recommended equipment == | |||
=== Windows PC === | |||
This is a requirement, but it doesn't have to be fancy. For remote access, Management Suite must be running in its server mode on a PC. The mobile application communicates with the PC which relays the commands to the carillon that is connected to the PC's USB port. | |||
If you don't connect the PC to the internet, you could use an old office PC running Windows XP. [https://www.google.com/?gws_rd=ssl#q=inexpensive+windows+laptop Inexpensive laptops] are available for less than $200 at most department and big box stores. | |||
What '''will not''' work: | |||
* Chromebooks | |||
* Apple or Android tablets | |||
* Windows RT | |||
* Windows 10s (the new student/sandbox version) | |||
=== Access point === | |||
In order to network your phone/tablet and the Windows PC together, WiFi is required. If the church doesn't have WiFi available, you can set up your own local area WiFi network using an access point. | |||
Old discarded internet routers with working WiFi radios can be used for local access points without an internet connection. New access points are not expensive. All of them need some setup using a connected PC. Some examples: | |||
* [https://www.google.com/?gws_rd=ssl#q=TP-LINK+TL-WA801ND TP-LINK TL-WA801ND Access Point] | |||
* [https://www.google.com/?gws_rd=ssl#q=nGenius+EAP350+N300 nGenius EAP350 N300] High-Power Access Point/WDS/Repeater | |||
== Troubleshooting == | |||
The most common problem is getting the mobile device and the PC running Management Suite on the same network. Often guest WiFi networks in the church are not connected or are firewalled from the office LAN. | |||
* If you are trying to connect to the public IP while in your facility, try turning WiFi off on your phone or tablet (no port reflection). | |||
* Check the mobile Remote Control app [[Church_Bell_Remote#Error_Messages|error messages]] | |||
* Try accessing the Management Suite host port from another PC browser. Enter the URL as IPaddress:Port (example: http://192.168.20.62:6777 the IP will be different for you) | |||
** You should see a screen from the Millennium Suite server. If not, troubleshoot the network and firewalls. | |||
[[Category:Management Suite]] | [[Category:Management Suite]] | ||
[[Category: | [[Category:Legacy_Products]] |
Latest revision as of 15:01, 3 June 2024
Our new Advanced eXperience Remote is now available! Call 800-344-7464 for upgrade information.
- If you are using one of our AX touchscreen products, the following instructions do not apply to you.
End of Life Notice
- This application is no longer available in the mobile app stores.
- Our current remote control for Advanced eXperience (AX) ringing systems replaces the Church Bell Remote app described below.
Call 800-344-7464 for upgrade information.
Setup Management Suite on host PC
Requirements:
- Chime Master 2200 series bell ringing system
- A license code for the Premium Management Suite option
- PC running Windows operating system
- .NET framework 2.0 or greater installed
- LAN or WLAN connection to the PC with WiFi access
- USB cable to connect the bell ringing system to the PC
Outline
The Church Bell Remote mobile app requires that you have a networked PC running Management Suite connected to the USB port of your bell system. You must install and configure Management Suite on the host PC before setting up the mobile app on your phone or tablet.
- Download the Management Suite installation files from: www.chimemaster.com/downloads
- Do not connect the bell system to the PC USB port until after you install the software.
- Disable third party antivirus programs on the PC during Management Suite installation.
- Install .NET if it is not on the PC already
- Run the installer (as administrator if possible).
- Plug the bell system into the USB port of the PC and wait for the drivers to load.
- Set up the desktop icon to run Management Suite as an administrator (see below).
- Start Management Suite. You may be warned that the program wants to make changes to you computer. This is normal for server software.
- Test functionality of Management Suite by launching the local Remote Control screen on the PC. You should see a copy of the carillon front panel display. Close the Management Suite Remote Control window.
- Apply your license code to Management Suite and close the program.
- Set up the Windows Firewall to allow incoming data from the remote control port (TCP 6777).
- Restart Management Suite. The splash screen should indicate that it is licensed to support the mobile apps.
- Open the Administration program from the Management Suite menu.
- Enable the mobile app server and restart Management Suite.
- Open the Administration screen and write down the host IP address for later entry in the mobile app. Add separate users for each mobile device. Remember the login credentials for each.
- Close the Administration program, and restart the Management Suite. It must be running at the main menu for the mobile app to connect to the bell system.
Video script
Download and install Management Suite
We are going to set up the Chime Master Church Bell remote mobile app.
First we will set up the Management Suite (download-link) on our host PC. Click the link and the file will begin to download.
We have removed the instruction to disconnect the system during installation. Also if Windows has been installed from a downloaded upgrade, .NET will not be installed. If .NET is not installed, see .NET Setup.
Also temporarily disable any third-party antivirus software before running the installer.
When the installation zip file has finished downloading, open it. We can close the browser window, find the setup application and double click it to begin.
Let's move the setup window off to the side so we can see when drivers install.
Agree to the EULA. next next next.. The software requires the .NET framework which is usually already a part of newer Windows systems. ... and close.
( strikethrough - connect the bell system to the host PC and) Wait for the drivers to install for the Millennium+ carillon. A notification that it is "ready to use" will appear when it is finished or you can click on the device setup icon to watch its progress. (Do not attempt to start the program until driver installation is complete - this may take a few minutes.)
Start and setup Management Suite
Right click the desktop start icon. Notice that the default action in bold is to OPEN. Select properties at the bottom of this context menu, click the advanced button and check RUN AS ADMINISTRATOR. OK OK continue ...
Right clicking the start icon, we see the bold default action is to RUN AS ADMINISTRATOR.
Let's launch Management Suite to make sure it is functional. When we launch the Remote screen, we should see a copy of the bell system's display. Close the remote screen, and notice that the menu only shows the functionality included with the free version of Management Suite.
Licensing
We can key in our license code to unlock the premium features by right clicking over the menu and selecting LICENSING
In addition to support for the mobile app - the premium license supports scheduling One time events and annual events Creating your own random play lists for each season and even more features for millennium and platinum carillons
After the license has been accepted, Management Suite must be restarted for the premium features to be registered.
Firewall setup
In windows 10, Setup the Windows Firewall by searching for FIREWALL and launching Windows Firewall advanced. see our installation instructions for other versions of windows.
Select Inbound Rules from the the left column, then New Rule from the actions window on the right.
The new rule is for a Port - not a program - it is a TCP port 6 7 7 7.
The rule allows the connection to the port and is applicable for all types of connections. We'll name it
Chime Remote
Setup the remote server host
Launch management suite and open the ADMINISTRATOR options panel.
To support the mobile remote app, we need to enable the host server when we start management suite. For this setting to take effect, we have to restart the management suite.
After restarting Management Suite, open the ADMINISTRATOR options again. Make a note of the App Host Address. This is the address of this PC on the local area network.
After we connect the mobile app to the network it will be able to reach the bell system host PC at this address. Note that this address probably will eventually change by itself unless it is made static. Your IT person can make this happen.
Next we will add User Accounts for those who will be logging into the bell system using mobile apps on their phones and tablets. You should set up a separate user for each phone or tablet that will be used.
First add Father Russ and set his password to rusty. We will trust him to do the right thing with access to all functions at all times.
Next we'll set up the account for the Sexton, Jerry. His password is justy. While strong passwords are encouraged, you want to remember that if you use strange characters you will have to find them on your phone's keyboard.
Jerry will only need the basic functions for funerals and weddings between 8 AM and 5 PM.
Finally add the Organist, Mike, with all features. His password will be musty.
We have to leave the management suite running with the main menu up at all times in order for the remote app to connect to the bell system. You can lock the PC while remaining logged in to prevent others from accessing the bell system through the PC's keyboard and display.
Setup mobile app
Requirements:
- Apple or Android tablet or phone
- Internet connection to Play or App store
- Local WiFi connection to same network as host PC (Internet optional)
Outline
- Connect phone or tablet to the Internet
- Find and install Church Bell Remote Control from the App Store or Play Store
- Connect phone or tablet to the local church WiFi network (Internet connectivity is optional)
- Add host with IP address from host Management Suite setup notes
- Login to the user given permissions in Management Suite setup
- Test functionality
Video script
Install the remote control app
Next we will set up the mobile app on the phone or tablet.
We have to connect the phone to the Internet either through 4G or the church wifi network to get the app installed from the App Store or Play Store.
Launch the App Store or Play Store and search for CHURCH BELL REMOTE. Find the Chime Master Church Bell Remote.
Tap the INSTALL button.
The app will install automatically after it downloads, then we will exit the store.
Connect the phone to your WiFi
At this point, we need to be sure that we are connected to a wifi access point that is on the same local area network as the host PC that is running Management suite
Setup the app
Then launch the app from the app icon button.
The EULA is easy to agree with, and a reminder will pop up that we need to finish setting up our link to the host PC in the Settings menu. We are reminded again in the display at the top of the app.
Add the host server
Tap the Settings button - then HOSTS - then ADD, to create a new link.
You may later create a separate entry for the same system that you use while connected to the Internet from anywhere. This is an advanced topic, so for now we will name this host
wifi at church
We need to edit the IP Address to match the one we made note of from the Management Suite's ADMINISTRATOR options panel.
Tap the name of the connection in the list to make sure it is selected before returning to SETTINGS.
The selected host will be displayed next to Host here in the settings menu and also in the gray area at the top of the remote screen.
Connecting and logging in
It may take a few seconds to make the connection. The connection timing can be lengthened in the SETTINGS menu if errors occur.
Once connected to the host, we are prompted for the User and Password for this phone.
We will log in as Mike, remembering to capitalize his name the way we entered it in the User Accounts window of Management Suite.
After authentication, you will see the remote control buttons that are enabled for the user who is logged in.
Using the remote
Tapping Monitor (plus) will turn up the inside speaker. After a tap on Peal the blue status line will indicate when we can tap PLAY to begin ringing.
Tap the STOP button when you want the bells to stop. (they will stop after a pre-programmed time anyway). The bell system indicates that it received an Operator Cancel and when the bells have finished ringing out, it indicates that it is in Standby mode awaiting our next command.
Tapping the selection entry button opens an edit window for selection entry. Tap this window for the keyboard.
Amazing Grace is selection 1 2 2 5 , then DONE
Tap selection entry again to close the entry screen.
Tap the back button (or home button) to close the remote control screen. This will log you out of the bell system.
To remove the app from memory, tap recent apps button and swipe the apps off of the screen.
When you launch the remote the next time, you will not have to type anything to log in. It should be ready to go, so long as your phone is connected to the church WiFi and the correct host has been selected.
Recommended equipment
Windows PC
This is a requirement, but it doesn't have to be fancy. For remote access, Management Suite must be running in its server mode on a PC. The mobile application communicates with the PC which relays the commands to the carillon that is connected to the PC's USB port.
If you don't connect the PC to the internet, you could use an old office PC running Windows XP. Inexpensive laptops are available for less than $200 at most department and big box stores.
What will not work:
- Chromebooks
- Apple or Android tablets
- Windows RT
- Windows 10s (the new student/sandbox version)
Access point
In order to network your phone/tablet and the Windows PC together, WiFi is required. If the church doesn't have WiFi available, you can set up your own local area WiFi network using an access point.
Old discarded internet routers with working WiFi radios can be used for local access points without an internet connection. New access points are not expensive. All of them need some setup using a connected PC. Some examples:
- TP-LINK TL-WA801ND Access Point
- nGenius EAP350 N300 High-Power Access Point/WDS/Repeater
Troubleshooting
The most common problem is getting the mobile device and the PC running Management Suite on the same network. Often guest WiFi networks in the church are not connected or are firewalled from the office LAN.
- If you are trying to connect to the public IP while in your facility, try turning WiFi off on your phone or tablet (no port reflection).
- Check the mobile Remote Control app error messages
- Try accessing the Management Suite host port from another PC browser. Enter the URL as IPaddress:Port (example: http://192.168.20.62:6777 the IP will be different for you)
- You should see a screen from the Millennium Suite server. If not, troubleshoot the network and firewalls.