NIWeek 2016 Technical Session 9636
You are here
LabVIEW
The UTS Software Suite from Bloomy
May 24, 2016
A universal test system software architecture
Are you developing test sequences using NI TestStand? If so, beware that a lot more goes into a full test architecture than test sequences. In our experiences, test developers often focus solely on the test sequences and code modules, leaving items like file management, hardware abstraction, operator interfaces, and result processing all but forgotten until you run into a problem. Unfortunately, these items often take longer to develop, and require more in-depth TestStand knowledge than the test sequences themselves.
- Read more about The UTS Software Suite from Bloomy
- ggothing's blog
- Log in or register to post comments
LabVIEW Source Code for Google Charts Example
Google Charts
So You Want a LabVIEW Interface?
April 4, 2016
(Me too!)
What is an interface?
An interface is the set of methods, messages, or VIs (think connector panes) that we use to pass data in and out of a software module. Simply put, what are the inputs and outputs, and how do they get in and out? A software module could be a class, a library, or simply a repository of VIs (in descending order of author preference).
Why are interfaces useful?
- Read more about So You Want a LabVIEW Interface?
- Ethan Stern's blog
- Log in or register to post comments
In this video Bloomy's Turnkey Systems Manager, Grant Gothing presents the concepts and benefits of hardware abstraction for automated test equipment (ATE) design. Implementing a hardware abstraction layer (HAL) with NI TestStand can save you time, money, and frustration by reducing the impact of hardware changes, maximizing code reuse, and minimizing development effort, helping you to maintain ATE for years to come.
In this brief video recorded at NIWeek 2015, Jon McBee demonstrates a beta version of a custom integrated development environment (IDE) for dynamic configuration and control of microfluidics devices developed using NI LabVIEW. Jon explains how the use of agile software development, paired with a scrum-based approach to project management, allowed Bloomy to deliver a tremendous amount of value in an extremely short amount of time.
Getting Started with the Actor Framework – Part II
September 3, 2015
In the previous installment, we built a very simple program which consisted of a single actor and a single message. In this part we will create an application that is a bit more complex. This example consists of two actors: a DAQ actor which can read an analog voltage and a User Interface actor which provides a graphical user interface to display the data. Let’s get started!
This presentation studies two of the five S.O.L.I.D principles with LabVIEW: interface segregation and dependency inversion. The aim is to help LabVIEW users write better software by understanding architecture fundamentals from computer science.
Authors: Jon McBee, Senior LabVIEW Architect and LabVIEW Champion, Bloomy and Stephen Loftus-Mercer, Senior Software Engineer, National Instruments
Conference: NIWeek 2015, August 6, 2015, Austin, TX
All rights reserved.
Agile in Action – After the Sprint (Part 5 of 5)
August 19, 2015
Scrum is powerful because it takes a large amount of work--for which estimating the total effort needed for completion is very difficult--and breaks it up into several 2-4 week long well-defined sprints. At the end of each sprint, the team delivers tested, documented, working code that the customer can immediately interact with and use to inject feedback into the next sprint cycle. Before the code is handed off, the team holds two meetings: the sprint review meeting and the sprint retrospective meeting.
Agile in Action - Sprint Planning (Part 4 of 5)
July 31, 2015
Sprint planning meetings are held before the start of each sprint and are attended by product owner, scrum master and the entire development team. During the meeting the product owner describes the goal of the upcoming sprint and prioritizes the backlog of user stories based on that goal. The sprint goal is a concise description of what the sprint team plans to achieve in the upcoming sprint.
Pages
