Welcome to Workers for LabVIEW
Create asynchronous LabVIEW applications efficiently
Last updated
Create asynchronous LabVIEW applications efficiently
Last updated
Welcome to Workers for LabVIEW! Our mission is to provide you with a robust framework and the essential tools needed to efficiently create scalable asynchronous applications in LabVIEW.
Workers is based on the Queued Messenger Handler (QMH) design pattern, and a Workers QMH is designed to have the same look and style as the LabVIEW QMH template that ships with LabVIEW. Familiarity with this or with the 'Producer-Consumer' design pattern is recommended to comfortably start developing with the framework.
While being simplistic in its development style, Workers is also an Object Oriented (LVOOP) framework, allowing developers to develop their applications using inheritance, reducing the amount of re-work and duplicated code required by each modular QMH (called a Worker).
The Workers SDK provides you with a framework API, tools for creating and integrating Workers into multi-process applications, tools to create Worker APIs and HALs, and a debugger for runtime management on your local network. Workers applications can also be created and deployed on NI real-time embedded platforms (such as a CompactRIO).
This documentation will guide you through the framework's core concepts, Worker APIs, and development tools, helping to get you started developing with the framework as soon as possible.
This style is well-known in the LabVIEW community and is easy for both beginner and advanced developers to understand and work with. The framework allows you to create modules (called Workers) with each module's Main VI designed in the style of the LabVIEW QMH template, featuring a Message Handling Loop (mandatory) and an Event Handling Loop (optional).
Workers allows you to create reusable modules that plug together to form application trees. These application trees offer a structured, scalable architecture, and can be built from both statically-linked modules and dynamically loadable modules. The initialization and shutdown sequences of all modules are managed sequentially by the framework from the top to the bottom of the tree.
Worker APIs can be created using the Workers development tools, allowing you to create Workers that are decoupled from their Callers. This makes each Worker highly reusable across projects, easier to test, and sharable with other developers. Asynchronous messages are exchanged between a Worker and its Caller as Requests (to a Worker) and Responses (to a Caller), providing structured message flow that is easy to follow and understand.
Sometimes you need to provide your applications with the flexibility to load interchangeable hardware drivers at run-time. API Abstractions can help you here, where in place of a concrete module, you instead use an API abstraction, and at run-time decide which implementation of the abstraction you want to load into your application. Thanks to the framework's foundational use of LVOOP, the Workers SDK allows you to create Worker HALs using the native architecture of the framework.
Workers 5.0 was first presented and introduced to the LabVIEW community at the GLA Summit in March 2024. The video below is the recording of this PowerPoint presentation. This presentation introduces the Workers framework, while focusing on what's new in Workers 5.0, discussing how to create Worker APIs and how to create API Abstractions using the new Public API Builder tool.
Good to know
You do not need prior experience with LVOOP to start developing with Workers. The framework is designed to be user-friendly for developers without LVOOP knowledge. Start your first project and as you gain LVOOP skills, you can explore the advanced features of the framework, such as creating Hardware Abstraction Layers (HALs) and overriding framework API VIs.
