Solution
A workaround is to modify the Real-Time Sequence Command channel definition in the SDF file and update the Value Table entries.
Original Value Table:
<Channel Name="Real-Time Sequence Command">
<Description>Internally commands the active real-time sequences with the following numeric values:
0: None
1: Stop All
2: Abort All</Description>
<Property Name="Value Table">
<Dictionary>
<Elem Key="None">
<Double>0</Double>
</Elem>
<Elem Key="Stop All">
<Double>1</Double>
</Elem>
<Elem Key="Abort All">
<Double>2</Double>
</Elem>
</Dictionary>
</Property>
Updated Value Table:
<Channel Name="Real-Time Sequence Command">
<Description>Internally commands the active real-time sequences with the following numeric values:
0: None
1: Stop All
2: Abort All</Description>
<Property Name="Value Table">
<Dictionary>
<Elem Key="None">
<Double>0</Double>
</Elem>
<Elem Key="Stop All">
<Double>268435456</Double>
</Elem>
<Elem Key="Abort All">
<Double>536870912</Double>
</Elem>
</Dictionary>
</Property>
After updating the SDF file:
- Save the modified System Definition File.
- Redeploy the VeriStand system.
- Execute the Stop All or Abort All command again.
The Real-Time Sequence Command channel should now successfully stop or abort the active real-time sequences as expected.