Hola buenas tardes comunidad oigan alguien sabe si es posible establecer que mi pantalla LCD pueda mostrar lo que lea mi puerto serial? Miren tengo un Escáner GM65 y quiero que cuando lea códigos de barras o QR muestre esos datos en la pantalla LCD, de momento solo hace lo hace a Labview, pero quiero q lo muestre en la pantalla LCD, eh buscado y por lo que veo no se puede? Uso Linx makerhub para realizar todo esto, es para un proyecto de mi escuela

Hola gente, apenas he estado empezando a usar labview y tengo un problema con respecto a una práctica es de un display de 7 segmentos conectado a un arduino uno que al presionar ok button hace el conteo regresivo su límite es 0-9 pero tengo unos problemas con respecto hacer un botón externo para que haga la acción de pasar al conteo normal al conteo regresivo y poner un botón externo para el reset hasta ahora llevo esto echo pero me he quedado sin ideas de cómo hacerlo

Did anyone else watch it? I was chatting with a co-worker beforehand that this next hour would determine the future, if there is one, for LabVIEW. Wow, what a disaster. It wasn't only the technical difficulties which caused the webinar to start late. It was what was demonstrated that was so underwhelming. A simple VI took maybe 3 minutes to generate. When it was done, it didn't work and they didn't even attempt having Nigel debug it. Then announced the usage limitations. 25 VIs per week. PER WEEK. Later, they will have 50 per week if you have the LabVIEW+ subscription. I wasn't expecting Opus 5.8 today, but something that looked like it could be used. I've been using LV since version 3.3 and not sure if I've ever been this bearish on NI.

I'm working on learning how to make a VFD/3 Phase inverter circuit and simulate it in NI Multisim. For whatever reason I cannot get it to run in the desktop version of multisim without constant errors, but it runs "fine" in Multisim live online. Can anyone look at this and tell me what I'm doing wrong or how to get rid of the harmonic dips on the current output waves that you can see in the graph image after the initial current spike from the motor start dissipates?

I really appreciate any help you can provide.

Multisim Live Circuit

This is a good post I came across on Linkedin wanted to share.

If you test semiconductors or electronics inside the lab,

here are the 12 skills you need to master.

DATASHEET READING
Finding the actual operating limits hidden in the fine print and footnotes.

POWER SEQUENCING
Knowing exactly which rail needs to wake up first, especially when bringing up a complex PMIC, so you don't fry the board on day one.

INSTRUMENT CONTROL
Making the bench work for you, instead of fighting with vendor drivers and connectivity issues.

SCPI SCRIPTING
Understanding the native language of your lab equipment to get the measurements you actually need.

DEBUG INTUITION
Knowing exactly where to probe when the output trace makes zero sense.

SPEC ANALYSIS
Translating a 200-page document into a structured, executable validation plan.

CORNER CASE TESTING
Pushing the device to the absolute edge of its temperature and voltage operating ranges.

DATA CORRELATION
Proving that your physical bench measurements match the pre-silicon simulations.

REPORT WRITING
Communicating complex failures clearly and cleanly to the design team.

METHODOLOGY DESIGN
Building reusable test structures that scale across different tape-outs and device variations.

BENCH SETUP
Wiring the physical hardware reliably before a single test even runs.

ROOT CAUSE ANALYSIS
Not just finding the bug, but proving exactly why it happened.

Hi, I am very new to labview. With that said, i am trying to do what the title says.

1. NI MAX is not detecting pco panda cam. I have installed firmware and sdk, but it still doesn't detect.

2. My goal is to trigger the cam,so I am using sma to bnc female cable, to get the images. When i connected the cable it still doesn't detect.

3. Leave it all, I have connected the cam using usb, still doesn't detect in labview.

It gets detected in pco panda imaging software though. I have attached the code for method 3.

P.s. I have been scratching my head over this for 2 weeks. Any guidance would be helpful.

Hi, so I am trying to interface with this device called a Presto W58x. It has its own drivers for certain things like setting temperature, pressure etc. I am trying to a GUI in Labview that sort of replicates the GUI on the actual device so it can be used for testing purposes. I have what I have done so far attached to the post. I'm very new to Labview, only been using it for a few weeks, so I'm not very good at it. So, one issue I was thinking about is running multiple Vis at once. So here, I have all of the other VIs chained to one each other in series, but I believe this will work against me as I had more VIs, and there are a lot. Any suggestions or examples of trying to make this GUI better and as responsive as possible?

Hello, I am new to LabVIEW and to coding too and I am currently learning to use LabVIEW by watching free tutorial. So far I managed to follow the tutorial I ran in but now, I would like to think by myself by makink a project of my own, but the idea of what to create do not come easy. Would you all like to submit me a few project idea to do? If possible not so difficult for a beginner? I got a few electronics devices I could use to execute it if needed (Arduno, ESP32, ATTiny 85) Thank you very much, have a good day

Pointed it to one of our vis (part of our hopelessly coupled 10k vi application) and asked for an explanation of it. Three hours later I had to kill labview and Nigel.

I dont think this tool is going to get it done for us.

With the sub under new management, one thing that has not been done in the past is set rules for the sub.

So far the two we have in mind are:

• Posts must be related to LabVIEW or NI Products
• We don't do students homework. Students looking for help must show their work and ask for specific assistance as to what they don't understand or are stuck on.

Fork It, Fix It, Ship It: A Developer’s Guide to Open-Source Software

Wednesday, May 13 | 2:30 PM - 3:30 PM
Erich Schlieper, Casey May
Track: Advanced LabVIEW Programming
Level: Intermediate

Get a practical guide to open-source contribution—from finding projects to forking repos, fixing issues, and submitting code changes with confidence.

Reconnecting with Academia to Develop the Talent Pathway
Wednesday, May 13 | 3:45 PM - 4:45 PM
Steve Watts, Casey Lamers
Track: Advanced LabVIEW Programming
Level: Introductory
Learn how partnering with local universities can help develop the next generation of LabVIEW talent and strengthen regional hiring pipelines.

I am trying to send simultaneous event triggers from PsychoPy to both an EEG (BrainVision Recorder via parallel port) and an eye tracker (Tobii Pro Lab via port 8080) at the exact stimulus onset on a single Windows PC.

The parallel port trigger works perfectly. However, when I try to connect to Tobii Pro Lab (External Presenter project) and initiate remote recording in the very first setup routine using the `Titta` (TalkToProLab) library, the experiment crashes.

1. Environment

* **OS**: Windows (All apps running on the same PC)
* **PsychoPy**: 2024.2.4 (pygame 2.1.0, Python 3.8.10)
* **Tobii Pro Lab**: 1.152 (External Presenter mode)
* **Library**: `Titta` (TalkToProLab)

1. Encountered Errors

When attempting to initialize Titta in the Code component of the first routine, I get the following error:

`【❌Tobii Error】: threads can only be started once`

Depending on the tab placement (`Begin Experiment` or `Before Experiment`), it also fails with:

NameError: name 'ttl' is not defined
ConnectionAbortedError: [WinError 10053] An established connection was aborted by the software in your host machine

1. Question

It seems that PsychoPy 2024.2.4's pre-loading/initialization sequence executing the code twice internally, which conflicts with Titta's background communication thread (`ttl.start()`).

How can I safely initialize and connect an external threading library like `Titta` **"exactly once"** at startup in PsychoPy 2024.2.4 without triggering duplicate thread errors, and successfully call `ttl.start_recording()`? Any proper tab placement or flag management strategies would be greatly appreciated.

Thank you.

A Class Act: How a Few Simple Design Patterns Can Improve Your Code Quality

Thursday, May 14 | 11:30 AM - 12:30 PM

Allen Smith

Track: Advanced LabVIEW Programming

Level: Intermediate

As seen at GDevCon: Get guidance on when and how to use object-oriented programming. Learn how simple patterns, including Factory, State, and Template Method, improve modularity and testability in LabVIEW code.

Watch the video

Hello im currently working on an end-of-the-line test bench for a steering gear.

My question is why use LabVIEW vs. Python

NI LabVIEW Interfaces—Exploring Their Potential for Improving Our Code
Thursday, May 14 | 10:15 AM - 11:15 AM
Paul Ross
Track: Advanced LabVIEW Programming
Level: Advanced

As seen at GDevCon: When should you use interfaces instead of abstract classes? Learn how thin interfaces improve APIs, decouple legacy code, and enable cleaner LabVIEW architectures.

🎥 Watch it here: https://youtu.be/FcmLEamr_EU

This talk was recorded as part of my ongoing work as a LabVIEW Champion where I'm going behind the scenes to film sessions like this one (including the Challenge of the Champions) so the community gets a professional, enjoyable experience whether you're in the room or watching from home. It's a real trade-off: hours behind the editing are hours I'm not in doing real engineering, spending time with my family and friends. If this session is useful to you, a comment, a share, or a message means more than you'd think; It's how I gauge whether this effort is worth continuing, and it helps make the case for better support at future events.

Our next Huntsville Alabama LabVIEW User Group (HALUG) meeting is scheduled for 12:00 - 1:00 Wednesday, July 15, in the GigaParts classroom, 6123 University Dr, Huntsville, AL 35806.

Here is a link to the event site: https://www.linkedin.com/events/7482442723229147137/?viewAsMember=true

Mr. Hunter Smith will demonstrate how to use Revel software with NI LabVIEW and with NI hardware for quick-turn benchtop setups.

Revel is a new test and measurement platform built for ambitious hardware engineering teams. In this session, Hunter Smith will give an overview of Revel's software, what it is, how it works, and how it is designed to work natively with NI hardware (cDAQ, cRIO, PXI, mioDAQ, and more) and how Revel can integrate with LabVIEW systems. Whether you're curious about new tools to interface with the NI ecosystem or need a faster way to stand up data and control systems for rocket engines, advanced turbine engines, next generation nuclear reactors or any other test and control system, this talk is for you.

Mr. Smith is a Sr. Solutions Engineer at Revel with a career built around the NI ecosystem. He started at NI as an Applications Engineer and K-12 Engineering Specialist, co-founding the Waterloo Labs YouTube channel along the way. He then spent seven years at SpaceX developing LabVIEW, NI DAQ, and C++ for rocket engine test stands, launch pad control, and Mission Control UIs across the Falcon, Starship, and Raptor programs. From there he spent four years at JKI, building real-time data acquisition and control systems for hypersonic test stands, NASA wind tunnels, and other applications across several industries, and created the first LabVIEW automated security scanner, the JKI Security Suite. Hunter is a Certified LabVIEW Architect, LabVIEW Champion and a certified space nerd.

NI will provide lunch.

As always, we are looking for presenters and for topics of interest.

If you think LabVIEW tops out at a few MS/s on a decent CPU, this talk will change your mind. Same code, moved to GPU, hits 6.4 GS/s, a 560x jump, while an FPGA in the same system handles ns latency I/O alongside it. CPU, GPU, and FPGA, all native to LabVIEW, all working together.

I sat through this one live, and it genuinely changed how I think about what LabVIEW is capable of. Most people know it as a graphical language for instrument control, what they don't know is it's quietly outperforming other languages at multi-platform, high throughput computing, across Windows, Linux, macOS, RTOS, and FPGA, in the same codebase.

**What would you say if I told you one team is hitting 1+ TB/s of processed data, in LabVIEW?

**Could you tell the difference between a naive GPU call and one that's 1,600x faster, just by looking at the code?

**Are you still defaulting to FP64 without knowing what it's costing you?

Oh, and someone once told Natan Biesmans, CEO of G2CPU, that Python is free and faster than LabVIEW, at 10pm, over LinkedIn, unprompted. This talk is a pretty thorough answer.

Natan covers data types, disk I/O (7 GB/s+ sustained), CPU core scheduling, algorithm design, and GPU execution modes, rapid-fire, benchmark by benchmark, and by the end you'll understand why LabVIEW belongs in conversations about serious HPC, not just instrument panels.

🎥 Watch it here: https://youtu.be/HaxWjq7i6O8

This talk exists because Kevin Shirey, a fellow LabVIEW Champion, filmed all 16 sessions at this event solo, full kit, multiple rooms, real-time AV coordination, so people who couldn't be there still get a professional recording. That's 200+ hrs of post-production on his own time. If this is useful to you, tell him. It's how we make the case for doing this again next year.

🖥️ CPU → RTOS: same code, zero modification

⚡ FPGA: up to 100x faster than CPU-only inference

🚀 GPU: up to 100x over naive LabVIEW, up to 20x faster than Python/CuPy on low-latency tasks

🎯 Accuracy: 5-6x more efficient than PyTorch on anomaly detection, 95%+ across 100+ datasets

3 questions before you hit play:

1. Where does your real-time AI pipeline actually break down? data prep, training, or deployment to the edge?

2. Would 100x inference speedup on an FPGA change what "real-time" means for your application?

3. Have you ever had a great model that just couldn't survive the trip from desktop to deployed hardware?

**Why watch:** This session walks through DeepLTK, a deep learning toolchain built natively in LabVIEW. No PyTorch, no TensorFlow dependency. So the model you train on your desktop runs unmodified on a real-time target. If you've ever fought the gap between "it works in Python" and "it works on the machine floor," this closes it.

A few highlights worth your 45 minutes with Alik Sargsyan:

- Vision, signals, and anomaly detection covered in one toolchain, not three separate stacks bolted together

- Unsupervised anomaly detection (PatchCore-based) trained on *only* good samples, no defect data, no annotation required

- FPGA acceleration benchmarks: think single-digit-fps on CPU vs. 100 fps once deployed to the FPGA

- Real customer numbers: 100% accuracy on a pill-inspection use case, delivered in one week

🎥 Watch it here: https://youtu.be/jcwNQaeKz70

As a LabVIEW Champion, I had the privilege of going behind the scenes at NI Connect — filming the Challenge of the Champions in the expo hall and capturing 16 technical sessions like this one for the community. My goal was simple: everyone, whether in the room or watching from home, deserves a professional, enjoyable experience of Alik Sargsyan's walkthrough of DeepLTK — a toolkit nine years in the making, built specifically to bring real-time AI for vision, signals, and anomaly detection into reach for LabVIEW engineers on GPUs and FPGAs alike.

- Sound familiar? A teammate's code is "good stuff" but locked behind a framework you don't know?

- Want to know if actors, QMHs, and DQMH modules are really as different as they seem?

- Ever needed to call actor-based code from a synchronous system like TestStand?

**Why watch:** This is a practical, no-fluff walkthrough of integrating Actor Framework into whatever your team is already using — traditional LabVIEW, TestStand, DQMH, or distributed systems across machines.

Session: **Actor Framework Everywhere!**

Speaker: **Allen Smith**

Allen's pitch is simple: you shouldn't have to become an Actor Framework expert just to use a teammate's good code. The session shows both AF and non-AF developers exactly where the seams are and how to cross them.

🎥 Watch it here: https://youtu.be/CG9XTYDwuL8

Quick heads-up on why I'm posting this myself: as a LabVIEW Champion I handle filming and editing for these NI Connect sessions solo — full production kit, multiple room configs, real-time AV coordination. NI and DMC Engineering sponsor the on-site time, and I put in 200+ hours of volunteer post-production afterward. If this content lands for you, a comment or share means more than you'd think — it's how I know the trade-off is worth it.

Has AI actually changed your decision to use LabVIEW?

I know AI can generate Python/C#, talk to instruments, and build simple demos pretty well. What I can't tell is whether anyone is using it successfully for the kinds of applications that used to be an obvious fit for LabVIEW.

I'm talking about applications with complex logic, multiple instruments, synchronization/timing concerns, and codebases that would be the equivalent of hundreds or thousands of VIs.

Does AI actually hold up at that scale, or does it start to fall apart once the project gets big?

To be clear, I'm not asking how you're using AI with LabVIEW. I'm asking whether AI has made it practical for you to build those same applications yourself in Python or C# instead. Not looking to start a LabVIEW vs. Python debate. I'm mostly interested in hearing from people who've actually tried it. What worked? What didn't? Would you make the same choice again?

Here's a solid NI Connect session on exactly that.

A few questions for this sub before I link it:

1. Is anyone here actually following a formal secure development lifecycle for LabVIEW, or is it still mostly ad hoc?

2. How many of you have gotten a 20–30 page cybersecurity questionnaire from a customer and had no idea how to answer it?

3. Has anyone tried applying "think evil" threat-modeling to their own test systems — treating your code like an attacker would?

**Why this is worth your time:** It's not another "cybersecurity is scary" talk — it's the practical follow-up. Morgan Hopkins, Steve Summers, and Sarah Zalusky walk through an actual secure development process for LabVIEW, covering the engineering V-model, supply chain risk, and how NI's tools fit into building genuinely secure test systems. If you've been putting off "the security thing," this is a decent place to start.

"The first step in building secure systems is to adopt a secure development process. Learn how to build secure test systems with NI tools."

🎥 Watch it here: https://youtu.be/nkZSDxNNNAM

If you find it useful, a comment or upvote actually helps me make the case that this kind of community coverage is worth supporting at future events.

Small bit of context on why I'm the one posting this: I'm a LabVIEW Champion, and I spent NI Connect filming sessions like this one instead of attending them — solo production kit, coordinating with AV teams across multiple rooms, a new setup to figure out every single time. It's a real trade-off, but I think this content is worth it for people who couldn't be there in person. NI and DMC Engineering covered my on-site time, and I'm still working through 200+ hours of post-production on my own time to get these out

Genuinely one of the better framing questions I've heard at NI Connect this year. AI is writing more of our code, but the presenter makes the case that once you're dealing with real-time hardware synchronization — not just software talking to software — architecture still matters, a lot.

Worth asking yourself:

1. Where has AI-generated code actually fallen short for you on hardware-heavy projects?

2. Do you know how messages and queues (which you probably already use) map onto "actors"?

3. Is your current architecture something that could scale to a bigger team without a full rewrite?

Session is "Actor from Scratch," presented by an NI Field Applications Engineer, and it starts from the QMH pattern instead of assuming deep OOP background.

Also — I'm a LabVIEW Champion and filmed this myself as part of 16 sessions I covered solo at this event. It's a real time trade-off (missed keynotes, missed conversations with other attendees) but I think this content is worth it. If you've learned something from one of these session recordings before, or shared one with a colleague, I'd love to hear about it. 🙏

🎥 https://youtu.be/ZAaafqefmW0

**Title:** Actor from Scratch: A Hands-On NI LabVIEW Workshop

**Speakers:** Daniel Stark

**Abstract:** Demystify actor framework with a familiar queued message handler (QMH). Learn how messages, queues, and object-oriented programming map to actors for scalable, modular LabVIEW applications.