Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


amaggs145 last won the day on April 9 2011

amaggs145 had the most liked content!

Community Reputation

1 Neutral
  1. Hi Michael, Just curious if this feature is now available. Thanks! Regards, Anthony
  2. Can't Read Back XML Data

    Ah, okay great, thank you. I actually converged on this solution before I even saw the post here. I am noticing a trend, my last issue required the use of that Varray to Vcluster, this seems to be a useful one for XML toolkit Is there any documentation that explains why some data types work and others don't?
  3. Can't Read Back XML Data

    I am having an issue with reading back XML data that was written with the XML toolkit. It must be something simple that I am missing here. CantReadXML_Data.vi
  4. One of my colleagues that I work with uses Perl to read & write XML files. One on the features that he likes most about this is that the XML files are extensible in the sense that more information can be added to the files later without breaking previous code that was used to write and read the original version of the files before additional information was added. I was wondering if there is some tip or trick to having this same capability with the VI's available in the XML toolkit. One way that I was thinking of was instead of using "Easy Read XML File.vi" directly I could read the all the data within the file first with LAbVIEW's file read VI's, then do some processing on the text to extract only necessary data and then use "Easy Parse XML.vi" on select portions of the file. There may be some other method that would require less custom coding for each file. Thanks for any input. Regards, Anthony
  5. Writing out Variable Name and Value

    Yes, that is what I was looking for. Thank you very much. Just out of curiosity, within the XML VIs, when writing values to the XML file does it use the OpenG VI "Format Variant Into String" ? Thanks, Anthony
  6. In an application that we are using, we have many variables, they are stored in a data structure as variants although their type varies. I would like to be able write their names and values out to an XML file using a string as the name and just the variant as the value. This works for one element, however when I try to write them all out using an array I get Error 1. I have attached the VI. Maybe there may even be a better method for doing this, any suggestions are welcome. Thanks Write Variable Name and Value.vi
  7. Hi Michael, it has been a few months since we talked about this feature. I am just wondering if this is something that is likely to be available soon or is kind of on the back burner for the moment. I guess I am just trying to figure out if I should put the effort into a work-around (which means rebuilding packages etc..), or just deal with it the way it presently is because a solution will be available soon. Thanks
  8. Hi Michael, All of my packages thus far have RFI as the custom category. But there is a level below this custom category (the Functions level) that I want VI's to be added from different packages, I am not sure if this is possible or not. I am attaching my source code with the two packages that I am hoping that their VIs can be consolidated under 1 Functions palette. The 2 packages with VI's to be consolidated under 1 Functions palette. (The name of this Functions Palette is "RFI Comparison Tools") rfi_lib_valid_number_expression- rfi_lib_within_percentage-- There is also one other package included that is needed for a dependency: rfi_lib_plus_&_minus_percentage- Packages and Source Code.zip
  9. Yes, I have RFI as a custom category and under RFI I have RFI Comparison Tools as the Functions Palette, and it is this palette that I would like to be able to add many VI's from different packages.
  10. So I have created some reusable VIs, packaged them, and had them install in my palette here: Functions\RFI\RFI Comparison Tools This worked great for the first package, but then when I created a another package of a reusable VI's and wanted them to install in the same palette as above, it just created a duplicate RFI Comparison Tools palette and installed these new VIs there. However I would like the previously installed VIs and these newer ones to all install on the same palette. What am I doing wrong? Let me know if you need me to post the packages or source code. Thanks
  11. The issue with the existing package is that if the input is not a predefined LV data type, the VI will morph the input, and the output becomes a variant where I now have to convert back to my original data type. So I have created a package with the same code but it drops the code onto the block diagram instead of the VI. But whether or not this is a breach of license I don't think depends on the designer's reason/motive, does it? I guess my question was a general one, rather than specific to this circumstance. But indecently this circumstance is an example of what I am generally concerned about. Thanks
  12. By the way, on another note. Is the way that I recreated this package compliant with OpenG's software licensing? In general is it okay to take any code under the BSD licensing and modify it to suit specific needs as long as the license and liability clauses stay intact?
  13. Hi Michael, Yes sir, this did it! Thanks for your help.

Important Information

By using this site, you agree to our Terms of Use.