User manual
Table Of Contents
- NOTE: All page numbers are hyperlinks.
- Press Ctrl + - to go back.
- 870 USE 101 00 Version 3.0
- Contents
- Overview of TSX Momentum M1 Processor Adapters
- Overview of TSX Momentum Option Adapters
- Assembling TSX Momentum Components
- Assembling a CPU
- Overview
- Assembling a Processor Adapter and I/O Base
- Disassembling a Processor Adapter from an I/O Base
- Assembling a CPU with an Option Adapter
- Overview
- Assembling a Processor Adapter and an Option Adapter
- Mounting the Assembled Adapters on the I/O Base
- Disassembling a Module with an Option Adapter
- Installing Batteries in an Option Adapter
- Installation Guidelines
- Labeling the CPU
- Guidelines for Labeling the CPU
- Using the Modbus Ports
- Modbus Port 1
- Overview
- Modbus Port 1
- Cable Accessories for Modbus Port 1
- Pinouts for Modbus Port 1
- Modbus Port 2
- Overview
- Modbus Port 2
- Four-Wire Cabling Schemes for Modbus RS485 Networks
- Two-Wire Cabling Schemes for Modbus RS485 Networks
- Cable for Modbus RS485 Networks
- Connectors for Modbus RS485 Networks
- Terminating Devices for Modbus RS485 Networks
- Pinouts for Modbus RS485 Networks
- Using the Ethernet Port
- Using the I/OBus Port
- Using the Modbus Plus Ports
- Configuring an M1 CPU with Modsoft
- Configuring the Processor Adapter
- Overview
- Selecting an M1 Processor Adapter
- Specifying an M1 Processor Type
- Default Configuration Parameters
- Changing the Range of Discrete and Register References
- Changing the Size of Your Application Logic Space
- Changing the Number of Segments
- Changing the Size of the I/O Map
- Establishing Configuration Extension Memory
- Configuring Option Adapter Features
- Overview
- Reserving and Monitoring a Battery Coil
- Setting up the Time-of-Day Clock
- Setting the Time
- Reading the Time-of-Day Clock
- Modifying Communication Port Parameters
- Overview
- Accessing the Port Editor Screen
- Parameters Which Should Not Be Changed
- Changing the Mode and Data Bits
- Changing Parity
- Changing the Baud Rate
- Changing the Modbus Address
- Changing the Delay
- Changing the Protocol on Modbus Port 2
- I/O Mapping the Local I/O Points
- Accessing and Editing the I/O Map
- I/O Mapping an I/OBus Network with Modsoft
- Configuring a Modbus Plus Network in Modsoft with Peer Cop
- Getting Started
- Overview
- Accessing the Peer Cop Configuration Extension Screen
- The Default Peer Cop Screen
- Using Modbus Plus to Handle I/O
- Overview
- Devices on the Network
- Defining the Link and Accessing a Node
- Confirming the Peer Cop Summary Information
- Specifying References for Input Data
- Accessing the Remaining Devices
- Completing the I/O Device Configuration in Peer Cop
- Passing Supervisory Data over Modbus Plus
- Overview
- Devices on the Network
- Configuring a Node to Exchange Data
- Confirming the Peer Cop Summary Information
- Specifying References for Input and Output Data
- Defining the References for the Next Node
- Defining References for the Supervisory Computer
- Completing the Configuration
- Saving to Flash in Modsoft
- Configuring an M1 CPU with Concept
- Configuring the Processor Adapter
- Overview
- Selecting an M1 Processor Adapter
- Default Configuration Parameters
- Changing the Range of Discrete and Register References
- Changing the Size of the Full Logic Area
- Understanding the Number of Segments
- Changing the Size of the I/O Map
- Establishing Configuration Extension Memory for Peer Cop
- Configuring Option Adapter Features
- Overview
- Reserving and Monitoring a Battery Coil
- Setting up the Time-of-Day Clock
- Setting the Time
- Reading the Time-of-Day Clock
- Modifying Modbus Port Parameters
- Overview
- Accessing the Modbus Port Settings Dialog Box
- Changing the Baud Rate
- Changing Mode and Data Bits
- Stop Bit Should Not Be Changed
- Changing Parity
- Changing the Delay
- Changing the Modbus Address
- Changing the Protocol on Modbus Port 2
- Configuring Ethernet Address Parameters and I/O Scanning
- Overview
- Accessing the Ethernet / I/O Scanner Screen
- Ethernet Configuration Options
- Setting Ethernet Address Parameters
- Configuring I/O
- Completing the I/O Configuration
- I/O Mapping the Local I/O Points
- Accessing and Editing the I/O Map
- I/O Mapping an I/OBus Network with Concept
- Configuring a Modbus Plus Network in Concept with Peer Cop
- Getting Started
- Overview
- Accessing the Peer Cop Dialog Box
- Adjusting the Amount of Extension Memory
- Other Default Settings in the Peer Cop Dialog Box
- Using Modbus Plus to Handle I/O
- Overview
- Devices on the Network
- Changing the Peer Cop Summary Information
- Specifying References for Input Data
- Specifying References for Output Data
- Passing Supervisory Data over Modbus Plus
- Overview
- Devices on the Network
- Specifying References for Input and Output Data
- Defining the References for the Next Node
- Defining References for the Supervisory PLC
- Saving to Flash with Concept
- Ladder Logic Elements and Instructions
- Run LED Flash Patterns and Error Codes
- Index
Using the Ethernet Port
870 USE 101 00 V.3 145
Description, Continued
Words 24, 25
Receive Buffer
Errors
Increments whenever a client attempts to connect to the M1 Ethernet, and fails,
because there is no available server path. The M1 Ethernet supports 14
simultaneous data paths and 2 program paths before this counter can increment.
This error indicates poor application architecture.
Transmission Errors
Words 26, 27
Transmit Buffer
Errors
Increments when the M1 is unable to transmit an Ethernet response frame because
all frame buffers are in use. For example, the M1 has 16 PING reply buffers. If all
16 PING buffers contain PING replies, ready to be transmitted, but this station’s
transmission is delayed because of collisions and backoff, and one more PING
request is received, then the new PING request is discarded and the counter is
incremented. This error can occur for PING, ARP, and connection attempt to server
path. Although this error is theoretically possible, it is not usually encountered.
Words 28, 29 Silo
Underflow
This field counts M1 TCP/IP retries. All M1 clients and server use the TCP/IP
protocol which implements sequence numbers and timeouts. Whenever TCP/IP
data is pushed from the M1, a subsequent acknowledgement of receipt of M1 data
must be received within the timeout period, or else the M1 issues a retry. Retries
may be the result of any of the following conditions:
● The original M1 data frame was garbled, corrupted, and lost
● The target TCP/IP stack is operating more slowly than the M1 retry rate
For Modbus 502 servers, the M1 initiates retries after (1, 1, 2, 2, 4, 8) seconds.
For Modbus 502 clients, the M1 retry rate is the larger of:
● 1/4 the health timeout for Ethernet I/O Scanner data (see
Accessing the
Ethernet / I/O Scanner Screen
on page 322,
OR:
● 4 times the previous measured TCP/IP round trip time for i/o Scanner MSTR
block.
Continued on next page