Technical FAQs

Ask a Question

Why does the ATV630 drive not save parameters when programmed over Modbus RTU?

Issue:
Why does the ATV630 drive not save parameters when programmed over Modbus RTU?

Product Line:
Altivar 630, Process

Environment:
All

Cause:
N/A

Resolution:
Modbus register value 8504 (CMI) will need to be written to in order for the drive parameters to be saved over the network.  

CMI      
Bit 0:    Factory setting command (active at 1).
Bit 1:   Save configuration to EEPROM non-volatile memory command (active at 1).
           This Bit automatically changes to 0 after the request is taken into account. The command is only active if the drive is stopped, and not in "5-Operation enabled" state.
Note: If CMI is a periodic network variable, the PLC program must write it to 0 after the first request is taken into account. The life of the EEPROM memory is limited to 100,000 write operations.
           Note: If the motor or configuration switching function is active, the configuration in the RAM is saved to the EEPROM in the configuration designated by [Config. Active] (CnFS).
Bit 2:    Reserved (= 0).
Bit 3:    Reserved (= 0).
Bit 4:    Reserved (= 0).
Bit 5:    Reserved (= 0).
Bit 6:    Reserved (= 0).
Bit 7:    Reserved (= 0).
Bit 8:    Reserved (= 0).
Bit 9:    Definition of the frequency reference (LFr) and output frequency (rFr) unit:
            = 0: 0.1 Hz
 = 1: Standardized value 16 signed bits based on the maximum frequency. The value 32767 corresponds to [Max frequency] (tFr). The default value of [Max frequency] (tFr) is 60 Hz, and the resolution is then approximately 0.0018 Hz.
           This function has no effect on the speed reference (LFrd) or the output speed (rFrd).
Bit 10:    Reserved (= 0).
Bit 11:    Reserved (= 0).
Bit 12:    Reserved (= 0).
Bit 13:    Reserved (= 0).
Bit 14:    Reserved (= 0).
Bit 15:    Parameter consistency check
 = 0: The check is activated. Each time a parameter is written, the drive checks the relationship between the written parameter and the configuration in the drive. For example, the [High speed] (HSP) parameter must be less than [Max frequency] (tFr).
 = 1: The check is deactivated. The drive is locked in stop mode. In this drive state, the configuration can be written parameter by parameter and the drive does not modify the values that are written.  The switch from 1 to 0 triggers a calculation of the consistency of the configuration. Some parameters can be modified automatically by the drive.
Was this helpful?
What can we do to improve the information ?