11-07-2019 02:45 PM
11-07-2019 03:47 PM
Convert To Dynamic Data.
Unfortunately, since its an express VI, its internal settings are hidden and we can't tell what they are just from the picture (eg: if columns are channels or rows are channels).
11-07-2019 09:28 PM
My recommendation is to never use this function, never use the Dynamic Data Wire (which is what it creates), and learn DAQmx and stop using the Dreaded DAQ Assistant (the Express VI into which you wired the Dynamic Data Wire). Learn DAQmx (numerous Tutorials, Examples, White Papers such as "Learn 10 Functions in NI-DAQmx and Handle 80 Percent of your Data Acquisition Applications). Your LabVIEW code will be much simpler (you'll probably use 3-4 DAQmx functions), easy to debug, easy to understand, easy to modify.
Bob Schor
11-08-2019 09:40 AM - edited 11-08-2019 09:42 AM
On top of what Bob said IMHO: Express VI's were made solely for those LabVIEW seminars sales pitches so they can show managers and other "decision makers" how easy you can just throw something together in LabVIEW.
But they are useless for any "real" application.
11-08-2019 11:36 AM
@Bob_Schor wrote:
My recommendation is to never use this function, never use the Dynamic Data Wire (which is what it creates), and learn DAQmx and stop using the Dreaded DAQ Assistant (the Express VI into which you wired the Dynamic Data Wire). Learn DAQmx (numerous Tutorials, Examples, White Papers such as "Learn 10 Functions in NI-DAQmx and Handle 80 Percent of your Data Acquisition Applications). Your LabVIEW code will be much simpler (you'll probably use 3-4 DAQmx functions), easy to debug, easy to understand, easy to modify.
Bob Schor
My work isn't so complicated yet that it requires DAQmx. That is a lot of things I need to learn to use DAQmx. I don't want to worry those things for now.
11-13-2019 10:06 AM
@RTSLVU wrote:
On top of what Bob said IMHO: Express VI's were made solely for those LabVIEW
seminarssales pitches so they can show managers and other "decision makers" how easy you can just throw something together in LabVIEW.
But they are useless for any "real" application.
occasionally, I use
https://zone.ni.com/reference/en-XX/help/371361R-01/glang/file_dialog/
and for prototyping
https://zone.ni.com/reference/en-XX/help/371361R-01/lvexpress/signal_filter/
like this:
https://forums.ni.com/t5/LabVIEW/Bad-points-at-beginning-and-end-of-filtered-data/m-p/769500#M352405