The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the products contained herein. This documentation is not intended as a
substitute for and is not to be used for determining suitability or reliability of these products for specific user
applications. It is the duty of any such user or integrator to perform the appropriate and complete risk
analysis, evaluation and testing of the products with respect to the relevant specific application or use
thereof. Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for
misuse of the information contained herein. If you have any suggestions for improvements or amendments
or have found errors in this publication, please notify us.
You agree not to reproduce, other than for your own personal, noncommercial use, all or part of this
document on any medium whatsoever without permission of Schneider Electric, given in writing. You also
agree not to establish any hypertext links to this document or its content. Schneider Electric does not grant
any right or license for the personal and noncommercial use of the document or its content, except for a
non-exclusive license to consult it on an "as is" basis, at your own risk. All other rights are reserved.
All pertinent state, regional, and local safety regulations must be observed when installing and using this
product. For reasons of safety and to help ensure compliance with documented system data, only the
manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant instructions must
be followed.
Failure to use Schneider Electric software or approved software with our hardware products may result in
injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
Read these instructions carefully, and look at the equipment to become familiar with the device before
trying to install, operate, service, or maintain it. The following special messages may appear throughout
this documentation or on the equipment to warn of potential hazards or to call attention to information that
clarifies or simplifies a procedure.
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel.
No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this
material.
A qualified person is one who has skills and knowledge related to the construction and operation of
electrical equipment and its installation, and has received safety training to recognize and avoid the
hazards involved.
BEFORE YOU BEGIN
Do not use this product on machinery lacking effective point-of-operation guarding. Lack of effective pointof-operation guarding on a machine can result in serious injury to the operator of that machine.
1672609EN-03 01/20205
WARNING
UNGUARDED EQUIPMENT
Do not use this software and related automation equipment on equipment which does not have point-
of-operation protection.
Do not reach into machinery during operation.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
This automation equipment and related software is used to control a variety of industrial processes. The
type or model of automation equipment suitable for each application will vary depending on factors such
as the control function required, degree of protection required, production methods, unusual conditions,
government regulations, etc. In some applications, more than one processor may be required, as when
backup redundancy is needed.
Only you, the user, machine builder or system integrator can be aware of all the conditions and factors
present during setup, operation, and maintenance of the machine and, therefore, can determine the
automation equipment and the related safeties and interlocks which can be properly used. When selecting
automation and control equipment and related software for a particular application, you should refer to the
applicable local and national standards and regulations. The National Safety Council's Accident Prevention
Manual (nationally recognized in the United States of America) also provides much useful information.
In some applications, such as packaging machinery, additional operator protection such as point-ofoperation guarding must be provided. This is necessary if the operator's hands and other parts of the body
are free to enter the pinch points or other hazardous areas and serious injury can occur. Software products
alone cannot protect an operator from injury. For this reason the software cannot be substituted for or take
the place of point-of-operation protection.
Ensure that appropriate safeties and mechanical/electrical interlocks related to point-of-operation
protection have been installed and are operational before placing the equipment into service. All interlocks
and safeties related to point-of-operation protection must be coordinated with the related automation
equipment and software programming.
NOTE: Coordination of safeties and mechanical/electrical interlocks for point-of-operation protection is
outside the scope of the Function Block Library, System User Guide, or other implementation referenced
in this documentation.
START-UP AND TEST
Before using electrical control and automation equipment for regular operation after installation, the system
should be given a start-up test by qualified personnel to verify correct operation of the equipment. It is
important that arrangements for such a check be made and that enough time is allowed to perform
complete and satisfactory testing.
Follow all start-up tests recommended in the equipment documentation. Store all equipment
documentation for future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and temporary grounds that are not installed
according to local regulations (according to the National Electrical Code in the U.S.A, for instance). If highpotential voltage testing is necessary, follow recommendations in equipment documentation to prevent
accidental equipment damage.
Before energizing equipment:
Remove tools, meters, and debris from equipment.
Close the equipment enclosure door.
WARNING
EQUIPMENT OPERATION HAZARD
Verify that all installation and set up procedures have been completed.
Before operational tests are performed, remove all blocks or other temporary holding means used for
shipment from all component devices.
Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
61672609EN-03 01/2020
Remove all temporary grounds from incoming power lines.
Perform all start-up tests recommended by the manufacturer.
OPERATION AND ADJUSTMENTS
The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English version
prevails):
Regardless of the care exercised in the design and manufacture of equipment or in the selection and
ratings of components, there are hazards that can be encountered if such equipment is improperly
operated.
It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or unsafe
operation. Always use the manufacturer’s instructions as a guide for functional adjustments. Personnel
who have access to these adjustments should be familiar with the equipment manufacturer’s
instructions and the machinery used with the electrical equipment.
Only those operational adjustments actually required by the operator should be accessible to the
operator. Access to other controls should be restricted to prevent unauthorized changes in operating
characteristics.
1672609EN-03 01/20207
81672609EN-03 01/2020
At a Glance
Document Scope
Validity Note
About the Book
This manual describes the DFB (Derived Function Block) library dedicated to TeSys U starter-controllers
and TeSys T motor management systems.
It is intended for design engineers and system integrators who have a good knowledge of Unity Pro PLC
programming platforms.
The purposes of this manual are to
describe the scope of the DFB library and platform compatibility,
describe the DFB characteristics and the download procedure from the Schneider Electric website,
explain how to implement the DFB in the PLC application.
This TeSys library is compatible and usable with the following versions of Unity Pro:
Unity Pro V2.3 SP2
Unity Pro V3.0
Unity Pro V3.1
Unity Pro V4.0 or later
This manual is valid for all TeSys DFBs. The following table describes the differences between versions 1
and 2 of Unity Pro:
You can download these technical publications and other technical information from our website at
https://www.se.com/ww/en/download/ .
101672609EN-03 01/2020
TeSys DFB Library V2 for Unity Pro
Introduction
1672609EN-03 01/2020
Introduction
Chapter 1
Introduction
Introduction
This chapter gives an overview of the TeSys U and TeSys T DFB (Derived Function Block) library,
presents the DFB library download procedure from the Schneider Electric website, and describes the
sequencing system used to synchronize the treatment between DFBs.
What Is in This Chapter?
This chapter contains the following topics:
Presentation12
TeSys DFB Library Overview13
TeSys DFB Sequencing17
TopicPage
1672609EN-03 01/202011
Introduction
Presentation
Aim of the TeSys DFB Library
The TeSys DFB library has been developed to simplify and optimize the integration of TeSys U startercontrollers and TeSys T motor management systems in PLC applications, for both PLC programmers and
end users.
The TeSys DFB library for Unity Pro can be ordered with part number UNYLTSZFUWB.
Advantages for the PLC Programmer
The TeSys DFB library enables the PLC programmer to
simplify the program design: the program is split by functions (control, command, data treatment,...),
optimize the programming time: the DFB is tested and can be re-used for different applications,
increase the program understanding: the applications are coded in the same way using the common
DFB,
optimize the program size: the same code is used for each DFB instantiation,
simplify the TeSys U and TeSys T integration: the data mapping management is masked.
Advantages for the End User
The TeSys DFB library enables the end user to
optimize the communication response time:
the Modbus requests management is optimized,
the data exchange management is optimized,
the product performance is taken into account,
have a functional view of the motor-starter by providing direct access to common functions (Ready,
Alarm, Run, Stop,...),
group data related to a specific application (diagnostic, maintenance, measurement,...) through a
program number,
facilitate debugging: variables used by the DFB are identified on its interface.
PLC Platform Compatibility
The TeSys DFB library can be integrated in the Unity Pro programming platform with Quantum, Premium
and M340 PLC platforms.
TeSys Compatibility
The TeSys DFB library for Unity Pro is compatible with:
TeSys U starter-controllers (up to 38 A/18.5 kW or 25 hp),
TeSys T motor management system.
Communication Protocol Compatibility
The following table describes the TeSys DFB library compatibility with communication protocols and the
corresponding TeSys U and TeSys T assemblies.
ProtocolTeSys UTeSys T
Modbus SL
(Serial Line)
Modbus/TCPStarter-controller with LULC033 Modbus
Profibus DPStarter-controller with LULC07 Profibus DP
CANopenStarter-controller with LULC08 CANopen
Advantys STB with
communication module
Starter-controller with LULC033 Modbus
communication module
communication module and Ethernet gateway
(TeSysPort, TSXETG100, TSXETG1000,...)
communication module
communication module
Starter-controller with LULC15 Advantys STB
communication module
LTMR••M•• Modbus SL controller with or without the
LTM E expansion module
LTMR••E•• Modbus/TCP controller with or without the
LTM E expansion module
LTMR••P•• Profibus DP controller with or without the
LTM E expansion module
LTMR••C•• CANopen controller with or without the
LTM E expansion module
–
12
1672609EN-03 01/2020
TeSys DFB Library Overview
TeSys DFB Library Organization
The following table lists the TeSys DFB library according to the communication protocol and service and
their availability according to the TeSys model:
Introduction
Communication Protocol /
Service
Modbus SLCtrl_cmd_mdb_u_••••√√–
Modbus SL and Modbus/TCPCustom_mdb_••••√–√
Modbus/TCP (for Quantum PLC) Custom_mdb_addq√–√
Profibus DPCtrl_pfb_u_ms√√–
Cyclic control/command
(Modbus/TCP (IO scanning),
CANopen, and Advantys STB)
PKWSpecial_pkw_u√––
TreatmentTimestamp_•√––
DFB NameTeSys U up to
32 A
Comm_manager_u√√–
Ctrl_cmd_mdb_t_••••––√
Comm_manager_t––√
Special_mdb_u_••••√––
Special_mdb_t_••••––√
Special_mdb_u_addq√––
Special_mdb_t_addq––√
Ctrl_pfb_u_mms√––
Ctrl_pfb_t_mms––√
Ctrl_cmd_u (Modbus/TCP (IO scanning), CANopen, and
Advantys STB)
Ctrl_cmd_t (Modbus/TCP (IO scanning) and CANopen)––√
Special_pkw_t––√
Custom_pkw√–√
Scale√––
√√–
TeSys U up to
38 A
TeSys T
Modbus SL DFB Library
The following table describes the Modbus SL (Serial Line) DFB library:
DFBDescriptionFor More Information
Ctrl_cmd_mdb_u_addr
Ctrl_cmd_mdb_u_addm
Comm_manager_uThis DFB is dedicated to the control and command of up to 31 TeSys U
These DFBs are dedicated to the control and command of a single TeS ys
U starter-controller with any control unit and a LULC033 Modbus
communication module.
Ctrl_cmd_mdb_u_addr is dedicated to Premium PLC.
Ctrl_cmd_mdb_u_addm is dedicated to M340 PLC.
These DFBs enable the user to
read status register 455,
write command register 704,
reset communication loss (register 703, bit 3).
The program number enables the user to select bit or word control.
starter-controllers with any control unit and a LULC033 Modbus
communication module.
It must be associated with the Ctrl_cmd_mdb_u_•••• DFBs to manage the
Modbus requests sequencing.
It enables the user to
optimize the response time by taking into account the response time
of the devices,
send write requests only when necessary,
manage the disconnection and reconnection of a TeSys U Modbus
slave.
The program number enables the user to select different Modbus request
sequences.
Ctrl_cmd_mdb_u_••••: TeSys U
Control/Command for Modbus
SL, page 22
Comm_manager_u: TeSys U
Communication Management for
Modbus SL, page 26
1672609EN-03 01/202013
Introduction
DFBDescriptionFor More Information
Ctrl_cmd_mdb_t_addr
Ctrl_cmd_mdb_t_addm
These DFBs are dedicated to the control and command of a single TeSys
T LTMR••M•• Modbus SL controller with or without the LTM E expansion
module.
Ctrl_cmd_mdb_t_addr is dedicated to Premium PLC.
Ctrl_cmd_mdb_t_addm is dedicated to M340 PLC.
Ctrl_cmd_mdb_t_••••: TeSys T
Control/Command for Modbus
SL, page 30
These DFBs enable the user to
read status registers 455 and 456,
write command register 704.
The program number enables the user to select bit or word control.
Comm_manager_tThis DFB is dedicated to the control and command of several TeSys T
LTMR••M•• Modbus SL controllers with or without the LTM E expansion
module. It must be associated with the Ctrl_cmd_mdb_t_•••• DFBs to
Comm_manager_t: TeSys T
Communication Management for
Modbus SL, page 34
manage the Modbus requests sequencing.
It enables the user to
optimize the response time by taking into account the response time
of the devices,
send write requests only when necessary,
manage the disconnection and reconnection of a TeSys U Modbus
slave.
The program number enables the user to select different Modbus
requests sequences.
Modbus SL and Modbus/TCP Library
The following table describes the Modbus SL and Modbus/TCP library:
DFBDescriptionFor More Information
Special_mdb_u_addr
Special_mdb_u_addm
Special_mdb_t_addr
Special_mdb_t_addm
Custom_mdb_addr
Custom_mdb_addm
These DFBs are dedicated to the reading of up to 16 predefined registers
(diagnostic, maintenance, measurement,...) of a TeSys U starter-controller
(up to 32 A/15 kW or 20 hp) with a LUCM multifunction control unit and a
LULC033 Modbus communication module.
The program number enables the user to select the predefined registers.
Special_mdb_u_addr is dedicated to Premium PLC and can be used with
a TeSys U starter-controller connected on Modbus Serial Line or through
a Modbus/TCP gateway.
Special_mdb_u_addm is dedicated to M340 PLC and can be used with
a TeSys U starter-controller connected on Modbus Serial Line or through
a Modbus/TCP gateway.
These DFBs are dedicated to the reading of up to 16 predefined registers
(diagnostic, maintenance, measurement,...) of a TeSys T Modbus SL
controller or TeSys T Modbus/TCP controller with or without the LTM E
expansion module.
The program number enables the user to select the predefined registers.
Special_mdb_t_addr is dedicated to Premium PLC and can be used with
a TeSys T controller LTMR••M•• connected through Modbus Serial Line
or a TeSys T controller LTMR••E•• through a Modbus/TCP network.
Special_mdb_t_addm is dedicated to M340 PLC and can be used with a
TeSys T controller LTMR••M•• connected through Modbus Serial Line or
a TeSys T controller LTMR••E•• through a Modbus/TCP network.
These DFBs are dedicated to the reading of up to 5 sets of registers in one
single TeSys device.
A set of registers is defined by the address of the first register to read and
the length of the set (up to 16 registers per set).
Custom_mdb_addr is dedicated to Premium PLC and can be used with
a TeSys connected through Modbus Serial Line or through a
Modbus/TCP network.
Custom_mdb_addm is dedicated to M340 PLC and can be used with a
TeSys connected through Modbus Serial Line or through a Modbus/TCP
network.
Special_mdb_u_••••: TeSys U
DFB for Modbus SL and
Modbus/TCP, page 40
Special_mdb_t_••••: TeSys T
DFB for Modbus SL and
Modbus/TCP, page 46
Custom_mdb_••••: Custom Read
DFB for Modbus SL and
Modbus/TCP, page 58
14
1672609EN-03 01/2020
Modbus/TCP Quantum Library
The following table describes the Modbus/TCP DFB library dedicated to Quantum PLC:
DFBDescriptionFor More Information
Special_mdb_u_addqThis DFB is dedicated to the reading of up to 16 predefined registers
(diagnostic, maintenance, measurement,...) in a TeSys U starter-controller
(up to 32 A/15 kW or 20 hp) with a LUCM multifunction control unit and a
LULC033 Modbus communication module through a Modbus/TCP gateway
connected to a Quantum PLC.
The program number enables the user to select the predefined registers.
Special_mdb_t_addqThis DFB is dedicated to the reading of up to 16 predefined registers
(diagnostic, maintenance, measurement,...) in a TeSys T Modbus/TCP
LTMR••E•• controller with or without the LTM E expansion module
connected to a Quantum PLC.
The program number enables the user to select the predefined registers.
Custom_mdb_addqThis DFB is dedicated to the reading of up to 5 sets of registers in one single
TeSys device connected through Modbus/TCP to a Quantum PLC.
A set of registers is defined by the address of the first register to read and
the length of the set (up to 16 registers per set).
Special_mdb_u_addq: TeSys U
DFB for Modbus/TCP for
Quantum PLC, page 62
Special_mdb_t_addq: TeSys T
DFB for Modbus/TCP for
Quantum PLC, page 68
Custom_mdb_addq: Custom
Read DFB for Modbus/TCP for
Quantum PLC, page 78
Profibus DP DFB Library
The following table describes the Profibus DP DFB library:
DFBDescriptionFor More Information
Ctrl_pfb_u_msThis DFB is dedicated to the control and command of a single TeSys U
starter-controller with any control unit and a LULC07 Profibus DP
communication module using the Motor Starter profile.
Ctrl_pfb_u_mmsThis DFB is dedicated to the control and command of a single TeSys U
starter-controller (up to 32 A/15 kW or 20 hp) with a LUCM multifunction
control unit and a LULC07 Profibus DP communication module using the
Motor Management Starter profile.
Ctrl_pfb_t_msThis DFB is dedicated to the control and command of a single TeSys T
LTMR••P•• Profibus controller with or without the LTM E expansion module.
Ctrl_pfb_u_ms: TeSys U
Control/Command for Profibus DP
MS, page 82
Ctrl_pfb_u_mms: TeSys U
Control/Command for Profibus DP
MMS, page 84
Ctrl_pfb_t_mms: TeSys T
Control/Command for Profibus DP
MMS, page 86
Introduction
Cyclic Control/Command DFB Library
The following table describes the cyclic control/command (Modbus/TCP (IO scanning), CANopen, and
Advantys STB) DFB library:
DFBDescriptionFor More Information
Ctrl_cmd_uThis DFB is dedicated to the control and command of a single TeSys U
starter-controller with any control unit and a LULC08 CANopen, a LULC15
STB communication module, or a LULC033 Modbus communication
module with an Ethernet gateway.
Ctrl_cmd_tThis DFB is dedicated to the control and command of a single TeSys T
LTMR••C•• CANopen controller or a TeSys T LTMR••E•• Modbus/TCP
controller, with or without the LTM E expansion module.
Ctrl_cmd_u: TeSys U Cyclic
Control/Command, page 90
Ctrl_cmd_t: TeSys T Cyclic
Control/Command, page 92
1672609EN-03 01/202015
Introduction
PKW DFB Library
The following table describes the PKW DFB library:
DFBDescriptionFor More Information
Special_pkw_uThis DFB is dedicated to the reading of up to 16 predefined registers
(diagnostic, maintenance, measurement,...) of a single TeSys U startercontroller (up to 32 A/15 kW or 20 hp) with a LUCM multifunction control
unit and one of the following communication modules that support PKW
exchanges:
The program number enables the user to select the predefined registers.
Special_pkw_tThis DFB is dedicated to the reading of up to 16 predefined registers
(diagnostic, maintenance, measurement,...) of a single TeSys T LTMR••P••
Profibus controller or a LTMR••C•• CANopen controller with or without the
LTM E expansion module.
The program number enables the user to select the predefined registers.
Custom_pkwThis DFB is dedicated to the reading of up to 5 sets of registers of a single
TeSys device supporting PKW exchanges.
A set of registers is defined by the address of the first register to read and
the length of the set (up to 16 registers per set).
Special_pkw_u: TeSys U DFB for
PKW Exchanges, page 96
Special_pkw_t: TeSys T DFB for
PKW Exchanges, page 102
Custom_pkw: Custom Read DFB
for PKW Exchanges, page 113
Treatment DFB Library
The following table describes the treatment DFB library:
DFBDescriptionFor More Information
ScaleThis DFB is dedicated to the conversion of current measurement unit from
Timestamp
Timestamp_q
relative value (% FLA) to Amps for a TeSys U starter-controller (up to
32 A/15 kW or 20 hp) with a LUCM multifunction control unit. It also enables
the user to select another unit in the A...mA range.
These DFBs are dedicated to the time-stamping of up to 8 input registers of
a TeSys U starter-controller (up to 32 A/15 kW or 20 hp) with a LUCM
multifunction control unit. It provides an output table of the 8 time-stamped
registers and 4 date and time registers.
Timestamp is dedicated to Premium and M340 PLCs
Timestamp_q is dedicated to Quantum PLC.
Scale: TeSys U DFB for
Measurement Unit Conversion,
page 118
Timestamp_•: TeSys U DFB for
Data Time-Stamping, page 120
16
1672609EN-03 01/2020
TeSys DFB Sequencing
Introduction
Some of the TeSys DFBs use a sequencing system using dedicated inputs and outputs that enable the
sequencing and the synchronization of the treatment between DFBs.
The following derived function blocks use a sequencing system:
The sequencer has 2 boolean inputs and 3 boolean outputs:
Introduction
The _cmd suffix indicates a command dedicated to the DFB sequencer function.
The _st suffix indicates a status information concerning the DFB sequencer function.
The following table describes the sequencer inputs and outputs:
Input/OutputDescription
Rst_cmdThis command resets the DFB and/or restarts the DFB treatment if Strt_cmd is set to 1.
Strt_cmdThis command starts the DFB treatment.
Fault_stThis status bit indicates
a parameterization error (value out of range),
a communication fault.
If a fault occurs, the applicative boolean outputs are reset to 0, and the output words are forced to –1.
Rst_stThis status bit indicates
a reset in progress,
a treatment in progress.
End_stThis status bit indicates the end of the DFB treatment.
Stand-Alone with Manual Restart
In the stand-alone with manual restart configuration, the DFB is not linked to another DFB and it is activated
each time %M0 is set to 1:
1672609EN-03 01/202017
Introduction
Stand-Alone with Automatic Restart
In the stand-alone with automatic restart configuration, the DFB is not linked to another DFB and it is
activated continuously when %M0 is set to 1:
DFB Chaining with Manual Restart
In the DFB chaining with manual restart configuration, the DFB is linked to other DFBs and it is activated
each time %M0 is set to 1:
18
1672609EN-03 01/2020
DFB Chaining with Automatic Restart
In the DFB chaining with automatic restart configuration, the DFB is linked to other DFBs and it is activated
continuously when %M0 is set to 1:
Introduction
1672609EN-03 01/202019
Introduction
20
1672609EN-03 01/2020
TeSys DFB Library V2 for Unity Pro
Modbus SL DFB
1672609EN-03 01/2020
Modbus SL DFB
Chapter 2
Modbus SL DFB
Introduction
This chapter describes the TeSys U and TeSys T Modbus SL (Serial Line) DFBs.
What Is in This Chapter?
This chapter contains the following topics:
Ctrl_cmd_mdb_u_••••: TeSys U Control/Command for Modbus SL22
Comm_manager_u: TeSys U Communication Management for Modbus SL26
Ctrl_cmd_mdb_t_••••: TeSys T Control/Command for Modbus SL30
Comm_manager_t: TeSys T Communication Management for Modbus SL34
TopicPage
1672609EN-03 01/202021
Modbus SL DFB
Ctrl_cmd_mdb_u_••••: TeSys U Control/Command for Modbus SL
Presentation
The Ctrl_cmd_mdb_u_•••• DFBs are dedicated to the control and command of a single TeSys U startercontroller with any control unit and a LULC033 Modbus communication module through the Modbus SL
(Serial Line) network.
Ctrl_cmd_mdb_u_addr uses XWAY addressing and is dedicated to Premium PLCs.
Ctrl_cmd_mdb_u_addm uses an addressing method dedicated to M340 PLCs.
For more information, see the
Characteristics
CharacteristicValue
NameCtrl_cmd_mdb_u_addrCtrl_cmd_mdb_u_addm
Version1.001.00
Input1111
Output1313
Input/Output00
Public Variable68
TeSys U LULC032-033 Modbus Communication Module User Manual
.
Graphical Representation
TeSys U Compliance
22
The Ctrl_cmd_mdb_u_•••• DFBs are compliant with the following TeSys U sub-assemblies:
Power base LUB•• non-reversing power base
LU2B•• reversing power base
Control unit
Communication module
LUCA standard control unit
LUCB and LUCD advanced control units
LUCC advanced control unit (up to 32 A/15 kW or 20 hp)
LUCL magnetic control unit
LUCM multifunction control unit (up to 32 A/15 kW or 20 hp)
LULC033 Modbus communication module
1672609EN-03 01/2020
Software Implementation
The parameters and the inputs can only be changed if the End_st output variable is set to 1.
The output data is only valid if the End_st output variable is set to 1 and if there is no fault detected
Input Characteristics
The following table describes the DFB inputs and their availability according to the control unit:
Modbus SL DFB
(Fault_st = 0).
InputTypeRangeDefault Value DescriptionLUCA
LUCL
Slav_numINT1...311Modbus slave number√√√
Prog_numINT1...30–See
Rst_cmdEBOOL0...10Reset command√√√
Strt_cmdEBOOL0...10Start command√√√
Run_fwdEBOOL0...10Motor run forward command√√√
Run_revEBOOL0...10Motor run reverse command√√√
Rst_fltEBOOL0...10Reset device (if register 451 = 102 or 104, fault
Rst_warnEBOOL0...10Reset warning (for example, communication
Trip_tstEBOOL0...10Overcurrent trip test via communication bus––√
In_wordINT––This input is only used when program number
Program Number, page 23
acknowledgment causes a return to
communication module factory settings)
loss)
is 10, 20, or 30. See next table and program
number description.
√√√
√√√
√√√
–––
LUCB
LUCC
LUCD
LUCM
The following table describes the In_word input:
InputTypeBitDescriptionLUCA
LUCL
In_wordINT0Motor run forward command√√√
1Motor run reverse command√√√
2Reserved–––
3Reset device (if register 451 = 102 or 104, fault
acknowledgment causes a return to communication module
factory settings)
4Reserved–––
5Automatic thermal overload fault test––√
6Overcurrent trip test via communication bus––√
7Reserved–––
8Reset warning (for example, communication loss)√√√
9...15Reserved–––
√√√
LUCB
LUCC
LUCD
LUCM
Program Number
The program number enables the user to select bit or word control.
The following table describes the programs of the DFB:
Program Number Description
1Read registers 455 and 456, then write register 704 (systematic)
2Read registers 455 and 456, then write register 704 (conditional)
3Write register 704
10Same as program 1 but using the In_word input and the Out_word output
20Same as program 2 but using the In_word input and the Out_word output
30Same as program 3 but using the In_word input and the Out_word output
1672609EN-03 01/202023
Modbus SL DFB
Output Characteristics
The following table describes the DFB outputs and their availability according to the control unit:
OutputTypeRangeDefault
Value
Fault_stEBOOL0...10Fault detected√√√
Rst_stEBOOL0...10Reset state√√√
End_stEBOOL0...10End state√√√
ReadyEBOOL0...10System ready: the rotary handle is turned to On
ClosedEBOOL0...10Pole status: closed√√√
FaultEBOOL0...10All faults√√√
AlarmEBOOL0...10All warnings√√√
TrippedEBOOL0...10System tripped: the rotary handle is turned to
Rst_authEBOOL0...10Fault reset authorized–√√
StartingEBOOL0...10Start in progress:
RunningEBOOL0...10Motor running with detection of current, if
Avg_currINT0...2000Average motor current (x 1% FLA)–√√
Out_wordINT––This output is only used when program number
DescriptionLUCA
LUCL
√√√
position and there is no fault
√√√
Trip position
–√√
0 = descending current is lower than 150% FLA
1 = ascending current is greater than 10% FLA
–√√
greater than 10% FLA
–––
is 10, 20, or 30. See next table and program
number description.
LUCB
LUCC
LUCD
LUCM
The following table describes the Out_word output:
OutputTypeBitDescriptionLUCA
LUCL
Out_wordINT0System ready: the rotary handle is turned to On position and
there is no fault.
1Pole status: closed√√√
2All faults√√√
3All warnings√√√
4System tripped: the rotary handle is turned to Trip position.√√√
5Fault reset authorized–√√
6Reserved–––
7Motor running with detection of current, if greater than
10% FLA
8...13Average motor current (% FLA)
32 = 100% FLA
63 = 200% FLA
14Reserved–––
15Start in progress:
0 = descending current is lower than 150% FLA
1 = ascending current is greater than 10% FLA
√√√
–√√
–√√
–√√
LUCB
LUCC
LUCD
LUCM
24
1672609EN-03 01/2020
Public Variables Characteristics
The following table describes the Ctrl_cmd_mdb_u_addr DFB public variables (using XWAY addressing)
and their availability according to the control unit:
Modbus SL DFB
Public VariableTypeRangeDefault
Value
Net_numINT0...2550Network address√√√
Stat_numINT0...2550Station address√√√
Rack_numINT0...70Destination rack address√√√
Slot_numINT0...100Destination slot address√√√
Chan_numINT0...10Destination channel address√√√
Sq_princINT0...70Reserved for support√√√
DescriptionLUCA
LUCL
LUCB
LUCC
LUCD
The following table describes the Ctrl_cmd_mdb_u_addm DFB public variables (using M340 addressing)
and their availability according to the control unit:
Public VariableTypeRangeDefault
Value
Rack_numINT0...70Destination rack address√√√
Slot_numINT0...100Destination slot address√√√
Chan_numINT0...10Destination channel address√√√
IP_addr1INT0...2550First byte of IP address√√√
IP_addr2INT0...2550Second byte of IP address√√√
IP_addr3INT0...2550Third byte of IP address√√√
IP_addr4INT0...2550Fourth byte of IP address√√√
Sq_princINT0...70Reserved for support√√√
DescriptionLUCA
LUCL
LUCB
LUCC
LUCD
LUCM
LUCM
1672609EN-03 01/202025
Modbus SL DFB
Comm_manager_u: TeSys U Communication Management for Modbus SL
Presentation
The Comm_manager_u DFB is dedicated to the control and command of up to 31 TeSys U startercontrollers with any control unit and a LULC033 Modbus communication module though the Modbus SL
(Serial Line) network. It must be associated with the Ctrl_cmd_mdb_u_•••• DFBs to manage the Modbus
requests sequencing.
The number of TeSys U Modbus slaves is defined in the Slav_num variable (Slav_num = 1...31).
For more information, see the
Characteristics
CharacteristicValue
NameComm_manager_u
Version1.00
Input4
Output4
Input/Output0
Public Variable3
TeSys U LULC032-033 Modbus Communication Module User Manual
.
Graphical Representation
TeSys U Compliance
The Comm_manager_u DFB is compliant with the following TeSys U sub-assemblies:
Power base LUB•• non-reversing power base
Control unit
Communication module
LU2B•• reversing power base
LUCA standard control unit
LUCB and LUCD advanced control units
LUCC advanced control unit (up to 32 A/15 kW or 20 hp)
LUCL magnetic control unit
LUCM multifunction control unit (up to 32 A/15 kW or 20 hp)
LULC033 Modbus communication module
26
1672609EN-03 01/2020
Software Implementation
The following figure shows a Unity Pro program extract in FBD language showing how to interconnect the
Ctrl_cmd_mdb_u_addr and the Comm_manager_u DFBs:
Modbus SL DFB
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Slav_numINT1...311Modbus slave number
Flt_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
In_wordINT––To connect to the Out_word output of the Ctrl_cmd_mdb_u_•••• DFB
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault ValueDescription
Slav_stINT1...311Modbus slave number
Prog_stINT20 or 30–Program number of the Ctrl_cmd_mdb_u_•••• DFB
End_stEBOOL0...10End state
Out_wordINT––To connect to the In_word input of the Ctrl_cmd_mdb_u_•••• DFB
1672609EN-03 01/202027
Modbus SL DFB
Public Variables Characteristics
The following table describes the DFB public variables:
Public VariableTypeRangeDefault ValueDescription
In_cmd[0]...[31]ARRAY [0...31] of INT––See
In_cmd[0]...[31] Public Variable,
page 28
Out_urgINT––Priority level
Out_st[0]...[31]ARRAY [0...31] of INT––See
Bit 0 = Pulling
Bit 1 = Writing priority
Bit 2 = Reading priority
Bit 3 = Fault priority
Out_st[0]...[31] Public Variable,
page 29
In_cmd[0]...[31] Public Variable
The In_cmd[0]...[31] public variable is a table of 32 words corresponding to the TeSys U Modbus slave
address. The following table describes the In_cmd[0]...[31] public variable:
Public VariableTypeBitDescription Corresponding to the TeSys U
Slave 1...31
In_cmd[0]INT–Not significant–––
In_cmd[1]...[31]INT0Motor run forward command√√√
1Motor run reverse command √√√
2Reserved–––
3Reset device
(if register 451 = 102 or 104, fault
acknowledgment causes a return to
communication module factory settings)
4Reserved–––
5Automatic thermal overload fault test––√
6Overcurrent trip test via communication bus––√
7Reserved–––
8Reset warning (for example, communication
loss)
9...15Reserved–––
LUCA
LUCL
√√√
√√√
LUCB
LUCC
LUCD
LUCM
28
1672609EN-03 01/2020
Out_st[0]...[31] Public Variable
The Out_st[0]...[31] public variable is a table of 32 words corresponding to the TeSys U Modbus slave
address.The following table describes the Out_st[0]....[31] public variable:
Modbus SL DFB
Public VariableTypeBitDescription Corresponding to the TeSys U Slave
1...31
Out_st[0]INT–Not significant–––
Out_st[1]...[31]INT0System ready: the rotary handle is turned to On
position and there is no fault.
1Pole status: closed√√√
2All faults√√√
3All warnings√√√
4System tripped: the rotary handle is turned to Trip
position.
5Fault reset is authorized–√√
6Reserved– – –
7Motor running with detection of current, if greater
than 10% FLA
8...13Average motor current (% FLA)
32 = 100% FLA
63 = 200% FLA
14Reserved–––
15Start in progress:
1 = ascending current is greater than 10% FLA
0 = descending current is lower than 150% FLA
LUCA
LUCL
√√ √
√√ √
–√√
–√√
–√√
LUCB
LUCC
LUCD
LUCM
1672609EN-03 01/202029
Modbus SL DFB
Ctrl_cmd_mdb_t_••••: TeSys T Control/Command for Modbus SL
Presentation
The Ctrl_cmd_mdb_t_•••• DFBs are dedicated to the control and command of a single TeSys T LTMR••M••
Modbus SL controller with or without the LTM E expansion module through the Modbus SL network.
Ctrl_cmd_mdb_t_addr uses XWAY addressing and is dedicated to Premium PLCs
Ctrl_cmd_mdb_t_addm uses an addressing method dedicated to M340 PLCs
For more information, see the
Characteristics
CharacteristicValue
NameCtrl_cmd_mdb_t_addrCtrl_cmd_mdb_t_addm
Version1.001.00
Input1010
Output2424
Input/Output00
Public Variable68
Graphical Representation
TeSys T LTMR Modbus Communication Guide
.
30
1672609EN-03 01/2020
Modbus SL DFB
TeSys T Compliance
The Ctrl_cmd_mdb_t_•••• DFBs are compliant with all the TeSys T LTM R••M•• controller versions, with or
without the LTM E expansion module.
Software Implementation
The parameters and the inputs can only be changed if the End_st output variable is set to 1.
The output data is only valid if the End_st output variable is set to 1 and if there is no fault detected
(Fault_st = 0).
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Slav_numINT1...311Modbus slave number
Prog_numINT1...30–See
Rst_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
Run_fwdEBOOL0...10Motor run forward command
Run_revEBOOL0...10Motor run reverse command
Rst_fltEBOOL0...10Fault reset command
AutotestEBOOL0...10Self test command
Lo_speedEBOOL0...10Motor low speed command
In_wordINT––This input is only used when program number is 10, 20,
Program Number, page 31
or 30. See next table and program number description.
The following table describes the In_word input:
InputTypeBitDescription
In_wordINT0Motor run forward command
1Motor run reverse command
2Reserved
3Fault reset command
4Reserved
5Self test command
6Motor low speed command
7...15Reserved
Program Number
The program number enables the user to select bit or word control.
The following table describes the programs of the DFB:
Program Number Description
1Read registers 455 and 456, then write register 704 (systematic)
2Read registers 455 and 456, then write register 704 (conditional)
3Write register 704
10Same as program 1 but using the In_word input and the Out_word output
20Same as program 2 but using the In_word input and the Out_word output
30Same as program 3 but using the In_word input and the Out_word output
1672609EN-03 01/202031
Modbus SL DFB
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault ValueDescription
Fault_stEBOOL0...10Fault detected
Rst_stEBOOL0...10Reset state
End_stEBOOL0...10End state
ReadyEBOOL0...10System ready
Syst_onEBOOL0...10System On
FaultEBOOL0...10System fault
AlarmEBOOL0...10System warning
TrippedEBOOL0...10System tripped
Rst_authEBOOL0...10Fault reset authorized
Ctrl_pwrEBOOL0...10Controller power
RunningEBOOL0...10Motor running (with detection of a current, if greater than 10% FLC)
Avg_currINT0...2000Motor average current ratio (x 1% FLC)
StartingEBOOL0...10Motor starting (start in progress)
0 = descending current is less than 150% FLC
1 = ascending current is greater than 10% FLC
Hi_speedEBOOL0...10Motor high speed
Hmi_ctrlEBOOL0...10Control through HMI
Auto_rstEBOOL0...10Auto-reset active
Pwr_rqstEBOOL0...10Power cycle requested
Rst_TimeEBOOL0...10Motor restart time undefined
Rpd_cyclEBOOL0...10Rapid cycle lockout
Load_shdEBOOL0...10Load shedding
Hmi_lossEBOOL0...10HMI port communication loss
Net_lossEBOOL0...10Network port communication loss
Motor_trEBOOL0...10Motor transition lockout
Out_wordDINT––This output is only used when program number is 10, 20, or 30. See
next table and program number description.
32
1672609EN-03 01/2020
The following table describes the Out_word output:
OutputTypeBitDescription
Out_wordDINT0System ready
1System On
2System fault
3System warning
4System tripped
5Fault reset authorized
6Controller power
7Motor running (with detection of a current, if greater than 10%FLC)
8...13Motor average current ratio
32 = 100% FLC
63 = 200% FLC
14Control through HMI
15Motor starting (start in progress)
0 = descending current is less than 150% FLC
1 = ascending current is greater than 10% FLC
16Auto-reset active
17Not significant
18Power cycle requested
19Motor restart time undefined
20Rapid cycle lockout
21Load shedding
22Motor speed
0 = FLC1 setting is used
1 = FLC2 setting is used
23HMI port communication loss
24Network port communication loss
25Motor transition lockout
26...31Not significant
Modbus SL DFB
Public Variables Characteristics
The following table describes the Ctrl_cmd_mdb_t_addr DFB public variables (using XWAY addressing):
Public VariableTypeRangeDefault ValueDescription
Net_numINT0...2550Network address
Stat_numINT0...2550Station address
Rack_numINT0...70Destination rack address
Slot_numINT0...100Destination slot address
Chan_numINT0...10Destination channel address
Sq_princINT0...70Reserved for support
The following table describes the Ctrl_cmd_mdb_t_addm DFB public variables (using M340 addressing):
Public VariableTypeRangeDefault ValueDescription
Rack_numINT0...70Destination rack address
Slot_numINT0...100Destination slot address
Chan_numINT0...10Destination channel address
IP_addr1INT0...2550First byte of IP address
IP_addr2INT0...2550Second byte of IP address
IP_addr3INT0...2550Third byte of IP address
IP_addr4INT0...2550Fourth byte of IP address
Sq_princINT0...70Reserved for support
1672609EN-03 01/202033
Modbus SL DFB
Comm_manager_t: TeSys T Communication Management for Modbus SL
Presentation
The Comm_manager_t DFB is dedicated to the control and command of up to 31 TeSys T LTMR••M••
Modbus SL controllers with or without the LTM E expansion module through the Modbus SL network. It
must be associated with the Ctrl_cmd_mdb_t_•••• DFB to manage the Modbus requests sequencing.
The number of TeSys T Modbus slaves is define din the Slav_num variable (Slav_num = 1...31).
For more information, see the
Characteristics
CharacteristicValue
NameComm_manager_t
Version1.0
Input4
Output4
Input/Output0
Public Variable3
Graphical Representation
TeSys T LTMR Modbus Communication Guide
.
TeSys T Compliance
The Comm_manager_t DFB is compliant with all the TeSys T LTM R••M•• controller versions, with or
without the LTM E expansion module.
34
1672609EN-03 01/2020
Software Implementation
The following figure shows a Unity Pro program extract in FBD language showing how to interconnect the
Ctrl_cmd_mdb_t and the Comm_manager_t DFBs:
Modbus SL DFB
The Comm_manager_t DFB can be used in case both TeSys U starter-controllers and TeSys T motor
management systems are present on the same Modbus SL network.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Slav_numINT1...311Modbus slave number
Flt_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
In_wordDINT––To connect to the Out_word output of the Ctrl_cmd_mdb_t_••••
1672609EN-03 01/202035
DFB
Modbus SL DFB
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault ValueDescription
Slav_stINT1...311Modbus slave number
Prog_stINT20 or 30–Program number of the Ctrl_cmd_mdb_t_•••• DFB
End_stEBOOL0...10End state
Out_wordINT––To connect to the In_word input of the Ctrl_cmd_mdb_t_••••
DFB
Public Variables Characteristics
The following table describes the DFB public variables:
Public VariableTypeRangeDefault ValueDescription
In_cmd[0]...[31]ARRAY [0...31] of INT––See
Out_urgINT––Priority level
Out_st[0]...[31]ARRAY [0...31] of DINT––See
In_cmd[0]...[31] Public Variable, page 36
Bit 0 = Pulling
Bit 1 = Writing priority
Bit 2 = Reading priority
Bit 3 = Fault priority
Out_st[0]...[31] Public Variable, page 37
In_cmd[0]...[31] Public Variable
The In_cmd[0]...[31] public variable is a table of 32 words corresponding to the TeSys T Modbus slave
address. The following table describes the In_cmd[0]...[31] public variable:
Public VariableTypeBitDescription Corresponding to the TeSys T Slave 1...31
In_cmd[0]INT–Not significant
In_cmd[1]...[31]INT0Motor run forward command
1Motor run reverse command
2Reserved
3Fault reset command
4Reserved
5Self test command
6Motor low speed command
7...31Reserved
36
1672609EN-03 01/2020
Out_st[0]...[31] Public Variable
The Out_st[0]...[31] public variable is a table of 32 words corresponding to the TeSys T Modbus slave
address.The following table describes the Out_st[0]....[31] public variable:
Public VariableTypeBitDescription Corresponding to the TeSys T
Slave 1...31
Out_st[0]DINT–Not significant
Out_st[1]...[31]DINT0System ready
1System On
2System fault
3System warning
4System tripped
5Fault reset authorized
6Controller power
7Motor running (with detection of a current, if greater than 10%FLC)
8...13Motor average current ratio
32 = 100% FLC
63 = 200% FLC
14Control through HMI
15Motor starting (start in progress)
0 = descending current is less than 150% FLC
1 = ascending current is greater than 10% FLC
16Auto-reset active
17Not significant
18Power cycle requested
19Motor restart time undefined
20Rapid cycle lockout
21Load shedding
22Motor speed
0 = FLC1 setting is used
1 = FLC2 setting is used
23HMI port communication loss
24Network port communication loss
25Motor transition lockout
26...31Not significant
Modbus SL DFB
1672609EN-03 01/202037
Modbus SL DFB
The Out_st[0]...[31] public variable is a table of 32 words corresponding to the TeSys T Modbus slave
address.The following table describes the Out_st[0]....[31] public variable:
Public VariableTypeBitDescription Corresponding to the TeSys T
Slave 1...31
Out_st[0]DINT–Not significant
Out_st[1]...[31]DINT0System ready
1System On
2System fault
3System warning
4System tripped
5Fault reset authorized
6Controller power
7Motor running (with detection of a current, if greater than 10%FLC)
8...13Motor average current ratio
32 = 100% FLC
63 = 200% FLC
14Control through HMI
15Motor starting (start in progress)
0 = descending current is less than 150% FLC
1 = ascending current is greater than 10% FLC
16Auto-reset active
17Not significant
18Power cycle requested
19Motor restart time undefined
20Rapid cycle lockout
21Load shedding
22Motor speed
0 = FLC1 setting is used
1 = FLC2 setting is used
23HMI port communication loss
24Network port communication loss
25Motor transition lockout
26...31Not significant
38
1672609EN-03 01/2020
TeSys DFB Library V2 for Unity Pro
Modbus SL and Modbus/T CP DFB
1672609EN-03 01/2020
Modbus SL and Modbus/TCP DFB
Chapter 3
Modbus SL and Modbus/TCP DFB
Introduction
This chapter describes the TeSys U and TeSys T Modbus SL and Modbus/TCP DFBs dedicated to
Premium and M340 PLCs.
What Is in This Chapter?
This chapter contains the following topics:
Special_mdb_u_••••: TeSys U DFB for Modbus SL and Modbus/TCP40
Special_mdb_t_••••: TeSys T DFB for Modbus SL and Modbus/TCP46
Custom_mdb_••••: Custom Read DFB for Modbus SL and Modbus/TCP58
TopicPage
1672609EN-03 01/202039
Modbus SL and Modbus/TCP DFB
Special_mdb_u_••••: TeSys U DFB for Modbus SL and Modbus/TCP
Presentation
The Special_mdb_u_•••• DFBs are dedicated to the reading of up to 16 predefined registers of a TeSys U
starter-controller (up to 32 A/15 kW or 20 hp) equipped with a LUCM multifunction control unit and a
LULC033 Modbus communication module directly through a Modbus SL network or through an Ethernet
gateway with a Modbus/TCP network.
Special_mdb_u_addr uses XWAY addressing and is dedicated to Premium PLCs and can be used with
a TeSys U starter-controller connected on Modbus Serial Line or through a Modbus/TCP gateway.
Special_mdb_u_addm uses an addressing method dedicated to M340 PLCs and can be used with a
TeSys U starter-controller connected on Modbus Serial Line or through a Modbus/TCP gateway.
For more information, see the
Characteristics
CharacteristicValue
NameSpecial_mdb_u_addrSpecial_mdb_u_addm
Version1.00 and 1.101.00 and 1.10
Input44
Output33
Input/Output00
Public Variable79
TeSys U LULC032-033 Modbus Communication Module User Manual
.
Graphical Representation
TeSys U Compliance
The Special_mdb_u_•••• DFBs are compliant with the following TeSys U sub-assemblies:
Power base LUB•• non-reversing power base (up to 32 A/15 kW or 20 hp)
Control unit
Communication module
Software Implementation
The parameters and the inputs can only be changed if the End_st output variable is set to 1.
With version 1.00:
The output data is only valid if the End_st output variable is set to 1 and if there is no fault detected
(Fault_st = 0).
With version 1.10:
The output data is only valid if there is no fault detected (Fault_st = 0).
Prog_num input can be modified on the fly.
LU2B•• reversing power base (up to 32 A/15 kW or 20 hp)
LUCM multifunction control unit
LULC033 Modbus communication module
40
1672609EN-03 01/2020
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Slav_numINT1...311Modbus slave number
Prog_numINT0...60Program number
See
Program Number, page 41
Rst_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault ValueDescription
Fault_stEBOOL0...10Fault detected
Rst_stEBOOL0...10Reset state
End_stEBOOL0...10End state
Program Number
The Prog_num input variable enables the user to define the public variables data depending on the
application type. Each program uses variables related to one application (diagnostic, maintenance,
measurement,...). The following table describes the programs of the DFB:
Modbus SL and Modbus/TCP DFB
Program Number Description
0Bypass: no action
1Diagnostic: faults monitoring variables, warnings monitoring variables, and communication monitoring variables
2Maintenance: global statistics variables
3Measurements: measurements monitoring variables
4Statistics: last trip statistics and trip N–1 statistics
5Statistics: trip N–2 statistics and trip N–3 statistics
6Statistics: trip N–4 statistics
Public Variables Characteristics
The following table describes the Special_mdb_u_addr DFBs public variables (using XWAY addressing):
Public VariableTypeRangeDefault ValueDescription
Net_numINT0...2550Network address
Stat_numINT0...2550Station address
Rack_numINT0...70Destination rack address
Slot_numINT0...100Destination slot address
Chan_numINT0...10Destination channel address
Sq_princINT0...70Reserved for support
Out_data[0]...[15]ARRAY [0...15] of
INT
0...655350The output data depends on the program number.
Out_data[0]...[15] Public Variable (Program
See
1), page 42
...
Out_data[0]...[15] Public Variable
(Program 6), page 45
The following table describes the Special_mdb_u_addm DFB public variables (using M340 addressing):
Public VariableTypeRangeDefault ValueDescription
Rack_numINT0...70Destination rack address
Slot_numINT0...100Destination slot address
Chan_numINT0...10Destination channel address
IP_addr1INT0...2550First byte of IP address
IP_addr2INT0...2550Second byte of IP address
IP_addr3INT0...2550Third byte of IP address
1672609EN-03 01/202041
Modbus SL and Modbus/TCP DFB
Public VariableTypeRangeDefault ValueDescription
IP_addr4INT0...2550Fourth byte of IP address
Sq_princINT0...70Reserved for support
Out_data[0]...[15]ARRAY [0...15] of INT 0...655350The output data depends on the program number.
Out_data[0]...[15] Public Variable (Program 1),
See
page 42
...
Out_data[0]...[15] Public Variable
(Program 6), page 45
Out_data[0]...[15] Public Variable (Program 1)
The following table describes the Out_data[0]...[15] public variable in the case of the diagnostic program
(program number 1):
Public VariableTypeRegisterBitDescription
Out_data[0]INT4520Short-circuit fault
1Magnetic fault
2Ground fault
3Thermal fault
4Long start fault
5Jam fault
6Phase imbalance fault
7Underload fault
8Shunt trip fault
9Test trip fault
10Communication loss fault on LUCM Modbus port
11Control unit internal fault
12Module identification or internal communication fault
13Module internal fault
14Module trip fault
15Module drop-out fault
Out_data[1]INT4610...1Not significant
2Ground fault warning
3Thermal warning
4Long start warning
5Jam warning
6Phase imbalance warning
7Under-current warning
8...9Not significant
10Communication loss fault on LUCM Modbus port
11Internal temperature warning
12Module identification or internal communication warning
13...14Not significant
15Module warning
Out_data[2]INT4570Button position On (0 = Off)
1Button position Trip (0 = Not tripped)
2Contactor state On
324 Vdc power supply present on outputs
4...15Not significant
Out_data[3]INT450–Time to automatic reset on a thermal fault (s)
Out_data[4]
...Out_data[15]
–––Not significant
42
1672609EN-03 01/2020
Out_data[0]...[15] Public Variable (Program 2)
The following table describes the Out_data[0]...[15] public variable in the case of the maintenance program
(program number 2):
Public VariableTypeRegisterDescription
Out_data[0]INT100Short-circuit faults count
Out_data[1]INT101Magnetic faults count
Out_data[2]INT102Ground faults count
Out_data[3]INT103Thermal faults count
Out_data[4]INT104Long start faults count
Out_data[5]INT105Jam faults count
Out_data[6]INT106Phase imbalance faults count
Out_data[7]INT108Shunt trip faults count
Out_data[8]INT115Auto-resets count
Out_data[9]INT116Thermal warnings count
Out_data[10]INT117Starts count (LSB)
Out_data[11]INT118Starts count (MSB)
Out_data[12]INT119Operating time (LSB)
Out_data[13]INT120Operating time (MSB)
Out_data[14]INT121Maximum internal temperature (°C)
Out_data[15]––Not significant
Modbus SL and Modbus/TCP DFB
Out_data[0]...[15] Public Variable (Program 3)
The following table describes the Out_data[0]...[15] public variable in the case of the measurements
program (program number 3):
Public VariableTypeRegisterDescription
Out_data[0]––Not significant
Out_data[1]INT465Thermal capacity level (%)
Out_data[2]INT466Average motor current (x 0.1 % FLA)
Out_data[3]INT467L1 current (% FLA)
Out_data[4]INT468L2 current (% FLA)
Out_data[5]INT469L3 current (% FLA)
Out_data[6]INT470Ground current (% FLA min)
Out_data[7]INT471Current imbalance coefficient
Out_data[8]INT472Control unit internal temperature (°C)
Out_data[9]
...Out_data[13]
Out_data[14]INT79Control unit sensor maximum current (x 0.1 A):
6 = adjustment range 0.15–0.6 A
14 = adjustment range 0.35–.4 A
50 = adjustment range 1.25–5 A
120 = adjustment range 3–12 A
180 = adjustment range 4.5–18 A
320 = adjustment range 8–32 A
minimum = 25 (default value)
maximum = 100
1672609EN-03 01/202043
Modbus SL and Modbus/TCP DFB
Out_data[0]...[15] Public Variable (Program 4)
The following table describes the Out_data[0]...[15] public variable in the case of the statistics program
(program number 4):
6 = adjustment range 0.15–0.6 A
14 = adjustment range 0.35–1.4 A
50 = adjustment range 1.25–5 A
120 = adjustment range 3–12 A
180 = adjustment range 4.5–18 A
320 = adjustment range 8–32 A
minimum = 25 (default value)
maximum = 100
44
1672609EN-03 01/2020
Out_data[0]...[15] Public Variable (Program 5)
The following table describes the Out_data[0]...[15] public variable in the case of the statistics program
(program number 5):
Out_data[13]INT247N–3 trip ground current (% FLA min)
Out_data[14]INT79Control unit sensor maximum current (x 0.1 A):
6 = adjustment range 0.15–0.6 A
14 = adjustment range 0.35–1.4 A
50 = adjustment range 1.25–5 A
120 = adjustment range 3–12 A
180 = adjustment range 4.5–18 A
320 = adjustment range 8–32 A
6 = adjustment range 0.15–0.6 A
14 = adjustment range 0.35–1.4 A
50 = adjustment range 1.25–5 A
120 = adjustment range 3–12 A
180 = adjustment range 4.5–18 A
320 = adjustment range 8–32 A
minimum = 25 (default value)
maximum = 100
1672609EN-03 01/202045
Modbus SL and Modbus/TCP DFB
Special_mdb_t_••••: TeSys T DFB for Modbus SL and Modbus/TCP
Presentation
The Special_mdb_t_•••• DFBs are dedicated to the reading of up to 16 predefined registers of a TeSys T
LTM R••M•• controller through the Modbus SL network or a TeSys T LTM R••E•• controller through the
Modbus/TCP network.
Special_mdb_t_addr uses XWAY addressing and is dedicated to Premium PLCs.
Special_mdb_t_addm uses an addressing method dedicated to M340 PLCs.
For more information, see:
TeSys T LTM R Modbus Communication Guide
TeSys T LTM R Ethernet Communication Guide
Characteristics
CharacteristicValue
NameSpecial_mdb_t_addrSpecial_mdb_t_addm
Version1.00 and 1.101.00 and 1.10
Input44
Output33
Input/Output00
Public Variable79
Graphical Representation
TeSys T Compliance
The Special_mdb_t_•••• DFBs are compliant with all the TeSys T LTM R••M•• and LTM R••E•• controller
versions, with or without the LTM E expansion module.
Software Implementation
The parameters and the inputs can only be changed if the End_st output variable is set to 1.
With version 1.00:
The output data is only valid if the End_st output variable is set to 1 and if there is no fault detected
(Fault_st = 0).
With version 1.10:
The output data is only valid if there is no fault detected (Fault_st = 0).
Prog_num input can be modified on the fly.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Slav_numINT1...311Modbus slave number
Prog_numINT0...60Program number
Rst_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
46
Program Number, page 47
See
1672609EN-03 01/2020
Modbus SL and Modbus/TCP DFB
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault ValueDescription
Fault_stEBOOL0...10Fault detected
Rst_stEBOOL0...10Reset state
End_stEBOOL0...10End state
Program Number
The Prog_num input variable enables the user to define the public variables data depending on the
application type. Each program holds variables related to one application (diagnostic, maintenance,
measurement,...). The following table describes the programs of the DFB:
Program Number Description
0Bypass: no action
10Diagnostic: faults monitoring variables, warnings monitoring variables, and communication monitoring variables
20Maintenance: global statistics variables
30Measurements 1
31Measurements 2
32Measurements 3
40Statistics: last fault statistics (N–0)
41Statistics: last fault statistics with expansion module (N–0)
Out_data[3]INT153Average current ratio N–0 (% FLC)
Out_data[4]INT154L1 current ratio N–0 (% FLC)
Out_data[5]INT155L2 current ratio N–0 (% FLC)
Out_data[6]INT156L3 current ratio N–0 (% FLC)
Out_data[7]INT157Ground current ratio N–0 (x 0.1 % FLC min)
Out_data[8]INT158Full load current max N–0 (x 0.1 A)
Out_data[9]INT159Current phase imbalance N–0 (%)
Out_data[10]INT160Frequency N–0 (x 0.1 Hz)
Out_data[11]INT161Motor temperature sensor N–0 (x 0.1 Ω)
Out_data[12]WORD[4]162Date and time N–0
Out_data[13]163
Out_data[14]164
Out_data[15]165
DT_DateTime, page 111
See
Out_data[0]...[15] Public Variable (Program 41)
The following table describes the Out_data[0]...[15] public variable in the case of the last fault statistics with
expansion module program (program number 41):
Public VariableTypeRegisterDescription
Out_data[0]INT166Average voltage N–0 (V)
Out_data[1]INT167L3–L1 voltage N–0 (V)
Out_data[2]INT168L1–L2 voltage N–0 (V)
Out_data[3]INT169L2–L3 voltage N–0 (V)
Out_data[4]INT170Voltage phase imbalance N–0 (%)
Out_data[5]INT171Active power N–0 (kW)
Out_data[6]INT172Power factor N–0 (x 0.01)
Out_data[7] ...Out_data[15] ––Reserved
52
1672609EN-03 01/2020
Modbus SL and Modbus/TCP DFB
Out_data[0]...[15] Public Variable (Program 50)
The following table describes the Out_data[0]...[15] public variable in the case of the N–1 fault statistics
program (program number 50):
Public VariableTypeRegisterDescription
Out_data[0]INT180Detected fault code N–1
Out_data[1]INT181Motor full load current ratio N–1 (% FLC max)
Out_data[3]INT183Average current ratio N–1 (% FLC)
Out_data[4]INT184L1 current ratio N–1 (% FLC)
Out_data[5]INT185L2 current ratio N–1 (% FLC)
Out_data[6]INT186L3 current ratio N–1 (% FLC)
Out_data[7]INT187Ground current ratio N–1 (x 0.1 % FLC min)
Out_data[8]INT188Full load current max N–1 (x 0.1 A)
Out_data[9]INT189Current phase imbalance N–1 (%)
Out_data[10]INT190Frequency N–1 (x 0.1 Hz)
Out_data[11]INT191Motor temperature sensor N–1 (x 0.1 Ω)
Out_data[12]WORD[4]192Date and time N–1
DT_DateTime, page 111
Out_data[13]193
Out_data[14]194
Out_data[15]195
See
Out_data[0]...[15] Public Variable (Program 51)
The following table describes the Out_data[0]...[15] public variable in the case of the N–1 fault statistics
with expansion module program (program number 51):
Public VariableTypeRegisterDescription
Out_data[0]INT196Average voltage N–1 (V)
Out_data[1]INT197L3–L1 voltage N–1 (V)
Out_data[2]INT198L1–L2 voltage N–1 (V)
Out_data[3]INT199L2–L3 voltage N–1 (V)
Out_data[4]INT200Voltage phase imbalance N–1 (%)
Out_data[5]INT201Active power N–1 (kW)
Out_data[6]INT202Power factor N–1 (x 0.01)
Out_data[7]
...Out_data[15]
––Reserved
1672609EN-03 01/202053
Modbus SL and Modbus/TCP DFB
Out_data[0]...[15] Public Variable (Program 60)
The following table describes the Out_data[0]...[15] public variable in the case of the N–2 fault statistics
program (program number 60):
Public VariableTypeRegisterDescription
Out_data[0]INT210Detected fault code N–2
Out_data[1]INT211Motor full load current ratio N–2 (% FLC max)
Out_data[3]INT213Average current ratio N–2 (% FLC)
Out_data[4]INT214L1 current ratio N–2 (% FLC)
Out_data[5]INT215L2 current ratio N–2 (% FLC)
Out_data[6]INT216L3 current ratio N–2 (% FLC)
Out_data[7]INT217Ground current ratio N–2 (x 0.1 % FLC min)
Out_data[8]INT218Full load current max N–2 (x 0.1 A)
Out_data[9]INT219Current phase imbalance N–2 (%)
Out_data[10]INT220Frequency N–2 (x 0.1 Hz)
Out_data[11]INT221Motor temperature sensor N–2 (x 0.1 Ω)
Out_data[12]WORD[4]222Date and time N–2
DT_DateTime, page 111
Out_data[13]223
Out_data[14]224
Out_data[15]225
See
Out_data[0]...[15] Public Variable (Program 61)
The following table describes the Out_data[0]...[15] public variable in the case of the N–2 fault statistics
with expansion module program (program number 61):
Public VariableTypeRegisterDescription
Out_data[0]INT226Average voltage N–2 (V)
Out_data[1]INT227L3–L1 voltage N–2 (V)
Out_data[2]INT228L1–L2 voltage N–2 (V)
Out_data[3]INT229L2–L3 voltage N–2 (V)
Out_data[4]INT230Voltage phase imbalance N–2 (%)
Out_data[5]INT231Active power N–2 (kW)
Out_data[6]INT232Power factor N–2 (x 0.01)
Out_data[7]
...Out_data[15]
––Reserved
54
1672609EN-03 01/2020
Out_data[0]...[15] Public Variable (Program 70)
The following table describes the Out_data[0]...[15] public variable in the case of the N–3 fault statistics
program (program number 70):
Public VariableTypeRegisterDescription
Out_data[0]INT240Detected fault code N–3
Out_data[1]INT241Motor full load current ratio N–3 (% FLC max)
Out_data[3]INT243Average current ratio N–3 (% FLC)
Out_data[4]INT244L1 current ratio N–3 (% FLC)
Out_data[5]INT245L2 current ratio N–3 (% FLC)
Out_data[6]INT246L3 current ratio N–3 (% FLC)
Out_data[7]INT247Ground current ratio N–3 (x 0.1 % FLC min)
Out_data[8]INT248Full load current max N–3 (x 0.1 A)
Out_data[9]INT249Current phase imbalance N–3 (%)
Out_data[10]INT250Frequency N–3 (x 0.1 Hz)
Out_data[11]INT251Motor temperature sensor N–3 (x 0.1 Ω)
Out_data[12]WORD[4]252Date and time N–3
DT_DateTime, page 111
Out_data[13]253
Out_data[14]254
Out_data[15]255
See
Modbus SL and Modbus/TCP DFB
Out_data[0]...[15] Public Variable (Program 71)
The following table describes the Out_data[0]...[15] public variable in the case of the N–3 fault statistics
with expansion module program (program number 71):
Public VariableTypeRegisterDescription
Out_data[0]INT256Average voltage N–3 (V)
Out_data[1]INT257L3–L1 voltage N–3 (V)
Out_data[2]INT258L1–L2 voltage N–3 (V)
Out_data[3]INT259L2–L3 voltage N–3 (V)
Out_data[4]INT260Voltage phase imbalance N–3 (%)
Out_data[5]INT261Active power N–3 (kW)
Out_data[6]INT262Power factor N–3 (x 0.01)
Out_data[7]
...Out_data[15]
––Reserved
1672609EN-03 01/202055
Modbus SL and Modbus/TCP DFB
Out_data[0]...[15] Public Variable (Program 80)
The following table describes the Out_data[0]...[15] public variable in the case of the N–4 fault statistics
program (program number 80):
Public VariableTypeRegisterDescription
Out_data[0]INT270Detected fault code N–4
Out_data[1]INT271Motor full load current ratio N–4 (% FLC max)
Out_data[3]INT273Average current ratio N–4 (% FLC)
Out_data[4]INT274L1 current ratio N–4 (% FLC)
Out_data[5]INT275L2 current ratio N–4 (% FLC)
Out_data[6]INT276L3 current ratio N–4 (% FLC)
Out_data[7]INT277Ground current ratio N–4 (x 0.1 % FLC min)
Out_data[8]INT278Full load current max N–4 (x 0.1 A)
Out_data[9]INT279Current phase imbalance N–4 (%)
Out_data[10]INT280Frequency N–4 (x 0.1 Hz)
Out_data[11]INT281Motor temperature sensor N–4 (x 0.1 Ω)
Out_data[12]WORD[4]282Date and time N–4
DT_DateTime, page 111
Out_data[13]283
Out_data[14]284
Out_data[15]285
See
56
1672609EN-03 01/2020
Out_data[0]...[15] Public Variable (Program 81)
The following table describes the Out_data[0]...[15] public variable in the case of the N–4 fault statistics
with expansion module program (program number 81):
Public VariableTypeRegisterDescription
Out_data[0]INT286Average voltage N–4 (V)
Out_data[1]INT287L3–L1 voltage N–4 (V)
Out_data[2]INT288L1–L2 voltage N–4 (V)
Out_data[3]INT289L2–L3 voltage N–4 (V)
Out_data[4]INT290Voltage phase imbalance N–4 (%)
Out_data[5]INT291Active power N–4 (kW)
Out_data[6]INT292Power factor N–4 (x 0.01)
Out_data[7]
...Out_data[15]
––Reserved
Modbus SL and Modbus/TCP DFB
1672609EN-03 01/202057
Modbus SL and Modbus/TCP DFB
Custom_mdb_••••: Custom Read DFB for Modbus SL and Modbus/TCP
Presentation
The Custom_mdb_•••• DFBs are dedicated to the reading of up to 5 sets of registers in one single TeSys
device through the Modbus SL or Modbus/TCP networks.
Custom_mdb_addr uses XWAY addressing and is dedicated to Premium PLCs.
Custom_mdb_addm uses an addressing method dedicated to M340 PLCs.
The Custom_mdb_•••• DFBs complete the Special_mdb_u_•••• and Special_mdb_t_•••• DFBs and enable
the user to select the registers to read.
Characteristics
CharacteristicValue
NameCustom_mdb_addrCustom_mdb_addm
Version1.00 and 1.101.00 and 1.10
Input33
Output33
Input/Output00
Public Variable1315
Graphical Representation
TeSys U and TeSys T Compliance
TeSys U: The Custom_mdb_•••• DFBs are compliant with the following TeSys U sub-assemblies:
LUB•• non-reversing power base and LU2B•• reversing power base (upto32A/15kW or 20hp)
LUCM multifunction control unit
LULC033 Modbus communication module
TeSys T: The Custom_mdb_•••• DFBs are compliant with all the LTM R••M•• and LTM R••E•• controller
versions, with or without the LTM E expansion module.
Software Implementation
The parameters and the inputs can only be changed if the End_st output variable is set to 1.
With version 1.00:
The output data is only valid if the End_st output variable is set to 1 and if there is no fault detected
(Fault_st = 0).
With version 1.10:
The output data is only valid if there is no fault detected (Fault_st = 0).
Prog_num input can be modified on the fly.
The public variables enable the user to read up to 5 sets of registers of a maximum length of 16 registers
for each set:
The user defines the starting point of a set of registers with the In_reg public variable.
The user defines the length of the set of registers with the corresponding In_len public variable.
The registers content is then returned in the corresponding Out_dat public variable.
58
1672609EN-03 01/2020
Input Characteristics
Modbus SL and Modbus/TCP DFB
The following table describes the DFB inputs:
InputTypeRangeDefault
Value
Slav_numINT1...311Modbus slave number
Rst_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
Description
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault
Value
Fault_stEBOOL0...10Fault detected
Rst_stEBOOL0...10Reset state
End_stEBOOL0...10End state
Description
Public Variables Characteristics
The following table describes the Custom_mdb_addr DFB public variables (using XWAY addressing):
Public VariableTypeRangeDefault
Value
Net_numINT0...2550Network address
Stat_numINT0...2550Station address
Rack_numINT0...70Destination rack address
Slot_numINT0...100Destination slot address
Chan_numINT0...10Destination channel address
In_regARRAY[0...4] of INT0...655350Array of 5 words for the 5 index registers
In_lenARRAY[0...4] of INT0...160Array of 5 words for the length of each set of registers
Out_dat[0]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[0] words
Out_dat[1]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[1] words
Out_dat[2]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[2] words
Out_dat[3]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[3] words
Out_dat[4]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[4] words
Sq_princINT0...70Reserved for support
Description
(In_reg[0]...In_reg[4])
(In_len[0]...In_len[4])
starting from In_reg[0]
starting from In_reg[1]
starting from In_reg[2]
starting from In_reg[3]
starting from In_reg[4]
The following table describes the Custom_mdb_addm DFB public variables (using M340 addressing):
Public VariableTypeRangeDefault Value Description
Rack_numINT0...70Destination rack address
Slot_numINT0...100Destination slot address
Chan_numINT0...10Destination channel address
IP_addr1INT0...2550First byte of IP address
IP_addr2INT0...2550Second byte of IP address
IP_addr3INT0...2550Third byte of IP address
IP_addr4INT0...2550Fourth byte of IP address
In_regARRAY[0...4] of INT0...655350Array of 5 words for the 5 index registers
1672609EN-03 01/202059
(In_reg[0]...In_reg[4])
Modbus SL and Modbus/TCP DFB
Public VariableTypeRangeDefault Value Description
In_lenARRAY[0...4] of INT0...160Array of 5 words for the length of each set of registers
(In_len[0]...In_len[4])
Out_dat[0]ARRAY[0...15] of INT0...2550Array of up to 16 words containing the In_len[0] words
starting from In_reg[0]
Out_dat[1]ARRAY[0...15] of INT0...2550Array of up to 16 words containing the In_len[1] words
starting from In_reg[1]
Out_dat[2]ARRAY[0...15] of INT0...2550Array of up to 16 words containing the In_len[2] words
starting from In_reg[2]
Out_dat[3]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[3] words
starting from In_reg[3]
Out_dat[4]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[4] words
starting from In_reg[4]
Sq_princINT0...70Reserved for support
60
1672609EN-03 01/2020
TeSys DFB Library V2 for Unity Pro
Modbus/TCP DFB for Quantum PLC
1672609EN-03 01/2020
Modbus/TCP DFB for Quantum PLC
Chapter 4
Modbus/TCP DFB for Quantum PLC
Introduction
This chapter describes the TeSys U and TeSys T Modbus/TCP DFBs dedicated to Quantum PLC.
What Is in This Chapter?
This chapter contains the following topics:
Special_mdb_u_addq: TeSys U DFB for Modbus/TCP for Quantum PLC62
Special_mdb_t_addq: TeSys T DFB for Modbus/TCP for Quantum PLC68
Custom_mdb_addq: Custom Read DFB for Modbus/TCP for Quantum PLC78
TopicPage
1672609EN-03 01/202061
Modbus/TCP DFB for Quantum PLC
Special_mdb_u_addq: TeSys U DFB for Modbus/TCP for Quantum PLC
Presentation
The Special_mdb_u_addq DFBs are dedicated to the reading of up to 16 predefined registers of a TeSys U
starter-controller (up to 32 A/15 kW or 20 hp) equipped with a LUCM multifunction control unit and a
LULC033 Modbus communication module through an Ethernet gateway with a Modbus/TCP network
connected to a Quantum PLC.
For more information, see the
Characteristics
CharacteristicValue
NameSpecial_mdb_u_addq
Version1.00
Input4
Output5
Input/Output0
Public Variable7
Graphical Representation
TeSys U LULC032-033 Modbus Communication Module User Manual
.
TeSys U Compliance
The Special_mdb_u_addq DFBs are compliant with the following TeSys U sub-assemblies:
Power base LUB•• non-reversing power base (up to 32 A/15 kW or 20 hp)
LU2B•• reversing power base (up to 32 A/15 kW or 20 hp)
Control unit
Communication module
LUCM multifunction control unit
LULC033 Modbus communication module connected through an Ethernet gateway
Software Implementation
The parameters and the inputs can only be changed if the End_st output variable is set to 1.
The output data is only valid if there is no fault detected (Fault_st = 0).
Prog_num input can be modified on the fly.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Slav_numINT1...311Modbus address of the slave connected to the gateway
Prog_numINT0...60Program number
Rst_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
Program Number, page 41
See
62
1672609EN-03 01/2020
Modbus/TCP DFB for Quantum PLC
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault ValueDescription
ControlARRAY [1...9] of INT0...655350For internal use of the DFB.
DatabufANY_ARRAY_INT0...655350For internal use of the DFB.
Fault_stEBOOL0...10Fault detected
Rst_stEBOOL0...10Reset state
End_stEBOOL0...10End state
Must be linked to an array of 9 located words (%MW)
Must be linked to an array of 38 located words minimum
(%MW)
Program Number
The Prog_num input variable enables the user to define the public variables data depending on the
application type. Each program uses variables related to one application (diagnostic, maintenance,
measurement,...). The following table describes the programs of the DFB:
Program Number Description
0Bypass: no action
1Diagnostic: faults monitoring variables, warnings monitoring variables, and communication monitoring variables
2Maintenance: global statistics variables
3Measurements: measurements monitoring variables
4Statistics: last trip statistics and trip N–1 statistics
5Statistics: trip N–2 statistics and trip N–3 statistics
6Statistics: trip N–4 statistics
Public Variables Characteristics
The following table describes the Special_mdb_u_addq DFB public variables (using Quantum addressing):
Public VariableTypeRangeDefault ValueDescription
Slot_numINT0...2540Slot address of the NOE coupler.
IP_addr1INT0...2550First byte of IP address
IP_addr2INT0...2550Second byte of IP address
IP_addr3INT0...2550Third byte of IP address
IP_addr4INT0...2550Fourth byte of IP address
Sq_princINT0...70Reserved for support
Out_data[0]...[15]ARRAY [0...15] of INT 0...655350The output data depends on the program number.
Must be equal to 254 if using integrated Ethernet
port of the CPU.
Out_data[0]...[15] Public Variable (Program 1),
See
page 42
...
Out_data[0]...[15] Public Variable
(Program 6), page 45
Out_data[0]...[15] Public Variable (Program 1)
The following table describes the Out_data[0]...[15] public variable in the case of the diagnostic program
(program number 1):
1672609EN-03 01/202063
Modbus/TCP DFB for Quantum PLC
Public VariableTypeRegisterBitDescription
Out_data[0]INT4520Short-circuit fault
1Magnetic fault
2Ground fault
3Thermal fault
4Long start fault
5Jam fault
6Phase imbalance fault
7Underload fault
8Shunt trip fault
9Test trip fault
10Communication loss fault on LUCM Modbus port
11Control unit internal fault
12Module identification or internal communication fault
13Module internal fault
14Module trip fault
15Module drop-out fault
Out_data[1]INT4610...1Not significant
2Ground fault warning
3Thermal warning
4Long start warning
5Jam warning
6Phase imbalance warning
7Under-current warning
8...9Not significant
10Communication loss fault on LUCM Modbus port
11Internal temperature warning
12Module identification or internal communication warning
13...14Not significant
15Module warning
Out_data[2]INT4570Button position On (0 = Off)
1Button position Trip (0 = Not tripped)
2Contactor state On
324 Vdc power supply present on outputs
4...15Not significant
Out_data[3]INT450–Time to automatic reset on a thermal fault (s)
Out_data[4]
–––Not significant
...Out_data[15]
64
1672609EN-03 01/2020
Out_data[0]...[15] Public Variable (Program 2)
The following table describes the Out_data[0]...[15] public variable in the case of the maintenance program
(program number 2):
Public VariableTypeRegisterDescription
Out_data[0]INT100Short-circuit faults count
Out_data[1]INT101Magnetic faults count
Out_data[2]INT102Ground faults count
Out_data[3]INT103Thermal faults count
Out_data[4]INT104Long start faults count
Out_data[5]INT105Jam faults count
Out_data[6]INT106Phase imbalance faults count
Out_data[7]INT108Shunt trip faults count
Out_data[8]INT115Auto-resets count
Out_data[9]INT116Thermal warnings count
Out_data[10]INT117Starts count (LSB)
Out_data[11]INT118Starts count (MSB)
Out_data[12]INT119Operating time (LSB)
Out_data[13]INT120Operating time (MSB)
Out_data[14]INT121Maximum internal temperature (°C)
Out_data[15]––Not significant
Modbus/TCP DFB for Quantum PLC
Out_data[0]...[15] Public Variable (Program 3)
The following table describes the Out_data[0]...[15] public variable in the case of the measurements
program (program number 3):
Public VariableTypeRegisterDescription
Out_data[0]––Not significant
Out_data[1]INT465Thermal capacity level (%)
Out_data[2]INT466Average motor current (x 0.1 % FLA)
Out_data[3]INT467L1 current (% FLA)
Out_data[4]INT468L2 current (% FLA)
Out_data[5]INT469L3 current (% FLA)
Out_data[6]INT470Ground current (% FLA min)
Out_data[7]INT471Current imbalance coefficient
Out_data[8]INT472Control unit internal temperature (°C)
Out_data[9]
...Out_data[13]
Out_data[14]INT79Control unit sensor maximum current (x 0.1 A):
6 = adjustment range 0.15–0.6 A
14 = adjustment range 0.35–.4 A
50 = adjustment range 1.25–5 A
120 = adjustment range 3–12 A
180 = adjustment range 4.5–18 A
320 = adjustment range 8–32 A
minimum = 25 (default value)
maximum = 100
1672609EN-03 01/202065
Modbus/TCP DFB for Quantum PLC
Out_data[0]...[15] Public Variable (Program 4)
The following table describes the Out_data[0]...[15] public variable in the case of the statistics program
(program number 4):
6 = adjustment range 0.15–0.6 A
14 = adjustment range 0.35–1.4 A
50 = adjustment range 1.25–5 A
120 = adjustment range 3–12 A
180 = adjustment range 4.5–18 A
320 = adjustment range 8–32 A
minimum = 25 (default value)
maximum = 100
66
1672609EN-03 01/2020
Out_data[0]...[15] Public Variable (Program 5)
The following table describes the Out_data[0]...[15] public variable in the case of the statistics program
(program number 5):
Out_data[13]INT247N–3 trip ground current (% FLA min)
Out_data[14]INT79Control unit sensor maximum current (x 0.1 A):
6 = adjustment range 0.15–0.6 A
14 = adjustment range 0.35–1.4 A
50 = adjustment range 1.25–5 A
120 = adjustment range 3–12 A
180 = adjustment range 4.5–18 A
320 = adjustment range 8–32 A
6 = adjustment range 0.15–0.6 A
14 = adjustment range 0.35–1.4 A
50 = adjustment range 1.25–5 A
120 = adjustment range 3–12 A
180 = adjustment range 4.5–18 A
320 = adjustment range 8–32 A
minimum = 25 (default value)
maximum = 100
1672609EN-03 01/202067
Modbus/TCP DFB for Quantum PLC
Special_mdb_t_addq: TeSys T DFB for Modbus/TCP for Quantum PLC
Presentation
The Special_mdb_t_addq DFBs are dedicated to the reading of up to 16 predefined registers of a TeSys T
LTM R••E•• controller through the Modbus/TCP network connected to a Quantum PLC.
For more information, see the
Characteristics
CharacteristicValue
NameSpecial_mdb_t_addq
Version1.00
Input3
Output5
Input/Output0
Public Variable7
Graphical Representation
TeSys T LTMR Ethernet Communication Guide
.
TeSys T Compliance
The Special_mdb_t_addq DFBs are compliant with all the LTM R••E•• controller versions, with or without
the LTM E expansion module.
Software Implementation
The parameters and the inputs can only be changed if the End_st output variable is set to 1.
The output data is only valid if there is no fault detected (Fault_st = 0).
Prog_num can be modified on the fly.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Prog_numINT0...60Program number
See
Program Number, page 47
Rst_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
68
1672609EN-03 01/2020
Modbus/TCP DFB for Quantum PLC
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault ValueDescription
ControlARRAY [1...9] of INT0...655350For internal use of the DFB.
DatabufANY_ARRAY_INT0...655350For internal use of the DFB.
Fault_stEBOOL0...10Fault detected
Rst_stEBOOL0...10Reset state
End_stEBOOL0...10End state
Must be linked to an array of 9 located words (%MW)
Must be linked to an array of 20 located words minimum
(%MW)
Program Number
The Prog_num input variable enables the user to define the public variables data depending on the
application type. Each program holds variables related to one application (diagnostic, maintenance,
measurement,...). The following table describes the programs of the DFB:
Program Number Description
0Bypass: no action
10Diagnostic: detected faults monitoring variables, detected warnings monitoring variables, and communication
monitoring variables
20Maintenance: global statistics variables
30Measurements 1
31Measurements 2
32Measurements 3
40Statistics: last detected fault (N–0) statistics
41Statistics: last detected fault (N–0) statistics (with expansion module)
Out_data[3]INT153Average current ratio N–0 (% FLC)
Out_data[4]INT154L1 current ratio N–0 (% FLC)
Out_data[5]INT155L2 current ratio N–0 (% FLC)
Out_data[6]INT156L3 current ratio N–0 (% FLC)
Out_data[7]INT157Ground current ratio N–0 (x 0.1% FLC min)
Out_data[8]INT158Full load current max N–0 (x 0.1 A)
Out_data[9]INT159Current phase imbalance N–0 (%)
Out_data[10]INT160Frequency N–0 (x 0.1 Hz)
1672609EN-03 01/202073
Modbus/TCP DFB for Quantum PLC
Public VariableTypeRegisterDescription
Out_data[11]INT161Motor temperature sensor N–0 (x 0.1 Ω)
Out_data[12]WORD[4]162Date and time N–0
See
Out_data[13]163
Out_data[14]164
Out_data[15]165
DT_DateTime, page 111
Out_data[0]...[15] Public Variable (Program 41)
The following table describes the Out_data[0]...[15] public variable in the case of the last detected fault
statistics with expansion module program (program number 41):
Public VariableTypeRegisterDescription
Out_data[0]INT166Average voltage N–0 (V)
Out_data[1]INT167L3–L1 voltage N–0 (V)
Out_data[2]INT168L1–L2 voltage N–0 (V)
Out_data[3]INT169L2–L3 voltage N–0 (V)
Out_data[4]INT170Voltage phase imbalance N–0 (%)
Out_data[5]INT171Active power N–0 (kW)
Out_data[6]INT172Power factor N–0 (x 0.01)
Out_data[7] ...Out_data[15] ––Reserved
Out_data[0]...[15] Public Variable (Program 50)
The following table describes the Out_data[0]...[15] public variable in the case of the N–1 detected fault
statistics program (program number 50):
Public VariableTypeRegisterDescription
Out_data[0]INT180Detected fault code N–1
Out_data[1]INT181Motor full load current ratio N–1 (% FLC max)
Out_data[3]INT183Average current ratio N–1 (% FLC)
Out_data[4]INT184L1 current ratio N–1 (% FLC)
Out_data[5]INT185L2 current ratio N–1 (% FLC)
Out_data[6]INT186L3 current ratio N–1 (% FLC)
Out_data[7]INT187Ground current ratio N–1 (x 0.1% FLC min)
Out_data[8]INT188Full load current max N–1 (x 0.1 A)
Out_data[9]INT189Current phase imbalance N–1 (%)
Out_data[10]INT190Frequency N–1 (x 0.1 Hz)
Out_data[11]INT191Motor temperature sensor N–1 (x 0.1 Ω)
Out_data[12]WORD[4]192Date and time N–1
DT_DateTime, page 111
Out_data[13]193
Out_data[14]194
Out_data[15]195
See
74
1672609EN-03 01/2020
Modbus/TCP DFB for Quantum PLC
Out_data[0]...[15] Public Variable (Program 51)
The following table describes the Out_data[0]...[15] public variable in the case of the N–1 detected fault
statistics with expansion module program (program number 51):
Public VariableTypeRegisterDescription
Out_data[0]INT196Average voltage N–1 (V)
Out_data[1]INT197L3–L1 voltage N–1 (V)
Out_data[2]INT198L1–L2 voltage N–1 (V)
Out_data[3]INT199L2–L3 voltage N–1 (V)
Out_data[4]INT200Voltage phase imbalance N–1 (%)
Out_data[5]INT201Active power N–1 (kW)
Out_data[6]INT202Power factor N–1 (x 0.01)
Out_data[7]
...Out_data[15]
––Reserved
Out_data[0]...[15] Public Variable (Program 60)
The following table describes the Out_data[0]...[15] public variable in the case of the N–2 detected fault
statistics program (program number 60):
Public VariableTypeRegisterDescription
Out_data[0]INT210Detected fault code N–2
Out_data[1]INT211Motor full load current ratio N–2 (% FLC max)
Out_data[3]INT213Average current ratio N–2 (% FLC)
Out_data[4]INT214L1 current ratio N–2 (% FLC)
Out_data[5]INT215L2 current ratio N–2 (% FLC)
Out_data[6]INT216L3 current ratio N–2 (% FLC)
Out_data[7]INT217Ground current ratio N–2 (x 0.1% FLC min)
Out_data[8]INT218Full load current max N–2 (x 0.1 A)
Out_data[9]INT219Current phase imbalance N–2 (%)
Out_data[10]INT220Frequency N–2 (x 0.1 Hz)
Out_data[11]INT221Motor temperature sensor N–2 (x 0.1 Ω)
Out_data[12]WORD[4]222Date and time N–2
DT_DateTime, page 111
Out_data[13]223
Out_data[14]224
Out_data[15]225
See
Out_data[0]...[15] Public Variable (Program 61)
The following table describes the Out_data[0]...[15] public variable in the case of the N–2 detected fault
statistics with expansion module program (program number 61):
Public VariableTypeRegisterDescription
Out_data[0]INT226Average voltage N–2 (V)
Out_data[1]INT227L3–L1 voltage N–2 (V)
Out_data[2]INT228L1–L2 voltage N–2 (V)
Out_data[3]INT229L2–L3 voltage N–2 (V)
Out_data[4]INT230Voltage phase imbalance N–2 (%)
Out_data[5]INT231Active power N–2 (kW)
Out_data[6]INT232Power factor N–2 (x 0.01)
Out_data[7]
...Out_data[15]
1672609EN-03 01/202075
––Reserved
Modbus/TCP DFB for Quantum PLC
Out_data[0]...[15] Public Variable (Program 70)
The following table describes the Out_data[0]...[15] public variable in the case of the N–3 detected fault
statistics program (program number 70):
Public VariableTypeRegisterDescription
Out_data[0]INT240Detected fault code N–3
Out_data[1]INT241Motor full load current ratio N–3 (% FLC max)
Out_data[3]INT243Average current ratio N–3 (% FLC)
Out_data[4]INT244L1 current ratio N–3 (% FLC)
Out_data[5]INT245L2 current ratio N–3 (% FLC)
Out_data[6]INT246L3 current ratio N–3 (% FLC)
Out_data[7]INT247Ground current ratio N–3 (x 0.1% FLC min)
Out_data[8]INT248Full load current max N–3 (x 0.1 A)
Out_data[9]INT249Current phase imbalance N–3 (%)
Out_data[10]INT250Frequency N–3 (x 0.1 Hz)
Out_data[11]INT251Motor temperature sensor N–3 (x 0.1 Ω)
Out_data[12]WORD[4]252Date and time N–3
DT_DateTime, page 111
Out_data[13]253
Out_data[14]254
Out_data[15]255
See
Out_data[0]...[15] Public Variable (Program 71)
The following table describes the Out_data[0]...[15] public variable in the case of the N–3 detected fault
statistics with expansion module program (program number 71):
Public VariableTypeRegisterDescription
Out_data[0]INT256Average voltage N–3 (V)
Out_data[1]INT257L3–L1 voltage N–3 (V)
Out_data[2]INT258L1–L2 voltage N–3 (V)
Out_data[3]INT259L2–L3 voltage N–3 (V)
Out_data[4]INT260Voltage phase imbalance N–3 (%)
Out_data[5]INT261Active power N–3 (kW)
Out_data[6]INT262Power factor N–3 (x 0.01)
Out_data[7]
...Out_data[15]
––Reserved
76
1672609EN-03 01/2020
Modbus/TCP DFB for Quantum PLC
Out_data[0]...[15] Public Variable (Program 80)
The following table describes the Out_data[0]...[15] public variable in the case of the N–4 detected fault
statistics program (program number 80):
Public VariableTypeRegisterDescription
Out_data[0]INT270Detected fault code N–4
Out_data[1]INT271Motor full load current ratio N–4 (% FLC max)
Out_data[3]INT273Average current ratio N–4 (% FLC)
Out_data[4]INT274L1 current ratio N–4 (% FLC)
Out_data[5]INT275L2 current ratio N–4 (% FLC)
Out_data[6]INT276L3 current ratio N–4 (% FLC)
Out_data[7]INT277Ground current ratio N–4 (x 0.1% FLC min)
Out_data[8]INT278Full load current max N–4 (x 0.1 A)
Out_data[9]INT279Current phase imbalance N–4 (%)
Out_data[10]INT280Frequency N–4 (x 0.1 Hz)
Out_data[11]INT281Motor temperature sensor N–4 (x 0.1 Ω)
Out_data[12]WORD[4]282Date and time N–4
DT_DateTime, page 111
Out_data[13]283
Out_data[14]284
Out_data[15]285
See
Out_data[0]...[15] Public Variable (Program 81)
The following table describes the Out_data[0]...[15] public variable in the case of the N–4 detected fault
statistics with expansion module program (program number 81):
Public VariableTypeRegisterDescription
Out_data[0]INT286Average voltage N–4 (V)
Out_data[1]INT287L3–L1 voltage N–4 (V)
Out_data[2]INT288L1–L2 voltage N–4 (V)
Out_data[3]INT289L2–L3 voltage N–4 (V)
Out_data[4]INT290Voltage phase imbalance N–4 (%)
Out_data[5]INT291Active power N–4 (kW)
Out_data[6]INT292Power factor N–4 (x 0.01)
Out_data[7]
...Out_data[15]
––Reserved
1672609EN-03 01/202077
Modbus/TCP DFB for Quantum PLC
Custom_mdb_addq: Custom Read DFB for Modbus/TCP for Quantum PLC
Presentation
The Custom_mdb_addq DFB is dedicated to the reading of up to 5 sets of registers in one single TeSys
device through the Modbus/TCP network connected to a Quantum PLC.
The Custom_mdb_addq DFB completes the Special_mdb_u_addq and Special_mdb_t_addq DFBs and
enable the user to select the registers to read.
Characteristics
CharacteristicValue
NameCustom_mdb_addq
Version1.00
Input3
Output5
Input/Output0
Public Variable13
Graphical Representation
TeSys U and TeSys T Compliance
TeSys U: The Custom_mdb_addq DFB is compliant with the following TeSys U sub-assemblies:
LUB•• non-reversing power base and LU2B•• reversing power base (upto32A/15kW or 20hp)
LUCM multifunction control unit
LULC033 Modbus communication module connected through an Ethernet gateway.
TeSys T: The Custom_mdb_addq DFB is compliant with all the LTM R••M•• (through an Ethernet
gateway) and LTM R••E•• controller versions, with or without the LTM E expansion module.
Software Implementation
The parameters and the inputs can only be changed if the End_st output variable is set to 1.
The output data is only valid if there is no fault detected (Fault_st = 0).
Prog_num input can be modified on the fly.
The public variables enable the user to read up to 5 sets of registers of a maximum length of 16 registers
for each set:
The user defines the starting point of a set of registers with the In_reg public variable.
The user defines the length of the set of registers with the corresponding In_len public variable.
The registers content is then returned in the corresponding Out_dat public variable.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault
Value
Slav_numINT1...311Modbus slave number
Rst_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
Description
78
1672609EN-03 01/2020
Output Characteristics
Modbus/TCP DFB for Quantum PLC
The following table describes the DFB outputs:
OutputTypeRangeDefault
Value
ControlARRAY [1...9] of INT0...655350For internal use of the DFB.
DatabufANY_ARRAY_INT0...655350For internal use of the DFB.
Fault_stEBOOL0...10Fault detected
Rst_stEBOOL0...10Reset state
End_stEBOOL0...10End state
Description
Must be linked to an array of 9 located words (%MW)
Must be linked to an array of 16 located words minimum
(%MW)
Public Variables Characteristics
The following table describes the Custom_mdb_addq DFB public variables (using Quantum addressing):
Public VariableTypeRangeDefault
Value
Slot_numINT0...2540Slot address of the NOE coupler.
IP_addr1INT0...2550First byte of IP address
IP_addr2INT0...2550Second byte of IP address
IP_addr3INT0...2550Third byte of IP address
IP_addr4INT0...2550Fourth byte of IP address
In_regARRAY[0...4] of INT0...655350Array of 5 words for the 5 index registers
In_lenARRAY[0...4] of INT0...160Array of 5 words for the length of each set of registers
Out_dat[0]ARRAY[0...15] of INT0...2550Array of up to 16 words containing the In_len[0] words
Out_dat[1]ARRAY[0...15] of INT0...2550Array of up to 16 words containing the In_len[1] words
Out_dat[2]ARRAY[0...15] of INT0...2550Array of up to 16 words containing the In_len[2] words
Out_dat[3]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[3] words
Out_dat[4]ARRAY[0...15] of INT0...655350Array of up to 16 words containing the In_len[4] words
Sq_princINT0...70Reserved for support
Description
Must be equal to 254 if using integrated Ethernet port of the
CPU.
(In_reg[0]...In_reg[4])
(In_len[0]...In_len[4])
starting from In_reg[0]
starting from In_reg[1]
starting from In_reg[2]
starting from In_reg[3]
starting from In_reg[4]
1672609EN-03 01/202079
Modbus/TCP DFB for Quantum PLC
80
1672609EN-03 01/2020
TeSys DFB Library V2 for Unity Pro
Profibus DFB
1672609EN-03 01/2020
Profibus DFB
Chapter 5
Profibus DFB
Introduction
This chapter describes the TeSys U and TeSys T Profibus DP DFBs.
What Is in This Chapter?
This chapter contains the following topics:
Ctrl_pfb_u_ms: TeSys U Control/Command for Profibus DP MS82
Ctrl_pfb_u_mms: TeSys U Control/Command for Profibus DP MMS84
Ctrl_pfb_t_mms: TeSys T Control/Command for Profibus DP MMS86
TopicPage
1672609EN-03 01/202081
Profibus DFB
Ctrl_pfb_u_ms: TeSys U Control/Command for Profibus DP MS
Presentation
The Ctrl_pfb_u_ms DFB is dedicated to the control and command of a single TeSys U starter-controller
through the Profibus DP MS (Motor Starter) network.
With the MS profile, the TeSys U starter-controller commands are managed on bit level. For more
information, see the
Characteristics
CharacteristicValue
NameCtrl_pfb_u_ms
Version1.00
Input7
Output10
Input/Output0
Public Variable0
Graphical Representation
TeSys U LULC07 Profibus DP Communication Module User Manual.
TeSys U Compliance
The Ctrl_pfb_u_ms DFB is compliant with the following TeSys U sub-assemblies:
Power base LUB•• non-reversing power base
LU2B•• reversing power base
Control unit
Communication module
GSD file modules
LUCA standard control unit
LUCB and LUCD advanced control units
LUCC advanced control unit (up to 32 A/15 kW or 20 hp)
LUCL magnetic control unit
LUCM multifunction control unit (up to 32 A/15 kW or 20 hp)
LULC07 Profibus DP communication module
Sc St R MS with or without PKW
Sc Ad R MS with or without PKW
Sc Mu R MS with or without PKW
Sc Mu L MS with or without PKW
Software Implementation
Ms_in1 input word must be linked to the first word of the Profibus slave input cyclic data.
Ms_out1 output word must be linked to the first word of the Profibus slave output cyclic data.
82
1672609EN-03 01/2020
Input Characteristics
Profibus DFB
The following table describes the DFB inputs and their availability according to the control unit:
InputTypeRangeDefault
Value
Ms_in1INT–0Must be linked to the first word of the
Run_fwdEBOOL0...10Motor run forward command√√√
Run_revEBOOL0...10Motor run reverse command√√√
Rst_fltEBOOL0...10Reset device (if register 451 = 102 or
Rst_warnEBOOL0...10Reset warning (for example,
Em_strtEBOOL0...10Emergency start (reset thermal
Trip_tstEBOOL0...10Overcurrent trip test via communication
DescriptionLUCA
LUCL
√√√
MS Profibus slave input cyclic data
√√√
104, fault acknowledgment causes a
return to communication module
factory settings)
√√√
communication loss)
––√
memory)
––√
bus
LUCB
LUCC
LUCD
Output Characteristics
The following table describes the DFB outputs and their availability according to the control unit:
OutputTypeRangeDefault
Value
Ms_out1INT–0Must be linked to the first word of the
ReadyEBOOL0...10System ready: the rotary handle is
ClosedEBOOL0...10Pole status: closed√√√
TrippedEBOOL0...10System tripped: the rotary handle is
FaultEBOOL0...10All faults√√√
AlarmEBOOL0...10All warnings√√√
Rst_authEBOOL0...10Fault reset authorized–√√
StartingEBOOL0...10Start in progress:
RunningEBOOL0...10Motor running with detection of current,
Avg_currINT0...2000Average motor current (x 1% FLA)–√√
DescriptionLUCA
LUCL
√√√
MS Profibus slave output cyclic data
√√√
turned to On position and there is no
fault
√√√
turned to Trip position
–√√
1 = ascending current is greater than
10% FLA
0 = descending current is lower than
150% FLA
–√√
if greater than 10% FLA
LUCB
LUCC
LUCD
LUCM
LUCM
1672609EN-03 01/202083
Profibus DFB
Ctrl_pfb_u_mms: TeSys U Control/Command for Profibus DP MMS
Presentation
The Ctrl_pfb_u_mms DFB is dedicated to the control and command of a single TeSys U starter-controller
(up to 32 A/15 kW or 20 hp) with a LUCM multifunction control unit and a LULC07 Profibus DP
communication module through the Profibus DP MMS (Motor Management Starter) network.
With the MMS profile, the TeSys U starter-controller commands are managed on bit rising edges. For more
information, see the
Characteristics
CharacteristicValue
NameCtrl_pfb_u_mms
Version1.00
Input10
Output13
Input/Output0
Public Variable0
Graphical Representation
TeSys U LULC07 Profibus DP Communication Module User Manual
.
TeSys U Compliance
The Ctrl_pfb_u_mms DFB is compliant with the following TeSys U sub-assemblies:
Power base LUB•• non-reversing power base (up to 32 A/15 kW or 20 hp)
LU2B•• reversing power base (up to 32 A/15 kW or 20 hp)
Control unit
Communication module
GSD file modules
84
LUCM multifunction control unit
LULC07 Profibus DP communication module
Sc Mu R MMS with or without PKW
Sc Mu L MMS with or without PKW
1672609EN-03 01/2020
Profibus DFB
Software Implementation
Mms_in1 and Mms_in2 input words must be linked to the first 2 words of the Profibus slave input cyclic
data.
Mms_out1 output word must be linked to the first word of the Profibus slave output cyclic data.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Mms_in1INT–0Must be linked to the first word of the MMS Profibus slave input
Mms_in2INT–0Must be linked to the second word of the MMS Profibus slave
Ms_out1INT–0Must be linked to the first word of the Profibus slave output cyclic
data
Rev_stEBOOL0...10Run reverse
Off_stEBOOL0...10System Off
Fwd_stEBOOL0...10Run forward
Th_ov_stEBOOL0...10Thermal overload
Automode_stEBOOL0...10Auto mode
FaultEBOOL0...10TeSys U on fault
AlarmEBOOL0...10TeSys U on alarm
ReadyEBOOL0...10TeSys U ready to operate
StartingEBOOL0...10Motor starting
RunningEBOOL0...10Motor running
TrippedEBOOL0...10Rotary knob on trip position
Avg_currINT0...20000Average motor current (x 0.1% FLA)
1672609EN-03 01/202085
Profibus DFB
Ctrl_pfb_t_mms: TeSys T Control/Command for Profibus DP MMS
Presentation
The Ctrl_pfb_t_mms DFB is dedicated to the control and command of a single TeSys T LTM R••P••
controller through the Profibus DP MMS (Motor Management Starter) network.
With the MMS profile, the TeSys T LTM R••P•• controller commands are managed on bit rising edges. For
more information, see the
Characteristics
CharacteristicValue
NameCtrl_pfb_t_mms
Version1.00
Input11
Output22
Input/Output0
Public Variable0
Graphical Representation
TeSys T LTMR Profibus DP Communication Guide
.
86
1672609EN-03 01/2020
Profibus DFB
TeSys T Compliance
The Ctrl_pfb_t_mms DFB is compliant with all the TeSys T LTM R••P•• controller versions, with or without
the LTM E expansion module.
Software Implementation
Mms_in1, Mms_in2 and Mms_in5 input words must be linked respectively to the first, second, and fifth
word of the Profibus slave input cyclic data.
Mms_out1 output word must be linked to the first word of the Profibus slave output cyclic data.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Mms_in1INT–0Must be linked to the first word of the MMS Profibus slave input
cyclic data
Mms_in2INT–0Must be linked to the second word of the MMS Profibus slave input
cyclic data
Mms_in5INT–0Must be linked to the fifth word of the MMS Profibus slave input
The following table describes the DFB outputs and their availability according to the programming platform:
OutputTypeRangeDefault ValueDescription
Mms_out1INT–0Must be linked to the first word of the Profibus slave output cyclic
Rev_stEBOOL0...10Run reverse
Off_stEBOOL0...10System Off
Fwd_stEBOOL0...10Run forward
Th_ov_stEBOOL0...10Thermal overload
Automode_stEBOOL0...10Auto mode
FaultEBOOL0...10System fault
AlarmEBOOL0...10System warning
ReadyEBOOL0...10System ready
StartingEBOOL0...10Motor starting
RunningEBOOL0...10Motor running (with detection of a current, if greater than 10% FLC)
TrippedEBOOL0...10System tripped
Auto_rstEBOOL0...10Auto-reset active
Pwr_rqstEBOOL0...10Fault power cycle requested
Rst_timeEBOOL0...10Motor restart time undefined
Rpd_cyclEBOOL0...10Rapid cycle lockout
Load_shdEBOOL0...10Voltage load shedding
Hi_speedEBOOL0...10Motor high speed
Hmi_lossEBOOL0...10HMI port communication loss
Net_lossEBOOL0...10Network port communication loss
Motor_trEBOOL0...10Motor transition lockout
Avg_currINT0...20000Average motor current (x 0.1 % FLA)
data
88
1672609EN-03 01/2020
TeSys DFB Library V2 for Unity Pro
Cyclic Control/Command DFB
1672609EN-03 01/2020
Cyclic Control/Command DFB
Chapter 6
Cyclic Control/Command DFB
Introduction
This chapter describes the TeSys U and TeSys T cyclic control/command DFBs.
What Is in This Chapter?
This chapter contains the following topics:
Ctrl_cmd_u: TeSys U Cyclic Control/Command90
Ctrl_cmd_t: TeSys T Cyclic Control/Command92
TopicPage
1672609EN-03 01/202089
Cyclic Control/Command DFB
Ctrl_cmd_u: TeSys U Cyclic Control/Command
Presentation
The Ctrl_cmd_u DFB is dedicated to the control and command of a single TeSys U starter-controller
through cyclic data exchanges on Modbus/TCP (IO scanning), CANopen, and Advantys STB networks.
For more information, see:
TeSys U LULC032-033 Modbus Communication Module User Manual
TeSys U LULC08 CANopen Communication Module User Manual
TeSys U LULC15 Advantys STB Communication Module User Manual
Characteristics
CharacteristicValue
NameCtrl_cmd_u
Version1.00 and 1.10
Input7
Output11
Input/Output0
Public Variable0
NOTE:
Version 1.10 is compatible with Quantum, Premium, and M340 PLCs.
Version 1.00 is compatible only with Premium and M340 PLCs.
Graphical Representation
90
1672609EN-03 01/2020
TeSys U Compliance
The Ctrl_cmd_u DFB is compliant with the following TeSys U sub-assemblies:
Power base LUB•• non-reversing power base
LU2B•• reversing power base
Control unit
Communication module
LUCA standard control unit
LUCB and LUCD advanced control units
LUCC advanced control unit (up to 32 A/15 kW or 20 hp)
LUCL magnetic control unit
LUCM multifunction control unit (up to 32 A/15 kW or 20 hp)
LULC08 CANopen communication module
LULC15 Advantys STB communication module
LULC033 Modbus communication module with an Ethernet gateway
Input Characteristics
The following table describes the DFB inputs and their availability according to the control unit:
Cyclic Control/Command DFB
InputTypeRangeDefault Value DescriptionLUCA
LUCL
LUCB
LUCC
LUCD
Reg_455INT0...655350To link to register 455 of cyclic data
√√√
inputs
Run_fwdEBOOL0...10Motor run forward command√√√
Run_revEBOOL0...10Motor run reverse command√√√
Rst_fltEBOOL0...10Reset device (if device 451 = 102 or 104,
√√√
fault acknowledgment causes a return to
communication module factory settings)
Trip_tstEBOOL0...10Overcurrent trip test via communication
––√
bus
Output Characteristics
The following table describes the DFB outputs and their availability according to the control unit:
OutputTypeRangeDefault Value DescriptionLUCA
LUCL
Reg_704INT0...655350To link to register 704 of cyclic data
√√√
outputs
Reg_703INT0...655350To link to register 703 of cyclic data
√√√
outputs
ReadyEBOOL0...10System ready: the rotary handle is
√√√
turned to On position and there is no
fault.
ClosedEBOOL0...10Pole status: closed√√√
TrippedEBOOL0...10System tripped: the rotary handle is
√√√
turned to Trip position.
FaultEBOOL0...10All faults√√√
AlarmEBOOL0...10All warnings√√√
Rst_authEBOOL0...10Fault reset authorized–√√
StartingEBOOL0...10Start in progress:
–√√
0 = descending current is lower than
150% FLA
1 = ascending current is greater than
10% FLA
RunningEBOOL0...10Motor running with detection of current, if
–√√
greater than 10% FLA
Avg_currINT0...2000Average motor current (x 1% FLA)–√√
LUCB
LUCC
LUCD
LUCM
LUCM
1672609EN-03 01/202091
Cyclic Control/Command DFB
Ctrl_cmd_t: TeSys T Cyclic Control/Command
Presentation
The Ctrl_cmd_t DFB is dedicated to the control and command of a single TeSys T LTM R••C•• CANopen
or a TeSys T LTMR••E•• Modbus/TCP controller through cyclic data exchanges on Modbus/TCP (IO
scanning) and CANopen networks.
For more information, see:
TeSys T LTMR Ethernet Communication Guide
TeSys T LTMR CANopen Communication Guide
Characteristics
CharacteristicValue
NameCtrl_cmd_t
Version1.00 and 1.10
Input7
Output21
Input/Output0
Public Variable0
NOTE:
Version 1.10 is compatible with Quantum, Premium, and M340 PLCs.
Version 1.0 is compatible only with Premium and M340 PLCs.
Graphical Representation
92
1672609EN-03 01/2020
Cyclic Control/Command DFB
TeSys T Compliance
The Ctrl_cmd_t DFB is compliant with the TeSys T LTM R••C•• CANopen and with the TeSys T LTM R••E••
Modbus/TCP controller versions, with or without the LTM E expansion module.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault Value Description
Reg_455INT0...655350To link to register 455 of cyclic data inputs
Reg_456INT0...655350To link to register 456 of cyclic data inputs
Run_fwdEBOOL0...10Motor run forward command
Run_revEBOOL0...10Motor run reverse command
Lo_speedEBOOL0...10Motor low speed command
Rst_fltEBOOL0...10Fault reset command
AutotestEBOOL0...10Self test command
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault Value Description
Reg_704INT0...655350To link to register 704 of cyclic data outputs
ReadyEBOOL0...10System ready
Syst_onEBOOL0...10System On
FaultEBOOL0...10System fault
AlarmEBOOL0...10System warning
TrippedEBOOL0...10System tripped
Rst_authEBOOL0...10Fault reset authorized
Ctrl_pwrEBOOL0...10Controller power
RunningEBOOL0...10Motor running (with detection of a current, if greater than 10% FLC)
Hmi_ctrlEBOOL0...10Control through HMI
StartingEBOOL0...10Motor starting (start in progress)
Auto_rstEBOOL0...10Auto-reset active
Pwr_rqstEBOOL0...10Power cycle requested
Rst_timeEBOOL0...10Motor restart time undefined
Rpd_cyclEBOOL0...10Rapic cycle lockout
Load_shdEBOOL0...10Load shedding
Hi_speedEBOOL0...10Motor speed
Hmi_lossEBOOL0...10HMI port communication loss
Net_lossEBOOL0...10Network port communication loss
Motor_trEBOOL0...10Motor transition lockout
Avg_currINT0...2000Average motor current (x 1% FLA)
0 = descending current is less than 150% FLC
1 = ascending current is greater than 10% FLC
0 = FLC1 setting is used
1 = FLC2 setting is used
1672609EN-03 01/202093
Cyclic Control/Command DFB
94
1672609EN-03 01/2020
TeSys DFB Library V2 for Unity Pro
PKW Exchanges DFB
1672609EN-03 01/2020
PKW Exchanges DFB
Chapter 7
PKW Exchanges DFB
Introduction
This chapter describes the TeSys U and TeSys T DFBs for PKW exchanges.
What Is in This Chapter?
This chapter contains the following topics:
Special_pkw_u: TeSys U DFB for PKW Exchanges96
Special_pkw_t: TeSys T DFB for PKW Exchanges102
Custom_pkw: Custom Read DFB for PKW Exchanges113
TopicPage
1672609EN-03 01/202095
PKW Exchanges DFB
Special_pkw_u: TeSys U DFB for PKW Exchanges
Presentation
The Special_pkw_u DFB is dedicated to the reading of up to 16 predefined registers of a TeSys U startercontroller (up to 12 A/5.5 kW or 7 hp) with a LUCM multifunction control unit and one of the following
communication modules that support PKW (Periodically Kept in Acyclic Words) exchanges:
LULC15 Advantys STB Communication Module User Manual
Characteristics
CharacteristicValue
NameSpecial_pkw_u
Version1.00
Input7
Output3
Input/Output2
Public Variable2
Graphical Representation
TeSys U Compliance
The Special_pkw_u DFB is compliant with the following TeSys U sub-assemblies:
Power base LUB•• non-reversing power base (up to 12 A/5.5 kW or 7 hp)
LU2B•• reversing power base (up to 12 A/5.5 kW or 7 hp)
Control unit
Communication module
GSD file modulesProfibus:
LUCM multifunction control unit
LULC07 Profibus DP communication module
LULC08 CANopen communication module
LULC15 Advantys STB communication module
Sc Mu R MS PKW
Sc Mu L MS PKW
Sc Mu R MMS PKW
Sc Mu L MMS PKW
96
1672609EN-03 01/2020
PKW Exchanges DFB
Software Implementation
Pkw_in1, Pkw_in2, Pkw_in3, and Pkw_in4 input words must be linked to the first 4 words of the PKW
slave input cyclic data.
Pkw_out1 and Pkw_out2 input/output words must be linked to the first 2 words of the PKW slave output
cyclic data.
The output data is only valid if the End_st output variable is set to 1 and if there is no fault detected
(Fault_st = 0).
When using TSXPBY100 Premium Profibus coupler it is mandatory to set %QWxy.0.242:X0 to 1 to
guarantee the data consistency.
Input Characteristics
The following table describes the DFB inputs:
InputTypeRangeDefault ValueDescription
Pkw_in1INT–0Must be linked to the first word of the PKW slave input cyclic
Pkw_in2INT–0Must be linked to the second word of the PKW slave input
Pkw_in3INT–0Must be linked to the third word of the PKW slave input cyclic
Pkw_in4INT–0Must be linked to the fourth word of the PKW slave input
Prog_numINT0...60Program number
Rst_cmdEBOOL0...10Reset command
Strt_cmdEBOOL0...10Start command
data
cyclic data
data
cyclic data
See
Program Number, page 97
Output Characteristics
The following table describes the DFB outputs:
OutputTypeRangeDefault ValueDescription
Fault_stEBOOL0...10Fault detected
Rst_stEBOOL0...10Reset state
End_stEBOOL0...10End state
Input/Output Characteristics
The following table describes the DFB input/outputs:
Input/OutputTypeRangeDefault ValueDescription
Pkw_out1INT–0Must be linked to the first word of the PKW slave output
cyclic data
Pkw_out2INT–0Must be linked to the second word of the PKW slave output
cyclic data
Program Number
The Prog_num input variable enables the user to define the public variables data depending on the
application type. Each program uses variables related to one application (diagnostic, maintenance,
measurement,...). The following table describes the programs of the DFB:
Program Number Description
0Bypass: no action
1Diagnostic: faults monitoring variables, warnings monitoring variables, and communication monitoring variables
2Maintenance: global statistics variables
3Measurements: measurements monitoring variables
4Statistics: last trip statistics and trip N–1 statistics
5Statistics: N–2 and N–3 trip statistics
6Statistics: N–4 trip statistics
1672609EN-03 01/202097
PKW Exchanges DFB
Public Variables Characteristics
The following table describes the DFB public variables:
Public VariableTypeRangeDefault ValueDescription
Sq_princINT0...70Reserved for support
Out_data[0]...[15]ARRAY[0...15] of INT 0...655350The output data depends on the program number
Out_data[0]...[15] Public Variable (Program 1)
The following table describes the Out_data[0]...[15] public variable in the case of the diagnostic program
(program number 1):
Public VariableTypeRegisterBitDescription
Out_data[0]INT4520Short-circuit fault
1Magnetic fault
2Ground fault
3Thermal fault
4Long start fault
5Jam fault
6Phase imbalance fault
7Underload fault
8Shunt trip fault
9Test trip fault
10Communication loss fault on LUCM Modbus port
11Control unit internal fault
12Module identification or internal communication fault
13Module internal fault
14Module trip fault
15Module drop-out fault
Out_data[1]INT4610...1Not significant
2Ground fault warning
3Thermal warning
4Long start warning
5Jam warning
6Phase imbalance warning
7Under-current warning
8...9Not significant
10Communication loss fault on LUCM Modbus port
11Internal temperature warning
12Module identification or internal communication warning
13...14Not significant
15Module warning
Out_data[2]INT4570Button position On (0 = Off)
1Button position Trip (0 = Not tripped)
2Contactor state On
324 Vdc power supply present on outputs
4...15Not significant
Out_data[3]INT450–Time to automatic reset on a thermal fault (s)
Out_data[4]
...Out_data[15]
–––Not significant
98
1672609EN-03 01/2020
Out_data[0]...[15] Public Variable (Program 2)
The following table describes the Out_data[0]...[15] public variable in the case of the maintenance program
(program number 2):
Public VariableTypeRegisterDescription
Out_data[0]INT100Short-circuit faults count
Out_data[1]INT101Magnetic faults count
Out_data[2]INT102Ground faults count
Out_data[3]INT103Thermal faults count
Out_data[4]INT104Long start faults count
Out_data[5]INT105Jam faults count
Out_data[6]INT106Phase imbalance faults count
Out_data[7]INT108Shunt trip faults count
Out_data[8]INT115Auto-resets count
Out_data[9]INT116Thermal warnings count
Out_data[10]INT117Starts count (LSB)
Out_data[11]INT118Starts count (MSB)
Out_data[12]INT119Operating time (LSB)
Out_data[13]INT120Operating time (MSB)
Out_data[14]INT121Maximum internal temperature (°C)
Out_data[15]––Not significant
PKW Exchanges DFB
Out_data[0]...[15] Public Variable (Program 3)
The following table describes the Out_data[0]...[15] public variable in the case of the measurements
program (program number 3):
Public VariableTypeRegisterDescription
Out_data[0]––Not significant
Out_data[1]INT465Thermal capacity level (%)
Out_data[2]INT466Average motor current (x 0.1 % FLA)
Out_data[3]INT467L1 current (% FLA)
Out_data[4]INT468L2 current (% FLA)
Out_data[5]INT469L3 current (% FLA)
Out_data[6]INT470Ground current (% FLA min)
Out_data[7]INT471Current imbalance coefficient
Out_data[8]INT472Control unit internal temperature (°C)
Out_data[9]
...Out_data[13]
Out_data[14]INT79Control unit sensor maximum current (x 0.1 A):
6 = adjustment range 0.15 to 0.6 A
14 = adjustment range 0.35 to 1.4 A
50 = adjustment range 1.25 to 5 A
120 = adjustment range 3 to 12 A
180 = adjustment range 4.5 to 18 A
320 = adjustment range 8 to 32 A
minimum = 25 (default value)
maximum = 100
1672609EN-03 01/202099
PKW Exchanges DFB
Out_data[0]...[15] Public Variable (Program 4)
The following table describes the Out_data[0]...[15] public variable in the case of the statistics program
(program number 4):
6 = adjustment range 0.15 to 0.6 A
14 = adjustment range 0.35 to 1.4 A
50 = adjustment range 1.25 to 5 A
120 = adjustment range 3 to 12 A
180 = adjustment range 4.5 to 18 A
320 = adjustment range 8 to 32 A
minimum = 25 (default value)
maximum = 100
Out_data[0]...[15] Public Variable (Program 5)
The following table describes the Out_data[0]...[15] public variable in the case of the statistics program
(program number 5):
Out_data[13]INT247N–3 trip ground current (% FLA min)
Out_data[14]INT79Control unit sensor maximum current (x 0.1 A):
6 = adjustment range 0.15 to 0.6 A
14 = adjustment range 0.35 to 1.4 A
50 = adjustment range 1.25 to 5 A
120 = adjustment range 3 to 12 A
180 = adjustment range 4.5 to 18 A
320 = adjustment range 8 to 32 A
100
1672609EN-03 01/2020
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.