01-04-2017 02:59 PM
I've used labview for interfacing with a DAQ that connects to external sensors for collecting all kinds of data. As the other guy mentioned, you don't seem to really know what labview is. Labview is a programming environment. Less like Excel, and more like the visual basic programming you can do in excel to create macro's. You can do pretty much anything with it, and interfacing with instruments and data acquisition is probably the greatest strength labview has. Interfacing and data acquisition is largely plug and play, where in a C based language you would have to work a heck of a lot harder to import data from a new instrument.
A better question would be “Is your Labview engineer more experienced and capable than whatever mad scientist wrote you a visual basic macro to interface with a microphone and collect real time data for you?”
If the answer is no, stick with the mad scientist. But you probably shouldn't be doing what your doing now if messing up means anyone can be harmed.
01-04-2017 03:11 PM
I (and surely many others) have used Labview for collecting accelerometer input.
But once again, you must understand that Labview is a programming language. What is it that you want to do with your data?
If you need to build up advanced vibration analysis programs, check out the Sound and Vibration Toolkit, however: http://sine.ni.com/nips/cds/view/p/lang/sv/nid/209056