The activity starts with development: using LabVIEW, MS Paint, and our own creativity, we all create ornament designs that inspire us for the year. We then print them, laminate them, and hole-punch just like any paper ornament before the best part: hanging them on the tree!

The activity is a team effort, as after several years of festive ornaments, we must be selective about what makes the tree each year. This year, themes like AI, LabVIEW package managers, and our ongoing NASA project felt particularly topical to keep on the tree, as well as some classic LabVIEW icons and the Top Level at the top of the tree. If you want to check out some of the prior years’ events, you can find them here and here!

One of DMC’s core values is Have Fun, and we’ve found that our ornament tradition helps us do just that. It’s a great way to refresh your focus with some creativity and come together as a team to make something we can enjoy for the rest of the holiday season.

Celebrating the Season as an NI Platinum Partner

Our ornament tradition is also a reminder of how closely we work with NI technologies throughout the year. DMC is proud to be one of NI’s highest-ranked partners worldwide and the exclusive Platinum-level partner in the Americas. Since 1997, our teams have partnered with NI to deliver complete instrumentation, measurement, and automated test solutions for clients across a wide range of industries.

The same LabVIEW tools that spark our creativity during the holidays are the foundation of the work we do every day. Our engineers bring deep knowledge of NI products to projects involving LabVIEW programming, automated test equipment, real-time and FPGA development, and more. This expertise helps us design solutions that are consistent, scalable, and built for long-term success. Visit our NI partner page to learn more about our expertise.  

Got a creative LabVIEW idea you’d like to take a swing at? Contact us today to learn more about our Test & Measurement team and our LabVIEW tips and tricks beyond the icon editor!

The post Spreading Holiday Cheer with New LabVIEW Ornaments appeared first on DMC, Inc..

Figure 1: Functions Palette

Figure 2: QuickDrop

To complement QuickDrop, we have been working on DMC-Complete: a tool that has the potential to supercharge the way you use LabVIEW by predicting the blocks you need right when you need them.

Simply clicking on a block triggers the DMC-Complete interface to predict what block you are most likely to use next, speeding up the process of programming so you can focus on the logic of your code rather than the tedium of searching for a specific block.

DMC-Complete Offers:

• Blazing speed – predictions happen in milliseconds
• Fully local operation – no internet required
• Minimal resource usage – runs efficiently even on VMs
• Full library compatibility – works with custom and VIPM packages
• Strong privacy – your code stays on your device
• Easy retraining – add or remove packages with minimal effort
• Open-source access – check out the code, available under the BSD 3-Clause License

Getting Started

If you want to get started with using DMC-Complete, check out our repository where the code for this project lives: https://github.com/fadilf/DMC-Complete

The Installation and Usage sections of the README.md file should help you get up and running with the tool in no time! Keep in mind that the project is currently an early beta, so if you encounter any issues while using it, please file them on the GitHub page.

How It Works

At GDevCon NA in Chicago this year, DMC got a chance to give a talk on how the tool works in more detail!

Markov Chains

The key to understanding DMC Complete? Markov chains. A Markov chain can model a sequence of events in which the probability of each event depends only on a limited set of prior states. This approach can be used to model things as important as the weather or something as mundane as your opponent’s next move in rock-paper-scissors:

[…, , , ] → (50%) / (30%) / (20%)

[…, rock, paper, scissors] → rock (60%) / paper (30%) / scissors (10%)

These simple statistical relationships form the basis for predicting the next LabVIEW block in your block diagram.

Analyzing Block Diagrams

Figure 3

Let’s look at an example block diagram. We’ve got different types of blocks like controls, indicators, constants, DAQmx functions, etc., as well as a for loop structure. If we ignore structures, our block diagram looks like this:

Figure 4

We then genericize the blocks so we can treat them as Markov states for analysis. You might notice that this looks a lot like a directed acyclic graph.

Figure 5

Once we have this set of Markov states, we can start to observe patterns of blocks to make predictions later. If we count 2-block sequences, a pattern begins to emerge.

Figure 6

Figure 7

Once you have a table like figure 7, you can reorganize it into a Markov model, which looks more like this:

Figure 8

Now, when we see a numeric control, we know that the next block is either a Sine Wave (50% chance), a DAQmx Create Channel block (~33% chance), or a DAQmx Timing block (~17% chance). If we apply this process to our entire training set, including the example files included with LabVIEW and any libraries we install, we get a model that learns the pattern of how we code with the blocks we have.

This model is just a mapping/dictionary, so it only takes up a few megabytes on disk and in memory. Using it is as simple as a map lookup, so it’s an instant O(1) operation. Behind the scenes, there is a caching mechanism that takes place, so if you want to retrain with fewer/more files, the retraining process runs very quickly. The slowest part of training is the initial conversion of a VI file into a graph, which is why we have taken on the burden of creating a pre-made cache that should speed up initial training as well.

Summary

DMC-Complete demonstrates how classical AI techniques can deliver surprising results. By combining the simple principle of Markov modeling with the power of LabVIEW’s graphical programming, you can have a practical, private, and responsive coding companion. Sometimes, the simplest solutions are the most effective.

By developing this tool, we hope to contribute to the ever-growing landscape of open-source projects written in LabVIEW that work to improve productivity and serve our needs as well as our clients’ needs better. Contributions to the project are welcome at the repository link provided above.

Want to leverage the expertise of our world-class LabVIEW developers with Test and Measurement Automation experience in a broad range of industries? Contact us today to learn more about our solutions and how we can help you achieve your goals.

The post DMC-Complete: Faster LabVIEW Coding with Old-Fashioned AI appeared first on DMC, Inc..

The Real-Time Advantage—When Determinism is King

LabVIEW RT shines when timing is non-negotiable. Think high-speed control loops, synchronized data acquisition, or safety-critical automation. With platforms like PXI, cRIO, and sbRIO, you get deterministic execution, hardware-level reliability, and the ability to run headless in harsh environments. It’s the kind of setup that makes engineers sleep better at night. 

But it comes at a cost—literally.  

RT systems often require specialized hardware, longer development cycles, and deeper expertise. Controlling costs requires familiarity with all of the hardware and software options out there, a rapidly increasing assortment. That’s why we recommend RT when the application demands it, not just because it sounds robust, and we carefully choose toolsets before we begin based on all the requirements, not just our preferences. 

The PC-Based Powerhouse—Flexibility, Speed, and UI 

Windows-based LabVIEW systems are the unsung heroes of test and measurement. They’re often faster to develop, easier to debug, and offer rich UI capabilities and easy data storage that RT typically just can’t match. Do you need to integrate with some weird DLL or third-party drivers? Then a PC may be your only friend. 

We’ve built PC-based systems for everything from EV battery validation labs to simple torque acquisition carts. Yes, these systems can be stable—if engineered with experience and care. We have clients that run PC-based testers for years without problems. The secret? Thoughtful architecture, plenty of lessons learned, and smart error handling. 

Stability Isn’t Exclusive to RT 

While RT systems are quickly becoming all the rage, a common misconception is that only RT systems are stable enough to handle long-term testing. While RT does offer inherent stability, Windows systems can be just as reliable with the right design. We’ve modernized many legacy LabVIEW codebases to run on modern Windows platforms, with smart improvements for stability. The result? Systems that are easier to maintain and just as robust. 

Hybrid Systems —The Best of Both Worlds 

Here’s where things get interesting. Many clients don’t realize that they don’t have to choose between RT and PC—sometimes they really need both. Hybrid systems combine RT for deterministic control and PC for orchestration, visualization, and data management. 

We’ve been building hybrid architectures for decades. Consider a test system where a cRIO handles real-time DAQ and control, while a Windows PC manages the UI, logging, and remote access. They also naturally facilitate extension outside of the NI Universe, if additional third-party RT systems are needed, like UEI, Beckhoff, etc. These systems require well-designed interfaces (TCP/IP, UDP, shared memory, OPC UA, EtherCAT, etc.), but when done right, they’re elegant yet robust, scalable and cost-effective. 

One of our engineers likes to say, “RT is the brainstem, PC is the cortex.” It’s a metaphor that works. Each part does what it’s best at, and together they form a complete system

Real-World Examples and More to Explore 

Explore some examples of DMC’s work.

• RT-101: Real-Time Operating Systems (RTOS)
• RT-301: Capabilities of Distributed LabVIEW Real-Time
• Real-Time EtherCAT Motion Control with NI cRIO and Embedded UI
• Real-Time Battery Testing: A Synergy of NI LabVIEW, TestStand, and VeriStand
• LabVIEW Real-Time solution for Chemical Process Monitoring
• Real-Time FPGA System for Fast-Responding High-Voltage Arc Detection
• Browse more examples across industries. 

What We’ve Learned at DMC 

From NI VeriStand to RT Linux to PAtools, NI cRIO to UEIdaq and PowerDNA to NI PXI, we’ve worked across platforms and industries. We’ve learned that the best solution often isn’t the most complex one. Sometimes a PC-based system with a solid framework beats a full RT deployment. Other times, RT is the only way to meet timing and safety requirements. Often, the sweet spot is somewhere in between. 

We’re proud to be one of NI’s Platinum Partners and an NI Center of Excellence. That means we don’t just build test systems—we build the right test systems for your requirements. 

Conclusion 

Choosing between LabVIEW RT and PC-based systems isn’t a binary decision. It’s a conversation—one that should consider timing, cost, stability, and long-term goals. Sometimes, the best answer is “both.” If you’re wondering which path is right for your next test system, let’s talk. We’d love to help you engineer a solution that’s not just functional—but exceptional. 

Ready to take your LabVIEW project to the next level? Contact us today to learn more about our solutions and how we can help you achieve your goals. 

The post LabVIEW Real-Time: When to Opt for RT and When to Stick to PC appeared first on DMC, Inc..

Standardizing helps, but building a “company framework” from scratch can take quarters (or years) and divert your best engineers. Even after it’s built, engineers inevitably come and go, and soon you may be left with no one who truly understands what you’ve built in-house. 

CORTEX changes the equation. 

What Is CORTEX?

CORTEX is a modular automated test framework built on NI TestStand and LabVIEW that engineering teams use to standardize production and non-real-time validation workflows. It combines a hardware abstraction layer (HAL), custom step types, process model and reporting plugins, and an operator-friendly application to deliver a repeatable platform you can deploy across benches, stations, and sites. 

Is CORTEX Right for Your Team? 

Choose CORTEX if you want to stop reinventing a framework for every new station, deploy consistently across benches and sites, integrate quickly with diverse hardware, and improve reliability with standardized safety and reporting. 

Ready to standardize your test platform? Contact us to schedule your CORTEX demo. 

CORTEX Highlights 

• CORTEX standardizes sequencing by leveraging TestStand with a custom Sequence Editor and reusable step libraries. TestStand is an open and industry-leading test sequencer, with plenty of experts who know how to develop tests using this tool and plenty of training for those looking to get started. 
• It abstracts hardware through a HAL and plugin classes for your devices and instruments, including but not limited to: DMMs, Digital/Analog IO, Serial & Industrial Communications, Power Supplies, PLCs, and more. 
• It prioritizes configuration over code with dynamic workspaces, station configurations, and socket mapping for multi-up stations. Your team can spend more time on the configuration without needing to be programming experts. 
• It delivers a production–grade user experience with Auto and Manual test modes, device dashboards, live data channel viewer, alarms, and a roles-based user-permission schema. 
• It ensures reporting and traceability with a combination of Test reports and engineering waveform logs, so you can understand what your test system was doing over the entire test, regardless of what you actually graded. 
• It integrates with your ecosystem: Need to connect to your PLCs/MES for material handling? What about that company database you’ve standardized on? Does your IT want to control user permissions? No problem—CORTEX can integrate with PLCs, custom databases for custom reporting, and IT systems by using LDAP to ensure the application works well in your environment. 

Architecture at a Glance

• The CORTEX app runs tests in Auto or Manual mode and provides dashboards, alarms, and live data visualization. 
• The CORTEX Sequence Editor enhances TestStand with custom tools for workspace management, signal mapping, and test point configuration. 
• TestStand process model and plugins handle device management along with safety interlocks, configuration management, and reporting workflows. 
• The HAL and device plugins integrate instruments like power supplies, standard DAQ, and common industrial communication protocols like Modbus and Ethernet/IP that let engineers configure tests at a high level without the need to dive into low-level code. 
• Data is captured in TDMS logs and TestStand reports, with the ability to correlate data output from both of these files and view them together to provide a comprehensive understanding of the test results. 

What You Get Out of the Box

• Auto Test Mode runs looping, operator-focused sequences with perUUT reports and live sequence execution view with debugging tools. 

• Manual Test Mode gives engineers direct control to run subsequences and operate instruments via device widgets. 

• The Channel Viewer provides real-time signal plots for monitoring and troubleshooting. 

• The Test Results Viewer correlates parametric results with waveform data for faster root cause analysis. 

• Alarms and history views simplify troubleshooting and improve operator understanding of system operations. 

• User permissions enforce role-based access for operators, engineers, and administrators. 
• Safety monitoring runs independently to terminate execution if limits are exceeded. 

How to Get Started with CORTEX

1. Schedule a Discovery Call 
   We’ll start by learning about your current testing setup, your pain points, and your future needs. This helps us understand where CORTEX can deliver the most value. Contact us to schedule a call.

2. See a Live Demo 
   We’ll walk you through the CORTEX framework, including its Sequence Editor, operator interface, and hardware abstraction layer. You’ll see how it simplifies test development and standardizes workflows. 

3. Discuss Your Hardware and Integration Needs 
   We’ll review the instruments, PLCs, and systems you need to connect, and outline how CORTEX’s plugin architecture can support them. These can include both short and long-term needs. 

4. Plan a Pilot Deployment 
   Identify a representative test station that we can deploy CORTEX to for an initial assessment and quick win. The best way to help you become convinced of the value of CORTEX and demonstrate the savings to your management is by experiencing it. After an initial deployment, we’ll work with your team to build a roadmap for scaling across your organization. 

Need hard Real-Time Test Sequencing?

TestStand is awesome at many things, but one thing it’s not suited for is real-time deterministic sequencing (e.g., submillisecond HIL control). If you need software that can do real-time simulation, emulation, or test sequencing, reach out to DMC to learn more about our custom HIL test solutions, as demonstrated in these case studies:  

• Power HIL Test Stand for an Autonomous Air Vehicle
• Battery Stack Simulator for Hardware in the Loop (HIL) Testing of Electric Vehicles

Ready to standardize your test systems? Contact DMC to schedule your discovery call and CORTEX demo. 

The post Standardize Your Automated Test Systems—Without Starting From Scratch appeared first on DMC, Inc..

Target Connection

Firewall issues typically emerge when communicating with multiple targets (computers or DAQ hardware). The first step when connecting to an external target is to confirm that you can at least ping it—preferably both directions. By default, Windows Firewall disables incoming ping requests to its computers.

Enabling Ping

Perform the following steps on any Windows device where you want to receive pings.

1. Open Windows Defender Firewall and select Advanced Settings in the sidebar. Depending on your organization, you may need administrator rights or an IT employee to do this.
2. Switch to Inbound Rules via the Getting Started page or the sidebar.
3. Find the rule named “Core Networking Diagnostics – ICMP Echo Request (ICMPv4-In).” Right-click the rule and Enable Rule for all relevant network types (Private, Domain, Public). The rule may also be named “File and Printer Sharing (Echo Request – ICMPv4-In).”

Once you can ping back and forth between your two targets, then you know the connection is set up correctly, and any additional issues are in the LabVIEW and Windows Firewall interaction.

Common Firewall Issues

So, how do you know if Windows Firewall is causing your problem? Here are a few common symptoms you might see.

1. TCP or UDP messages sent between two separate LabVIEW applications on the same or different targets aren’t making it to their destination.
2. Intermittent connection errors to external devices or computers. If connecting via TCP, this will likely manifest as Error 56.
3. Failure to connect to NI hardware in NI MAX, or open DAQmx or IMAQdx resource connections.
4. If using Shared Variables, errors when pulling data from the Shared Variables.

If you’re seeing unexplained or inconsistent network operation errors after you’ve confirmed that the two targets are connected, then Windows Firewall should be a suspect.

Troubleshooting and Resolution

Disable the Firewall and Add Rules

The first step to determining if the firewall is the culprit is, if possible, disabling the firewall altogether. If this resolves the issue, but you can’t leave the firewall off, then it’s time to explore adding firewall rules. NI has a list of ports that they use that can be worth enabling if you are experiencing an issue with one of their listed tools. However, it’s common for custom LabVIEW applications to use custom or dynamic port numbers. In that case, you’ll want to make firewall rules not only for the ports you’re using, but also to allow all ports for the specific LabVIEW application you’re running. Microsoft outlines some risks to doing this, as well as instructions, here. The important thing to remember is that with no firewall, the ports and applications are more vulnerable, so only allow what you actively plan to use.

Run a TCP or UDP Tester

If you’ve added firewall rules or haven’t been able to troubleshoot whether the firewall is the issue, a great way to test LabVIEW’s ability to access network resources is using a tester. LabVIEW ships with a TCP/IP communication tester. Running this for a while and logging any errors can help determine if the issues you’re encountering are intermittent and possibly firewall-related, or if there’s something else in your application causing issues. Running just this tester distills out only the network operation from LabVIEW—it’s like the LabVIEW equivalent of constantly pinging. If you’re able to run this successfully, then there may be other issues at play beyond the firewall.

We Can Help

Fighting with the firewall, or any mysterious LabVIEW TCP connection errors, is better with a partner. If you’re looking for support as you troubleshoot existing systems or prepare to set up new ones, we’d love to help.

Ready to take your LabVIEW project to the next level? Contact us today to learn more about our solutions and how we can help you achieve your goals. 

The post Diagnosing LabVIEW: Windows Firewall and What to Do appeared first on DMC, Inc..

For engineers working in test and validation, LIN presents a unique challenge: it’s easy to wire up but not always straightforward to automate, especially when diagnostic messages (UDS) come into play. Fortunately, NI XNET provides a unified way to manage both standard broadcast LIN communication and higher-level diagnostic protocols with minimal effort.

NI XNET Hardware Setup for LIN Communication

In the simplest test scenario, we have a PC based bus master and a device under test (slave device).

The bus master is a PC connected to the LIN bus through an NI compactDAQ chassis, NI-9860 XNET module, and a TRC-8456 LIN dongle.

Configuring Broadcast LIN Communication in LabVIEW

Configuring broadcast LIN starts by loading the LIN Definition File (LDF) into the NI-XNET Database Editor and assigning it an alias. For this example, we’ll use an example LDF from NI.

Once the LDF is loaded, a simple VI can start communication with the Device Under Test. Here’s what’s happening in the below VI.

1. Create Input and Output Sessions
   • These are RX (input) and TX (output) sessions for receiving and sending data to the Device Under Test.
   • On a test bench, it’s often necessary to enable termination at the TRC-8456 and configure the PC as the bus master.
   • Signal Single-Point Sessions handle signals rather than raw frames, so there’s no need to manually unpack frame data. “Single-Point” means XNET maintains a current-value table of signals for both input and output.
   • The front panel controls input signal list and output signal list are linked to the database, providing dropdowns to select signals to read and write.
2. Start Sessions
3. Assert a Schedule
   • Schedules are defined by the LDF, and the XNET controls will provide a drop-down to select a schedule to assert.
4. While Loop
   • Continuously write and read signals
5. Cleanup Logic
   • Stop and clear both input and output sessions

Performing UDS (Unified Diagnostic Services) over LIN in LabVIEW

UDS (Unified Diagnostics Services) is another common test engineering use case. Here’s another VI showing how to talk UDS with XNET.

1. Open Frame input and output sessions.
   • Instead of working with signals, UDS communication has more variability making reading and writing frames easier
   • Queued Sessions are used here, which store every frame seen on the bus, unlike Single-Point sessions that only track the most recent value
2. Start Sessions
3. Assert a Diagnostic event on the bus Master Request
4. Write a UDS frame e.g. 0x22 ReadDataByIdentifier
5. Wait for the transmission to complete
6. Assert a Diagnostic event on the bus Slave Response
   • Allowing the device under test to respond
7. Read the frames sent by the device under test
8. For clarity, closing and clearing the sessions is not shown

If you’re talking LIN to devices and are ready to take your Test and Measurement project to the next level, contact us today to learn more about our solutions and how we can help you achieve your goals.

The post LIN Communication in LabVIEW with NI-XNET appeared first on DMC, Inc..

LabVIEW and Windows Compatibility

NI considers LabVIEW versions 2021 SP1 and older to be incompatible with Windows 11. NI notes that “Using incompatible versions may result in errors, the inability for Microsoft Windows to recognize or detect and then find a driver for your device, or missing devices.” This means that while running an incompatible version of Windows will not necessarily result in your application no longer functioning on Windows 11, there is added risk in doing so. Upgrading now mitigates this risk and prevents potential downtime in the future.

Hardware Compatibility

As with Windows compatibility, NI provides documentation on the minimum LabVIEW version that is compatible with the given NI hardware. The required LabVIEW version changes depending on what version of Windows is running LabVIEW, so a LabVIEW upgrade may be required, depending on what hardware is used by your application. For example, DMC has upgraded a number of deprecated FieldPoint systems to NI cDAQ, such as this one.

Feature Upgrades

Choosing to update your LabVIEW version offers a great opportunity to implement feature upgrades during the update process. Over the years and throughout use, most applications generate a list of feature requests or quality-of-life issues that could be improved. A LabVIEW version update can be the best time to incorporate these new features, improve quality of life, or simply take advantage of the latest versions of any DMC or 3^rd party toolkits.

Additional reasons to consider using this time for feature upgrades are as follows:

Deprecated Toolkits

From time to time, NI deprecates toolkits or features within LabVIEW and either rolls the functionality into different toolkits or stops support for the toolkit altogether. When this happens, related features within your LabVIEW app must be updated to leverage replacement options.

New Functionality

NI also adds functionality over time in new versions of LabVIEW. Taking full advantage of this additional functionality has the potential to unlock your application by making previously difficult features more attainable or by simplifying the implementation for easier maintainability.

Future Proofing

Upgrading your application to use the latest standards and toolkits will help protect against feature deprecation in the future. Taking the time to upgrade now means less worry in the future. DMC worked with a client where an audit took more than three quarters of their test cells fixtures offline due to outdated software on legacy cRIOs, and we were able to upgrade their software to meet requirements and be ready for the future without work stoppage.

Improved Documentation

Many toolkits, whether provided by NI, DMC, or 3^rd parties, improve their documentation over time for greater ease of use. This means that upgrading to the latest versions of these toolkits has the added benefit of increasing the maintainability and serviceability of your application, in addition to improved feature coverage.

Why ask DMC?

DMC has upgraded hundreds of LabVIEW systems over the years, and we’ve seen the numerous pitfalls associated with working with outdated hardware and software. Whether you’re upgrading on your own and want some support or looking for an overhaul as you migrate to Windows 11, DMC is ready to keep your NI driver versions matching and your hardware non-obsolete.

Closing Thoughts

Timing and context are always of the utmost importance when planning a LabVIEW upgrade for existing applications. With the upcoming end of Windows 10 support, now is a great time to plan a LabVIEW upgrade in conjunction with upgrading to Windows 11. If you are planning any upgrades, connect with us to learn how DMC can use our experience to help you navigate the LabVIEW upgrade process and implement new features to improve your application.

Ready to take your Test and Measurement project to the next level? Contact us today to learn more about our solutions and how we can help you achieve your goals.

The post Upgrading LabVIEW for Windows 11 Compatibility appeared first on DMC, Inc..

So… Why LabVIEW?

Abstract Away 

One of the major benefits of using LabVIEW is and has always been the ease of getting off the ground.  

While SiLA is a well-designed framework that boasts easy implementation, like any text-based language, there is some groundwork that needs to be set up beforehand. By creating a wrapper of functions in LabVIEW, all the complexities of a text-based language can be abstracted away and turned into more approachable inputs and outputs.  

Depending on your exact needs, the SiLA commands can even be wrapped into groups of commands that function as a single block. Once this block is proven to work, it can be reused repeatedly, executing complicated commands in the background without the user having to worry about specific software details. 

For example, the top image becomes the bottom image.

Faster Ramp-Up 

As a visual language, LabVIEW allows users with less programming experience to understand what is going on. 

If a SiLA application requires some modifications due to new needs in your lab, a user with minimal programming experience can jump in and adapt the program to fit their new needs. Calling a LabVIEW-wrapped SiLA function is as simple as finding the correct file, dragging and dropping it into your program, and connecting the appropriate wires.  

Data Entry and User Experience 

It is easy to add new inputs or enter complicated data into a LabVIEW program. 

As a framework primarily used in a laboratory, the data entry and processes can get very complicated. LabVIEW allows the users to quickly adjust and implement new changes without much hassle. 

A function that expects an array can easily be adjusted to accept all forms of file types that you may have that data stored in. LabVIEW supports binary input, spreadsheet input, measurement files, configuration files, and waveform files that can all be converted into your desired format with native functions and input into your SiLA wrapper. 

Sounds great! Why doesn’t everyone do this? 

While there are many advantages to a well-developed SiLA wrapper in LabVIEW, there are also some difficulties.  

Abstract Away 

Yep, you read that right. The abstraction, while great for the end user, adds some difficulty for initial development. 

Since the SiLA DLLs are a text-based integration, they cannot be directly read in LabVIEW. This means that the creation of the LabVIEW wrapper itself can require additional digging and testing. DMC has worked with several tools to parse DLLs into LabVIEW wrappers, such as JetBrains dotPeek, so reach out to us if this is a sticking point! 

Errors 

An error in a SiLA method is hard to trace. 

If an error occurs at any point during a specific SiLA method call, the entire method will report as an error. This can create some difficulties, as the user will not be able to dig into the actual text-based code to see which line is causing the errors. 

Conclusion 

A well-designed LabVIEW SiLA wrapper can save researchers an extensive amount of time in an ever-changing environment. By integrating SiLA into LabVIEW, scientists can do what they do best without worrying whether their hardware is going to perform.  

If you are curious about whether your SiLA needs could benefit from a LabVIEW integration, or if you’re looking for help doing one, reach out to DMC and we’d be happy to discuss further.

Learn more about DMC’s LabVIEW expertise and contact us for your next project. 

The post SiLA Integration with LabVIEW appeared first on DMC, Inc..

LabVIEW Discussion

The program kicked off with the community reviewing the latest LabVIEW trends, updates to certifications, and products reaching their end of life. Then, the group moved on to an ice breaker. During the activity, attendees shared how LabVIEW empowers them, discussed their favorite features, and expressed what they hope to learn in the future.

DMC CORTEX Application Framework

Next, Kevin Shirey, LabVIEW Champion and DMC Senior Project Engineer, led the main technical talk for the day presenting DMC CORTEX.

NI TestStand has a feature-rich set, but mastering it—especially for custom step types, process models, and integration—can be time-consuming. It can also be challenging to create custom operator interfaces and build in data visualization.

DMC’s solution is DMC CORTEX, a powerful, flexible test application framework designed to leverage TestStand for its sequencing capabilities by integrating into LabVIEW. DMC CORTEX is engineered to get developers from setup to actionable test data faster. By building on top of NI’s commercial off-the-shelf (COTS) software platforms, including LabVIEW and TestStand, CORTEX minimizes the need for custom development and maximizes the value of proven tools.

At the user group meeting, Kevin highlighted the CORTEX user interface and data visualization. He hinted at future LabVIEW User Group topics such as test modes, safety monitoring, error and alarm handling, station configuration, and parameterized sequence— all of which are already handled by CORTEX.

CORTEX also uses two publicly available DMC UI toolkits, which improve the UI/UX of the application. These toolkits are available for anyone to install and use on VIPM.io, and are widely used in the LabVIEW community:

• DMC GUI Suite
• DMC Styles Toolkit

If you are interested in attending the next Research Triangle LabVIEW user group, reach out to Kevin Shirey (kevin.shirey@dmcinfo.com) or check out the NI Research Triangle LabVIEW User Group Forums.

Ready to take your Test and Measurement project to the next level? Contact us today to learn more about our solutions and how we can help you achieve your goals.

The post Raleigh LabVIEW User Group Meeting at DMC Featuring CORTEX Application Framework appeared first on DMC, Inc..

At DMC, we’ve been at the forefront of this evolution, building robust, scalable, and future-proof battery test solutions for major OEMs, EV startups, and energy labs. As part of our journey, we’ve continued to work with a variety of legacy and cutting-edge battery cycler platforms, including a longtime staple in the industry: the Aerovironment battery cyclers, now rebranded under Webasto Charging Systems following their acquisition.  

If you walk into a battery lab or R&D center today, there’s a good chance you’ll still spot AV-900, ABC-150, or ABC-170 cyclers humming away in a corner. These workhorses have been around for years and have built a track record for staying accurate and dependable under heavy use. They’ve been put to the test on everything from older lead-acid cells to the newest high-performance lithium-ion packs, and they’re still getting the job done. The challenge isn’t the hardware—it still performs as reliably as ever, but the built-in software tools haven’t evolved alongside the rapid changes in battery testing. Many of the original integration options now feel dated. The good thing is, modern automation platforms and updated integration methods make it possible to breathe new life into these proven systems. 

Modernizing Control & Automation with LabVIEW and TestStand

At DMC, we’ve built dozens of test systems that interface with Webasto/Aerovironment cyclers using a variety of control strategies.

Common strategies include:

• Remote Operation System (ROS) scripting, which requires C-based development, offers basic command-level access—but lacks user-friendly interfaces and extensibility for long-term test programs.  
• Legacy DCOM Drivers for Windows applications like LabVIEW have been available but are notoriously outdated, lacking support for modern toolchains and requiring extensive debugging.  

To simplify the process, DMC has developed custom LabVIEW drivers, reusable APIs, and scalable frameworks that integrate Webasto cyclers into full-featured test automation platforms.

CAN-Based Communication remains the most effective, open, and performant option for high-speed integration—especially for systems with dual outputs or demanding test sequencing. These DMC solutions are built using NI LabVIEW, TestStand, and CompactDAQ/PXI platforms, often tightly coupled with MES systems, high-speed instrumentation, and safety interlocks.  

Whether retrofitting an older AV/ABC cycler or building a new test stand that supports multiple equipment types (Webasto, Bitrode, Chroma, Arbin, etc.), we ensure operator-friendly UIs, data-logging pipelines, and real-time feedback for test traceability and compliance.  

DMC has expertise and proven software control routines to support these common Aerovironment/Webasto cycler models:

• MT-30
• ABC-150
• ABC-170 / CE
• ABC-600
• AV900 / 900-EX

Typical Use Cases We’ve Enabled

• End-of-line (EOL) validation of high-voltage EV packs
• Functional verification of Battery Management System (BMS)
• Remanufacturing and warranty diagnostics
• High-throughput cycling for R&D across multiple chemistries
• HiL simulation of charge/discharge behavior with Webasto cyclers

In all cases, we help customers move beyond “bare-bones” PC control to a fully automated, traceable, and scalable test environment.  

Should You Build it Yourself or Work with a Partner?

DMC brings decades of expertise, a deep portfolio of turnkey battery test systems, and partnerships with industry leaders like NI, Webasto, and Microsoft. So, whether you’re modernizing a legacy test bench or developing a brand-new validation platform, you don’t need to reinvent the wheel or the driver stack. We’re here to help you accelerate development, reduce risk, and build for scale.  

Let’s Talk Battery Test Automation

Want to bring new life to your AV/Webasto cyclers? Looking to scale your test infrastructure with modern tools? Contact us to learn more about how DMC can help you integrate, automate, and future-proof your battery testing workflow. 

Ready to take your Test and Measurement project to the next level? Contact us today to learn more about our solutions and how we can help you achieve your goals. 

The post Modernizing Battery Testing with Webasto Cyclers and LabVIEW Integration appeared first on DMC, Inc..