General time-division performance characteristics
(Original Document)
Calling an event task
Diagram of an event task call
The module includes 7 event sources (capture, cycle switching, cam ....).
The calling of event tasks is limited to a maximum of 1 event per ms.
Only one type of event is sent at a time to the system.
In the case of one event
The start of the event task is executed no more than 3 ms after the real event (e.g.: switch to cycle modulo).
In the case of several simultaneous events
The module integrates a buffer that allows the storing up to 7 events awaiting transmission to the system. The events will be sent in their order of arrival (1 per ms). This, therefore, increases the reaction time.
Table
Description of the functions
Function
Comments
Value
Counter
Permitted frequency
500Khz in x1
250Khz in x4
Activation of the event task on switching of cycle
< 3 ms
Recalibration of counter on Z marker pulse
< 1 micro second
Recalibration of counter on Irec
< 50 micro seconds
Event task activation
< 3 ms
Cam function
Refreshing output
50 micro seconds up to 16  cams
100 micro seconds up to 32 cams
200 micro seconds up to 128 cams
Updating the correction values (anticipation)
< 4ms
Activating the event task (cam, parts counter)
< 3 ms
Implicit interface
Influence of the module on the processor cycle time
Refreshing %I and %IW
< 1 ms
Recognizing %Q and %QW
< 1 ms
Explicit interface
WRITE_PARAM
300 ms
SAVE_PARAM
300 ms
RESTORE
300 ms
READ_STS
immediate (1)
MOD_PARAM
send: 20 ms (2)
MOD_CAM
send: 20 ms (2)
MOD_TRACK
send: 20 ms (2)
TRF_RECIPE
300 ms
DETAIL_OBJECT
immediate (1)
Additional cycle time
The cycle time has no effect on the output reaction time
1 ms
(1) There is no access to the module / Execution time is included in the task execution.
(2) For GET and READ it is immediate as in (1).