Defining Nck Hardware Interrupt Event - Siemens SINUMERIK MC Commissioning Manual

Whether or not an event was triggered by the NCK can be queried as follows:
● LADDR in the start information of the hardware interrupt OB
LADDR contains the hardware identifier of the module that has triggered the hardware
interrupt. The HW identifiers that occur in your project can be viewed in the system
constants.
● PointAddr in the start information of the hardware interrupt OB
LBP_NCKProcessIRT [FC3] should only be called after such a successful query to avoid
unnecessary calling.
Alternatively, you can call the LBP_NCKProcessIRT [FC3] without any distinction at the start of
the hardware interrupt OB and then specifically query the pending individual NCK signals in the
output parameters of LBP_NCKProcessIRT [FC3].
5.4.7.4

Defining NCK hardware interrupt event

Requirement
● A SINUMERIK MCU has been created.
MCU commissioning: NC, PLC, Drive
Commissioning Manual, 02/2020, A5E47437618B AB
Slice #PointAddr.B3
ac‐
cess
Bit 31 ... 24
num‐
ber
Mean‐ currently not used
ing (set to 0)
#PointAddr.B2 #PointAddr.B1
23 ... 16 15
currently not used Channel
(set to 1)
currently not used
(set to 0)
PLC commissioning
5.4 Creating a PLC program
#PointAddr.B0
... 8 7 ...
Event that triggered
the hardware inter‐
rupt.
10 or B#16#0A:
Event-driven signal
exchange NCK to
PLC
0
91