The automotive category contains case studies and blogs related to ITM’s engineering and testing services for automobile design and manufacture.

Another Successful Condition Monitoring System Installation

Last week our team successfully and safely installed another Boiler Monitoring System (BMS).  This system, a Sootblower Fouling Detection (SFD) system, monitors structural and vibration sensors that quantify the boiler’s response to sootblower operations. The SFD system analyzes the boiler response data and outputs Key Performance Indicators (KPIs) such as fouling level, sootblower efficiency, and sootblower health to automated boiler cleaning systems.

This boiler uses over 50 sootblowers located at different elevations to clean soot build-up from boiler steam tubes.  Since the vibration measurement locations are relatively far apart, the SFD system requires a distributed monitoring system consisting of several junction  boxes that monitor and process data for groups of sensors.  One team of engineers mounted the vibration sensors to the sootblowers and confirmed communication back to a local junction box containing the National Instruments condition monitoring hardware.  The other team installed the junction box panels and terminated the sensor cables.

After all the sensor installations and terminations were completed, each sensor’s location and calibration were verified.  While the sensor verification was being completed, one engineer worked with the mill IT department and the controls engineer to establish remote connection to the system and confirm communication with the mill’s automated cleaning system.

After commissioning the system and returning to our home base, our engineers are now monitoring the system through a VPN connection and assisting boiler operators with optimizing their cleaning process.

For more information about our boiler condition monitoring systems, contact Ryan Welker via email at or phone @ 1.844.837.8797 x702

Machine Failures Caused by Intermittent Damaging Events

Over the years we have been tasked with identifying the root cause of machine structural failures. In many cases, we can determine the failure mode through strain and vibration testing, order analysis, modal analysis, and operating deflection shape analysis.  What tests can you run when the damaging conditions are intermittent and not easily identified?

In these cases, we like to install a cellular networked temporary data acquisition (DAQ) system that can autonomously log vibration and strain data along with machine status data. We have deployed two types of DAQ systems to collect data remotely.  An interactive system that includes an industrial PC running our iTestSystem software and National Instruments (NI) Compact DAQ hardware and a headless system that utilizes NI Compact RIO hardware.  Our test engineers prefer using the interactive solution for troubleshooting because they can view real-time signal waveforms and collected data files, and then adjust the test parameters accordingly without having to reprogram the hardware.

Rugged Measurement System

Figure 1: Headless networked data acquisition system

When potentially damaging events are identified in the vibration and strain data collected by these systems, it is important to know the machine’s operating status. Collecting the machine status information is just as important as collecting the structural data.  Many machines transmit these operating variables and operating stages over their network/bus.  Recently we have recorded process data from Allen Bradley Control Logix PLCs via Ethernet/IP, mining machine data from a Siemens controller via proprietary TCP/IP protocol, boiler condition data from a DCS via Modbus TCP,  machine pressures from PI historian via the UFL connector (TCP), and vehicle speeds and pressure via CAN.  Fortunately, we were able to use and adapt LabVIEW communication protocol tools to build applications and addons that allow this network tag data to be collected along with structural data.

LabVIEW Modbus to Shared Variable Code

Figure 2: Modbus to Shared Variable Tool

After the data collection phase, our engineers perform statistical analysis on the sensor and status channels in all data files and aggregate the results into a database for searchability. To identify the root cause probabilities, you can process the channel statistics data using your favorite correlation algorithm or application.  The image below shows an example data set containing related sensor data that was processed using a LabVIEW correlation test tool.

LabVIEW Correlation VI

Figure 3: Correlation Test Example vi

Contact Information: For more information about our remote data acquisition service, our LabVIEW development service, or iTestSystem contact:

Mark Yeager – Integrated Test & Measurement (ITM), LLC.  Email: or Phone: 1.844.TestSys

Recent News:  Ohio University Asphalt Cracking Prediction System Project

Strain Gauge Installations for Field Testing

Image1: Shaft torque strain gauge installation example for field testing

Our engineers and technicians have epoxied, soldered and spot welded strain gauges for applications ranging from high temperature exhaust systems to miniature load cell measurements. Every application requires a unique understanding of the strain measurement requirements including installation environment.

If the strain gauge installation is to survive in the field you must plan for the conditions it will undergo. Three important variables that you should account for are temperature range, liquid exposure, and potential impact forces. These variables determine the type of strain gauge, epoxy, solder, wiring, coating, and impact/wear protection to use in the application. The table below shows which variables affect your installation choices.

Liquid Exposure   
Impact Forces   

Table1: Strain gauge installation variables

For more information about ITM’s strain gauging services contact Ryan Welker at email: or phone: 1.844.837.8797 x702

Roving Accelerometer Impact Tests with iTestSystem

3D Animator: Bike Frame Twist Vibration Mode at 26.2 Hz

In order to prevent or troubleshoot structural vibration problems, it is important to characterize a structure’s dynamic behavior using both experimental and Finite Element Analysis (FEA) technologies.  One method used to identify a structure’s vibration modes is to perform a roving accelerometer or roving hammer impact test.  In an impact test, engineers measure the response of a structure from an impulse delivered by a calibrated hammer using tri-axial accelerometers.

FRF View: Bike Frame Point 9 Coherence & Magnitude

Managing impact tests on large structures can be tedious and cost prohibitive, since they require collecting accelerometer responses at hundreds of locations to resolve the vibration motion.  Not only do test engineers need to keep track of the locations, they also need to keep track of the orientation that an accelerometer is positioned.

Our test engineers have found that the most efficient and cost effective solution for collecting impact data is to use a National Instruments (NI) cDAQ chassis with either NI-9234, NI-9232, NI-9231 or NI-9230 IEPE modules along with a calibrated impulse hammer and between 3 – 9 tri-axial accelerometers. To collect, manage, and visualize the modal data, our LabVIEW software engineers developed the Impact Test DAQ, FRF Viewer, and 3D Animator applications for our iTestSystem software platform. These applications incorporate tools that our test engineers need to manage and validate the quality of their modal data while in the field.

For more information about impact tests, modal analysis, our iTestSystem Impact Test applications, or to schedule a modal test contact Mark Yeager or Ryan Welker.

Click Here to download iTestSystem

Building a Modern User Interface in LabVIEW

When we develop LabVIEW™ applications for our customers, a common request is for a simple, resizable and intuitive user interface (UI) for data visualization.  In these cases, we use a tree control and a subpanel.  This type of UI functions like a tab control that automatically resizes.  The main benefit of using a subpanel is to make your code more modular.

Figure 1: Modern User Interface with a Tree and Sub Panel.

To illustrate the modularity that this type of UI creates, I made an example LabVIEW™ project.  The main VI shown above uses a tree control to switch between a VI containing a graph and a VI containing a table.  I used our multi-queue event architecture for VI information communication messaging.  The image below shows the main VI’s significant functions.

Figure 2: Main VI’s Block Diagram – Significant Functions

The main VI’s functions are listed below.


  1. Initialize queues and events and then generate initialize event.
  2. Initialize tree and add tree items.
  3. When a user selects an item in the tree, generate data and then send it to the subpanel VI.
  4. Receive SubPanel Ready event from a subpanel VI and then insert the VI into the subpanel.
  5. Destroy queues and unregister for events.

In this example the subpanel VIs are very simple.  They populate an indicator (table or graph) and then generate a SubPanel Ready Event.  The two (2) subpanel VIs and block diagrams are shown below.

Figure 3: SubPanel VIs: and

Contact Information: For more information on this example or our LabVIEW development service contact:

Mark Yeager – Integrated Test & Measurement (ITM), LLC.  Email: or Phone: 1.844.TestSys