Setting Search Directory with LabVIEW RTE

Hi,
I've LabVIEW 8.0.1 run time engine installed on target computer and would like to run LabVIEW executable on target computer. I also have required low level support VIs for developed VIs.
Question is: how do I set the search directory for low level VIs with LabVIEW run time engine installed on the system.
Suggestions/comments are appreciated. Thank you.

If your hierarchy is the same as was in the IDE, then there won't be a need to search for the VIs. If the VIs are not found where they are expected to be, then LV (including the RTE) starts to search for them first in the folder where the VI\application is and then in the folders in its list. To change the list, you need to place the viSearchPath key in your application's INI file. You can copy this key from the labview.ini file and then modify the paths listed in it.
Try to take over the world!

Similar Messages

Search directory with a portion of a filename

I need to make a page that I can search a directory and it's subdirs for files that contain the text supplied. Can anyone help me? Thanks.

I was looking at the class methods, but I am still not sure on searching for filenames. Use listFiles(FileFilter filter) - Returns an array of abstract pathnames denoting the files and directories in the directory denoted by this abstract pathname that satisfy the specified filter? Can someone give syntax on this?
Let me give my game plan and if you maybe tell me there is a much better way of doing this, that would be appreciated. We have about 7000 docs that I want to search from the parent dir down through all of the subdirectories using a string value that may only be a portion of the filename. We are currently using perl for this and want to convert it to jsp. I was thinking I could do a listfiles into an array then search the array. But my concerns are that a) 7000+ possible IFs b) how do I get a file listing of the parent and all subs and all their subs and so on? Please help out, I really appreciate it.
Basically here is my starting point with the code:
String subDir = "/docs";
out.println(subDir+"<BR>");
File f = new File(subDir);
File[] files = f.listFiles();
for (int i=0; i < files.length; i++) {
out.println("<br>" + files);

How can I set the SRQ bit on GPIB with LabView ?

Hello,
I am developping an application with LabView RT on a PXI RT system. This application acts as an instrument (non controller GPIB), and I need to assert the SRQ line. How can I do that ?
I know the ibrsv function, but I can't find it in LabView, and I can not use it through a DLL call since GPIB DLLs are not compatible with Real-Time.
Thank you.

Hello Alfonso,
It sounds like you might be getting errors -200279 and -200278. (In the future, if you post the actual error codes, it helps us to know exactly what is happening). Error -200279 happens when you are performing a hardware-timed acquisition (meaning the data is sampled according to a clock signal on your board), but your LabVIEW program is not reading the values from the buffer allocated for that task in computer memory fast enough. Basically it's a buffer overflow error. It means older samples have been overwritten before you attempted to read them out. As the error message suggests, "increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all available samples might correct the problem." For more information on this error, please see the KB (DAQmx) Error -200279 During a Continuous, Buffered Acquisition.
Error -200278 happens most often when you have configured a finite acquisition, but are calling the DAQmx Read function in a loop. If you want to perform a finite acquisition, you should only call DAQmx Read once. For more information on this error, see the KB Error -200278 at DAQmx Read.
Finally, please refer to Abhinav's earlier post about the sample rate on the 9237 module. As he described, the NI-DAQmx 8.3 driver will only allow you to set the sample clock to integer divisions of 50k (50,000/n, where n can be 1, 2, 3...13). Since the maximum divisor is 13, the smallest sample rate that can be used is 3.846 kS/s. You can check what value the driver is actually using for the sample clock by reading from the SampClk.Rate property of the DAQmx Timing property node.
I hope this helps! Let me know if you have any questions about what I've described.
Best regards,

How set parameters of AKD driver with LABVIEW ?

Hi
I am looking a simple example to set or read paramaters of AKD driver with Labview .
The AKD has ethernet communication and the control is analogue - AKD-P00306-NBAN-0000
I want to use Labview to read the same paramerters like Kollmorgen WorkBench
Thank you for you help
Solved!
Go to Solution.

Hi k-usa,
We use Workbench to access these parameters, and unfortunately for many of them there isn't a way to access them in LabVIEW. The manual for using the AKD with our C-Series modules (http://www.ni.com/pdf/manuals/375516b.pdf) specifies setting these parameters in Workbench for this reason. I apologize that there isn't a way to access many of them in LabVIEW.
Julian R.
Applications Engineer
National Instruments

Error when trying to set up OPC I/O server with LabView 2009

Hi.I get an error when I try to set up OPC I/O server with LabView 2009 and the DSC module. If I open an empty project, right click ”My Computer”. Select new / I/O Server… and then OPC Client, the following error appears: Unable to browse OPC Server from the selected machine.Error -2147467262 occurred at GetOPCServerList.viPossible reason(s):LabVIEW: (Hex 0x80004002) No such interface supported. I have tried to repair LabView, but with no luck. Any idea what it could be?

The problems are not related to each otherOk then. Lets try getting this solved. Lemme dig......

How can I build app's for RTE 8.0 with Labview 8.2

Is there a possibility to build applications with LabView 8.2 in a way to execute them with the RTE 8.0. It's not a problem to save the sourcecode as LabView 8.0 format, but if I build this code e.g as *.exe and try to execute with RTE 8.0 an error occured. The errormessage is, that it's not possible to execute an file created for RTE 8.2 with RTE 8.0. What is to do to build an RTE 8.0 compatible application?

Applications written for 8.0 will only run with the 8.0 rte. New applications written for 8.2 will run only with the 8.2 rte. Your internal support doesn't know what it is talking about if they think otherwise. No need to upgrade the rte unless you paln to rebuild the 8.0 apps with 8.2. Both run times can be installed on the same pc if the old apps are working. Not much reason to change unless they need to be edited and you use 8.2 as the editor. I would image that if you build a new app in 8.2, it would have to undergo the same quality check as the 8.0 applications.
You are able to do a save as for 8.0 so that users with 8.0 can open them and use them with the older version. It's simply not possible for a newer development environment to target a build for an older run-time. Before you even do a build, the source code is compiled for the version you are currently using. The only way to swithc compilers is to switch versions of LabVIEW.

Who can i make a set-reset flip-flop with labview interacting with for cycle outputs

Who can i make a set-reset flip-flop with labview interacting with for cycle outputs

Are you wanting a VI that emulates a RS filp flop, or do you have a question about using an actual one?
You can make a RS flip flop by knowing the 4 states:
R=0, S=0, Q=no change
R=0, S=1, Q=1
R=1, S=0, Q=0
R=1, S=1, Q=?(invalid condition)
I have attached a RS flip flop VI in LV version 6.0
dhuff
Attachments:
RS_Flip_Flop.vi ‏34 KB

LabView TestStand interoperability with LabView runtime adapter

I would like to get some background information on how the interoperability of LabView and TestStand works.
We are using LabView steps mainly for some minor tasks in TestStand projects.
We do not use the regular deployment way as proposed by NI, but simply use one or more VI folders from which we reference LabView steps.
Deployment is done by copying the whole TestStand/LabView folder structure to the target machine.
We use the LabView runtime adapter within on our deployed systems.
We never mix LabView versions within one project.
Now, we frequently face the situation that the exact same project structure on two different machines has problems with the LabView steps.
So one changed VI runs on one target machine while the other after copy deployment is broken. Due to the same project structure and the virtual drives the paths must be the same.
A mass compile usually solves the situation.
So this is mystery number 1.
Today, I had the same problem, however I did not mass compile the full VI folder but simply some folders which I assumed had changed.
One VI which was referenced by TestStand was not mass compiled and was declared as broken by TestStand.
All I did was opening the broken VI in LabView Development System and nothing was obviously changed by LabView.
I closed the VI and pressed the Reload VI button on the TestStand step and the VI was working again, however the sequence file now had changed somehow (* at file name).
Another phenomenon:
An existing project on a machine was running with a certain user.
After switching the user, the VI steps of the project were suddenly broken.
My questions?
1) Why do VIs which run in the development system flawlessly become broken in the runtime?
2) Does the runtime use different search paths than the development system?
3) What kind of information does the mass compilation produce and where is it stored.
4) What kind of information does TestStand store along with the VI?
5) Is there a way to diagnose the problem with the runtime adapter ? With the runtime adapter I cannot open the VI to see what is the problem and in the developer mode it works.

First, to clarify a few points:
1) It is not necessary to use a workspace for TestStand deployments. You can specify a directory of source files for a TestStand deployment.
2) TestStand licensing should not be affecting this issue in any way. TestStand licenses do not have any impact on LabVIEW VI execution in TestStand.
Thorsten,
The issues you are describing are likely being caused by the LabVIEW VIs needing to be recompiled. The runtime engine is not able to recompile VIs, but the LabVIEW Dev System can, so this explains why you are able to execute again after opening the VIs in LabVIEW Dev. it also explains why a mass compile fixes the issue.
There are a variety of reasons why this could be happening. One scenario that could cause this to happen is that you make a change in one VI, but the change causes a second VI to need to be recompiled. This could cause a problem if you redeploy only the VI that you changed, because it will not be able to work properly unless the second VI is recompiled, which cannot be done by the LabVIEW RTE alone. This can happen because the LabVIEW compiler will optimize certain operations in the compiled code depending on where data is used--for example, the compiler will try to avoid allocating a copy of an array if it does not need to be accessed by multiple pieces of code at the same time. As you can imagine, this type of optimization might be appropriate for one version of your code, but might not be appropriate if a subVI changes such that it needs access to the array in parallel with the rest of the code.
The specific example I mentioned is called the Inplaceness Algorithm, and is described along with much more information about the LabVIEW compiler in this whitepaper. This might help explain the reasons a LabVIEW VI would need to be recompiled.
One potential solution to your problem that would allow you to keep your current deployment method would be to use packed project libraries (PPLs). You could have multiple PPLs for different parts of your code that you want to be able to update individually, which would allow you to make small changes to your codebase without having to deploy the entire set of code at once. A PPL is a self-contained set of compiled code that does not change, which should avoid the recompile issue from occurring.

Configuring dynamically loaded VI's search directory for both 64 and 32bit

Background:
I have an application that has been developed, built in LV2012 32bit. It needs to run on a 32bit and 64bit machine (Win7, I understand the application itself will only ever be 32bit, but it needs to run in both environments). The application dynamically loads a bunch of VI's which are raw vi's on disk (think just copy directory of files over from developer machine to the target machine that already has a exe running -- and just a copy, not a build of any sort). All of these dyanamically loaded vi's at some point reference vi.lib, so I have a few things I need to do to the application to get it to work
a) within the .ini file for the running exe viSearchPath=......C:\Program Files (x86)\National Instruments\LabVIEW 2012\<<bunch of directories>>\*
b) within the VI object cache directory, I have a lvDistPath.txt file that includes C:\Program Files (x86)\National Instruments\LabVIEW 2012
This works just fine for when I deploy these files and run the application on a 64bit version of Win7. However, when I try to run the application on a 32bit version of Win7, it breaks -- LabVIEW is installed in C:\Program Files\.... (no (x86)).
I am stuck with the dynamic loading architecture we have, and I can't start making changes to my code because it's not my code that is specifying where to find the files -- it's LabVIEW's internal searching algorithm.
What can I do (short of managing two separate .ini & .txt configuration files, one set each for x86 and 64bit and managing two separate installers) to get around this problem?

It sounds like you really don't have a problem with a 32 bit app vs. a 64 bit app. It sounds like a problem with file paths being different on a 32 bit app on 32 bit windows vs. a 32 bit app on 64 bit windows.
Two things you could do.
1. (Not sure this would work.) Put 2 paths in the search directory, one for c:\program files path for 32 bit windows, and one for c:\program files (x86) for 64 bit windows. One or the other will exist. I don't know if something will hangup if it searches the other path that doesn't exist.
2. Since you are dynamically loading the VI's, you should specify the path when you are dynamically loading them rather than having LV search for them. There is a function called Get System Info in the File I/O >> File Constants palette that will return the path to the Program Files folder for you environment so that you can build on that to get to your dynamic VI path.

How can I create a new excel workbook only with labview

Hi everyone...
I'm trying to create a new excel workbook only with labview but I can't find the file in the hard disk.
Someone knows?
Labview 8,0
Attachments:
Create new WB with LV.vi ‏18 KB

You are not using the correct mechanism. Pull up the Example Finder in LabVIEW, click on the "Search" tab, and enter "Excel". Look for an example called "Write Table to XL". Use this as a starting point for creating new workbooks and adding data to it.
Note: on disk the example is at <LabVIEW install directory>\examples\comm\ExcelExamples.llb.
Message Edited by smercurio_fc on 06-05-2007 11:08 AM

Unable to set working directory (-2147024832) for some app installs

I've found several drivers on a Dell Laptop that don't play well with others in MDT 2012, so I started making an application install package for them instead. Most of them fail with an "unable to set working directory" error. I checked
the app install logs and they don't really make any sense to me. I know the process as a whole works, because I can install .Net 4.0 runtimes without any problems using the same method. The important bits of the ZTI App log are below. Would
be for any guidance on this, as I'm stumped and none of the searches on the exact errors are of much help.
A sample error returned in the wizard is:
WARNING - unable to set working directory (-2147024832)Error installing application Dell 3440_Chipset_Driver_JD3WN IMEI drivers 9.5.3.1520_A00: The system cannot find the file specified.
The ZTIApplication.log file contains the following... the first is one that works (.NET 4), the second is one that fails. (Not using code block for this one, it doesn't like it).
<![LOG[Validating connection to \\ITSASERVER\DeploymentShare$\Applications\Microsoft .NET 4.0 runtime 4.0]LOG]!><time="08:20:30.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1"
thread="" file="ZTIApplications">
<![LOG[Already connected to server ITSASERVER as that is where this script is running from.]LOG]!><time="08:20:30.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[ Change directory: \\ITSASERVER\DeploymentShare$\Applications\Microsoft .NET 4.0 runtime 4.0]LOG]!><time="08:20:30.000+000" date="09-27-2013" component="ZTIApplications"
context="" type="1" thread="" file="ZTIApplications">
<![LOG[ Run Command: \\ITSASERVER\DeploymentShare$\Tools\X64\bddrun.exe dotNetFx40_Full_x86_x64.exe /norestart /passive]LOG]!><time="08:20:30.000+000" date="09-27-2013"
component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI installing application ]LOG]!><time="08:20:30.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41031 sent: ZTI installing application ]LOG]!><time="08:20:30.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[About to run command: \\ITSASERVER\DeploymentShare$\Tools\X64\bddrun.exe dotNetFx40_Full_x86_x64.exe /norestart /passive]LOG]!><time="08:20:30.000+000" date="09-27-2013" component="ZTIApplications" context=""
type="1" thread="" file="ZTIApplications">
<![LOG[Command has been started (process ID 3212)]LOG]!><time="08:20:30.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 3212)]LOG]!><time="08:20:31.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 3212)]LOG]!><time="08:20:31.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1"
thread="" file="ZTIApplications">
<![LOG[Return code from command = 0]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Application Microsoft .NET 4.0 runtime 4.0 installed successfully]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41033 sent: Application Microsoft .NET 4.0 runtime 4.0 installed successfully]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[Property InstalledApplications001 is now = {9abb5842-9a8e-45c5-9268-4fa4e69dba34}]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[Application Microsoft .NET 4.0 runtime 4.0 needs a reboot, initiating.]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[Dependent application requested a reboot]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property SMSTSRetryRequested is now = true]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Exiting to initiate a reboot with retry (to pick up where we left off)]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[ZTIApplications processing completed successfully.]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41001 sent: ZTIApplications processing completed successfully.]LOG]!><time="08:23:48.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Entry: {dee65f94-e269-4eac-927d-6e06c0e0eb9d}]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Name: Dell 3440_Chipset_Driver_JD3WN IMEI drivers 9.5.3.1520_A00]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[################]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Validating connection to \\ITSASERVER\DeploymentShare$\Applications\Dell 3440_Chipset_Driver_JD3WN IMEI drivers 9.5.3.1520_A00]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context=""
type="1" thread="" file="ZTIApplications">
<![LOG[Already connected to server ITSASERVER as that is where this script is running from.]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[ Change directory: \\ITSASERVER\DeploymentShare$\Applications\Dell 3440_Chipset_Driver_JD3WN IMEI drivers 9.5.3.1520_A00]LOG]!><time="08:25:04.000+000" date="09-27-2013"
component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[WARNING - unable to set working directory: (-2147024832)]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="2" thread="" file="ZTIApplications">
<![LOG[ Run Command: \\ITSASERVER\DeploymentShare$\Tools\X64\bddrun.exe Setup.exe -s]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications"
context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI installing application ]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Error executing web service http://ITSASERVER:9800/MDTMonitorEvent/PostEvent?uniqueID=2a0f4469-d803-4976-b434-adbf06b85c23&computerName=Lat3440_0927b&messageID=41031&severity=1&stepName=Install Applications&currentStep=61&totalSteps=88&id=4C4C4544-0031-4610-8053-B7C04F4C5731,E0:DB:55:AC:48:1C&message=ZTI
installing application &dartIP=&dartPort=&dartTicket=&vmHost=&vmName=: The server name or address could not be resolved
(-2147012889)]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41031 sent: ZTI installing application ]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[About to run command: \\ITSASERVER\DeploymentShare$\Tools\X64\bddrun.exe Setup.exe -s]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread=""
file="ZTIApplications">
<![LOG[Error installing application Dell 3440_Chipset_Driver_JD3WN IMEI drivers 9.5.3.1520_A00: The system cannot find the file specified.
]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="3" thread="" file="ZTIApplications">
<![LOG[Error executing web service http://ITSASERVER:9800/MDTMonitorEvent/PostEvent?uniqueID=2a0f4469-d803-4976-b434-adbf06b85c23&computerName=Lat3440_0927b&messageID=41032&severity=3&stepName=Install Applications&currentStep=61&totalSteps=88&id=4C4C4544-0031-4610-8053-B7C04F4C5731,E0:DB:55:AC:48:1C&message=Error
installing application Dell 3440_Chipset_Driver_JD3WN IMEI drivers 9.5.3.1520_A00: The system cannot find the file specified.
&dartIP=&dartPort=&dartTicket=&vmHost=&vmName=: The server name or address could not be resolved
(-2147012889)]LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41032 sent: Error installing application Dell 3440_Chipset_Driver_JD3WN IMEI drivers 9.5.3.1520_A00: The system cannot find the file specified.]
<![LOG]!><time="08:25:04.000+000" date="09-27-2013" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
Why can't it find it or set the working directory, especially when it's already validated that it's there?
--smthng

I'm not familiar with how Dell does their client side software, but for the server-side software (my area of expertise), I've always done something like the following:
I recommend running every application install in a VBScript/Powershell wrapper. You get logging for the application back on your SLShare as well as its cleaner (you can replace Drivers A05 with A06 by changing the script, rather than editing the application
in MDT).
sApplicationName = "Dell 12G Chipset"
oLogging.CreateEntry "Install-" & sApplicationName & ": Starting " & sApplicationName & " installation", LogTypeInfo
'//Set Destination Folder
sDestFolder = "c:\temp\"
'//Set Source Install Directory
sSourceDir = oUtility.ScriptDir
sSourceDir = sSourceDir & "\Source"
'//Check that folder exists, if not, create it.
oLogging.CreateEntry "Install-" & sApplicationName & ": Check that " & sDestFolder & " exists.", LogTypeInfo
if not oFSO.FolderExists (sDestFolder) then
oFSO.CreateFolder sDestFolder
End If
'//Copy folder from MDT share to C:\Temp
oLogging.CreateEntry "Install-" & sApplicationName & ": Copy from " & sSourceDir & " to " & sDestFolder, LogTypeInfo
oFSO.CopyFolder sSourceDir, sDestFolder
'//Sleep for 2 seconds to allow copy to finish
wscript.sleep 2000
sFile = sDestFolder & "Source\setup.exe"
'// Check if file/folder exists
If not oFSO.FileExists(sFile) then
oLogging.CreateEntry "Install-" & sApplicationName & ": " & sFile & " was not found, unable to install " & sApplicationName & "", LogTypeError
ZTIProcess = Failure
Exit Function
End if
'// Create log entry to show file being run
oLogging.CreateEntry "" & sFile & " -s", LogTypeInfo
iRetVal = oUtility.RunWithHeartbeat("" & sFile & " -s")
if (iRetVal = 0) or (iRetVal = 3010) then
ZTIProcess = Success
Else
ZTIProcess = Failure
End If
wscript.sleep 15000
'// Disable Zone Checks
oEnv("SEE_MASK_NOZONECHECKS") = 1
'//Folder Cleanup
oFSO.DeleteFolder sDestFolder & "Source"
I always copy any drivers that are installed after the fact (everything for me other than SAS/NIC drivers) to the C:\Temp as it can break. I always update my NIC drivers during the build to the latest Dell software using their packs. I try to
not mess with my boot image unless I'm adding a new model that is not supported by the built-in drivers.

Warner/superior electric's SS2000PCi motion controller interfacing with LabVIEW 6i

Sir,
In our application, we are controlling the movement of X-Y arm on the X-Y table. For this we are using superior electric products:
(a) Slo-Syn SS2000PCi Programmable Step Motor Controller
(b) MD808 Motor Drive
We are using two such controllers and motor drives to drive two 2 Amps Sanyo Denki Stepper motors: one each along X-axis and Y-axis. Along with the arm movement a data acquisition also has to be carried out. So, the motion control and Data Acquisition has to be synchronized by means of software. The problem now is to program the controller. Though MCPI Version 4.41 is there, we want to program the controller in LabVIEW 6i so that we can synch
ronize both motion control and Data Acquisition.There is no driver which is compatible to LabVIEW 6i.
Is there any 32-bit DLLs for this controller? If any one has these dll's please let me know. My E-mail ID: [email protected]
So that i can call these DLLs in LabVIEW 6i and program it.Or else send me at least the detailed low level command sets of the controller in pdf format so that i can develop our own drivers.
Regards,
Nagendra

Nagendra,
Unfortunately, I was unable to find any helpful resources for you based on a cursory web search. I recommend that you contact the manufacturer of the hardware and ask them if they have a driver (DLL) that you can use to interface with LabVIEW.
Good luck with your application, and have a good day.
Sincerely,
Darren N.
NI Applications Engineer
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Integrating TortoiseSVN with LabVIEW's Compare tool

I’m trying to set up the TortoiseSVN Diff tool, as described:
https://decibel.ni.com/content/docs/DOC-12175 and
http://digital.ni.com/public.nsf/allkb/3BEC521972301FF2862576EA00609CA6
To configure TortoiseSVN to use LabVIEW’s compare tool I added the following for “.vi” file extensions:
"C:\Program Files (x86)\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" %mine %base -nobdcosm –nobdpos
The links above tell you use “Program Files,” but on my system the LVCompare.exe is located in my “Program Files (x86)” directory.
When I try to run the diff tool (right click on the file in question -> TortoiseSVN -> Diff with previous version), I get the following error:
I cannot get the LVCompare tool to work with the command prompt either, as described:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configlvcomp_thirdparty/
I did notice that it mentions the Compare tool is only available with LabVIEW Professional Development System. Does this apply for using it with TortoiseSVN as well? I am running LabVIEW 2011 Full Development System on Windows 7 (64 bit). The version of TortoiseSVN I am using is: TortoiseSVN 1.7.6, Build 22632 - 64 Bit , 2012/03/08 18:29:39 Subversion 1.7.4.
Any help getting the LVCompare tool integrated with TortoiseSVN to work would be greatly appreciated!
Thanks!
Lauren

Lauren_CPC wrote:
I cannot get the LVCompare tool to work with the command prompt either, as described:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configlvcomp_thirdparty/
I did notice that it mentions the Compare tool is only available with LabVIEW Professional Development System. Does this apply for using it with TortoiseSVN as well? I am running LabVIEW 2011 Full Development System on Windows 7 (64 bit). The version of TortoiseSVN I am using is: TortoiseSVN 1.7.6, Build 22632 - 64 Bit , 2012/03/08 18:29:39 Subversion 1.7.4.
Yes it does. LVCompare is only a simple wrapper executable that eventually tries to run a VI in the LabVIEW installation directory. And this VI will not work if the LabVIEW installation is not licensed as Professional Development system.
Note to the AEs: In the second link of Laura's post, it states incorrectly: Primary Software: LabVIEW Development Systems>>LabVIEW Base Package
This is completely contradictory to the note in the last link, that states that the Professional Development System is required. A documentation correction request seems in order.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Callable VEE with LabView? / Accessing HP Lan gateways?

Hello,
We have several years worth of HP VEE code written and are now exploring
LabView as a new development tool. HP VEE provides something called
"Callable VEE" which loads a server and allows any program which can
"access C routines" to call HP VEE's userfunctions. Has anyone had
experience implementing such a hybrid? Can examples be found anywhere?
While this is probably not the best solution it would give immediate
access to a lot of proven code. Are there any better solutions to
accessing the HP VEE code base?
Also, there are currently several Lan <--> GPIB gateways installed. Is
there any way LabView can access these lan-drops to access the test
equipment installed there?
Alternatively,
is it possible to set up a computer with LabView as a
test site and have others log on to it over the lan and access all local
resources (serial ports & GPIB devices) remotely (without having to use
Timbuktu) ? Any examples or ideas would be appreciated.
Thanks in advance for any help,
joel

> We have several years worth of HP VEE code written and are now exploring
> LabView as a new development tool. HP VEE provides something called
> "Callable VEE" which loads a server and allows any program which can
> "access C routines" to call HP VEE's userfunctions. Has anyone had
> experience implementing such a hybrid? Can examples be found anywhere?
>
LV has a node called the Call Library Function Node that can call
functions within a DLL. If the VEE object looks like a DLL, then
it should work. I'm not aware of any examples laying around, but
I do know of organizations that use both; so they might be good
places to start. I know that JPL uses both.
> While this is probably not the best solution it would give immediate
> access to a lot of proven code. Are there any better solutions to
> accessing the HP VEE code base?
>
> Also, there are currently several Lan <--> GPIB gateways installed. Is
> there any way LabView can access these lan-drops to access the test
> equipment installed there?
NI sells an Ethernet-GPIB device that I think is similar. The device
comes with drivers that make it look just like any other GPIB device
hooked to the computer. If the LAN/GPIB device has drivers, then it
should be possible to hook it into LV. It is probably access normally
through HP-VISA drivers. You might want to search the Knowledge Base
on the NI web site to see if there are any guiding instructions there
on whether to use the NI-VISA drivers instead.
> Alternatively, is it possible to set up a computer with LabView as a
> test site and have others log on to it over the lan and access all local
> resources (serial ports & GPIB devices) remotely (without having to use
> Timbuktu) ? Any examples or ideas would be appreciated.
>
It is currently possible to write smallish LV client programs that
talk to a LV server program to carry out the I/O. The programming
to do the client server stuff is quite easy using the VI Server.
It is also possible to write the client in most other tools and
communicate to LV over DCOM using the VI Server's ActiveX interface.
The interface publishes a class to the EXE to load VIs and make lots
of other changes, and another class to a VI that allows for Running,
printing, and lots of other changes. Remote interaction without
doing the client/server stuff isn't currently possible, but it was
demonstrated at NIWeek working in web browsers.
Greg McKaskle

Integrating custom PCIe hardware with LabView

Hi, I am new to LabView so appologize if question is in the wrong place.
I have a custom PCIe acquisition card that I want to use in LabView environment to postprocess some data. So far the board has been used successfully with its windows drivers and VS.NET software. What is the process for setting up a device like that in LabView? Can LabView use the COM object windows driver just like a Visual Studio project would? If yes, is there a document that explains how this is done?
I have worked with NI's own instruments where the driver is provided and seamlessly integrates into the LabView, but I am a bit lost with this custom non NI board.
Thank you.

Thanks. I tried searching that site for examples... but this is a board that our company has developed (software defined radio) and I am certain no one has written any drivers for it yet. Thats the problem statement that I am trying to research. What would it take to make the board we designed compatible with LabView. Since this is a Software defined radio platform, LabView offers some useful functions that can be used to postprocess and analyze data captured by our card.
Ideal goal is to have LabView module capture data from PCIe buffer allowing for further processing (filtering, FFT, demodulation, etc...). I would appreciate if you can direct me to some examples or literature on this topic.
Thanks,
Anton

Setting Search Directory with LabVIEW RTE

Similar Messages

Maybe you are looking for