MPI 04.00 Reference >> mpiMotor

MPIMotorFaultBit

Definition

typedef enum MPIMotorFaultBit {
	MPIMotorFaultBitINVALID =	-1,

	MPIMotorFaultBitAMP_FAULT,
	MPIMotorFaultBitDRIVE_FAULT,
	MPIMotorFaultBitWATCHDOG_FAULT,
	MPIMotorFaultBitCHECKSUM_ERROR,
	MPIMotorFaultBitFEEDBACK_FAULT,
	MPIMotorFaultBitNOT_READY_FOR_REMOTE_CONTROL,
	MPIMotorFaultBitDRIVE_NOT_READY,
	MPIMotorFaultBitFEEDBACK_FAULT_SECONDARY,
	
	MPIMotorFaultBitEND,
	MPIMotorFaultBitFIRST = MPIMotorFaultBitINVALID + 1
} MPIMotorFaultBit;

 

Required Header: stdmpi.h

Change History: Modified in 04.00.

Description

MPIMotorFaultBit is an enumeration of motor fault bits for the SynqNet node drive interface. The support for motor fault bits is node/drive specific. Please see the node\drive manufacturer's documentation for details.

MPIMotorFaultBitAMP_FAULT
External amp fault input pin. Indicates a fault condition in the amplifier.Available on remote motion blocks.
MPIMotorFaultBitDRIVE_FAULT
Bit in the drive interface status register. Indicates a fault condition in the drive.NOT available on remote motion blocks.
MPIMotorFaultBitWATCHDOG_FAULT
Bit in the drive interface status register. Indicates a drive failure due to a watchdog timeout. The node alternately sets/clears the watchdog each sample, the drive's processor then clears/sets the watchdog. If the drive's processor does not respond, the watchdog fault bit is set.NOT available on remote motion blocks.
MPIMotorFaultBitCHECKSUM_ERROR
Bit in the drive interface status register. Indicates the data transfer (via serial or parallel memory interface) between the failed SynqNet node FPGA and drive with a checksum error.NOT available on remote motion blocks.
MPIMotorFaultBitFEEDBACK_FAULT
Bit in the drive interface status register. Active when one or more of the feedback status bits is triggered. Indicates that the drive/motor position feedback system has failed.Available on remote motion blocks.
MPIMotorFaultBitNOT_READY_FOR_REMOTE_CONTROL
Bit in the drive interface status register. If this bit is TRUE, the SynqNet drive is not ready for motor control operation. The reasons may include one or more of the following:
– Amplifier does not have sufficient power
– Safe torque-off input bit is active
– An inhibit input is active
– A fault is active
For details about the reasons, consult your drive manufacturer's documentation. The amp cannot be enabled until the NOT_READY_FOR_REMOTE_CONTROL bit is clear. This bit is NOT available with SynqNet RMBs (remote motion blocks).
MPIMotorFaultBitDRIVE_NOT_READY
Bit in the drive interface status register. The SynqNet drive is not ready to receive commands or servo motors. This fault indicates the drive has not completed its processor initialization or there is some other serious drive processor problem. NOT available on remote motion blocks.
MPIMotorFaultBitFEEDBACK_FAULT_SECONDARY
Bit in the drive interface status register. Active when one or more of the secondary feedback status bits is triggered. Indicates that the drive/motor auxilury position feedback system has failed. Available on remote motion blocks.

See Also

MPIMotorFaultMask | MPIMotorFaultConfig | mpiMotorStatus