Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Build executable with NI 4351

Hello,

 

I have a PXI4351 card to monitor the temperature with a PT100 sensor. I modified the driver from NI a bit to save the data and here everything works fine. But as soon as I want to build an executable from this vi I run into trouble. Now, the output of the "NI435x Read.vi" shows "Inf" and I can not read out any temperature values. I have not changed anything in the vi before compiling it. I also tried to implement some waiting times of a few hundred ms, without success. So, what does "Inf" mean? Really infinity or is it some form of error message I just don't understand?

 

Thx in advance

Greetings Dennis

0 Kudos
Message 1 of 6
(4,104 Views)

Hello Dennis,

 

- Which LabVIEW version do you use for building this executable?

- Did you add the ni435xcm.dll to your project as this link describes? I would assume that this might be the cause for the behaviour you're experiencing.

- Another helpful link could this one be. 

- Could youpost your project, so I could try to reproduce the behaviour on my side?

 

Best regards,

Andy

 

 

 

 

 

 

0 Kudos
Message 2 of 6
(4,083 Views)

Hi Andy,

 

sorry it took me quite a bit to reply.

 

In the attachment you can find the small project. This is now a version without the driver itself (I tried to include also the driver in the project, but this resulted in a big mess). Nevertheless in the developer enviroment it should work, when the driver is installed in some standard directory.

 

Answering your questions:

1) I am using LabView 8.2 and I tried to run the executable on the same machine where I compiled it.

2) I also found the link just after I posted this thread, but unfortunately it does not help.

3) The driver I downloadad is for LV Version 7.1. As far as I understand the link, it was already solved there.

4) see attachment

 

Thanks again

Greetings Dennis

0 Kudos
Message 3 of 6
(4,054 Views)

Hi Dennis,

 

I looked at your Project and found a few inconsistences that might cause this problem:

 

-it would be much more efficient if you open and close your file once beyond your while loop

-insert a timing in your while loop to save systemresources elsewise your PC would execute the while loop as fast as possible and ousted therefore other processes.

-at least, it would be much more easier to debugg your programm if you merge all errorlines together and insert a errordialogbox at the end of the line.

 

Best regards and good luck!

 

 

 

0 Kudos
Message 4 of 6
(4,004 Views)

Hi again 🙂

 

I tried to build an executable of your project and everything works fine.

Other than you did I used only unmodified driver from NI. Therto I want to ask you if you saved the changed driver VIs at the same location with the same name?

Respectively could you send me the modified driver too.

 

have a nice day!

Andy

0 Kudos
Message 5 of 6
(3,997 Views)

Hi,

 

so finally I solved the problem, but I don´t know why ... Smiley Surprised.

I started from scratch and installed the driver again, wrote my vi again and compiled it again (this time I was more careful with the naming and the location of the files, so I am sure this is all fine now), with the same result: I could not read out the temperature sensor with the executable. And now comes the funny part: I am using a current of 1mA, so in my Vi I executed the SetCurrentSource Sub-Vi with the parameter 1mA. But if I set this to 25uA everything is fine and the executable is working. The wrong factor of 40 I can now easily compensate later. But it is strange, and I don´t understand why this one parameter has this effect.

 

Thanks again for your help

Greetings Dennis

0 Kudos
Message 6 of 6
(3,923 Views)