![background image](http://html1.mh-extra.com/html/magnetek/impulse-link-5/impulse-link-5_user-manual_3572949018.webp)
IMPULSE
®
•Link 5 Instruction Manual
April 2020
Page 18 of 47
4.4.4. Runs
When the DLS4 detects a run, it increments the run counter and begins to take average and peak values of the
Monitors being logged. It also logs how long the run remains active. When the run has ended, this information
is written to the internal memory. If the run ended due to a fault, the reference to that fault gets linked with the
run. A reference to the last alarm (if any) that occurred during the run is also stored. The DLS4 records
numerous pieces of data at the end of the run event. Each of these can be turned ON or OFF for viewing
purposes. For example, when
“Model” is deselected, it will not be displayed in the Events window.
shows the various data that is collected.
Name
Description
Run #
Number of Runs recorded by the DLS4.
Date
Date the Run event ended [Day/Month/Year].
Time
Time the Run event ended [Hour:Minute:Second].
Direction
“FWD” or “REV”.
Duration [sec]
Amount of time the Run command was active.
Avg DC Bus [VDC]
Average DC Bus Voltage during the Run.
Peak DC Bus [VDC]
Peak DC Bus Voltage during the run.
Avg Iout [A]
Average output current to the motor.
Peak Iout [A]
Peak output current to the motor.
Avg Fout [Hz]
Average output frequency of the drive.
Peak Fout [Hz]
Peak output frequency of the drive.
Avg Mtr Speed [Hz]
1
Average speed of the motor.
Peak Mtr Speed [Hz]
1
Peak speed of the motor.
Avg Mtr Torque [%]
1
Average torque applied to the motor during the Run.
Peak Mtr Torque [%]
1
Peak torque in the motor.
Heatsink [°C]
Heatsink temperature when the Run event ended.
Last Alarm
Last Alarm recorded.
Last Fault
Last Fault recorded.
Control
Control method of the drive.
Motion
Motion of the drive.
1
Only valid when the control method is Open Loop Vector or Flux Vector.
Table 2: Run Data
– AC Drive