topic Re: LabVIEW Code Generation failed to execute on LabVIEW 2023 Q3 in LabVIEW

LabVIEW Code Generation failed to execute on LabVIEW 2023 Q3

S3Lab — Fri, 22 Sep 2023 11:36:09 GMT

Greetings,

I'm trying to create my first LabVIEW project with a cRIO-9054 system. The project consists on the acquisition of a tension signal by means of a NI 9219 module. The version of the software is the latest (LabVIEW 2023 Q3) and I've configured the hardware so that I can use the NI-DAQ toolbox.

When I try to use the DAQ Assistant it always displays the "LabVIEW Code Generation failed to execute" error.

I've tryed to follow every troubleshooting procedure but it didn't work. Eventually, I've read in other discussions that this problem happened in the versions 2022 Q3 too and the proposed solution was the installation of the version 2021 SP.

I tried to download such version but this didn't solve the problem. Can someone help me with this problem? Thank you so much!

Re: LabVIEW Code Generation failed to execute on LabVIEW 2023 Q3

ZYOng — Fri, 22 Sep 2023 17:22:06 GMT

My recommendation: Don't use DAQ Assistant.

There are plenty of shipping examples available. See Take Your First Measurement in LabVIEW Real-Time (Data Logging)

Re: LabVIEW Code Generation failed to execute on LabVIEW 2023 Q3

S3Lab — Mon, 25 Sep 2023 08:03:37 GMT

Many thanks for your answer. The reason why I would like to use the DAQ assistant is that with the examples like the one that you recommended I'm not able to save the data that I acquire since the path that I enter is not recognized and it always return me the error-201304 "File path specified is invalid, or the file is not a valid TDMS file". I doubt that the problem is the location of the VI that allows a correct reading of the physical channel but it's unable to recognize the path folder in my PC.

I attach the project and the VI for a better understending of my problem. Thank you so much.

Re: LabVIEW Code Generation failed to execute on LabVIEW 2023 Q3

GerdW — Mon, 25 Sep 2023 08:18:20 GMT

Hi S3Lab,

@S3Lab wrote:

I'm not able to save the data that I acquire since the path that I enter is not recognized and it always return me the error-201304 "File path specified is invalid, or the file is not a valid TDMS file". I doubt that the problem is the location of the VI that allows a correct reading of the physical channel but it's unable to recognize the path folder in my PC.

The problem is not with your PC or the example VI, the problem is (like in most cases) between keyboard and chair (PEBKAC)… 😉

When you want to save data with a VI running on your cRIO then you must select a path available to your cRIO!

The cRIO has NO access to the harddrive of your computer, it only knows its own internal harddrive. Use a path on that internal drive "c" (or USB memorystick "u")…

Re: LabVIEW Code Generation failed to execute on LabVIEW 2023 Q3

S3Lab — Mon, 25 Sep 2023 09:04:44 GMT

I see. Since I'm afraid that the size of the file produced might exceed the dimension of the space available on the cRIO, do you know if there's some way to stream and store datas to the PC so that I use more space?

Re: LabVIEW Code Generation failed to execute on LabVIEW 2023 Q3

GerdW — Mon, 25 Sep 2023 09:11:30 GMT

Hi S3Lab,

@S3Lab wrote:

I see. Since I'm afraid that the size of the file produced might exceed the dimension of the space available on the cRIO, do you know if there's some way to stream and store datas to the PC so that I use more space?

Sure there is a way to stream data from cRIO to your computer!

Have you ever considered to use the examples coming with LabVIEW?

There are example projects explaining how to implement data transfers to/from cRIO: File->New… or File->Create project…

There are also example VIs in the example finder explaining certain functions/aspects like NetworkStreams…

Re: LabVIEW Code Generation failed to execute on LabVIEW 2023 Q3

AdamSlowik — Tue, 24 Mar 2026 20:46:48 GMT

I have the same problem with newest LabVIEW 2026 Q1 version . I installed full software version with all drivers and with all available software. How can I resolve this problem. Last info in the error window is, that it can be possible if I use a LabVIEW version under development. I use our development licence in my university site.