Instruction manual Modbus®/RTU/TCP – DIN, Pro, Core variants

MITSUBISHI ELECTRIC

Art. no14 01 Versio

MEsoftstart

Industrial Soft StartersDIN, Pro and Core Variants

Instruction Manual

Modbus®/RTUModbus®/TCP

Interface Control Document

INDUSTRIAL AUTOMATIONMITSUBISHI ELECTRIC.: 496950

2020n A Version check

Instruction ManualMEsoftstart

Art. no.: 496950

Version Changes / Additions / Corrections

A 01/2020 pdp First edition

For maximum safety● Mitsubishi Electric soft starters are not designed or manufactured to be used in equipment or systems in situa-

tions that can affect or endanger human life.● When considering this product for operation in special applications such as machinery or systems used in pas-

senger transportation, medical, aerospace, atomic power, electric power, or submarine repeating applications,please contact your nearest Mitsubishi Electric sales representative.

● Although this product was manufactured under conditions of strict quality control, you are strongly advised toinstall safety devices to prevent serious accidents when it is used in facilities where breakdowns of the productare likely to cause a serious accident.

● Please check upon receiving of the soft starter whether this instruction manual corresponds to the deliveredsoft starter. Compare the specifications on the capacity plate with the specifications given in this manual.

Thank you for choosing this Mitsubishi Electric soft starter.

This instruction manual provides instructions and guidelines for the interface control of the MEsoftstartseries soft starters DIN, Pro and Core variants. Incorrect handling might cause an unexpected fault. Be-fore using the soft starter, always read the instruction manual of the MEsoftstart soft starter and thisinstruction manual carefully and ensure to follow all safety instructions to use the equipment to its op-timum.

Safety instructions

Do not attempt to install, operate, maintain or inspect the soft starter until you have read through thisinstruction manual and appended documents carefully and can use the equipment correctly. Do notuse the soft starter until you have a full knowledge of the equipment, safety information andinstructions and are qualified to do installations of this nature.Installation, operation, maintenance and inspection must be performed by qualified personnel. Here,qualified personnel means personnel who meets all the conditions below.

● A person who took a proper engineering training. Such training may be available at your localMitsubishi Electric office. Contact your local sales office for schedules and locations.

● A person who can access operating manuals for the protective devices (e.g. light curtain) connectedto the safety control system. A person who has read and familiarized himself/herself with the manuals.

In this instruction manual, the safety instruction levels are classified into “WARNING” and “CAUTION”.

Note that even the CAUTION level may lead to a serious consequence according to conditions. Pleasefollow strictly the instructions of both levels because they are important to personnel safety.

PWARNING:Assumes that incorrect handling may cause hazardous conditions, resulting in death or severe injury.

ECAUTION:Assumes that incorrect handling may cause hazardous conditions, resulting in medium or slightinjury, or may cause physical damage only.

MEsoftstart I

Electric shock prevention

Fire prevention

PWARNING:● Do not open the soft starter enclosure while there is power on the soft starter power terminals.● Always replace the finger guards after wiring is completed.● Ensure that the power is OFF (MCCB open) before working on the motor or any load connected

to the motor. Do not assume that the power at the motor is OFF while the power to the softstarter is still ON.NOTE: When wired for inside-delta connection, the six motor terminals remain live even whenthe motor is off.

● Do not run the soft starter with the cover removed - this increases the risk of access to theexposed terminals and electric shock.

● Even if power is OFF, do not open the soft starter enclosure except for replacement of a fan.● Before wiring or inspection, the power must be switched OFF.● This soft starter must be earthed (grounded). Earthing (grounding) must conform to the

requirements of national and local safety regulations and electrical code (NEC section 250,IEC 536 class 1 and other applicable standards).

● Any person who is involved in wiring or inspection of this equipment shall be fully competentto do the work.

● The soft starter must be installed before wiring otherwise there is a risk of electric shock or injury.● Ensure that cables are not damaged, under excessive stress or pinched anywhere otherwise

there is a risk of causing a short circuit or even electric shock.● Do not change the cooling fan while power is ON - this is dangerous.● Do not touch any part of the soft starter or handle the cables with wet hands - this increases

the risk of electric shock.

ECAUTION:● The soft starter must be installed against a non-flammable surface - mounting it in proximity

of flammable material may cause a fire.● If the soft starter has become faulty, the soft starter power must be switched OFF. A contin-

uous flow of large current may cause a fire.● Be sure to perform weekly and periodic inspections as specified in the Instruction Manual. If

a product is used without regular inspection, damage or even a fire may occur.

II

Injury prevention

Transportation and installation

ECAUTION:● The voltage applied to each terminal must be as specified in the Instruction Manual - other-

wise damage will occur.● The cables must be connected to the correct terminals - otherwise damage may occur.● The connection order of the phases must be correct. ● While power is ON or for some time after it was ON, do not touch the soft starter as it may be

extremely hot and could inflict a burn injury.

ECAUTION:● Any person who is opening a package using a sharp object, such as a knife and cutter, must

wear gloves to prevent injuries caused by the edge of the sharp object.● The product must be transported in an appropriate method for the weight of the package.

Failure to do so may lead to injuries.● Do not stand or rest heavy objects on the product.● Do not stack the boxes containing soft starters higher than the number recommended.● During installation, caution must be taken not to drop the soft starter as doing so may cause

injuries and damage to the product.● The product must be installed against a surface that withstands the weight of the soft starter.● Do not install the product on a hot surface.● The mounting orientation of the soft starter must be correct.● The soft starter must be installed on a strong surface securely with screws so that it will not drop.● Do not install or operate the soft starter if it is damaged or has parts missing.● Foreign conductive objects must be prevented from entering the soft starter. That includes

screws and metal fragments or flammable substance such as oil and water.● As the soft starter is a precision instrument, do not drop or subject it to impact.● For all models of the soft starter, the surrounding air temperature must be 0 to +50 °C.

Otherwise the soft starter may be damaged.● The ambient humidity specification must be adhered to. Otherwise the soft starter may be

damaged. (Refer to the MEsoftstart soft starter instruction manual)● The storage temperature (applicable for a short time, e.g. during transit) specification must

be adhered to. Otherwise the soft starter may be damaged.● The soft starter must be used indoors (without corrosive gas, flammable gas, oil mist, dust

and dirt etc.) Otherwise the soft starter may be damaged.● The soft starter can be used as rated, at an altitude of 1400 m or less above sea level. Higher

altitudes require de-rating.

MEsoftstart III

Transportation and installation (continued)

Wiring

Usage

ECAUTION:● The soft starter should not be subjected to operational vibration. The soft starter is designed

for transportation vibration in its factory supplied packaging only. (Refer to the MEsoftstartsoft starter instruction manual)

● If halogen-based materials (fluorine, chlorine, bromine, iodine, etc.) infiltrate into a Mitsubi-shi product, the product will be damaged. Halogen-based materials are often included infumigant, which is used to sterilize or disinfect wooden packages. When packaging, preventresidual fumigant components from being infiltrated into Mitsubishi products, or use analternative sterilization or disinfection method (heat disinfection, etc.) for packaging. Ster-ilization or disinfection of wooden package should also be performed before packaging theproduct.

ECAUTION:● The output side terminals (terminals T1, T2, and T3) must be connected correctly. The soft

starter will protect against phase reversal if configured to do so. If the soft starter is config-ured to not check the phase rotation, the motor will rotate inversely - which may, or may notbe a problem in the installation.

● Never connect the output side terminals (terminals T1, T2, and T3) to the grid power supply.Applying the grid power supply to motor terminals (T1, T2, T3) will damage the soft starter.The induction motor may be connected to the grid power supply only via a bypass contactorthat is under control of the soft starter.

● Return wires from an inside delta motor connection should be connected to the supply lineson L1, L2, L3 (and NOT on the Bypass terminals BL1 BL2 BL3).

ECAUTION:● The soft starter's built-in temperature trip functions can only protect the motor from over-

heating if the motor temperature sensor is wired in and connected to the motor at anappropriate temperature sensing location.

● The effect of electromagnetic interference must be reduced by using a noise filter or by othermeans. Otherwise nearby electronic equipment may be affected.

● Before running a soft starter, which had been stored for a long period, inspection and testoperation must be performed.

● Static electricity in your body must be discharged before you touch the product.● Some of the diagrams, drawings and photographs in the instruction manual show the

product without a cover or partially open for explanation. Never operate the product in thismanner. The cover(s) must always be re-installed before operating the soft starter.

● Earthing leakage detection is not active when inside delta motor wiring configuration is used.

IV

Commissioning

Emergency stop

Maintenance, inspection and parts replacement

Disposal

ECAUTION:Before starting operation, each configuration parameter must be adjusted for the installationand motor size. Failure to do so may cause unexpected behaviour or damage to the motor.

ECAUTION:● An independent hardware emergency stop must be provided as a safety measure to prevent

hazardous conditions to the machine and equipment in case of soft starter failure (refer tothe MEsoftstart soft starter instruction manual).

● When the circuit breaker on the soft starter input side trips, the wiring must be checked forfaults (short circuit), damage, etc. The cause of the trip must be identified and removedbefore turning ON the power of the breaker.

● When a fuse on the soft starter input blows, the wiring and the soft starter needs to bechecked for faults. The cause of the blown fuse must be identified and removed beforereplacing the fuse and turning on again.

● When a protective function activates, take an appropriate corrective action, then reset thesoft starter, and resume the operation.

ECAUTION:Do not carry out a megger (insulation resistance) test on the soft starter when connected. It maycause damage.

ECAUTION:When unserviceable, the soft starter should be treated as industrial waste.

MEsoftstart V

Symbols used in the manual

Use of instructions

Instructions concerning important information are marked separately and are displayed as follows:

Use of examples

Examples are marked separately and are displayed as follows:

Use of numbering in the figures

Numbering within the figures is displayed by white numbers within black circles and is explained ina table following it using the same number, e.g.:

1 2 3 4

Use of handling instructions

Handling instructions are steps that must be carried out in their exact sequence during startup, op-eration, maintenance and similar operations.

They are numbered consecutively (black numbers in white circles):

a Text.

b Text.

c Text.

Use of footnotes in tables

Instructions in tables are explained in footnotes underneath the tables (in superscript). There is a foot-note character at the appropriate position in the table (in superscript).

If there are several footnotes for one table then these are numbered consecutively underneath the ta-ble (black numbers in white circle, in superscript):a Text b Text c Text

NOTE Text of instruction

Example å Example text ã

VI

Contents

MEsoftst

Contents

1 Scope

1.1 System overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

1.1.1 MEsoftstart/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

1.1.2 MEsoftstart/DIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

1.2 Modbus® protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

1.3 Document intent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

1.4 Document outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

1.5 Applicable and referenced documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

1.5.1 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

1.5.2 Reference documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

2 Interface requirements

2.1 Physical interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

2.1.1 Modbus®/RTU 485 (applicable to all MEsoftstart models) . . . . . . . . . . . . . . . . . . . . . . . .2-1

2.1.2 Modbus®/TCP Ethernet (applicable to MEsoftstart/I Pro only). . . . . . . . . . . . . . . . . . . .2-2

2.2 Slave (soft starter) address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

2.2.1 Modbus®/RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

2.2.2 Modbus®/TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

2.3 Modbus® message structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

2.3.1 Modbus®/RTU message structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

2.3.2 Modbus®/TCP message structure (applicable to MEsoftstart/I Pro only) . . . . . . . . . .2-4

2.4 Data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2.4.1 Unsigned short integer (U2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2.4.2 Unsigned long integer (U4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2.4.3 IP Address (IP4) (applicable to MEsoftstart/I Pro only) . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2.5 Interaction between the TCP and RTU interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

art VII

Contents

VIII

3 MEsoftstart/I Modbus® function codes and registers

3.1 Supported function codes (MEsoftstart/I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

3.2 Scaling of register values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

3.3 Limits for register values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

3.4 Input registers (MEsoftstart/I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

3.5 Holding registers (MEsoftstart/I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8

3.5.1 Shadow holding registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

3.5.2 Completing a configuration write sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

3.5.3 Suggested sequence of operations to change the configuration. . . . . . . . . . . . . . . 3-26

3.5.4 Using the unlock register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

3.5.5 Consistency of entire configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

3.5.6 Soft starter valid commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.6 Supported exception codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

4 MEsoftstart/DIN Modbus® function codes and registers

4.1 Supported function codes (MEsoftstart/DIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

4.2 Scaling of register values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

4.3 Limits for register values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

4.4 Input registers (MEsoftstart/DIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

4.5 Holding registers (MEsoftstart/DIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5

4.5.1 Using the unlock register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7

4.5.2 Consistency of entire configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7

4.5.3 Soft starter valid commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8

4.6 Supported exception codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9

A Appendix

A.1 Modbus®/RTU CRC calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Scope

1 Scope

This document establishes the ICD (Interface Control Document) for communication with theMEsoftstart DIN and MEsoftstart industrial soft starters (both Pro and Core models) of software ver-sions V1.xx. This ICD provides the physical interface characteristics, and applicable Modbus® functioncodes and registers as implemented in this soft starter to effect:

● control (start, stop and reset functions),

● operational parameter monitoring (all operational parameters internal to the soft starter), and

● configuration (monitoring of- and changes to parameters affecting soft starter operation).

The Pro variants support both Modbus®/RTU and TCP, while the DIN and Core versions supportModbus®/RTU only.

List of abbreviations

Abbreviation Definition

AC Alternating Current

ARIO ArioGenix (Pty) Ltd.

ASCII American Standard Code for Information Interchange

BCD Binary Coded Decimal

CAT5 Category 5 network cable

CAT6 Category 6 network cable

CB Circuit Breaker

CPU Central Processing Unit

CRC Cyclic Redundancy Check

D02L MEsoftstart/DIN model identifier

D03S MEsoftstart/DIN model identifier

DIN Metal rail used for mounting equipment

DIP Dual-in-line package (switch)

EIA/TIA-485 Serial communication hardware standard

FC Function Code

HMI Human Machine Interface

I00 MEsoftstart/I model identifier (100A model)





ICD Interface Control Document

ID Identifier

IF Interface

IP Internet Protocol

IP4 Internet Protocol version 4

LM35 Type of temperature sensor

LS Least Significant

LSB Least Significant Bit

MB/s Mega-Bits per second

MFLC Maximum Full Load Current

MOLC Motor Overload Current

MS Most Significant

MSC Maximum Starting Current

MULC Motor Underload Current

NA Not Applicable

PC Personal Computer (also implies Laptop)

PF Power Factor

Tab. 1-1: List of abbreviations (1)

MEsoftstart 1 - 1

Scope

PT100 Type of temperature sensor

RJ45 Standard type of connector for network cables

RMS Root Mean Square

RPM Revolutions per Minute

RS485 Electrical standard for use in serial communications (used for Modbus® in MEsoftstart)

RTC Real Time Clock

RTU Protocol variant for Modbus® (RTU for RS485)

SCADA Supervisory Control and Data Acquisition

SCR Silicon Controlled Rectifier

TCP Protocol variant for Modbus® (TCP for Ethernet communication)

TCP/IP Transmission Control Protocol

TFT Thin Film Transistor (display)

UART Universal Asynchronous Receiver Transmitter

UInt16 16-bit Unsigned Integer value type

UInt32 32-bit Unsigned Integer value type

Abbreviation Definition

Tab. 1-1: List of abbreviations (2)

1 - 2

System overview Scope

1.1 System overview

1.1.1 MEsoftstart/I

The MEsoftstart/I industrial soft starter range are microprocessor-based advanced digital soft startersfeaturing bypass control for internal or external bypass and full 3-phase control. It incorporates bothenhanced soft-start and soft-stop characteristics providing the best solution for a wide range of appli-cations. Two MEsoftstart/I variants are available namely “Core” and “Pro”:

Core – Low-cost, simple-to-configure models, using 6 potentiometers each for start and stop rampdefinition and a few slider switches to fully configure the soft starter. Monitoring and control with PCapplication on Modbus®/RTU.

NOTE The Core model features a Modbus®/RTU port, potentiometer and dip-switch HMI for configura-tion. The parameters that are set via these controls, cannot be set vie the Modbus® interface, andcan only be monitored via this interface.

I Core soft starter

Fig. 1-1: Softstarter Core model

MEsoftstart 1 - 3

Scope System overview

Pro – Used for complex applications where more advanced control options are required. Setting up,monitoring and control with full-function local colour touch TFT screen (as shown) and/or PC appli-cation on Modbus®/RTU or TCP.

1.1.2 MEsoftstart/DIN

The MEsoftstart/DIN range are ready-to-use two and three phase intelligent soft starters. TheMEsoftstart/DIN range offers a compact solution for small to medium applications such as pumps,fans, scroll compressors, filler lines, conveyors and more. The operating current is up to 32A RMS andthe starting current is up to 100A RMS. Built-in bypass relays are included in all models. Reverse phaserotation protection is included as well as motor protection using motor thermal overload protectioncurves (Classes 1, 2, 5, 10). Also included is a pre-start short circuit detection and motor protectionfunctionality.

The MEsoftstart/DIN models have no local HMI and is factory configured for the largest motor that isapplicable for the model. On all DIN models except the factory configured model, monitoring, controland further configuration may be done via the Modbus®/RTU port.

NOTE The Pro model features a touch-display for local configuration. On these models, all configurationparameters may be set and monitored via the Modbus® interface (and the touch-display).

I Pro soft starter

Fig. 1-2: Softstarter Pro model

DIN soft starter

Fig. 1-3: Softstarter DIN model

1 - 4

Modbus® protocol Scope

1.2 Modbus® protocol

Note that the Modbus® protocol will not be described in this document, but rather derived from theModbus® standard documents (refer to section 1.5.1). Any implementation specific information (set-tings, physical characteristics, options, etc.) applicable to this specific Modbus® implementation willbe given in the appropriate locations in this ICD.

1.3 Document intent

The intent of this document is to define the implementation specific information for this use case,such that a general purpose SCADA system can interface with the industrial soft starter for control andmonitoring purposes using the Modbus® commands described in this ICD.

1.4 Document outline

Section 1.5 provides any external documentation required for this document. It includes any stand-ards as well as documents that apply to this document.

Chapter 2 provides the settings and information applicable to this implementation of Modbus® forthis platform. Any physical characteristics and application specific information to fully define theModbus® implementation is given in this chapter.

Chapter 3 provides the Modbus® function codes and registers implemented by the MEsoftstart/I Proand Core models.

Chapter 4 provides the Modbus® function codes and registers implemented by the MEsoftstart/DINmodels (all except the factory configured model).

Appendices provide reference information

1.5 Applicable and referenced documents

1.5.1 Standards

This document used the following three documents as reference from the website:http://www.modbus.org

1) MODBUS over serial line specification and implementation guide V1.02

2) MODBUS Application Protocol Specification V1.1b3

3) MODBUS Messaging on TCP/IP Implementation Guide V1.0b

1.5.2 Reference documents

1) A015-070-INT-EN-004, MEsoftstart DIN Rail-/Panel mounted Low-Voltage Soft Starter Installationand Instruction Manual

2) A018-070-INT-EN-004 MEsoftstart Industry hardened low-voltage soft starter Users Installationand Instruction Manual

MEsoftstart 1 - 5

http://www.modbus.org

Scope Applicable and referenced documents

1 - 6

Physical interfaces Interface requirements

2 Interface requirements

This chapter defines the Modbus® implementation information as is applicable to this ICD. It isassumed that the reader is familiar with Modbus®, using the documents 1) and 2) in section 1.5.1 as ref-erence for the Modbus® standard. This chapter will only address the settings and information appli-cable to the Modbus® implementation as for this ICD, rather than addressing the entire Modbus®standard.

2.1 Physical interfaces

2.1.1 Modbus®/RTU 485 (applicable to all MEsoftstart models)

Modbus® serial line settings

The Modbus®/RTU implementation is implemented according to the underlying communicationsmedium of the specified network. This means that the network media indicated as RS485 are imple-mented as standard serial Modbus®/RTU over an EIA/TIA-485 (RS485) physical interface. These RS485serial interfaces are setup as indicated in tab. 2-1.

Setting Value

Data bit rate 115200 bits per second

Number of start bits 1

Number of stop bits 1

Parity Even

Flow control None

Tab. 2-1: Modbus®/RTU default serial settings

Setting Value

Data bit rate 9600, 14400, 19200, 28800, 38400, 57600, 115200 bits per second

Number of start bits 1

Number of stop bits 1

Parity None, Even, Odd

Tab. 2-2: Modbus®/RTU range of serial settings

MEsoftstart 2 - 1

Interface requirements Physical interfaces

Modbus® multi-drop layout

The typical connection topology for a multi-drop connection is as per fig. 2-1. In the diagram, the“master” is the Modbus®/RTU SCADA master and is usually but not necessarily at the end of the cablenetwork. Therefore, view this diagram as though any one of the stations could be located at any pointin the network wiring including in the middle somewhere or at either end. Since the installer may berequired to run a long network at 115200 bits per second, it is recommended that CAT5 or CAT6shielded cable is used.

The “master” in this diagram is assumed to have a built in 120 Ω termination resistor. If this is not thecase the installer must allow for 120 Ω terminations that are easily implemented using off the shelfcommercially available Modbus® RJ45 line terminators that have 120 Ω resistor built in. Typical exam-ples can be sourced from companies like Schneider Electric with part number VW3A8306RC as lookexactly like a normal RJ45 connector.

Other typical physical layer requirements from the document 1) in section 1.5.1 should be followed.

2.1.2 Modbus®/TCP Ethernet (applicable to MEsoftstart/I Pro only)

This Modbus®/TCP implementation is implemented according to the underlying communicationsmedium of the specified network. This means that network media indicated as TCP are implementedas standard serial Modbus®/ TCP over an 10/100 MBs Ethernet physical interface typically using cablespecification CAT5 or better with an RJ45 connector on the cable. The cable may be crossed over ornormal. This TCP interface is setup as indicated in tab. 2-3.

Multi-drop-connections

Fig. 2-1: Typical Modbus® serial line multi-drop connections implementation

Setting Value

Data bit rate 10/100 MB/s

Default slave IP address (soft starter) 192.168.0.15

TCP/IP network mask 255.255.255.0 (class C)

TCP/IP port 502

Modbus®/ TCP transaction identifier Assigned by master and sent back in response by slave

Tab. 2-3: Modbus®/TCP Ethernet settings

Master Disp. slave 1 Disp. slave 2

120 Ω

2 - 2

Slave (soft starter) address assignment Interface requirements

2.2 Slave (soft starter) address assignment

2.2.1 Modbus®/RTU

The industrial soft starter unit has a default slave address of 1 which can be changed to any value from1 to 247.

2.2.2 Modbus®/TCP

In Modbus®/TCP, the slave address is the unit identifier and since the soft starter does not function asa HUB or bridge between a TCP and a sub RS485 network the unit identifier is set to a default 0xFF.

MEsoftstart 2 - 3

Interface requirements Modbus® message structure

2.3 Modbus® message structure

2.3.1 Modbus®/RTU message structure

The MEsoftstart soft starters implement the Modbus®/RTU frame as described in section 2.3 of thedocument 1) in section 1.5.1. The frame format is shown in tab. 2-4.

The different fields comprising the Modbus®/RTU frame are described below:

● Address field: A single byte address is used (default for the soft starters is 1).

● Function code: A single byte function code (FC) is used (the supported function codes aredescribed in section 3.1 for MEsoftstart/I and section 4.1 for MEsoftstart/DIN

● Data payload: The variable-length data payload content varies as a function of the packet type.The contents of this field are transferred and addressed in 16-bit fields, i.e. a field of 16 bits is thesmallest addressable/distinct field in a Modbus® PDU. All registers (16-bit fields) are sent in BigEndian (or “network”) order, i.e. the most significant byte of a register is sent first. For any instancewhere this may be different, the difference is explicitly described in the parameter description.

● CRC: The standard 16-bit Modbus® CRC is used. An example C implementation is given in section A.

2.3.2 Modbus®/TCP message structure (applicable to MEsoftstart/I Pro only)

The soft starters (Pro only) implement the Modbus®/TCP frame as described in section 3 ofdocument 3) in section 1.5.1. The frame format is shown in tab. 2-5.

The different fields comprising the Modbus®/TCP frame are described below:

● Transaction Identifier: This is a two-byte identifier which is initialized by the client (master) andcopied into the response by the slave. This is used to pair responses to requests.

● Protocol Identifier: A two-byte field set to 0 for Modbus®.

● Length: This two-byte fields specifies the total number of bytes following (and not including) thisfield.

● Unit Identifier: This field is used for intra-system routing, such as connecting to a Modbus®/RTUslave through a Ethernet TCP/IP gateway. This is not relevant in our application, hence this valueis set to the default 0xFF

● Function Code and Data Payload: These fields are the same as for Modbus®/RTU.

NOTE In this table the fields making up the Modbus® PDU are highlighted in green while theModbus®/RTU frame overhead is highlighted in blue.

Address field Function code (FC) Data payload CRC

Tab. 2-4: Modbus®/RTU frame overview

NOTE In this table the fields making up the Modbus® PDU are highlighted in green while theModbus®/TCP frame overhead is highlighted in blue.

Transaction identifier

Protocol identifier Length Unit

identifier Function code (FC) Data payload

Tab. 2-5: Modbus®/TCP frame overview

2 - 4

Data types Interface requirements

2.4 Data types

This section provides the data types used in this ICD.

2.4.1 Unsigned short integer (U2)

Two concatenated bytes of data representing a binary number from 0 to 65535. Data is transmittedmost significant byte first (Big-Endian byte order). This data type is also commonly known as a UInt16value.

2.4.2 Unsigned long integer (U4)

Four concatenated bytes of data representing a binary number from 0 to 4294967295. The Modbus®registers are 16-bits long, which means that two Modbus® registers are required to store data of thistype. To illustrate the data packing, consider the example shown in tab. 2-6. In this case a single U4value of 0x12345678 is loaded into two 16-bit Modbus® registers. Note that the least significant wordis stored in the lower-address Modbus®, and the most significant word is stored in the higher-addressModbus® register.

As an additional point note that since the Modbus®/RTU protocol dictates that registers are transmit-ted most significant byte first, this U4 value will be transmitted in the order 0x56, 0x78, 0x12, 0x34when contained in a Modbus®/RTU packet.

This data type is also commonly known as a UInt32 value.

2.4.3 IP Address (IP4) (applicable to MEsoftstart/I Pro only)

A 4-byte IP address is packed into two consecutive 2-byte registers. An IP address of the form w.x.y.zis packed into two consecutive registers as xw and zy. An example is shown in tab. 2-7.

NOTE Signed values are also stored as UInt16 values in the Modbus® registers, with an offset and scalingapplied.

Register offset Register name Value

0x00 Counter (LS word) 0x5678

0x01 Counter (MS word) 0x1234

Tab. 2-6: Example of handling a U4 value in 16-bit Modbus® registers

Register offset Register name Value

0x00 IP address (LS word) 0xA8C0 (0xA8 = 168, 0xC0 = 192)

0x01 IP address (MS word) 0x0F00 (0x0F = 15, 0x00 = 0)

Tab. 2-7: Example of packing the IP address 192.168.0.15 in 16-bit Modbus® registers

MEsoftstart 2 - 5

Interface requirements Interaction between the TCP and RTU interfaces

2.5 Interaction between the TCP and RTU interfaces

The MEsoftstart Pro soft starter models provide both a Modbus®/TCP interface and a Modbus®/RTUinterface.

Although it is possible to do configuration changes through both interfaces this might lead to unex-pected results. If both interfaces are connected it is recommended that one be used for monitoringonly, while the other can be used for both monitoring and control.

The MEsoftstart DIN and Core models only have a Modbus®/RTU interface.

NOTE The soft starter can be simultaneously accessed through both interfaces.

2 - 6

Supported function codes (MEsoftstart/I) MEsoftstart/I Modbus® function codes and registers

3 MEsoftstart/I Modbus® function codes and registers

This chapter defines the function codes (FC) supported by the MEsoftstart/I Pro and Core models, andthe applicable registers available for each function code.

3.1 Supported function codes (MEsoftstart/I)

This platform supports the function codes given by tab. 3-1.

If the soft starter detects a Modbus® transaction with a function code that is not supported, it willrespond with exception code 0x01, indicating an illegal function has been performed.

3.2 Scaling of register values

For each Modbus® register a scaling value and offset are provided. When packing a value into a reg-ister the value to load into the register is calculated as:

– Register contents = (floor operator of )(Effective value * scaling value) + offset value

When reading a register, the effective value corresponding to what is stored in the register is calcu-lated as:

– Effective value = (register contents – offset value)/scaling value

3.3 Limits for register values

For each register an upper- and lower limit is provided. If a value outside of these limits is sent to thesoft starter the value will be rejected and the soft starter shall respond with exception code 0x03 (Ille-gal data value).

Function code Value (8-bit) Description

FC03 0x03 Read holding register

FC04 0x04 Read input register

FC06 0x06 Write single output register

FC16 0x10 Write multiple output registers

Tab. 3-1: Supported Modbus® function codes (MEsoftstart/I)

NOTE The units of measure provided in tab. 3-2 and tab. 3-3 refer to the effective values, not the valuesas stored in the Modbus® registers.

NOTE If any value within a multiple register transaction is rejected due to failing the limit checking, theentire packet will be discarded.

MEsoftstart 3 - 1

MEsoftstart/I Modbus® function codes and registers Input registers (MEsoftstart/I)

3.4 Input registers (MEsoftstart/I)

This section lists the memory map describing the input registers, (Modbus® address range 0x3xxxx).These registers support the function code FC04. The register addresses are given in tab. 3-2.

Input (0x3xxxx) registers (MEsoftstart/I Pro and Core)

Register name Description Unit Scale

factorOffset value

Validrange

Offset address

Motor run time (LS Word)

These two registers together comprise a U4 value (refer to section 2.4.2) containing the number of sec-onds that the attached motor has been running. When the motor is not running this register contains the value 0.

s 1 0 0–65535 0

Motor run time (MS Word) s 1 0 0–65535 1

Start count (LS Word) These two registers together comprise a U4 value

(refer to section 2.4.2) containing the number of starts that have been performed by the soft starter.

NA 1 0 0–65535 2

Start count (MS Word) NA 1 0 0–65535 3

Delay time remaining

After a motor has been stopped, a delay is required before it can be started again. This parameter is an unsigned integer and contains the number of seconds remaining in the current delay.

s 1 0 0–3600 4

Status

This value describes the current soft starter status. It can be one of the following values:

Value Interpretation0 The soft starter is powering up1 The soft starter is in idle mode. The attached

motor is stopped, and the soft starter is ready to perform a ramp.

2 The soft starter is busy performing a start ramp3 The soft starter has completed a start, and the

attached motor is busy running.4 The soft starter is busy performing a stop ramp5 The soft starter is in an error state following the

detection of an error condition. The cause of the error is given in the fault ID field. A reset command is required to recover from this state.

6 Delay restart state. The soft starter is process-ing a delay following the last stop in accord-ance with the allotted number of starts per hour.

7 Jog state. The soft starter is busy jogging.8 Temperature delay. The soft starter detects

that either the motor or an internal heatsink is too hot to allow a start. The soft starter will remain in this mode until all temperatures have dropped sufficiently

NA 1 0 0–8 5

Tab. 3-2: Input (0x3xxxx) registers (MEsoftstart/I Pro and Core) (1)

3 - 2

Input registers (MEsoftstart/I) MEsoftstart/I Modbus® function codes and registers

Fault ID

After the soft starter experienced an error condition and entered the error state, this value identifies the cause of the error. The possible values are:

Value Interpretation0 No error condition present1 Motor protection curve trip2 The maximum motor starting current was

exceeded during a start ramp. 3 The motor overload current (MOLC) was

exceeded. This refers to the MOLC limit that can be configured as part of the soft starter setup

4 Motor underload condition detected. This indi-cates that the motor drew less than the under-load current limit for at least 60 s. Typically indicates a pump running dry.

5 Unbalanced grid voltage detected6 Unbalanced motor voltage detected7 Excessive motor temperature detected. This

test is only applied if a motor temperature sen-sor is configured.

8 Excessive grid voltage detected9 Too low grid voltage detected

10 Soft starter control electronics temperature exceeds safe limit

11 Soft starter heat sink temperature exceeds limit

12 Over current detected on L1 phase during start ramp



15 Fault detected on SCR switching element16 Motor current imbalance detected

NA 1 0 0–28 6

17 Reserved

18 Motor start time limit exceeded19 Soft starter current limit exceeded while run-

ning

20 Reserved

21 Configured- and detected phase rotations differ22 Operating frequency limits transgressed23 Earth leakage trip detected24 Soft starter internal hardware error detected25 Soft starter sensor validation failed. The spe-

cific sensor that failed is identified in the “Failed sensors” fields.

26 Bypass relay activation error. The bypass relay did not close as expected.

27 A brownout was detected28 An error is detected with the motor and/or

power connections

Failed sensors 1 Reserved for future use NA 1 0 0–65535 7

Failed sensors 2 Reserved for future use NA 1 0 0–65535 8

Current imbalance %

This value shows the current imbalance % contained within a U2 value. No scaling is applied, i.e. a value of 50 corresponds to a current imbalance of 50%.

% 1 0 0–100 9

Grid voltage imbalance %

This value shows the input voltage imbalance % con-tained within a U2 value. No scaling is applied, i.e. a value of 50 corresponds to a grid voltage imbalance of 50%.

% 1 0 0–100 10


factorOffset value

Validrange

Offset address


MEsoftstart 3 - 3


Motor voltage imbalance %

This value shows the motor voltage imbalance % con-tained within a U2 value. No scaling is applied, i.e. a value of 50 corresponds to a motor voltage imbalance of 50%.

% 1 0 0–100 11

Power factorThis parameter contains the measured power factor (PF), represented in a U2 variable. A register value of 50 corresponds to a PF of 0.5.

NA 100 0 0–100 12

Apparent powerThis parameter contains the apparent power that is being delivered to the motor. After scaling a register value of 1000 corresponds to 100 kVA

kVA 10 0 0–25000 13

Active powerThis parameter contains the active power that is being delivered to the motor. After scaling a register value of 1000 corresponds to 100 kW

kW 10 0 0–25000 14

Reactive powerThis parameter contains the reactive power that is being delivered to the motor. After scaling a register value of 1000 corresponds to 100 kVAR

kVAR 10 0 0–25000 15

Grid frequency Detected grid frequency. A register value of 501 corre-sponds to 50.1 Hz. Hz 10 0 0–1000 16

Grid phase rotation

This value describes the phase detected on the incom-ing AC lines:- 0 = Unknown phase, i.e. no phase detected,

typically no AC present- 1 = L1-L3-L2 phase rotation detected

(anti-clockwise)- 2 = L1-L2-L3 phase rotation detected

(clockwise)

NA 1 0 0–2 17

Desired phase rotation

This value describes the phase that the soft starter expects to see on the incoming AC lines according to its configuration:- 0 = Unknown phase, i.e. no phase detected,


(anti-clockwise)- 2 = L1-L2-L3 phase rotation detected

(clockwise)

NA 1 0 0–2 18

Motor RPM

This value gives the measured motor RPM. If no RPM sensor is connected this value will return 0.

NOTEThis parameter is only available on the Pro models. On the Core models this register always contains 0.

RPM 1 0 0–4000 19

Grid voltage VRSGrid side line-to-line RMS voltage between input connections L1 and L2 V 1 0 0–1000 20

Motor voltage VUVMotor side line-to-line RMS voltage between outputs T1 and T2 V 1 0 0–1000 21

Grid voltage VSTGrid side line-to-line RMS voltage between input connections L2 and L3 V 1 0 0–1000 22

Motor voltage VVWMotor side line-to-line RMS voltage between outputs T2 and T3 V 1 0 0–1000 23

Grid voltage VTRGrid side line-to-line RMS voltage between input connections L3 and L1 V 1 0 0–1000 24

Motor voltage VWUMotor side line-to-line RMS voltage between outputs T3 and T1 V 1 0 0–1000 25

Line current R RMS current flowing in phase R (Input L1) A 10 0 0–50000 26

Line current S RMS current flowing in phase S (Input L2) A 10 0 0–50000 27

Line current T RMS current flowing in phase T (Input L3) A 10 0 0–50000 28

Line current R % of MFLC

This parameter expresses the current flowing in phase R (input L1) as a percentage of specified motor full load current (MFLC)

% 1 0 0–100 29


factorOffset value

Validrange

Offset address


3 - 4


Line current S % of MFLC

This parameter expresses the current flowing in phase S (input L2) as a percentage of specified motor full load current (MFLC)

% 1 0 0–100 30

Line current T % of MFLC

This parameter expresses the current flowing in phase T (input L3) as a percentage of specified motor full load current (MFLC)

% 1 0 0–100 31

Average phase current

The average of the three RMS currents flowing through the different phases. A 10 0 0–50000 32

Heatsink 1 temperature Temperature of heatsink 1 0C 1 0 0–150 33

Heatsink 2 temperature

Temperature of heatsink 2 (if heatsink 2 is not fitted this value will be 0) 0C 1 0 0–150 34



Internal temperature Temperature of soft starter control electronics 0C 1 0 0–150 36

Motor temperature

This parameter contains the motor temperature. Depending on the machine setup the temperature sensor can either be an LM35 sensor or a PT100 sen-sor, or the machine can have no motor temperature sensor fitted. In the case where no temperature sensor is present this value will be fixed to 0. The effective range of temperatures that can be reported are -200–250 0C.

NOTEFor the Core models the LM35 cannot be fitted

0C 1 256 56–506 37


factorOffset value

Validrange

Offset address


MEsoftstart 3 - 5


Relay status

This parameter describes the status of the output relays. The status of each relay is represented by one bit in this word, which is treated as a bitfield. A value of 1 indicates that the relay that corresponds to that bit position is closed, while a value of 0 indicates that the relay is open. The mapping of output relays to bit positions for the Pro models is:

(Refer to the manual for a description of the function of each relay)For the Core models the mapping looks as follows:

(Refer to the manual for a description of the function of each relay)

NA 1 0 0–0x3FF 38

Reserved Reserved for future use NA 1 0 0 39








factorOffset value

Validrange

Offset address


Bit position Relay description

0 Fan relay – This output controls the fans inside the soft starter

1 Run relay

2 Shunt trip relay

3 Ready relay

4

Trigger card inhibit relay –This is an internal soft starter signal. When activated the firing circuits for the switching elements are disabled.

5 Over alarm relay

6 Fault/incoming alarm relay

7 Temperature fault relay

8 Bypass contactor relay

9 Reversing contactor relay

10–15 Reserved (will be set to 0)

Bit position Relay description

0 Fan relay

1 Run/Bypass relay

2 Reserved (will be set to 0)

3 Ready relay

4 Trigger card inhibit relay


6 Fault relay


8

Bypass contactor relay (only relevant if an internal bypass is present, in which case the Run/Bypass relay becomes a Run relay only)

9–15 Reserved (will be set to 0)

3 - 6


Alpha firing angle %

This parameter contains the percentage SCR firing angle, where 0% corresponds to the switching ele-ments being completely off and 100% corresponds to the switching elements being on all the time. During a ramp up this value will go from 0 to 100% (i.e. from 0 to 100000) as the percentage of the total voltage applied to the motor increases.

% 100 0 0–10000 43

Graph ramp time

During a ramp up or down this parameter contains the time that has elapsed since the start of the ramp. The time is given as a number of 40 ms intervals, i.e. a value of 1 corresponds to 40 ms elapsed and a value of 250 corresponds to 10000 ms elapsed (= 10 s elapsed).

s 25 0 0–25000 44

Reserved Reserved for future use NA 1 0 0–65535 45–62

Monitor control status

This parameter indicates which control interfaces are connected, and what functions are currently allowed via each connected interface. The word is divided into groups of 2 bits, with each group corresponding to a different interface as shown below:

NOTEFor the Core models the TCP interface is not available. Its status will always be reported as “Interface not con-nected”

NA 1 0 0–0x3FF 63

Reserved Reserved for future use NA 1 0 0–65535 64

Configuration write info

This register contains feedback about the last configu-ration write transaction. If the write failed due to a compliance error, this register contains the Modbus® register address of the value that violated the compli-ance rules. If the last write was successful, this register contains 0xFFFF

NA 1 0 0–65535 65

Earth leakage current

This value contains the peak earth leakage current that flowed during the last grid phase period. A 100 0 0–10000 66


factorOffset value

Validrange

Offset address


Bits Description

0–1

Modbus®/ TCP interface:0 = Interface not connected1 = Interface connected. Monitor only2 = Interface connected. Monitor and

configure3 = Interface connected. Monitor, config-

ure and control

2–3

Modbus®/RTU interface:0 = Interface not connected1 = Interface connected. Monitor only2 = Interface connected. Monitor and

configure3 = Interface connected. Monitor, config-

ure and control

4–5 Reserved

6–7

Remote start interface:This interface consists of the remote start line only, and as such is always present.1 = Cannot start via remote start line3 = Starting allowed via remote start line

8–15 Reserved

MEsoftstart 3 - 7

MEsoftstart/I Modbus® function codes and registers Holding registers (MEsoftstart/I)

3.5 Holding registers (MEsoftstart/I)

This section lists the memory map describing the holding registers, (Modbus® address range0x4xxxx). These registers support the function codes FC03, FC06 and FC16.

The holding registers for the Core and Pro models differ substantially. The main reason for this is thatall configuration settings that are influenced by the Pot HMI settings on the Core models are not set-table through the Modbus® interface. In the case of the Pro models all configuration parameters canbe adjusted through the Modbus® interface. The register addresses are given in tab. 3-3 (for the Promodel) and tab. 3-4 (showing deviations for the core model) . The control parameters are described inmore detail in section 5 of document 1) in section section 1.5.2.

Holding (0x4xxxx) registers for the MEsoftstart/I Pro model

NOTE This section only describes the holding register memory map. Refer to the manual for a descrip-tion of the meaning of each parameter and how the soft starter should be configured for thedesired behaviour.

Register name Description Unit Scale factor

Offset value Valid range Default Offset

address

Start type and inside delta con-nection

This parameter selects the start type, as well as the motor connection type, i.e. inside delta or not. The 16-bit word is interpreted as follows:

NA 1 0

Bits 0–7:0–1Bits 8–15:1–4

0x100 0

Kickstart %

If the start type is set to ‘kickstart’ this parameter sets the voltage % during the kick period as a % of nominal voltage. If a different start type is selected this param-eter is not used.

% 1 0 40–100 60 1

Kickstart period

If the start type is set to ‘kickstart’ this parameter defines the duration of the kick, in increments of 200 ms. That means that a value of 5 corresponds to a kickstart period of 1s. The valid range of 1–10 corre-sponds to an effective range of 0.2 s–2 s. If a different start type is selected this parameter is not used.

s 0.2 0 1–10 1 2

Pedestal ramp up %

If the start type is set to ‘pedestal’ this parameter sets the firing angle % during the pedestal period. If a dif-ferent start type is selected this parameter is not used.

% 1 0 5–60 20 3

Ramp up time

For all start types this parameter sets the period over which the ramp takes place.

NOTEThe start can run as long as ‘maximum starting time’ should current limiting occur during the ramp.

s 1 0

‘Normal duty’ selected:10–30‘Heavy duty’ selected:10–60

10 4

Tab. 3-3: Holding (0x4xxxx) registers for the MEsoftstart/I Pro model (1)

Bits Description

0–7Motor connection:0 = Normal connection, not inside delta1 = Inside delta connection

8–15

Start type:1 = Normal start ramp profile2 = Kickstart ramp profile3 = Pedestal ramp profile4 = Constant current ramp profile

...

3 - 8

Holding registers (MEsoftstart/I) MEsoftstart/I Modbus® function codes and registers

Maximum starting time

This time represents the maximum possible time that the motor could start in, which includes current lim-ited delays incurred during the motor starting phase.

NOTEThis parameter must always be set equal to or larger than the “Ramp up time”.

s 1 0


60 5

Constant current %

If the start type is set to “Constant current” this param-eter sets the control current level as a percentage of motor rated current. If a different start type is selected this parameter is not used.Refer to the MSC% description for an explanation on how the upper limit is calculated.

% 1 0150 – Max for motor and frame

150 6

Stop type

This parameter selects the stop type as follows:1 = Coasting stop2 = Standard ramp down profile3 = Pedestal stop profile

NA 1 0 1–3 1 7

Pedestal ramp down %

If the stop type is set to ‘pedestal’ this parameter sets the firing angle % during the pedestal period. If a dif-ferent stop type is selected this parameter is not used.

% 1 0(Ramp stop angle %) –60

50 8

Ramp down time For all stop types except ‘coasting’ this parameter sets the period over which the ramp takes place s 1 0 10–30 10 9

Reserved Reserved for future use NA 1 0 0–65535 0 10



Motor size kW

This parameter specifies the power rating of the motor to be started. The register value corresponds to the power rating (kW) x 10, i.e. a register value of 75 corresponds to a 7.5 kW motor.

NOTES● This value can only be set to one of the standard

motor sizes, as listed in the table below:

● The range of motor values that can be selected depends on the soft starter frame size, the selected workload (‘heavy’ or ‘normal’), the nominal voltage and the selected connection type (‘normal’ or ‘inside delta’). This is described in the user manual.

● The motor rated current must be set independently of the motor power rating, and is not calculated from the motor power rating. For protection- and control functions the rated current is used instead of the motor power rating.

kW 10 0 Refer to manual 75 13



address


3 kW 4 kW 5.5 kW

7.5 kW 11 kW 15 kW

18.5 kW 22 kW 30 kW

37 kW 45 kW 55 kW

75 kW 90 kW 110 kW

132 kW 160 kW 200 kW

250 kW 315 kW 355 kW

400 kW 450 kW 500 kW

560 kW 630 kW 710 kW

800 kW 900 kW 1000 kW

1120 kW 1400 kW 1500 kW

MEsoftstart 3 - 9


Maximum starting current (MSC) %

This parameter sets the maximum current that is allowed during a start as a percentage of the motor full load current (MFLC).

NOTEThe range of this parameter is dependent on the soft starter frame size and the configured MFLC. This value must be set such that the maximum allowed starting current remains below the limit for the soft starter frame size in the selected operating mode (‘heavy’ or ‘normal’).Example: For the MEsoftstart/I01, in ‘heavy’ mode, connected to a motor with MFLC of 110A, the maxi-mum MSC% value is 227.

% 1 0100 – Max for motor and frame

300 14

Motor under load current (MULC) %

This parameter sets the MULC % that defines the run-ning current level below which a MULC trip will occur. This parameter specifies the trip level as a percentage of the MFLC. Setting this value to 0 disables the MULC trip condition.

% 1 0 0–100 10 15

Motor over load current (MOLC) %

This parameter sets the MOLC % that defines the run-ning current level above which a MOLC trip will occur. This parameter specifies the trip level as a percentage of the MFLC. This parameter provides the ability to restrict the allowed current flow through the motor in addition to the motor thermal protection curve implementation, which always runs.

% 1 0 100–MSC% 110 16

Maximum starts per hour

This parameter sets the delay that will be enforced fol-lowing a stop in order to protect the soft starter from over-heating due to excessive starts.

Starts/Hour 1 0


10 17

Nominal grid voltage

This parameter sets the expected nominal grid volt-age level. This value can only be set to either 400 V, 525 V or 690 V.

V 1 0 400, 525 or 690 400 18

Phase rotation

This parameter sets the desired phase rotation direc-tion as follows:0 = Unknown/Undefined1 = Anti-Clockwise (L1-L3-L2)2 = Clockwise (L1-L2-L3)

NA 1 0 0–2 2 19

Maximum voltage imbalance %

This parameter defines the maximum percentage voltage imbalance that is acceptable both on the input voltages and the motor voltages. The imbalance is calculated by expressing the difference between the highest and lowest of the three phase values as a per-centage of the lowest value.

NOTEDuring a start or stop this limit is temporarily increased

% 1 0 15–25 20 20

Maximum current imbalance %

This parameter defines the maximum percentage cur-rent imbalance that is acceptable between the cur-rents measured in the three phases. The imbalance is calculated by expressing the difference between the highest and lowest of the three phase values as a per-centage of the lowest value.


% 1 0 5–20 10 21



address


3 - 10


Ramp type

This parameter specifies the ramp type as follows:1 = Linear firing angle vs time2 = Linear RMS motor voltage vs time3 = S-curveThis selection is applied both to the start ramp and stop ramp (if selected)This parameter is ignored when the start type is “Con-stant current”

NA 1 0 1–3 1 22

RPM sensor presence

This parameter specifies whether there is an RPM sen-sor connected to the soft starter or not, as follows:0 = No RPM sensor present1 = RPM sensor connected

NA 1 0 0–1 0 23

Ramp start angle %

This parameter sets the firing angle % at which any ramp will commence. % 1 0 0–35 15 24

Protection classThis parameter can take a value of 2, 5, 10, 20 or 30, and represents the tripping class for motor overload protection.

NA 1 0 2, 5, 10, 20, 30 10 25

Heatsink fan control

This parameter sets whether the fan control is linked to the motor state or to soft starter temperature. The meaning of the contents of this register is as follows:0 = The soft starter fan is switched on whenever the soft starter is starting, stopping or running, irrespec-tive of soft starter temperatures1 = The soft starter fan is controlled based on the tem-peratures of the internal heatsinks

NA 1 0 0–1 0 26

Heatsink fan start temperature

This parameter sets the temperature above which the soft starter fan will be on. This parameter is only used when the fan control is set to be linked to tempera-ture.

0C 1 0 30–55 55 27

Heatsink restart temperature

This parameter sets the heatsink temperature below which the soft starter will be allowed to perform a start. If the restart time delay has expired and the heatsink is above this temperature the soft starter will enter the ‘temperature delay’ state. No further starts will be allowed until the soft starter has cooled down sufficiently.

0C 1 0 40–60 60 28

Maximum motor temperature

This parameter specifies the maximum temperature at which the motor may operate, as specified in the sup-plier datasheet. If this temperature is exceeded the soft starter will trip.The range of allotted temperatures depends on the type of temperature sensor that is used (either an LM35 or a PT100).

NOTEWhen no temperature sensor is selected this value is not used.

0C 1 0

PT100 selected: 90 – 175LM35 selected:90 – 115

115 29

Reserved Reserved for future use NA 1 0 0 0 30

Realtime clock (RTC) year month

This register is part of a set of registers that is used to set the current time on the soft starter. The least sig-nificant byte of this register contains the years since 2000 and the most significant byte contains the cur-rent month, i.e. writing a value of 0x0413 sets the month and year to April 2019.

NOTEThe contents of this register are not updated as time elapses on the soft starter. Reading this register returns the last value that was written to it.

NA 1 0

Year (LS byte):18–255Month (MS byte):1–12

0x0112 31



address


MEsoftstart 3 - 11


RTC day hour

This register is part of a set of registers that is used to set the current time on the soft starter. The least sig-nificant byte of this register contains the day of the month and the most significant byte contains the cur-rent hour, i.e. writing a value of 0x0010 sets the hour to 00 on the 16th day of the month.

NOTES● The limit check for the day of the month depends

on the year and month that are set and considers leap years.

● The contents of this register are not updated as time elapses on the soft starter. Reading this regis-ter returns the last value that was written to it.

NA 1 0

Day (LS byte):1 – Max days in monthHour (MS byte):0–23

0x0C01 32

RTC minute second

This register is part of a set of registers that is used to set the current time on the soft starter. The least sig-nificant byte of this register contains the current min-ute and the most significant byte contains the current second, i.e. writing a value of 0x1E0F sets the minutes to 15 and the seconds to 30.


NA 1 0

Minute (LS byte):0–59Second (MS byte):0–59

0x001E 33

User language

This parameter selects the language for the soft starter TFT. The current language options are:0 = English1 = AfrikaansAfter changing the language, it might be necessary to switch pages on the TFT for the display to reflect the new language.

NA 1 0 0–1 0 34

Motor name 1–2 These registers together contain an ASCII string that defines a name for a soft starter/motor. For the first register the least significant byte is character 1, and the most significant byte is character 2. For the next register, the least significant byte is character 3, and the most significant byte is character 4. This pattern continues for all the registers. As an example, consider the values shown in the ‘default value’ column. The default string is ‘motor 1’.A byte value of 0 indicates the string termination.

A maximum of 11 characters can be used. The 12th character will be overwritten with a string termination character.

NA 1 0

Each byte:32–122 (any ASCII char-acter from ‘space’ to ‘z’) or 0 (end of string)

0x6F4D‘oM’ 35

Motor name 3–4 NA 1 0 0x6F74 ‘ot’ 36

Motor name 5–6 NA 1 0 0x2072‘ r’ 37

Motor name 7–8 NA 1 0 0x0031‘ 1’ 38

Motor name 9–10 NA 1 0 0x0 39




Jog motor voltage %

This parameter defines the percentage of nominal voltage that is applied to a motor when the ‘jog func-tion’ is activated.A value of 0 disables the jog functionality

% 1 0To operate:15–800 to disable

0 43

Workload normal/heavy

This parameter specifies whether the soft starter will be used for a normal duty or heavy-duty application. Set this register as follows:0 = Normal duty1 = Heavy duty

NOTES● Changing this parameter affects the valid ranges of

several other parameters. If an attempt to change this register causes other registers to become inva-lid the write operation will fail.

● Refer to the user manual for more details.

NA 1 0 0–1 0 44



address


3 - 12


Bypass contactor

This register indicates to the system whether a bypass contactor is present or not. This register is interpreted as follows:0 = No bypass contactor1 = Bypass contactor is present

NOTEIrrespective of the setting of this value the soft starter will drive the appropriate relay to attempt to activate the “Bypass contactor”. However, if this option is set to ‘no bypass contactor’ the soft starter will continue to fire the switching elements as long as the motor is running.

NA 1 0 0–1 0 45

Motor restart temperature

This parameter sets the motor temperature below which the soft starter will be allowed to perform a start. If the restart time delay has expired and the motor is above this temperature the soft starter will enter the ‘temperature delay’ state. No further starts will be allowed until the soft starter has cooled down sufficiently.

NOTEIf no motor temperature sensor is present this register is disregarded.

0C 1 0 40–80 65 46

Soft starter model

This register shows the model of the connected soft starter as follows:0 = MEsoftstart/I00 (100 A)1 = MEsoftstart/I01 (200 A)2 = MEsoftstart/I02 (390 A)3 = MEsoftstart/I03 (600 A)4 = MEsoftstart/I04 (900 A)

NOTEThis parameter is read only. Writes to this register will be ignored.

NA 1 0

0–4 for reads. Written val-ues will be discarded.

NA 47

Main CPU firm-ware revision

This register contains the revision of the firmware that is running on the main CPU. The major- and minor revisions are stored as follows:Most significant byte = Major revisionLeast significant byte = Minor revision


NA 1 0

MS byte: 0–255LS byte: 0–255

NA 48

RMS CPU firm-ware revision

This register contains the revision of the firmware that is running on the RMS CPU. The major- and minor revi-sions are stored as follows:Most significant byte = Major revisionLeast significant byte = Minor revision


NA 1 0


NA 49

Serial number

This register returns the serial number for the attached soft starter.


NA 1 0 0–65535 NA 50



address


MEsoftstart 3 - 13


New password [1–4]

These two registers are accessed to change the 6-digit password. The password can be set to any value from 1–999999. The new password is written to these regis-ters in BCD format. If the password is to be set to 123456 the first register is written as 0x3412 and the second register is written as 0xFF56.

NOTES● The 0xFF value in the MS byte of the second register

is a password confirmation flag. If this byte contains any other value the password write will be ignored.

● If the password is shorter than 6 digits leading zeros are appended. As an example, if the password must be set to 123, the first register is written as 0x0100 and the second register as 0xFF23.

● The password change is confirmed by writing the current password to the password registers. If the old password is not written to the password regis-ters the password change will be rejected.

● Keep the password set to 0 to disable password checks.

● Reads from these registers always return 0.

NA 1 0 Each nibble can be 0–9 0 51

New password [5–6] NA 1 0

Both nib-bles of LS byte: 0–9MS byte: 0–255

0 52



Fault/incoming CB

The value of this register defines the function of the fault/incoming CB relay as follows:0 = The relay is configured as the fault relay1 = The relay is configured as the incoming CB relay

NA 1 0 0–1 0 55

Motor tempera-ture selection

This parameter specifies the type of motor tempera-ture sensor that is connected to the soft starter. The following options are supported:0 = LM35 temperature sensor1 = PT100 temperature sensor2 = No motor temperature sensor connected

NA 1 0 0–2 2 56

Ramp stop angle %

This parameter defines the firing angle percentage to which the soft starter will ramp down for any stop type other than ‘Coasting’.

% 1 0 15–60 15 57

Rated current

This register must be set to the nameplate rated cur-rent for the attached motor. This is the value that is used for soft starter control and trip detection.

NOTEThis value is not updated automatically if the “Motor size kW” parameter is changed. This parameter must be updated separately.

A 1 0 10–2700

As for default motor, at 0.8 PF

58

Soft starter IP(LS word) These two registers set the IP address of the soft

starter for use on the Modbus®/TCP interface. Refer to section 2.4.3 for a description of the byte packing

NA 1 0 0–65535 0xA8C0 59

Soft starter IP (MS word) NA 1 0 0–65535 0x0F00 60

IP subnet mask (LS word) These two registers set the subnet mask used by the

soft starter on the Modbus®/TCP interface. Refer to section 2.4.3 for a description of the byte packing

NA 1 0 0–65535 0xFFFF 61

IP subnet mask (MS word) NA 1 0 0–65535 0x00FF 62









address


3 - 14


UART configura-tion register

This parameter allows changes to the UART configura-tion of the soft starter, including the baud rate, parity and slave address. The 16-bit register is used as fol-lows:- bits 7–0: Modbus® slave address, 1–247 - bits 11–8: Defines the selected parity as follows:

● 0 = No parity● 1 = Even parity● 2 = Odd parity

- bits 15–12: Sets the baud rate as follows:● 0 = 9600 baud● 1 = 14400 baud● 2 = 19200 baud● 3 = 28800 baud● 4 = 38400 baud● 5 = 57600 baud● 6 = 115200 baud

NA 1 0

Only the ranges listed in the description will be accepted for each part of the word

0x6101 69

Unlock register

This parameter must be set to a specific value to allow the UART configuration register and/or IP address reg-ister values to be changed. If it is not set to 0xACDC, the aforementioned parameters will not be changed. A read from this register always return 0.

NA 1 0 0–65535 0 70

Control command

This register is used to provide commands to the soft starter:0 = No change1 = Start the motor2 = Stop the motor3 = Reset the soft starter to clear an error condition4 = Enter jog mode

NOTEReads from this register always return 0.

NA 1 0 0–4 0 71

Password [1–4]

These two registers are written to confirm the current password. The password can be any value from 1–999999. The new password is written to these regis-ters in BCD format. If the password is 123456 the first register is written as 0x3412 and the second register is written as 0x0056.If the password is shorter than 6 digits leading zeros are appended. As an example, if the password is 123, the first register is written as 0x0100 and the second register as 0x0023.

NOTES● Even if the password is set to 0 (password checking

disabled) a write is required to the password regis-ters to complete a write transaction. In this case any value can be written to these registers.

● Reads from these registers always return 0.

NA 1 0 Each nibble can be 0–9 0 72

Password [5–6] NA 1 0

Both nib-bles of LS byte: 0–9MS byte: 0

0 73

Modbus® IF command

Writes to this register pass commands concerning the handling of the Modbus® interface to the soft starter. The following commands are defined:0 = No change1 = Reset the temporary Modbus® register values to defaultsMore detail will be given about this operation in sec-tions to follow.

NOTES● This register is the only register that can be

accessed on its own, with no password protection. ● Any write transaction of which the address range

includes this register position, will be treated as a write to this register only. Any other register writes in the same multi-word Modbus® write will be ignored.

74



address


MEsoftstart 3 - 15


Holding (0x4xxxx) registers for the MEsoftstart/I Core model

NOTE Only registers that differ from the Pro model are shown in detail. These registers are highlighted ingreen.


Offset value

Valid range Default Offset

address

Start type and inside delta con-nection

This register is read only. All writes to this address will be ignored. This parameter contains the start type, as well as the motor connection type, i.e. inside delta or not. The 16-bit word is interpreted as follows:

NA 1 0 256–257 NA 0

Reserved Not applicable to Core model. Writes are ignored, reads return 0 NA 1 0 0–65535 0 1



Ramp up timeThis parameter is set via the Pot HMI and cannot be changed through the Modbus® interface. This register is read only. All writes to this address will be ignored.

s 1 0 5–30 NA 4

Maximum starting time

This time represents the maximum possible time that the motor could start in, which includes current lim-ited delays incurred during the motor starting phase.

NOTEThis parameter must always be set equal to or larger than the “Ramp up time”.

s 1 0


60 5


Stop type

This register is read only. All writes to this address will be ignored. This parameter describes the selected stop type as follows:2 = Standard ramp down profile

NOTEIf the “Ramp down time” is set to 0 this is equivalent to a coasting stop.

NA 1 0 2 2 7


Ramp down time

This register is read only. All writes to this address will be ignored. This parameter contains the period over which the ramp down takes place as set by the Pot HMI. A 0s ramp down is equivalent to a coasting stop.

s 1 0 0–30 NA 9




Tab. 3-4: Holding (0x4xxxx) registers for the MEsoftstart/I Core model (1)

Bits Description

0–7Motor connection:0 = Normal connection, not inside delta1 = Inside delta connection

8–15Start type:1 = Normal start ramp profile

...

3 - 16


Motor size kW

This register is read only. The value is determined by the Pot HMI settings. All writes to this address will be ignored.This register specifies the selected motor power rat-ing. The register value corresponds to the power rat-ing (kW) x 10, i.e. a register value of 75 corresponds to a 7.5 kW motor.

NOTES● This value can only be set to one of the standard

motor sizes, as listed in the table below:

(This list of motor sizes assumes that the Core models will only be 100A or 200A frame sizes.)● Also note that the range of motor values that can

be selected depends on the soft starter frame size, the selected workload (‘Heavy’ or ‘Normal’), the nominal voltage and the selected connection type (‘Normal’ or ‘Inside delta’). This is described in the user manual.

● For protection- and control functions the rated cur-rent is used instead of the motor power rating.

kW 10 0 Refer to manual NA 13

Maximum starting current (MSC) %

This register is read only. The value is determined by the Pot HMI settings. All writes to this address will be ignored. This parameter contains the selected maximum cur-rent that is allowed during a start as a percentage of the motor full load current (MFLC).

% 1 0 100–700 NA 14

Motor under load current (MULC) %

This parameter sets the MULC % that defines the run-ning current level below which a MULC trip will occur. This parameter specifies the trip level as a percentage of the MFLC.Setting this value to 0 disables the MULC trip condition.

% 1 0 0–100 10 15

Motor over load current (MOLC) %

This parameter sets the MOLC % that defines the run-ning current level above which a MOLC trip will occur. This parameter specifies the trip level as a percentage of the MFLC. This parameter provides the ability to restrict the allowed current flow through the motor in addition to the motor thermal protection curve implementation, which always runs.

% 1 0 100–MSC% 110 16

Maximum starts per hour

This parameter sets the delay that will be enforced fol-lowing a stop in order to protect the soft starter from over-heating due to excessive starts.

Starts/ Hour 1 0


‘Normal duty’: 10‘Heavy duty’: 60

17

Nominal grid voltage

This parameter sets the expected nominal grid volt-age level. This value can only be set to either 400 V, 525 V or 690 V.

V 1 0 400, 525 or 690 400 18

Phase rotation

This parameter sets the desired phase rotation direc-tion as follows:0 = Unknown/Undefined1 = Anti-Clockwise (L1-L3-L2)2 = Clockwise (L1-L2-L3)

NA 1 0 0–2 2 19


Offset value


address


3 kW 4 kW 5.5 kW

7.5 kW 11 kW 15 kW

18.5 kW 22 kW 30 kW

37 kW 45 kW 55 kW

75 kW 90 kW 110 kW

132 kW 160 kW 200 kW

250 kW 315 kW

MEsoftstart 3 - 17


Maximum voltage imbalance %

This parameter defines the maximum percentage voltage imbalance that is acceptable both on the input voltages and the motor voltages. The imbalance is calculated by expressing the difference between the highest and lowest of the three phase values as a per-centage of the lowest value.


% 1 0 15–25 20 20

Maximum current imbalance %

This parameter defines the maximum percentage cur-rent imbalance that is acceptable between the cur-rents measured in the three phases. The imbalance is calculated by expressing the difference between the highest and lowest of the three phase values as a per-centage of the lowest value.


% 1 0 5–20 10 21

Ramp type

This register is read only. All writes to this address will be ignored. This parameter describes the selected ramp type as follows:1 = Linear firing angle vs timeThis selection is applied both to the start ramp and stop ramp (if selected)

NA 1 0 1 1 22


Ramp start angle %

This register is read only. The value is determined by the Pot HMI settings. All writes to this address will be ignored. This parameter contains the firing angle % at which a start ramp will commence.

% 1 0 15–60 NA 24

Protection classThis parameter can take a value of 2, 5, 10, 20 or 30, and represents the tripping class for motor overload protection.

NA 1 0 2, 5, 10, 20, 30 10 25

Heatsink fan control

This parameter sets whether the fan control is linked to the motor state or to soft starter temperature. The meaning of the contents of this register is as follows:0 = The soft starter fan is switched in whenever the soft starter is starting, stopping or running, irrespec-tive of soft starter temperatures1 = The soft starter fan is controlled based on the tem-peratures of the internal heatsinks

NA 1 0 0–1 0 26

Heatsink fan start temperature

This parameter sets the temperature above which the soft starter fan will be on. This parameter is only used when the fan control is set to be linked to temperature.

0C 1 0 30–55 55 27

Heatsink restart temperature

This parameter sets the heatsink temperature below which the soft starter will be allowed to perform a start. If the restart time delay has expired and the heatsink is above this temperature the soft starter will enter the ‘temperature delay’ state. No further starts will be allowed until the soft starter has cooled down sufficiently.

0C 1 0 40–60 60 28

Maximum motor temperature

This parameter specifies the maximum temperature at which the motor may operate, as specified in the sup-plier datasheet. If this temperature is exceeded the soft starter will trip. For the Core models only a PT100 temperature sensor can be connected

NOTEWhen no temperature sensor is selected this value is not used.

0C 1 0 90–175 115 29



Offset value


address


3 - 18


Realtime clock (RTC) year month

This register is part of a set of registers that is used to set the current time on the soft starter. The least sig-nificant byte of this register contains the years since 2000 and the most significant byte contains the cur-rent month, i.e. writing a value of 0x0413 sets the month and year to April 2019.


NA 1 0

Year (LS byte):18–255Month (MS byte):1–12

0x0112 31

RTC day hour

This register is part of a set of registers that is used to set the current time on the soft starter. The least sig-nificant byte of this register contains the day of the month and the most significant byte contains the cur-rent hour, i.e. writing a value of 0x0010 sets the hour to 00 on the 16th day of the month.

NOTES● The limit check for the day of the month depends

on the year and month that are set and considers leap years.

● The contents of this register are not updated as time elapses on the soft starter. Reading this regis-ter returns the last value that was written to it.

NA 1 0

Day (LS byte):1 – Max days in monthHour (MS byte):0–23

0x0C01 32

RTC minute second

This register is part of a set of registers that is used to set the current time on the soft starter. The least sig-nificant byte of this register contains the current min-ute and the most significant byte contains the current second, i.e. writing a value of 0x1E0F sets the minutes to 15 and the seconds to 30.


NA 1 0

Minute (LS byte):0–59Second (MS byte):0–59

0x001E 33

User language

This parameter selects the language for the soft starter TFT. The current language options are:0 = English1 = AfrikaansAfter changing the language, it might be necessary to switch pages on the TFT for the display to reflect the new language.

NA 1 0 0–1 0 34

Motor name 1–2 These registers together contain an ASCII string that defines a name for a soft starter/motor. For the first register the least significant byte is character 1, and the most significant byte is character 2. For the next register, the least significant byte is character 3, and the most significant byte is character 4. This pattern continues for all the registers. As an example, consider the values shown in the ‘default value’ column. The default string is ‘motor 1’.A byte value of 0 indicates the string termination.

A maximum of 11 characters can be used. The 12th character will be overwritten with a string termination character.

NA 1 0

Each byte:32–122 (any ASCII character from ‘space’ to ‘z’) or 0 (end of string)

0x6F4D‘oM’ 35

Motor name 3–4 NA 1 0 0x6F74‘ot’ 36

Motor name 5–6 NA 1 0 0x2072‘ r’ 37

Motor name 7–8 NA 1 0 0x0031‘ 1’ 38





Jog motor voltage %

This register is read only. The value is determined by the Pot HMI settings and is applicable when JOG is selected on the DIP switch on the HMI. All writes to this address will be ignored. This parameter defines the percentage of nominal voltage that is applied to a motor when the Jog func-tion is activated. A value of 0 indicates that the jog functionality is disa-bled.

% 1 015–80, 0 when disabled

NA 43


Offset value


address


MEsoftstart 3 - 19


Workload normal/heavy

This register is read only. The value is determined by the Pot HMI settings. All writes to this address will be ignored. This parameter specifies whether the soft starter will be used for a normal duty or heavy-duty application as follows:0 = Normal duty1 = Heavy duty

NA 1 0 0–1 NA 44

Bypass contactor

This register is read only. The value is determined by the Pot HMI settings. All writes to this address will be ignored. This register indicates whether a bypass contactor is present or not. This register is interpreted as follows:0 = No bypass contactor1 = Bypass contactor is present

NA 1 0 0–1 NA 45

Motor restart temperature

This parameter sets the motor temperature below which the soft starter will be allowed to perform a start. If the restart time delay has expired and the motor is above this temperature the soft starter will enter the ‘temperature delay’ state. No further starts will be allowed until the soft starter has cooled down sufficiently.

NOTEIf no motor temperature sensor is present this register is disregarded.

0C 1 0 40–80 65 46

Soft starter model

This register shows the model of the connected soft starter as follows:0 = MEsoftstart/I00 (100 A)1 = MEsoftstart/I01 (200 A)


NA 1 0 0–1 NA 47

Main CPU firm-ware revision

This register contains the revision of the firmware that is running on the main CPU. The major- and minor revisions are stored as follows:Most significant byte = Major revisionLeast significant byte = Minor revision


NA 1 0


NA 48

RMS CPU firm-ware revision

This register contains the revision of the firmware that is running on the RMS CPU. The major- and minor revi-sions are stored as follows:Most significant byte = Major revisionLeast significant byte = Minor revision


NA 1 0

MS byte: 0–255LS byte:0–255

NA 49

Serial number

This register returns the serial number for the attached soft starter.


NA 1 0 0–65535 NA 50







Offset value


address


3 - 20


Motor tempera-ture selection

This parameter specifies the type of motor tempera-ture sensor that is connected to the soft starter. The following options are supported:1 = PT100 temperature sensor2 = No motor temperature sensor connected

NA 1 0 1–2 2 56

Ramp stop angle %

This register is read only. The value is determined by the Pot HMI settings. All writes to this address will be ignored. This parameter contains the firing angle percentage to which the soft starter will ramp down.

% 1 0 15–60 NA 57

Rated current

This register is read only. The value is determined by the Pot HMI settings. All writes to this address will be ignored. This register returns the motor rated current as set on the Pot HMI board. This value should be set to the nameplate rated current for the attached motor. This is the value that is used for soft starter control and trip detection.

A 1 0

10% to 100% of soft starter running current. For the I00 model:10–100

NA 58















NA 1 0

Only the ranges listed in the descrip-tion will be accepted for each part of the word

0x6101 69

Unlock register

This parameter must be set to a specific value to allow the UART configuration register and/or IP address reg-ister values to be changed. If it is not set to 0xACDC, the aforementioned parameters will not be changed. A read from this register always return 0.

NA 1 0 0–65535 0 70


Offset value


address


MEsoftstart 3 - 21


Control command

This register is used to provide commands to the soft starter: 0 = No change1 = Start the motor2 = Stop the motor3 = Reset the soft starter to clear an error condition

NOTEReads from this register always return 0.

NA 1 0 0–4 0 71


Write confirma-tion register

Any write to this register completes a write transac-tion. All the preceding writes which were placed in the shadow register set on the soft starter will now be evaluated for validity, and then used.Reads from this address always return 0.

NA 1 0 0–65535 0 73

Modbus® IF command

Writes to this register pass commands concerning the handling of the Modbus® interface to the soft starter. The following commands are defined:0 = No change1 = Reset the temporary Modbus® register values to defaultsMore detail will be given about this operation in sec-tions to follow.

NOTES● This register is the only register that can be

accessed on its own, with no password protection.● Any write transaction of which the address

range includes this register position, will be treated as a write to this register only. Any other register writes in the same multi-word Modbus® write will be ignored.

74


Offset value


address


3 - 22


3.5.1 Shadow holding registers

Internal to the Modbus® interfaces there are two sets of holding registers:

● The active registers: these registers contain the latest validated set of configuration parameters.These are the values that are used by the soft starter. Modbus® read transactions return the valuesfrom the active registers.

● The shadow registers: these registers contain configuration values that have not yet been finalisedby a user. The shadow register contents are transferred to the active registers on completion of aconfiguration write sequence (refer to section 3.5.2), if the limit and configuration consistencychecks pass. Note that no limit checking or configuration consistency checking is performed ondata written to these registers prior to completion of a configuration write sequence.

After power-up, and on completion of a configuration write sequence the shadow registers are ini-tialised with the current validated values. Their contents can then be modified through single- or mul-tiple register write transactions.

Shadow_Active Registers

Fig. 3-1: Shadow registers and active registers

Modbus®Writes

Modbus®Reads

Values transferred oncompletion of configuration

write sequence

Active registers

Shadow registers

MEsoftstart 3 - 23


3.5.2 Completing a configuration write sequence

A single configuration write sequence can consist of any combination of single- and multiple holdingregister write operations. The configuration write sequence is completed in one of three ways:

● For the Pro models the sequence can be completed by writing a password to the passwordregisters (or 0 if password checking is disabled). For the Core models the sequence is completedby writing any value to the write confirmation register.

● Doing a command write sequence.

● Writing to the Modbus® IF command register

These operations are explained in the following sections.

Writing a password to the password registers

Writing to the password registers indicates that a configuration write sequence is complete. At thispoint the shadow holding register values are subjected to limit checking and configuration consist-ency checking (this includes password checking, if password validation is active). If the checks pass,the contents of the shadow holding registers are transferred to the active holding registers and thesevalues become the new validated configuration. If the checks fail, the active holding registers remainunchanged and the contents of the shadow holding registers are reset to contain the values in theactive holding registers.

A new configuration can be loaded through a number of separate single- or multiple register writesfollowed by a write to the password registers, or as a single multi-register write operation covering theentire holding register range up to and including the password registers. When using multiple writeoperations, the overall configuration could be in an inconsistent state at different stages during thewrite without resulting in the configuration being rejected. Limit checks and configuration consist-ency checks are only performed after a write to the password register.

NOTES – In the case of the Core models, password protection is not implemented. The same discussionapplies, except that the write sequence is completed by a transaction that accesses the writeconfirmation register.

– The contents of the control command register will be ignored for writes of this nature.

3 - 24


Doing a command write sequence

To issue a command to the soft starter, a 3-register multiple register write transaction must be used toaccess only register addresses 71–73. These three registers are the control command register and thepassword registers. Only if a valid command and correct password are received will the command beissued.

This is the only write sequence that can be used to issue a command to the soft starter. For other writeoperations the contents of the control command register are ignored.

Consider the scenario where a start command (0x01) is to be written to a soft starter via theModbus®/RTU interface. The Modbus® slave address of the soft starter is 1. A multiple register writetransaction (FC 0x10) will be used. Assume the password for the soft starter is set to 123456. Therequest packet that is sent to the machine is shown in tab. 3-5.

In this case the soft starter accepts the request packet and sends a positive response. The responsemessage is shown in tab. 3-6.

– Tx to the soft starter: 01 10 00 47 00 03 06 00 01 34 12 00 56 46 45 (Hexadecimal bytes)

– Response from the soft starter: 01 10 00 47 00 03 30 1D (Hexadecimal bytes)

NOTE If other values have been written to the shadow holding registers prior to executing a commandwrite sequence these values will be discarded. The contents of the shadow register set will berestored to state of the active holding registers.

Modbus® address

Function code (FC)

Starting address

Register quantity Byte count Data1 Data2 Data3 CRC

0x01 0x10 0x0047 0x0003 0x06 0x0001 0x3412 0x0056 0x4546

Tab. 3-5: Modbus®/RTU multiple register write command to the soft starter slave

Modbus® address

Function code (FC)

Starting address

Register quantity CRC

0x01 0x10 0x0047 0x0003 0x1D30

Tab. 3-6: Modbus®/RTU successful response from soft starter slave

NOTE Since according to the Modbus® standard all 16-bit registers are transmitted most significant bytefirst (except the CRC which is transmitted least significant byte first) the sequence of bytes on theserial lines are shown below:

NOTE The same discussion applies for the Core models, except that the Core models do notrequire a password. In the case of the Core models the 3-register write starts with the controlcommand register and ends with any value being written to the write confirmation register.

MEsoftstart 3 - 25


Writing to the Modbus® IF command register

The contents of the shadow holding registers are not visible to a user. Read operations from the hold-ing registers return the validated configuration values that are currently in the active holding registerset. If a user wants to set only specific parts of the holding register map instead of all the registers, itis recommended to first clear the shadow holding registers to discard any changes that could previ-ously have been made.

Writing the appropriate command to the Modbus® IF register discards any changes in the shadowholding registers, restoring their contents to the same state as the active holding registers.

3.5.3 Suggested sequence of operations to change the configuration

When changing values in the holding registers, the following two approaches are recommended:

● In the case where all the register values are to be updated (or just confirmed), use one or multiplewrite transactions to write to all the shadow holding registers (except the Modbus® IF commandregister). The correct password (or 0 if password checking is disabled) should be sent as part ofthe last write transaction. (In the case of the Core models the write confirmation register shouldbe accessed as part of the last transaction.)

● In the case where only some of the holding registers are to be changed by selectively writing tospecific addresses, it is recommended that the write sequence be started by writing the appro-priate command to the Modbus® IF command register. This will clear any changes that mightalready have been made to the shadow holding registers, preventing unexpected results. Onceagain, the correct password (or 0 if password checking is disabled) should be sent as part of thelast write transaction to confirm the changes. (In the case of the Core models the write confirma-tion register should be accessed as part of the last transaction.)

3.5.4 Using the unlock register

In order to prevent inadvertent writes to the UART configuration register or the network configurationregisters (registers 59–62), an additional write verification step is required via the unlock register. Newvalues written to the UART configuration register or the network configuration registers are onlyaccepted if a value of 0xACDC is written to the unlock register.

The steps to follow to change the UART configuration register and/or the network configuration reg-isters are as follows:

● Clear the shadow holding registers by writing the appropriate command to the Modbus® IFcommand register.

● Write the desired new values to the UART configuration register and/or the network configurationregisters. These values will be stored in the shadow holding registers.

● Write the unlock code (0xACDC) to the unlock register.

● Write the password to the password register (or for the Core models perform a write to the writeconfirmation register).

NOTE Any write that accesses the Modbus® IF command register will be treated as a write to that addressonly. If this address is included in a multiple register write command the values that were writtento the other registers in the same write operation will be ignored.

3 - 26


The requested values will now be applied. If the UART configuration register contents were changedthe Modbus® UART will be re-initialized with the new settings. If the network parameters werechanged the TCP/IP interface will be re-initialized.

On completion of the write command the unlock register its contents will be reset to 0, indicating thatthere are no further unconfirmed commands pending.

3.5.5 Consistency of entire configuration

On reception of a write to the password registers (or for the Core models a write to the write confir-mation register) the entire configuration in the shadow holding registers is checked for consistency.If the resulting configuration is found to be inconsistent the write transaction is rejected (exceptioncode for illegal data value is returned), the contents of the shadow holding registers are reset to reflectthe current validated configuration and the configuration is left unchanged.

As an example, consider the case where the workload is set to ‘normal’ and the maximum starts perhour is set to 10. If one wishes to change the maximum starts per hour to 30, the workload needs tobe changed to ‘heavy’. There are two ways in which this can be accomplished:

● Update the contents of both the workload register and the maximum starts per hour registerbefore confirming the write transaction by writing the password.

● First change the contents of the workload register to ‘heavy’ and confirm the write (write to thepassword register). Then change the contents of the maximum starts per hour register to 30 andconfirm the write. If the registers are changed in a different sequence the configuration consist-ency check will fail after attempting to change the maximum starts per hour register.

NOTE The new register values, unlock code and password (or write confirmation) can be issued as sepa-rate Modbus® transactions using function code FC06 or as a single Modbus® multiple registerwrite transaction using function code FC16 (or as a combination of the above).

MEsoftstart 3 - 27


The first option is illustrated in fig. 3-2 to fig. 3-5.

Before the configuration write sequence starts the values in the shadow registers and the active reg-isters are the same. This will be the case immediately after the completion of the previous configura-tion write sequence (any one of the three options listed in section 3.5.2). This is shown in fig. 3-2.

Then a single holding register write transaction is performed to the max starts per hour register to setthe value to 30. The new state of the registers is shown in fig. 3-3. Note that at this point the config-uration in the shadow registers is not valid since the maximum starts per hour that is allowed in ‘nor-mal’ mode is 10. Since no consistency checks are done yet this does not cause a failure.

State of the registers_all

Fig. 3-2: State of the registers before the configuration write sequence starts


Fig. 3-3: State of the registers after writing to the maximum starts per hour register

Active registers

Shadow registers

Register name

Max. starts per hour

Workload

Password [1–4]

Password [5–6]

Addr

17

44

72

73

Value

10

Normal

0

0

Register name


Workload

Password [1–4]

Password [5–6]

Addr

17

44

72

73

Value

10

Normal

0x3412

0x0056

Active registers

Shadow registers

Register name


Workload

Password [1–4]

Password [5–6]

Addr

17

44

72

73

Value

30

Normal

0

0

Register name


Workload

Password [1–4]

Password [5–6]

Addr

17

44

72

73

Value

10

Normal

0x3412

0x0056

3 - 28


Next a single holding register write transaction is performed to the workload register to set the valueto ‘heavy’. The new state of the registers is shown in fig. 3-4.

Finally, a two-register holding register write transaction is performed to write the correct password tothe password registers. The new state of the registers is shown in fig. 3-5.


Fig. 3-4: State of the registers after writing to the workload register

NOTE At this point the valid configuration from the shadow registers is transferred to the active registersafter passing the limit and configuration consistency tests. The shadow register set password reg-isters are reset to 0.


Fig. 3-5: State of the registers after writing to the password registers

Active registers

Shadow registers

Register name


Workload

Password [1–4]

Password [5–6]

Addr

17

44

72

73

Value

30

Heavy

0

0

Register name


Workload

Password [1–4]

Password [5–6]

Addr

17

44

72

73

Value

10

Normal

0x3412

0x0056

Active registers

Shadow registers

Register name


Workload

Password [1–4]

Password [5–6]

Addr

17

44

72

73

Value

30

Heavy

0

0

Register name


Workload

Password [1–4]

Password [5–6]

Addr

17

44

72

73

Value

30

Heavy

0x3412

0x0056

MEsoftstart 3 - 29


3.5.6 Soft starter valid commands

When a command is received via the Modbus® interface, the soft starter will immediately attempt toperform the command. If the soft starter is in a state where the requested command cannot be exe-cuted, the command will be ignored.

Fig. 3-6 shows which commands are accepted in which soft starter states for the Pro models. Validcommands resulting in state transitions are highlighted in green. The error state is shown in blue. Thisstate can be entered from any other state should an error occur (these state transitions were omittedto limit clutter).

For the Core models the jog command cannot be issued through the Modbus® interface, but can onlybe issued using the Pot HMI interface. Also, if the DIP switch is set to jog mode all commands receivedacross the Modbus® interface will be rejected.

MEsoftstarter main states and commands

Fig. 3-6: MEsoftstart/I soft starter main states and accepted commands

Stop Cmd

Stop Cmd

Stop Cmd

Start Cmd

Jog CmdReset Cmd

Error

Cooling

Jogging

Running

Starting

Stopping

Delayrestart

Idle

Ramp done

Ramp done

Delaycompleted

Cooleddown

Toohot Time

exceeded

3 - 30

Supported exception codes MEsoftstart/I Modbus® function codes and registers

3.6 Supported exception codes

The following Modbus® exception codes are supported:

● Code 01 – Illegal function: Only the function codes listed in section 3.1 are supported. A transac-tion requesting a different function code will be rejected with this exception code.

● Code 02 – Illegal data address: Any transactions attempting to access register locations outsideof the defined address ranges will be rejected with this exception code.

● Code 03 – Illegal data value: If the contents written to any register fall outside the limits specifiedfor that register, or the requested write results in an inconsistent configuration, the write transac-tion will be rejected with this exception code.

NOTES – Code 03 is only sent in response to a write that included the password registers since that is theonly time that the limit checks and configuration consistency checks are performed.

– Modbus® transactions are handled as atomic units. If any part of the transaction fails (for examplea ten register write command accesses nine legal addresses and one address beyond the rangeof supported addresses) the entire transaction is rejected with the appropriate exception code.

MEsoftstart 3 - 31

MEsoftstart/I Modbus® function codes and registers Supported exception codes

3 - 32

Supported function codes (MEsoftstart/DIN) MEsoftstart/DIN Modbus® function codes and registers

4 MEsoftstart/DIN Modbus® function codes and registers

This chapter defines the function codes (FC) supported by the DIN soft starter, and the applicable reg-isters available for each function code.

4.1 Supported function codes (MEsoftstart/DIN)

This platform supports the function codes given by tab. 4-1.

If the DIN soft starter detects a Modbus® transaction with a function code that is not supported, it willrespond with exception code 0x01, indicating an illegal function has been performed.

4.2 Scaling of register values

For each Modbus® register a scaling value and offset are provided. When packing a value into a reg-ister the value to load into the register is calculated as:

– Register contents = (floor operator of )(Effective value * scaling value) + offset value

When reading a register, the effective value corresponding to what is stored in the register is calcu-lated as:

– Effective value = (register contents – offset value)/scaling value

4.3 Limits for register values

For each register an upper- and lower limit is provided. If a value outside of these limits is sent to thesoft starter the value will be rejected and the soft starter shall respond with exception code 0x03 (Ille-gal data value).

Function code Value (8-bit) Description

FC03 0x03 Read holding register

FC04 0x04 Read input register

FC06 0x06 Write single output register

FC16 0x10 Write multiple output registers

Tab. 4-1: Supported Modbus® function codes (MEsoftstart/DIN)

NOTE The units of measure provided in tab. 4-2 and tab. 4-3 refer to the effective values, not the valuesas stored in the Modbus® registers.

NOTE If any value within a multiple register transaction is rejected due to failing the limit checking, theentire packet will be discarded.

MEsoftstart 4 - 1

MEsoftstart/DIN Modbus® function codes and registers Input registers (MEsoftstart/DIN)

4.4 Input registers (MEsoftstart/DIN)

This section lists the memory map describing the input registers, (Modbus® address range 0x3xxxx).These registers support the function code FC04. The register addresses are given in tab. 4-2.

Input (0x3xxxx) registers (MEsoftstart/DIN)


factorOffset value

Validrange

Offset address

Start count (LS Word) These two registers together comprise a U4 value

(refer to section 2.4.2) containing the number of starts that have been performed by the soft starter.

NA 1 0 0–65535 0

Start count (MS Word) NA 1 0 0–65535 1

Frequency Detected AC frequency Hz 100 0 0–10000 2

VL1-L2 RMS Line-to-line RMS voltage between input phases L1 and L2 V 10 0 0–7500 3



IL1 RMS RMS current flowing in phase L1 A 100 0 0–15000 6



External supply This value reports the voltage at terminal +24 V DC relative to terminal 0 V (refer to document 1) in sec-tion 1.5.2). Only valid for externally powered models.

V 100 0 0–4000 9

AC phase detected

This value describes the phase detected on the incoming AC lines:- 0 = Unknown phase, i.e. no phase detected,


- Other values = Incorrect phase rotation detected

NA 1 0 0–3 10

Operating mode

This parameter reports the current operational state of the soft starter:- 0 = Idle mode, waiting for a start command- 1 = Busy performing a ramp, could be ramp up or

ramp down- 2 = Motor has been started and is running, bypass

relays on- 3 = Motor has been stopped, processing restart

delay- 4 = Cooling down, temperature is too high to per-

form a start- 5 = Error detected, will automatically recover after

5 minutes delay- 6 = Excessive errors detected, user reset required

NA 1 0 0–6 11

Time remaining

While enforcing the delay to prevent excessive starts per hour or while recovering from an error condition this value indicates how many seconds remain until completion of the delay

s 1 0 0–65535 12

Tab. 4-2: Input (0x3xxxx) registers (MEsoftstart/DIN) (1)

4 - 2

Input registers (MEsoftstart/DIN) MEsoftstart/DIN Modbus® function codes and registers

Last fault ID

This register identifies the cause of a current trip con-dition- 0 = No error condition present- 1 = Incorrect AC phase detected- 2 = Incoming AC voltage is too high- 3 = Incoming AC voltage is too low- 4 = AC frequency out of range- 5 = Over current/short circuit detected during

ramp- 6 = Ramp did not complete within allotted time- 7 = Over current/short circuit detected while in

bypass state- 8 = Motor thermal protection curve limit

exceeded- 9 = Voltage imbalance detected

- 10 = Switching element conducting current when it should be off

- 11 = Switching element failed open circuit- 12 = Lost synchronisation with incoming AC signal- 13 = Over temperature detected within soft starter- 14 = Exceeded soft starter continuous operating

current limit- 15 = Exceeded soft starter dynamic current limit

during ramp- 16 = Input power brownout condition detected- 17 = Motor/input power not connected correctly- 18 = Motor under load condition detected- 19 = Switching element failed short circuit- 20 = Internal hardware error- 21 = Stored configuration settings are invalid

NA 1 0 0–21 13

Firmware revision

Reports the revision of the firmware loaded on the soft starter. The least significant byte is an unsigned 8-bit integer containing the firmware minor revision, while the most significant byte contains the firmware major revision.

NA 1 0 0–65536 14

Hardware configuration

This parameter reports the hardware configuration of the connected soft starter:- bit 0: 0 = 3-phase control,

1 = only 2 phases are controlled- bit 1: 0 = 32 A running current model,

1 = 16 A running current model- bit 2: 0 = internal power supply present,

1 = externally powered- bit 3: 0 = user configuration allowed,

1 = factory configured- bits 15–4: ReservedFor example, the MEsoftstart-D03S will repot a value of 0x00, while the MEsoftstart-D02L will report a value of 0x03 (refer to document 1) in section 1.5.2 for hardware model descriptions.

NA 1 0 0–15 15

Reserved Used during acceptance testing NA 1 0 0–65536 16–19

Internal temperature

Internal soft starter temperature. The effective range of temperatures that can be reported are -55 0C–150 0C

0C 16 32768 31888– 35168 20

Reserved Used during acceptance testing NA 1 0 0–65536 21


factorOffset value

Validrange

Offset address


MEsoftstart 4 - 3

MEsoftstart/DIN Modbus® function codes and registers Input registers (MEsoftstart/DIN)

Power status

This describes the status of the power source detec-tion logic (where is 24 V power received from), as well as whether the soft starter is inhibited from starting or not:- bit 0: 0 = Not on internal 24 V power,

1 = internal 24 V power detected- bit 1: 0 = Not on external 24 V power,

1 = external 24 V power detected- bit 2: 0 = Not inhibited,

1 = soft starter starting is inhibited- bit 3: 0 = Power level OK,

1 = Power level low, in shutdown

NA 1 0 0–15 22

Reserved Used during acceptance testing NA 1 0 0–65536 23

Trip counter This parameter counts the number of times that the soft starter has tripped due to any error condition NA 1 0 0–65536 24

Reserved Used during acceptance testing NA 1 0 0–65536 25–28


factorOffset value

Validrange

Offset address


4 - 4

Holding registers (MEsoftstart/DIN) MEsoftstart/DIN Modbus® function codes and registers

4.5 Holding registers (MEsoftstart/DIN)

This section lists the memory map describing the holding registers, (Modbus® address range0x4xxxx). These registers support the function codes FC03, FC06 and FC16. The register addresses aregiven in tab. 4-3. The control parameters are described in more detail in section 5 of document 1) ofsection 1.5.2.

Holding (0x4xxxx) registers (MEsoftstart/DIN)


Offset value


address

Start ramp duration

This parameter specifies the duration of the start ramp. ms 1 0 1000–

10000 1000 0

Starting duty cycle %

This parameter specifies the firing angle percentage from which the start ramp will commence. % 1 0 15–40 15 1

Ramp down duration

This parameter specifies the duration of the stop ramp.

NOTEIf the motor configuration is selected to be inside delta this parameter must be set to a minimum of 1000 ms (1 s).

ms 1 0 0–10000 0 2

Ramp down start duty cycle %

This parameter specifies the firing angle percentage from which the stop ramp will commence. % 1 0 60–100 100 3

Ramp down end duty cycle %

This parameter specifies the firing angle percentage to which the stop ramp will decrease. % 1 0 15–40 15 4

ReservedThese registers are currently unused. A write to any of these registers must set the register value to 0 or the transaction will be rejected.

NA NA NA 0 0 5–65

Starts per hour

This value determines the time that the soft starter will ‘delay’ before allowing to start the motor again. This is a safety mechanism to protect the motor and the soft starter against overuse.

NA 1 0 1–30 12 66

Motor power rating

This parameter configures the size of the motor. The motor size is selected as follows:0 = 750 W1 = 1.1 kW2 = 1.5 kW3 = 2.2 kW4 = 3 kW5 = 4 kW6 = 5.5 kW7 = 7.5 kW8 = 11 kW9 = 15 kW

10 = 18.5 kW11 = 22 kW12 = 30 kW13 = 37 kW

NA 1 0 0–13 10 67

Motor configuration

This parameter describes the motor configuration as follows:- bit 0: 0 = normal connection,

1 = inside delta connection- bits 3–1: Motor protection class.

● 0 = Class 2● 1 = Class 5● 2 = Class 10

- bits 15–4: Reserved

NA 1 0 0–5 4 68

Tab. 4-3: Holding (0x4xxxx) registers (MEsoftstart/DIN) (1)

MEsoftstart 4 - 5

MEsoftstart/DIN Modbus® function codes and registers Holding registers (MEsoftstart/DIN)

Maximum % of rated current

This parameter specifies the maximum current that can be applied during a start as a percentage of the nameplate rated current.

% 1 0 150–600 314 69

Nameplate rated current

This value sets the nameplate rated current that is specified for the motor and should be set according to the exact details of the attached motor.

NOTEThis value supersedes any assumptions made about the motor size based on the motor power rating.

A 100 0 0–6000 3176 70

Motor under load current %

After the motor has been started the soft starter mon-itors the running current to verify that enough current is drawn. This parameter specifies the current level under which the soft starter will trip due to a low run-ning current condition. This level is specified as a per-centage of the nameplate rated current.

% 1 0 0–100 0 71

Start control

This register contains options related to the auto-start feature of the soft starter. The bit mapping is as fol-lows:- bit 0: If this bit is clear, auto-start is enabled.

Setting this bit disables the auto-start function.

- bits 15–1: Reserved for future use.

72

ReservedThese registers are currently unused. A write to any of these registers must set the register value to 0 or the transaction will be rejected.

NA NA NA 0 0 73–99





NA 1 0 0–0x62F7 0x6101 100

Command register

This register is used to provide commands to the soft starter: 0 = No change1 = Start the motor2 = Stop the motor3 = Reset the soft starter to clear an error condition

NA 1 0 0–3 0 101

Unlock register

This parameter must be set to a specific value to allow the Modbus® configuration and/or command register values to be changed. If it is not set to 0xACDC, the aforementioned parameters will not be changed. A read from this register always return 0.

NA 1 0 0–65535 0 102


Offset value


address

Tab. 4-3: Holding (0x4xxxx) registers (MEsoftstart/DIN) (2)

4 - 6

Holding registers (MEsoftstart/DIN) MEsoftstart/DIN Modbus® function codes and registers

4.5.1 Using the unlock register

In order to prevent inadvertent writes to the command register or the UART configuration register, anadditional write verification step is required via the unlock register. New values written to the com-mand register or the UART configuration register are only accepted once a value of 0xACDC is writtento the unlock register.

The process to follow to change either of the command register or the UART configuration register isas follows:

● Write the desired new value to the command register and/or UART configuration register. Thesevalues will be stored in the holding registers but will not be applied yet at this point. This meansthat a read from these registers will return the desired future value that will be applied onceconfirmed.

● Write the unlock code (0xACDC) to the unlock register. The requested values will now be applied.If the UART configuration register contents were changed the Modbus® UART will be re-initializedwith the new settings. If a Modbus® command was issued this command will be applied immedi-ately according to the control state machine.

After writing the unlock code to the unlock register the command register contents will be reset to 0,indicating that there are no further unconfirmed commands pending.

4.5.2 Consistency of entire configuration

On reception of any holding register write command (FC06 or FC16) the entire configuration (the con-tents of all the holding registers together) is checked for consistency. If the resulting configuration isfound to be inconsistent the write transaction is rejected (exception code for illegal data value isreturned) and the holding register contents are restored to the state prior to the write transaction.

As an example, consider the case where the motor configuration is set to indicate that the motor iswired in a normal delta configuration, and a 0 s ramp down duration is set. If one wishes to change themotor configuration to inside delta the ramp down duration must be increased to at least 1s. There aretwo ways in which this can be accomplished:

● Update the contents of both the ramp down duration register and the motor configurationregister in a single multi-register write transaction.

● First change the contents of the ramp down duration register to 1 s by doing a single register write(this is a legal setting for normal delta as well). Then change the contents of the motor configura-tion register by doing a second single-register write. If the sequence of the two single-registerwrite transactions is reversed the motor configuration register write transaction will be rejected.

The recommended approach is to write the entire holding register set from address 0 to address 72using a single multi-register write transaction.

NOTE The new register values and the unlock code can be issued as separate Modbus® transactionsusing function code FC06 or as a single Modbus® multi-register write transaction using functioncode FC16 (or as a combination of the above).

NOTE The new configuration settings become effective when the next start is performed.

MEsoftstart 4 - 7

MEsoftstart/DIN Modbus® function codes and registers Holding registers (MEsoftstart/DIN)

4.5.3 Soft starter valid commands

When a command is received via the Modbus® interface, the soft starter will immediately attempt toperform the command. If the soft starter is in a state where the requested command cannot be exe-cuted, the command will be ignored.

Fig. 4-1 shows which commands are accepted in which soft starter states. Valid commands resultingin state transitions are highlighted in green. The error states are shown in blue. These states can beentered from any other state should an error occur (these state transitions were omitted to keep thediagram uncluttered).

DIN soft starter main states and commands

Fig. 4-1: MEsoftstart/DIN soft starter main states and accepted commands

Stop Cmd

Stop Cmd

Start Cmd

Reset Cmd

Errorrecoverable

Cooling down

Running

Delayrestart

Idle

Ramp done

Ramp done

Delaycompleted

Cooled down

Too hot

Excessiveerrors

Reset Cmd

Reset Cmd

Time out

Ramp up/down

4 - 8

Supported exception codes MEsoftstart/DIN Modbus® function codes and registers

4.6 Supported exception codes

The following Modbus® exception codes are supported:

● Code 01 – Illegal function: Only the function codes listed in section 4.1 are supported. A transac-tion requesting a different function code will be rejected with this exception code.

● Code 02 – Illegal data address: Any transactions attempting to access register locations outsideof the defined address ranges will be rejected with this exception code.

● Code 03 – Illegal data value: If the contents written to any register fall outside the limits specifiedfor that register, or the requested write results in an inconsistent configuration, the write transac-tion will be rejected with this exception code.

NOTE Modbus® transactions are handled as atomic units. If any part of the transaction fails (for examplea ten register write command accesses nine legal addresses and one address beyond the range ofsupported addresses) the entire transaction is rejected with the appropriate exception code.

MEsoftstart 4 - 9

MEsoftstart/DIN Modbus® function codes and registers Supported exception codes

4 - 10

Modbus®/RTU CRC calculation Appendix

A Appendix

A.1 Modbus®/RTU CRC calculation

This section provides a C code snippet for calculating the 16-bit Modbus®/RTU CRC. The followingparameters are passed to the function:

● data_p: This is a pointer to the data for which the CRC is to be calculated.

● len: This contains the number of bytes of data to be processed.

● firstByte: Set to 1 if this is the first byte in a CRC calculation. In that case the CRC value is initialisedto 0xFFFF. If set to 0 the CRC value is set to prevCrc.

● prevCrc: The interim output of a previous call to MyUtilsUpdateCRC16.

A CRC can be calculated over an entire payload by passing a pointer to the received payload, settingthe length appropriately and setting firstByte to 1 (the value of prevCrc doesn’t matter).

A CRC can be calculated as a cumulative operation by calling this function for every byte that isreceived. In this case firstByte is set to 1 for the first received byte. After that firstByte is set to 0 for eachfollowing byte, and the result of the last call to this function is passed in prevCrc.

MEsoftstart A - 1

Appendix Modbus®/RTU CRC calculation

A - 2

Mitsubishi Electric Europe B.V. / FA - European Business Group / Mitsubishi-Electric-Platz 1 / D-40882 Ratingen / Germany / Tel.: +49(0)2102-4860 / Fax: +49(0)2102-4861120 / [email protected] / https://eu3a.mitsubishielectric.com

Mitsubishi Electric Europe B.V. EUROPEMitsubishi-Electric-Platz 1D-40882 RatingenPhone: +49 (0)2102 / 486-0Fax: +49 (0)2102 / 486-1120

Mitsubishi Electric Europe B.V. CZECH REP.Pekařská 621/7CZ-155 00 Praha 5Phone: +420 255 719 200Fax: +420 251 551 471

Mitsubishi Electric Europe B.V. FRANCE25, Boulevard des BouvetsF-92741 Nanterre CedexPhone: +33 (0)1 / 55 68 56 95Fax: +33 (0)1 / 55 68 57 57

Mitsubishi Electric Europe B.V. IRELANDWestgate Business Park, BallymountIRL-Dublin 24Phone: +353 (0)1 4198800Fax: +353 (0)1 4198890

Mitsubishi Electric Europe B.V. ITALYViale Colleoni 7 Palazzo SirioI-20864 Agrate Brianza (MB)Phone: +39 039 / 60 53 1Fax: +39 039 / 60 53 312

Mitsubishi Electric Europe B.V. NETHERLANDSNijverheidsweg 23CNL-3641RP MijdrechtPhone: +31 (0) 297 250 350

Mitsubishi Electric Europe B.V. POLANDul. Krakowska 48PL-32-083 BalicePhone: +48 (0) 12 347 65 00Fax: +48 (0) 12 630 47 01

Mitsubishi Electric (Russia) LLC RUSSIA2 bld. 1, Letnikovskaya st.RU-115114 MoscowPhone: +7 495 / 721 2070Fax: +7 495 / 721 2071

Mitsubishi Electric Europe B.V. SPAINCarretera de Rubí 76-80 Apdo. 420E-08190 Sant Cugat del Vallés (Barcelona)Phone: +34 (0) 93 / 5653131Fax: +34 (0) 93 / 5891579

Mitsubishi Electric Europe B.V. (Scandinavia) SWEDENHedvig Möllers gata 6,SE- 223 55 LundPhone: +46 (0) 8 625 10 00

Mitsubishi Electric Turkey Elektrik Ürünleri A.Ş. TURKEYFabrika Otomasyonu Merkezi Şerifali Mahallesi Kale Sokak No:41TR-34775 Ümraniye-İSTANBULPhone: +90 (216) 969 25 00Fax: +90 (216) / 661 44 47

Mitsubishi Electric Europe B.V. UKTravellers LaneUK-Hatfield, Herts. AL10 8XBPhone: +44 (0)1707 / 28 87 80Fax: +44 (0)1707 / 27 86 95

Mitsubishi Electric Corporation JAPANTokyo Building 2-7-3Marunouchi, Chiyoda-kuTokyo 100-8310Phone: +81 (3) 3218-2111Fax: +81 (3) 3218-2185

Mitsubishi Electric Automation, Inc. USA500 Corporate Woods ParkwayVernon Hills, IL 60061Phone: +1 (847) 478-2100Fax: +1 (847) 478-0328

GEVA AUSTRIAWiener Straße 89A-2500 BadenPhone: +43 (0)2252 / 85 55 20Fax: +43 (0)2252 / 488 60

OOO TECHNIKON BELARUSProspect Nezavisimosti 177-9BY-220125 MinskPhone: +375 (0)17 / 393 1177Fax: +375 (0)17 / 393 0081

INEA RBT d.o.o. BOSNIA AND HERZEGOVINAStegne 11SI-1000 LjubljanaPhone: +386 (0)1/ 513 8116Fax: +386 (0)1/ 513 8170

AKHNATON BULGARIA4, Andrei Ljapchev Blvd., PO Box 21BG-1756 SofiaPhone: +359 (0)2 / 817 6000Fax: +359 (0)2 / 97 44 06 1

INEA CR CROATIALosinjska 4 aHR-10000 ZagrebPhone: +385 (0)1 / 36 940 - 01/ -02/ -03Fax: +385 (0)1 / 36 940 - 03

AutoCont C. S. S.R.O. CZECH REPUBLICKafkova 1853/3CZ-702 00 Ostrava 2Phone: +420 595 691 150Fax: +420 595 691 199

HANS FØLSGAARD A/S DENMARKTheilgaards Torv 1DK-4600 KøgePhone: +45 4320 8600Fax: +45 4396 8855

Electrobit OÜ ESTONIAPärnu mnt. 160iEST-11317, TallinnPhone: +372 6518 140

UTU Automation Oy FINLANDPeltotie 37iFIN-28400 UlvilaPhone: +358 (0)207 / 463 500 Fax: +358 207 / 463 501

UTECO A.B.E.E. GREECE5, Mavrogenous Str.GR-18542 PiraeusPhone: +30 (0)211 / 1206-900Fax: +30 (0)211 / 1206-999

MELTRADE Kft. HUNGARYFertő utca 14.HU-1107 BudapestPhone: +36 (0)1 / 431-9726Fax: +36 (0)1 / 431-9727

OAK Integrator Products SIA LATVIARitausmas iela 23LV-1058 RigaPhone: +371 67842280

Automatikos Centras, UAB LITHUANIANeries krantiné 14A-101LT-48397 KaunasPhone: +370 37 262707Fax: +370 37 455605

ALFATRADE Ltd. MALTA99, Paola HillMalta-Paola PLA 1702Phone: +356 (0)21 / 697 816Fax: +356 (0)21 / 697 817

INTEHSIS SRL MOLDOVAbld. Traian 23/1MD-2060 KishinevPhone: +373 (0)22 / 66 4242Fax: +373 (0)22 / 66 4280

Fonseca S.A. PORTUGALR. João Francisco do Casal 87/89PT-3801-997 Aveiro, EsgueiraPhone: +351 (0)234 / 303 900Fax: +351 (0)234 / 303 910

SIRIUS TRADING & SERVICES SRL ROMANIAAleea Lacul Morii Nr. 3RO-060841 Bucuresti, Sector 6Phone: +40 (0)21 / 430 40 06Fax: +40 (0)21 / 430 40 02

INEA SR d.o.o. SERBIAUl. Karadjordjeva 12/217SER-11300 SmederevoPhone: +381 69 172 27 25

SIMAP SK (Západné Slovensko) SLOVAKIADolné Pažite 603/97SK-911 06 TrenčínPhone: +421 (0)32 743 04 72Fax: +421 (0)32 743 75 20

INEA RBT d.o.o. SLOVENIAStegne 11SI-1000 LjubljanaPhone: +386 (0)1 / 513 8116Fax: +386 (0)1 / 513 8170

OMNI RAY AG SWITZERLANDIm Schörli 5CH-8600 DübendorfPhone: +41 (0)44 / 802 28 80Fax: +41 (0)44 / 802 28 28

CSC- AUTOMATION Ltd. UKRAINE4 B, Yevhenа Sverstyuka Str.UA-02002 KievPhone: +380 (0)44 / 494 33 44Fax: +380 (0)44 / 494-33-66

HEADQUARTERS EUROPEAN REPRESENTATIVES EUROPEAN REPRESENTATIVES EURASIAN REPRESENTATIVES

MIDDLE EAST REPRESENTATIVE

TOO Kazpromavtomatika KAZAKHSTANUL. ZHAMBYLA 28,KAZ-100017 KaragandaPhone: +7 7212 / 50 10 00Fax: +7 7212 / 50 11 50

EIM Energy EGYPT3 Roxy Square ET-11341 Heliopolis, CairoPhone: +202 24552559Fax: +202 245266116

SHERF Motion Techn. Ltd. ISRAELRehov Hamerkava 19IL-58851 HolonPhone: +972 (0)3 / 559 54 62Fax: +972 (0)3 / 556 01 82

CEG LIBAN LEBANONCebaco Center/Block A Autostrade DORALebanon-BeirutPhone: +961 (0)1 / 240 445Fax: +961 (0)1 / 240 193

AFRICAN REPRESENTATIVE

ADROIT TECHNOLOGIES SOUTH AFRICA20 Waterford Office Park 189 Witkoppen RoadZA-FourwaysPhone: + 27 (0)11 / 658 8100Fax: + 27 (0)11 / 658 8101

Documents

Instruction manual Modbus®/RTU/TCP – DIN, Pro, Core variants