While every precaution has been taken in the preparation of this document, Schneider
Electric SA assumes no liability for any omissions or errors it may contain, nor for any
damages resulting from the application or use of the information herein.
The products and options d escribed i n this document may be changed or modi fied at
any time, either from a technical point of view or in the way they are operated. Thei r
description can in no way be considered contractual.
2
1. Before you begin
Read and understand these instructions before performing any procedure with thi s drive.
DANGER
HAZARDOUS VOLTAGE
• Read and understand the Installation Ma nual before inst alling or op erating the Al tivar 71 drive. Installati on, adjustme nt,
repair, and maintenance must be performed by qualified personnel.
• The user is responsible for compliance with all international and national electrical standards in force concerning
protective grounding of all equipment.
• Many parts of this variable speed drive, including the printed circuit board s, operate at the line voltage. DO NOT TOUCH.
Use only electrically insulated tools.
• DO NOT touch unshielded components or terminal strip screw connections with voltage prese nt.
• DO NOT short across terminals PA/+ and PC/- or across the DC bus capacitors.
• Install and close all covers before applying power or starting and stopping the drive.
• Before servicing the variable speed drive
- Disconnect all power.
- Place a “DO NOT TURN ON” label on the variable speed drive disconnect.
- Lock the disconnect in the open position.
• Disconnect all power including external control power that may be present before servicing the drive. WAIT 15
MINUTES to allow the DC bus capacitors to discharge. Then follow the DC bus voltage measurement procedure given
in the installation manual to verify that the DC volta ge is less than 45 VDC. The drive LEDs are not accura te indi cators
of the absence of DC bus voltage.
Electric shock will result in death or serious injury.
CAUTION
EQUIPMENT DAMAGE
Do not operate or install any drive that appears damaged.
Failure to follow these instructions can result in equipment damage.
3
2. Documentation structure
The following Altivar 71 technical documents are availa ble on the Telemecanique website (www.telemecanique.com) as we ll as on the CDROM supplied with the drive.
b Installation Manual
This manual describes:
• How to assemble the drive
• How to connect the drive
b Programming Manual
This manual describes:
• The functions
• The parameters
• How to use the drive display terminal (integrated display terminal and graphic display terminal)
b Communication Parameters Manual
This manual describes:
• The drive parameters with specific information (addresses, formats, etc.) for use via a bus or communication network
• The operating modes specific to communication (state chart)
• The interaction between communication and local control
b Modbus, CANopen, Ethernet, Profibus, INTERBUS, Uni-Telway, DeviceNet, Modbus Plus and
FIPIO manuals
These manuals describe:
• Connection to the bus or network
• Configuration of the communication-specific parameters via the integrated display terminal or the graphic display terminal
• Diagnostics
• Software setup
• The communication services specific to the protocol
b Altivar 58/58F Migration Manual
This manual describes the differences between the Altivar 71 and the Altivar 58/58F.
It explains how to replace an Altivar 58 or 58F, including how to replace drives communicating on a bus or network.
4
3. Introduction
3. 1. Presentation
The communication card (catalog number VW3 A8 303) is used to connect an Altivar 71 drive to a Uni-Telway or Modbus bus.
This manual only describes how to use the Modbus protocol. For Uni-Telway, please refer to the Uni-Telway protocol manual.
The data exchanges permit access to all Altivar 71 functions:
• Configuration
• Adjustment
• Control and command
• Monitoring
• Diagnostics
The card has a female 9-way SUB-D connector for connection to the Modbus bus.
The connection cables and accessories should be ordered separately.
The drive address should be configured using the switches on the card.
The graphic display terminal or the integrated display terminal offer numerous functions for communication diagnosti cs.
Note: The Modbus card supports the following services in addition to those provided by the drive’s integrated ports:
- 2-wire and 4-wire RS485
- Choice of line polarization
- RTU and ASCII modes
- More diagnostic subcodes
- More Modbus functions (04: Read Input Registers and 11: Get Comm Event Counter)
3. 2. Notation
Drive terminal displays
The graphic display terminal menus are shown in square brackets.
Example: [1.9 COMMUNICATION]
The integrated 7-segment display terminal menus are shown in round brackets.
Example: (COM-)
Parameter names displayed on the graphic display terminal are shown in square brackets.
Example: [Fallback speed]
Parameter codes displayed on the integrated 7-segment display terminal are shown in round brackets.
Example: (LFF)
Formats
Hexadecimal values are written as follows: 16#
Binary values are written as follows: 2#
Abbreviations
Hi: High order
Lo: Low order
5
4. Hardware setup
4. 1. Receipt
Check that the card catalog number marked on the label is the same as that on the delivery note corresponding to the purchase order.
Remove the option card from its packaging and check that it has not been damaged in transit.
4. 2. Hardware description
LEDs
Female 9-way SUB-D connector
Polarization switches
4. 3. Installing the card in the drive
See the Installation Manual.
Address switches
6
4. Hardware setup
4. 4. Switch coding
b Choosing polarization
Normal setting for a Modbus bus:
• No polarization at drive level
Special setting (see "Creating a Modbus bus using non-standard equipment" on page 44
Ω RS485 line polarization at drive level
• 4.7 k
b Coding the address
The address switches are used to encode the address (1 to 247) of the drive on the bus.
The switch settings can only be changed when the drive is turned off.
The correspondence between the value and the position of the switch is as follows:
• 0 = OFF = Switch in upper position
• 1 = ON = Switch in lower position
The address is binary-coded.
Examples:
Address 11 = 2#0000 1011
Address 34 = 2#0010 0010
):
7
4. Hardware setup
The table below indicates the positions of the 8 switches for all configurable addresses:
• Use Telemecanique-approved cables and wiring accessories to ensure good transmission quality (matched impedance, immunity,
shielding connection, etc.).
• Keep the Modbus cable away from the power cables (30 cm minimum).
• Be sure to cross the Modbus cable and the power cables at right angles.
• Whenever possible, connect the bus cable shiel ding to the protective ground, e.g., to th e ground of each device if this ground is connected
to the protective ground.
• Install a line terminator at both ends of the line.
• Ensure the correct line polarization.
• Connect the common polarity ("Common" signal) to the protective ground at one or more points on the bus.
For more information, please refer to the TSX DG KBL E guide: "Electromagnetic compatibility of industrial networks and fieldbuses".
5. 2. Modbus RS485 standard
The characteristics and accessories mentioned in this section ("5. Connecting to the bus") comply with the Modbus standard.
Other non-Modbus-standard RS485 wiring diagrams are possible. Please see the Appendix for further information.
The latest generation of Telemecanique equipment conforms to Modbus (2-wire RS485).
Main characteristics:
Maximum length of bus1000 m at 19,200 bps
Maximum number of stations32 stations, i.e., 31 slaves (without repeater)
9
5. Connecting to the bus
5. 3. Connection via RJ45 wiring system
1. Master (PLC, PC or communication module)
2. Cable depending on the type of master (see table)
100Supplied without connector6TSXCSA 100
200Supplied without connector6TSXCSA 200
500Supplied without connector6TSXCSA 500
4VW3 A58 306 R10
4VW3 A58 306 R30
10
5. Connecting to the bus
b Connection cables for the master
Type of masterMaster interfaceDescriptionCatalog number
Twido PLCAdaptor or mini-DIN
RS485 interface module
Adaptor or screw
terminal RS485
interface module
TSX Micro PLCMini-DIN RS485
connector port
PCMCIA card
(TSX SCP114)
TSX Premium PLCTSX SCY 11601 or
TSX SCY 21601
module
(25-way SUB-D socket)
PCMCIA card
(TSX SCP114)
Ethernet bridge
(174 CEV 300 20)
Profibus DP gateway
(LA9P307)
Fipio (LUFP1) or
Profibus DP (LUFP7) or
DeviceNet (LUFP9)
gateway
Serial port PCMale 9-way SUB-D
Screw terminal RS4853 m cable equipped with an RJ45 connector and stripped at
RJ45 RS4851 m cable equipped with 2 RJ45 connectorsVW3 P07 306 R10
RJ45 RS4850.3 m cable equipped with 2 RJ45 connectors or
RS232 serial port PC
3 m cable equipped with a mini-DIN connect or and an RJ45
connector
3 m cable equipped with an RJ45 connector and stripped at
the other end
3 m cable equipped with a mini-DIN connect or and an RJ45
connector
Stripped cableTSX SCP CM 4030
Cable equipped with a 25-way SUB-D connector and
stripped at the other end (for connection to the screw
terminals of the LU9GC3 splitter block)
Stripped cableTSX SCP CM 4030
the other end
1 m cable equipped with 2 RJ45 connectors or
3 m cable equipped with 2 RJ45 connectors
RS232/RS485 converter and 3 m cable equipped with an
RJ45 connector and stripped at the other end (for
connection to the screw terminals of the LU9GC3 splitter
block)
TWD XCA RJ030
VW3 A8 306 D30
TWD XCA RJ030
TSX SCY CM 6030
VW3 A8 306 D30
VW3 A8 306 R03 or
VW3 A8 306 R10 or
VW3 A8 306 R30
TSX SCA 72 and
VW3 A8 306 D30
11
5. Connecting to the bus
5. 4. Connection via junction boxes
1. Master (PLC, PC or communication module)
2. Modbus cable depending on the type of master (see table)
1
32
44
3. Modbus cable TSX CSAp00
4. Subscriber sockets TSX SCA 62
5. Modbus drop cable VW3A83062
A TV 71
6
6
b Connection accessories
DescriptionRef.Catalog
number
Subscriber socket
2 female 15-way SUB-D connectors, 2 screw terminals, and an RC line terminator,
to be connected using cable VW3 A8 306 or VW3 A8 306 D30
4TSX SCA 62
b Connection cables
DescriptionLength (m)ConnectorsRef.Catalog
number
Cables for Modbus bus31 9-way SUB-D connector and
1 male 15-way SUB-D connector
for TSX SCA 62
RS485 double shielded twisted pair
cables
100Supplied without connector3TSX CSA 100
200Supplied without connector3TSX CSA 200
500Supplied without connector3TSX CSA 500
6VW3 A8 306 2
12
5. Connecting to the bus
b Connection cables for the master
Type of masterMaster interfaceDescriptionCatal og number
Twido PLCAdaptor or screw terminal
RS485 interface module
TSX Micro PLCMini-DIN RS485
connector port
PCMCIA card (TSX SCP114)Cable equipped with a special connector and
TSX Premium PLCTSX SCY 11601 or
TSX SCY 21601 module
(25-way SUB-D socket)
PCMCIA card (TSX SCP114)Cable equipped with a special connector and
Ethernet bridge
(174 CEV 300 10)
Profibus DP gateway
(LA9P307)
Fipio (LUFP1) or
Profibus DP (LUFP7) or
DeviceNet (LUFP9) gateway
Serial port PCMale 9-way SUB-D RS232
Screw terminal RS485Modbus cableTSX CSA100 or
RJ45 RS4853 m cable equipped with an RJ45 connector
RJ45 RS4853 m cable equipped with an RJ45 connector
serial port PC
Modbus cableTSX CSA100 or
TSX CSA200 or
TSX CSA500
Tap junctionTSX P ACC 01
TSX SCP CM 4030
stripped at the other end
Cable equipped with a 25-way SUB-D
connector and stripped at the other end
stripped at the other end
and stripped at the other end
and stripped at the other end
RS232/RS485 converter and
Modbus cable
TSX SCY CM 6030
TSX SCP CM 4030
TSX CSA200 or
TSX CSA500
VW3 A8 306 D30
VW3 A8 306 D30
TSX SCA 72 and
TSX CSA100 or
TSX CSA200 or
TSX CSA500
13
6. Configuration
6. 1. Communication parameters
Configure the following parameters in the [1.9 - COMMUNICATION](COM-) menu, [Uni-Telway/Modbus](UtL-) submenu:
[Protocol](PrO), [Bit rate](bdr) and [Format](FOr).
These parameters can only be modified when the motor is stopped. Modifications can only be taken into account by the drive following a
power break.
Parameter Possible valuesTerminal displayDefault value
[Protocol]
(PrO)
[Address]
(AdrC)
[Bit rate]
(Bdr)
[Format]
(FOr)
Uni-Telway
Modbus/RTU
Modbus/ASCII
0 to 247[0](0) to [247](247)Value taken from the address switches
4800 bps
9600 bps
19,200 bps
In RTU mode only:
8 data bits, odd parity, 1 stop bit
8 data bits, even parity, 1 stop bit
8 data bits, no parity, 1 stop bit
8 data bits, no parity, 2 stop bits
In RTU and ASCII modes:
7 data bits, odd parity, 1 stop bit
7 data bits, even parity, 1 stop bit
7 data bits, odd parity, 2 stop bits
7 data bits, even parity, 2 stop bits
Numerous configurations are possible. For more information, refer to the Programming Manual and th e Parameters Manual.
The following configurations are just some of the possibili ties available.
b Control via Modbus in I/O profile
The command and reference come from Modbus.
The command is in I/O profile.
Configure the following parameters:
ParameterValueComment
ProfileI/O profileThe run command is simply obtained by bit 0 of the control word.
Reference 1 configurationNetwork card The reference comes from Modbus.
Command 1 configurationNetwork card The command comes from Modbus.
Configuration via the graphic display terminal or the integrated display terminal:
b Control via Modbus or the terminals in I/O profile
Both the command and reference come from Modbus or the terminals. Input LI5 at the terminals is used to switch between Modbus and the
terminals.
The command is in I/O profile.
Configure the following parameters:
ParameterValueComment
ProfileI/O profileThe run command is simply obtained by bit 0 of the control word.
Reference 1 configurationNetwork cardReference 1 comes from Modbus.
Reference 1B configurationAnalog input 1 on the termi nals Reference 1B comes from input AI1 on the terminals.
Reference switchingInput LI5Input LI5 switches the reference (1
Command 1 configurationNetwork cardCommand 1 comes from Modbus.
Command 2 configurationTerminalsCommand 2 comes from the terminals.
Command switchingInput LI5Input LI5 switches the command.
Note: Reference 1B is directly connected to the drive reference limit. If switching is performed, the functions that affect the reference
(summing, PID, etc) are inhibited.
Configuration via the graphic display terminal or the integrated display terminal:
b Control via Modbus or the terminals in Drivecom profile
Both the command and reference come from Modbus or the terminals. Input LI5 at the terminals is used to switch between Modbus and the
terminals.
The command is in Drivecom profile.
The run commands are in Drivecom profile, the command and the reference
come from the same channel.
Configure the following parameters:
ParameterValueComment
ProfileDrivecom profile not separateThe run commands follow the Drivecom profile, and the command and
Reference 1 configurationNetwork cardReference 1 comes from Modbus.
Reference 2 configurationAnalog input 1 on the terminalsReference 2 comes from input AI1 on the terminals.
Reference switchingInput LI5Input LI5 switches the reference (1
Caution: Reference 2 is directly connected to the drive reference limit. If switching is performed, the functions that affect the reference
(summing, PID, etc) are inhibited.
Configuration via the graphic display terminal or the integrated display terminal:
b Control in Drivecom profile via Modbus and reference switching at the terminals
The command comes from Modbus.
The command comes either from Modbus or from the terminals. Input LI5 at the t erminals is used to switch the referenc e between Modbus
and the terminals.
The command is in Drivecom profile.
Configure the following parameters:
ParameterValueComment
ProfileSeparate Drivecom profileThe run commands follow the Drivecom profile, and the command and
Reference 1 configurationNetwork cardReference 1 comes from Modbus.
Reference 1B configuration Analog input 1 on the terminalsReference 1B comes from input AI1 on the terminals.
Reference switchingInput LI5Input LI5 switches the reference (1
Command 1 configurationNetwork cardCommand 1 comes from Modbus.
Command switchingChannel 1Channel 1 is the command channel.
Note: Reference 1B is directly connected to the drive reference limit. If switching is performed, the functions that affect the reference
(summing, PID, etc) are inhibited.
Configuration via the graphic display terminal or the integrated display terminal:
The communication scanner enables all the applicatio n-relevant parameters to be grouped in 2 co nsecutive word tables so that singl e read
and write operations may be performed. It is even possible to perform a si ngle transact ion usi ng the "Rea d/Write Multi ple Re gist ers" (23 =
16#17) function.
The 8 output variables are assigned using the 8 [Scan.Outp address](nCAp) parameters. They are configured using the graphic display
terminal via the [1.9 - COMMUNICATION](COM-) menu, [COM. SCANNER OUTPUT](OCS-) submenu.
The 8 input variables are assigned using the 8 [Scan. INp address](nMAp) parameters. They are configured using the graphic display
terminal via the [1.9 - COMMUNICATION](COM-) menu, [COM. SCANNER INPUT](ICS-) submenu.
Enter the logic address of the parameter (see the Parameters Manual).
If a [Scan.Outp address](nCAp) or [Scan. INp address](nMAp) parameter equals zero, the corresponding variable is not used by the
drive.
These 16 assignment parameters are described in the tables below:
Configuration parameter nameDefault assignment of the output variable
[Scan. Out1 address](nCA1)Control word (CMd)
[Scan. Out2 address](nCA2)Speed reference (LFrd)
[Scan. Out3 address] (nCA3)Not used
[Scan. Out4 address] (nCA4)Not used
[Scan. Out5 address](nCA5)Not used
[Scan. Out6 address](nCA6)Not used
[Scan. Out7 address](nCA7)Not used
[Scan. Out8 address](nCA8)Not used
Configuration parameter nameDefault assignment of the input variable
[Scan. IN1 address](nMA1)Status word (EtA)
[Scan. IN2 address](nMA2)Output speed (rFrd)
[Scan. IN3 address](nMA3)Not used
[Scan. IN4 address](nMA4)Not used
[Scan. IN5 address](nMA5)Not used
[Scan. IN6 address](nMA6)Not used
[Scan. IN7 address](nMA7)Not used
[Scan. IN8 address](nMA8)Not used
Example of configuration via the graphic display terminal:
Any modification to parameters [Scan.Outp address] (nCAp) or [Scan. INp address] (nMAp) must be made with the motor stopped. The
master PLC program should be updated to take account of this modification.
18
6. Configuration
6. 4. Communication faults
A Modbus fault is triggered if the Modbus card does not receive any Modbus requests at its address within a predefined time period (time
out). All Modbus request types are taken into account (read, write, etc.). The time out is fixed at 10 s (non-modifiable).
The response of the drive in the event of a Modbus communication fault can be configured.
RDYNET+0.00Hz0A
COM. FAULT MANAGEMENT
Configuration can be performed using the graphic display terminal or
integrated display terminal using the [Network fault mgt](CLL)
parameter in the [1.8 FAULT MANAGEMENT](FLt-) menu, [COM.
FAULT MANAGEMENT](CLL-) submenu.
The values of the [Network fault mgt](CLL) parameter, which trigger a [Com. network] (CnF) drive fault, are:
The values of the [Network fault mgt](CLL) parameter, which do not trigger a drive fault, are:
ValueMeaning
[Ignore](nO)Fault ignored
[Per STT](Stt)Stop according to configuration of [Type of stop]
[fallback spd](LFF)Switch to f allback speed, maintain ed as long as the faul t is present and the run command is not disabled.
[Spd maint.]
The fallback speed can be configured via the [Fallback speed]
(rLS)
The drive maintains the speed at the time the fault occurred, as long as the fault persists and the run
command has not been removed.
(LFF) parameter in the [1.8 – FAULT MANAGEMENT](FLt-) menu.
(Stt).
19
6. Configuration
6. 5. Monitored parameters
It is possible to select up to 4 parameters to display their values in the [1.2 - MONITORING] menu ([COMMUNICATION MAP] submenu)
on the graphic display terminal.
The selection is made via the [6 – MONITOR CONFIG.] menu ([6.3 - CONFIG. COMM. MAP] submenu).
Each parameter [Address 1 select] ... [Address 4 selec t] can be used to
choose the logic address of the parameter. Select an address of zero
to disable the function.
In the example given here, the monitored words are:
• Parameter 1 = Motor current (LCr): logic address 3204;
signed decimal format
• Parameter 2 = Motor torque (Otr): logic address 3205; signed
decimal format
• Parameter 3 = Last fault occurred (LFt): logic address 7121;
hexadecimal format
• Disabled parameter: address 0; default format: hexadecimal format
RDYNET+0.00Hz0A
6.3 CONFIG. COMM. MAP.
Address 1 select: 3204
FORMAT 1: Signed
Address 2 select: 3205
FORMAT 2: Signed
Address 3 select: 7121
CodeQuick
FORMAT 3: Hex
Address 4 select: 0
FORMAT 4: Hex
One of the three display formats below can be assigned to each monitored word:
On the graphic display terminal or integrated dis play te rmi na l, chec k th e add ress t hat has been code d on the switches usi ng t he [Address]
(AdrC) parameter in the [1.9 COMMUNICATION](COM-) menu, [Uni-Telway / Modbus] (UtL-) submenu.
This parameter cannot be modified.
7. 2. LEDs
The Modbus card has 2 LEDs, RUN and ERR, which are visible through the drive cover.
1.1
1.2
1.3
1.4
1.5
RUN (green)
2.3
2.4
2.5
ERR (red)
Green RUN
LED
OffOff
OnOnDrive starting
OnOffNormal operation
OffOn
OffFlashingError on character received
FlashingOff
Red ERR
LED
MeaningCorrective action
Drive not operating
or turned off
Communication fault
on the bus
Card fault
[internal com. link](ILF)
Check the power supply.
• Check the environment (electromagnetic compatibility).
• Check the wiring.
• Check that the master is communicating within the time out period
(= 10 s).
• Check the environment (electromagnetic compatibility).
• Check the communication parameter configuration (protocol, speed,
format).
• Do not forget that the communication parameter configuration is only
taken into account by the drive following a power break.
• Check that the slave address is unique.
• Check the environment (electromagnetic compatibility).
• Check the card/drive connection.
• Check that only one communication card has been installed.
• Check that no more than two option cards have been installed.
• Replace the communication card.
• Inspect or repair the drive.
21
7. Diagnostics
7. 3. Control - Command
On the graphic display terminal only, the [1.2 - MONITORING] menu ([COMMUNICATION MAP] submenu) can be used to display cont rolsignal diagnostic information between the drive and the master:
Active command channel
Value of control word used
Value of frequency reference
(unit 0.1 Hz) used to control the drive
Values of the four monitored words selected by the user.
The address and display format of these parameters
[6 - MONITORING CONFIG.] menu,
[6.3 - COM. MAP CONFIG.]
submenu (see "Configuration" section on page 20
The value of a monitored word is equal to "-----" if:
- Monitoring is not activated
(address equal to 0)
- The parameter is protected
- The parameter is not known (e.g., 3200)
Communication
scanner
Control word from Modbus
[COM. card cmd.](CMd3)
Frequency reference from Modbus
to control the drive
(hexadecimal format)
Active reference channel
Value of status word
(hexadecimal format)
can be configured in the
Value of input variables
Value of output variables
[Com. card ref.](LFr3)
RUN NET+50.00Hz80A
COMMUNICATION MAP
Command Channel: Com. card
Cmd value: 000F
Active ref. channel: Com. card
Frequency ref.: 500.0
Status word: 8627
Modbus communication faults are indicated by the red ERR LED on the Modbus card .
In the factory configuration, a communication fault will trigger a resettable [Com. network](CnF) drive fault and initiate a freewheel stop.
It is possible to change the response of the drive in the event of a Modbus communication fault (see the Configuration section).
- [Com. network](CnF) drive fault (freewheel stop, stop on ramp, fast stop or DC injection braking stop)
- No drive fault (stop, maintain, fallback)
The Parameters Manual contains a detailed description of how to manage communication faults (see the "Communication monitoring"
section).
• Following initialization (power-up), the drive checks that at least one command or referenc e parameter has been wri tten for the first time
by Modbus.
• Then, if a communication fault occurs on Modbus, the drive will react according to the configuration (fault, maintain, fallback, etc.).
7. 6. Card fault
The [internal com. link](ILF) fault appears when the following serious problems occur:
- Hardware fault on the Modbus card
- Dialog fault between the Modbus card and the drive
The response of the drive in the event of an [internal com. link](ILF) fault cannot be configured, and the drive trips with a freewhee l stop.
This fault cannot be reset.
Two diagnostic parameters can be used to obtain more detailed information about the origin of the [internal com. link] (ILF) fault:
- [Internal link fault 1](ILF1) if the fault has occurred on option card no. 1 (installed directly on the drive)
- [Internal link fault 2](ILF2) if the fault has occurred on option card no. 2 (installed on option card no. 1)
The Modbus card can be in position 1 or 2.
The [Internal link fault 1](ILF1) and [Internal link fault 2](ILF2) parameters can only be accessed on the graphic display terminal in
the [1.10 DIAGNOSTICS](DGt-) menu, [MORE FAULT INFO](AFI-) submenu.
ValueDescription of the values of the [Internal link fault 1] (ILF1) and [Internal link fault 2] (ILF2) parameters
0No fault
1Loss of internal communication with the drive
2Hardware fault detected
3Error in the EEPROM checksum
4Faulty EEPROM
5Faulty Flash memory
6Faulty RAM memory
7Faulty NVRAM memory
8Faulty analog input
9Faulty analog output
10Faulty logic input
11Faulty logic output
101Unknown card
102Exchange problem on the drive internal bus
103Time out on the drive internal bus (500 ms)
24
8. Modbus protocol
8. 1. Principle
The Modbus protocol is a master-slave protocol.
Only one device can transmit on the line at any one time.
The master manages the exchanges and only it can take the initiative.
It interrogates each of the slaves in succession.
Master
No slave can send a message unless it is invited to do so.
In the event of an error during data exchange, the master repeats the question and declares the interrogated
slave absent if no response is received within a given time period.
If a slave does not understand a message, it sends an exception response to the master.
The master may or may not repeat the request.
Slave i
Direct slave-to-slave communications are not possible.
For slave-to-slave communication, the master’s application software must therefore be designed to interrogate one slave and send back
data received to the other slave.
Two types of dialog are possible between master and slaves:
• The master sends a request to a slave and waits for it to respond.
• The master sends a request to all slaves without waiting for them to respond (broadcasting principle).
Note: The Modbus server on the "Controller Inside" card cannot be accessed via the Modbus card.
Slave j
Slave k
25
8. Modbus protocol
8. 2. Modes
b RTU mode
The Modbus RTU frame contains no message header byte, nor end of message bytes.
It is defined as follows:
Slave addressFunction codeDataCRC16
The data is transmitted in binary code.
CRC16: Cyclic redundancy check parameter.
The end of the frame is detected on a silence greater than or equal to 3.5 characters.
The format used for the frames in the rest of this document is RTU mode.
b ASCII mode
The structure of the Modbus ASCII frame is as follows:
Header
":"
Header: By default, ":" = 16#3A. Two other characters are possible: "CR" = 16#0D and "LF" = 16#0A.
LRC: The 2's-complement of the modulo 256 sum (in hexadecimal format) of the frame (excluding the header and end characters) before
ASCII coding.
Example: Write a value of 10 to logic address word 9001 (16#2329) on slave 2
Identical request and response:
In hexadecimal format
3A30323036323332393030304141320D0A
In ASCII format
:02062329000AA2CRLF
Slave
address
Function
code
DataLRCEnd
HiLo"CR""LF"
26
8. Modbus protocol
8. 3. Modbus functions available
The following table indicates which Modbus functions are managed by t he Altivar 71 and specifies their limits.
The "read" and "write" functions are defined from the point of view of the master.
Functions 3 and 4 access all the drive registers that make no distinction between the "Holding" or "Input" types.
Read Holding RegistersRead N output words
Read Input RegistersRead N input words
Write Single RegisterWrite one output word
DiagnosticsDiagnostics
Get Comm Event CounterRead counter
Write Multiple RegistersWrite N output words
Read/Write Multiple RegistersRead/write N words
Read Device IdentificationIdentification
NO
NO
YES
NO
NO
YES
NO
NO
63 words, max.
63 words, max.
61 words, max.
20/20 words max.
Request:
Slave no.03/04No. of first wordNumber of wordsCRC16
HiLoHiLoLoHi
1 byte1 byte2 bytes2 bytes2 bytes
Response:
Slave no.03/04Number of
bytes read
1 byte1 byte1 byte2 bytes2 bytes2 bytes
Example: Use function 3 to read 4logic address words 3102 to 3105 (16#0C1E to 16#0C21) on slave 2, where:
First word value-------Last word valueCRC16
HiLoHiLoLoHi
Response:
0203080028025801F4000052B0
Value of:3102310331043105
Parameter code:SFrtFrHSPLSP
27
8. Modbus protocol
8. 5. Write Single Register (6)
Request and response:
Slave no.06Word numberValue of wordCRC16
HiLoHiLoLoHi
1 byte1 byte2 bytes2 bytes2 bytes
Example: Write value 16#000D to logic address word 9001 (16#2329) on slave2 (ACC = 13 s)
Request and response:
02062329000D9270
28
8. Modbus protocol
8. 6. Diagnostics (8)
Request and response:
Slave no.08Sub-codeDataCRC16
HiLoHiLoHiLo
1 byte1 byte2 bytes2 bytes2 bytes
Sub
FunctionRequest
code
00Echo
This function asks the slave to return the request sent by the master. The size
of the data is limited to 2 bytes.
01Reinitialize channel
This function is used to reinitialize slave communication and, in particular, to
make it exit listen only mode (LOM).
03Change ASCII delimiter
In ASCII mode, messages are delimited by the line feed character
(LF = H'0A). This function is used to change this character.
04Change to LOM mode
This function is used to force a slave to listen only mode (LOM). In this mode,
the slave does not handle messages which are add ressed to it, nor does i t send
any responses, except when the channel is reinitialized.
0ACounter reset
This function resets all the counters responsible for monitoring slave
exchanges.
0BRead the number of correct messages on the line without checksum error00 00Value of
0CRead the number of incorrect messages on the line with checksum error00 00Value of
0DRead the number of exception responses sent by the slave00 00Value of
0ERead the number of messages addressed to the slave excluding
broadcast messages regardless of type
0FRead the number of broadcast messages on the line regardless of type00 00Value of
10Read the number of NAK exception responses
The value read is always 0.
11Read the number of slave not ready responses
The value read is always 0.
12Read the number of message s received with character overrun00 00Value of
data
XX YYXX YY
16#00 00
or
16#FF 00
XX 00
XX = new delimiter
00 0000 00
00 0000 00
00 00Value of
00 0000 00
00 0000 00
Response
16#00 00
16#FF 00
counter
counter
counter
counter
counter
counter
data
or
XX 00
The counters are unsigned words.
Example: Values 16#31 and 16#32 echoed by slave 4
Request and response:
Slave no.CodeSubcodeValue of
HiLoLoHi
040800003132741B
st
byte
1
Value of
2nd byte
CRCCRC
29
8. Modbus protocol
8. 7. Get Comm Event Counter (11 = 16#0B)
Question:
Slave no.0BCRC16
1 byte1 byte2 bytes
Response:
Slave no.0B0000Value of counterCRC16
HiLoLoHi
1 byte1 byte2 bytes2 bytes2 bytes
8. 8. Write Multiple Registers (16 = 16#10)
Request:
Slave no.10No. of first wordNumber of wordsNumber of bytesValue of first word-------CRC16
HiLoHiLoHiLoLoHi
1 byte1 byte2 bytes2 bytes1 byte2 bytes2 bytes
Response:
Slave no.10No. of first wordNumber of wordsCRC16
HiLoHiLoLoHi
1 byte1 byte2 bytes2 bytes2 bytes
Example: Write values 20 and 30 t o logic address words 9001 and 9002 on sl ave 2 (acceleration time = 20 s and deceler ation time = 30 s)
Request:
Slave no.Request
code
021023290002040014001E73A4
Response:
Slave no.Response codeNo. of first wordNumber of wordsCRC16
0210232900029BB7
No. of first wordNumber of
words
HiLoHiLoHiLoHiLoLoHi
HiLoHiLoLoHi
Number of
bytes
Value of first wordValue of second
word
CRC16
30
8. Modbus protocol
8. 9. Read/Write Multiple Registers (23 = 16#17)
Request:
Slave no.17No. of 1
st
word to be
read
Number of words to be
read
No. of 1st word to be
written
Number of words to be
written
---
HiLoHiLoHiLoHiLo---
1byte1byte2bytes2bytes2bytes2bytes
---Number of bytes to be
written
Value of 1
st
word to be
written
Value of last word to be writtenCRC16
---HiLo-----------------------------HiLoLoHi
1 byte2 bytes2 bytes2 bytes
Response:
st
Slave no.17Number of bytes
Value of 1
word readValue of last word readCRC16
read
HiLo--------------HiLoLoHi
1 byte1 byte1 byte2 bytes2 bytes2 bytes
Example: This example combines the two examples for functions 3 and 16. With function 23, the line is less busy than with these two
functions. However, the number of words that can be read and written is restricted.
• Write the values 20 (16#14) and 30 (16#1E) respectively to the 2 logic address words 9001 and 9002 on slave 2.
• Read the 4 logic address words 3102 to 3105 on the same slave (values read = 16#0028, 16#0258, 16#01F4, and 16#0000).
Request:
Slave no.Request codeNo. of 1
word to be
read
No. of words to be
read
No. of 1st word to be
written
No. of words to be
written
---
st
HiLoHiLoHiLoHiLo---
02170C1E000423290002---
--- No. of bytes to be writtenValue of 1
st
word to be writtenValue of 2nd word to be writtenCRCCRC
---HiLoHiLoLoHi
---040014001ED2F5
Response:
Slave no.Response codeNo. of bytes
read
Value of 1
word read
st
Value of 2
word read
HiLoHiLoHiLoHiLoLoHi
nd
Value of 3
word read
rd
Value of 4
word read
th
CRCCRC
0217080028025801F4000012F0
31
8. Modbus protocol
8. 10. Read Device Identification (43 = 16#2B)
Request:
Slave no.2B
1 byte1 byte1 byte1 byte1 byte2 bytes
Response:
Slave no.2B
1 byte1 byte1 byte1 byte1 byte
-------Number of additional frames
-------Id of object no. 1
00+
1 byte1 byte13 bytes
-------Id of object no. 2
01
1 byte1 byte11 bytes
-------Id of object no. 3
02
1byte1byte04bytes
Type of MEI
0E
Type of MEI
0E
00
1byte1byte1byte
Length of object no. 1
Length of object no. 2
Length of object no. 3
ReadDeviceId
ReadDeviceId
0D
0B
04
01
01
Object Id
Degree of conformity
Next object Id
00
Value of object no. 1
“Telemecanique”
Value of object no. 2
“ATV71HU15M3”
Value of object no. 3
00
“0201”
LoHi
02
Number of objects04-------
CRC16
-------
-------
-------
-------
-------Id of object no. 4
06
1byte1byte09bytes
-------CRC16
LoHi
1byte1byte
The total response size given in this example equals 55 bytes.
The response contains the following four objects:
• Object no. 1:Manufacturer name (always "Telemecanique", i.e., 13 bytes).
• Object no. 2:Device catalog number (ASCII string; for example: “ATV71HU15M3”, i.e., 11 bytes).
The length of this object varies accordin g to drive type. Use the “Length of object no. 2” field to det ermine the length.
• Object no. 3:Device version, in "MMmm" format where "MM" represents the determinant and "mm" the subdeterminant (4-byte
ASCII string; for example: "0201" for version 2.1).
• Object no. 4:Device name (ASCII string; for example: "MACHINE 4", i.e., 9 bytes).
The length of this object varies according to the device name assigned to the drive (the latter being configured by
the user): [7. DISPLAY CONFIG.] menu, [7.1 USER PARAMETERS] submenu, [DEVICE NAME] parameter.
This menu can only be accessed in Expert mode.
Maximum size 16 bytes.
Length of object no. 4
09
Value of object no. 4
“MACHINE 4”
-------
32
8. Modbus protocol
Negative response specifically related to the identification function:
Slave no.2B + 80
AB
1 byte1 byte1 byte1 byte1 byte1 byte
Error code:16#00 =No error
16#01 =The "Request code" (16#2B), the "Type of MEI" (16#0E) or the "ReadDeviceId" (16#01) contained in the
16#02 =The "Object Id" (16#00) contained in the request is incorrect.
Example of positive response:
• Address = 2
• Manufacturer name = “Telemecanique”
• Device name = “ATV71HU15M3”
• Device version = “0201”
• Device name = “MACHINE 4”
Request:
Slave no.Request codeType of MEIReadDeviceldObject Id
022B0E01003477
Response:
Type of MEI
0E
request is incorrect.
Error code
00 to 02
CRC16
LoHi
CRC
Lo
CRC
Hi
Slave no.Response
022B0E0102000004
-----Id of
object no.
-----’T’’e’’l’’e’’m’’e’’c’’a’’n’’i’’q’’u’’e’
----Id of
----’A’’T’’V’’7’’1’’H’’U’’1’’5’’M’’3’
----Id of
----’0’’2’’0’’1’
----Id of
----’M’’A’’C’’H’’I’’N’’E’’ ’’4’LoHi
1
000D54656C656D6563616E69717565
object no.
2
010B4154563731485531354D33
object no.
020430323031
object no.
4
06094D414348494E4520346F50
code
Length of
object no. 1
Length of
object no. 2
Length of
object no. 3
Length of
object no. 4
Type of
MEI
Value of object no. 3
ReadDeviceld
Value of object no. 4CRC CRC
Degree of
conformity
Value of object no. 1
Value of object no. 2
No. of additional
frames
Next object Id
----
----
Object no.
-------
-------
-----
-----
33
8. Modbus protocol
8. 11. Communication scanner
The communication scanner can be used to enhance application performance. The drive automa tically cop ies non-cont iguous paramet ers
to an input table and an output table. Thus, the copy of several non-contiguous parameters can be read or written in a single request (an
operation which would normally have required several Modbus requests).
The input table and the output table each contain 8 variables.
Output variablesLogic addressDefault assignment
[Com Scan Out1 val.](nC1)12 761 = 16#31D9Control word (CMd)
[Com Scan Out2 val.](nC2)12 762 = 16#31DASpeed reference (LFrd)
[Com Scan Out3 val.](nC3)12 763 = 16#31DBNot used
[Com Scan Out4 val.](nC4)12 764 = 16#31DCNot used
[Com Scan Out5 val.](nC5)12 765 = 16#31DDNot used
[Com Scan Out6 val.](nC6)12 766 = 16#31DENot used
[Com Scan Out7 val.](nC7)12 767 = 16#31DFNot used
[Com Scan Out8 val.](nC8)12 768 = 16#31E0Not used
Input variablesLogic addressDefault assignment
[Com Scan In1 val.](nM1)12 741 = 16#31C5Status word (EtA)
[Com Scan In2 val.](nM2)12 742 = 16#31C6Output speed (rFrd)
[Com Scan In3 val.](nM3)12 743 = 16#31C7Not used
[Com Scan In4 val.] (nM4)12 744 = 16#31C8Not used
[Com Scan In5 val.](nM5)12 745 = 16#31C9Not used
[Com Scan In6 val.](nM6)12 746 = 16#31CANot used
[Com Scan In7 val.](nM7)12 747 = 16#31CBNot used
[Com Scan In8 val.](nM8)12 748 = 16#31CCNot used
The values of these communication scanner variables can be displayed on the graphic display terminal using the
[1.2-MONITORING] menu, [COMMUNICATION MAP](CMM) submenu (see section "7. Diagnostics - 7.4 Communication scanner").
These parameters can be accessed via all the read and write requests supported by the drive.
There is a marked improvement in performance for the following functions:
CodeModbus nameDescriptionSize of data
3 = 16#03Read Holding RegistersRead N output words63 words, max.
4 = 16#04Read Input RegistersRead N input words63 words, max.
16 = 16#10Write Multiple RegistersWrite N output words61 words, max.
23 = 16#17Read/Write Multiple RegistersRead/write N words20/20 words max.
43 = 16#2BRead Device IdentificationIdentification
34
8. Modbus protocol
The link between the drive parameters and the communication scanner variables can be made:
- Via the display terminal (see section "6. Configuration - 6.2 Communication scanner")
- Via Modbus: Before starting the application, the PLC must first write the address tables described below.
word readValue of 6th word readValue of 7th word readValue of 8th word readCRCCRC
---HiLoHiLoHiLoHiLo LoHi
---00F0006500320000 E490
---
---
36
8. Modbus protocol
8. 12. Exception responses
An exception response is returned by a slave when it is unable to perform the request which is addresse d to it.
Format of an exception response:
Slave
no.
1 byte1 byte1 byte2 bytes
Response
code:
Error code:1 = The function requested is not recognized by the slave.
Example: Writing the value 1 to the status word (EtA) = logic address 3201 (which cannot be written, because in “read-only" mode) on
slave 4
Request:
Slave no.Request
4 100C8100010200018AD1
Response:
Response
code
request code + H’80.
2 = The addresses indicated in the request do not exist in the slave.
3 = The values indicated in the request are not permitted on the slave.
4 = The slave has started to execute the request but cannot continue to process it completely.
6 = The requested write operation has been refused because the drive is in "Forced local" mode.
7 = The requested write operation has been refused because the motor is running (configuration parameters).
code
Error
code
st
No. of 1
HiLoHiLoHiLoLoHi
wordNo. of wordsNo. of
CRC16
LoHi
Value of 1st word CRCCRC
bytes
Slave no.Response
code
490005C01
Error codeCRC
Lo
CRC
Hi
37
8. Modbus protocol
8. 13. Read non-existent or protected parameters
If a set of parameters is read using a Modbus function, the value returned for non-exi stent and protected parameters is equal to 16#8000.
If the same Modbus function is used to read parameters, all of which are non-existent or protected, the drive sends back an exception
response with an error code equal to 2.
Example of non-existent or protected parameters being read:
In this example, the same request to read a non-exi stent parameter followed by 2 existing parameters is used s everal times in a row in order
to demonstrate the effects of parameter protection.
The "Read Holding Registers" request (3) is addressed to a drive with a Modbus address of 12 (16#0C). The read operation is performed
for 3 consecutive words, starting with address 8400.
Slave no.Request codeNo. of 1st wordNo. of wordsCRC16
0C0320D000030EEF
↔ 2] (COP)2
HiLoHiLoLoHi
Response:
Scenario no. 1: Parameters CHCF (8401) and COP (8402) not protected
to 16#8000 for the non-existent parameter located at address 8400.
Slave no.Response codeNo. of bytes read
0C0306
Scenario no. 2: Parameter CHCF (8401) protected and COP (8402) not protected
16#8000 for the non-existent parameter located at address 8400 and for parameter CHCF.
Slave no.Response codeNo. of bytes read
0C0306
Scenario no. 3: Parameters CHCF (8401) and COP (8402) protected
all the parameters read are either non-existent, or protecte d; error code equal to 2 (the word addresses in dicated in the request do not exist
in the slave).
Slave no.Response codeError codeCRC16
0C80+03 = 83025132
Value 8400Value 8401Value 8402CRC16
HiLoHiLoHiLoLoHi
80000003000217E4
Value 8400Value 8401Value 8402CRC16
HiLoHiLoHiLoLoHi
800080000002CE24
LoHi
V Successful reading of these two parameters and value equal
V Successful reading of COP and value equal to
V Exception response (response code = 16#80 + request code), as
38
9. Appendix
9. 1. RS485 standard
The RS485 standard (ANSI/TIA/EIA-485-A-1998) allows variants of certain characteristics:
• Polarization
• Line termination
• Distribution of a reference potential
• Number of slaves
• Length of bus
It does not specify the connector type or pinout.
The Modbus specification published on www.modbus.org in 2002 contains precise details of all these characteristics. They are also
summarized in the next sections (Modbus 2-wire and 4-wire standard schematics). The latest generation Telemecanique devices
(Altivar 31, Altivar 71, etc.) conform to this specification.
Older devices comply with earlier specifications. The two most widespread are described in the following sections:
• "Uni-Telway schematic" page 42
• "Jbus schematic" page 43
Requirements enabling different types of protocol to coexist are given in the following section in this appendix:
• "Creating a Modbus bus using non-standard equipment" on page 45
39
9. Appendix
9. 2. Modbus 2-wire standard schematic
The standard schematic corresponds to the Modbus specification published in 2002 on www.modbus.org
(Modbus_over_serial_line_V1.pdf, Nov 2002) and, in particular, to the 2-wire multipoint serial bus schematic.
The Modbus card (VW3 A3 303) conforms to this specification.
Schematic diagram:
Master
G
R
650 Ω
D1
5 V
650 Ω
0 V
120 Ω
1n F
Type of trunk cable
Maximum length of bus
Maximum number of stations (without
repeater)
Maximum length of tap links
Bus polarization
Line termination
Common polarity
120 Ω
1n F
R
Slave 1
G
D0
Common
R
Slave n
G
Shielded cable with 1 twisted pair and at least a 3rd conductor
1000 m at 19200 bps with the Telemecanique TSX CSAp00 cable
32 stations, i.e., 31 slaves
• 20 m for one tap link
• 40 m divided by the number of tap links on a multiple junction box
• One 450 to 650 Ω pull-up resistor to the 5 V (650 Ω or thereabouts recommended)
• One 450 to 650
Ω pull-down resistor to the Common (650 Ω or thereabouts
recommended)
This polarization is recommended for the master.
One 120 Ω 0.25 W resistor in series with a 1nF 10 V capacitor
Yes (Common), connected to the protective ground at one or more points on the bus
40
9. Appendix
9. 3. Modbus 4-wire standard schematic
Master
G
R
5 V
TXD1
LT
TXD0
RXD1
LT
RXD0
Slave pair
Master pair
Rp
Rp
LT
5 V
Rp
LT
Rp
Common
R
G
R
G
Slave 1Slave n
41
9. Appendix
9. 4. Uni-Telway schematic
The Uni-Telway bus schematic was used by Telemecanique for older-generation drives and soft starters (ATV58, ATV28, ATS48, etc.)
marketed before the Modbus specifications were published on www.modbus.org.
Schematic diagram:
Master
G
R
4.7 kΩ
D(B)
5 V
4.7 kΩ
0 V
120 Ω
1 nF
D(A)
0VL
5 V
4.7 kΩ
0 V0 V
R
4.7 kΩ
G
Slave 1
4.7 kΩ
R
Slave n
5 V
4.7 kΩ
G
120 Ω
1 nF
Type of trunk cableCable with 2 twisted pairs shielded in pairs
Maximum length of bus1000 m at 19200 bps
Maximum number of stations (without
29 stations, i.e., 28 slaves
repeater)
Maximum length of tap links
•20 m
• 40 m divided by the number of tap links on a multiple junction box
Bus polarizationFor the master and each slave:
• One 4.7 kΩ pull-up resistor to the 5 V
• One 4.7 kΩ pull-down resistor to the 0 VL
Line terminationOne 120 Ω 0.25 W resistor in series with a 1 nF 10 V capacitor
Common polarityYes (0 VL) and high impedance placed between 0 VL and the ground in each station
42
9. Appendix
9. 5. 2-wire Jbus schematic
Schematic diagram:
150 Ω150 Ω
L- (B/B')
L+ (A/A')
Master
470 Ω
G
R
5 V
470 Ω
0 V
R
G
Slave 1
Type of trunk cableCable with 1 shielded twisted pair
Maximum length of bus1,300 m at 19200 bps
Maximum number of stations (without
32 stations, i.e., 31 slaves
repeater)
Maximum length of tap links3 m
Bus polarizationOne 470 Ω pull-up resistor to the 5 V
One 470 Ω pull-down resistor to the 0 V
This polarization is often provided in the master.
Line terminationOne 150 Ω resistor
Common polarityNo
R
Slave n
G
43
9. Appendix
9. 6. Creating a Modbus bus using non-standard equipment
b Different scenarios
M If the Modbus bus is created using the latest-generation Telemecanique devices and Telemecanique Modbus wiring accessories,
installation is simple and no calculation is required (see the section entitled "Connecting to the bus").
M If a new Modbus bus has to be created using devices of different brands or older-generation devices, which do not comply with the
Modbus standard, several checks are required (see "Recommendations" below).
M If, on an existing Modbus bus, a device with 4.7 kΩ polarization is to be replaced by a new-generation device, set the 2 polarization
switches to the lower position to activate the card’s 4.7 kΩ polarization.
Polarization switche s :
Ω RS485 line polarization at drive level
4.7 k
b Recommendations
1. Identify the polarities D0 and D1.
They are labeled in different ways depending on the standard:
Standard
ModbusEIA/TIA-485
(RS 485)
D0A/A’D (A)RD +/TD + or L +
Signals
Generator
Receiver
However, certain RS485 electronic components are labeled in the opposite way to the EIA/TIA-485 standard.
It may be necessary to perform a test by connecting a master to a slave, then reversing the connection in the event of failure.
2. Check polarizations
Check the documentation supplied with the devices to determine their polarization.
If there is a polarization, check that the equivalent polarizat ion value is correct (see "Calculating the polarization").
It is not always possible to implement correct polarizat ion (for example, if the 5 V is not available on the master).
In this case, it may be necessary to limit the number of slaves.
3. Choose a line terminator
If there is a polarization, select an RC line terminator (R = 120 Ω, C = 1 nF)
If it is not possible to install a polarization, select an R line terminator (R = 150 Ω).
D1B/B’D (B)RD -/TD - or L -
CommonC/C’0VL
BG
RR
Uni-TelwayJbus
44
9. Appendix
b Calculating the polarization
M Principle
1
1
---------
Rm
Ω and 650 Ω.
1
1
1
----------
Rs
1
----------…+++=
Rs
1
----------
Rs
Master
R
2
----------…+++ +=
Rs
1
2
G
5 V
You must ensure that the equivalent bus resistance is between 162
The equivalent bus resistance (Re) depends on the polarization resistance of the slaves (Rs) and the master (Rm):
1
------- -
---------
Re
Rm
If Re is too low, reduce the number of slaves.
If Re is too high, adapt the master’s polarization (if po ssible) or add polarization resistors (Rp).
1
------- -
Rp
1
------- -
Re
Rm
Rm
0 V
D1
120 Ω
1 nF
D0
5 V
Rp
Common
5 V
Rs
1
0 V
R
Slave 1
Rs
1
R
G
G
Slave n
Rp
0 V
Example 1
If the master has 470 Ω polarization and all the slaves have 4.7 kΩ polarization, a maximum of 18 slaves can be connected.
Rm = 470 Ω
Rs = 4.7 kΩ
A/Re = 1/470 + 18 x 1/4700
i.e., Re = 168 Ω
Example 2
If the bus polarization Rp is 470 Ω (installed in the master) and 2 slaves hav e 4.7 Ω polarization, the equivalent polarization is:
1/Re = 1/470 + 1/4700 + 1/4700
i.e., Re = 1/ (1/470 + 1/4700 + 1/4700)
and therefore Re = 390 Ω
390 Ω is between 162
Ω and 650 Ω, and the schematic is correct.
For an ideal equivalent polarization (650 Ω), the master’s polarization can be adapted so that:
1/650 = 1/Rm + 1/4700 + 1/4700
i.e., Rm = 1/(1/650 - 1/4700 - 1/4700)
and therefore Rm = 587 Ω
45
9. Appendix
9. 7. RS485 schematic for the card
The RS485 interface on the Modbus card is electrically isolated from the drive.
Schematic diagram:
5V
Polarization switch
Pull-up polarization resistor
4.7k
Ω
G
Tx
D1=B/B'=D(B)
D0=A/A'=D(A)
Female 9-way
SUB-D
7
3
Pull-down polarization resistor
4.7k
Enable
Ω
Polarization switch
0V
R
0V
5V
100k
Ω
R
100k
Ω
0V
RXD1=RD(B)
RXD0=RD(A)
0V
5624
Rx
&
The polarization switches are used to connect or disconnect th e pull-up and pull-down resisto rs, which impl ement eithe r Modbus (no sla ve
polarization) or Uni-Telway (4.7 kΩ polarization for each station) type polarization.