My issue is basically the same as this from 5 years ago
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:
When I create an instance I get
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.
Solved! Go to Solution.
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.
This is a bug. I would expect the custom XML to propagate through the Initialization VI. I filed Bug 214138 for this.
Staff Product Support Engineer
A fix has been submitted and will be available in the next release of VeriStand.
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-->