Schneider Electric assumes no responsibility for any errors that may appear in this document. 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.
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.
1743234 03/20095
61743234 03/2009
At a Glance
Document Scope
Validity Note
About the Book
This Manual describes the implementation, functions and operation of the LULC032-033 Modbus
communication module.
Area of application: mainly control system applications in the Industry and Building sectors.
Firmware version compatibility:
Product versions
LULC03•LUTMLUCMLUCMT
V1.1V1.1---V2.06
LULC032
LULC033V2.2V1.2*V1.10*V2.11*
V1.2V1.2*---V2.10*
V1.3V1.2*---V2.11*
Related Documents
User Comments
* and later versions.
Title of DocumentationReference Number
LULC033 Modbus Module - Instruction Sheet1743239
LU9GC3 Modbus Tap Module - Instruction Sheet1638860
TeSys U Communication Variables - User’s Manual1744082
LU•B/LU•S• TeSys U Starters - Instruction Sheet1629984
LUTM• TeSys U Controller - User’s Manual1743233
LUTM• TeSys U Controller - Instruction Sheet1743236
LUCM/LUCMT Multifunction Control Units - User’s Manual1743237
LUCM/LUCMT/LUCBT/LUCDT Control Units - Instruction SheetAAV40504
LUCA/LUCB/LUCC/LUCD Control Units - Instruction SheetAAV40503
Modbus Over Serial Line, Specification & Implementation GuideModbus_over_serial_line_V1
You can download these technical publications and other technical information from our website at
www.schneider-electric.com.
We welcome your comments about this document. You can reach us by e-mail at techcomm@schneiderelectric.com.
1743234 03/20097
81743234 03/2009
Hard
Introduction
What's in this Part?
ware Implementation
1743234 03/2009
Hardware Implementation
I
This section describes the LULC032-033 Modbus communication module installation and technical
characteristics.
This part contains the following chapters:
ChapterChapter NamePage
1Installing the LULC032-033 Modbus Module11
2Technical Characteristics31
1743234 03/20099
Hardware Implementation
10
1743234 03/2009
I
nsta
lling the LULC032-033 Modb
1743234 03/2009
Installing the LULC032-033 Modbus Module
Introduction
This chapter introduces the LULC032-033 Modbus communication module and describes the various
steps involved in the physical installation of the product.
What's in this Chapter?
This chapter contains the following topics:
Safety Instructions12
Presentation of the LULC032-033 Modbus Communication Module13
Description of the Module and Installation15
Electrical Connection18
Connection to the RS485 Bus23
us Module
1
TopicPage
1743234 03/200911
Installing the LULC032-033 Modbus Module
Safety Instructions
General Instructions
HAZARDOUS OPERATION
These devices must be installed, configured and used by qualified staff only.
Users must follow all current instructions, standards and regulations.
Check the function settings before starting the motor.
Do not downgrade or modify these devices.
Failure to follow these instructions can result in injury or equipment damage.
PRECAUTIONS WHEN USING COMMUNICATION VARIABLES
Only use the serial link for transmitting data that is not critical to the application.
There is some delay in the transmission of data relating to motor-starter states and load-current values.
This data must not therefore be used in the management of safety devices and emergency stops.
Data such as Forward, Reverse and Stop must not be used in safety and emergency-stop circuits.
Failure to follow these instructions can result in injury or equipment damage.
CAUTION
CAUTION
12
1743234 03/2009
Presentation of the LULC032-033 Modbus Communication Module
Receiving the Product
On opening the box containing the LULC032-033 Modbus communication module, you should find the
following items:
- An Instruction Sheet (IS), providing brief pictorial information about the standard installation of the
module
- An LULC032-033 Modbus communication module with connectors.
NOTE: Check that you actually have all the items described above. Make sure that the Quick Reference
Guide is included, along with the correctly inserted connectors.
Functions offered
The communication module is used to control a motor-starter remotely, via Modbus, from:
LULC032LULC033
TeSys U starter-controllerLUB••/LU2B••
TeSys U starterLUS••/LU2S••
TeSys U controllerLUTM••
NOTE: Modbus LULC032 communication modules should be used exclusively with LUTM10BL or
LUTM20BL controllers.
Using the communication module, you can:
Read the motor-starter states
Control the motor-starter (reversing or non-reversing)
Adjust the protection functions
Read the data processed in the advanced and multifunction control units
Read the state of the I/O (controller base)
Installing the LULC032-033 Modbus Module
DANGER
CONTROL VOLTAGE
The LULC032 Modbus communication module must only be used with 24 V control units (LUC•••BL).
.
Failure to follow these instructions will result in death or serious injury.
NOTE: For information on the Modbus protocol, please refer to the following website: www.Modbus.org.
1743234 03/200913
Installing the LULC032-033 Modbus Module
Data Available
The available protection and control data depend on the control unit with which the Modbus
communication module is used.
The table below can be used to check the data and commands you can access with each type of control
unit:
Data - Commands
Start and stop commands
Status (ready, running, fault
condition)
Warning
Automatic reset and remote reset
via the bus
Indication of the motor load
Differentiation of faults
Remote parameter setting and
viewing of all functions
'Log' function
'Monitoring' function
Control unit
Standard
(LUCA)
Advanced
(LUCB/C/D,
LUCBT/DT)
Multifunction
(LUCM/MT)
14
1743234 03/2009
Description of the Module and Installation
Diagram of the Module
Connectors and indicator lights (LEDs) on the LULC032-033 Modbus communication module :
Installing the LULC032-033 Modbus Module
NOTE: The pinout differs from that on the LULC031 Modbus communication module.
1 Green "COMM" Modbus communication status LED.
2 Red "ERR" Modbus communication module fault indication LED.
3 Green "24V " LED indicating voltage presence at outputs OA1, OA3, LO1.
4 RJ45 connector for the Modbus RS485 link.
5 Connection of the module power supply.
6 Connection of the 24 V power supply for outputs OA1, OA3, LO1.
7 Discrete input 2.
8 Discrete input 1.
9 Discrete output 1, assignable depending on the configuration register (685 LSB).
10 24 V prewired coil connector for the power base.
The assignment of OA1 depends on the configuration register (686 LSB).
The assignment of OA3 depends on the configuration register (686 MSB).
11 Connector for communication with the advanced or multifunction control unit.
1743234 03/200915
Installing the LULC032-033 Modbus Module
Description of Indicator Lights (LEDs)
Description of the various states of the indicator lights (light-emitting diodes, LEDs) on the LULC032-033
Modbus communication module.
Light-emitting diodes (LEDs)
Green "COMM"
LED
Flashing (alternately
with the "ERR" LED)
Flashing during
communication with
the Module address
Off
Red "ERR" LED
Flashing
(alternately with
the "COMM" LED)
OffOnNormal operation
OffOff
OnOn
FlashingOn
Green "24V
" LED
On
Meaning
Bus parameter initialization in
progress
Faulty: 24 V DC voltage
missing on the 24 V DC
terminal. Check the connection
between the power supply and
the communication module.
Internal fault on the LULC032033 Internal Faults, page 59
Loss of communication on the
Modbus network
NOTE: During startup, because the default fallback mode is "forced stop", if no communication has
previously been established, the red "ERR" LED will flash after one minute (default timeout value).
Addressing Using Switches
The Modbus communication module address is defined by switches located on the underside of the
module. Simply turn the module over to access them:
The range of accepted values is between 1 and 31.
The address coding is in binary format.
The least significant bit is on the right, indicated by.
Address 0 is not taken into account by the module, since it is used by the Master for a broadcast request.
Caution: Address selection differs from that on the LULC031 Modbus communication module.
NOTE: Addressing is only taken into account when the communication module is powered up.
16
1743234 03/2009
Order of Mounting on a Base
The LULC032 module is installed in a controller base, the LULC033 module is installed in a power base
or a controller base (on the underside of the control unit which locks it in position).
To install the module in the power base or controller base:
StepAction
1Choose the prewired coil connection terminals.
2Insert the LULC032-033 Modbus communication module.
3Insert the control unit which locks the module.
The diagram below illustrates these steps. Installation of the LULC032-033 Modbus communication
module corresponds to step (2). The numbers indicate both the order of mounting for the components
and their location.
Installing the LULC032-033 Modbus Module
1743234 03/200917
Installing the LULC032-033 Modbus Module
Electrical Connection
24 V and 24 V Aux Power Supply
Diagram for 24 V and 24 V Aux power supplies.
18
1743234 03/2009
Power-up with an LUCM Multifunction Control Unit
LUCM and Power Base
The power-supply source must be the same for the LULC032-033 Modbus communication module and
the LUCM multifunction control unit.
It is essential that the LUCM multifunction control unit and the LULC032-033 Modbus communication
module are powered up simultaneously. Indeed, monitoring of the internal dialog between the LUCM and
the LULC032-033 will produce two error messages depending on the order in which these objects were
powered up.
When the A1-A2 terminals are not yet powered up (24V ), there are 3 possible scenarios for powering
up the 24V Aux:
Installing the LULC032-033 Modbus Module
Powering
up the
LUCM ...
SimultaneouslyRecommended
1st2nd
2nd1st
Powering up
the
LULC032-033
...
Comment
The "M15" fault is displayed. This only occurs when the LULC032-033 Modbus
communication module has already been used with the LUCM multifunction control
unit.
The LUCM control unit is identified by the LULC032-033 Modbus communication
module when the 24 V Aux for the LULC032-033 Modbus communication module is
switched on.
If the 24 V Aux for the LUCM control unit is switched on for longer than twice the
duration of the timeout (i.e., more than 1 s), the "M101" fault is displayed (register
451, communication module internal faults).
NOTE: Both these faults are reset by powering down and then powering up the LULC032-033 Modbus
communication module (power cycle) and the LUCM control unit.
LUCM and Controller Base
The 24 V module power supply is provided by the LUTM controller.
1743234 03/200919
Installing the LULC032-033 Modbus Module
Power Supply for the LULC032 and Outputs OA1, OA3 and LO1
In order to operate, the LULC032-033 Modbus communication module must be powered by a 24 V
source:
With a power base, the LULC033 must be powered by an external source.
With a controller base, the LULC032 or LULC033 is powered directly.
Power Supply for LUB••/LUS•• /LU2B••/LU2S•• Power Bases
1 24 V Aux: Power-supply terminal for the LULC033 Modbus communication module.
2 24 V ==: Power-supply terminal for outputs OA1 OA3 and LO1.
3 Prewired link for connecting outputs OA1 and OA3 to terminals A1/A3/A2 on the starter.
Power Supply for an LUTM Controller Base
1 24 V ==: Power-supply terminals for the LUTM and the LULC032-033 Modbus communication module via an
internal link.
2 The 24 V == power supply for the LULC032-033 Modbus communication module is only required when using
outputs OA1, OA3 and LO1.
20
1743234 03/2009
Power Base: Terminal Power Supply
The user has two options for connecting the power-base terminals:
Power supply via the LULC033 Modbus communication module with a prewired link
Direct power supply with a wire-to-wire link
Prewired Link
Catalog numbers for the two prewired coils:
DesignationWith a power baseCatalog number
Prewired coil
Illustration for both types of power base:
Installing the LULC032-033 Modbus Module
LUB••/LUS••LU9B N11C
LU2B••/LU2S••LU9M RC
Wire-to-Wire Link (Power Supply to Outputs OA1, OA3 and LO1)
This type of link is compulsory in the case of a reversing starter-controller created from an LU6M
reversing unit, for separate assembly.
The wire-to-wire link can also be used to insert a local or external stop command, for example.
1743234 03/200921
Installing the LULC032-033 Modbus Module
Connection Capacities of the LULC032-033 Terminals
The table below shows the conductor cross-sections to be used:
ConnectionType of conductorCross-section (min. - max.)
Solid conductor
Stranded conductor
1 conductor
2 conductors (same
cross-section)
Connectors3 and 6 pts
Increment3.81 mm 0.15 in.
Tightening torque0.2/0.25 N.m. 28.3/35.4 lb-in.
Flat screwdriver2.5 mm 0.10 in.
Stranded conductor with cable end:
- Non-insulated
- Insulated
2 solid conductors
2 stranded conductors
2 stranded conductors with cable end:
- Non-insulated
- Insulated
0.14 ... 1 mm
0.14 ... 1 mm
0.25 ... 1 mm
2
2
2
0.25 ... 0.5 mm
0.14 ... 0.5 mm
0.14 ... 0.75 mm
0.25 ... 0.34 mm
0.50 mm
2
AWG 26 ... AWG 18
AWG 26 ... AWG 18
AWG 24 ... AWG 18
2
2
2
2
AWG 24 ... AWG 20
AWG 26 ... AWG 20
AWG 26 ... AWG 20
AWG 24 ... AWG 22
AWG 20
22
1743234 03/2009
Connection to the RS485 Bus
General
There are several ways in which the user can connect the communication module to the RS 485 bus:
Direct connection to the bus via a VW3A8306TF•• T-junction box
Connection to the bus via a splitter box
Connection to the bus via SCA type junction boxes
For Interference Protection:
Use the Schneider Electric cable with 2 pairs of shielded twisted conductors (references: TSXCSA100,
TSXCSA200, TSXCSA500, VW3A8306TF••).
Keep the Modbus cable away from the power cables (at least 30 cm).
Create crossovers of the Modbus cable and the power cables at right-angles, if necessary.
NOTE: For more information, consult guide TSX DG KBL F: "Electromagnetic Compatibility of Industrial
Networks and Fieldbuses".
The RS 485 standard allows variants of some characteristics:
Polarization
Line terminator
Number of slaves
Length of bus
The new Modbus specification, published in 2002 on the Modbus.org site, defines all these characteristics precisely. All new Schneider Electric devices conform to this specification.
Installing the LULC032-033 Modbus Module
Connection to the Bus via a Tee
The standard diagram corresponds to the Modbus specification published in 2002 on the Modbus.org site
(Modbus_over_serial_line_V1.pdf, Nov 2002) and in particular to the 2-wire multidrop serial bus diagram.
The LULC032-033 Modbus communication module conforms to this specification.
The simplified diagram is as follows:
Master
Slave 1Slave 2
1743234 03/200923
Installing the LULC032-033 Modbus Module
The characteristics for direct connection to the bus are as follows:
DesignationDescription
Type of trunk cableSingle shielded twisted pair cable and at least a 3rd conductor
Maximum length of bus1000 m at 19,200 bps with the Schneider Electric TSX CSA•• cable
Maximum number of stations
(without repeater)
Maximum length of tap-offs
Bus polarization
Line terminatorA 150 ohm resistor +/- 5%
Common polarityYes (Common), connected to the protective ground in at least one point on the bus
Connection to the Bus via a Splitter Box
The connection diagram for connection to the bus via a splitter box is as follows:
32 stations, i.e., 31 slaves
20 m for one tap-off
40 m divided by the number of tap-offs on the multiple junction box
A 450 to 650 ohm pulldown resistor at the 5 V
A 450 to 650 ohm pulldown resistor at the Common
This polarization is recommended for the master. There is no polarization at the
RS 485 terminal on the communication module.
24
1 Master (PLC, PC or communication module)
2 Modbus cable depending on the type of master (with polarization integrated on the master side or on another part
of the bus)
3 Modbus splitter box LU9 GC3
4 Modbus drop cables VW3 A8 306 R••
5 Line terminators VW3 A8 306 R
6 Modbus T-junction boxes VW3A8306TF•• (with cable)
7 Modbus cable (to another splitter box) TSX CSA•00 (replaces (5))
NOTE: It is advisable to place a line terminator at each end of the bus to avoid malfunctions on the
communication bus. This means that a tee should not have a free connector. It is either connected to a
slave or to the master, or there is a line terminator.
NOTE: It is important to connect the bus to the "IN" input (or the screw terminals on the bottom) of the
splitter box. Connection to another splitter box is made via the "OUT" output.
1743234 03/2009
Connection Diagrams (PLC <=> Splitter Box)
The two diagrams below describe the connection between:
Channel 0 of the TSX CSY 21601 module and the LU9 GC3 splitter box using cable
TSX SCY CM6030
PCMCIA card TSX SCP 114 and the LU9 GC3 splitter box using cable TSX SCP CX4030
NOTE: Ensure that the 470 ohm resistors are connected to the 0 V and 5 V polarities correctly.
Connection between TSX SCY 21601 module (channel 0) and splitter box LU9 GC3 using cable TSX
SCY CM6030:
Installing the LULC032-033 Modbus Module
1 Green/White
2 White/Green
3 Orange/White
4 White/Orange
5 Brown/White
1743234 03/200925
Installing the LULC032-033 Modbus Module
Connection between PCMCIA/TSX SCP 114 card and LU9 GC3 splitter box using cable TSX SCP
CX4030:
Modbus T-junction boxesWith 0.3 m integrated cableVW3 A8 306 TF03
With 1 m integrated cableVW3 A8 306 TF10
Line terminatorsFor RJ45 connectorR = 150 ohmsVW3 A8 306 R
List of connection cables:
DesignationLength (meters)ConnectorsCatalog number
Cables for Modbus bus31 RJ45 connector and 1 stripped endVW3 A8 306 D30
RS 485 double shielded
twisted pair cables
0,3
1VW3A8 306R10
3VW3A8 306R30
100
200TSX CSA 200
300TSX CSA 500
2 RJ45 connectors
Supplied without connector
VW3A8 306R03
TSX CSA 100
26
1743234 03/2009
Installing the LULC032-033 Modbus Module
List of Modbus connection accessories for RJ45 wiring system:
Type of masterInterface with the masterDescriptionCatalog number
Twido PLCMini-DIN RS 485 adaptor or
interface module
Screw terminal RS 485
adaptor or interface module
TSX Micro PLCMini-DIN RS 485 terminal
port
PCMCIA card
(TSX SCP114)
TSX Premium PLCTSX SCY 11601 or TSX
SCY 21601 module (25-pin
SUB-D port)
PCMCIA card (TSX
SCP114)
Fipio (LUFP1) or
RS 485 RJ45Cable, equipped with 2 RJ45 connectors,
Profibus DP (LUFP7)
or DeviceNet
(LUFP9) gateway
Serial port PCPC with 9-pin male SUB-D
RS 232 serial port
3 m cable equipped with a mini-DIN
TWD XCA RJ030
connector and an RJ45 connector
3 m cable equipped with an RJ45
VW3 A8 306 D30
connector and stripped at the other end
3 m cable equipped with a mini-DIN
TWD XCA RJ030
connector and an RJ45 connector
Stripped cableTSX SCP CX4030
Cable equipped with a 25-pin SUB-D
TSX SCY CM6030
connector and stripped at the other end
(for connection to the screw terminals on
the LU9GC3 splitter box)
Stripped cableTSX SCP CX4030
of the following length:
- 0.3 mVW3 A8 306 R03
- 1 mVW3 A8 306 R10
- 3 mVW3 A8 306 R30
- RS 232/RS 485 converter TSX SCA 72
- 3 m cable equipped with an RJ45
VW3 A8 306 D30
connector and stripped at the other end
(for connection to the screw terminals on
the LU9GC3 splitter box)
1743234 03/200927
Installing the LULC032-033 Modbus Module
Connection to the Bus via SCA Junction Boxes
The connection diagram for connection to the bus via SCA junction boxes is as follows:
1 Master (PLC, PC or communication module).
2 Modbus cable depending on the type of master (with polarization integrated on the master side or on another part
of the bus).
3 Modbus cable TSX CSA•00.
4 TSX SCA 50 junction box (without line polarization).
5 TSX SCA 62 subscriber port (without line polarization).
6 Modbus drop cable VW3 A8 306.
7 Modbus drop cable VW3 A8 306 D30.
List of connection accessories:
DesignationCatalog number
Junction box
3 screw terminals and RC line terminator, connected with cable VW3 A8 306 D30
Subscriber port
2 15-pin female SUB-D connectors, 2 screw terminals, and RC line terminator, connected with
cable VW3 A8 306 or VW3 A8 306 D30
TSX SCA 50
TSX SCA 62
List of connection cables:
DesignationLength
(meters)
Cables for Modbus bus31 RJ45 connector and 1 stripped endVW3 A8 306 D30
51 RJ45 connector and 1 15-pin male SUB-
RS 485 double shielded twisted
pair cables
100
200TSX CSA 200
300TSX CSA 300
ConnectorsCatalog number
VW3 A8 306
D connector for TSX SCA 62
TSX CSA 100
Supplied without connector
28
1743234 03/2009
Installing the LULC032-033 Modbus Module
List of Modbus connection accessories for junction box on screw terminals:
Type of masterInterface with the masterDescriptionCatalog number
Twido PLCScrew terminal RS 485
adaptor or interface module
TSX Micro PLCMini-DIN RS 485 terminal
port
PCMCIA card (TSX
SCP114)
TSX Premium PLCTSX SCY 11601 or TSX
SCY 21601 module (25-pin
SUB-D port)
PCMCIA card (TSX
SCP114)
Profibus DP
(LA9P307) gateway
Fipio (LUFP1) or
Profibus DP (LUFP7)
or DeviceNet (LUFP9)
gateway
Serial port PCPC with 9-pin male SUB-D
RS 485 RJ453 m cable equipped with an RJ45
RS 485 RJ453 m cable equipped with an RJ45
RS 232 serial port
Modbus cableTSX CSA100 or
TSX CSA200 or
TSX CSA500
Junction boxTSX P ACC 01
Cable equipped with a special connector
and stripped at the other end
Cable equipped with a 25-pin SUB-D
connector and stripped at the other end
Cable equipped with a special connector
and stripped at the other end
connector and stripped at the other end
connector and stripped at the other end
RS 232/RS 485 converter and
Modbus cable
TSX SCP CX4030
TSX SCY CM6030
TSX SCP CX4030
VW3 A8 306 D30
VW3 A8 306 D30
TSX SCA 72 and
TSX CSA100 or
TSX CSA200 or
TSX CSA500
RJ45 Connector Pinout
The communication module is connected to the Modbus network with an RJ45 connector in compliance
with the following wiring:
Pin no.Signal
1Do not connect
2Do not connect
3Do not connect
4D(B) or D1
5D(A) or D0
6Do not connect
7Do not connect
80 V.L
1743234 03/200929
Installing the LULC032-033 Modbus Module
30
1743234 03/2009
Technical Ch
1743234 03/2009
Technical Characteristics
Introduction
In addition to information about the module's conditions of use and technical characteristics, this chapter
provides instructions on how to replace an LULC031 module with an LULC032-033.
What's in this Chapter?
This chapter contains the following topics:
Conditions of Use and Technical Characteristics32
Replacing an LULC031 Module with an LULC032-033 Module35
aracteristics
2
TopicPage
1743234 03/200931
Technical Characteristics
Conditions of Use and Technical Characteristics
The characteristics of the LULC032-033 Modbus communication module are as follows:
Conditions of Use
Characteristics of the 24V and 24V Aux power supply circuits
Characteristics of the outputs (OA1, OA3 and LO1) and logic inputs (LI1 and LI2)
The communication characteristics (module Modbus port) are also described.
Conditions of Use
The conditions of use for the LULC032-033 Modbus communication module are as follows:
CertificationUL, CSA
Conformity to
standards
European Community
Directives
Temperature of the
ambient air around the
device
IEC/EN 255-6, UL 508, CSA C22-2 No. 14
marking. Satisfies the essential requirements of the low
voltage (LV) machinery and electromagnetic compatibility
(EMC) directives.
StorageC- 40 ... + 85
OperationC- 25 ... + 55
24V Power Supply Circuit
The characteristics of the LULC032-033 Modbus communication module 24 V power supply circuit
are as follows:
Supply voltage
Maximum current
drawn
Resistance to
microbreaks
24 V Aux power-supply circuit
The characteristics of the LULC032-033 Modbus communication module 24 V Aux power supply circuit
are as follows:
Supply voltage
Maximum current
drawn
Resistance to
microbreaks
U
nominal
Operating rangeV20 ... 28
U
nominal
Operating rangeV20 ... 28
V24 V
A1
ms2
V24 V
mA30
ms3
32
1743234 03/2009
Logic Outputs OA1, OA3 and LO1
The characteristics of the LULC032-033 Modbus communication module outputs are as follows:
Technical Characteristics
Nominal output values
Output limit values
Coincidence factor of
the 3 outputs
Output response time (register 704)
(Time between the request start bit and the change in
the output state)
Protection
Number of operating
cycles
Maximum rateIn operating cycles per hour3600
Logic inputs LI1 and LI2
The characteristics of the LULC032-033 Modbus communication module inputs are as follows:
Nominal input values
Input limit values
Response time
Type of inputResistive
Protectiongl fuseA1
VoltageV24 V
CurrentmA500
VoltageV20 ... 28
CurrentmA500
%66
5 (LUCA/B/C/D)
15 (LUCM)
ms
Against overvoltageYes
Against inversionsYes
Against short-circuits and
overloads
In millions of operating cycles15
VoltageV
CurrentmA7
At state 1
At state 0
Change to state 1ms10 +/- 30 %
Change to state 0ms10 +/- 30 %
VoltageV16
CurrentmA6
VoltageV5
CurrentmA2
30 (LUCBT/DT)
45 (LUCMT)
with stop bit
Electronic circuitbreaker with automatic
reset
20 ... 28
(positive logic)
1743234 03/200933
Technical Characteristics
Communication (Modbus Port)
The technical characteristics of the LULC032-033 Modbus communication module Modbus port are as
follows:
Factory configuration
Physical interface1Multidrop RS 485
ConnectionsRJ45 on the front panel
Connection pinout
ProtocolModbus RTU
Physical addressRange1 to 31 (address 0 not permitted) 1
Indication of communication losses according to the fallback modes:
LULC031LULC032-033
Forced stop mode: Fault indicated
Other modes: Alarm indicated
Any mode: Alarm indicated
Acknowledgment via register 703 bit 3
Firmware version number:
LULC031LULC032-033
Register 62 = version no. x 100Register 62 = version no. x 10,000
NOTE: If you are combining an LULC033 module with a multifunction control unit (LUCM) on a power
base, you must reinitialize the LUCM on first use.
1743234 03/200937
Technical Characteristics
38
1743234 03/2009
Sof
Introduction
What's in this Part?
tware Implementation
1743234 03/2009
Software Implementation
II
Once the LULC032-033 Modbus communication module hardware implementation phase is complete,
the software implementation can begin. It focuses on configuration (the various operating modes), and
the function parameters to be set (e.g., protection, current measurement, etc.).
This part contains the following chapters:
ChapterChapter NamePage
3Starting up the Module via the Registers41
4Fault and Warning Management55
5Configuration of Predefined Functions61
1743234 03/200939
Software Implementation
40
1743234 03/2009
S
tarting up the Module via the Registers
1743234 03/2009
Starting up the Module via the Registers
Introduction
This chapter describes how to start up the LULC032-033 communication module by means of the
Modbus registers. It provides general information, describes the data-exchange format, the product’s
factory configuration and how it can be customized, and also the Modbus read and write requests.
What's in this Chapter?
This chapter contains the following topics:
General Information on Start-up via the Registers 42
Data-Exchange Format43
Factory Configuration45
Customizing Your Configuration46
Modbus Requests and Programming Examples52
Use of the Main Registers for Simplified Management53
3
TopicPage
1743234 03/200941
Starting up the Module via the Registers
General Information on Start-up via the Registers
All the LULC032-033 communication module settings are implemented - or simply displayed - via the
Modbus registers.
Access to Parameters
The module I/O parameters are set by one of the following three methods:
The Modbus RJ45 port, via the application PLC
The LUCM multifunction control unit’s terminal port
Locally, via the LUCM multifunction control unit’s keypad
42
1743234 03/2009
Data-Exchange Format
Modbus Format
Communication is based on the slave Modbus RTU protocol.
The data format is as follows:
1 start bit8 data bits1 parity bit1 stop bit
NOTE: The detailed format of these requests is explained on the www.Modbus.org site.
Initialization
Initialization consists of two phases:
Starting up the Module via the Registers
When the auxiliary 24 V is powered up, the LULC032-033 Modbus communication
module is initialized:
The addressing is taken into account.
The type of control unit is taken into account.
At the end of the initialization phase, the LULC032-033 Modbus communication
module automatically identifies the configuration parameters (speed and parity) of
the RS 485 link as soon as traffic is detected on the network.
After analysis of up to 20 frames at a speed of 19,200 baud, initialization continues
(at 1200 baud, the number of frames is higher):
The default or configured speed is taken into account.
The Master parity is taken into account.
Read-Write Zones
Exception Code
The memory zone from 0 to 19,999 can be accessed by the client.
- Reading the zone of a 'Reserved' register (or non-set) causes a correct response (value 0).
- Writing to the zone of a 'Reserved' register causes a correct response (value 0). The write operation is
not taken into account and the contents remain equal to 0.
- Writing to the zone of a 'Read only' register causes a response with an exception code (code 03).
The memory zone 2000 is private and therefore reading/writing is not authorized. All accesses will be
signaled by an exception code (code 02).
The presence of an exception code is indicated by the report from the PLC (refer to the Modbus master
module documentation).
The Modbus exception codes supported are as follows:
Value of the exception code NameComment
HexadecimalDecimal
0x011Illegal functionUnknown request code
Register address invalid
Access to the private memory
0x022Illegal data address
0x033Illegal data value
zone (address 20000)
Writing to a "read-only" register
The memory zone is prohibited in
both read and write modes
Invalid value
The write command is interrupted
1743234 03/200943
Starting up the Module via the Registers
Speed and Parity
The recognized values are as follows:
Possible valuesFactory value
Speed1200, 2400, 4800, 9600 and 19,200 baud.19,200 baud
ParityEven, odd, no parity (parity bit deleted).Even*
* All versions (except LULC032 < V1.3: factory-configured with "No parity").
TSX Micro or Premium Platform
Applications for Micro and Premium PLCs are designed and implemented using PL7 software.
READ_VAR or WRITE_VAR requests (see Modbus Requests and Programming Examples) are used to
read or write respectively the value of one or more consecutive objects of the same type (bit, word), in
PL7 language.
NOTE: For more details concerning Modbus communication programming within a TSX platform, refer
to the PL7 online help, Communication Volume 2/Modbus communication.
44
1743234 03/2009
Factory Configuration
The communication module parameters are set in order to determine:
The operating mode
The reset mode for thermal overload faults
The correspondence between the communication module outputs and the LUTM controller inputs
The parameter registers (Modbus protocol) are accessible in read/write mode. The factory-set values are
as follows:
Starting up the Module via the Registers
TopicRegister Factor
y
value
Reset mode for thermal
overload fault
Enable communication
between LUCM/MT and
LULC032
Fallback mode for
control outputs on loss of
communication
Local operating mode or
via the bus with the LUTM
and LULC032
Inversion of the LULC032
outputs
On power base,
assignment of:
- Output LO1
- Output OA1
- Output OA3
On controller base,
assignment of:
- Output 13
- Output 23
Recovery mode after
stopping
Control unit ID6900The control unit is identified automatically
602.01"Manual" mode
602.41Communication active
6822
6830
6840
685 LSB
686 LSB
686 MSB
687 LSB
687 MSB1213
6880
2
12
13
Meaning
Forced stop
Power base: OA1 and OA3 at 0
Controller base: 13 and 23 at 0
Mode for controlling the LUTM controller
outputs "remotely via the bus"
The state of the outputs is the image of the
control bits
LO1 is the state of control bit 700.0
OA1 is the state of control bit 704.0
OA3 is the state of control bit 704.1
13 is the state of control bit 704.0
23 is the state of control bit 704.1
The outputs revert to the state they were in
before the power cut.
NOTE: For more information, refer to the "TeSys U Communication Variables" User’s Manual.
1743234 03/200945
Starting up the Module via the Registers
Customizing Your Configuration
You can use the factory settings (see Factory Configuration) or customize your configuration.
The following parameters can be set:
Control unit configuration
Control unit ID
Timeout duration
Fallback mode
Control mode with a LUTM controller.
Inversion of the output states
Assignment of outputs LO1, OA1, OA3, 13 and 23
Recovery after stopping
Control unit forcing
UNEXPECTED OPERATION
A configuration can be loaded or edited via both Modbus ports (via the communication module or via
the control unit LUCM). One configuration can then overwrite another, as the system does not prevent
such an action. The result is not certain.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
WARNING
Control unit configuration (Reg 602)
Register 602 (accessible in read/write mode) is used to configure the control unit (reset mode 602.0-2,
and communication 602.4).
Reg•Value Comment
602.01Resetting is manual (by default). Bits 1 and 2 are at 0.
0You have activated either bit 1 (remote reset) or bit 2
602.41Communication with the LUCM/MT multifunction control
0When forced to 0, this bit inhibits communication
Control unit configuration (Reg 680)
The control unit is identified each time the communication module is powered up.
However, the multifunction control unit memorizes the reference of the communication module
assembled with it.
To use a multifunction control unit on its own, once it has been used with a communication module,
identification register 680 is reinitialized locally via the keypad in the menu (Id = 0) or via the remote LUCM
Modbus terminal port (value 0 written to register 680).
Timeout Duration (Reg 681)
Register 681 (accessible in read/write mode) is used to set or read the value of the timeout on loss of
communication with the PLC. Following loss of communication, the timeout corresponds to the time
before switching to fallback mode. Loss of communication results in a warning, which is signaled by
register 460 = 109.
(automatic reset)
unit has been activated.
between the LUCM/MT multifunction control unit and the
LULC032-033 Modbus communication module.
46
Reg• ValueRangeUnit
681-0 - 6553510 ms6000Value of timeout
Factor
y value
Comment
The value 0 represents a time of zero.
1743234 03/2009
Fallback mode (Reg 682)
Register 682 (accessible in read/write mode) is used to configure the fallback mode in the event of loss
of communication with the PLC.
Register 682 ValueFallback Mode
0Ignored
1Freeze outputs
2Stop
3Signal comm loss warning
4Force run forward
5Force run reverse
AUTOMATIC RESTART OF THE MOTOR
When communication stops,outputs OA1-OA3 take the status corresponding to the selected fallback
mode (register 682), but command bits 704.0 and 704.1 are not modified.
During the loss of communication warning (register 703 or push button on the controller), the motor will
restart automatically if command bits 704.0 or 704.1 have not been reset to zero first by the PLC
application.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Starting up the Module via the Registers
WARNING
1743234 03/200947
Starting up the Module via the Registers
Description of the different fallback modes:
Fallback ModeLoss of CommunicationCommunication RecoverLoss of Communication
Ignored
(reg 682 = 0)
Freeze outputs
(reg 682 = 1)
Stop
(reg 682 = 2)
Signal comm loss
warning
(reg 682 = 3)
Force run forward
(reg 682 = 4)
Force run reverse
(reg 682 = 5)
Acknowledgement
No detection of the loss of
communication
OA1 and OA3 keep their
status
OA1 and OA3 keep their
status
ERR LED blinking on the front
face
OA1 and OA3 are forced to 0OA1 and OA3 are forced to 0 On rising edge by bit 703.3
ERR LED blinking on the front
face
OA1 and OA3 keep their
status
ERR LED blinking on the front
face
OA1 is forced to 1
OA3 is forced to 0
ERR LED blinking on the front
face
OA1 is forced to 0
OA3 is forced to 1
ERR LED blinking on the front
face
No detection of the loss of
communication
OA1 and OA3 keep their
status
OA1 and OA3 keep their
status
ERR LED blinking on the
front face
Every new On/Off command
is stored but with no impact
on OA1 and OA3
ERR LED blinking on the
front face
Every new On/Off command
is stored but with no impact
on OA1 and OA3
OA1 and OA3 keep their
status
ERR LED blinking on the
front face
Every new On/Off command
is considered and has an
impact on OA1 and OA3
OA1 is forced to 1
OA3 is forced to 0
ERR LED blinking on the
front face
Every new On/Off command
is stored but with no impact
on OA1 and OA3
OA1 is forced to 0
OA3 is forced to 1
ERR LED blinking on the
front face
Every new On/Off command
is stored but with no impact
on OA1 and OA3
No acknowledgement of the
loss of communication
On rising edge by bit 703.3
(do not leave set to 1)
Once the acknowledgement
is done, the last command
stored in register 704 is
enabled
ERR LED switches off
(do not leave set to 1)
Once the acknowledgement
is done, the last command
stored in register 704 is
enabled
ERR LED switches off
On rising edge by bit 703.3
(do not leave set to 1)
ERR LED switches off
On rising edge by bit 703.3
(do not leave set to 1)
Once the acknowledgement
is done, the last command
stored in register 704 is
enabled
ERR LED switches off
On rising edge by bit 703.3
(do not leave set to 1)
Once the acknowledgement
is done, the last command
stored in register 704 is
enabled
ERR LED switches off
48
NOTE: The red 'ERR' LED flashes to indicate a loss of communication (fault on timeout).
1743234 03/2009
Control Mode (Local/Bus) with an LUTM Controller (Reg 683)
Control of outputs 13 and 23 on the LUTM controller depends on the operating mode selected in register
683.
ValueOperationComment
'Remote via
0
1'Local' mode
2
the bus'
mode
'Mixed' mode
(input I.10
has priority)
Outputs 13 and 23 are only controlled by the bus.
The state of inputs I.1 and I.2 does not affect outputs 13 and 23.
Outputs 13 and 23 are only controlled by inputs I.1 and I.2.
Commands via the bus are not taken into account.
'Local' mode if I.10 = 1
'Remote via the bus'
mode if I.10 = 0
NOTE: Commands transmitted during communication are passed directly to the output relays, without
wiring between the communication module outputs and inputs I.1 and I.2.
Inversion of output states (Reg 684)
Depending on requirements (signaling, run, stop, etc.), it is possible to assign NO or NC behavior to
outputs OA1, OA3 and LO1, by configuring register 684.
To do this, define the output concerned ==> register 684.
Starting up the Module via the Registers
Outputs 13 and 23 are only controlled
by inputs I.1 and I.2.
Commands via the bus are not taken
into account.
Outputs 13 and 23 are only controlled
via the bus, from the PLC.
The state of inputs I.1 and I.2 does not
affect outputs 13 and 23.
The tables below show how the assignments of outputs LO1, OA1, OA3, 13, and 23 can be modified. To
modify the assignments (factory values), write a different value (0 to 45), referring to the 'TeSys U
Communication Variables' User’s Manual.
UNEXPECTED OPERATION
Before modifying an output's assignment by means of parameterization, you must note the following
information. Otherwise, you run the risk of unexpected operation.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Register 704 is used for controlling the motor-starter. The following are associated with this register:
functions for monitoring loss of communication, fallback mode (register 682), reflex functions or recovery
mode after stopping (register 688). Only the outputs activated by bits 704.0 and 704.1 benefit from these
functions.
In addition, command bits 704.0 and 704.1 are independent and can be activated simultaneously.
Using register 700 to activate outputs is comparable with unconditional forcing.
Setting the parameters of output LO1 (Reg 685 LSB)
Assignment/control (factory value) of output LO1 on the LULC032 Modbus communication module is as
follows:
_.0 = 1
_.1 = 1
_.2 = 1
WARNING
Reg• BitValueFactory valueComment
6850 to 70 to 452Output LO1 = state of register 700.0
1743234 03/200949
Starting up the Module via the Registers
Setting the Parameters of Output OA1 (Reg 686 LSB)
Assignment/control (factory value) of output OA1 on the LULC032-033 Modbus communication module
is as follows:
Reg• BitValueFactory valueComment
6860 to 70 to 4512Output OA1 = state of register 704.0
Setting the Parameters of Output OA3 (Reg 686 MSB)
Assignment/control (factory value) of output OA3 on the LULC032-033 Modbus communication module
is as follows:
Reg• BitValueFactory valueComment
6868 to 150 to 4513Output OA3 = state of register 704.1
Setting the Parameters of Output 13 (Reg 687 LSB)
Assignment/control (factory value) of output 13 on the LUTM controller is as follows:
Reg• BitValueFactory valueComment
6870 to 70 to 4512Output 13 = state of register 704.0
Setting the Parameters of Output 23 (Reg 687 MSB)
Assignment/control (factory value) of output 23 on the LUTM controller is as follows:
Reg• BitValueFactory valueComment
6878 to 150 to 4513Output 23 = state of register 704.1
Recovery mode (Reg 688)
If you use register 704 to control outputs OA1-OA3, writing the value 1 to register 688 allows you to lock
the motor and prevent it restarting following the occurrence of certain events:
Loss followed by restoration of 24V DC (outputs OA1-OA3)
Change in position of rotary knob on power base followed by return to Ready position.
When one of these events occurs, command bits 704.0 and 704.1 (outputs OA1-OA3) are forced to 0
automatically. As long as one of these events remains pending, if values are written to register 704, the
module will return exception code 02. Once these conditions have disappeared, control of the motor can
be restored by sending a new run command.
AUTOMATIC RESTART OF THE MOTOR
In the case of cyclic writing to register 704 (e.g., an LUFP• gateway in its predefined configuration), this
monitoring function must be used with caution. The application program must take this state into
account and request that bits 704.0 or 704.1 are written to 0. Otherwise, when this event disappears,
the motor will restart automatically.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
WARNING
50
1743234 03/2009
Forcing control unit (Reg 690)
The control unit is identified automatically, but identification can be forced.
ValueComment
0Default value. The system automatically identifies the type of control unit
1If the value is set to 1, this deactivates automatic identification and forces
2If the value is set to 2, this deactivates automatic identification and forces
NOTE: (Read/Write) registers 681 to 690 can also be accessed via the LUCM keypad.
Starting up the Module via the Registers
connected (standard, advanced, multifunction).
identification of a standard or advanced control unit.
identification of a multifunction control unit.
1743234 03/200951
Starting up the Module via the Registers
Modbus Requests and Programming Examples
Modbus Requests
The recognized Modbus requests are as follows:
Code value
HexadecimalDecimal
0x033Read multiple registersRead mode
0x066Write single register
0x1016Write multiple registers
0x2B43Read register identification
NameComment
Write mode
Read mode for identifying the LULC032-033 Modbus
communication module
The maximum number of registers per request is limited to 100.
NOTE: The "Broadcast" function is supported. To use it, a write operation (code 6 or 16) to address 00
is necessary.
WARNING
UNEXPECTED OPERATION
Use of this device on a Modbus network that uses the broadcast function should be considered with
caution.
This device has a large number of registers that must not be modified during normal operation.
Unintended writing of these registers by the broadcast function may cause unexpected and unwanted
product operation.
For more information, refer to the "Internal Communication Variables" User’s Manual.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Example of a Read Operation
The example below describes a READ_VAR request, within a TSX Micro or Premium platform, in order
to read the motor-starter states at address 4 (slave no. 4) contained in internal word MW0:
1 Address of the module with which you wish to communicate: 3 (module address), 0 (channel), 4 (module address
on the bus)
2 Type of PL7 objects to be read: MW (internal word)
3 Address of the first register to be read: 455
4 Number of consecutive registers to be read: 1
5 Word table containing the value of the objects read: MW0:1
6 Read report: MW100:4
Example of a Write Operation
The example below describes a WRITE_VAR request, within a TSX Micro or Premium platform, in order
to control a motor-starter by sending the content of internal word MW 502:
1 Address of the module with which you wish to communicate: 3 (module address), 0 (channel), 4 (module address
on the bus)
2 Type of PL7 objects to be written: MW (internal word)
3 Address of the first register to be written: 704
4 Number of consecutive registers to be written: 1
5 Word table containing the value of the objects to be sent: MW502:1
6 Write report: MW200:4
52
1743234 03/2009
Use of the Main Registers for Simplified Management
Before implementing a motor-starter, it is useful to know which of the main registers are invoked, and in
what order.
Diagram of Register Usage
The diagram below provides basic implementation information, using the following registers:
configuration, control and monitoring (system state, measurements, faults and warnings,
acknowledgment). Starting with the factory configuration (predefined), you will easily be able to follow or
anticipate how your system behaves.
Starting up the Module via the Registers
1743234 03/200953
Starting up the Module via the Registers
54
1743234 03/2009
Fault and Warning Management
1743234 03/2009
Fault and Warning Management
This chapter shows how to manage the various types of fault and warning that may occur.
What's in this Chapter?
This chapter contains the following topics:
Displaying Faults56
Application Faults57
Warnings - Loss of Communication58
Internal Faults59
4
TopicPage
1743234 03/200955
Fault and Warning Management
Displaying Faults
The presence of a fault is signaled by various indicators:
State of the LEDs on the LULC032-033 Modbus communication module
With a power base:
State of the power base rotary knob (0 or "trip")
State of the output relays
With a controller base:
State of the LEDs on the controller base
State of the output relays
With a standard or advanced control unit:
Internal signals sent to the LULC032-033 Modbus communication module
With a multifunction control unit:
Warning
Message(s) displayed on-screen
Internal dialog with the LULC032-033 Modbus communication module
Presence of an exception code (report from the PLC). See Exception Code, page 43.
NOTE: The warning and the fault are taken into account in the relevant registers. For more information,
refer to the "TeSys U Communication Variables" User’s Manual: fault monitoring registers (450 to 452)
and warning monitoring registers (460 to 461).
56
1743234 03/2009
Application Faults
Acknowledgement of Application Faults
The possible application faults are listed below. Their reset (or acknowledgment) method can be:
manual/automatic/remote.
Fault and Warning Management
Application faults
Short-circuit fault1_.0 = 1
Overcurrent fault2_.1 = 1I>>-
Thermal overload fault4_.3 = 1Overload-
Application fault in the
LUCM• multifunction
control unit
Overload Fault with LU•B•/LU•S• Power Base
Following a thermal overload fault, either the rotary knob or the blue pushbutton on the front panel can
be used, irrespective of which reset mode has been configured.
Configuration
register
602.0 = 1
602.1 = 1"Remote"
602.2 = 1"Automatic"Managed by the control unit
Reset
(acknowledgment)
"Direct "manual"
"Remote "manual"
Registers
451
Fault number
3 and 5 to 12
LULC032
LULC033
452
Fault bit
"ERR"(line 2)"FAULT"
Off
Refer to the User’s Manual
for the LUCM••BL or LUCMT1BL multifunction control unit
Method
With the rotary knob on LU•B•
With the blue pushbutton on LU•S•
With the LU9 AP•• kit on LU•B•
With the LU9 •• kit on LU•S•
Acknowledgment by bit 704.3
This bit is active on rising edge and must be reset
to 0 by programming.
LUCM•LUTM
DC-
Fault
acknowledgment
Manual reset
According to the
reset mode
configured in
register 602
Overload Fault with LUTM Controller Base
Following a thermal overload fault, either the blue pushbutton on the front panel or input I.5 can be used,
irrespective of which reset mode has been configured.
Configuration
register
602.0 = 1
602.1 = 1"Remote"
602.2 = 1"Automatic"Managed by the control unit
Reset
(acknowledgment)
"Local "manual"With the blue pushbutton on the front panel
"Remote "manual"
Method
With the reset button on the front of the rack or
control panel (via Input I.5)
Acknowledgment by bit 704.3
This bit is active on rising edge and must be reset
to 0 by programming.
NOTE: The reset mode must be configured.
1743234 03/200957
Fault and Warning Management
Warnings - Loss of Communication
Warning Acknowledgment
List of possible warnings.
Warnings
Thermal overload
warning
Loss of
communication with
the master warning
LUCM• multifunction
control unit warning
Warnings
Registers
460
Warning number
4_.3 = 1-
109_.15 = 1Comm Loss -
2 and 4 to 13
Registers
460
Warning number
461
Warning bit
Refer to the User’s Manual
for the LUCM••BL or LUCMT1BL multifunction control unit.
461
Warning bit
LULC032
LULC033
"ERR"(Line 1)"FAULT"
LULC032
LULC033
LUCM•LUTM
Overload
warning
LUCM•LUTM
Acknowledgment
of a warning
Automatic when the
-
overload is less
than 85%
Acknowledgement
by bit 703.3
This bit is active on
rising edge and
must be reset to 0
by programming.
Acknowledgment
of a warning
LUTM external
warning indicated by
I.6 changing to 0
Recovery After Loss of Communication
After acknowledgment by setting bit 703.3 to 1, recovery occurs according to the states of control bits
704.0 and 704.1.
"ERR"(Line 2)"FAULT"
201_.15 = 1-Warn-M201
Automatic with I.6
returning to 1
58
1743234 03/2009
Internal Faults
Acknowledgment of Internal Faults
List of possible internal faults.
Fault and Warning Management
Registers
451
Internal faults
Fault on the LULC032-033
Modbus communication
module
LULC032-033 Modbus
communication module not
installed or not supplied with
power, or loss of
communication with the
module
Internal fault in the LUC••
control unit
Fault in the LUCM•
multifunction control unit
Write-to-EEPROM fault100_.13 = 1OnM100-
Communication fault with
the LUCM• multifunction
control unit
Checksum fault in EEPROM 102_.13 = 1OnM102
EEPROM configuration fault 104_.13 = 1OnM104
Communication fault with
the LUTM controller base
Communication fault with
the LULC032-033 module
Fault number
14-
15-M15-
54_.11 = 1M54-
51 to 53, 55 to 63Refer to the User’s Manual
101_.12 = 1OnM101
105_.13 = 1OnM105
205
452
Fault bit
for the LUCM••BL or LUCMT1BL multifunction control unit.
LULC032
LULC033
"ERR"(Line 2)"FAULT"
Off
LUCM•LUTM
M14-
Fault
acknowledgment
Power down and
then power up the
LULC032-033 and
the LUCM•
Power down and
then power up the
LULC032-033
Power down and
then power up the
LULC032-033
Rising edge on
704.3=1
Rising edge on
704.3=1
Power down and
then power up the
LULC032-033
Power down and
then power up the
LUTM
_.13 = 1On-
No control unit206
1743234 03/200959
Power down and
then power up the
LUTM
Fault and Warning Management
60
1743234 03/2009
Config
uration of Predefined Functions
1743234 03/2009
Configuration of Predefined Functions
This chapter describes the predefined functions.
What's in this Chapter?
This chapter contains the following topics:
Description of Reflex Stop Functions62
Use of Reflex1 and Reflex264
5
TopicPage
1743234 03/200961
Configuration of Predefined Functions
Description of Reflex Stop Functions
The reflex stop ensures accurate repeated position control, unhindered by the bus and PLC scan times.
There are two types of reflex stop function:
Reflex1: "Reflex stop 1" function
Reflex2: "Reflex stop 2" function
Description of Reflex1
Sensor no. 1 (logic input LI1) directly controls motor stopping.
After a new run command (stop command then run command), the motor restarts even if something is
still detected (LI1=1).
1 Bus2 Sensor no. 1 (LI1)
NOTE: In the case of a reversing starter, the reflex stop works in both directions.
Data sequence
62
1743234 03/2009
Description of Reflex2
Sensor no. 1 (logic input LI1) controls motor stopping in forward mode.
Sensor no. 2 (logic input LI2) controls motor stopping in reverse mode.
After a new run command (stop command then run command), the motor restarts even if something is
still detected (LI1 or LI2 = 1).
NOTE: Sensor no. 2 (LI2) does not affect forward mode and sensor no. 1 (LI1) does not affect reverse
mode.
Configuration of Predefined Functions
1 Bus2 Sensor no. 1 (LI1)3 Sensor no. 2 (LI2)
1743234 03/200963
Configuration of Predefined Functions
Use of Reflex1 and Reflex2
To use a "reflex stop" function, it must be selected in the register of the output to be monitored.
Reflex1.Fw
Reflex
function
Reflex1
Reflex2
Direction of motor rotation
Reflex1.Fw = forward8
Reflex1.Rev = reverse9
Reflex2.Fw = forward10
Reflex2.Rev = reverse11
Value
of Reg•
LUB••/S•• LU2B••/2S•• base
Output
LO1
Reg685
(LSB)
Outputs
OA1
OA3
Reg686
(LSB)
(MSB)
LUTM••
base
Outputs
13
23
Reg687
(LSB)
(MSB)
NOTE: Before using the "reflex stop" functions, outputs OA1/OA3 must first be assigned to the
forward/reverse directions. This selection is made in register 686. By default, OA1 is assigned to forward
and OA3 to reverse.
This function is active on a rising edge and not on the level.
LI1 = 1 stops the motor, irrespective of the chosen direction of operation.
.Fw
After a new run command (stop command followed by a run command),
even if logic input LI1 = 1,
the motor restarts in the chosen direction.
NOTE: Logic input LI2 is not used.
Reflex1.Rev
Reflex2.Fw
Reflex2.Rev
This function is active on a rising edge and not on the level.
LI1 = 1 stops the motor, irrespective of the chosen direction of operation.
.Rev
After a new run command (stop command followed by a run command),
even if logic input LI1 = 1,
the motor restarts in the chosen direction.
NOTE: Logic input LI2 is not used.
This function is active on a rising edge and not on the level.
Logic input LI1 = 1 stops the motor in forward mode.
Logic input LI2 = 1 stops the motor in reverse mode.
.Fw
After a new run command (stop command followed by a run command),
even if logic input LI2 = 1,
the motor restarts.
NOTE: Logic input LI2 does not affect forward mode and logic input LI1 does not affect reverse mode.
This function is active on a rising edge and not on the level.
Logic input LI2 = 1 stops the motor in reverse mode.
.Rev
Logic input LI1 = 1 stops the motor in forward mode.
After a new run command (stop command followed by a run command),
even if logic input LI2 = 1,
the motor restarts.
64
NOTE: Logic input LI2 does not affect forward mode and logic input LI1 does not affect reverse mode.