LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmx Read errors

Solved!
Go to solution

I'm refactoring an old project that uses this .vi:

 

DAQmx Read (Digital Bool 1Line 1Point).vi

 

Sometimes (not every times) this .vi fails to compile for a problem with a missing library/driver .. 

 

michelesantucci_0-1729777995615.png

 

Maybe this depends on this configuration:

 

michelesantucci_1-1729778139698.png

I tried to fix it setting the library file path to C:\Windows\SysWOW64\nilvaiu.dll and C:\Windows\System32\nilvaiu.dll 

but nothing changed.

0 Kudos
Message 1 of 12
(951 Views)

Hi Michele,

 


@michele.santucci wrote:

I'm refactoring an old project that uses this .vi:

DAQmx Read (Digital Bool 1Line 1Point).vi

Sometimes (not every times) this .vi fails to compile for a problem with a missing library/driver .. 


This is a VI belonging to the DAQmx driver and is provided by NI.

You should not start to mess with VIs provided by NI…

 

I never had problems to build executables with DAQmx so the problem is maybe related to how you installed your LabVIEW IDE!?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 12
(920 Views)

There's a way to 'fix' the installation ?

I mean from the NI Packet Manager which Product I need to REPAIR to fix them?

0 Kudos
Message 3 of 12
(917 Views)
Solution
Accepted by michele.santucci

Try repairing NI-DAQmx:

dsbNI_0-1729823872665.png


or repair just NI-DAQmx Support for LabVIEW:

dsbNI_1-1729823902399.png

 

Doug
Enthusiast for LabVIEW, DAQmx, and Sound and Vibration
Message 4 of 12
(863 Views)

DAQmx Read (Digital Bool 1Line 1Point).vi

 

Sometimes (not every times) this .vi fails to compile for a problem with a missing library/driver .. 

What happens if you force compile (Ctrl + Run) the VI when the fail to compile problem occurs? Does the problem recur after clearing LabVIEW's compiled object cache?

Doug
Enthusiast for LabVIEW, DAQmx, and Sound and Vibration
Message 5 of 12
(860 Views)

Need to try this. Thnx

0 Kudos
Message 6 of 12
(824 Views)

> What happens if you force compile (Ctrl + Run) the VI when the fail to compile problem occurs?

 

Nothin'

 

> Does the problem recur after clearing LabVIEW's compiled object cache?

 

Well... I learned how to do this just after I fixed the error by replacing DAQmx VIs ... next time I'll try this.

0 Kudos
Message 7 of 12
(802 Views)

I reinstalled all DAQmx support and replaced one of the original code VI with an older version.

This fixed everything.

Anyway the only thing I changed into this VI was a diagram cleanup... 

0 Kudos
Message 8 of 12
(801 Views)

I fighting again with DAQmx ... I have a couple of old VIs that will not compile because of these errors:

 

michelesantucci_0-1730303042505.png

 

Both VIs uses a Channel Node in this way:

 

michelesantucci_1-1730303110168.png

 

But as you can see the Channel Node is not correctly referenced/populated .. and I can't understand where's the problem.

And moreover I finally noticed that this section of components pallette is not populated with DAQmx items:

 

michelesantucci_2-1730303283531.png

 

I tried to repair NI DAQMx support but nothing changes.

There's a way to force LabView to update the component pallette ?

I'm missing packages?

michelesantucci_3-1730303474411.png

And also examples are missing:

 

michelesantucci_0-1730304209120.png

 

???

 

BTW I'm using LabView 2013 SP1.

0 Kudos
Message 9 of 12
(762 Views)
Solution
Accepted by michele.santucci

Hi Michele,

 


@michele.santucci wrote:

BTW I'm using LabView 2013 SP1.


And why did you install DAQmx2024Q3.1 when you still use LabVIEW2013SP1?

This combination will NEVER work!

 

Please install DAQmx13 to DAQmx16 for your LV2013 installation: this is the suported range!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 10 of 12
(739 Views)