By using Active X or the NI LabVIEW Report Generation Toolkit you can match your timestamps in LabVIEW with your timestamps in Excel.
Here’s a file path to filter out unnecessary data, allowing you to automatically update the file path so your VI will only save data that meets your special criteria.
Some of the most common human activities are actually rather complex. Take walking, for example. It is a “repetitive process that requires the coordination of the lower limbs to move forward and maintain body balance with one foot in contact with the ground at all times.”
Darwin Gouwanda and Arosha Senananayake are two engineers from Monash University in Malaysia who developed an application that analyzes stride, stance phase, and swing phase – things that occur between the heel-strike to another heel-strike of the same foot (otherwise known as a gait cycle). Acute injury to one of the limbs can disrupt this process and cause abnormal gait. Significant differences between normal and abnormal gait can be found in the duration of a stride, stance phase, and swing phase. To quantify these parameters and study a person's gait, they developed a wireless gyroscope-based gait monitoring system to help them diagnose and track the rehabilitation progress of patients.
The gait monitoring system measures the angular rates of the lower limbs, and identifies and quantifies gait cycles. They used LabVIEW to develop a user-friendly GUI and collect simultaneous real-time data streaming from two wireless gyroscopes, which is in turn sent to a workstation. Using the LabVIEW Advanced Signal Processing Toolkit shortened the development time and reduced the tedious programming work because it offers comprehensive signal processing tools and algorithms.
Just another example of how engineers use NI tools to improve everyday life.
Community macaba has a piece of code available on the community that allows you to easily send data from a running VI to a UI mockup of the VI on your iOS device. It uses a special version of the UDP protocol to send data back and forth. The direct applicaitons I see this benefiting is when you want to control a VI remotely and want to use devices that are commonly available (e.g. I want to turn off that valve from my iPhone while I travel) and also for just remote viewing as well (e.g. I just want to see what the temperature if on my applicaiton from anywhere). Go check out macaba's example and see if it could fit into your LabVIEW application!
Commmunity member DBiel has submitted an example showing how to programmatically determine what cDAQ modules are in a chassis. This example uses LabVIEW and built-in DAQmx property nodes to communicate with a chassis and return an array of module information. This can be really useful during the startup phase of an application to make sure that the chassis is configured correctly before starting any data aquisition or other activities.
The example in the NI Community is called Get cDAQ Module Types in LabVIEW.