TAMAGAWA TS5016N60 TS5016N60 TS5016N60 TS5016N60 TS5016N60 TS5016N60 TS5016N60

TS5016N60

Guang Zhou Lai Jie Electric Co.,LTD

Please contact with “Tommy” for the price

TS20N2E11

TS2142N1E63

TS2151N1E26

TS2151N1E45

TS2151N11E45

TS2640N321E64

TS2641N31E64

TS2650N1E78

TS2650N11E78

TS2650N101E78

TS2651N111E78

TS2651N181E78

TS5000N532

TS5000N632

TS5003N632

TS5005N122

TS5007N122

TS5007N635

TS5208N500

TS5208N510

TS5208N530

TS5208N569

TS5208N576

TS5210N450

TS5210N453

TS5210N458  

TS5210N530

TS5210N54

TS5210N553

TS3684N1E3

TS3684N2E6

TS3684N3E8

TS3684N11E3

TS3684N12E6

TS3684N13E8

TS3617N1E3

TS3617N1E1

event
triggers the execution of the assigned OB. The event enters the queue according to its
priority.
● If the event comes from an event source to which you have not assigned an OB, the
default system reaction is executed.
Note
Some event sources, such as startup, pull/plug, exist even if you do not configure them.The table below provides an overview of:
● possible event sources
● possible values for the OB priority
● possible OB numbers
● default system reaction
● Number of OBsThe type of OB determines where you make the assignment between OB and event source:
● With hardware interrupts and isochronous mode interrupts, the assignment is made
during the configuration of the hardware or when the OB is created.
● For MC servo, MC pre-servo, MC post-servo and MC interpolator, STEP 7 automatically
assigns OBs 91/92 as soon as you add a technology object.
● For all other types of OB, the assignment is made when the OB is created, where

For hardware interrupts, you can change an assignment which has already been made
during runtime with the instructions ATTACH and DETACH. In this case, only the actually
effective assignment changes, and not the configured assignment. The configured
assignment takes effect after loading, and upon each startup.
The CPU ignores hardware interrupts to which you did not assign an OB in your
configuration or which occur after the DETACH instruction. The CPU does not check
whether an OB is assigned to this event when an event arrives, but only prior to the actual
processing of the hardware interrupIf you have assigned an OB to the event, the OB has the priority of the event. CPUs
support the priority classes 1 (lowest) to 26 (highest). The following items are essential to the
execution of an event:
● Call and execution of the assigned OB
● The update of the process image partition of the assigned OB
The user program processes the OBs exclusively on a priority basis. This means the
program processes the OB with the highest priority first when multiple OB requests occur at
the same time. If an event occurs that has a higher priority than the currently active OB, this
OB is interrupted. The user program processes events of the same priority in order of
occurrence.
Note
CommunicationThe communication (e.g. test functions with the PG) always works with priority 15. To
prevent extending the program runtime unnecessarily in time-critical applications, these OBs
should not be interrupted by communication. Assign a priority > 15 for these OBs.For the event scenarios considered in the following section, it is assumed that you have
assigned an OB to each event source and that these OBs have the same priority. The
second condition, in particular, is only for the sake of a simplified representation.An occurring event triggers the execution of the associated OB. Depending on the OB
priority and the current processor load, a time delay may occur before the OB is executed
when there is an overload. The same event can therefore occur once or several times before
the user program processes the OB belonging to the preceding event. The CPU treats such
a situation as follows: The operating system queues the events in the queue associated with
their priority in the order of their occurrence.
To control temporary overload situations, you can limit the number of queued events that
originate from the same source. The next event is discarded as soon as the maximum
number of pending triggers of a specific cyclic interrupt OB, for example, is reached.
An overload occurs when events which originate from the same source occur faster than
they can be processed by the CPU.
More detailed information is provided in the following sectionsBelow, the term "similar events" refers to events from a single source, such as triggers for a
specific cyclic interrupt OB.
The OB parameter "Events to be queued" is used to specify how many similar events the
operating system places in the associated queue and therefore post-processes. If this
parameter has the value 1, for example, exactly one event is stored temporarily.
Note
Post-processing of cyclic events is often not desirable, as this can lead to an overload with
OBs of the same or lower priority. Therefore, it is generally advantageous to discard similar
events and to react to the overload situation during the next scheduled OB processing. If the