Running Stimulus Profile from not the gateway/host

[h_yong]

I'd like to know if this is possible:

Run a VeriStand project on one computer (the "gateway") and run stimulus profiles from another computer on the same network subnet. I try to do this and specify the gateway IP address from the stimulus profile editor but get the error -307998:

Error compiling....

TopLevelSequenceFileDoesnotExist....

But the sequence files are definitely there. And I know it's communicating somewhat with the gateway, because if I gave a bogus gateway address, I'd get different errors. Are there other configurations details that I need to know to run stmulus profiles from a different computer?

Thanks.

[Alisha_P]

Hi Harris,

I just tested it to make sure sure, but this should be completely doable. My stimulus profile ran without any error. You should just have to change the Gateway IP address and the file path to the project.

Can you run this particular stimulus profile on the gateway computer successfully?

[h_yong]

Hi Alisha,

Yes, these profiles work fine on the gateway computer. In fact, even simple profiles that essentially don't do anything also give me the error that the sequence cannot be found. I did point the stimulus profile editor to the gateway IP address. What do you mean by changing the file path to the project? Do you mean I need to point the project to the gateway? How do I point to a folder on a different computer? Thanks.

[Alisha_P]

Harris,

No. Sorry I wasn't clear. You should have the project on both computers and point to it in the local directory on the computer where you're running the stimulus profile.

When you try the simple profiles, I'm assuming they don't use a real-time sequence. Is that accurate?

Have you tried it with a sample project and a sample stimulus profile. What if you try the test I did so we can know for sure it's something specific to your system.

1) I opened up the Engine Demo that comes with VeriStand and resides at    C:\Users\Public\Documents\National Instruments\NI VeriStand 2012\Examples\Stimulus Profile\Engine Demo .

2) I ran it on the gateway computer (with the gateway computer as the target)

3) I opened up the stimulus profile editor on another computer in the same subnet and opened the Basic Engine Demo example.

4) I changed the gateway IP and the file path to the project.

5) I pressed the run button and it ran successfully, no errors.

(I also opened VeriStand on the second computer, but I don't think that matters)

[h_yong]

Hi Alisha,

My simple profiles that I use for testing this call a very simple sequence. I did the same steps as you did, and so did my colleague on his computer, and we always get the error that the sequence cannot be found. Both our computers and the one running the gateway do have the same project and definition, etc.

[Alisha_P]

And is the real-time sequence present on both computers?

Can you try the test I suggested?

[Alisha_P]

Does a stimulus profile that doesn't call a real-time sequence work?

[h_yong]

Hi, I can try the test you mentioned a bit later. I haven't tried a profile that doens't call a sequence but will also try that. Thanks.

[h_yong]

Hi Alisha,

Running a blank profile without a sequence call does nothing as there's nothing to run and no execution result. If I put in a prompt message box, then it passes. The engine demo fails in the same way unfortunately!

[Jarrod_S. · Accepted solution]

You can run stimulus profiles remotely on a different machine than the Gateway host, but it requires some work to set it up correctly. The problem is that when the stimulus profile specifies to run a particular real-time sequence, the file path it specifies is the file path on the Gateway machine, not on the local machine. So the problem you are probably seeing is that the sequence exists on your local machine at the specified path, but not on the Gateway machine.

For example, if your stimulus profile runs a real-time sequence at "c:\temp\mySequence.nivsseq", then that sequence has to be in c:\temp on the Gateway machine.

You can make by storing the sequences on some shared network location that is the same for both the Gateway machine and the local machine. For instance, if you have some file server called myFiles, then you can copy the sequences there and specify the path "\\allFiles\mySequences\mySequence.nivsseq". This should work, because the path is the same from both the local machine and the Gateway.

Alternatively, you can map drive paths in Windows from both side to create the same virtual drive letter on both the local machine and the Gateway host.