Front_Screen

 

A research and development company needed a system to monitor their automated material dispensing system.  The measurement system needed to monitor pressure, flow, and digital signals from a robotic dispenser.   The software was required to work with hardware the customer previously owned along with modern USB data acquisition hardware.  The customer also wanted the same software to view the acquired data.

Continue Reading

Print

Energy_Test

An automotive customer that develops batteries needed a custom program to monitor and control an energy test.  The energy test consisted of 20 electrical loads connected to 20 battery cells that were controlled with a digital output.  Each cell needed be discharged until the cell reaches a user specified level.  The battery voltage needed to be monitored and saved to an excel file.  The excel file needed to be a template that contained a user defined macro for data analysis.

Continue Reading

Print

Gauge_Monitor

An automotive company needed a program to monitor two LVDT's from a measurement gauge.  The system needed to communicate with existing Marposs LVDT probes.  The software had to easily indicate to the user a good or bad part, allow for pass/fail criteria to be easily changed, and save data to file.

Continue Reading

Print

data_acquisition

A company manufacturing brake controllers for towing trailers needed an in-vehicle test system that monitored various quantities (i.e. brake temperature, vehicle speed, brake distance, etc). The company needed the system to be flexible enough to add or remove data channels as needed. They also needed a triggering function (i.e. when a data channel reached a certain level the data acquisition would begin). Logging the data to an excel file was required. A read back function was needed to display the data for analysis purposes.

Continue Reading

Print

mirror_measurement_front

An automotive supplier that manufactures side mirrors needed to upgrade their automated mirror testing station. The previous software required the operators to analyze the data from each run using a cumbersome software tool and transfer the results to a hand written report. The user interface wasn't intuitive, and required the operator to do a lot of manual set up. The operator also had to do a manual analysis to determine if the mirror passed or failed the test. Finally the data from each run could not be saved for later analysis.

 

Continue Reading

Print

More Articles ...

  • 1
  • 2