Applies To: |
|
Summary: |
When I startup Citect, my PLC's take a long
time to come online. However after 30 seconds Citect seems to start
processing alarms, and displays data on the pages before the PLC's
are online. This causes problems as the data displayed is zero, and
any alarms that are configured to alarm in 0 state, are tripped. I
also see the following message in the kernel:
Communication system timeout How can we delay this timeout until after the units have come online? Is there a CITECT.INI variable? |
Solution: |
On startup Citect waits for all PLC's to
come online before processing alarms, trends, reports and
displaying data on any page. However, if the PLC's don't come
online after a timeout period, Citect will start processing. This
allows Citect to startup even when a PLC will never come online.
This timeout is set to 30 seconds and you can modify it by an
CITECT.INI option.
Section : [COM] Example : If units come online in 60 seconds then you may set the startup timeout to a value greater than 60, i.e 90 seconds. [COM] |
Keywords: |
Related Links
Attachments