Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Delay On Timer trigger Inconsistent - Lookout 6.1

Having problems with some DelayOn timers.....
 
When DelayOn Timer uses pushbutton(implicit) for "On/off signal =" properties field, timer cycles fine each time pushbutton is cycled (pushed) until process is saved and restarted.
 
DelayOn Timer no longer works after restart of process.  It will start working again if "On/off signal =" value is changed or if "Timer delay" value is changed.
 
Again, timer works correctly after creation or adjustment of it's properties, but then fails to properly cycle after process is re-opened.
 
Ed
 
Update:  Just touching the properties of the DelayOn timer in any way (right-click, properties in object explorer, then click OK in properties dialog box) fixes the issue after each process restart....weird!!!


Message Edited by erblock on 06-19-2008 01:59 AM
0 Kudos
Message 1 of 3
(6,192 Views)
Ed,
I cannot reproduce the problem. This is what I saw on my computer.
 
A switch connected to DelayOn On/Off.  With Switch ON, save and reopen, DelayOn will count down automatically, and turn on after delay. With Switch OFF, save and reopen, DelayOn will keep OFF.
 
If I connect pushbutton to DelayOn, it behaves similar. But pushbutton cannot keep ON, so if I save and reopen with pb OFF, DelayOn will be OFF. Then, I press pb, DelayOn will work.
 
Do you connect it in a different way? An example may be helpful.
Ryan Shi
National Instruments
0 Kudos
Message 2 of 3
(6,173 Views)
Found the problem...My error.

I had connected  "now(pb1)" to the same (pb1) push-button's value member resulting in a circular reference of sorts....

The intention was to use the "now(pb1)" as a reset value connection on a separate pot.  The pot and pb names were similar and I had connected the "now(pb1)" to both the pot and push button in error.

I fixed the intended logic using a latch gate between the pushbutton and the timer.  This was being used to facilitate resetting many hypertrend start times and their subsequent go-live behavior.

Not sure why I had the behavior above in my first post....However, issue is SOLVED.

Thanks Ryan...
Ed

0 Kudos
Message 3 of 3
(6,168 Views)