At Labvolution, we specialise in developing high-quality software solutions for automated electronic test systems, data acquisition applications and vision monitoring and analysis software. All bespoke software is based on National Instruments LabVIEW graphical programming language which connects with National Instruments, third party or custom hardware.
Labvolution director and founder Greg Payne is a National Instruments Certified LabVIEW Architect (CLA) and passionate electronics engineer with a specific interest in testing and diagnostics of electronics.
Previous projects include: production and regression testing for the automotive industry; production and programming tests for the communications industry; product test development within the manufacturing industry; verification and validation testing.
If you need support for your LabVIEW or test development projects, please contact us via the contacts page. We look forward to working together and making your next project a success.
April 29, 2016
Knowing how to include C# libraries into a LabVIEW project can be a very useful tool. There are many reasons why you would want to include C# dll’s into a LabVIEW project but the two that come up most often for me is reusing legacy code that was initially written in C# and writing a C# wrapper when wanting to use a third party driver or library. Sometimes it’s easier to write the wrapper in C# and then implement the library directly in LabVIEW. […]
April 11, 2016
Leading on from the LabSSH Library that I shared a while back, I have also created a LabSFTP LabVIEW library. From Wikipedia, SFTP can be described as follows: In computing, the SSH File Transfer Protocol (also Secure File Transfer Protocol, or SFTP) is a network protocol that provides file access, file transfer, and file management over any reliable data stream. […]
December 18, 2015
This week I attended my local LabVIEW User Group (CSLUG). I have been a member for a few years and can’t emphasise enough how much you can get out of a two (sometimes three/four) hour discussion once a quarter. Topics that are discussed can be anything from new and advanced ideas, different ways of documenting code, error handling and anything else that you have an interest in or need help understanding. […]