LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmx Counter not working on deployed computer

I have a program to read the counter frequency, it works with LabVIEW and i have no problem running the application (EXE) when using the development PC, but it fails to read in another PC that I created a package installer from this project. I checked for errors and the right input from the DAQ but everything looks good. Feels like I am missing some software but I don´t know what to check next.

Counter.png

 

Here is the software installed in the PC that doesn´t work with the counter.

Screenshot 2026-08-03 084701.png

0 Kudos
Message 1 of 4
(151 Views)

How does that software list compare with the Development PC?

 

0 Kudos
Message 2 of 4
(130 Views)

This is the development PC software installed.

Screenshot 2026-08-03 133136.png

0 Kudos
Message 3 of 4
(127 Views)

Trying to compare two "pictures" of installed software makes my head hurt (to say nothing about the "finger pain").  It looks like the PC where the code doesn't work has the latest version of LabVIEW 2026 (i.e. Q3) installed, while the development PC (where it does work) has Q1.

 

I'd suggest (for your own "sanity") that you (maybe "by hand") create an Excel WorkSheet with the Development Software PC entries in Column A and the PC that doesn't work in Column B.  If the A and B entries are identical, put them both in the same row, but if they are different (or only appear in one of the PCs), make a row with only one column filled.  [I hope that makes sense to you -- you want to be able to "see at a glance" where the differences between A and B lie].

 

Since your non-working PC (I'll call it PC B) "doesn't work", and has "the latest version of LabVIEW installed", one approach would be to do the following:

  1. Uninstall LabVIEW completely from PC B.  This is a 3-step process, best done with Control Panel.
  2. Duplicate (as best you can) the LabVIEW software of PC A (the working PC).  I'd recommend installing in "most recent version first" order, but only because I was burned when trying to install a multi-versions LabVIEW system when NIPM was first rolled out (took me two years! to get it to work, as I was installing "oldest-first").
  3. Let us know if this works.  If it does, then you can try to "upgrade" to the latest (2026 Q3) versions ln PC B, retaining PC A (which"still" should work).  Only then should you consider upgradng PC A.

Bob Schor

 

0 Kudos
Message 4 of 4
(59 Views)