Tesys DFB Offer V2 For Unity Pro: A Socollaborative Library User Manual
Tesys DFB Offer V2 For Unity Pro: A Socollaborative Library User Manual
www.schneider-electric.com
The information provided in this documentation contains general descriptions and/or technical character-
istics 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.
No part of this document may be reproduced in any form or by any means, electronic or mechanical,
including photocopying, without express written permission of Schneider Electric.
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.
© 2009 Schneider Electric. All rights reserved.
2 1672609 09/2009
Table of Contents
Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
TeSys DFB Offer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
TeSys DFB Offer Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
TeSys DFB Sequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 2 Modbus SL DFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Ctrl_cmd_mdb_u_••••: TeSys U Control/Command for Modbus SL . . . . . . . . . . . . . . . . . . . . . 24
Comm_manager_u: TeSys U Communication Management for Modbus SL . . . . . . . . . . . . . . 28
Ctrl_cmd_mdb_t_••••: TeSys T Control/Command for Modbus SL . . . . . . . . . . . . . . . . . . . . . . 32
Comm_manager_t: TeSys T Communication Management for Modbus SL. . . . . . . . . . . . . . . 36
Chapter 3 Modbus SL and Modbus/TCP DFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Special_mdb_u_••••: TeSys U DFB for Modbus SL and Modbus/TCP . . . . . . . . . . . . . . . . . . . 42
Special_mdb_t_••••: TeSys T DFB for Modbus SL and Modbus/TCP. . . . . . . . . . . . . . . . . . . . 49
Custom_mdb_••••: Custom Read DFB for Modbus SL and Modbus/TCP . . . . . . . . . . . . . . . . 61
Chapter 4 Modbus/TCP DFB for Quantum PLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Special_mdb_u_addq: TeSys U DFB for Modbus/TCP for Quantum PLC . . . . . . . . . . . . . . . . 66
Special_mdb_t_addq: TeSys T DFB for Modbus/TCP for Quantum PLC. . . . . . . . . . . . . . . . . 72
Custom_mdb_addq: Custom Read DFB for Modbus/TCP for Quantum PLC. . . . . . . . . . . . . . 83
Chapter 5 Profibus DFB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Ctrl_pfb_u_ms: TeSys U Control/Command for Profibus DP MS . . . . . . . . . . . . . . . . . . . . . . . 86
Ctrl_pfb_u_mms: TeSys U Control/Command for Profibus DP MMS . . . . . . . . . . . . . . . . . . . . 88
Ctrl_pfb_t_mms: TeSys T Control/Command for Profibus DP MMS . . . . . . . . . . . . . . . . . . . . 90
Chapter 6 Cyclic Control/Command DFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Ctrl_cmd_u: TeSys U Cyclic Control/Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Ctrl_cmd_t: TeSys T Cyclic Control/Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Chapter 7 PKW Exchanges DFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Special_pkw_u: TeSys U DFB for PKW Exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Special_pkw_t: TeSys T DFB for PKW Exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Custom_pkw: Custom Read DFB for PKW Exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Chapter 8 Treatment DFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Scale: TeSys U DFB for Measurement Unit Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Timestamp_•: TeSys U DFB for Data Time-Stamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
1672609 09/2009 3
4 1672609 09/2009
Safety Information
§
Important Information
NOTICE
Read these instructions carefully, and look at the equipment to become familiar with the device before
trying to install, operate, 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 the installation, and has received safety training to recognize and avoid the
hazards involved.
1672609 09/2009 5
BEFORE YOU BEGIN
Do not use this product on machinery lacking effective point-of-operation guarding. Lack of effective
point-of-operation guarding on a machine can result in serious injury to the operator of that machine.
WARNING
UNGUARDED MACHINERY CAN CAUSE SERIOUS INJURY
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 the user can be aware of all the conditions and factors present during setup, operation, and
maintenance of the machine; therefore, only the user 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, the user 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-of-
operation 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.
6 1672609 09/2009
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.
CAUTION
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 injury or equipment damage.
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 grounds, except those grounds
installed according to local regulations (according to the National Electrical Code in the U.S.A, for
instance). If high-potential 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.
Remove ground from incoming power lines.
Perform all start-up tests recommended by the manufacturer.
1672609 09/2009 7
8 1672609 09/2009
About the Book
At a Glance
Document Scope
This manual describes the DFB (Derived Function Block) offer 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 offer 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.
Validity Note
The TeSys DFB V2 offer 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 describes all versions of the TeSys DFB offer. The following table describes the differences
between versions 1 and 2 of the TeSys DFB offer:
1672609 09/2009 9
Related Documents
You can download these technical publications and other technical information from our website at
www.schneider-electric.com.
User Comments
We welcome your comments about this document. You can reach us by e-mail at techcomm@schneider-
electric.com.
10 1672609 09/2009
Introduction
1672609 09/2009
Introduction
1
Introduction
This chapter gives an overview of the TeSys U and TeSys T DFB (Derived Function Block) offer,
presents the DFB offer download procedure from the Schneider Electric website, and describes the
sequencing system used to synchronize the treatment between DFBs.
1672609 09/2009 11
Introduction
Presentation
have a functional view of the motor-starter by providing direct access to common functions (Ready,
Fault, Alarm, Run, Stop,...),
group data related to a specific application (diagnostic, maintenance, measurement,...) through a
program number,
facilitate debugging: all variables used by the DFB are identified on its interface.
This manual describes only DFBs relevant for the Unity Pro programming platform. For more information
regarding DFBs for the PL7 programming platform, see the TeSys DFB Offer for PL7 User Manual.
TeSys Compliance
The TeSys DFB offer for Unity Pro is compliant with:
TeSys U starter-controllers (up to 32 A/15 kW or 20 hp),
TeSys T motor management system.
12 1672609 09/2009
Introduction
1672609 09/2009 13
Introduction
14 1672609 09/2009
Introduction
1672609 09/2009 15
Introduction
16 1672609 09/2009
Introduction
1672609 09/2009 17
Introduction
18 1672609 09/2009
Introduction
Download Procedure
The following table describes the steps to follow to download the TeSys DFB library from the
www.schneider-electric.com website:
Step Action
1 Open the Schneider Electric website: www.schneider-electric.com.
2 Click Products and Services, and then click Automation and Control.
3 In the Downloads section of the left menu bar, click Current offers.
4 In the Choose a function drop-down list, select Motor Control.
In the Choose a range drop-down list, select TeSys U.
In the Choose a type of document drop-down list, select Software/Firmware.
Click >Find
5 Select TeSys DFB Library for Unity Pro and download the zip file.
6 Extract the TeSys DFB Library for Unity Pro.zip file content to a single directory on your hard disk.
7 Double-click the .setup file to launch the installation of the library and user manual. Follow the
instructions provided to complete the installation.
NOTE: Unity Pro V2 can be installed successfully only if there is an existing version of Unity Pro on
the machine which is the target of the installation.
1672609 09/2009 19
Introduction
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:
Ctrl_cmd_mdb_u_••••
Ctrl_cmd_mdb_t_••••
Special_mdb_u_••••
Special_mdb_t_••••
Custom_mdb_••••
Special_pkw_u
Special_pkw_t
Custom_pkw
Timestamp_•
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/Output Description
Rst_cmd This command resets the DFB and/or restarts the DFB treatment if Strt_cmd is set to 1.
Strt_cmd This command starts the DFB treatment.
Fault_st This 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_st This status bit indicates
a reset in progress,
a treatment in progress.
End_st This status bit indicates the end of the DFB treatment.
20 1672609 09/2009
Introduction
1672609 09/2009 21
Introduction
22 1672609 09/2009
Modbus SL DFB
1672609 09/2009
Modbus SL DFB
2
Introduction
This chapter describes the TeSys U and TeSys T Modbus SL (Serial Line) DFBs.
1672609 09/2009 23
Modbus SL DFB
Presentation
The Ctrl_cmd_mdb_u_•••• DFBs are dedicated to the control and command of a single TeSys U starter-
controller (up to 32 A/15 kW or 20 hp) 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 TeSys U LULC032-033 Modbus Communication Module User Manual.
Characteristics
Characteristic Value
Name Ctrl_cmd_mdb_u_addr Ctrl_cmd_mdb_u_addm
Version 1.00 1.00
Input 11 11
Output 13 13
Input/Output 0 0
Public Variable 6 8
Graphical Representation
TeSys U Compliance
The Ctrl_cmd_mdb_u_•••• DFBs are compliant with the following TeSys U sub-assemblies:
24 1672609 09/2009
Modbus SL DFB
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 and their availability according to the control unit:
1672609 09/2009 25
Modbus SL DFB
Program Number
The program number enables the user to select bit or word control.
The following table describes the programs of the DFB:
Output Characteristics
The following table describes the DFB outputs and their availability according to the control unit:
26 1672609 09/2009
Modbus SL DFB
The following table describes the Ctrl_cmd_mdb_u_addm DFB public variables (using M340 addressing)
and their availability according to the control unit:
1672609 09/2009 27
Modbus SL DFB
Presentation
The Comm_manager_u DFB is dedicated to the control and command of up to 31 TeSys U starter-
controllers (up to 32 A/15 kW or 20 hp) 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 TeSys U LULC032-033 Modbus Communication Module User Manual.
Characteristics
Characteristic Value
Name Comm_manager_u
Version 1.00
Input 4
Output 4
Input/Output 0
Public Variable 3
Graphical Representation
TeSys U Compliance
The Comm_manager_u DFB is compliant with the following TeSys U sub-assemblies:
28 1672609 09/2009
Modbus SL DFB
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:
Input Characteristics
The following table describes the DFB inputs:
Output Characteristics
The following table describes the DFB outputs:
1672609 09/2009 29
Modbus SL DFB
Public Variable Type Bit Description Corresponding to the LUCA LUCB LUCM
TeSys U Slave 1...31 LUCL LUCC
LUCD
In_cmd[0] INT — Not significant — — —
In_cmd[1]...[31] INT 0 Motor run forward command √ √ √
1 Motor run reverse command √ √ √
2 Reserved — — —
3 Reset device √ √ √
(if register 451 = 102 or 104, fault
acknowledgment causes a return to
communication module factory
settings)
4 Reserved — — —
5 Automatic thermal overload fault test — — √
6 Overcurrent trip test via communication — — √
bus
7 Reserved — — —
8 Reset warning (for example, √ √ √
communication loss)
9...15 Reserved — — —
30 1672609 09/2009
Modbus SL DFB
Public Variable Type Bit Description Corresponding to the LUCA LUCB LUCM
TeSys U Slave 1...31 LUCL LUCC
LUCD
Out_st[0] INT — Not significant — — —
Out_st[1]...[31] INT 0 System ready: the rotary handle is √ √ √
turned to On position and there is no
fault.
1 Pole status: closed √ √ √
2 All faults √ √ √
3 All warnings √ √ √
4 System tripped: the rotary handle is √ √ √
turned to Trip position.
5 Fault reset is authorized — √ √
6 Reserved — — —
7 Motor running with detection of current, if — √ √
greater than 10% FLA
8...13 Average motor current (% FLA) — √ √
32 = 100% FLA
63 = 200% FLA
14 Reserved — — —
15 Start in progress: — √ √
1 = ascending current is greater than
10% FLA
0 = descending current is lower than
150% FLA
1672609 09/2009 31
Modbus SL DFB
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 TeSys T LTM R Modbus Motor Management Controller User Manual.
Characteristics
Characteristic Value
Name Ctrl_cmd_mdb_t_addr Ctrl_cmd_mdb_t_addm
Version 1.00 1.00
Input 10 10
Output 24 24
Input/Output 0 0
Public Variable 6 8
Graphical Representation
32 1672609 09/2009
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:
Program Number
The program number enables the user to select bit or word control.
The following table describes the programs of the DFB:
1672609 09/2009 33
Modbus SL DFB
Output Characteristics
The following table describes the DFB outputs:
34 1672609 09/2009
Modbus SL DFB
The following table describes the Ctrl_cmd_mdb_t_addm DFB public variables (using M340 addressing):
1672609 09/2009 35
Modbus SL DFB
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_•••• DFBs to manage the Modbus requests sequencing.
The number of TeSys T Modbus slaves is defined in the Slav_num variable (Slav_num = 1...31).
For more information, see the TeSys T LTM R Modbus Motor Management Controller User Manual.
Characteristics
Characteristic Value
Name Comm_manager_t
Version 1.0
Input 4
Output 4
Input/Output 0
Public Variable 3
Graphical Representation
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.
36 1672609 09/2009
Modbus SL DFB
Software Implementation
The following figure shows a Unity Pro program extract in FBD language showing how to interconnect
the Ctrl_cmd_mdb_t_addr and the Comm_manager_t DFBs:
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:
1672609 09/2009 37
Modbus SL DFB
Output Characteristics
The following table describes the DFB outputs:
Public Variable Type Bit Description Corresponding to the TeSys T Slave 1...31
In_cmd[0] INT — Not significant
In_cmd[1]...[31] INT 0 Motor run forward command
1 Motor run reverse command
2 Reserved
3 Fault reset command
4 Reserved
5 Self test command
6 Motor low speed command
7...31 Reserved
38 1672609 09/2009
Modbus SL DFB
1672609 09/2009 39
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:
40 1672609 09/2009
Modbus SL and Modbus/TCP DFB
1672609 09/2009
3
Introduction
This chapter describes the TeSys U and TeSys T Modbus SL and Modbus/TCP DFBs dedicated to
Premium and M340 PLCs.
1672609 09/2009 41
Modbus SL and Modbus/TCP DFB
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 TeSys U LULC032-033 Modbus Communication Module User Manual.
Characteristics
Characteristic Value
Name Special_mdb_u_addr Special_mdb_u_addm
Version 1.00 and 1.10 1.00 and 1.10
Input 4 4
Output 3 3
Input/Output 0 0
Public Variable 7 9
Graphical Representation
TeSys U Compliance
The Special_mdb_u_•••• DFBs are compliant with the following TeSys U sub-assemblies:
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.
42 1672609 09/2009
Modbus SL and Modbus/TCP DFB
Input Characteristics
The following table describes the DFB inputs:
Output Characteristics
The following table describes the DFB outputs:
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:
1672609 09/2009 43
Modbus SL and Modbus/TCP DFB
The following table describes the Special_mdb_u_addm DFB public variables (using M340 addressing):
44 1672609 09/2009
Modbus SL and Modbus/TCP DFB
1672609 09/2009 45
Modbus SL and Modbus/TCP DFB
46 1672609 09/2009
Modbus SL and Modbus/TCP DFB
1672609 09/2009 47
Modbus SL and Modbus/TCP DFB
48 1672609 09/2009
Modbus SL and Modbus/TCP DFB
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 SL Motor Management Controller User Manual
TeSys T LTM R Modbus/TCP Motor Management Controller User Manual
Characteristics
Characteristic Value
Name Special_mdb_t_addr Special_mdb_t_addm
Version 1.00 and 1.10 1.00 and 1.10
Input 4 4
Output 3 3
Input/Output 0 0
Public Variable 7 9
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:
1672609 09/2009 49
Modbus SL and Modbus/TCP DFB
Output Characteristics
The following table describes the DFB outputs:
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:
50 1672609 09/2009
Modbus SL and Modbus/TCP DFB
The following table describes the Special_mdb_t_addm DFB public variables (using M340 addressing):
1672609 09/2009 51
Modbus SL and Modbus/TCP DFB
52 1672609 09/2009
Modbus SL and Modbus/TCP DFB
1672609 09/2009 53
Modbus SL and Modbus/TCP DFB
54 1672609 09/2009
Modbus SL and Modbus/TCP DFB
1672609 09/2009 55
Modbus SL and Modbus/TCP DFB
56 1672609 09/2009
Modbus SL and Modbus/TCP DFB
1672609 09/2009 57
Modbus SL and Modbus/TCP DFB
58 1672609 09/2009
Modbus SL and Modbus/TCP DFB
1672609 09/2009 59
Modbus SL and Modbus/TCP DFB
60 1672609 09/2009
Modbus SL and Modbus/TCP DFB
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
Characteristic Value
Name Custom_mdb_addr Custom_mdb_addm
Version 1.00 and 1.10 1.00 and 1.10
Input 3 3
Output 3 3
Input/Output 0 0
Public Variable 13 15
Graphical Representation
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.
1672609 09/2009 61
Modbus SL and Modbus/TCP DFB
Input Characteristics
The following table describes the DFB inputs:
Output Characteristics
The following table describes the DFB outputs:
62 1672609 09/2009
Modbus SL and Modbus/TCP DFB
The following table describes the Custom_mdb_addm DFB public variables (using M340 addressing):
1672609 09/2009 63
Modbus SL and Modbus/TCP DFB
64 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
1672609 09/2009
4
Introduction
This chapter describes the TeSys U and TeSys T Modbus/TCP DFBs dedicated to Quantum PLC.
1672609 09/2009 65
Modbus/TCP DFB 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 TeSys U LULC032-033 Modbus Communication Module User Manual.
Characteristics
Characteristic Value
Name Special_mdb_u_addq
Version 1.00
Input 4
Output 5
Input/Output 0
Public Variable 7
Graphical Representation
TeSys U Compliance
The Special_mdb_u_addq DFBs are compliant with the following TeSys U sub-assemblies:
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:
66 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
Output Characteristics
The following table describes the DFB outputs:
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:
1672609 09/2009 67
Modbus/TCP DFB for Quantum PLC
68 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
1672609 09/2009 69
Modbus/TCP DFB for Quantum PLC
70 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
1672609 09/2009 71
Modbus/TCP DFB 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 TeSys T LTM R Modbus/TCP Motor Management Controller User Manual.
Characteristics
Characteristic Value
Name Special_mdb_t_addq
Version 1.00
Input 3
Output 5
Input/Output 0
Public Variable 7
Graphical Representation
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:
Output Characteristics
The following table describes the DFB outputs:
72 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
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:
1672609 09/2009 73
Modbus/TCP DFB for Quantum PLC
74 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
1672609 09/2009 75
Modbus/TCP DFB for Quantum PLC
76 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
1672609 09/2009 77
Modbus/TCP DFB for Quantum PLC
78 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
1672609 09/2009 79
Modbus/TCP DFB for Quantum PLC
80 1672609 09/2009
Modbus/TCP DFB for Quantum PLC
1672609 09/2009 81
Modbus/TCP DFB for Quantum PLC
82 1672609 09/2009
Modbus/TCP DFB 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
Characteristic Value
Name Custom_mdb_addq
Version 1.00
Input 3
Output 5
Input/Output 0
Public Variable 13
Graphical Representation
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:
1672609 09/2009 83
Modbus/TCP DFB for Quantum PLC
Output Characteristics
The following table describes the DFB outputs:
84 1672609 09/2009
Profibus DFB
1672609 09/2009
Profibus DFB
5
Introduction
This chapter describes the TeSys U and TeSys T Profibus DP DFBs.
1672609 09/2009 85
Profibus DFB
Presentation
The Ctrl_pfb_u_ms DFB is dedicated to the control and command of a single TeSys U starter-controller
(up to 32 A/15 kW or 20 hp) 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 TeSys U LULC07 Profibus DP Communication Module User Manual.
Characteristics
Characteristic Value
Name Ctrl_pfb_u_ms
Version 1.00
Input 7
Output 10
Input/Output 0
Public Variable 0
Graphical Representation
TeSys U Compliance
The Ctrl_pfb_u_ms DFB is compliant with the following TeSys U sub-assemblies:
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.
86 1672609 09/2009
Profibus DFB
Input Characteristics
The following table describes the DFB inputs and their availability according to the control unit:
Output Characteristics
The following table describes the DFB outputs and their availability according to the control unit:
1672609 09/2009 87
Profibus DFB
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 TeSys U LULC07 Profibus DP Communication Module User Manual.
Characteristics
Characteristic Value
Name Ctrl_pfb_u_mms
Version 1.00
Input 10
Output 13
Input/Output 0
Public Variable 0
Graphical Representation
TeSys U Compliance
The Ctrl_pfb_u_mms DFB is compliant with the following TeSys U sub-assemblies:
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.
88 1672609 09/2009
Profibus DFB
Input Characteristics
The following table describes the DFB inputs:
Output Characteristics
The following table describes the DFB outputs:
1672609 09/2009 89
Profibus DFB
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 TeSys T LTM R Profibus Motor Management Controller User Manual.
Characteristics
Characteristic Value
Name Ctrl_pfb_t_mms
Version 1.00
Input 11
Output 22
Input/Output 0
Public Variable 0
Graphical Representation
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.
90 1672609 09/2009
Profibus DFB
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:
Output Characteristics
The following table describes the DFB outputs and their availability according to the programming
platform:
1672609 09/2009 91
Profibus DFB
92 1672609 09/2009
Cyclic Control/Command DFB
1672609 09/2009
6
Introduction
This chapter describes the TeSys U and TeSys T cyclic control/command DFBs.
1672609 09/2009 93
Cyclic Control/Command DFB
Presentation
The Ctrl_cmd_u DFB is dedicated to the control and command of a single TeSys U starter-controller (up
to 32 A/15 kW or 20 hp) 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
Characteristic Value
Name Ctrl_cmd_u
Version 1.00 and 1.10
Input 7
Output 11
Input/Output 0
Public Variable 0
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
TeSys U Compliance
The Ctrl_cmd_u DFB is compliant with the following TeSys U sub-assemblies:
94 1672609 09/2009
Cyclic Control/Command DFB
Input Characteristics
The following table describes the DFB inputs and their availability according to the control unit:
Output Characteristics
The following table describes the DFB outputs and their availability according to the control unit:
1672609 09/2009 95
Cyclic Control/Command DFB
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 LTM R Modbus/TCP Motor Management Controller User Manual
TeSys T LTM R CANopen Motor Management Controller User Manual
Characteristics
Characteristic Value
Name Ctrl_cmd_t
Version 1.00 and 1.10
Input 7
Output 21
Input/Output 0
Public Variable 0
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
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.
96 1672609 09/2009
Cyclic Control/Command DFB
Input Characteristics
The following table describes the DFB inputs:
Output Characteristics
The following table describes the DFB outputs:
1672609 09/2009 97
Cyclic Control/Command DFB
98 1672609 09/2009
PKW Exchanges DFB
1672609 09/2009
7
Introduction
This chapter describes the TeSys U and TeSys T DFBs for PKW exchanges.
1672609 09/2009 99
PKW Exchanges DFB
Presentation
The Special_pkw_u DFB is 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) with a LUCM multifunction control unit and one of the following
communication modules that support PKW (Periodically Kept in Acyclic Words) exchanges:
LULC07 (Profibus)
LULC08 (CANopen)
LULC15 (Advantys STB)
For more information, see:
TeSys U LULC07 Profibus Communication Module User Manual
TeSys U LULC08 CANopen Communication Module User Manual
TeSys U LULC15 Advantys STB Communication Module User Manual
Characteristics
Characteristic Value
Name Special_pkw_u
Version 1.00
Input 7
Output 3
Input/Output 2
Public Variable 2
Graphical Representation
TeSys U Compliance
The Special_pkw_u DFB is compliant with the following TeSys U sub-assemblies:
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:
Output Characteristics
The following table describes the DFB outputs:
Input/Output Characteristics
The following table describes the DFB input/outputs:
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:
Presentation
The Special_pkw_t DFB is dedicated to the reading of up to 16 predefined registers of a single TeSys T
LTM R••P•• Profibus controller through the Profibus (MS and MMS) network, and a TeSys T LTM R••C••
CANopen controller through the CANopen network, and supporting PKW (Periodically Kept in Acyclic
Words) exchanges.
Characteristics
Characteristic Value
Name Special_pkw_t
Version 1.00
Input 7
Output 3
Input/Output 2
Public Variable 2
Graphical Representation
TeSys T Compliance
The Special_pkw_t DFB is compliant with all the TeSys T LTM R••P•• controller versions, with or without
the LTM E expansion module.
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:
Output Characteristics
The following table describes the DFB outputs:
Input/Output Characteristics
The following table describes the DFB input/outputs:
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 Description
Number
0 Bypass: no action
10 Diagnostic: faults monitoring variables, warnings monitoring variables, and communication
monitoring variables
20 Maintenance: global statistics variables
30 Measurements 1
31 Measurements 2
32 Measurements 3
40 Statistics: last fault statistics (N—0)
41 Statistics: last fault statistics (with expansion module) (N—0)
50 Statistics: N—1 fault statistics
51 Statistics: N—1 fault statistics (with expansion module)
60 Statistics: N—2 fault statistics
61 Statistics: N—2 fault statistics (with expansion module)
70 Statistics: N—3 fault statistics
71 Statistics: N—3 fault statistics (with expansion module)
80 Statistics: N—4 fault statistics
81 Statistics: N—4 fault statistics (with expansion module)
DT_DateTime
DT_DateTime is WORD[4] type and indicates date and time:
Where:
0 = unused
s = second
The format is 2 binary coded decimal (BCD) digits.
The value range is 00...59 in BCD.
m = minute
The format is 2 binary coded decimal (BCD) digits.
The value range is 00...59 in BCD.
H = hour
The format is 2 binary coded decimal (BCD) digits.
The value range is 00...23 in BCD.
D = day
The format is 2 binary coded decimal (BCD) digits.
The value range is (in BCD):
01...31 for months 01, 03, 05, 07, 08, 10, 12,
01...30 for months 04, 06, 09, 11,
01...29 for month 02 in a leap year,
01...28 for month 02 in a non-leap year.
M = month
The format is 2 binary coded decimal (BCD) digits.
The value range is 01...12 in BCD.
Y = year
The format is 4 binary coded decimal (BCD) digits.
The value range is 2006...2099 in BCD.
Data entry format and value range are:
NOTE: If the user enters values outside the defined range, the system will return an error.
Presentation
The Custom_pkw DFB is dedicated to the reading of up to 5 sets of registers of a single TeSys device
supporting PKW (Periodically Kept in Acyclic Words) 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).
The Custom_pkw DFB completes the Special_pkw_u and Special_pkw_t DFBs and enables the user to
select the registers to read.
Characteristics
Characteristic Value
Name Custom_pkw
Version 1.00
Input 6
Output 3
Input/Output 2
Public Variable 7
Graphical Representation
TeSys T: The Custom_pkw DFB is compliant with all the LTM R controller versions, with or without the
LTM E expansion module.
When using TSXPBY100 Premium Profibus coupler it is mandatory to set %QWxy.0.242:X0 to 1 to
guarantee the data consistency.
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 output words must be linked to the first word of 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).
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.
The following table describes the values of the corresponding In_reg and In_len public variables:
The following table describes the values of the corresponding Out_dat public variables:
Input Characteristics
The following table describes the DFB inputs:
Output Characteristics
The following table describes the DFB outputs:
Input/Output Characteristics
The following table describes the DFB input/outputs:
Treatment DFB
8
Introduction
This chapter describes the Scale and Timestamp treatment DFBs.
Presentation
The Scale DFB is dedicated to the conversion of current measurement unit from relative value (% FLC)
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.
The Scale DFB is particularly used with the Special_pkw_u or the Special_mdb_u_•••• DFBs.
Characteristics
Characteristic Value
Name Scale
Version 1.00
Input 1
Output 1
Input/Output 0
Public Variable 22
Graphical Representation
TeSys U Compliance
The Scale DFB is compliant with the following TeSys U sub-assemblies:
Software Implementation
See the Special_mdb_u_•••• DFB public variables description in Public Variables Characteristics,
page 44.
The Scale DFB converts the measurements unit from % FLA to A and to any unit in the A...mA range:
The Out_ri output variables return the current measurements in A.
The Out_ii output variables return the current measurements in the unit chosen by the user in the
A...mA range.
If a fault occurs:
the Special_mdb_u_•••• DFB outputs are set to —1,
the Scale DFB outputs are set to —1,
the Scale DFB Fault_st output is set to 1.
Input Characteristics
The following table describes the DFB input:
Output Characteristics
The following table describes the DFB output:
Presentation
The Timestamp_• 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 (see DT_DateTime, page 118).
Timestamp is compatible with Premium and M340 PLCs.
Timestamp_q is compatible with Quantum PLCs.
Characteristics
Characteristic Value
Name Timestamp Timestamp_q
Version 1.00 1.00
Input 3 3
Output 3 3
Input/Output 0 0
Public Variable 3 3
Graphical Representation
TeSys U Compliance
The Timestamp_• DFBs are compliant with all the TeSys U sub-assemblies.
Input Characteristics
The following table describes the DFB inputs:
Output Characteristics
The following table describes the DFB outputs: