1. Verify Equipment Hub connection by navigating to “Manage - Measurement Devices” and clicking the “Manage Equipment Hubs” button in the upper left corner:
Click the “Edit” button for the specific Equipment Hub to be tested:
Click the “Check connection” button in the upper right corner. A green text popup in the lower right corner indicates connection:
A red popup indicates a problem with the connection:
2. If you are using a Daily QA3 device and unable to connect, ensure that the Firebird Server is running from Windows Services. Open the Windows Services snap-in (on Windows 10 type "services" in the search bar) on the computer where Equipment Hub is installed, right-click on the Firebird Server service, and note the status. If Firebird Server is not running, right click on the service and click “Restart”. If a restart succeeds, confirm the connection by re-performing step 1.
3. If connecting to Daily QA, ensure that a version of Firebird compatible with the Daily QA3 database is used. Known compatible version is Firebird Server 32-bit v2.5.8.
4. If you are still unable to connect, confirm that the parameters are correct for the QA Equipment connected to the Equipment Hub. Start by noting connected equipment from the last screen in step 1:
Navigate to “Manage QA Equipment” and click “Edit” for each individual QA Equipment noted above, one at a time:
Verify that the device is active and the settings are correct:
For Daily QA 3 or QA BeamChecker Plus QA Equipment, confirm the database path, database user name, and database password.
For Fluke QA Equipment, confirm the com port.
For PIPSPro QA Equipment, confirm the PIPSPro username, PIPSPro password, and the server.
For each QA Equipment make any needed changes and click the “Check connection to equipment” button:
A green popup indicates success while a red popup requires further troubleshooting.
5. Confirm that the Equipment Hub software service is running by opening the Windows Services snap-in (on Windows 10 type "services" in the search bar) on the computer where Equipment Hub is installed, right-click on the Total QA Equipment Hub service, and note the status. If Equipment Hub is not running, right click on the service and click “Restart”. If a restart succeeds, confirm the connection by re-performing step 1.
6. Confirm that the computer on which the Equipment Hub software is installed can reach Total QA by navigating to https://tqa-eqhub.imageowl.com/ in a web browser. Below is a successful attempt:
An unsuccessful attempt will yield:
Typically if the connection to https://tqa-eqhub.imageowl.com/ fails it is because of insufficient permissions to access the site through a firewall. Equipment Hub communicates via HTTPS (port 443).
7. Ensure that the Equipment Hub service has permissions to access the location where the daily QA files are stored. If Equipment Hub will be accessing files that a local system account does not have rights to access, for example a network drive, a user who does have access rights must be assigned. To assign a user: open the Windows services snap-in, right-click on the Total QA service, select properties, and click the Log On tab. Click the This account radio button, and enter the information for the user account with access. Select the options that meet the needs of the site and click Ok.
8. Inspect the console to see the processing step and identify any potential problems. To open the console, navigate the the new QA page in question, right click anywhere on the page, click on inspect, and click the console tab in the upper right:
Each capture process is similar but there are differences. The example below is for an MPC import:
The next example below is from a Daily QA3 device:
9. If the connection continues to be problematic, obtain a copy of the Equipment Hub log for analysis. The log is named log.txt and is located in the install directory, typically at C:\Program Files (x86)\Total QA® Equipment Hub.
Note: If you see frequent issues with the Total QA Equipment Hub service at a particular site, it is recommended to set the recovery options to restart the service automatically. To set these options:
It may also be advisable to set the service for a delayed start. To configure this setting, open the Windows services snap-in, right-click on the Total QA service, and select properties. Click the Startup type drop down and select Automatic (Delayed Start) as shown below: