Search the Community
Showing results for tags 'xml'.
Found 8 results
-
Version 1.0.0
145 downloads
This XML test report library is available for you to modify at your will. It is based on the IPC-2547 standard so it is easier for any other application or database to parse. The html file report offered by LabVIEW was not sufficient for my need. So I created those. enjoy!!! -
View File .xml test report Measurements.zip This XML test report library is available for you to modify at your will. It is based on the IPC-2547 standard so it is easier for any other application or database to parse. The html file report offered by LabVIEW was not sufficient for my need. So I created those. enjoy!!! Submitter Benoit Submitted 02/26/2018 Category *Uncertified*
-
Hello all, My question is: what is your preferred non-volatile way of storing daqmx task configurations? Backstory: For a long time I've used ini files to maintain task configurations between executions of a program. This has worked for primarily static DAQmx configurations but I'm looking at creating a test executive with some degree of flexibility, which means daqmx task configurations start to get more complicated. If you use MAX for storing your tasks: Do you run into problems accessing and maintaining these tasks even though you don't have direct access to the file? Or i
-
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <DCT Version="V3.0" User="Administrator" FileType="4" TagListFile=""><DATASOURCE Name="Marchwood" User="root" Password="" Driver="PI"/><PLANT PlantName="Marchwood" UnitName="Plant" ConfigFile="MAR1_Avg_000.XML" ConfigFileCreation="16/04/2007 14:01:40" TimeBias="0" Locale="(GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London"/><DATA_MESSAGE Type="Average" TimeBegin="31-Dec-2007 00:00:00" TimeEnd="01-Jan-2008 00:00:00" SamplePeriod="00:05:00" RequestType="Automatic" TransferPeriod="24"><DATA_POINT
-
I'm building an application (which I am intending to share at a local user group soon), but am having issues with XML file data versioning. My intent is to have a data type which has a version string, and a variant for the data which will be read according to the version number in the version string. The issue is that if you flatten the data type to an XML string with any data in the variant, then try to unflatten the data, you get an error (1106: "LabVIEW: The XML tag describing the type of data does not match the wired type.") How have you done versioning for data files which you a
-
Hi all, I'm having problems with a program I've written that hangs after some period of running. The program is fairly simple but it does a lot of xml parsing so to fix the problem I'm looking for things like references that are not closed. I have found one unclosed reference in one of my subVI:s but I can't close it without breaking the program so I look to you for help. The reference in question is the "Node Out" reference in the NI_XML.lvlib:Get First Matched Node.vi marked in the attached file CloseRef. What I would like to do is really to wire it to the invoke node (and not use th -
For any who are interested, we've added a new tool to the MGI library to make Unflatten from XML more robust. You can read about it here, download it within VIPM for free. It handles cluster and enum changes that are outside of classes without throwing errors so you can get more forwards and backwards compatibility.
-
I am flattening an array of classes and loading into an MSSQL database in an XML column. When the XML is returned it is formatted to take up less space. Which means a line of "<Cluster></Cluster>" becomes "<Cluster/>". When returned in this manner I get an error: 1403 LabVIEW: Attempted to read flattened data of a LabVIEW class. The data is corrupt. LabVIEW could not interpret the data as any valid flattened LabVIEW class. Lines that have <Val/> and <Name/> work ok. It is only the custer tag that has the issue. I have attached two xml files...one with <
