HEIDENHAIN TNC 426 CB, Technical Manual

Page: 1014 / 1135

December 2001 Cooperative Multitasking 7 – 165
Example Entry in the OEM.SYS file:
PLCEVENTS=PLC:\EXAMPLE.PEV
Content of the file PLC:\EXAMPLE.PEV:
JOB_1;I5==1;$0010; Event $0010 to process JOB_1, if I5==1
JOB_1;B20==5;$0004; Event $0004 to process JOB_1, if B20==5
AUXJOB;W6 <10;$0100; Event $0100 to process AUXJOB, if W6 <10
The TNC triggers an event if a particular condition is met after one run of the
cyclic PLC program and if this condition was not met after the previous run of
the cyclic PLC program (edge formation). The number of events of this type
that can be activated simultaneously is limited to 15.
If you produce a PLC process with the spawn command, the TNC searches
the event file for entries for this process. It places all relevant entries in a list
that is run after every cycle of the cyclic PLC program. If a PLC process
terminates itself, or if you terminate the process by recompiling the PLC
program, the TNC then deletes all entries in the list.
The TNC does not monitor the entries in the event file. This means that
syntactically incorrect entries of incorrect job names do not result in an error
message.
The TNC issues a blinking error message if:
n
A non-existing event file is listed in the OEM.SYS file (when the first spawn
command is executed).
n
Due to the number of entries in the event file, more events need to be
monitored than the run-time list permits. Maximum number of entries in the
run-time list: 15
Process monitor In the PLC programming mode you can use the PROCESS MONITOR soft key
to open a status screen in which the TNC displays all parallel processes,
including the process for the submit queue. In a time interval of 1 second, the
TNC shows:
n
The current process status (runable, running, waiting for event, waiting for
a time period).
n
How often the process changed contexts during the last time interval.
n
The CPU time consumed by the process. The TNC also shows the
distribution of CPU time in a bar chart.