LabVIEW
Need labVIEW assistance
It is highly unlikely that you will get folks to give you their email address, what with the prevalence of SPAM. You might, however, get a number of business cards from folks willing to do the work for you. 
With a situation such as this you should first model the system, and develop an overall operational diagram of the system. Write down what the input conditions are to the various components, how the components interact, and what causes a component to behave a certain way. What kind of requirements do you have? Which requirements are must-have, which are kind-of-nice to have, and which are gravy? A state machine will go a long way in helping to document the system. Remember that before you plop down a single function or element on a LabVIEW program you must have a clear idea of what you're trying to implement and how it works. Perhaps you might want to look into UML as a way of modeling your system. Once you've gotten past that stage then you need to determine the implementation details. You've written down the way the system operates, now you need to detemine how you want the program to behave. What kind of user inputs do you have? What kind of data are you dealing with? Do you have synchronous and/or asynchrounous processes? You may find that LabVIEW isn't the best language to use to implement an application for your system. Doubt it, but you never know.
And there's always:
To learn more about LabVIEW it is recommended that you go through the tutorial(s) and look over the material in the NI Developer Zone's Learning Center which provides links to other materials and other tutorials. You can also take the online courses for free.
With a situation such as this you should first model the system, and develop an overall operational diagram of the system. Write down what the input conditions are to the various components, how the components interact, and what causes a component to behave a certain way. What kind of requirements do you have? Which requirements are must-have, which are kind-of-nice to have, and which are gravy? A state machine will go a long way in helping to document the system. Remember that before you plop down a single function or element on a LabVIEW program you must have a clear idea of what you're trying to implement and how it works. Perhaps you might want to look into UML as a way of modeling your system. Once you've gotten past that stage then you need to determine the implementation details. You've written down the way the system operates, now you need to detemine how you want the program to behave. What kind of user inputs do you have? What kind of data are you dealing with? Do you have synchronous and/or asynchrounous processes? You may find that LabVIEW isn't the best language to use to implement an application for your system. Doubt it, but you never know.
And there's always:
To learn more about LabVIEW it is recommended that you go through the tutorial(s) and look over the material in the NI Developer Zone's Learning Center which provides links to other materials and other tutorials. You can also take the online courses for free.
