14.2Statusbits
MOOG
ID
No.: CB40859-001 Date: 02/2018
MSD Servo Drive- Device Help
301
14 Device status
14.3Loadfactor
ID Index Name Unit Description
1651 LU_Timing_Max SWTiming:Maximumtimes
1651 0 LU_Timing ms ControlISR
1651 1 LU_Timing ms Asynchronous1msTask
1651 2 LU_Timing ms InitializationTask
1651 3 LU_Timing ms ControlCOMHandler
1651 4 LU_Timing ms ServiceCOMHandler
1651 5 LU_Timing ms CoDeSysRTSTask
1651 6 LU_Timing ms Motion1msTask
1652 LU_Timing_Avg SWTiming:Averagetimes
1652 0 LU_Timing ms ControlISR
1652 1 LU_Timing ms Asynchronous1msTask
1652 2 LU_Timing ms InitializationTask
1652 3 LU_Timing ms ControlCOMHandler
1652 4 LU_Timing ms ServiceCOMHandler
1652 5 LU_Timing ms CoDeSysRTSTask
1652 6 LU_Timing ms Motion1msTask
1653 0 LU_Timing_Reset resetmaximalandaveragetimingvalues
1654 0 LU_Timing_Total % totalcomputationalload
1661 LU_MemoryLoad SWMemory:Memoryload
1661 0 LU_Memory % ContextSaveArea
1661 1 LU_Memory % Dynamicprogrammemorytotal
1661 2 LU_Memory % DynamicprogrammemoryICODE
1661 3 LU_Memory % DynamicprogrammemorySCODE
Table 14.3: “Device status - Load” parameters
Fig. 14.2: “Status bits” window
To select the DriveCom status word (P151[0]) for viewing in the oscilloscope, click
on the “Scope signals of
Status bits
” (at the very top of the window).
ID Index Name Unit Description
151 0 MPRO_DRVCOM_
STAT_DWord
DriveComstatusword(32Bit)
Table 14.2: “Device status - Status bits” parameters
Comprehensive error information can be accessed using the “Error History” button
(see Section "Alarms and warnings (Details)" on page 255.)
If an error is currently present, it can be confirmed by clicking on the “Quit error”
button.
ID Index Name Unit Description
150 0 Numericalstatus
152 0 Textualstatus
153 0 Faultreset
Actualnumericaldevicestatus
Actualtextualdevicestatus
Faultresetcommand
Table 14.1: “Device status” parameters