FB_AKDFltRpt

Description

Outputs AKD drive fault Information.

The oFAULT output turns TRUE when the selected drive goes into a fault state. This function block outputs the total number of faults in the AKD drive fault history variable (Pre-Defined Error Field Object 1003h), and the fault number and message for the last 3 drive faults.

Each fault has two outputs: the fault number and a fault message. The fault number is the same number as reported on the display of the AKD drive. The fault message provides a short description of the fault. For example if the first fault is a feedback error with a F401 displayed on the front of the drive, the output of this FB are:

• oFirstFaultNumber = 401
• oFirstFaultMessage = Failed To Set Feedback Type

The iResetfaultHistory Input resets the faults reported by the FB.

The oDriveNotUsed outputs a 1 (True) if the axis is configured to Simulated in the ProjectEthercat setup screen.

• 
  

• This function block lists the earliest occurring fault first. This may not be the same fault as is being reported on an AKD's display, which is based on priority. The MCFB_AKDFault function block may be preferred as it reports the same error as displayed on the drive.

This function Block can be used with either the PipeNetwork or PLCopen A vendor -and product- independent worldwide association active in Industrial Control and aiming at standardizing PLC file formats based on XML Motion engines.The following figure shows the function block I/O:

Figure 7-257: AKDFltRpt

Arguments

Input

EN	Description	ENABLES the Kollmorgen UDFB "User Defined Function Block" UDFB can be used as a sub-function block in another program of the application. It is described using FBD, LD, ST or IL language. Input / output parameters of a UDFB (as well as private variables) are declared in the variable editor as local variables of the UDFB (used in FFLD editor only)
	Data type	BOOL
	Range	[0 , 1]
	Unit	N/A
	Default	—
iEtherCat_ID	Description	EtherCAT ***EtherCAT is an open, high-performance Ethernet-based fieldbus system. The development goal of EtherCAT was to apply Ethernet to automation applications which require short data update times (also called cycle times) with low communication jitter (for synchronization purposes) and low hardware costs address desired AKD Drive ex. 1001 or AKD_1
	Data type	INT
	Range	—
	Unit	N/A
	Default	—
iRstFltHist	Description	When input is TRUE, clears all Faults saved to drives history
	Data type	BOOL
	Range	[0 , 1]
	Unit	N/A
	Default	—

Output

oFAULT	Description	TRUE if selected drive currently has a Fault
	Data type	BOOL
	Unit	N/A
oNumberFaults	Description	Number of faults saved in the Drive's history
	Data type	DINT
	Range	[0 , 10]
	Unit	N/A
oFirstFaultNumber	Description	Three digit AKD Fault identifier
	Data type	DINT
	Range	[100 , 999]
	Unit	N/A
oFirstFaultMessage	Description	Description of the Fault
	Data type	STRING
	Unit	N/A
oSecondFaultNumber	Description	Three digit AKD Fault identifier.
	Data type	DINT
	Range	[100 , 999]
	Unit	N/A
oSecondFaultMessage	Description	Description of the Fault
	Data type	STRING
	Unit	N/A
oThirdFaultNumber	Description	Three digit AKD Fault identifier
	Data type	DINT
	Range	[100 , 999]
	Unit	N/A
oThirdFaultMessage	Description	Description of the Fault
	Data type	STRING
	Unit	N/A
oDriveNotUsed	Description	Is this Drive Real (0) on Simulated (1)
	Data type	BOOL
	Unit	N/A

Usage

Typical usage for this UDFB are:

• Provide drive fault information that the application program uses to determine next steps such as perform a machine controlled stop or perform an immediate disable of the servo drives.
• In the application program send output fault information from this UDFB to the HMI "Human-machine interfaces " Also known as computer-human interfaces (CHI), and formerly known as man-machine interfaces, they are usually employed to communicate with PLCs and other computers, such as entering and monitoring temperatures or pressures for further automated control or emergency response for review by the machine operator.

Related Functions

MC_ReadStatus (PLCopen Motion Engine)

MLAxisStatus (Pipe Network Motion Engine)

MCFB_AKDFault

Example

Structured Text

//Execute the Function Block A function block groups an algorithm and a set of private data. It has inputs and outputs.
1_AKDFltRpt (1001, resetFaultHistST);

//Read Function A function calculates a result according to the current value of its inputs. A function has no internal data and is not linked to declared instances. Block Outputs
AKD1_Fault:= A1_AKDFltRpt.oFault;
AKD1_NumFault:= A1_AKDFltRpt.oNumberFaults;
AKD1_FirstFaultNumber:= A1_AKDFltRpt.oFirstFaultNumber;
AKD1_FirstFaultMessage:= A1_AKDFltRpt.oFirstFaultMessage;
AKD1_SecondFaultNumber:= A1_AKDFltRpt.oSecondFaultNumber;
AKD1_SecondFaultMessage:= A1_AKDFltRpt.oSecondFaultMessage;
AKD1_ThirdFaultNumber:= A1_AKDFltRpt.oThirdFaultNumber;
AKD1_ThirdFaultMessage:= A1_AKDFltRpt.oThirdFaultMessage;
;

• 
  

• A1_FaultReporting is an instance of the FB_S700FltRpt function block.

Ladder Diagram

Function Block Diagram

 [Top]