NI VideoMASTER and NI AudioMASTER

cancel
Showing results for 
Search instead for 
Did you mean: 

Changing NI PQA PXIe-1491 Provider Setting During Run Time

I'm posting this question here because VideoMaster and AudioMaster are the closest things related to PQA; I couldn't find the PQA forum location so here it goes.

 

I have a requirement that our software needs to change the PXIe-1491 video source programmatically, this is because we have 4 1491s in one PXIe chassis and I want to be able to switch between 1491s during run time.  Previously I would switch 1491s by adjusting the configuration file, although at the moment this will not suffice.  By the way I have already created help ticket with NI which is 2029965.

 

After using the PQA LabVIEW API to make this happen I realized that I kept receiving the following error:

 

Untitled.png

 

Below is a sample VI that shows what I'm trying to do, I have also attached it if someone needs to run it.

 

Untitled.png

 

So I then dropped PQA GUI.vi before the PQA Start.vi to see what the settings are when trying to run PQA.  Below is what I saw:

 

Untitled.png

 

You will notice that the Stream0 is blank which explains why I'm seeing the error that I mentioned above. When I change the Audio Source or Video Source they appear to stick and show up in the GUI although nothing happens when I change the Stream0 in code.

 

 

 

 

0 Kudos
Message 1 of 3
(10,143 Views)

Hi Daniel,

 

After working with our PQA R&D group this morning we were able to track down the cause of this issue. When programmatically setting the Stream0 (or Stream1) resource, you have to also set the RIO task string so that the name you are selecting is included there, otherwise the PQA API won't recognize it as a valid name. If you edit your code to be formatted similar to what I'm showing below I believe you will see that Stream0 input populate into the GUI when you call the niPQA GUI VI.

 

PQA GUI.png

 

This is supposed to be a safety check to make sure that you are connecting to the correct devices for your test, but it can cause issues with the LabVIEW API if you don't set the RIO task string because you may be checking your device names against an empty array.

 

Let me know if this works on your end as well.

 

Best Regards,

Peter W.

Message 2 of 3
(10,122 Views)

Thanks for the response, this appears to work!

0 Kudos
Message 3 of 3
(10,117 Views)