NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Start a Real Time VI and move to the next step

If you are not creating a build (of any form) then forget about my comments, as the problems are not related to that.  

 

Just to confirm, the situation you have is that if you run RIO_Initialise from LabVIEW it starts RIO_Controller successfully, but if you call RIO_Initialise from TestStand running on the same machine you get a 1004 error?

 

Can you run an Analysis of your TestStand sequence to see if that picks up any Severe errors.

0 Kudos
Message 11 of 18
(941 Views)

Yes, this is exactly the problem. If I run Initialise_RIO from LV project, it works perfectly. If I run the same Initialise_RIO VI using TestStand Action step, I get the error 1004. 

 

Regards

John

0 Kudos
Message 12 of 18
(938 Views)

Is the RIO_Controller VI still running from the LV call to RIO_Initialise?

 

Maybe go for a Power Cycle and then run your TestStand sequence first?

0 Kudos
Message 13 of 18
(927 Views)

The open VI reference function can take a path input (path of RIO_Controller VI) as well as a string input (just the RIO_Controller VI file name). If I input string, it works perfectly in LV, but produces error 1004 in TestStand (understandable because path is not wired). On the other hand, if I input path input to the open VI reference function, the TestStand produces error 1003 (in which the open FPGA reference gets destroyed).

0 Kudos
Message 14 of 18
(926 Views)

Do you have this sort of thing inside RIO_Initialise

Launch VI.JPG

0 Kudos
Message 15 of 18
(920 Views)

The path is not like this. When I browse the path of the RIO_Controller VI, it automatically changes the direction of the slashes and becomes something like this. I think this is because of the NI Linux RT target.

JohnRick7117_0-1599138358700.png

 

0 Kudos
Message 16 of 18
(916 Views)

We have different setup, we are going Windows to FPGA, whereas it looks like you are going Windows to RT to FPGA?

 

Are you able to post your sequence/code?

0 Kudos
Message 17 of 18
(895 Views)

Yes, my architecture is Host (Windows) to RT to FPGA. I am afraid I won't be able to share the code due to confidentiality reasons as it is an external project. Anyways, if you get an insight about this problem, please let me know! Any help will be appreciated!

 

Regards

John

0 Kudos
Message 18 of 18
(888 Views)