What is a data acquisition system (DAQ)?

A DAQ system is used to measure, record, and analyze physical or electrical signals (temperature, voltage, pressure, etc.) from sensors or instruments in industrial or scientific environments.

What types of signals can be acquired?

Our systems handle analog, digital, and synchronized signals, as well as communication protocols like CAN, RS-232, and Modbus.

Are your solutions compatible with LabVIEW?

Yes, our DAQ systems are fully compatible with LabVIEW, TestStand, and National Instruments tools, with customizable interfaces.

Can multiple acquisition channels be synchronized?

Yes. We offer high-precision synchronization options for angular, multi-sensor, or real-time measurements.

Do you offer portable or custom systems?

Absolutely. We design tailor-made DAQ systems adapted to your environment, communication, and processing constraints.

Which industries do you serve?

Our solutions are used in the aerospace, energy, transportation, scientific research, and manufacturing sectors.

Calling a VI from the Stimulus Profile Editor: Yes, It’s Possible!

Blog Neosoft Technologies

Calling a VI from the Stimulus Profile Editor: Yes, It’s Possible!

NI VeriStand is a highly flexible environment designed to support a wide range of applications—from rapid prototyping to HIL testing, all the way to basic real-time data logging.
One of VeriStand’s greatest strengths is its ability to integrate custom LabVIEW code in multiple ways:

The Stimulus Profile Editor: More Than Just a Sequencing Tool

When running automated test scenarios in VeriStand, the Stimulus Profile Editor includes a powerful yet often overlooked feature: the “Open Workspace Tool” step.

This step can actually call any VI, as long as it contains all its dependencies.
To do this, simply generate a source distribution from LabVIEW.

With this technique, you can launch a daemon or an additional user interface during the execution of a stimulus, enabling advanced or interactive use cases.

Be Careful With Asynchronous Behavior

It’s important to remember that launching the VI is asynchronous: as soon as the VI starts, the stimulus continues execution without waiting for it to finish.

If your application requires blocking behavior—for example, waiting for user interaction or manual validation—you must instead create an executable containing the VI and call it using the “Command Shell” step.

This approach ensures the stimulus pauses until the external process ends, giving you full control over the test sequence.

➡️ Exemple d’application :

Pour attendre une interaction utilisateur ou une validation manuelle. Il faut alors créer un exécutable contenant ce VI et l’appeler via le step “Command Shell”.

Cette approche garantit que le stimulus suspendra son exécution jusqu’à la fin du processus externe, offrant un contrôle total sur la séquence de test.

In Summary

✅ Yes, it is possible to call a VI from the Stimulus Profile Editor.
💡 Use the “Open Workspace Tool” step for asynchronous execution.
🧩 For blocking execution, use an executable with the “Command Shell” step.

This feature, although discreet, once again highlights the flexibility of NI VeriStand and its ability to adapt to complex and scalable test architectures.

Share the blog post :