LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

CRIO 9073 Question

I think this image shows the issue.  I am using a network shared variable.  I send the command to set DISC_OUT::LIN OUT::VALUE to false.  

 

The command executes, it can find DISC_OUT, but there does not seem to be anything under DISC_OUT, so it does not fine LIN OUT so it returns the Label Not Found as the Command Response.

 

Any thoughts on what may be going on?

 

Capture2.PNG

0 Kudos
Message 11 of 16
(204 Views)

OK, I see where the Labview VI is writing the label names and I can minpulate it manually.  The program reads the Label names from an XML file, and then writes them to the CRIO to initialize it.  I believe the issue is with the reading of the XML file, specifically, sending the expression for parsing the XML.  I am trying to understand what @SystemName means in the below expression.  Does it mean the PC Name?

Capture.PNG

0 Kudos
Message 12 of 16
(196 Views)

Hi 5060,

 


@Fifty60 wrote:

I believe the issue is with the reading of the XML file, specifically, sending the expression for parsing the XML.  I am trying to understand what @SystemName means in the below expression.  Does it mean the PC Name?

Capture.PNG


The image in your message shows text that I would expect in a TestStand sequence: where does those text come from?

(The "@" char can be used in TestStand to indicate filepath data when using a string variable.)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 13 of 16
(192 Views)
The "@" char can be used in TestStand to indicate filepath data when using a string variable.)
IDKNT!
Learning every day

"Should be" isn't "Is" -Jay
0 Kudos
Message 14 of 16
(182 Views)

Hi Jay,

 

I use the "@" this way:

Otherwise TestStand requires you to use double backslashes in filepaths, the @ allows to use single backslashes...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 15 of 16
(158 Views)

Thanks for all of the replies.  I was able to get my issue resolved.  Final problem was that the XML query was looking at the wrong configuration file.  Definitely learned a lot, thank you!

0 Kudos
Message 16 of 16
(149 Views)