Run and Terminate the sequence file

[Sailfish]

User want to use two buttons on the test fixture to replace the mouse touching on the relevant toolbar ico to run and terminate the selected sequence file. 

So it has two problem:

1)  where do the two buttons  link to in the PC?   Printer_Port?

2)  Are there some API s or  Call back sequence to run and terminate the sequence file?

[PalanivelThiruvenkadam]

Use API to Run and terminate.

For better undestanding check LabVIEW UserInterface

[CharlieRodway]

Hi Sailfish,

It depends on your level of proficiency with LabVIEW and TestStand.

If you are quite confident with LabVIEW, you could produce a TestStand Operator Interface like IanS's example of a Really Simple TestStand User Interface (Run a Test With a Single Button Press), but uses a simple DAQ device (like a 6008) to detect the two buttons on the test fixture.

Otherwise, you could call the sequences using the command line parameters Configuring Sequence Editor and User Interface Startup Options from a shortcut, eg.

testexec.exe /operatorInterface /runEntryPoint "Single Pass" "c:\My Seqs\test1.seq" /quit

But you'd have to work out a way of executing the shortcut from the test fixture button press.

I hope this helps,

[buton]

---

@CharlieRodway wrote:

Hi Sailfish,

It depends on your level of proficiency with LabVIEW and TestStand.

If you are quite confident with LabVIEW, you could produce a TestStand Operator Interface like IanS's example of a Really Simple TestStand User Interface (Run a Test With a Single Button Press), but uses a simple DAQ device (like a 6008) to detect the two buttons on the test fixture.

Otherwise, you could call the sequences using the command line parameters Configuring Sequence Editor and User Interface Startup Options from a shortcut, eg.

testexec.exe /operatorInterface /runEntryPoint "Single Pass" "c:\My Seqs\test1.seq" /quit

But you'd have to work out a way of executing the shortcut from the test fixture button press.

I hope this helps,

---

I will agree on this and recomend the interface. With a cheap daq.

On the other hand a simple solution just to terminate is to run a thread on the background always checking the button states on the daq. and terminate the sequences from there.

[WireWeaver]

I'd recommend considering an option that doesn't involve continuously polling a DAQ channel.

There are 3rd party USB Buttons that you can configure Windows to recognize as a keystroke (or combination of keystrokes). At that point, the button is no different than pressing some combination of keys, like Shortcut Keys for example.

With a little reading on Commands and some modifications to your user interface, you could also have your button correspond to a custom user defined ShortcutKey.

Hope this helps,

Trent