Jump to content

tadowden

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0

About tadowden

  • Rank
    LAVA groupie

LabVIEW Information

  • Version
    LabVIEW 2010
  • Since
    2010
  1. The VI does have a fairly normal name and I do not believe that anything would be throwing off the scripting. I do not know if there is anything unique about the name that is not generated in the parameters.xml file. I also do not know if the error occurs with the same parameter, because I do not know what the parameter should be. I will wait for you to post sections of the code. Thank you for your help.
  2. Bob, Thank you for the reply. I have resolved the first two issues but still receive the parameters.xml error. As I said before, this only happens some of the time. The error messages are reported when I select "Generate" on the "Generate Files" tool. The first message says "The parameters.xml file contains an empty name attribute. Please fix the file and recompact." The second message confirms the first and says "not well-formed (invalid token) at line 2, column 171, byte 279." This line within the parameters.xml file ends with <parameter id=""</parameter>, which clearly shows the empty name attribute. At other times when I do not receive this error, this line is complete and does not have an empty name attribute. Lastly, the error message directs me to line 187 of Parser.pm and line 51 of ListSpecifiedDoctypeFiles.pl. Do you think I need to change the code on either of these lines in order to resolve this issue?
  3. I am able to produce documentation for some but not all of my VIs. Occasionally, I am presented with an error that states: "parameters.xml contains an empty attribute." This error is followed by another that directs me to line 2 of the parameters.xml file where an invalid token exists. When I view this line I can see that there is indeed no attribute assigned. The second error also directs me to two other files: Parser.pm and ListSpecifiedDoctypeFiles.pl. Specifically, I am directed to line 187 of parser.pm and line 51 of ListSpecifiedDoctypeFiles.pl. Line 187 has $result = $expat->parse($arg); and line 51 has if($@) {mxDie "[$xmlPath]\n".$@;}. I would like to remove the bug in this code to prevent the need of manually entering an attribute for each problematic file. I am not sure why this works for some but not all of my VIs but if anyone can help it would be much appreciated. Thank you.
  4. I have completed the documentation process but when I open the chm file I am presented with an error that states: "The following mnu files did not contain resources or were duplicate filenames." It then lists the directory of the two mnu files that I have created for testing purposes under "Missing Resources." I have no "Duplicate Filenames." Lastly the message says: "Filenames that only have _pal.xml indicate Control palettes, which are not supported." I am still able to view the documentation for my VIs but would like to resolve this issue to properly format the table of contents. Thank you for your help.
  5. Bob, I have resolved the issue but now need your help with something else. After I had completed all of the steps I was able to view my chm file. I wanted to link this to the LabVIEW Help that a user selects from the main screen of LabVIEW (Help - LabVIEW Help). Within FAR, I used the help express wizard to specify the folder to be compressed, the title of the help window, the home page, and the destination help file. I then completed step 10 by specifying the directories of VIs, text files, and help file path. However, I somehow managed to believe that the destination help file should be the same as the help file path and after I restarted LabVIEW looking for my chm file within Lab VIEW Help I only found my chm file. All of the other files were gone. I am able to open the original chm files that were located in LabVIEW Help by searching in the help folder. In order to reverse this process and revert LabVIEW Help to its previous state, must I link all original chm files back to the lvhelp chm? Any help is much appreciated and I thank you for your help!
  6. Bob, I do not have any .txt files in my output directory. My output directory consists of ent files, html documents, JScript script files, xml documents, xsd files, and xsl stylesheets. I have completed steps 1 - 3 and am currently having trouble with step 4. Specifically, I am able to complete steps 4-1 through 4-3 but do not know how to execute step 4-4 or step 5. I skipped these two steps and tried to generate the xml files by clicking "Generate Files." This is when I received the error message and found my output directory full of files with the extensions above. Do you know how to add the 'topLevel=True' tag to the xml created for the top level palette? Also, do you know how to include the top level .mnu file for the palette? I am confused as to where to find this created xml file if the xml files are not generated until step 6. I have installed ActivePerl community edition version 5.14.2.1402. Please let me know if you need additional information. Thank you for your help.
  7. I have installed the VI to XML Documentation Tool in hopes of creating compiled help files for a VI library. I have also installed the required software programs found at the following link: https://decibel.ni.com/content/docs/DOC-18765 I am able to complete steps 1 - 3 (found in the same link) but after I tag the VIs and select "Generate Files" I receive an error message that reads similar to: "PERL was not able to generate files for allVI.xml." However, when I open the folder that I had designated for my files, I am able to find and open the .xml files of my VIs. I do realize that I skipped step 4-4, but do not know how to add the required tag before any .xml files are generated. Does anyone know how I may go about adding this tag? Also, because of the error that I get when I generate my .xml files, I am unable to move to the next steps and convert my .xml files to .html files. Any help is much appreciated. Thank you.
×
×
  • Create New...

Important Information

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