DAQ not communicating with EXE

[Arru]

Hi all, 

I had running a DAQ USB 6501 till the computer had to be replaced, I can see the DAQ in NI MAX, all the tests work perfectly but unfortunately the DAQ is not communicating with the app on the new computer. The problem is I don't have access anymore to the VI file so I cannot edit or modify the program, I can't remember what's the name of the device when I created the EXE file, any idea about how I can find the name of the device? Could be that the cause for the DAQ stop communicating with the app?

Many thanks gentlemen.

S.

[santo_13]

If you did not specify an Alias for the DAQ, typically it will be 'Dev1'

You need to know what Alias your application is looking for, or else you have infinite options to name the DAQ.

[Kyle97330]

Any chance the EXE was built with debugging enabled and you could connect to it and examine the code?

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YIEsCAO&l=en-US

[Arru]

Hi santo_13,

Thanks for your answer, that is was I supposed, I built this app 10 years ago so let's see if I did enable the debugging when creating the EXE file and I can dig a little bit in the code.

Thanks.

Arru.

[Arru]

Hi Kyle, 

Fingers crossed, I built the app 10 years ago so I'll try your solution.

Thanks.

Arru.

[Kevin_Price]

Another possibility:  use "NI I/O Trace" to capture the DAQmx calls -- that might show you the device alias the EXE is trying to use.

(Note: if trying this on a system with older DAQ drivers, the app used to be named "NI Spy")

-Kevin P

[JÞB]

If you did it correctly the first time you should either have a NI MAX configuration file (*.nce) somewhere that you can import into MAX.

OR, if you were really on the ball and used Project persisted DAQmx configurations, the NI DAQ folder exists in the application support directory and contains a DAQmx.ini file with all the DAQmx settings in human readable text.

If you did neither of these, I hope you at least published a ReadMe.txt.

---

@Kevin_Price wrote:

Another possibility:  use "NI I/O Trace" to capture the DAQmx calls -- that might show you the device alias the EXE is trying to use.

(Note: if trying this on a system with older DAQ drivers, the app used to be named "NI Spy")

-Kevin P

---

The old machine WILL HAVE a HKEY registry entry for the USB-6501 Alias