MCP (Model Context Protocols) is a plugin interface for large language models (LLMs). It allows an AI chatbot to call functions autonomously. Using the MCP toolkit for LabVIEW an AI Agent can call LabVIEW VIs based on their description to complete a given task. This also enables LLMs to call VI-Scripting functions to generate code which is very experimental, but an exciting usecase.
NI now ships official LabVIEW container images and a licensing model built for automation — but going from "I have a container" to a real CI/CD workflow still takes work. This session presents an open-source reference implementation that does exactly that, and that you can copy into your own repositories.
We'll walk through how it uses NI's containers and the new licensing to run headless LabVIEW on GitHub Actions, and how it parses the .vipc and .dragon files in your repo to build a dependency-matched image stored in your own GitHub Container Registry. On top of that foundation it delivers a rich workflow: whole-project Mass Compile, VI Analyzer reports, visual VIDiffs, a searchable VI Browser, unit tests, and a live dashboard — all on every commit.
The goal is a working example you can learn from and reuse, with a one-click installer to apply it to your own repos in minutes.
Developers transitioning from desktop LabVIEW applications to Real-Time (RT) targets often hesitate to adopt advanced software architecture due to concerns about determinism, performance, and resource constraints. This presentation demonstrates that the Delacor Queued Message Handler (DQMH) framework can be successfully applied to LabVIEW Real-Time applications when designed with modularity and deterministic execution in mind. It discusses architectural principles such as minimizing module dependencies through a dedicated Controller Module, organizing software according to hardware or business processes, and separating user interface functionality from RT code. A proof of concept implemented on an NI myRIO using LabVIEW Community Edition 2025 validates the approach, showing reliable execution with low jitter and execution times well below a 10ms Timed Loop period. The results suggest that DQMH provides robust, scalable, and maintainable architecture for Real-Time systems, making it a practical choice for applications ranging from compact embedded controllers to larger Compact RIO and PXI-based platforms.
Omni-Bus is a LabVIEW library that provides a common value-based abstraction for both application data and external I/O, including interfaces such as Modbus and UDP. By exposing these different data sources through a unified interface, Omni-Bus helps reduce coupling, simplify integration, and support cleaner, more scalable, and more maintainable LabVIEW architectures.
Security professionals often use TableTop exercises to talk through a "what would we do if ..." scenario. It's a great way to think about what you would do. It also helps to point out where existing policies and safeguards might need updated and where policies and safeguards might need added. I will walk through 3 scenarios that are guaranteed to get you thinking and give you something to talk about with your team.