Siemens POL6XX Modbus Communication, POL902 Modbus Communication Module Integration guide
The Siemens POL6XX and POL902 are designed to provide a Modbus communication interface for integration with other systems and devices. These products offer a powerful and reliable way to connect your Climatix™ controllers to Modbus networks, enabling seamless data exchange and control.
advertisement
Assistant Bot
Need help? Our chatbot has already read the manual and is ready to assist you. Feel free to ask any questions about the device, but providing details will make the conversation more productive.
POL6XX
Modbus RTU / TCP
POL6XX
Climatix™
Modbus communication, slave mode
Integration guide
CB1J3960en
01.03.2010
Building Technologies
Siemens Switzerland Ltd.
Building Technologies Group
International Headquarters
Gubelstrasse 22
CH-6301 Zug
Tel. +41 41-724 24 24
Fax +41 41-724 35 22 www.siemens.com/sbt
2 / 28
Siemens
Building Technologies
Modbus communication, slave mode
© 2010 Siemens Switzerland Ltd.
Subject to change
CB1J3960en
01.03.2010
Table of contents
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
3
3.1
3.2
3.3
3.4
3.5
2
2.1
2.2
2.3
2.4
2.5
2.6
4
4.1
4.2
4.3
About this document ..............................................................................5
Revision history.........................................................................................5
Before you start.........................................................................................5
Reference documents...............................................................................5
Document conventions .............................................................................6
Important information on safety ................................................................7
Trademarks and copyrights.......................................................................8
Quality assurance .....................................................................................8
Document use/ request to the reader .......................................................8
Modbus networks ...................................................................................9
Modbus protocol........................................................................................9
RS485 networks......................................................................................10
RS485, cable installation ........................................................................10
Bus termination ....................................................................................... 11
TCP/IP networks ..................................................................................... 11
Tools........................................................................................................ 11
Commission instructions.....................................................................13
General ...................................................................................................13
Commission internal Modbus RTU .........................................................14
Commission internal Modbus TCP .........................................................16
The Modbus module ...............................................................................17
Commission Modbus modules................................................................18
Integration..............................................................................................21
Map registers ..........................................................................................21
Function codes........................................................................................21
Reference Modbus addresses ................................................................22
5
5.1
5.2
5.3
5.4
Other information..................................................................................23
Troubleshooting, tips...............................................................................23
FAQ on TCP/IP .......................................................................................24
Upgrade application or BSP via SD card................................................25
Override I/Os via communication............................................................26
Index ................................................................................................................27
Siemens
Building Technologies
Modbus communication, slave mode
Table of contents
3 / 28
CB1J3960en
01.03.2010
4 / 28
Siemens
Building Technologies
Modbus communication, slave mode
Table of contents
CB1J3960en
01.03.2010
Version Date
Validity
Product versions
Target audience
Prerequisites
Changes Section Pages
1.2 Before you start
This document applies to the following products:
Name
Modbus communication module
Controller with onboard modbus
Controller with onboard TCP/IP
Type (ASN) Short name
POL902.00/STD Modbus module
POL63x.00/STD Basic controller
POL638.00/STD TCP/IP controller
Description and functional scope of the products are based on the Climatix Valid
Version Set 8.0 or higher and application based on standard AHU.
This document is intended for the following audience:
Modbus system integrators
Measuring and control engineering staff
Sales and commissioning staff
The above target audience:
Has general professional knowledge on planning and commissioning HVAC technology measuring and control solutions.
Has basic knowledge of Modbus.
Has the additional reference addresses documentation for the specific product.
Further information
The following documents contain additional information on the products described in this manual:
Document
Data sheet "Communication module Modbus"
Basic documentation "Modbus communication module"
Reference addresses "Modbus communication, slave mode"
Note! Uniqe documentation for each application.
Basic documentation "Standard Application AHU"
Order no.
CB1Q3934en
CB1P3934en
CB1Y3961en
CB1P3977en
Siemens
Building Technologies
Modbus communication, slave mode
About this document
5 / 28
CB1J3960en
01.03.2010
Symbols used
Abbreviations
STOP
Below is an overview of all symbols used in this document denoting risks or important information:
This symbol draws your attention to special safety notes and warnings. Failing to observe these notes may result in injury and/or serious damages.
This symbol denotes special information that, when failed to observe, may result in faulty functionality or loss of data.
Notes with this symbol provide important information that requires appropriate attention.
This symbol marks passages containing tips and tricks.
The following abbreviations are used in text and illustrations:
Abbreviation Meaning
BACS Building Automation and Control System
BSP Board Support Package (operating system)
Climatix
Gateway
HMI
Controller family with common tools
A device for transfer data between different kind of networks
Human Machine Interface, e.g Operator unit
HVAC
LSB
MSB
RTU
SELV
TCP/IP
Heating, Ventilating, Air Conditioning
Least Significant Bit
Most Significant Bit
Remote Terminal Unit
Safety Extra-Low Voltage
Transmission Control Protocol, e.g. Ethernet/Internet
6 / 28
Siemens
Building Technologies
Modbus communication, slave mode
About this document
CB1J3960en
01.03.2010
Field of application
Intended use
Electrical installation
Wiring
Commissioning and maintenance
Maintenance
Faults
Storage and transport
Disposal
1.5 Important information on safety
Use Modbus communication only for control and monitoring.
Trouble-free and safe product operation of the above products presupposes transport, storage, mounting, installation, and commissioning as intended as well as careful operation.
Fuses, switches, wiring and grounding must comply with local safety regulations for electrical installations.
When wiring, strictly separate AC 230 V mains voltage from AC 24 V safety extralow voltage (SELV) to protect against electrical shock!
Only qualified staff trained accordingly may prepare for use, commission, and maintain Modbus communication modules.
Maintenance of Climatix Controller and Modbus communication modules generally only means regular cleaning. We recommend removing dust and dirt from system components installed in the control panels during standard service.
Only authorized staff may diagnose and correct faults and recommission the plant.
This applies to working within the panel as well (e.g. testing or changing fuses).
Refer to the environmental conditions specified in the respective data sheets for storage and transport.
If in doubt, contact your supplier.
Devices contain electrical and electronic components; do not dispose of them in household garbage.
Observe all local and applicable laws.
Siemens
Building Technologies
Modbus communication, slave mode
About this document
7 / 28
CB1J3960en
01.03.2010
Trademarks, legal owners
Copyright
Document contents
Request to the reader
Exemption from liability
1.6 Trademarks and copyrights
The table below lists the third-party trademarks used in this document and their legal owners. The use of trademarks is subject to international and domestic provisions of the law.
Trademarks Legal owner
Modbus® The Modbus Organization, Hopkinton, MA, USA
All product names listed in the table are registered (®) or not registered (™) trademarks of the owner listed in the table. We forgo the labeling (e.g. using the symbols ® and ™) of trademarks for the purposes of legibility based on the reference in this section.
This document may be duplicated and distributed only with the express permission of Siemens, and may be passed on only to authorized persons or companies with the required technical knowledge.
assurance
These documents were prepared with great care.
The contents of all documents are checked at regular intervals.
All necessary corrections are included in subsequent versions.
Documents are automatically amended as a consequence of modifications and corrections to the products described.
Please make sure that you are aware of the latest document revision date.
1.8 Document use/ request to the reader
Before using our products, it is important that you read the documents supplied with or ordered at the same time as the products (equipment, applications, tools etc.) carefully and in full.
We assume that persons using our products and documents are authorized and trained appropriately and have the technical knowledge required to use our products as intended.
Siemens assumes no liability to the extent allowed under the law for any losses resulting from a failure to comply with the aforementioned points or for the improper compliance of the same.
8 / 28
Siemens
Building Technologies
Modbus communication, slave mode
About this document
CB1J3960en
01.03.2010
Modbus, general information
Master/slave protocol
Transactions on
Modbus
Function codes
Transmission modes
Telegrams with multiple data points
Modbus TCP Ethernet
For more information on Modbus
The following section provides only a brief overview of the Modbus protocol.
For the full specification, see:
"Modicon Modbus Protocol Reference Guide PI MBUS 300 Rev. J".
The Modbus is a master/slave protocol. This, by definition, means that a Modbus network contains only one master and at least one slave.
The Modbus master uses a slave query to start transactions on the network. The slave either responds positively with the requested service (response) or transmits an "exception message".
The type of transaction is defined by the function code transmitted in the Modbus telegrams. A function code defines the following:
Structure of the telegram, query and response.
Direction of data transmission (master → slave or slave → master).
Data format of data point.
The Modbus protocol defines two alternative serial transmission modes:
These modes have the following characteristics:
RTU (Remote Terminal Unit) mode
Binary-coded data.
Start and end of telegrams marked by timed pauses (a "silent interval") between the characters transmitted.
Check sum algorithm: CRC (cyclical redundancy check).
ASCII mode
Data in hexadecimal notation.
Beginning and end of telegrams marked by start and end characters.
Check sum algorithm: LRC (longitudinal redundancy check).
Certain types of Modbus transactions allow for transmission of a variable number of Modbus data points in a single telegram.
A Modbus TCP/RTU gateway helps connect a Modbus/TCP master to one or several Climatix controllers (slaves) if not a Climatix controller with internal TCP/IP onboard is available:
Modbus RTU, RS485 Modbus TCP, Ethernet
Gateway Master
P3934Z03
Slave Slave
The Modbus TCP/RTU gateway acts as a Modbus/TCP slave on an Ethernet network, and transforms the queries to the serial Modbus network and back.
See www.modbus.org
Siemens
Building Technologies
Modbus communication, slave mode
Modbus networks
9 / 28
CB1J3960en
01.03.2010
RS485 definition
More than 32 devices on one RS485 trunk?
Task of the third wire
Screening not required
Screening as third wire?
Cat5 cables?
RS485 is a balanced line, half-duplex transmission system that meets the requirements for a truly multi-point communications network. The standard specifies up to 32 drivers and 32 receivers on a single (2-wire) bus.
Half-duplex data transmission means that data can be transmitted in both directions on a signal carrier, but not at the same time.
Yes, a repeater makes this possible.
However, in reality a repeater is not always necessary because:
Although the RS485 standard is based on just 32 devices, most RS485 chips need less than the specified unit load since initial development. Today, some devices on the market require only half or a quarter of the load units.
Read the associated data sheets and count the required load to determine how many devices you can install. This data is located in "UL" ("Unit Load").
2.3 RS485, cable installation
Handle the RS485 bus in practice as 3-wire network even though RS485 as per
EIA 485 only specifies a two-wire line for differential signals. Reason:
Devices with RS485 interface have third connection named "Common", "Ground" or "REF" (e.g. in Climatix).
This connection is not used to connect to ground, but rather for a common reference signal. Voltage on lines Tx/Rx (or +/-) are measured relative to the voltage level on the reference signal.
You do not need screens. The twisted cable for Tx and Rx suppresses interference more effectively than a screen.
You can use the third wire as screen for emergencies. It is better, however, to use a wire of the second wire pair of a CAT5 cable; see "Cable selection" below.
Yes, these cables are good. Use a pair for Tx/Rx and a wire of the other pair for the reference signal (ground).
We recommend the following cables:
Manufacture / Type Specifications
Belden 3106A Multi-Conductor - EIA Industrial RS-485 PLTC/CM
22 AWG stranded (7×30) tinned copper conductors,
Datalene® insulation, twisted pairs, overall Beldfoil®
Bild02 shield (100% coverage) plus a tinned copper braid (90% coverage), drain wire, UV resistant PVC jacket.
Belden 3107A Multi-Conductor - EIA Industrial RS-485 PLTC/CM
22 AWG stranded (7×30) tinned copper conductors,
Datalene® insulation, twisted pairs, overall Beldfoil®
Bild03 shield (100% coverage) plus a tinned copper braid (90% coverage), drain wire, UV resistant PVC jacket.
10 / 28
Siemens
Building Technologies
Modbus communication, slave mode
Modbus networks
CB1J3960en
01.03.2010
Cable length and baud rates
RS485, cable installation,
continued
RS485 does not specify max cable length. It depends largely on transmission rates:
The greater the transmission rate, the shorter the possible cable length.
Rule of thumb for AWG cable:
Cable length [m] x data rate [bps] < 10
8.
The following guide values result:
Baud rate Cable length [m]
9,600
19,200
10,400
5,200
38,400 2,600
Additionally, note the following:
The higher the baud rate, the more important the cable installation quality. Issues such as twisted pair cable unfolded at each resistor gain importance.
Termination resistance
As Modbus RTU is based on an RS485 bus, both bus ends require terminating resistances.
In Climatix, the resistances can be enabled or disabled via operator unit. No external resistance is needed.
Modbus TCP port
IP address
Modbus master simulation tools
Modbus TCP in Climatix uses the TCP port 502. This port number is not changeable.
The IP address is assigned either dynamically via the DHCP server or set manually via HMI. Normally is to use fixed IP address.
If the controller is Server (Slave) he is able to serve 3 Modbus IP Clients, so it is possible to connect for example 3 touch panels to one controller at the same time.
The onboard Ethernet port used for Modbus can be used for remote service or internal web HMI at the same time as Modbus TCP.
2.6 Tools
Modbus slave devices e.g. Climatix controllers can be tested with several Modbus master simulation tools such as "Modbus Poll" or "ModScan" from a computer.
"Modbus Poll" can be downloaded from www.modbustools.com.
A RS485/RS232 converter or a Modbus RTU/TCP gateway may be needed to connect to a computer.
Siemens
Building Technologies
Modbus communication, slave mode
Modbus networks
11 / 28
CB1J3960en
01.03.2010
Blank page
12 / 28
Siemens
Building Technologies
Modbus communication, slave mode
Modbus networks
CB1J3960en
01.03.2010
Connection ways
Internal RTU
(POL63x)
Internal TCP
(POL638)
External communication module POL902
3.1 General
There are up to 3 ways to communicate with Modbus on a Climatix controller:
Internal RTU (POL63x)
Internal TCP (POL638)
External communication module POL902
A Modbus RTU, via RS485, interface is always available on the basic controller
POL63x.00/STD. It can be defined as the master or slave or switched off.
The internal Modbus interface is automatically set to master if any master function is enabled in the controller.
A Modbus TCP interface is available on the POL638.00/STD controller via the standard Ethernet port. The internal Modbus TCP interface is normally only used for slave mode and can be used for slave mode even if the RS485 port is used as master.
An extra slave interface, with two separate channels, is always provided with the external Modbus communication module POL902. The internal interface cannot be used if the external module is used and the internal interface is no longer required as the master.
Prerequisite for commissioning any of the above mentionned ways:
Working application loaded and started in the Climatix controller.
Siemens
Building Technologies
Modbus communication, slave mode
Commission instructions
13 / 28
CB1J3960en
01.03.2010
Involved devices
Connection
Configuration via operator unit
14 / 28
Siemens
Building Technologies
3.2 Commission internal Modbus RTU
The picture shows the devices and connections involved in commissioning:
POL63x
RS485
HMI-DM
Modbus RTU
Proceed as follows to connect the Climatix controller to the Modbus bus:
Step Action
2 Connect Modbus bus cable to the RS485 interface
(pins A+ and B-, Ref for GND).
Proceed as follows to configure the controller for internal Modbus RTU:
Step Action
1 Log in to HMI using the password for level 4 (Service), default 2000.
Internal mode:
Select the integrated Modbus interface RS485 to be used as slave.
Caution!
The integrated RS485 cannot be used as slave if already used as master. This selection is blocked when a function require master.
Internal slave Address:
Enter the corresponding Modbus slave address (1…247).
Caution!
This is true for Modbus TCP as well.
Baudrate:
Enter the transmission rate as per the Modbus (2400, 4800, 9600,
19200 and 38400). All participants must have the same setting.
One or two stop bits
All participants must have the same setting.
Parity:
None, even or odd parity.
All participants must have the same setting
Delay time:
Delays the response by n milliseconds.
- Response timeout:
Setting access time if used as master.
The master must undertake read access within this period, otherwise an alarm is triggered. This has no influence for Modbus slave mode.
Termination:
The RS485 topology must always be ended using wave resistors.
They can be enabled or disabled as described in Section, 2.4.
When done, restart controller using this command.
Extra MB communication is the alarm object and settings like alarm class etc for Modbus faults can be changed here.
Modbus communication, slave mode
Commission instructions
CB1J3960en
01.03.2010
Configuration via operator unit,
cont.
Commission internal Modbus RTU,
cont.
After restart, the internal Modbus RTU is configured and ready to use.
As a matter of principle, the controller must be restarted with "Reset required !!" or power off/on the controller after changing any settings to assume the data.
Other setting than described above has nothing to do with Modbus RTU slave mode and should not be changed.
Siemens
Building Technologies
Modbus communication, slave mode
Commission instructions
15 / 28
CB1J3960en
01.03.2010
Involved devices
Connection
Configuration via operator unit
16 / 28
Siemens
Building Technologies
3.3 Commission internal Modbus TCP
The picture shows the devices and connections involved in commissioning:
POL638
Ethernet
HMI-DM
Modbus TCP
Connect the Climatix controller to the Ethernet (Modbus TCP) with a standard network cable.
Proceed as follows to configure the controller for internal Modbus TCP:
Step Action
1 Log in to HMI using the password for level 4 (Service), default 2000.
-
-
Internal mode:
Selects if the integrated Modbus interface RS485 should be used as master or slave. This has no influence for Modbus TCP.
Enter the corresponding Modbus slave address (1…247).
Caution!
This is true for Modbus RTU as well.
Note!
Settings for TCP/IP can also be displayed and changed in:
Main Index > System overview > Communication > TCP/IP >
Take care to change TCP/IP setting if the controller is already connected to Ethernet for other purpose.
Active, DHCP server issues addresses.
Passive, IP address is fixed.
Enter controller IP address if DHCP is set to passive.
Enter subnet mask if DHCP is set to passive.
Enter gateway address if DHCP is set to passive.
When done, restart controller using this command.
After restart, the internal Modbus TCP is configured and ready to use.
As a matter of principle, the controller must be restarted with "Reset required !!" or power off/on the controller after changing any settings to assume the data.
Other setting than described above has nothing to do with Modbus RTU slave mode and should not be changed.
Modbus communication, slave mode
Commission instructions
CB1J3960en
01.03.2010
Design
Elements and connections
Status LEDs
"BSP" LED
"BUS" LED
1
3.4 The Modbus module
The figure shows the Modbus module. Properties:
Two galvanically separated RS485 interfaces.
Connection to the Climatix controller via internal communications extension bus using the plug on the controller's left.
6
RS485 5
SIEMENS
SIEMENS
POL902.00/xxx
RS485 BSP BUS
4
3
2
The elements and connections in the figure are:
Pos. Element / Connection
1 Modbus RS485 interface T1 (slave, channel 0).
2 Modbus RS485 interface T2 (slave, channel 1).
3 Status display "BSP" (Board Support Package).
4 Status display "BUS" (bus connections o.k. / bus traffic).
5 Plug connection "Communication extension bus".
6 Climatix controller POL6XX.
The status LEDs "BSP" and "BUS" can light red, green and yellow during operation.
This LED informs on the status of the "Board Support Package" (BSP). Color and flashing frequency of the LED:
Color Flashing frequency Meaning / Mode
Red / yellow 1 s "on" / 1 s "off" Upgrade mode.
Green
Yellow
Red
Red
Steady "on"
Steady "on"
Flashing at 2Hz
Steady "on"
BSP operating and communication with controller working.
BSP operating, but no communication with controller.
BSP error (software error).
Hardware fault.
This LED shows the status of external communication with the bus, not to the controller. Color and flashing frequency of the LED:
Color
Green
Flashing frequency Meaning / Mode
Steady "on" Communication active.
Red Steady "on" Communication interrupted.
Power supply is outside the allowed range if both LEDs are dark.
Siemens
Building Technologies
Modbus communication, slave mode
17 / 28
CB1J3960en
01.03.2010
Involved devices
Connection
Configuration via operator unit
3.5 Commission Modbus modules
The picture shows the devices involved in commissioning:
Modbus RTU
J3960Z04
POL902 / POL6XX
HMI-DM
Proceed as follows to connect the Modbus module to the Modbus bus via RS485
(see also description in section for the Modbus module):
Step Action
2
3
Connect Modbus module to controller using plug connection.
Connect Modbus bus cable to Modbus module (pins + and -, Ref for
GND).
Use the T1 interface if only one master/bus should be connected.
Use the T2 interface if an additionally master/bus should be connected.
The module starts / initialization begins.
As soon as the two LEDs "BSP" and "BUS" are steady green, communication with the controller and Modbus bus is active.
Caution!
HMI must be reset a second time to update; prior to parameterization.
Proceed as follows to configure the Modbus module for Modbus RTU step by step:
Step Action
1
2
Log in to HMI using the password for level 4 (Service), default 2000.
Select Main Index > System overview > Communication > Modbus >
Module[x] Modbus > or
Main Index > System overview > Communication > Comm module
overview > Module[x] Modbus >
Note! [x] is the position of the connected communication module. This is only information used when more than one module is connected.
3
Select Settings channel [y] >
Channel 0 / Channel 1. Displays as of this point the data for the first
Modbus channel (channel 0, terminal T1) and the second Modbus channel (channel 1, terminal T2) of the module.
These are the corresponding parameters, with the exception of enable:
-
Select Enable:
Only for channel 1. Set to Active to enable channel 1 (T2).
Enter the corresponding Modbus slave address (1…247).
Enter the transmission rate as per the Modbus (2400, 4800, 9600,
19200 and 38400). All participants must have the same setting.
18 / 28
Siemens
Building Technologies
Modbus communication, slave mode CB1J3960en
01.03.2010
Configuration via operator unit,
cont.
Commission Modbus modules,
cont.
Step Action
One or two stop bits
All participants must have the same setting.
None, even or odd parity.
All participants must have the same setting.
Settings access time for master.
The master must undertake read access within this period, otherwise an alarm is triggered
The RS485 topology must always be ended using wave resistors.
They can be enabled or disabled as described in Section,2.4
When done, restart controller using this command.
After restart, the Modbus module is configured and ready to use.
As a matter of principle, the controller must be restarted with "Reset required !!" or power off/on the controller after changing any settings to assume the data.
Other setting than described above has nothing to do with Modbus RTU slave mode and should not be changed.
Siemens
Building Technologies
Modbus communication, slave mode
19 / 28
CB1J3960en
01.03.2010
Blank page
20 / 28
Siemens
Building Technologies
Modbus communication, slave mode CB1J3960en
01.03.2010
4 Integration
Modbus data formats
Leading character
Modbus registers are organized into reference types identified by the leading numeric character of the reference address:
The "x" following the leading character represents a four-digit reference address.
ModbusType Reference Description (refers to master device)
Coil Status 0xxxx Read/Write Discrete Outputs or Coils.
Input Status
A 0x reference address is used to drive output data to a digital 1-bit output channel.
1xxxx Read Discrete Inputs.
The 1-bit status of a 1x reference address is
Input Register
Holding
Register controlled by the corresponding digital input channel.
3xxxx Read Input Registers.
A 3x reference register contains a 16-bit number.
4xxxx Read/Write Output or Holding Registers.
A 4x register is used to store 16-bits of numerical data (binary or decimal), or to send the data from the CPU to an output channel.
The leading character is generally implied by the function code and omitted from the address specified for a given function. The leading character also identifies the
I/O data type.
Meaning
Siemens
Building Technologies
The functions below are used to access the registers outlined in the register map of the module for sending and receiving data.
Function
Code
Modbus function Modbus master application
(ID-COIL) slave: (0xAdr)
05
06
15
16
(ID-STATE) from slave: (1xAdr)
Holding-Register Read holding registers (16 bit
(ID-HOLD) register) from slave :(4xAdr)
(ID-INP)
Read input registers (16 bit register) from slave: (3xAdr)
Write Single Coil-Register Write one single coil register (bit register) to slave: (0xAdr)
Write Single Holding-
Register
Write multiple Coil-
Register
Write multiple Holding-
Register
Write one single holding register (16 bit register) to slave: (4xAdr)
Write multiple coil registers (bit registers) to slave: (0xAdr)
Write multiple holding registers (16 bit registers) to slave: (4xAdr)
Modbus communication, slave mode
Integration
21 / 28
CB1J3960en
01.03.2010
Register restrictions
Addresses used
Use the right document for the actual application
See actual application
4.3 Reference Modbus addresses
The internal Modbus onboard the controller has limited number of registers. Input and holding registers are limited to max 125 addresses. The Modbus communication module can handle up to 1000 addresses. In some applications are some of the reference addresses higher than 125 and it is then only possible to access them via the Modbus communication module.
All reference addresses from 0001-0125 for on-board and -1000 for module are generated and can be accessed even if not listed. As a result, multiple coils/registers can be forced/reset even if there is a gap between two reference addresses.
Do not read/write any addresses above 0125/1000. Doing so causes an exception and communication fails.
All address types starts with 1, and due to that some Master devices starts with 0 it’s in that case necessary to subtract all addresses in the reference list with 1.
The reference addresses are found in a separate document and are specific for the actual application. All different applications, and in some cases also application versions, have different reference addresses. The specific document for the actual application must be used to see what reference addresses that are used.
The actual application name and version can be found using the HMI. In some cases it is also good to check the controller BSP version.
Proceed as follows to see the actual application name and version:
On the HMI select Main Index > System overview > Application info >
Parameter Explanation / Example
Application manufacturer e.g. Siemens
Application name and version e.g. STD_AHU_vX.XX
See actual BSP version
Name
Street
City application manufacturer e.g. plant name. e.g. plant address. e.g. plant address.
Proceed as follows to see the actual controller BSP version:
Log in to HMI using the password for level 4 (Service), default 2000.
Select Main Index > System overview > Target >
Parameter
BSP version
Explanation / Example
Controller operating system.
22 / 28
Siemens
Building Technologies
Modbus communication, slave mode
Integration
CB1J3960en
01.03.2010
General
Modbus communication error
RS485 network
TCP/IP network
General things to check:
Check the actual application version and controller BSP version before call any support.
As a matter of principle, the controller must be restarted with “Reset required !!” or power off/on the controller after changing any settings to assume the data.
Non-adherence to the following rules may result in communication errors:
The slave address must be unique in the network, valid addresses are from 1-247.
Only reference addresses that are generated can be read/write, see chapter about reference addresses for more information about the specific application.
All address types starts with 1, and due to that some Master devices starts with
0 it’s in that case necessary to subtract all addresses in reference manual with 1.
Observe the following for RS485 network design and structure:
Baud rate, parity and stop bits must match network and master.
The 2-wire bus is NOT interchangeable and must be connected correctly.
In case of long distance and/or high baud rate, consider end-of-line resistors like
120 Ohms on both sides (according to RS485 rules). In Climatix this can be done via HMI.
Observe the following for TCP/IP network design and structure:
Check that the DHCP parameter is set to “Passive” if fixed IP address should be used.
Try to ping the controller if the communication is not working. If the ping fails something is wrong in the network or the IP settings.
Check that the defined TCP/UDP port is open in the firewall. For Modbus the
TCP port 502 is used.
Siemens
Building Technologies
Modbus communication, slave mode
Other information
23 / 28
CB1J3960en
01.03.2010
TCPI/UDP ports
5.2 FAQ on TCP/IP
Port number Type Used for …
Network:
Disconnected
4242 TCP TCP/IP
Ping the communication module using the IP address to test communications:
Step Action
Start > Run on the Windows start bar:
The "Run" dialog box opens.
CMD and click OK:
The "CMD.exe" DOS window opens.
3 Enter C:\>ping XXX.XXX.XXX.XXX and press Enter:
The ping result is displayed.
Note! (XXX.XXX.XXX.XXX is the set IP address)
You are dealing with a network or IP settings error if pinging does not work.
24 / 28
Siemens
Building Technologies
Modbus communication, slave mode
Other information
CB1J3960en
01.03.2010
Situation
5.3 Upgrade application or BSP via SD card
The Climatix POL6XX controller and/or the Modbus communication module
POL902 can in special cases be updated with new software.
Modbus / Ethernet
J3960Z05
SD
Prerequisite
Upgrade procedure
POL902 / POL6XX
BSP BUS
To upgrade the following items are needed:
SD card
Application- and/or BSP files from the actual manufacturer
for…
POL8196.hex
POL63x.hex
Modbus Communcation module, POL902, BSP
Controller, POL63x, BSP*
OBH.bin Controller, POL63x, Communication mappings
HMI/HMI4Web.bin Controller, HMI structure
* These files may set all settings in the controller to default!
All settings can be saved to the SD card before the upgrade and then loaded again after the upgrade.
The upgrade procedure and how to save/load all settings are not described in this manual. See basic documentation for the specific product depending of what upgrade is needed.
Siemens
Building Technologies
Modbus communication, slave mode
Other information
25 / 28
CB1J3960en
01.03.2010
Preamble
Prerequisite
Configuration via operator unit
26 / 28
Siemens
Building Technologies
5.4 Override I/Os via communication
Some inputs can be overridden via Modbus, see reference addresses. However these inputs must first be setup for this before it works. Inputs can work, only via hardware, only via communication or as a combination.
Input must first be enabled and hardware place selected in configuration.
Proceed as follows to select input handling:
Step Action
1 Log in to HMI using the password for level 4 (Service), default 2000.
Example Main Index > Unit > Inputs > Temperatures > Outside temp >
3 Select Special settings > Value selector, see selections below
Parameter Range
Value selector
(Digital inputs)
– Hardware
– Comm
– And.
– Or.
– PreferedHW
– PrefComm
Value selector
(Analog inputs)
– Hardware
– Comm
– Average
– Minimum
– Maximum.
– PreferedHW
– PrefComm
Function
Select valid input value for the application:
– Value on hardware input.
– Value from communications.
– The input is 1, if the value on the hardware input and the value from communications = 1. Alarm triggers, if one of the two values is invalid.
– The input is 1, if the value on the hardware input or the value from communications = 1. Alarm triggers, if one of the two values is invalid.
– Value on hardware input has priority. The value from communications assumed if invalid. Alarm triggers, if both values are invalid.
– Value from communications has priority. The value from hardware input assumed if invalid.
Alarm triggers, if both values are invalid.
Select valid input value for the application:
– Value on hardware input.
– Value from communications.
– Average from the values on hardware input and from communications. Alarm triggers, if one of the two values is invalid.
– Lowest value from the values on hardware input and from communications. Alarm triggers, if one of the two values is invalid.
– Highest value from the values on hardware input and from communications. Alarm triggers, if one of the two values is invalid.
– Value on hardware input has priority. The value from communications assumed if invalid. Alarm triggers, if both values are invalid.
– Value from communications has priority. The value from hardware input assumed if invalid.
Alarm triggers, if both values are invalid.
Modbus communication, slave mode
Other information
CB1J3960en
01.03.2010
Index
A
Abbreviations .......................................................... 6
Application information ......................................... 22
B
Before you start ...................................................... 5
Bus termination..................................................... 11
C
Commission instructions....................................... 13
Commission internal Modbus RTU....................... 14
Commission internal Modbus TCP ....................... 16
Commission Modbus modules ............................. 18
D
Document use......................................................... 8
Document validity ................................................... 5
Documents, other ................................................... 5
F
Function codes ..................................................... 21
I
I/Os via communication ........................................ 26
M
Map register.......................................................... 21
Modbus module mechanical design ..................... 17
Modbus protocol......................................................9
Modbus reference addresses................................22
Modbus TCP Ethernet.............................................9
Q
Quality assurance....................................................8
R
Revision history .......................................................5
RS485 cable installation........................................10
RS485 networks ....................................................10
S
Safety notes. ...........................................................7
Status displays ......................................................17
Symbols in document..............................................6
T
Target audience.......................................................5
TCP/IP FAQ...........................................................24
TCP/IP networks ...................................................11
Tools ......................................................................11
Trademarks and copyrights.....................................8
Troubleshooting, tips .............................................23
U
Upgrade via SD card .............................................25
Siemens
Building Technologies
Modbus communication, slave mode
Index
27 / 28
CB1J3960en
01.03.2010
Siemens Switzerland Ltd.
Building Technologies Group
International Headquarters
Gubelstrasse 22
CH-6301 Zug
Tel. +41 41-724 24 24
Fax +41 41-724 35 22 www.siemens.com/sbt
28 / 28
Siemens
Building Technologies
Modbus communication, slave mode
© 2010 Siemens Switzerland Ltd.
Subject to change
CB1J3960en
01.03.2010
advertisement
Key Features
- Modbus RTU/TCP communication
- Slave mode operation
- Integration with Climatix™ controllers
- Flexible configuration options
- Supports multiple communication channels
- Easy to install and configure
- Reliable and robust performance
Frequently Answers and Questions
What is the purpose of the Siemens POL6XX and POL902?
How can I configure the communication parameters for the POL6XX and POL902?
How many communication channels are available on the POL902?
What is the maximum number of Modbus addresses that can be supported by the POL6XX and POL902?
How can I upgrade the software on the POL6XX or POL902?
Related manuals
advertisement
Table of contents
- 5 About this document
- 5 Revision history
- 5 Before you start
- 5 Reference documents
- 6 Document conventions
- 7 Important information on safety
- 8 Trademarks and copyrights
- 8 Quality assurance
- 8 Document use/ request to the reader
- 9 Modbus networks
- 9 Modbus protocol
- 10 RS485 networks
- 10 RS485, cable installation
- 11 Bus termination
- 11 TCP/IP networks
- 11 Tools
- 13 Commission instructions
- 13 General
- 14 Commission internal Modbus RTU
- 16 Commission internal Modbus TCP
- 17 The Modbus module
- 18 Commission Modbus modules
- 21 Integration
- 21 Map registers
- 21 Function codes
- 22 Reference Modbus addresses
- 23 Other information
- 23 Troubleshooting, tips
- 24 FAQ on TCP/IP
- 25 Upgrade application or BSP via SD card
- 26 Override I/Os via communication
- 27 Index