FAQ

The parameters available for configuration are based on the TeSys Tera system configuration. 

Store to Device operation cannot be performed when the motor is in run state.

By default, the Communication Loss protection function is disabled. If this function is enabled and the device is connected to the SoMove software through the Modbus RTU communication port, and if you try to disconnect the DTM, the communication loss trip will be triggered in the device.

Configuration of all setting under Parameters List, except for User Map, is disabled when the motor is in run state. In order to configure the parameters, stop the motor and then configure the settings.

When configuring the start and stop of the motor in a system as a single relay, the DI Start Validation Time should be greater than the DI Stop Validation Time.

To configure the parameters under the Fieldbus Protocol Setting, Profibus Settings, and HMI Communication sections, the device should be disconnected from the DTM. After performing a store to device operation to write the changed settings to the device, you can connect to the device by performing the Scan Devices using the new parameter values provided.

If the Main Unit Temperature value is set to None, Temperature Protection Main Unit settings will be unavailable for configuration.

If LTMTCUF control operator unit is connected on HMI port. The HMI communication settings must be configured as follows:

• Node Address: 1

• Baud rate: 19200 bps

• Parity: Even

• Byte Format: Big Endian

For more information on the individual parameters, refer to TeSys Tera Motor Management System User Guide – DOCA0257EN.

The value in the Default Value column remains constant, regardless of any configuration changes.

CT sensor unit firmware version updates regardless of sensor detection status.

If the CT is not connected, the DTM will highlight or display mismatch information in the Device tab.

During operations that result in the disconnection of the TeSys Tera system from the DTM, a slight delay is observed before the corresponding status is updated on the DTM.

You have to manually switch the protocol to TCP when loading the project.

The HMI firmware version cannot be displayed, if the HMI enters boot load mode prior to establishing a connection with the device through the DTM.