post stop condition duration

[Marky]

Hi

I one to collect 5 seconds of data prior to the start of a test, and then 30 seconds after the end.  So I have been using start and stop condition with pre and post logging options.  For the start condition, with 5 seconds pre condition every thing is fine, however the post stop condition of 30 sec does not occur and logging stops as soon as the stop condition occurs.  Screenshot of the start/stop condition page are attached with a copy of the project.

Has any one any experience of this, what am I doing wrong?  Have I misunderstood the way this should work?

thanks

Mark

[JTG_Wilson]

Hello Mark,

I've been looking at your issue and I've not been able to replicate your problem.

You may find that if you look at  P Red in your log file in Data View it will show that the Stop Condition is not happening quite where you are expecting it to and thus is making it appear that the Post-stop logging is not working correctly.

If this is not the solution then I can look into it further for you if you could you tell me what version of signal express you're using please?

Also it would be helpful if you could attach one of your log files to your reply for me to have a look at please as they are saved in a separate place to your project and thus have not been posted with it.

Kind regards,

[Marky]

Hi James

Thanks for looking at this, sorry for the delay in replying.  

I have reattached the project file and a data set.  I've been messing around with the settings, but still no joy.  In the current project I am asking for 30s of data after the stop condition occurs but it still is not happening.  In Data View for 'P Red' the stop condiditon occurs as specified when the pressure goes below 1 bar, and then logging ceases a couple of seconds after that.  In the meta data for the logs it specifies the start and stop conditions, and it also specifies that I want 5 s pre start, however there is no mention of my post stop requirements 

Does the 30s I specified really mean 30 seconds after the stop event, it wouldn't be something like stop after 30s or at the stop condition, which ever is longer?  Is it possible for you to look at the code or the logic in the programming of this feature?

thanks

Mark

[JTG_Wilson]

Hi Mark,

I'm sorry about the delay in responding.

I've been looking at your issue further and I've still not been able to find a solution.

The way you have setup the project means that is should indeed record 30 seconds of data after the stop condition and add it to the log. As to why it doesn't do this, I'm still at a loss.

What I suggest as the next step is that you try doubling the Post-Stop Condition Duration to 60 seconds and see if the actual delay that results is twice what it was when the duration was set to 30.  If the delay does double then we can at least work around the problem by putting a very high value in as the duration so that the program actually records 30 seconds as it should.

If this works then I will submit a corrective action request and get the R&D team to look into the cause of the problem properly.

What I'm most concerned about at the moment is making the code work in the way that you want by whatever means we can and figuring out exactly what has caused the problem once we have a work around in place.

Kind regards

James

[Marky]

James

Thanks for your suggestion.  I'm going to be side tracked for a week or so but will give it a go shortly and let you know

regards

Mark

[JTG_Wilson]

Hi Mark,

Sorry to bother you but I was just wondering if you have had chance to try the workaround for your issue.

If not don't worry, I was just wanting you to know that I've not forgotten about you.

Kind regards,

[Marky]

Hi James

Sorry for the long lapse in time!  I had a look at your suggesttion of varing the stop condition duration and this had no effect.  I have also had my SE version upgraded to the latest release (2011), and also had the drivers updated.  Still no joy.  n.b. the stop condition details still fails to be registered in the meta data so I feel there is a fundamental problem in the connection between the gui and the logic

As a work around I will use some other signal, or just do it manually.  

Thanks for your help.  Please can you put the issue in the developers bug list

many thanks

Mark(y)