LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to debug a single vi in target PC?

(1) I build a project in my development PC, it runs fine.

(2) But when I run the exe file in target PC, one of Vi failure, vi run and did not detect DAX value as I expect.

(3) I try build with debug feature in the project , then run it in Target PC, 

  connect to this Debug project from development PC, but it seem can not see the block Diag for this failure vi test case .

(4) I just wonder if I can run ONLY this vi in Target PC, and to see how the block diag. works and try find out why it failure.

(5) can anyone give me some suggestion?

(6) I including the failure vi and the NI software different between 2 PC.

 hope someone can see if it is cause by one of  NI SW different from target PC, I could not find the reason if it is cause by NI SW.

Thanks

 

0 Kudos
Message 1 of 20
(1,228 Views)

Hi zy6,

 

some notes:

- DON'T use the DAQAssistent for "production type" software! Use plain DAQmx functions instead!

- There is NO ERRORHANDLING in your VI (regarding the DAQAssistent)!

- Does your target PC have a Dev1 at all? Is it the very same DAQ device as in your development PC?

- why do you convert a boolean array to DDT, just to convert the DDT to a DBL array???

- why are there so many local variables and so many unused terminals?

- What's the point of a case structure with just one case?

 

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 2 of 20
(1,224 Views)

Is DAQmx (DAX?) even installed on the target PC?

0 Kudos
Message 3 of 20
(1,211 Views)

(1) I build a project in my development PC, it runs fine.

(2) But when I run the exe file in target PC, one of Vi failure, vi run and did not detect DAX value as I expect.

(3) I try build with debug feature in the project , then run it in Target PC, 

  connect to this Debug project from development PC, but it seem can not see the block Diag for this failure vi test case .

(4) I just wonder if I can run ONLY this vi in Target PC, and to see how the block diag. works and try find out why it failure.

(5) can anyone give me some suggestion?

0 Kudos
Message 4 of 20
(1,209 Views)

Hi zy,

 

please stick with your thread instead of creating new threads for the same topic!

(I merged your threads.)

 

What's wrong with our answers so far?

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 5 of 20
(1,206 Views)

Hi:

 (1)  I installed the NI-DAQmxBase3.4 into Target , it still failure.

(2) My target PC had DEV1.

(3) How to create DAQmx functions ? to do what I have  now? 

Thanks 

0 Kudos
Message 6 of 20
(1,185 Views)

Hi zy,

 

1. Nobody suggested to install DAQmxBase! Install the real package - or even better create an installer from your executable with all needed installers included!

2. Is it the very same hardware - "Dev1" is just an alias…

3. Read this…

 

Please don't ask questions by PM when you could ask in this thread too!

Do some error handling with your DAQAssistent:

check.png

But in the end you should replace it by plain DAQmx functions. They are explained in the article I linked to and in all those example VIs coming with LabVIEW!

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 7 of 20
(1,172 Views)

Hi:

 (1) I change to DAQmx functional. it passed in development PC, but

still failure in target PC. see attached file. 

(2) I build the exe file from project., them copy exe file to target PC.

 not sure why it failure since I can not tell any runtime version is down rev in target PC.

Is newer version may cause the problem since some runtime are newwer.

(3) What do you mean ?

Install the real package - or even better create an installer from your executable with all needed installers included!

answer: I though I already have real package.

Thanks

 

0 Kudos
Message 8 of 20
(1,158 Views)

HI:

 Just let know you , it is the same UUT, unit under test hardware .

only different is different test PC, different NI software.

 

0 Kudos
Message 9 of 20
(1,156 Views)

Hi zy,

 

"just to let you know": you got several responses but you didn't answer them…

 

Is your problem solved?

 

it is the same UUT

This is totally irrelevant for the problem: your problem is (most probably) the setup of your executable or to create an installer with all needed runtimes included!

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 10 of 20
(1,142 Views)