Keeping Lookout from polling data from a COM port at start up.

[MEWART]

I need to keep Lookout from polling the COM port at start up. I currently have a delay on timer set to 30 Sec connected to a pulse that triggeres the poll. At start up, the delay is running, and the pulse is not (as expected), but Lookout does one initial poll at the beginning. I need this delay because I have other delay off timers and one shot timers that have to "stabilize" before I talk to the Fieldpoint modules, else things switch that shouldn't. This worked with 4.01 and 4.5(9) but doesn't in 4.5(12).

Thanks for the help, Mark

[Zork]

This sounds like an issue you will need to work with tech support. Send a question into www.ni.com/ask

Include a small example that show this or which objects you use to re-create the poll.

[GK_Associates]

Mark

What signal do you use to initialize the timers at startup? I have been
trying to find a way to set a flag when Lookout starts so that I can
initialize some signals, totalizers, etc.

Regarding your problem with the poll at startup; what type of I/O are you
using? I use Field Point I/O modules and they have built-in startup flags
to set the state of each signal.

Geoff


"Mark E." wrote in message
news:5065000000080000006B170000-984280909000@quiq.com...
> I need to keep Lookout from polling the COM port at start up. I
> currently have a delay on timer set to 30 Sec connected to a pulse
> that triggeres the poll. At start up, the delay is running, and the
> pulse is not (as expected), but Lookout does one initial poll at the
> beginning. I need t
his delay because I have other delay off timers and
> one shot timers that have to "stabilize" before I talk to the
> Fieldpoint modules, else things switch that shouldn't. This worked
> with 4.01 and 4.5(9) but doesn't in 4.5(12).
>
> Thanks for the help, Mark

[MEWART]

Geoff, I use a pushbutton as my start object. If the button is false (as it is when Lookout starts) then run the delay_on timer. I too use th Fieldpoint mods and have flags set for startup, but we communicate to a remote site, 50 miles away, over a telco DDS line. If we loose communications, or we have to work on the server, thing that need to go into auto do via the watchdog. The problem is that we have many one_shot timers in the server prosess and they need to "stabilize" before they talk to the remote site. If not, these timers will switch things that (at that moment) shouldn't switch. This caused us some problems recently, (and signifigant down time), so we are VERY aware of the problem. At startup, Lookout 4.5 b13 polles the mods 1 time. This is enough to cause
our problem. Earlier versions did not do this.

Thanks for your reply, Mark