measureQuick FAQs

View solutions to commonly asked questions below. If you still can’t find the answers you’re looking for, try searching our Support Knowledge Base, or try our Community Forums.

  1. Make sure your Bluetooth is on
  2. Make sure the analyzer is not paired in the Bluetooth settings. If it is “forget this device”
  3. Make sure that your analyzer is not currently connected to the BluFlame application. Only one app can be connected at a time.
  4. Make sure that your analyzer is configured for iOS even if you have an Android phone. measureQuick only uses BTLE.
  5. Go to the toolbox and use the +add button to search for the BluFlame. If it does not find it the first time, search again.
  6. Tap save and connect


Your probes need to be mapped. Go to the toolbox and open the probe manager for the probe that is not transmitting to the display. Tap the probe and select its function from the drop down menu.


The red dot means that the probe has lost its connection. measureQuick will hold the last reading for a few seconds to several minutes depending on the reading. For example, RA temperatures do not change quickly so mQ holds those for a longer time. To get fresh data, you need to move back into range. If you are using Testo probes, they may have powered down due to the lost connection and need to be turned back on.


This is normal as new data comes in.

Green- means it is new data

Yellow- 1 second old

Orange- 3 seconds old

Red- means the connection with the probe has been lost

The further you are away from the probes and the more probes you are using the slower the data will come in.


A greyed out target means that you have not profiled the system and provided mQ the information that we need to determine the target zone. For example; without a TESP (total external static pressure) rating, we cannot tell if the static is in an acceptable range. Your system might be rated at .3″ wc or .5″ wc. Go to the “system information” page at the home screen and fill out the heating or cooling profile to get the target zones to show.


This is normal and an advantage of using mQ. Your TP chart and most apps do not determine or consider the average coil temperature. measureQuick calculates the average coil temperatures using the weighted midpoint or the midpoint of the refrigerant glide. This is so we can determine the target pressures based on design temperature differences and so that you know the coil temperature. The superheat and subcooling are calculated from the dew point and bubble point of the refrigerant.


It’s none of your damn business, but basically it’s a mass flow calculation. If we told you the secret, we’d have to kill you.

Solution: A high efficiency or oversized evaporator is elected when the evaporator is larger than the condenser (ie. the condenser is a 3-ton and the evaporator is 3.5-ton) to drive up the suction pressure and the efficiency by decreasing the compression ratio. This is often done to increase SEER. That said, many times is is also done to decrease static pressure drop across the coil, and the airflow is reduced to 350 CFM/ton to take the suction pressure back to typical. If you are shooting for the higher SEER and higher suction, turn the switch to “on” to adjust the target.


This typically happens when the user inputs an airflow that is much higher than the actual air flow of the system. Remove the user input airflow and remeasure or use the mQ estimated airflow calculation.


The most common issue is not having the probes mapped. Click the T/P button in the heating screen, then tap +Pres. See if you have data coming in from the manometer to the manifold pressure. If you do not, go to the tool box, from the probe manager select the probe that is measuring manifold pressure, tap it and map it to that function.

2 points of data are needed for the filter face velocity to show up on the report.

1.) Filter size: With a project open you can find this field under “Equipment Info & System Profile”, “Installation Information”

2.) Tonnage: This can be found under “Equipment Info & System Profile”, “System Profile”

After these data points are entered, the app will use the estimated airflow calculation to determine the filter face velocity.

Updated on August 19, 2020

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Tech Support

Leave a Comment