ABB NextMove e100 motion controller troubleshooting guide

The configuration logic of EPL remote axis and local axis

Each of the 7 local axes (4-step+3 servo) occupies one profiler; There are three control methods for remote EPL axis: the management node continuously sends incremental demands (consumes profiler), the driver profiles the demand after sending a single demand (does not consume profiler), or only monitors feedback (does not consume profiler). Therefore, the 16 profiles can be allocated in any combination of "7 local+9 remote" or "4 groups x 4 synchronous axes". Remote axis configuration only requires specifying the node ID and axis number, which can be completed through the Add Device → Map process in the System Configuration Wizard. The axis number and node ID do not need to be the same, but it is recommended to be consistent for small networks for easy identification.

ScaleFactor calibration is the programming foundation: Mint's position/velocity commands are represented by encoder orthogonal counts (servo) or steps (step). After setting SCALEFACTOR, they are converted to user units -1000 line encoder x 4=4000 counts/revolution. Setting SCALEFACTOR=4000, MOVER (0)=4 means 4 revolutions. Setting SCALEFACTOR on the remote axis does not result in down transmission, and position data is always transmitted in raw count, so the remote axis can correctly parse instructions no matter what.

Common troubleshooting (classified by phenomenon)

(1) Status LED indicator. Green constant light=initialization completed, controller enabled (normal); Green flashing rapidly=firmware download in progress; Red constant light=initialization in progress; Red flashing=serious hardware or firmware error, please contact ABB. The detailed error code can be found in the Error Handling manual chapter by pressing F1 in Mint WorkBench.

(2) Mint WorkBench cannot detect the controller. Check sequentially: whether the 24V power supply is connected to X1 and has been closed; Whether the USB/Ethernet/serial port cable is well connected and there are no other programs occupying the serial port; Does the "USB Motion Controller" entry appear in the Device Manager; Is the node ID mistakenly set to 240 (F0) when connecting to Ethernet, and is the TCP/IP configuration of the PC network card correct according to 192.168.100.241; Is the 'Search up to Nodexx' value in the Select Controller dialog box lower than the controller node ID? After firmware download, the controller must be powered off and restarted, which is an official mandatory step.

(3) The motor does not rotate or loses control. The controller is working but the motor is not rotating: check the motor driver wiring, drive enable output configuration (section 5.4.5), and whether the servo loop gain is zero (factory zero, 0 V requirement upon power on). When the motor is powered on, it loses control and flies: first, verify that the controller and driver are grounded together; Check if the encoder feedback signal is received correctly and powered normally; When confirming zero demand, the driver demand input is 0 V. After the motor loses control for a short period of time, stop: check the polarity of the encoder channel - positive demand should generate positive position increment. ENCODERMODE can be used to reverse the encoder counting direction, DACMODE can be used to reverse the DAC output polarity, and both must be used together; When the tracking error is too large, FOLERORMODE can be set to 0 to temporarily disable detection.

(4) Inconsistent reciprocating positioning. Check whether the common ground and encoder channels are affected by electrical noise interference, and whether the A/B square waves maintain a phase difference of about 90 °; The encoder cable must be shielded twisted pair, with the outer shield grounded at both ends and the inner shield grounded only at the controller end. Stepper axis step loss is usually caused by acceleration, speed, or load exceeding the motor's capacity.

(5) CANopen bus passive/off. The passive state indicates that the error count exceeds 127 (self-healing before recovery threshold), and the off state indicates that it exceeds 255 and enters BUS OFF, which must be restored using the BUSRESET keyword or reset controller. The troubleshooting checklist for both is the same: ① 12-24V isolated power supply between pins 9 and 6/3; ② At least one other CANopen node exists on the network; ③ Only terminate at both ends of the bus; ④ Consistent baud rate across the entire network; ⑤ Unique node ID; ⑥ Cable integrity.

(6) EPL network abnormality. Confirm that there is only one management node (ID 240) in the entire network, all controlled node reference sources have been set to EPL in the Operating Mode Wizard, each device node ID is unique, and each branch daisy chain does not exceed 10. The Ethernet redirection function of MMC allows remote viewing and configuration of EPL nodes through only USB physical connection, provided that the node switch of NextMove e100 is not set to F0.

Servo tuning methodology (Mint gain system)

The NextMove e100 position loop includes KPROP (proportional), KINT (integral), KVEL (velocity feedback), KDERIV (derivative), and feedforward term KVELF/KACEL. Practical tuning process: