SIMATIC TI505/TI500 Modnim: User Manual
SIMATIC TI505/TI500 Modnim: User Manual
MODNIM
User Manual
01/21/92
MANUAL PUBLICATION HISTORY
SIMATIC TI505/TI500 MODNIM User Manual
Order Manual Number: PPX:505-8122-1
Refer to this history in all correspondence and/or discussion about this manual.
Cover/Copyright Original
History/Effective Pages Original
iii — ix Original
1-1 — 1-20 Original
2-1 — 2-39 Original
A-1 — A-4 Original
B-1 — B-2 Original
C-1 — C-3 Original
D-1 — D-6 Original
Index-1 — Index-3 Original
Registration Original
Contents
Preface
Chapter 1 Installation and Set-up
1.1 Modbus Communications Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Modbus Network Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Modbus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Transmission Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.2 Quick Reference Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Handling the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Inspecting the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Getting Started with Configuration and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.3 Setting the Dipswitches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Dipswitch Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Setting the Network Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Selecting Network Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Data Transmission Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Stopbit Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Parity/No Parity Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Odd/Even Parity Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
ASCII/RTU Mode Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
RTS/CTS Handshaking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Y/C Coil Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.4 Installing the MODNIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Installing the Series 505 MODNIM in the I/O Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Installing the Series 500 MODNIM in the I/O Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.5 Switches and Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Switches and Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Reset Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Test Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Local/Remote Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Status Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
1.6 Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Built-in Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Power-up Self Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Run-time Self Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
User-Initiated Self Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Contents iii
1.7 Establishing Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Verifying that the MODNIM is Logged into the PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Connecting the Network Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Recommended Communication Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Building a Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
iv Contents
Appendix A Network Cable Communications
A.1 Network Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Recommended Communication Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Building Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
A.2 Communications Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
RS-232-C Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Recommended Communications Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Appendix C Specifications
C.1 Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Contents v
List of Figures
vi Contents
Figure 2-28 Coil Bit Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Figure 2-29 Write Multiple Coils Example — Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Figure 2-30 Write Multiple Registers Example — Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Figure 2-31 Write Multiple Registers Example — Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Figure 2-32 Report Slave ID Example — Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Figure 2-33 Report Slave ID Example — Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Figure 2-34 Exception Response Frame— ASCII Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Figure 2-35 Exception Response Frame — RTU Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Contents vii
List of Tables
viii Contents
Preface
Purpose of this This manual provides the following information on the Series 505 and
Manual Series 500 MODNIM (Modbus Network Interface Module), model
numbers PPX:505–5184 and PPX:500–5184.
• Operating instructions
• MODNIM specifications
Related Manuals The following publications contain related information which supplement
this manual.
Technical If you need information that is not included in this manual, or if you have
Assistance problems using the module, contact your Siemens Industrial Automation,
Inc. distributor or sales office. If you need assistance in contacting your
distributor or sales office in the United States, call 1–800–964-4114.
Modbus Network The Modbus system is a Local Area Network (LAN) designed to work in an
Characteristics industrial environment. It is a master/slave network in which a number of
slave nodes (e.g., Programmable Logic Controllers, or PLCs) are connected
to a Master Node, which is a host computer.
Modbus Protocol The Modbus protocol determines how messages are passed between the host
computer and the secondary nodes. Up to 247 slaves can reside on a single
network. Each node in that network must have a unique address ranging
from 1 to 247.
• The Broadcast/No Response type, where all nodes are addressed but
none respond.
Transmission Two modes of data transmission are available for a given network; however,
Modes only one mode can be selected at a given time, and every node on the
network must conform to that mode. Usually, the requirements of the host
computer determine which mode should be selected. The two modes are the
following.
Modem
Modbus Network
Modem Modem
Programmable Controllers
MODNIM MODNIM
Multidrop Configuration Point-to-point
General In order to install and use the MODNIM module correctly, you must meet
Requirements the following requirements.
Procedures Figure 1-2 provides a quick reference list of the basic steps for installing the
MODNIM.
Insert module into selected I/O slot (Series 505) or two adjacent slots (Series 500).
Both the module and the person handling the module should be at the same
ground potential. Also, follow these guidelines.
• Ensure that the work area has a conductive pad with a lead connecting
it to a common ground.
Inspecting the Inspect the module for any visible damage before setting any selectable
Module features. If damage is detected, contact your distributor or sales office for
further instructions.
Getting Started The following sections describe the procedures for configuring the module,
with Configuration installing the module in the base, connecting the communications cables to
and Installation the MODNIM, and initializing the system for operation. Before installing
the MODNIM, make sure that the PLC is installed and the programming
device is connected to the system.
NOTE: The configuration and address switch settings are read only once
following a power-up or RESET. Be sure to reset the MODNIM following
any change in dipswitch settings or PLC memory configuration. In addition,
be aware that when the MODNIM is reset, no communication can occur
from the host to the module for several seconds.
Setting the Network Each node on a Modbus network must have a unique address. The range of
Address valid addresses is 1 to 247 (0000 0001 to 1111 0111). The address is set in
binary numbers using the block of 8 dipswitches.
NOTE: Addresses 0 or 248 to 255 (0000 0000 or 1111 1000 to 1111 1111) are
invalid addresses and, if selected, cause the module to go into Test mode.
1 1 1
1 2 3 4 5 6 7 8
0 0 0 0 0 0 0 1
1 2 3 4 5 6 7 8
0 0 0 1 1 0 0 1
1 2 3 4 5 6 7 8
1 1 0 0 1 0 1 1
2 2 2
4 4 4
Bit 8 8 8
Weight
16 16 16
32 32 32
64 64 64
128 128 128
0 1 0 1 0 1
Data Transmission Switches 1 through 4 are used to set the data transmission rate. All devices
Rate on the network must be configured to communicate at the same data rate.
Switch settings for each of the available data rates are shown in Figure 1-4.
Switches
Network Configuration 1 2 3 4 Baud
Dipswitches
0 0 0 0 – 50
10 0 0 0 1 – 50
9 0 0 1 0 – 75
8 0 0 1 1 – 110
7 0 1 0 0 – 150
6 0 1 0 1 – 200
5 0 1 1 0 – 300
4 0 1 1 1 – 600
3 Data 1 0 0 0 – 1200
2 Rate 1 0 0 1 – 1800
1 1 0 1 0 – 2400
1 0 1 1 – 3600
For Series 505: 0 1 1 1 0 0 – 4800
1 1 0 1 – 7200
For Series 500: 1 0 1 1 1 0 – 9600
1 1 1 1 – 19200
Stopbit Selection Switch 5 is used to select 1 or 2 stopbits. Set switch to the left for 1 stopbit,
to the right for 2 stopbits (on Series 505; for Series 500, see Figure 1-6).
Parity/No Parity Switch 6 is used to select Parity or No Parity when communicating over an
Selection RS-232-C data link. To select Parity, set switch to the left, then determine
whether you need odd or even parity and set switch 7 accordingly.
Odd/Even Parity If you selected Parity with switch 6, then you must also select either Odd or
Selection Even Parity using switch 7. This switch is active only if switch 6 is set to
Parity. Set switch to the left for Even parity, to the right for Odd parity.
ASCII/RTU Mode Switch 8 is used to select ASCII or RTU mode of transmission. Slide switch
Selection to the left for ASCII mode, to the right for RTU mode.
Y/C Coil Selection Switch 10 is used to determine whether the MODNIM collects data from the
PLC’s Discrete Output (Y) memory or the Control Relay (C) memory. Set
switch to the left for C coils, to the right for Y outputs.
MODNIM
NIM GOOD — PC GOOD —
Base power and NIM PC
PLC/MODNIM
MODNIM operating status GOOD GOOD communication
link status
XMT REC REC —
XMT — Receiving Data
Data Transmit indicator ON indicator
LINE TEST
ON LINE — TEST —
Connected to the Modbus network. Test mode status
Continuous ON indicates remote mode;
flashing indicates local mode REMOTE
LOCAL
Side View of Module,
Faceplate Up TEST
RESET
Network
Configuration
Network
PORT A
Address
Dipswitches
NIM GOOD
ONLINE
Reset
Self-Test
DIPSWITCH Settings Data Transmission Rates
Switches
1 2 3 4 Baud
1 0
Local/Remote 0 0 0 0 – 50
Y OUTPUTS 10 C COILS 0 0 0 1 – 50
RTS/CTS: ON 9 RTS/CTS: OFF 0 0 1 0 – 75
RTU MODE 8 ASCII MODE
PARITY: ODD 7 PARITY: EVEN 0 0 1 1 – 110
PARITY: OFF 6 PARITY: ON 0 1 0 0 – 150
STOPBITS: 2 5 STOPBITS: 1
1 4 0
0 1 0 1 – 200
Configuration 1 3 0 DATA 0 1 1 0 – 300
Switches 1 2 0 RATE
1 1 0 SELECT 0 1 1 1 – 600
1 0 0 0 – 1200
1 0 0 1 – 1800
1 8 1 0 1 0 – 2400
2 7
Network 4 6 1 0 1 1 – 3600
Address Network 8 5 1 1 0 0 – 4800
16 4
0
Switches Address 1 1 0 1 – 7200
32 3
64 2 1 1 1 0 – 9600
128 1
1 1 1 1 – 19200
Installing the To install the Series 505 MODNIM in the selected slot of the I/O base, follow
Series 505 MODNIM these steps.
in the I/O Base
2. Set the dipswitches, as described in Section 1.3. (See also Figure 1-8 for
example dipswitch configuration settings.)
4. Hold the top and bottom of the bezel and carefully slide the module into
the slot, pushing it all the way into the base connector. (See Figure 1-7.)
5. Ensure that the edge card connector is firmly seated in the I/O base
connector.
6. Tighten the screws at the top and bottom of the faceplate with a flat-
bladed screwdriver. (These screws also ground the module to the base.)
Figure 1-7 Installing the Series 505 MODNIM in the I/O Base
1 1 2 4 8 16 32 64 128
0
Network address is
determined by the
sum of the values of
Baud Rate selected switches.
(19200 shown)
(Address 2 shown)
Stop bits 2 or 1
Parity OFF/ON
Parity ODD/EVEN
Mode RTU/ASCII
RTS/CTS: OFF/ON
C coils/Y outputs Note: D = side of
switch to press down.
Installing the You can key the Series 500 MODNIM module to prevent another I/O module
Series 500 MODNIM from being inserted by mistake into the two slots reserved for the MODNIM
in the I/O Base module.
To do this, insert the three keys provided in the right slot of the two slots
occupied by the module so that they fit into the notches in the edge card of
the module. (See Figure 1-9.)
Figure 1-9 Keying the I/O Base Slot for the Series 500 MODNIM
3. Hold the top and bottom of the bezel and carefully slide the module into
the slot, pushing it all the way into the base connector. When the
module is fully seated in the I/O base, locking tabs will hold the module
in place. (See Figure 1-10.)
Locking tabs
Locking tabs
Figure 1-10 Installing the Series 500 MODNIM in the I/O Base
4. To remove the module, pull the tabs away from the module and slide it
out of the base, being careful not to damage the edge card.
Switches and The three switches located on the face of the module behind the access door
Buttons are Reset, Self Test, and Local/Remote, and are described in the following
paragraphs.
Reset Button The Reset button is a momentary-contact switch which initializes the
MODNIM and initiates the power-up self test. When you press Reset, all the
indicators turn on for approximately 1 second. Then, all indicators except
TEST go off for about 5 seconds. During this time, the MODNIM runs a
series of diagnostic tests to verify that the hardware components of the
module are operating properly. In addition, buffers and counters that
service the Modbus Diagnostic Functions are initialized.
If the tests have been successfully completed, only the NIM GOOD and the
PC GOOD (PC/NIM COMM GOOD) indicators will turn back on, while the
TEST indicator turns off. If, however, the TEST indicator remains on, run
the User Initiated Self-Test to determine the source of the error.
NOTE: Always press the Reset button after you change any of the
configuration dipswitches or address selection dipswitches. In addition, be
aware that when the MODNIM is reset, no communication can occur from
the host to the module for several seconds.
Test Button The Test button initiates a series of diagnostic tests when it is held down for
3 seconds after a Reset operation. Before running the diagnostic tests,
disconnect all communications cables and install loopback connectors on the
RS-232-C communications ports. These tests are described in more detail in
Section 1.6.
Local/Remote When set to Remote, this two-position toggle switch enables the MODNIM
Switch to perform write operations to PLC memory. In the Local position, the
MODNIM cannot write to the PLC.
In either position, the MODNIM can monitor PLC memory and mode of
operation. After the MODNIM is set to Online state, local or remote status
is indicated as follows.
When set to Local mode, only the Read functions 1, 2, 3, 4, 7, 11, 12, and 17
plus diagnostics function 8 can be performed. All other functions (write
operations) will be rejected with Exception Code 01.
ONLINE
XMT REC
ON RECEIVE
LINE TEST
TRANSMIT
TEST MODE
Table 1-2 shows how to interpret the status of the six indicator lights on the
faceplate of the MODNIM during normal operation. Section 1.6 describes
additional interpretations of the indicator lights during diagnostic testing.
Built-in Diagnostic The MODNIM has the following three levels of self tests available.
Tests
• Power-up Self Tests
Power-up Self Test The MODNIM executes a Power-up Self Test in the following cases.
• Immediately after you apply +5 VDC power from the I/O base as part of
initialization.
The Power-up Self Test checks the processor and performs a test of on-board
RAM and ROM. At the start of the test, all MODNIM indicators are turned
on for approximately 1 second, then all except the TEST MODE indicator go
off for about 5 seconds.
If the Power-up Self Test is successful, the NIM GOOD light turns on, and
the MODNIM attempts to establish communications with the PLC. If this is
successful, the PC GOOD (PC/NIM COMM GOOD) light turns on and the
MODNIM is ready for normal network control (see Figure 1-12).
If the Power-up Self Test fails, the TEST MODE indicator remains on and
the MODNIM will not respond to any communication attempts.
If the PLC does not respond, the PC GOOD (PC/NIM COMM GOOD)
indicator remains off, and the MODNIM will issue an exception response
with Error Code 04 (failure in associated device) to any host computer
initiating an interactive request to this MODNIM. In addition, the TEST
MODE indicator flashes at a 3-second interval, remaining on for 1 second.
Successful Communicating
1 second 5 seconds
internal tests with PLC
If any failures are detected in the ROM integrity test, the NIM GOOD
indicator light turns off and the MODNIM is forced into the failed state. In
this condition, the module goes into the Offline Mode and will not respond to
any requests. (See Figure 1-13.)
NOTE: The first time a valid request is received, the ON LINE indicator
goes on and remains on as long as everything is operating properly.
ON ON ON
LINE TEST LINE TEST LINE TEST
User-Initiated The User-Initiated Self Test performs a complete test of the MODNIM
Self Test hardware, including the communications ports. To run this test, follow the
steps listed below.
3. Press the RESET button and, at the same time, press and hold the
TEST button for about 5 seconds.
The TEST MODE indicator light turns on to signal the start of the test,
while all other indicators go off. After about six seconds, all LED indicators
will flash on and off for approximately two seconds. When the test has
finished executing, the TEST MODE indicator flashes at a rate of 2 Hz.
Table 1-3 shows how to interpret the results of the user-initiated diagnostic
test according to the status of the indicator lights on the MODNIM. The
indicators show the pass or fail status of each of the tests conducted.
Verifying that the After installing and configuring the MODNIM, you should verify that the
MODNIM is Logged module is properly logged into the PLC I/O map.
into the PLC
NOTE: The PLC I/O map is the first thing to check if the PC GOOD
(PC/NIM COMM GOOD) indicator light is off.
3. Check all the I/O points on the base that the MODNIM is installed in.
4. Look at the chart for the number corresponding to the slot occupied by
the MODNIM module. If an S or SF (Special Function) and word
memory locations (or 8 Ys) appear on this line, the module is registered
in the PLC memory. Assign a unique I/O address to the module and
execute a Write PC function. You can now begin to communicate with
the MODNIM.
If the data on the line is incorrect, first check to see if the module is
firmly seated in the I/O base and enter the command again. If you still
cannot verify the module login, contact your local Siemens Industrial
Automation, Inc. distributor.
Connecting the Network cabling should already be in place before you begin installing the
Network Cables MODNIM.
The MODNIM has two communication ports. Only one port communicates
at a time, but two are provided for cabling redundancy.
Building a Cable If you prefer to build your own 25-pin cable, refer to Appendix A for the
pinouts. Ensure that the following requirements are met.
Modbus Protocol This chapter examines the Modbus protocol for both ASCII and RTU modes
of transmission. The MODNIM-supported functions are then described in
detail, with examples of requests and responses for each function code.
The ASCII Each frame in the ASCII transmission mode begins with a colon ( : ) and
Transmission Frame ends with CR LF (Carriage Return/Line Feed), shown in Figure 2-1.
The Start Field The Start field is a colon (: = 3A hex), and marks the start of the message.
This is the first character transmitted.
The Address Field The Address field identifies the node to which this message is being sent
and is a number in the range of 1 to 247. Each node on any one network
must have a unique address. Only those nodes addressed will respond
unless the broadcast address 0 is used. In that case, each slave will read
and act on the message but not respond.
The Function Field The Function field is a 2-character (16-bit) code that determines the action
that a slave takes when receiving the message. The function codes
supported by the MODNIM are summarized in Table 2-1 and described in
more detail with examples in section 2.4.
The Data Field The Data field contains the information needed by the specified node to
perform the required operation, or the information returned by the node to
the host computer. The data is in multiple bytes, with two ASCII character
bytes representing a hexadecimal value (1 . . . 9 and A . . . F or a . . . f).
The LRC Field The Longitudinal Redundancy Checking (LRC) is the method employed by
ASCII mode to ensure that the message transmitted by the host is the same
as the one that arrives at the secondary (and vice versa). The characters are
passed to a mathematical algorithm creating a checksum of 2 characters in
length that can be duplicated at either end for comparison. The calculation
of this checksum is described in the Modbus Protocol Reference Manual.
The EOF Field The End of File (EOF) marker, CR (carriage return) indicates the end of the
data and is the point up to which the LRC is generated.
The Ready Field The Ready field, LF (line feed) indicates that the sender is now ready for
any reply. This character can be changed using Function Code 08, with
Diagnostic code 03. Unless there is a compelling reason to change this
character, it should be left as the default value (LF).
The RTU The RTU mode determines the start and finish of a message based on a time
Transmission Frame period of silence (no transmission) equivalent to the time it would take to
transmit 3.5 characters at the chosen baud rate. The RTU transmission
frame is shown in Figure 2-2.
The RTU Frame The RTU mode of transmission is more efficient than the ASCII mode as it
Fields only uses 8 bits for each field (except for the checksum) and the end of the
message is detected by timing. The body of the message (address, function
code, and data field) is the same with both modes; therefore, only the
message delineation and the checksum are discussed in the following
paragraphs.
Message The start and finish of a message is determined by timing in RTU mode.
Delineation Any time period longer than 3.5 character lengths marks the end of a
transmission. The next character after that would then mark the start of
the next message. This time period is dependent on the baud rate. Table 2-2
shows the effect of baud rate on the time delay period.
Invalid Characters The MODNIM ignores messages that contain invalid characters. Messages
and Messages containing the following errors are also ignored.
• Incorrect checksum
• Parity error
• Framing errors
• Incomplete transmission
Modbus Functions This section outlines some of the differences between Modbus and
vs. TIWAY TIWAY I network commands.
Commands
• Whereas Modbus uses Functions Codes, TIWAY I uses Primitives.
Primitives differ from Function codes in one important way: primitives
use TT-types to allow one primitive to address different types of data.
With Modbus a different function code is required for each type of data.
• With SIMATIC TI PLCs, the first address for each type of memory is
always 1. By comparison, Modbus PLCs allow 0 as the first legal
address.
8 7 6 5 4 3 2 1 1 2 3 4 5 6 7 8
For example, if you want to access 1000 coils starting at the 703rd coil, the
Function Code 01 would be as follows:
: 01 01 02 BF 03 E8 52 CR LF [ASCII mode]
01 01 02 BF 03 E8 0C E8 [RTU mode]
Address Limits Modbus imposes a buffer size limit of 256 bytes. Because of this restriction,
MODNIM requests have been limited to the following values.
The command checking will reject requests for data greater than the limits
shown above. What the checking does not do is check the request against
the available PLC memory. When a request goes beyond the memory of a
particular PLC, the command will be rejected by the PLC and the MODNIM
will notify the host computer with Exception Code 02.
Introduction In the descriptions that follow, each function starts on a separate page and
includes the TIWAY primitive sent to the secondary in square brackets. For
each function, an example of request and response is given.
NOTE: As Mode-specific data is not given, each of these examples omits the
header ( : ) and tail (CR/LF) of ASCII mode.
Code 01 — Read Code 01 enables the user to read the On/Off values of logic coils. The data
Coil Status passed with this command is the start address and the number of coils to be
read. Addressing is sequential up to the maximum memory size for a
particular PLC. The maximum number of coils that can be addressed with
one command is 2000. If more are requested, the whole command will be
rejected with an Exception code 03.
Example:
This request is asking the MODNIM to return the data from 5 coils (On/Off)
starting at the 10th coil.
The response returns in the data field a single byte (1A) which contains the
1’s or 0’s for the 5 coils, packed out with zeros for the three high bits.
1A = 0001 1010
Coil 0A (OFF)
Coil 0B (ON)
Coil 0C (OFF)
Coil 0D (ON)
Coil 0E (ON)
Packed with zeros (000)
Code 02 — Read Code 02 allows the application to read a series of discrete inputs. The
Input Status command includes the start address and the number of points to be read.
Example:
This request is for the data from 5 discrete inputs (On/Off) starting at the
10th input.
Response: 07 02 01 1A XXXX
Checksum (XXXX)
Data (1A)
Number of bytes (01)
Function code (02)
Slave address (07)
1A = 0001 1010
Input 0A (OFF)
Input 0B (ON)
Input 0C (OFF)
Input 0D (ON)
Input 0E (ON)
Packed with zeros (000)
Code 03 — Read Code 03 allows you to read the contents of holding registers in the attached
Output Registers secondary device. The data field of this command includes the start address
of the registers and the number of registers to be read.
Example:
The response has returned the number of bytes of data (06) and the values
for the requested registers; these are 032C, 0001, and 0030 respectively
(812, 1, and 48 decimal).
Example:
This request is for secondary address 7 to read and return the value stored
in input register 0008.
Checksum (XXXX)
Input register value (0020)
Number of bytes (02)
Function code (04)
Slave address (07)
The response has returned the number of bytes of data (02) and the value
0020 (32 decimal) from the requested input register (0008).
FF00 (hex) . . . . . . . ON
0000 (hex) . . . . . . . . OFF
1100 (hex) . . . . . . . . forced ON
2200 (hex) . . . . . . . . forced OFF
3300 (hex) . . . . . . . . unforced
NOTE: All other values are illegal and will result in error response 03.
Where the Broadcast address (00) is used, the MODNIM will send the
change coil command to all attached secondaries.
Example:
Code 06 — Write a Code 06 allows the contents of a holding register to be changed. Addressing
Single Register is sequential up to the maximum memory size for a particular PLC. This
function is limited to integer values contained in V-memory. The MODNIM
will also direct any broadcast address (00) to all attached secondaries.
Example:
This request to secondary 7 is asking for the value of holding register 0064
(100 decimal) to be changed to 0220 (544 decimal).
This implementation will read the first 8 coils (first 8 Ys or first 8 Cs,
depending on the position of the dipswitch) in the discrete image register in
a secondary and pack them into one data byte.
NOTE: The programmer of a non-Modbus PLC must make certain that the
application program running within the PLC will place meaningful data in
these locations. This data can reflect status information.
Example:
Request: 11 07 XXXX
Checksum (XXXX)
Function code (07)
Slave address (11)
Response: 11 07 3B XXXX
Checksum (XXXX)
Data value (3B)
Function code (07)
Slave address (11)
The response shows that 3B (hex) has been returned. If the individual bits
are examined, they indicate the status of each bit.
Coils
3B (hex)
0 0 1 1 1 0 1 1
Coil 1 (ON)
Coil 2 (ON)
Coil 3 (OFF)
Coil 4 (ON
Coil 5 (ON)
Coil 6 (ON)
Coil 7 (OFF)
Coil 8 (OFF)
Example:
This example shows a request to conduct diagnostic test 0000. This is the
loopback query, where the outgoing message field is returned unchanged.
Diagnostic Code — 00
When Function Code 08 uses diagnostic code 0000, any data passed in the
information field is returned to the host computer by the addressed
secondary node without change.
Diagnostic Code — 01
0001 | 00 00
or 0001 | FF 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0001, the information frame
can contain 0000 or FF00.
This function causes the MODNIM to clear all internal counters and
registers. If the MODNIM had been in Listen Only Mode (LOM), it will be
returned to normal operating mode at the successful conclusion of the
command. If the information frame contains FF00, the Communications
Event Log will be cleared. If any other value is passed in the information
field, the Communications Event Log will not be cleared, and no response
will be returned.
Diagnostic Code — 02
0002 | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0002, the information field
may contain any value (00 00 shown). The MODNIM returns a 16-bit word
containing diagnostic data about the attached device. The meaning of each
bit is given in Table 2-5.
Bit Description
If the bit contains a 1, then the error associated with that bit is current.
0003 | Char 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0003, the ASCII character
given in the information field is then used as the delimiter of an ASCII
mode message replacing the standard LF (line feed) character.
You also need to be aware that while the request must be sent with the
existing ‘ready’ character (default: LF), this response, and all future ones
will be returned with the new character until a RESET or a power cycle.
Diagnostic Code — 04
0004 | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0004 and any value in the
information field (00 00 shown), the secondary node will be forced into
Listen Only Mode. In this mode, while the node may be listening to the
traffic on the network, it will only react to a Function 8, diagnostic code 01
command, which returns the MODNIM to normal operation. The MODNIM
also returns to normal operating mode if the RESET button is pressed or
the power is cycled. When the MODNIM enters Listen Only Mode, the
ONLINE indicator goes off.
Diagnostic Code — 0A
000A | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 000A and any value in the
information field (00 00 shown), all diagnostic registers and counters within
the MODNIM will be cleared. This also happens when the power is cycled or
the RESET button is pressed.
Diagnostic Code — 0B
000B | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 000B and any value in the
information field (00 00 shown), the information field will return the
number of processed messages received by the MODNIM since the last
RESET or power-up. The counter will increment to a value of FFFF (65535)
and will then return to zero (0).
000C | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 000C and any value in the
information field (00 00 shown), the information field will return the
number of checksum errors detected by the MODNIM since the last RESET
or power-up. The counter will increment to a value of FFFF (65535) and will
then return to zero (0).
Diagnostic Code — 0D
000D | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 000D and any value in the
information field (00 00 shown), the information field will return the
number of exceptions detected by the MODNIM since the last RESET or
power-up. The counter will increment to a value of FFFF (65535) and will
then return to zero (0).
Diagnostic Code — 0E
000E | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 000E and any value in the
information field (00 00 shown), the information field will return the
number of messages addressed to the MODNIM since the last RESET or
power-up. The counter will increment to a value of FFFF (65535) and will
then return to zero (0).
Diagnostic Code — 0F
000F | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 000F and any value in the
information field (00 00 shown), the MODNIM will return 0000 in the
information field.
This Modbus diagnostic code has no equivalent in Series 500 or Series 505
PLCs. In this application, 0000 is always returned.
0010 | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0010 and any value in the
information field (00 00 shown), the MODNIM will return 0000 in the
information field.
This Modbus diagnostic code has no equivalent in Series 500 or Series 505
PLCs. In this application, 0000 is always returned.
Diagnostic Code — 11
0011 | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0011 and any value in the
information field (00 00 shown), the MODNIM will return 0000 in the
information field.
This Modbus diagnostic code has no equivalent in Series 500 or Series 505
PLCs. In this application, 0000 is always returned.
Diagnostic Code — 12
0012 | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0012 and any value in the
information field (00 00 shown), the information field will return the
number of character overruns detected by the MODNIM since the last
RESET or power-up. This indicates the number of times that characters
have arrived faster than the UART can store them without loss. The
counter will increment to a value of FFFF (65535) and will then return to
zero (0).
Diagnostic Code — 13
0013 | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0013 and any value in the
information field (00 00 shown), the MODNIM will return 0000 in the
information field.
This Modbus diagnostic code has no equivalent in Series 500 or Series 505
PLCs. In this application, 0000 is always returned.
0014 | 00 00
Information frame
Diagnostic code
When Function Code 08 uses diagnostic code 0014 and any value in the
information field (00 00 shown), the MODNIM will clear the character
overrun counter.
Code 11 — Get Code 11 returns a 2-byte status word and an associated 2-byte event
Comms Event counter. The status word is defined in the Modbus Protocol Reference
Counter Specification as being 0 for no command in progress and FFFF if a previous
command is in progress. The status will always be 0 in the MODNIM.
The event counter will increment to the value FFFF (65535 decimal), then
begin again from zero.
Example:
Request: 15 0B XXXX
Checksum (XXXX)
Function code 11 (0B hex)
Slave address 21 (15 hex)
In this example, secondary node 21 (15 hex) has been asked to return the
event counter and the associated status word.
The response shows that the status word is 0000 and that 323 (decimal)
events have occurred.
Example:
Request: 10 0C XXXX
Checksum (XXXX)
Function code 12 (0C hex)
Slave address (10)
The response has returned 70 bytes of data (2 status bytes + 2 event counter
bytes + 2 message counts + 64 event bytes). Only two of the event bytes are
shown; these indicate the secondary node was reset (00) and then received a
broadcast message (C0). The most recent events are returned first.
The broadcast address (00) can be used to change the same coils in all
networked programmable controllers.
Example:
This request is for the secondary node to change the values of 12 (0C hex)
coils starting at address 12 (18 decimal) to the states given by the following
bit pattern.
D C 0 8
1 1 0 1 1 1 1 0 0 0 0 0 1 0 0 0
25 24 23 22 21 20 19 18 33 32 31 30 29 28 27 26
Coil 26 (OFF)
Coil 25 (ON) Coil 18 (OFF) Coil 29 (ON)
The bit pattern indicates that coils 19, 20, 21, 22, 24, 25, and 29 are to be
changed to ON and 18, 23, 26, 27, and 28 changed to OFF.
Example:
Checksum (XXXX)
2nd register data (0201)
1st register data (000B)
Number of bytes (04)
Number of registers (0002)
Start register address (0078)
Function code 16 (10 hex)
Slave address (02)
Code 17 — Report Code 17 permits the user to get information from the slave concerning its
Slave ID type, run mode, and other device-dependent data.
Example:
Request: 03 11 XXXX
Checksum (XXXX)
Function code 17 (11 hex)
Slave address (03)
Response: 03 11 06 3C FF 01 00 0A 30 XXXX
Checksum (XXXX)
Release 3.0
Port A operational (0A)
Auxiliary power (00)
Operational mode (01)
Run light (FF = On)
Slave ID (3C = TI530C)
Number of bytes (06)
Function code 17 (11 hex)
Slave address 030)
This response indicates that 6 bytes have been returned. These bytes show
that the Slave ID is a TI530C PLC, the RUN light is On, the operational
mode is 01, auxiliary power is good, and the operational port is A. The last
byte contains the software version number (see Table 2-7).
Request:
Start Address Function Data LRC EOF Ready
07 01 00000041 AD CR LF
Response:
Start Address Function Except. Code LRC EOF Ready
07 81 02 76 CR LF
Request:
Address Function Data CRC
07 01 00000041 XXXX
Response:
Address Function Exception Code CRC
07 81 02 XXXX
In this example, the request is for secondary node 07 to return the data for
65 (41 hex) coils starting at address 00, which is an illegal address for a
SIMATIC TI PLC. The response is an exception indicated by the Function
Code 81 (01 with the high bit set), with the exception code 02 indicating that
the data address was illegal.
Recommended The following cables are available through your Siemens distributor.
Communication
Cables
Cable P/N Description Adapter at Module
2601094–8001 Standard 9-pin null modem 9-pin (F) to 25-pin (M) port adapter
VPU200–3605 Standard 25-pin null modem None required
Building Cables If you prefer to build your own 25-pin cable, ensure that the following
requirements are met to minimize the possibility of noise interference.
Cable Pinouts Figure A-1, Figure A-2, and Figure A-3 show the cable connections which
can be used for both ASCII and RTU modes of transmission.
RS-232-C Pin The modem interface is a standard Type E DTE configuration as defined in
Assignments the EIA RS-232-C standard. This interface uses a male 25-pin D-type
connector plug on the communication cable. The pin assignments are listed
in Table A-1.
Pin # Description
2 Transmit Data (TXD)
3 Receive Data (RXD)
4 Request to Send (RTS)
5 Clear to Send (CTS)
6 Data Set Ready (DSR)
7 Signal Ground
8 Receive Line Signal Detector/Data Carrier Detect (RLSD/DCD)
20 Data Terminal Ready (DTR)
Table B-1 lists the subset of SIMATIC TI Exception Codes that are mapped
to the Modbus exception codes.
Exception
Definition
Code (hex)
The Series 505 I/O subsystem is tested against some of the most stringent
standards in the world. Table C-1 lists specifications that are common to
Series 505 I/O devices.
Item Description
Table C-3 lists the TIWAY primitives that correspond to the Modbus codes.
SIMATIC TI505/TI500 MODNIM User Manual Using the MODASST Program D-1
D.1 Getting Started
Hardware You will need the following components to run this program.
Requirements
• IBM PC-compatible computer
• RS-232-C null-modem cable (the same cable as the one used from
MODNIM to Host, connected directly without modems).
To set up the hardware to use this program, find out the COM port number
you will use to communicate with the module, then follow these steps.
2. When safe to do so, power up the MODNIM and its associated PLC or
power up the TIWAY Gateway module.
Running the This program does not require any special installation to use. You may run
Program from the this program directly from the floppy disk or from a hard drive.
Floppy Disk
To run this program from the floppy disk, follow these steps.
a: Enter
modasst Enter
You will now see the start-up screen. Press Enter to continue. The program
starts your configuration setup with the screen as shown in Figure D-1.
D-2 Using the MODASST Program SIMATIC TI505/TI500 MODNIM User Manual
Running the To set up this program on your computer’s hard drive, follow these steps.
Program from the
Hard Disk 1. Insert the disk into the appropriate slot in your computer.
c: Enter
cd\ Enter
md\modasst Enter
cd\modasst Enter
copy a:*.* c:\modasst Enter
To run the program on your computer’s hard drive, at the DOS prompt type:
c: Enter
cd\modasst Enter
modasst Enter
You will now see the start-up screen. Press Enter to continue. The program
starts your configuration setup with the screen as shown in Figure D-1.
Setups Run Diags Find Module Settings Talk to Module Batch, Send from File
OK Cancel Help
SIMATIC TI505/TI500 MODNIM User Manual Using the MODASST Program D-3
D.2 Starting Program Operation
Setting the When the program begins, you will be prompted for the communications
Communication port number that you wish to use to communicate from your computer to
Port Options the MODNIM or TIWAY Gateway module.
Use the up and down arrows on your keyboard to select the communications
port from COM1 to COM4. If you don’t need to set up advanced options for
your COM port, press Enter to continue.
If you need to set up advanced options, press TAB to move the cursor from
the COM Port box to the Advanced Options box. Use the up/down arrow
keys to select the desired IRQ, then press TAB to move the cursor to the
address option. Again, select the desired option and press Enter when your
selections are complete.
Setting the After setting the communication port options, the first of seven additional
Remaining Options option windows is displayed to help you complete your configuration
settings. These set-up windows are the following.
For each of these set-up windows, use the arrow keys if you want to select a
choice other than the highlighted default, then press Enter to continue to the
next selection. You can also press TAB to move the highlight cursor to the
OK, Cancel, or Help options at the bottom of each window.
In each panel, press TAB to move from one field of the screen to the next
and the arrow keys to move the selection dots from one choice to another.
Press Enter to accept your choice and exit the screen. To exit a screen
without choosing anything or to cancel the selections made, press Esc . You
can also use a mouse to select menu options by placing the mouse cursor on
the option or selection and pressing the left mouse button. Press F1 at
any time to access Help screens.
After entering the last set-up option, the screen is empty except for the top
and bottom menus. Press ALT and one of the highlighted letters on the top
row of the screen to select the function option you want. To exit the
MODASST program, press ALT and X together.
D-4 Using the MODASST Program SIMATIC TI505/TI500 MODNIM User Manual
D.3 Using Program Options
Setup Options Figure D-2 shows the first menu and the sub-menu available after pressing
ALT S to choose the Setups option from the top menu. You can also press
F10 to access the top menu, and, since Setups is the default, press Enter .
Setups Run Diags Find Module Settings Talk to Module Batch, Send from File
Port Setup
Communications Parameters
Dip Switch Setup ❯
Cable Pin-Outs ❯
• Port Setup allows you to change the computer Com Port that you
selected when the program started.
Run Diagnostics The Run Diags option lists the MODNIM diagnostics available using
function code 08. You can select and run a diagnostic function by using the
up/down arrows and pressing Enter . This option uses the communications
parameters selected on the Setup menu item to run diagnostics.
SIMATIC TI505/TI500 MODNIM User Manual Using the MODASST Program D-5
Using Program Options (continued)
Find Module The Find Module option is available when you want to communicate with a
Settings MODNIM or TIWAY Gateway module and the communications parameters
are not known. This selection tries the various parameter combinations
until either a successful match of communications parameters is found, or
all combinations have been tried. This option then displays on the screen
the communications parameters determined and an option to choose those
as the parameters to use for module setup.
Talk to Module The Talk to Module option tries to communicate with the MODNIM or the
TIWAY Gateway module using one of the following choices.
• Prompt for Info to Send prompts for the function to send and for
each of the function fields. (These are described in Chapter 2 of the
user manual.) The function is then packaged properly and sent to the
MODNIM or TIWAY Gateway module.
Batch Send from This option will Batch Send a file to the module. It prompts for the input file
File name and for the output file name. If you do not change them, it assumes
modasst.tst as the input file name and modasst.log as the output file
name.
Verifying After using the MODASST program to verify that communications with the
Communications MODNIM or Gateway are functional and properly configured, you may still
find that network communications are not operating in your installation. In
that case, the network cabling from the MODNIM or TIWAY Gateway
module to the host computer or the host computer itself may need to be
evaluated to determine the source of the problem.
D-6 Using the MODASST Program SIMATIC TI505/TI500 MODNIM User Manual
Index
Diagnostic bits, 2-22
A
Diagnostic codes, 2-20–2-29
Address, setting network address, 1-6 Diagnostic tests
Address 0, 2-8 power-up, 1-16
run-time, 1-17
Address 1, 2-8 user-initiated, 1-18, D-2–D-6
Address field, 2-2 Dipswitches
Addressing, limits, 2-7 ASCII/RTU mode selection, 1-7
data transmission rate, 1-7
ASCII transmission mode, 1-2–1-3, 2-2–2-3 example setting, 1-11
ASCII/RTU mode selection, 1-7 handshaking selection, 1-7
location, 1-8, 1-9, 1-11
network address, 1-6
parity selection, 1-7
B Series 500, 1-9, D-2–D-6
Series 505, 1-8, D-2–D-6
Baud rate, 1-8, 1-9 stopbit selection, 1-7
Broadcast mode, 1-2, 2-3, 2-14, 2-16, 2-19, 2-31, Y output/C coil selection, 1-7
2-33, 2-35 Distributor, information, ix
Building communication cables, 1-20, A-2
E
C Environmental specifications, C-2
EOF field, 2-3
Cable connections, A-2–A-3
Error responses, 2-38–2-39
Cables
Event bytes, 2-32
building your own, 1-20, A-2
connecting, 1-20, A-2 Exception codes, B-2
ordering information, 1-20, A-2 Exception responses, 2-39
recommended, 1-20, A-2
Execute diagnostics, 2-19
Checksum, 2-5
Coil type selection (Y/C), 1-7
F
Communications parameters, 1-3, A-4
Function field, 2-2
Communications specifications, C-3
Configuring the module, 1-6–1-9, D-2–D-6
G
Connecting network cables, 1-20, D-2–D-6
Get comms event counter, 2-30
Get comms event log, 2-31
D
Data field, 2-3 H
Data transmission rate, 1-7 Handling the module, 1-5
Index-1
Handshaking Modbus commands
MODNIM to host, A-3 function code descriptions, 2-8–2-37
MODNIM to modem, A-3 protocol, 2-2–2-7
Help Modbus functions supported, 2-3
contacting distributor, 1-5 Modbus manuals, ix
distributor, sales office, ix
Modbus network characteristics, 1-2
Modbus protocol, 1-2
I ASCII transmission mode, 1-2–1-3, 2-2–2-3
RTU transmission mode, 1-2–1-3, 2-4–2-5
I/O definition chart, 1-19–1-21 Modbus vs. TIWAY, 2-6–2-7
I/O slot keys, 1-12 Modems, 1-3, D-5
Inspecting the module, 1-5 Module
handling, 1-5
Installation
inspecting, 1-5
getting started, 1-5
quick reference steps, 1-4 Module log-in verification, 1-19–1-21
Series 500 MODNIM, 1-12 Multi-drop configuration, 1-3
Series 505 MODNIM, 1-10
Invalid characters and messages, 2-5
N
Network cable, A-2–A-3
K
Network configuration, 1-7
Keying I/O base slot, 1-12 NIM Good LED, 1-16, 1-18
L O
LEDs, status indicators, 1-8, 1-9, 1-15 Offline mode, 1-17
Local/remote switch, 1-14 On Line LED, 1-15, 1-17
Loopback Operational mode, 2-36, 2-37
connectors, 1-18 Output type selection (Y/C), 1-7
diagnostics, 1-18
LRC field, 2-3
P
Parameters, communications, 1-3, A-4
M Parity selection, 1-7
Manuals, related, ix PC Good LED, 1-17, 1-18
Master node, 1-2 Pin assignments, RS-232-C, A-4
Message delineation, 2-4 Point-to-point configuration, 1-3
MODASST configuration & diagnostics Power-up test, 1-16
assistant program, D-1–D-6
Primitives, 2-6
Modbus codes vs. TIWAY primitives, C-3 TIWAY, C-3
Index-2
Switches
Q function, 1-14
Quick reference installation, 1-4 location, 1-8, 1-9
Switches and indicator lights, 1-14–1-15
R
T
Read coil status, 2-8
Read exception status, 2-17 Technical assistance, ix
Read input status, 2-10 Test mode LED, 1-15, 1-16, 1-18
V
S Verifying module log-in, 1-19–1-21
Secondary node, 1-2 Version of software, 2-36, 2-37
Self test, 1-16, 1-17, 1-18
Slave ID report, 2-36, 2-37
W
Slave node, 1-2
Software version, 2-36, 2-37 Write a single coil, 2-14
Index-3
SIMATIC is a registered trademark of Siemens AG.
MODNIM, Series 500, Series 505, 5TI, PM550, PM550C, TISOFT, and TIWAY are trademarks of Siemens Industrial Automation, Inc.
Modbus is a trademark of Modicon, Inc.
Texas Instruments and TI are registered trademarks of Texas Instruments Incorporated.
TI500, TI505, TI520, TI520C, TI530, TI530C, TI525, TI535, TI545, TI555, TI560, TI565, and TI575 are trademarks of Texas Instruments
Incorporated.
IBM is a registered trademark of International Business Machines Corporation.
UL is a registered trademark of Underwriters Laboratories.
CSA is a registered trademark of the Canadian Standards Association.
Customer Registration
We would like to know what you think about our user manuals so that we can serve you better.
How would you rate the quality of our manuals?
Would you be interested in giving us more detailed comments about our manuals?
Your Name:
Title:
Telephone Number: ( )
Company Name:
Company Address:
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
FOLD