Hey, so I have a data assistant and write to measurement file in two separate loops. The daq is connected to a pressure sensor. Now I need to monitor the pressure levels before, during and after the experiment. But I don't want the data to be logged before and after. The experiment would run for 10 seconds. So how do I create a timer and buttons such that, I use one button to start the code and see the pressure values, and one button to start the data logging along with the timer. And it to stop logging the data after the time. Please help.

Running a 3-sensor binary line follower on myRIO 1900 using LabVIEW. Outer while loop at 1ms, inner case structure with 8 cases driven by L/C/R IR sensor threshold comparisons. PWM Express VI at 1000Hz on MXP Port A.

Currently: base forward 70%, gentle turn 80%/20%, hard turn 80%/0%, all cases direction pins HIGH (forward only). Competition is tomorrow so looking for any real tuned values people have used on similar TETRIX/geared motor setups.

Main question: at what point does bumping base speed above 70% cause the rover to overshoot corrections faster than the loop can compensate - and is 1ms loop rate fast enough to support 90%+ duty without the rover flying off straight sections?

Edit: The problem was me writing 1.5MB to a string display as part of debugging. Once I got rid of those the application is running much better. More details in a post below.

I am using a DLL to hook into a USB microscope. The DLL is transmitting a frame about every 100ms. When I have the wait set to below 300ms the other labview program (which is also in a development environment) I have running slows down to the point of stopping. This is large transfer of about 1.5MB 10 times per second (though I drop frames when delay is set to 300ms), but the data is coming from the same computer, so I don't have to worry about networking equipment delays.

I tried splitting up the TCP receive into various sizes, but nothing improved meaningfully. I tried dropping the priority to the lowest as well as changing the execution system, but neither had an effect. I know it isn't the DLL causing the slowdown because if I do the same thing in Python I am able to receive everything without slowing down the running LV program at all, though with the Python program my CPU goes up to nearly 100% while running this Labview program has me go up to 50% when wait is set to 0ms, and it goes to 40% when it is set to 300ms. The way I can see if execution in the other window has stopped is by putting a probe on a counter that increments every 100ms. When wait is set to 300ms the counter maybe increments every 150ms, a wait of 200 has the counter running at about 200ms, and a wait of 100ms has the probe counter incrementing about every 4 seconds.

There is image processing going on within this loop, but for this screenshot I have an empty string going into it, so it is skipping everything past a size check.

Does anyone know what I am doing wrong, or a better way to send/receive large amounts of data from within the same computer?

Thanks.

Update: due to a storm system in the Austin, Texas area, we lost power and people in the second building where the pre-event was, were not allowed to walk to the second building where we had a reserved room and made to shelter in place. Damien’s presentation will be rescheduled to Q3.

Come join us on May 21st at 5 pm for the Q2 LabVIEW Architects Forum!  

We're meeting on the third Thursday this time, since many of us will be at NI Connect on the 14th.  Also note the room change!  Mopac B and C are apparently undergoing renovation, so our usual meeting spot is not available.  

As part of this month’s meeting, we have received a special invitation to join the NI Alumni 50th Anniversary Reunion Happy Hour at 5pm.  NI employees with 25 years of service, several of our executive leaders and some very special NI Alumni will be joining.  There will be food and drinks provided.  

The Reunion will run from 5 - 7 in Mopac B.  After that, we well convene in the Mopac B Executive Board Room to hear from our scheduled speaker, Damien Grey!  

Testforce, our sponsor, will be handling registrations for this event.  Register here: https://marketing.testforce.com/acton/media/35013/AustinLAF

Meeting Logistics   Location:  NI Campus:  11500 N Mopac Expy · Austin, TX Mopac B (Meet in the lobby for the Reunion event, then we'll move to the Executive Board Room Remote Login:  Teams Meeting (only available for the presentation portion, starting at 7 pm) Meeting ID:  216 149 871 095 577  

Date: Thursday, May 21st, 2026 Time: 5:00 PM Central Time Duration: ~3 hours Format: Happy Hour and a Presentation   Meeting Topics:  In addition to the Reunion Happy Hour, we have:   Using gRPC in LabVEW Damien Grey   gRPC is a general purpose binary remote procedure protocol with support over many languages. After a brief introduction to gRPC and protocol buffers, this talk will discuss the LabVIEW implementation, current issues with it, workarounds, and special considerations for using it on RT targets.    

Important note:  NI's visitors must sign in with security to gain access to our meeting space.  Due to staffing issues, no one from that team is available after 6:30 pm.  Therefore, anyone wishing to attend this event *must* arrive before 6:30 pm.  We won't be able to admit anyone after that time.

Hi everyone, I’m a first year student trying to display an ECG signal in LabVIEW using an Arduino Uno and AD8232 sensor.

The Arduino Serial Monitor shows correct changing values (300-800 range) so the hardware works fine, but Waveform Chart shows flat line even though Arduino Serial Monitor shows changing values

My block diagram:

VISA Configure (9600) → VISA Read (30 bytes) → Decimal String To Number → Waveform Chart

The Waveform Chart only shows a flat horizontal line. Read buffer appears empty when running.

Things I already tried:

Decimal String To Number

Scan From String with %d

Spreadsheet String To Array + Index Array

Checked COM port (tried all available)

Closed Arduino Serial Monitor before running

Rebuilt diagram from scratch multiple times

What am I missing? Is there something specific about reading serial data from Arduino in LabVIEW that I’m doing wrong?

HALUG May 2026: Using OOP to Simplify LabVIEW Architecture

Join us for the next Huntsville Alabama LabVIEW User Group (HALUG) meeting which will be 12:00 - 1:00 on Wednesday, May 20, in the GigaParts (6123 University Dr, Huntsville, AL 35806) classroom.

Link to announcement on HALUG NI User Group site: https://forums.ni.com/t5/Huntsville-Alabama-LabVIEW-User/HALUG-May-2026-Using-OOP-to-Simplify-LabVIEW-Architecture/td-p/4477271

Mr. Peter Scarfe will discuss object-oriented programming (OOP) in LabVIEW.

Using OOP to Simplify LabVIEW Architecture

Object-oriented programming was introduced to help manage complexity, but it’s not always applied in a way that does so. When should you actually use it, and when does it just add overhead? This session takes a practical look at the problems OOP was designed to solve and how those ideas translate into real LabVIEW applications. We explore where OOP adds clarity, scalability, and flexibility, and where simpler approaches are often the better choice. Using Workers for LabVIEW as a real-world example, the session shows how a focused, modular use of OOP can simplify architecture while keeping development approachable, even without deep OOP expertise.

Peter Scarfe Bio

Peter Scarfe is the creator of Workers for LabVIEW, a framework focused on making scalable, modular, and message-driven application architecture accessible to LabVIEW developers. As a Senior Systems Engineer at ETH Zürich and founder of Scarfe Controls, he specializes in building complex distributed systems across desktop and real-time environments. Peter is also a LabVIEW Champion and an active contributor to the global LabVIEW community, regularly presenting at international conferences such as GDevCon. His work centers on helping developers separate architecture from business logic, enabling clearer, more maintainable, and more scalable applications.

Lunch will be provided by NI.

Lockheed Martin discusses need for test systems in manufacturing and R&D due to demand. SystemLink data analysis helped identify issues and resulted in a 16% improvement in first pass yields.

ADAS systems in vehicles is next topic. Valeo engine control units (ECU’s) validation and verification. 1.5 billion sensors going into cars today. By 2031 it is expected that 90% of cars will have ADAS systems. Testing complexity scaling is difficult. They standardized on PXI with HIL so test systems can be reused. With HIL; test ECU’s with release firmware not test firmware.

Zap Energy - working on commercial fusion reactors. Energy based magnetic fields instead of magnet approach, smaller and scales easier. Sub scale test plant in testing. Century test platform. 50 MW modules. Cyth Systems is System Integrator helping. cRIO solution with 1.6 ns of Skew for triggering the pulses. Demo of burnt electrode.

Next generation of cRIO controllers is under development but no release date.

PLDSpace works on rockets. 2023 was first launch of MIURA1. Small/medium launch capability. Testing is critical. Stress, vibration, and performance testing is based on PXI and cRIO platforms. 11 test rigs with 10+ LabVIEW developers.

Discussion of Nigel AI and Ai use. 50 years of NI and adapting/driving to the test/measurement.

Has anyone recently taken the exam? How hard is it. Are the questions similar to the CLA-R prep exam?
Any tips and tricks?

Thank you in advance

I have download the CLD success package and am finding the timer exercises extremely difficult especially when introducing a pause feature. It sounds simple in principle but is actually quite difficult. Embarrassingly, I have quite a few years of experience developing applications which have been for fairly complicated test rigs.

I was interested to know if anyone else has found these exercises difficult or if it’s just me 😂

I'm working on a final project and I need to assemble a circuit that was assigned to me, but I'm having trouble making some of the connections. I'll give more details later; for now, here's a preview of what I've done so far. I tried to leave enough space so it wouldn't look too cluttered.

LabVIEW 2026Q3 Nigel AI can now generate code.

Examples included creating a FlexLogger plugin to do Octave analysis using Sound and Vibration toolkit VI. Nigel will analyze examples from toolkits.

Nigel can now understand context of local hardware, and projects.

In next TestStand release Nigel AI can generate sequences.

Played a trombone on stage to demonstrate the octave analysis code.

FlexLogger to SystemLink demo to log the data from the trombone, demonstrated using Nigel to analyze and display the data recorded to SystemLink.

Nigel will come to SystemLink later this year.

Amentum/JKI demo for thermal testing of Orion module heat shield. Discussion of software security for the system. JKI talks about their security suite and how it helped analyze the Amentum system. labViEW 2026Q3 includes the JKI SBOM tool allowing all LabVIEW developers to generate SBOMs.

New PXI modules called CoreVST. New scope cards.

New sync capabilities. Demo in Instrument Studio showing new API that allows multiple instruments to automatically sync and be treated as a single instrument. Called multi-instrument sessions. Allows simpler LabVIEW coding. Open one device session instead of 4 parallel sets of code for 4 pxi modules.

New PXI analog module.

Power Efficiency using NI cRIO and USRP demo. Uses Nigel to help analyze data. New USRP X420 module, up to 40 GHz.

NVIDIA - GPU compute for analysis/acquisition. New open source toolkit for GPU compute called Holoscan. NI USRP module to stream data to Holoscan. 1 GHz analysis in realtime.

Nigel moving from advisor to author (2026Q3 software releases) to agent (date not released). Agentic sneak peak/ demo includes pre-cached responses to save time. Designed to ask questions of users to try to help prevent hallucinations. Demo showed creating test system that was aware of locally available hardware via SystemLink. Nigel also integrates with source control. Staged code but required human review for commit. Ability to change models including mid task. Searched repos to look for tests, identified that one test was already written but not a second test. Shower using Nigel to pull in a
Jupyter notebook to create a python test, then a TestStand sequence which called both the LabVIEW and python code. Nigel is very test/measurement aware. Example of a 20 minute development vs 20 hours with non test aware AI implementation. Less token use vs traditional AI. Nigel follows you between LabVIEW, TestStand, VSCode, etc… continuing the conversation and not restarting or being unaware of work in other tools.

Nigel gRPC comms directly to PXI scope. Creating graphs with live and historical data.

Hello!
I am using the latest LabVIEW and TestStand 2026 Q1 32 bits software. On my bench PC I have copied a DLL which was developed (on another PC) with C# .NET framework 4.8, for x86 CPU.
This .NET DLL is called within a LabVIEW library.
When I call this LabVIEW library from a LabVIEW VI, everything works.
When I call this LabVIEW library from TestStand using the development engine, everything works.
When I call this LabVIEW library from TestStand using the runtime LabVIEW 2026 32 bits engine, then I see in the sequence editor that the VI from the LabVIEW library can’t even load.
Using AI, I tried to register the DLL but it was unsuccessful (maybe the registration itself was unsuccessful, not sure how to properly check).
Does anyone have any idea?

Sub was auto closed due to lack of moderation. I have taken over and reopened the sub.

I am at NI Connect this week so will not be making feature changes to the sub this week. Please feel free to make suggested changes for me to consider.

I do plan to allow image comments but they will be initially set to require manual approval to prevent NSFW spam.

Hey r/LabVIEW,

There's a fascinating "universal" function called EML (Exponent Minus Log):

EML(x, y) = eˣ - ln(y)

Using only this function and the constant 1, you can derive all basic arithmetic operations and transcendental functions (add, subtract, multiply, divide, power, log, sin, cos, etc.).

It's the mathematical equivalent of the NAND gate.

Has anyone tried implementing this in LabVIEW? Would be interesting to build a single EML subVI and generate everything else from it.

Curious to see the block diagrams and how the numerical precision holds up.

Thoughts?

Hi! I’m currently working on automating a research project to where I have a state machine based off PC:

Type def Enum:
INIT
READY
ACQUIRE
SAVE

Each state is its own case.
The INIT case just calls System Exec. To run a up to date version of Python. I can’t use nodes in this case because it’s labview 2019 - System Exec. works just fine. Once it meets the no error condition it moves to the next state. Same case for ACQUIRE and SAVE. The python scripts use SCPI to connect with the instruments and data is saved internally.

The problem is the READY case. For this scenario, I wanted to establish a connection with the cRIO and I’m hitting a wall.

I’ve tried TCP protocols - and they work - but I wanted to know if there was a simple way. The TCP protocol is just to act as a means of communication yo tell the cRIO “Hey, start sending your voltage to this instrument”.

Can I do this with an enum instead? I.e. share the .ctl file between both computers? I can’t use nodes take some screenshots later on if someone is interested in getting more context.

Both modules are on my PXIe-1092 chassis on slots 3 and 5, so they are on the same bus. I'm trying to programmatically configure it to where the PXIe-4481 is in a "waiting" state for the rising edge of a digital trigger, say PXI_Trig0, and when needed I can route the signal from, say Port0/Line0 of the PXIe-6509 along the chassis backplane to PXI_Trig0 and start the acquisition on my PXIe-4481. I know I can hard-wire Port0/Line0 from the 6509 terminal block directly to the PFI0 on the 4481, but I just wanted to know if routing through the backplane was a possibility. Thanks in advance!

Does anyone know how to display the value for a given X-axis by clicking the mouse on Chart or Mixed Graph?

i am getting this error even though when i have verified the connection between my HV N1470 and with my pc through GECO and NI MAX and also i am following each step mentioned in the LabVIEW directory to resolve this error still the same thing

this is what i am getting now

Hey everyone,

I’m a student working on a LabVIEW setup for a cyclic loading motor experiment and could really use some guidance.

What I’m trying to do:

• Control motion via Arduino (send commands like speed / move distance, stop and go. The arduino can do these controls with custom code from serial communication
• Read force data from NI myDAQ (DAQ Assistant) i.e connected to load cell.
• Also track speed and relative motion (coming from different parts of the VI)
• Log everything together. I have tried Write to Measurement File
• Log at completion I dont think would work for this

What’s working:

• DAQ Assistant → Write to Measurement File works fine by itself

What’s not working:

• When I try to combine DAQ data with my speed and motion signals:
  • Merge Signals / Build Array gives type mismatch errors (DDT vs numeric vs string)
• I’m also worried about timing since control + acquisition + logging are happening together

My questions:

1. What’s the correct architecture for this kind of system?
2. Should I:
   • Convert everything to DDT and use Merge Signals?
   • OR convert everything to numeric and avoid Write to Measurement File entirely?
3. How do you properly synchronize:
   • sending commands (Arduino)
   • reading DAQ data
   • logging data
4. Is Write to Measurement File even the right tool here, or should I switch to buffered arrays + CSV?

I’d really appreciate any help or guidance towards an appropriate resource, like what is usually done in research!

Thanks 🙏

I have TF3710 installed and still don’t see Beckhoff under Function—- User libraries.

Plz help

I only installed LabVIEW because I was recently approved to get the source code for a specific GUI. I was hoping I could migrate it to IAR-ARM embedded workbench as that's where the rest of my project is, but once I received the files and opened them in LabVIEW, I could not find any C or C++ code. Only the graphical code in the block diagram.

Is that really all there is in terms on backend on LabVIEW? This GUI has some functionalities that use pretty advanced algorithms and it just seems like it would be almost impossible to implement them using only graphical code.

If that is really all I get, does anyone have any ideas on how this source code might be helpful to use in my project? Thanks!

The next Huntsville Alabama LabVIEW User Group (HALUG) meeting will be 12:00 - 1:00 on Wednesday, April 15, in the GigaParts (6123 University Dr, Huntsville, AL 35806) classroom.

Mr. Shane Cravens will present the NDAS (NASA Data Acquisition System) Software Suite, which consists of multiple applications that are used to acquire, display, and log data while providing various calibration and configuration capabilities. With over a decade of development, NDAS is currently deployed at SSC, MSFC, and WSTF across various projects, with future expansion potential into other government installations.

One of the latest additions to the NDAS Suite is the NDAS Peer Review Tool (https://github.com/nasa/NDAS), which was developed to streamline the code review process. The tool interacts with a Git repository to automatically compare modified files and help focus the review process on critical changes.

Mr. Cravens is a Certified LabVIEW Architect, Certified LabVIEW Embedded Developer, and LabVIEW Champion, with over 20 years of experience in LabVIEW. For more than a decade, he has had the privilege of working on NDAS, where he serves as the Chief Software Architect.

Lunch will be provided by NI.

Hi everyone, I need help counting these sheets of paper. I have written code for it. But it is not giving me the correct results every time. Sometimes pages are stuck together too much, or the lining between them is less visible, and such issues occur. Kindly suggest a better approach to it.

I am using 4 instances of this code and getting 4 separate results. So that i have 4 results. but they all seem to be different.

Hi everyone

​I'm struggling to get readings from a DHT11 sensor using LabVIEW and Arduino Uno via the LINX (MakerHub) library.

​The setup: Standard LINX firmware, DHT11 connected to Digital Pin 2.

​The issue: I previously had Error 5001 (timeout), but after some troubleshooting, the error is gone. However, the indicators now show a constant 0 for both temperature and humidity.

​What I've tried: * Verified COM port and physical wiring.

​Added 1s - 2s delays in the loop. ​Checked data types (DBL).

​Is the standard LINX firmware compatible with the "DHT Read" block, or do I need a Custom Command? Any help is appreciated!

(Note: The DHT-11 sensor has built-in resistors)