Troubleshooting

Overview

LTMCUF will work on the same commercial references and at its best with the same LTMR firmware (FW) version, with optimal compatibility from FW pack 10.

LTMCUF will manage all settings registers of current LTMR firmware version and all anterior firmware versions.

If there is a register mismatch between 2 firmware versions and a risk of parameter not being fully downloaded, LTMCUF displays a detected error message.

See the troubleshooting list below. Some detected errors are not critical and only indicate that a few registers could not be written. For example, some registers in memory are related to LTME, and LTME is not connected.

Another example: if LTMR is in a trip state during Restore/Backup command, it will be prevented from writing to registers related to the trip. LTMCUF will then display “Error code F07”. From FW pack 10, LTMR will have the specific access right to write trip register even in trip.

Trips and Alarm display

LTMCUF detects errors related to FDR services are displayed following the diagram below:

1 Trip/Alarm name
Detected error Code

By default, when LTMCUF is new, the detected error F09 "No config valid" appears as the LTMCUF memory is empty. This is a reminder that a backup operation needs to be done before using the FDR services.

Troubleshooting

Trip/Alarm name	Detected Error Code	Probable Cause	Checks or repairs
Target not match	F01	Target not match Targeted product commercial reference does not match the saved configuration. For example a config for Canopen cannot be transferred on a Modbus LTMR or a config for LTMR08 will not work on LTMR27 because of different current ranges.	The user made a mistake on the target. Operate FDR on products with the same references.
	F02	EtherNet version mismatch The target product is not compatible with the device profile recorded in the memory in terms of firmware or hardware.	Replace the targeted product with a compatible firmware and hardware version.
	F03	Ground current settings LTMCUF has not been able to write part of registers related to ground current protection. Possible reason is register range change between 2 different firmware versions.	Verify settings for: ground current protection disable at start reg 559.1 ground current trip and alarm settings minimum value: register 557,558,611,612. Another solution: use HMI FDR with same LTMR Firmware version. Then retry HMI FDR.
	F04	Network address is default value and cannot be written by LTMCUF. Set the network address.	Set a valid network address then redo backup operation.
	F05	LTME. Some settings related to LTME are activated but target does not have LTME connected.	Connect a LTME or verify the target is the correct one.
Restore Detected error or detected failure	F06	Restore Detected error or detected failure because at least one register had timeout when written. Restore has been interrupted.	Power off LTMR or LTMCUF and reconnect it to restart a restore. If detected error happens again please contact regional technical support.
	F07	Product is in trip state and registers linked to trip (637 to 642) cannot be written.	Cancel the trip condition then reset trip and redo restore.
	F08	LTMCU FW unknown registers. This can happen if new LTMR firmware requires additional registers not supported by LTMCUF.	Reserved trip code for future use.
No config valid	F09	No configuration loaded in memory or checksum trip (=configuration not valid).	Do backup memory again.
Motor is running	F10	When motor is running, some settings of LTMR cannot be modified so FDR cannot start.	Stop motor and retry HMI FDR.
Config via HMI not allowed	F11	Configuration through HMI port is disabled inside LTMR settings meaning that HMI FDR cannot work. Configuration via engineering tool is not allowed (register 601.09) or configuration via HMI is not allowed (register 601.08).	Use SoMove to Enable register 601.08 and 601.09.
Backup detected error or detected failure	F08	LTMCU FW unknown registers. Error detected if new firmware requires additional registers not supported by LTMCUF.	Reserved trip code for future FW package.
Backup detected error or detected failure	F12	At least one register had timeout. Backup has been interrupted.	Power off LTMR and retry backup operation. If detected error happens again please contact regional technical support.

When a detected error or detected failure occurs, please press to return to the main menu.