teststand shortcut command line

[LuigiM]

Hi All,

I'm experiencing the new features of deployment utility...

Regarding the Shortcuts, it is possible to set as 'Shortcut command line arguments' a string with a PATH macro?

As to explain better can I write inside "<INSTALLATIONDIR>\SeqPath\MySeq.seq"

My attempts fail.

In any case there is a workaround?

Sincerely

[AndreaN]

Hello Luigi,

have you taken a look at this KnowledgeBase?

How to Run a Sequence File When Opened from Windows Explorer or the Command Line

http://digital.ni.com/public.nsf/allkb/146D372C1F807E6D862567E7004881AB?OpenDocument

 Also you could look at TestStand Reference Manual at page 8-9 and  8-10

I hope this can help.

Regards, 

[LuigiM]

Dear Andrea,

I know quite well at what you are referencing.

My question is related how to properly define the shortcut with the TS deployment tool in order to reference, after the installation, the proper target directory.

Sincerely

[AndreaN]

Hello Luigi,

I bet you know quite well TestStand...

I've actually tried to insert a shortcut command line but I couldn't succeed. I forwared your question also to my colleagues at NIC, as soon as they tell me something I'll let you know.

Ciao, 

[LuigiM]

Many thanks Andrea.

I have another request that probably could you submit to your colleagues at NIC.

In the deploy tools I added some Custom commands in order to perform installation of IVI drivers and other supporting apps. But these commands are executed immediately after the end of the main TS installation so the system configuration isn't updated so the driver installation fail. (I'm speaking about the installation on a clean PC without NI SW installed)

If I run manually the driver installation after the reboot all the things are ok.

So my question is: it is possible to execute some commands after the reboot? As happens when you define (into deploy tools) a MAX configuration to import that is executed after the reboot.

Let me (us) know.

Ciao e grazie.

[AndreaN]

Ciao Luigi,

we made it...;)

Let's say I want to create a shortcut for my operator interface TestExec.exe and being able to run the sequence from the command line.

Here's the correct procedure:

What you have to do is create a shortcut to the TestExec.exe file (select TestExec.exe in the Distributed Files window, then click Shorcut).  Then, in the configuration of the shortcut, insert the following (customize it for your application):

When doing this, I wind up with a shortcut to TestExec.exe that uses the appropriate command line arguments.  The "Target" field of the shortcut winds up looking like this:

"C:\Program Files\National Instruments\TestStand 4.1.1\UserInterfaces\Full-Featured\LabVIEW\TestExec.exe" /run MainSequence "C:\MessagePopup.seq"

In order to launch it from the command line you need to set the prompt to the desktop directory path and then  insert just the name of the shortcut with the extension .lnk and your sequence will run!

In my example I've put in the "Shortcut relative path" the name "test" and I've pointed it in the program files directory. Once installed the distribution I went to the command line at C:\Program files> prompt and by inserting the command "test.lnk" Windows opened the operator interface TestExec.com and rum my sequence.

I think this is what you were looking for!!! 🙂

Ciao, 

[LuigiM]

Ciao Andrea,

probably my English isn't so clear to understand... It's my fault

I want to specify this:

in this way whatever the target installation will be my shortcut argument will point correctly to my testing sequence to execute.

In your example you are sure (?) that the sequence is on C:\, but is not my (and in general) case.

I hope to have been more clear at this time.

Saluti