Randy

As the description states, the issue I'm having is with an application I've developed which utilizes class "plug-ins". I've also posted this issue on the main discussion board at NI (http://forums.ni.com/t5/LabVIEW/Get-LV-Class-Default-Value-Error-1498/td-p/1129973) but I thought I'd get it over here as well since from my experience this board is more finely tuned to LVOOP development. In short, the plug-in architecture works fine in development environment or if the plug-in doesn't utilize any hardware drivers (i.e. mxDAQ, Fieldpoint, Serial) in the runtime environment but if I try to load a class which contains a hardware driver in the compiled program it throws a 1498 error. What I've traced this error to is that the class cannot be loaded because it appears to be broken (even though it loads fine in development). I've tried different methods of compiling, including classes, hardware drivers, etc but cannot seem to find a solution. If anyone has any thoughts or has conquered this issue in the past I'd appreciate the wisdom. If you want to get a simple example of what I'm talking about, I attached one to the discussion linked above. Thanks, Randy

Name: Calling External Javascript Submitter: LAVA 1.0 Content Submitted: 03 Jul 2009 Category: Database & File IO LabVIEW Version: 8.0 Version: 1.0.0 License Type: Creative Commons Attribution 3.0 Potentially make this available on the VI Package Network?: Undecided Copyright © 2006, Randy Recob All rights reserved. Author: Randy Recob --see readme file for contact information Description:: An example of utilizing external javascript in Labview. In this example an external javascript is loaded into Labview and it's functions are called to modify an existing XML database/file by adding information passed to the javascript function from Labview. Included in this zip file are the following: CallingJavascript.vi - Example vi users.xml - XML database file users.xsl - Extensible Structure Language for converting XML to HTML users.htm - Webpage for displaying database contents xml.js - External javascript called by Labview and users.htm All files must be located in the same directory. Version History: 1.0.0: Initial release of the code. Click here to download this file

I'm still not able to get this functionality to work, I've tried posting a couple of different labels on the front panel with no success (I've perused the binary file and don't find any mention of the keywords that get coded in the labels). I have been able to make this work putting the tags in the VI description (which I could pull out to the front panel or splash screen) and I thank you for the insight on the fixed length keyword replacement information to allow that but it would be nice if I could just paste a text label on the VI and not have to go through the coding. Any more insight would be appreciated (maybe I'm not finding the correct label). QUOTE (Chris Davis @ Feb 7 2009, 01:45 PM)

Thanks, kind of what I was thinking from the research I've conducted...I think we'll move to a panel PC with a full blown OS instead. Thanks again, Randy QUOTE (jgcode @ Nov 5 2008, 04:23 PM)

I'm looking at implementing a system that publishes a vi through the labview web server for remote access/control. I'd like to be able to view this webpage on a PDA/Windows CE device and was wondering if there is a runtime deployment for Windows CE that would allow this kind of remote panel type setup since I've needed to install runtime on PC based machines with a similar setup. I'm operating with LV8.6 on the system acting as a web server. Thanks

Just a note for those of you who were using the instructions above to automatically add the svn:needs-lock property to labview files before commiting to the repository. I had multiple issues with the setup of the pre-commit hook file in the linked wiki, what turned out to be the problem was some issues with text parsing, I cleaned up the issues that I found (it was a major headache to debug) and am posting the modified coded below, please note that the SVNLOOK and TEMP variables are specific to my installation and may need to be modified for yours. Regards, Randy @ECHO OFFset REPOS=%1set TRANSACTION=%2set SVNLOOK=c:\svnserve\svnlook.exeset TEMP=c:\repository</P> <P>if exist %TEMP%\tempfile%2 del %TEMP%\tempfile%2for /f "usebackq tokens=1*" %%i in (`%SVNLOOK% changed -t %2 %1`) do @if NOT %%i==_D @echo %%j>> %TEMP%\tempfile%2 if not exist %TEMP%\tempfile%2 goto NOFILESADDED for /f "usebackq tokens=*" %%i in (`findstr /E /I /R "\.bmp.$ \.gif.$ \.ico.$ \.jpeg.$ \.jpg.$ \.png.$ \.tif.$ \.tiff.$ \.doc.$ \.jar.$ \.odt.$ \.pdf.$ \.ppt.$ \.swf.$ \.vsd.$ \.xls.$ \.zip.$ \.vi.$ \.vit.$ \.ctl.$ \.llb.$ \.dwg.%CONTENT%#34; %TEMP%\tempfile%2`) do ( %SVNLOOK% propget -t %2 %1 svn:needs-lock "%%i" 1> nul 2> nul if ERRORLEVEL 1 ( echo commit denied, binary files must have property svn:needs-lock >&2 type %TEMP%\tempfile%2 >&2 del %TEMP%\tempfile%2 EXIT /B 1 ) ):NOFILESADDEDdel %TEMP%\tempfile%2EXIT /B 0 QUOTE (jdunham @ Oct 5 2008, 11:54 PM)

many different ways... QUOTE (highreel @ May 6 2008, 10:20 PM)

QUOTE(jpdrolet @ Jan 3 2008, 01:03 PM) That did it...I knew it was something I was missing. Thanks for the help. :thumbup: Randy

When running the attached code in Dev environment, no problems but as soon as the code is compiled the setting of the "VI Name" throws an error. I'm using a template VI and then launching multiple instances but I'd like to name each VI created so that the operator knows which test station the VI is tied to (i.e. "Test Station 1", "Test Station 2"). The code works well up until the setting of the aforementioned property (reference is opened, EFT_Ctrl data is passed and the cloned VI is opened then comes the error). Any ideas on how I can make this work in an executable? Thanks, Randy

I've found that working through XML files can be quite tedious in LabView due to the lack of garbage cleanup (each time you open a node, property, etc. you need to make sure you close the reference). I'm currently generating custom XML files on my test systems by calling/passing arguments to an external javascript which has automatic garbage cleanup (will close all references once code has executed). You can see a simple example of what/how I'm doing this here. QUOTE(Phil Duncan @ Dec 5 2007, 08:28 PM)

You may want to check out this (xml using javascript) piece of code I put into the repository, it utiilizes javascript to write to an xml file with the msxml active x objects. The benefit of doing this through the javascript interface is the garbage collection built into javascript where as using the msxml active x objects in Labview can be cumbersome due to the continuous opening and closing of references when working through an xml file. While the example is simplistic, with a little investigation you can turn it into a powerful tool for documentation. The following is an example of an xml file being generated on one of my test systems. XML file example QUOTE(Kalmar @ Apr 22 2006, 02:01 PM)

A better example one of my system's test results stored in an xml. Download File:post-3040-1165338503.xml

Thomas, Glad it helped ...just another example of utilizing external code to read xml files. It's important to realize what the javascript is doing because it is very specific to the XML file you submitted. The vi is loading the javascript code and then calling three functions in the javascript. The first function is loading the XML file that you located through the dialog, the next function is searching the XML for the "//Info/Created" and "//Info/Culture" node values and the third function is stepping through all the "//MeanPublic" nodes and putting the contents of the nodes into a spreadsheet string. This string is then passed to LV where it is put into an array. A better example of calling external javascript and accessing/writing XML files can be found here: http://forums.lavag.org/CR-Calling-Externa...ript-t4977.html Randy