Deployment Utility copies my MAX configuration to the target system

Hi,
I am creating an Installer for TestStand 3.5 and I have found that my MAX device configuration is carried to the target system. How can I prevent the installer from coping this configuration to the target system? My Labview VIs use VISA 4.1 to access Serial Ports.

Hello goldee,
In the TestStand Deployment Utility, select the Installer Options tab, and then click the Drivers and Components... button. Make sure the Include Hardware Configuration from Measurement & Automation Explorer checkbox is unchecked.
Let me know if that fixes it or not.
Kristen
National Instruments

Similar Messages

Where is the MAX configuration stored?

We had a PC die with a pretty convoluted set of MAX Tasks set up, but not exported.
Is it possible to retrieve the MAX configuration file off the HDD and load it into another machine running MAX?
Where is this file located?

Hi Jed,
The steps in this article for removing MAX Database corruption will show you where to locate the MAX Data folder (step 5 of "For earlier versions of MAX"). If you're on Windows Vista or Windows 7, this would be under: C:\ProgramData\National Instruments\MAX\Data.
You can copy the whole folder, but the main file of interest is config3.mxs, so you can try copying just that if all else fails.
Hope this helps!
Matt Lee
National Instruments
Applications Engineer

Problem importing max configuration

I would like to import my device configuration file programatically with MAXcopy configuration.vi but when I use it an error appears.
Here are the settings I entered:
source: H:\TEST DEPT LABVIEW FUNCTION TESTER\Labview program\configData.nce
destination: system://192.168.4.124
product:
replace mode: replace
error: code -2147220480
MAX Copy Configuration.vi<APPEND>
<b>Complete call chain:</b>
MAX Copy Configuration.vi
Initialize Max configuration.vi

Hi Yanndouglas,
Here is another work around for your problem. I hope this helps.
The error code is 2147220444 and says error occurred at MAX Copy Configuration.vi. Reason: the operation failed because of unresolved conflicts requiring user input.
The conflicts seem to be the warnings that appear when using the MAX import wizard when the imported file is going to overwrite an existing task. So the Replace option only works on export. On import the configuration has to be cleared.
A work around is to open MAX and pop up a dialog that explains how to clear the configuration. The user can then click the import button on the dialog and import the desired configuration without errors.
I hope this helps.
Kind regards,
Prashant M
Applications Engineer
NI UK & Ireland
Message Edited by Prashant M on 07-24-2009 04:52 AM
Message Edited by Prashant M on 07-24-2009 04:53 AM

Muti channel configuration for the keithley 2700

I am trying to do multi chanel configuration on the Keithley 2700. I will be using hundreds of channels and would like to be to pass configuraton once and not have to individually send configuration files. As seen in the examples, I can allready read mutiple channels.
Any input would be great. Also, I will be using a combination of voltage, amps, therocouples, and resistors. Not all configurations will be the same.
Attachments:
k2700_scan.zip ‏101 KB

In response to my question, it is best to create an array of clusters that has the channel number and the measurement type and input this array into a for loop with a ke2700 set channel list and a ke 2700 configure measurement. Similarly, you can use this same method to read a channel back. I found that if performance is an issue, it is best to group the channels by what type of measurement you want to do. This way the Keithley doesn't have to continually switch measurement types.
See example below.
Attachments:
ke2700_multichannel_config_and_read.zip ‏309 KB

What is needed to run the deployment utility while not logged into Windows?

I am running a bash script to perform nightly builds of our test s/w. This script calls the deployment utility via command line. The actual command I am using is:
/cygdrive/c/Program\ Files/National\ Instruments/TestStand\ 4.1.1/Components/Tools/Deployment\ Utility/DeploymentUtility -- build "C:\Sandbox\ATE\Production_Test_Projects\eHLC_RX\Deployment\Unified_eHLC_RX_Test_Deployment_Config.tsd"
It works flawlessly as long as I am logged into the PC. I have a cron job running to invoke my main script on a daily basis. As soon as I log out of the PC is when I am having the trouble. The script does get started but when looking at the processes on the PC I see my bash sessions open as well as the deployment utility open but it is not doing anything. If I end the deployment utility process the bash script continues and exits normally. Is there something I have to put in the command line to make the deployment utility work if I am not logged in? I have the cron running as a service and it is using my username and pw when required. But the deployment utility just hangs and does nothing. The deployment utility log is blank so it was basically opened but did not perform the build. Any ideas as to what may be causing this? Thanks in advance for any help.
Troy

Here is a little more information. I changed the service that is running my script which is calling the Deployment Utility via command line from This Account on the Log On tab which requires my username and password to Local System Account and checked Allow Service to Interact with Desktop. This time when I was logged out of the PC and the script started I logged back on and could see the message that was thrown when the Deployment Utility was initialized. I could not see this with the service set to the other parameter because it is running in the back ground. I am sure this is what is happening because in this state I check the processes on the PC and it is reflecting the same information. The memory usage is the same and the Deployment Utility is doing nothing obviously waiting for acknowledgement of this error. If I click OK the build does start but at the end I get all types of debug messages at the end which do not happen when I am logged in and this process completes. Does anyone have any idea what this error message is referring to and maybe how to fix it?
Thanks again for any help.
Attachments:
Startup_Error.JPG ‏80 KB

Deployment Utility and Labview Modules

Hi,
I am fairly new to TestStand. I have created a TestStand Sequence that calls a number of Labivew modules. Everything works fine on my development machine.
I am trying to deploy this to another machine running a base development license. I ran the development utility and created a setup.exe which I have just installed on the 2nd machine.
When I go to run my test sequence on the 2nd machine it cannot locate the labview modules called in the test sequence.
So my questions are:
Can TestStand deploy these files for me, or should I do it manually?
If it can, is there a specific folder I should store all labview moduels on my development machine so the deployment utility picks them up?
Is there any option in the Deployment Utility that I need to set for TestSTand to pick up these modules?
Is there any special option I should set in the sequence file? Search area???
Thanks & Regards,
Don1.
Solved!
Go to Solution.

Hi,
You should be able to see the LabVIEW VI's in your deployment tool. If you can't then that is why you can't see them on the target system.
Are you using a TestStand WorkSpace/Project files?
Regards
Ray Farmer
Message Edited by Ray Farmer on 02-11-2009 06:30 AM
Regards
Ray Farmer
Attachments:
deployment.JPG ‏70 KB

Installer created via Deployment Utility - disable uninstall before install?

With an Installer created by the TestStand 3.1 Deployment Utility, when the Installer executes it always has to first uninstall any deployed files that are on the target system. If I wanted to disable this feature and have the Installer just always overwrite existing files is there a way to do so?

Hi Snood1,
I was able to reproduce that message on my end here and unfortunately could not find a way to prevent that message or auto-uninstall. I tried using the command prompt, but could not get a silent uninstall to occur. I did however try it out on both TestStand 3.5 and 4.0 and each of these versions recognized that I was upgrading my deployment and installed over the old system with the new versions of the files. The only thing I know to recommend here is an upgrade of the version of TestStand if you want to prevent this message. If needed, click here for product information.
Best of luck!
Chris R.
Applications Engineer
National Instruments

Deployment utility drivers and components, some missing?

I have Testand 3.5 and LabWindows/CVI 8.5 installed on my machine. I would like to modify an existing TestStand deployment to include the LabWindows/CVI 8.5 Run-Time Engine, so that the installed program can run as an executable on the target system(s) without requiring a full install of LW/CVI. When I click on "Installer Options" and then "Drivers and Components" I see that the LW/CVI 8.1 RTE is available, but not 8.5. I've never had 8.1 on my machine. I have 7.1 and 8.5 installed. (See attached screenshot.) I assumed that the 8.5 RTE would be installed along with LW/CVI 8.5, but is this not the case?
-Joel
Attachments:
TS_deploy.PNG ‏31 KB

Hi Joel,
This is most definitely a bug with the NI Build Installer. The bug has been reported under ID 100489.
Rest assured however that although the Drivers and Components list shows CVI 8.1 RTE, it will actually bundle the CVI 8.5 RTE with the deployed system. This is true since the Build Installer captures the CVI Run-time from: C:\Program Files\National Instruments\Shared\ProductCache, which contains the latest CVI RTE.
Thanks for the info Joel.
Nestor

Release Management vNext deployment succeeds without deploying the DSC to the target.

All of a sudden, a couple of weeks ago, our vNext releases stopped working.
The log in the release management client says that the release has been deployed successfully, but nothing has actually happened on the target server. The log looks like this (which is bad)...
Copying recursively from \\xxxxx.co.nz\Public\Share\Development\Builds\DispatchService_MAIN\DispatchService_MAIN_1.1.7.0\DispatchService\_PublishedWebsites\DispatchService to C:\Windows\DtlDownloads\DispatchService Component succeeded.
That's all it says. No error, no nothing.
It used to look like this (which was good)...
Copying recursively from \\xxx.co.nz\Public\Share\Development\Builds\SosService_MAIN\SosService_MAIN_1.1.32.0\SOSWindowsService to C:\Windows\DtlDownloads\SosServices succeeded.
Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
An LCM method call arrived from computer BDWEB10 with user sid S-1-5-21-3667390900-813461161-666584507-16981.
[BDWEB10]: LCM: [ Start Set ]
[BDWEB10]: LCM: [ Start Resource ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ Start Test ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ End Test ] [[bStopService]StopTheService] in 0.0000 seconds.
[BDWEB10]: LCM: [ Start Set ] [[bStopService]StopTheService]
[BDWEB10]: [[bStopService]StopTheService] Stopping service SosServiceDevReviewPci
[BDWEB10]: LCM: [ End Set ] [[bStopService]StopTheService] in 0.1400 seconds.
[BDWEB10]: LCM: [ End Resource ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ Start Resource ] [[File]CopyDeploymentBits]
[BDWEB10]: LCM: [ Start Test ] [[File]CopyDeploymentBits]
etc etc
I have tried many things, and have discovered some clues, but have filed to find a solution.
It seems that it is successfully creating the .mof file on the "Deploy using PS/DSC Server" but then it deletes the .mof file and does not try to do a Start-DscConfiguration with the .mof file.
This is very frustrating, as we have sunk an awful lot of time and money into Microsoft Release Manager.
Does anyone have any ideas?

Hi Leighton,
Thanks for your post.
You’re using TFS 2013 Update 4 and Release Management 2013 Update 4?
Do you mean that the files be copied to C:\Windows\DtlDownloads\DispatchServices folder on target machine as expect, but no file be executed to perform the deploy?
You said the release template works fine a couple of weeks ago, do you know which changes happened on this release template after that week?
Only this current one release template cannot works? Or if you create a new release template to run DSC deploy, it will receive the same result too?
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Deployment configuration files

every now & then our system   Login-Users (users.ini) change also the station options change
can I simply copy the   Cfg files directly in my deployment system
or shld I be religiously making the whole deplyment(Image+ Insatller)   everytime

aparab,
If the only thing you want to restore is the Station Options, you can certainly just copy the users.ini and config files to the deployment machine. These files generally do not have extra dependencies, so it is not strictly necessary to use the Deployment Utility to transfer them. If you make larger changes, such as changing custom data type versions or changing test sequences, you would want to do a deployment to be sure all files are included and updated properly.
Daniel E.
TestStand Product Support Engineer
National Instruments

Configuration Utility - Is this supported on new Thinkpads

Can anyone confirm whether the Lenovo Configuration Utility is still supported on new Thinkpads. Looking at the Lenovo website it doesn't look as though anything has been updated since 2006 when the X60/T60 were current models.
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4ZFRG3
If this is no longer supported what has this been replaced by if anything?
Many thanks
Paul
Message Edited by paulw on 05-26-2009 04:53 PM
Solved!
Go to Solution.

Hi Paul:
Although I am no expert on this subject, I think that the "ThinkPad Configuration Utility" has been replaced by additional functionality that Microsoft built into the operating system of Windows Vista.
There is now a tool (program?) that comes with Windows Vista called "Mobility Center". This appears to include most of the functionality that Lenovo used to provide in the configuration utility. Lenovo has released a little add-on tweak that gives the Microsoft provided Mobility Center a bit of extra functionality to control features that are unique to the ThinkPad, such as the keyboard light. That Lenovo add-on is called "Mobility Center Customization", and it is available from the DDFM.
For folks who are still using earlier OS, such as XP, there has probably been no need to update the ThinkPad Configuration Utility since 2006. By this I mean that the XP operating system is fully mature, the ThinkPad Configuration Utility is fully mature, and it is unlikely that either will be updated again unless some problem is identified.
Michael
W520 (4270 CTO), which replaced a W500 (4062-27U), which replaced a T42P, which replaced an A21P...

Deploying Switch Executive configurations.

I read the "How Do I Deploy My Switch Executive Configuration to Target Systems?"
However, I can not find the following in the help file. Where am I going wrong?
Exporting IVI Configuration
The "Switch Executive Help >> System Deployment >> Preparing a Target Computer" chapter (see link below) says that to quickly export the IVI configuration, users can copy the IVI configuration file from your deployment computer to the target computer.
thanks
Scott Youngren
Northrop/Grumman Navigation Systems
[email protected]

The mentioned help states:
To export the IVI configuration to the target machine, copy the IVI configuration file from your deployment computer to the target computer. If you have IVI Engine 2.0 or higher, the IVI Configuration (including IVI Driver Sessions and IVI Logical Names) is saved in the IVIConfigurationStore.xml file usually located in the folder \Program Files\IVI\Data.
What you need to do to deploy the system is to make a copy of the IVI configuration file (IviConfigurationStore.xml) and put it in the IVI Data folder on the target machine AFTER you have installed switch executive there. If you are not changing any of the directories between the installations on the development and deployment machines, then this method should work just fine.
What specifically is not working for you, or what specifically would you want to have better explained?
Thank you for your feedback!
-Serge
Srdan Zirojevic

Problem with deploying FPGA host VIs using TestStand deployment utility

I am using a PCI-7831R FPGA to control an automated test fixture. I have several host VI's that I am calling from TestStand (4.2.1) in order to control the 7831R. The host VI's that TestStand calls are setup as sub-VI's and are used for various things such as opening an FPGA reference (which is bound to a strict type def), downloading and executing the files on the 7831R, reading writing to controls, and finally closing the reference. In the sequence file, I am passing the reference values as a file global so that the host sub-VI's can communicate correctly. I have all functionality working correctly in TestStand on my development PC. When I go to deploy this to a production PC, I get errors when the sequence file trys to load the first host VI. The error basically states that the VI is broken - try to open and run it (which I can't because I have no development license on the production PC). I am currently trying to deploy this to another development PC to see if I can track down where the VI might be breaking.
I have included the lvbitx and strict type def control that the host subVI's reference in my deployment files. I can't think of anything that I might be missing. Is there any good documentation on exactly which files I need to include in the deployment when using FPGA Host VIs (the TestStand reference manual is pretty vague at best)? It seems that any documentation that I read says the TestStand deployment utility will analyze all VI dependencies (other than shared variables). On a side question, is the strict type def considered a shared variable?
Has anyone successfully deployed a sequence that calls host VI's? Any help would be greatly appreciated. If any of the above needs further clarification please ask away and I will be happy to give more details.
Thanks,
Mike

Hi hawkstringer
Do you encounter this problem using a deployed version of your code? Note that the subject of this topic is about deploying an FPGA application.
I forgot I posted here, in the mean time I've managed to deploy my application. I think my problem was solved when I included all necessary drivers and components (but I'm not absolutely sure). I included the following:
NI IVI Compliance Package
NI FlexRIO
NI PXI Platform Services Configuration Support
NI R Series Multifunction RIO
NI DAQmx Core Runtime
NI DAQmx MAX Configuration Support
NI RIO
Good luck!

Error code 1127 when using teststand deployment utility

I'm have installed on my pc Teststand 3.0 and labview 7.0 -this error occurs during build
Error Code:1127
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Open VI Reference in TestStand - Dist Chg and Save VIs.vi->TestStand - Dist Build LLB Image.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller

>>>>>>>ok, I'm getting a different error code: error code 7 instead of a error code 1127 with the error:
Error Code:7 Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW
error: Invoke Node in TestStand - Dist Cmp Settings to Disk Hier.vi->TestStand - Build VI
Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI
Distribution AX Wrapper.vi.ProxyCaller
>>>>>>>>And I did a mass compile of the directory mentioned above and I got this error:
#### Starting Mass Compile: Thu, Jul 15, 2004 9:44:04 PM
Directory: "C:\Program Files\National Instruments\TestStand
3.0\Components\NI\Tools\Deployment Utility"
CompileFolder: error 13 at C:\Program Files\National Instruments\TestStand 3.0\Compon
ents\NI\Tools\Deployment Utility\DeploymentUtility.exe
#### Finished Mass Compile: Thu, Jul 15, 2004 9:44:17 PM

Is there a way to keep Deployment Utility from modifying sequence file paths?

While the Deployment Utility appears to be a great tool, it does some things that I'd rather it didn't. One is that it modifies all paths in sequence that it is including from Absolute to Relative. While this is a nice feature for many reasons, it is a show-stopper for our uses. This is because as part of our distribution process, we also use a checksum routine to verify that the sequence files being run by the operators on the Test Stations we deploy to are running the correct (unmodified) version of the test software. By using Absolute paths, we can detect and prevent accidental editing/changing of the sequences or paths that we have deployed, but if we have to use relative paths that is something that we could work with also.
So my questions are: 1. Can this path update 'feature' be disabled? and 2. If not, then will pre-setting all paths in a sequence cause the deployment utility to only copy the file and not update it (thus changing it's checksum)?
I'm going to test the latter when I have time, and if there are any other suggestions that might be useful, I'm love to hear them.
Thanks,
-Jack

Rick,
In my experimentation to see if using relative paths, I was able to prove that a sequence that uses them will not be updated - with one caveat; if the path that is referenced by the sequence is not itself in a sub-directory, i.e.; it's in a different branch of the relative directory structure with respect to the Target (such as the TestStand directory), then the sequence file is always updated and re-saved. An example is that we have a sequence in the Tools directory that calls a DLL in the FrontEnd directory of the Components\User path. This re-saving causes a checksum change and screws up our verification mechanism.
It is unfortunate that I cannot prevent the deployment utility from modifying sequence files - Since we control the entire Test environment, including the location that software gets installed to - Test Station custodians can't go installing the software in a different location, or worse, multiple locations, so we don't have the issue to worry about.
Because of this 'better' method, we now have to re-evaluate how to control the installed version of the software, or use a different installer, such as CVI, which while it has been working for us, has it 's own issues that we're trying to get away from. I'm glad that I am finding out about this now before I've locked down the sequences so that I can probably move the features in the Tools to the Frontend Callback sequence.
It's almost always the case thought that one persons forced enhancement is another's 'feature' or worse 'bug'.
Thanks for confirming the behavior on the Deployment utility for me.
-Jack

Deployment Utility copies my MAX configurat​ion to the target system

Similar Messages

Maybe you are looking for

Deployment Utility copies my MAX configuration to the target system