Files
docs/content/articles/2025-04-23-NonInvasiveTesting.md
Michael Housh e1bf53bd70
All checks were successful
CI / release (push) Successful in 7m7s
feat: Adds non-invasive testing article.
2025-04-23 09:49:15 -04:00

2.9 KiB

date, tags
date tags
2025-04-23 service, procedure, measureQuick

Non-Invasive Testing

In this article we will walk through when and when not to use non-invasive testing in measureQuick.

The Challenge

Non-invasive testing is an awesome feature of measureQuick and something that was extremely challenging prior to tools like measureQuick because a service technician needed to know how to do all the math and know what the targets were.

However, for non-invasive testing to work properly in measureQuick, the system needs to be benchmarked first using an invasive test to set the baseline of the system. This is because measureQuick will compare the current conditions to the benchmarked conditions.

When running a non-invasive test on a system that has NOT been benchmarked then a "score" will not be generated and the reports look incomplete, such as the below image.

non-invasive

Our Responsibility

It is our responsibility and goal during maintenance visits to truly assess the system operation and performance, so that we can catch premature failures before they occur as well as offer options to improve the system performance.

Tools like measureQuick and Bluetooth probes make this possible, but only when the tools are used properly.

Flags and errors need to be individually assessed and not be glossed over. Any flags that can be resolved with normal maintenance should be addressed at the time of the service. A solution / reason should be documented as to why it couldn't be, what is causing it, and options should be offered to resolve if the customer would like to do so.

Non-Benchmarked Systems

Non-benchmarked systems are indicated by a red thumbprint on the profile button, and will say "Not Benchmarked" when clicking into the profile. If a system is not benchmarked, then an invasive test should be performed, all errors should be resolved (or as many as possible), then the system should be benchmarked so that non-invasive tests can be performed in the future.

profile-1 profile-2

Invasive Testing

A non-invasive test is best practice, however it does not mean that it is the only thing that should be used. If a non-invasive test indicates there may be a charge problem, then it should be transitioned into an invasive test. In other words, a non-invasive test should be used to know if you need to do an invasive test or not.

Invasive tests are less problematic than they were when technicians used manifold gauges with long hoses that could be contaminated. With the use of probes and no hoses, these concerns are much less.

Conclusion

In conclusion, do not use non-invasive testing on systems that are not benchmarked. Do use non-invasive testing on systems that are benchmarked. Do not think that a non-invasive test is the only way to do it. When in doubt fall back to an invasive test.