Tag Archive for: 85

100 Things #85: Integrate Soundcheck Data With Your Database

Using SoundCheck as part of your test setup and database is easy. SoundCheck’s data can be saved directly to Microsoft Access or an SQL database, all from within a sequence. This includes curves, values, results, and waveforms. SoundCheck’s autosave sequence steps can automatically gather, format, and export sequence data. Plus, with TCP/IP integration, SoundCheck’s data can be accessed and ready to use in your own program.

Integrate Soundcheck Data With Your Database

Learn more about SoundCheck integration

SoundCheck includes examples scripts for externally controlling SoundCheck via TCP/IP. C sharp, C++, LabVIEW, MATLAB, and Python examples are included.

Our SoundCheck tutorial series covers everything you need to know to get testing with SoundCheck, including how to configure SoundCheck autosave steps with a database. Check out the Autosave to Database tutorial, or the full tutorial playlist.

The SoundCheck manual gives detailed written instructions on setting up your database with SoundCheck, configuring TCP/IP connections, and more.

Video Script:

SoundCheck performs many measurements on your audio device – frequency response, sensitivity, harmonic distortion, perceptual distortion, transient distortion, directivity, pass/fail results and more. When you test hundreds, or even thousands of devices a day on a production line, that’s a lot of data. Everyone wants to manage this differently, so we offer several different database options for seamless integration with your manufacturing and business intelligence systems.

Directly in a SoundCheck step, you can save your curves, values, results, or waveforms to a database. Using an autosave step you can make a connection to a Microsoft Access or SQL database so that whenever your sequence runs,  the data is sent to the database. Industry standard tools can then be harnessed to run analytics over large data sets. For example, a procedure could be created to examine the frequency response on all measured devices on the database and create limits based on the average. 

Even if you’re not using a database, SoundCheck still has options to get your data into a format that’s easy to work with. In addition to the options shown directly in the autosave editor  – that’s text, csv, Excel, TDMS, Matlab .dat, .wfm, and.res, there’s also a plugin available to transfer data to WATS. WATS is a full test data management platform created by Virinco that can quickly and easily take production data and place it into dashboards to help see your production statistics at a glance. 

If these options aren’t enough, all the data, curves, and other  items saved in SoundCheck’s memory list, can always be accessed directly via TCP/IP. This means you can write your own customized program to collect exactly the SoundCheck data you need. Simply read the memory list items using a TCP/IP connection to the SoundCheck computer and you’ll have all the measurements ready to go in your own program. We have some very basic examples of this included with the Soundcheck installation in the external control examples folder, but the final product can be as specific to your use case as you need. 

Hopefully this brief introduction has demonstrated how SoundCheck’s flexible data management enables it to be easily integrated into your test environment. Check out the SoundCheck manual for detailed information on how to set up database connections, use TCP/IP and more.