NI VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

"Custom XML" section for custom device

Solved!
Go to solution

My issue is basically the same as this from 5 years ago

https://forums.ni.com/t5/NI-VeriStand/Custom-Device-XXX-Initialization-VI-vi-how-to-use-quot-Custom/...

 

I made a custom device (Inline HW interface) from the scripting tool that does nothing. I added the following string to my custom device XML:

 

  <CustomXML>
    <SweetData>1.23</SweetData>
  </CustomXML>

 Initialization VI.vi has:

Capture.PNG

When I create an instance I get

c2.PNG

How can I get the custom xml to flow to my device as documented?

cd3.zip is my custom device, but all the steps to reproduce are above.

0 Kudos
Message 1 of 5
(1,094 Views)
Solution
Accepted by topic author smithedtes

For the record, I've confirmed the XML provided in my example is valid against the custom device XSD using an online validator. The XML and XSD also both come up as valid.

I've since worked around this by just parsing the xml file myself.

0 Kudos
Message 2 of 5
(776 Views)
Solution
Accepted by topic author smithedtes

Hey smithedtes,

 

This is a bug. I would expect the custom XML to propagate through the Initialization VI. I filed Bug 214138 for this. 

 

Thanks,

Andy

Staff Product Support Engineer

0 Kudos
Message 3 of 5
(747 Views)

Thanks for the update Andy 🙂

0 Kudos
Message 4 of 5
(742 Views)
Solution
Accepted by topic author smithedtes

A fix has been submitted and will be available in the next release of VeriStand.

 

SweetData.png

 

Note that you are limited to a single top level element in the XML. You can add additional elements under the top level element, but you should not have multiple top level elements.

  <!--This will not work-->
<CustomXML> <SweetData>1.23</SweetData>
<MoreSweetData>4.56</MoreSweetData> </CustomXML>



Message 5 of 5
(678 Views)