YASKAWA iC9200 Series, Operating Manual, Page: 162 / 220

162 HB700 | CPU | PMC921xEx | en | 24-04
Deployment CPU iC921xM-FSoE
iC9200 Series
System variables and status information > System variables
SliceBus system variables
System variable Type - description
NAME
1
STRING - name of the task.
EXCEPTION_COUNT USINT - number of exceptions.
EXCEPTION_INFOS ESM_EXCEPTION_INFO_ARRAY
[1] ... [2] ESM_EXCEPTION_INFO - Information on the exceptions [1 ... 2]
2
.
TYPE_ID UDINT - ID of the exception.
SUB_TYPE STRING512 - exception type.
SUB_TYPE_ID UDINT - ID of the task in which the exception occurred.
TASK_NAME STRING - name of the task in which the exception occurred.
PROGRAM_NAME STRING512 - name of the program instance in which the exception
occurred.
INFORMATION STRING512 - information about the exception that occurred.
1) You can set the system variable in the Tasks and events editor of the software iCube Engineer.
2) Please note that some CPUs only support ESM1.
⮫
‘Technical data’...page 69
−
Please consider the System SLIO power and clamp modules do not
have any module ID. These cannot be recognized and are therefore
not taken into account when listing or assigning the slots.
−
The counting of the slots starts at 1, i.e. the 1st slot corresponds to bit
0 in the corresponding diagnostic register.
−
A diagnostic interrupt is not automatically acknowledged. The
acknowledgement happens by reading the diagnosis. As long as a
diagnostic interrupt is not acknowledged, no further diagnostic inter-
rupt is issued at this slot.
Diagnostic interrupt handling
■
As soon as a module reports a diagnostic interrupt via the backplane bus, this is
automatically recognized by the CPU and in SB_DIAG_ALARM_STATUS the register
bit corresponding to the slot is set.
■
The diagnostic interrupt must be enabled for the module in iCube Engineer.
■
You can acknowledge a diagnostic message by reading record set 0x00 (diagnostics)
or 0x01 (extended diagnostics) from the corresponding slot. Information concerning
the structure of the diagnostic data may be found in the manual of the corresponding
System SLIO module.
■
In iCube Engineer you can use the Y_SB_DataRecordRead block from the system
library to read the corresponding record set. To do this, you must first add the
‘Y_SliceBus.pcwlx’ system library to your project.
System variable Type - description
SB_DATA_VALID BOOL - bus activity
■
This variable is set if data transfer via SliceBus is active.
SB_TOPOLOGY_OK BOOL - bus topology
■
This variable is set when the plugged modules on the SliceBus
match the configuration.
SB_DIAG_ALARM_STATUS ULINT - diagnostic status of the modules
■
As soon as a module reports a diagnostic alarm on the Sli-
ceBus , according to the slot position the corresponding bit is set
in the 64-bit register.