TYCO V23401-U2020-B201 V23401-U2020-B201 V23401-U2020-B201 V23401-U2020-B201

 We can sell the products of TYCO at a advantage price

Guang Zhou Lai Jie Electric Co.,LTD

Please contact with “Tommy” for the price

V23401-U2020-B201

V23401-T1009-B122

V23401-H1009-B122

V23401-T1009-B101

V23401-H1009-B101

V23401-T1009-B102

V23401-H1009-B102

V23401-T2001-B214

V23401-H2001-B214

V23401-T2001-B222

V23401-H2001-B222

V23401-T2001-B201

V23401-H2001-B201

V23401-T2001-B202

V23401-H2001-B202

V23401-T2009-B214

V23401-H2009-B214

V23401-T2009-B222

V23401-H2009-B222

V23401-T2009-B201

V23401-H2009-B201

V23401-T2009-B202

V23401-H2009-B202

V23401-T2010-B214

V23401-H2010-B214

V23401-T2010-B222

V23401-H2010-B222

V23401-T2010-B201

V23401-H2010-B201

Process value archiving is controlled by cycles and events. The acquisition and archiving cycles enable continuous acquisition and archiving of process values. Furthermore, process value archiving can also be triggered or ended by events and actions. Cycles and events may be combined: A process value is for example acquired regularly; archiving is however only triggered by a binary event. Acquisition cycle The acquisition cycle determines the interval at which the process value of a process tag is read. The shortest possible value is 500 ms. All other values are integer multiples of this value. The starting point of an acquisition cycle is determined by the run-up time of the WinCC Runtime. Note A short acquisition cycle may lead to a high system load. Use process-controlled tags where there are frequent or fast process value changes

The archiving cycle determines when a process value is saved in the archive data bank. The archiving cycle is always an integer multiple of the acquisition cycle. For standard timers, the starting point of the archiving cycle depends on either the startup time of WinCC Runtime or the starting point of the timer used. The starting point for calendar-based timers is set in the time series configuration. Specifying the start point means that the values are logged with a delay and that the logging load is distributed. Here are two examples: ● Process values are archived in three cycles: every minute, every two minutes, and every three minutes. This causes a high archiving load every six minutes. Assign a different starting point to each of the three cycles. For example, archive every minute at the 15th second, every two minutes at the 30th second, and every three minutes at the 45th second. The archiving load is thus distributed. ● Many process values must be archived every ten seconds. In order to distribute the archiving load you can, for example, configure two "10 second" cycles with different starting points. Archiving takes place at second 0 or at second 5. All process values read from the process tags during the time period between acquisition and archiving will be processed by the archiving function. In the process value archive, you can use only one of the following archiving functions: ● Actual value: Saves the last acquired process value. ● Total: Saves the sum of all acquired process values. ● Maximum value: Saves the highest of all acquired process values. ● Minimum value: Saves the lowest of all acquired process values

Average value: Saves the mean of all acquired process values. ● Difference: Saves the difference between the process values of two archiving cycles ● Action: The most recently acquired process value is calculated, using a function created in Global Script. Note If the same cycle is used for acquisition and archiving, it does not necessarily mean that acquisition and archiving are started simultaneously. There might be a system delay of up to the length of an acquisition cycle between acquisition and archiving.

Events start and stop process value archiving. Conditions which trigger an event can be linked to a tag or to scripts (C, VBS). In WinCC, events / actions are differentiated as follows: ● Binary action: Response to changes in a Boolean process tag. Example: turning on a motor might start the archiving of a process value. ● Limit value event: Triggered by a limit value being exceeded or reached. Limit value events might be in absolute or scaled numbers. Example: temperature fluctuations of more than 2% might trigger archiving. ● Time-controlled event: Triggered when a fixed point in time is reached, or a defined period of time from the start time of the process value archiving has elapsed. Example: a report is generated after each shift change.

Each process tag in WinCC (B) corresponds to a certain process value in the memory of one of the connected automation systems (A). The acquisition cycle (1) controls when the process value is read from the memory of the connected automation system. The Runtime component of the archive system (C) processes the process value: ● Whether the process value is archived at all depends on the way you have configured the system. The process value must change by a certain amount or percentage (2). ● The archiving function (3) determines how the acquired process values are processed, for example, by averaging. The archiving cycle (4) determines when the processed process value is written to the archive database (D)