software trigger

[ben64]

I created a project with Signal Express v3.0 where I use software trigger to start and stop acquisition. When I close signal express and then reopen the project the software triggers do not show up in the bar below the menus.

Is there a way to keep the software triggers in the bar when we close the project and signal express?

Thanks,

Ben

[John_P1]

Hi Ben,

I tried configuring a software trigger over here and it seems to be working OK on my end. Which bar are you referring to, could you provide a screenshot? If I look in the Triggering Tab of my DAQmx Read configuration, the Software trigger remains configured as I left it:

Again, a screenshot or perhaps the SignalExpress project itself could be helpful, since I am not entirely sure of what the problem is you are experiencing.

-John

[ben64]

Hi John, if you look at the attached screenshots view1 shows the top part of the project when I open it. In view3 the software triggers are present. In view2 I display the start condition settings of the project. When I open the project I have to remove software trigger A and then add it back to have both trigger A and trigger B buttons appears at the top as in view3.

Ben

[John_P1]

Hi Ben,

Thanks for the images, now I know exactly what you are talking about. 

The behavior you are experiencing sounds like it could be a possible bug, but I am still unable to reproduce over here.  Are there any specific steps that you have noticed that cause this behavior?  Is there a series of steps that you can take to reproduce the problem?  Also, if you could post your SignalExpress project file I could take a look at it to see if I experience the same problem over here.

-John 

[ben64]

Hi John,

I attached the project.

Thanks

Ben

[John_P1]

Hi Ben,

I opened the project you attached and there was no trigger configured.  I configured a software trigger, saved the program, then re-opened.  The trigger remained configured as I specified and the button was still present.  This was with SignalExpress 3.0.

Are there any other specific steps we can try to reproduce the problem you are seeing?  The first step to finding the cause of the apparent bug would be to reproduce the issue on one of our test systems, so any other information you can provide us should help a great deal.  Thanks and have a good weekend!

-John