SoMove is Schneider’s counterpart to the drive-commissioning tools every vendor ships — and the discipline that makes commissioning stick is vendor-neutral. Here it is in ATV dialect.
The sequence
- Connect and identify: SoMove reads the drive’s exact reference and firmware; save the as-found parameter file before touching anything on an existing installation — evidence first.
- Motor data verbatim from the nameplate, connection type included. ATV families then offer autotuning (stationary as minimum); run it with the motor properly wired and cold, rerun after motor or cable changes — same physics, same reasons as everywhere.
- Choose the macro/application configuration deliberately (the ATV configuration presets wire I/O and logic for typical duties): a preset accepted blindly is a mystery for the next engineer; a preset chosen and documented is a time-saver.
- Protection floor before optimization: current/thermal limits, minimum-maximum frequencies, ramp times the mechanics tolerate, fault behavior choices (catch on the fly, automatic restart policies — the ones with safety implications get decided consciously).
- Interface and telegram: terminal, Modbus, Ethernet — command/reference channels are explicit in ATV land (the channel mixing options are flexible and thus a documentation duty).
- Archive twice: SoMove parameter file into the machine dossier plus a printed deviation summary. The multi-loader/backup options cover the fleet case.
FAQ
Equivalent of the trace for tuning? SoMove’s scope views cover the essentials — record the speed step response before/after tuning and file both.
Reusing a parameter file across “identical” drives? As a template, then re-autotune per unit — files carry measured motor data that does not transfer.
Zone Otomasyon commissions mixed-brand drive estates with one discipline. Multi-vendor service.