You are on page 1of 582

FactoryLink

Version 7.5
• • • • • • • • • • • • • • • • • • • • • • • • • • •

Device Interfaces Using EDI Technology

• • • • © Copyright 2004 Tecnomatix group of companies. All rights reserved. NOTICE: The information contained in this document (and other media provided herewith) constitutes confidential information of Tecnomatix group of companies (“Tecnomatix”) and is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. Such information is not to be disclosed, used or copied by, or transferred to, any individual, corporation, company or other entity, in any form, by any means or for any purpose, without the express written permission of Tecnomatix. The information contained in this document and related media constitutes documentation relating to a software product and is being provided solely for use with such software product. The software product was provided pursuant to a separate license or other agreement and such information is subject to the restrictions and other terms and conditions of such license or other agreement. The information contained in this document and related media is subject to change without notice and does not represent a commitment and does not constitute any warranty on the part of Tecnomatix. Except for warranties, if any, set forth in the separate license or other agreement relating to the applicable software product, Tecnomatix makes no warranty, express or implied, with respect to such information or such software product. Tecnomatix, Tecnomatix Logo, FactoryLink, Knowledge Puts You In Control, Open Software Bus, and Xfactory are trademarks or registered trademarks of Tecnomatix in the United States and/or other countries. All other brand or product names are trademarks or registered trademarks of their respective holders.

Document Version: 2004-1118

Contents
Chapter 1 Device Interface Overview ........................................................................... 1
Supported Drivers ................................................................................................................. 1 Guidelines for Driver Technology Selection ........................................................................ 4

Chapter 2

External Device Interface Overview ............................................................ 7
Communications Methodology ............................................................................................ 8 Communicating with Multiple Devices .............................................................................. 10 Communicating with Multiple Protocol Modules .............................................................. 11 Device Topologies .............................................................................................................. 16 Serial Port .................................................................................................................. 16 Ethernet Board Port ................................................................................................... 17 Combination ............................................................................................................... 17 Components of a Communication Path .............................................................................. 19 Retrieving and Transferring Data ....................................................................................... 23 Triggered Read Operations ........................................................................................ 23 Unsolicited Read Operations ..................................................................................... 24 Write Operations ........................................................................................................ 25 Tag Naming Considerations for EDI .................................................................................. 26 Triggering Considerations .................................................................................................. 27 How Shared Memory Works ....................................................................................... 28 How to Avoid Filling Up Shared Memory ................................................................. 31 Configuration Considerations ............................................................................................. 33 Triggered Read Operations ........................................................................................ 33 Unsolicited Read Operations ..................................................................................... 34 Write Operations ........................................................................................................ 34 Triggering Guidelines ................................................................................................ 35 Optimization Guidelines ............................................................................................ 36 Cable Connection ............................................................................................................... 38

Chapter 3

Setting Operating System Parameters ....................................................... 39
Windows 2000 Ethernet ..................................................................................................... 39

FactoryLink Device Interfaces Using EDI Technology / iii

• • • •

Chapter 4

Setting Up Serial Communications........................................................... 41
Electrical Interface Signals ................................................................................................. RS-232 Mechanical Interface Standard Reference ............................................................. Cable Description and Diagrams ........................................................................................ Worksheet for Cable Connections ...................................................................................... Using ComWiz to Configure Ports ..................................................................................... 42 43 46 49 51

Chapter 5

Configuring Communication Paths.......................................................... 57
Identifying Protocol Types and Defining Logical Ports ..................................................... Creating the Logical Port Definitions ....................................................................... Sample External Device Definition Table Entries ..................................................... Creating Logical Station Definitions .................................................................................. Modicon Modbus Plus Logical Station Table ............................................................ Sample Logical Station Table Entries ........................................................................ Table Entries for Sample Worksheet .................................................................................. 58 58 60 61 64 69 71

Chapter 6

Reading Data from a Device ..................................................................... 73
Triggered Read Request ..................................................................................................... Unsolicited Read Request .................................................................................................. Defining the Table Type and Triggers ................................................................................ Triggered Read Request ............................................................................................. Unsolicited Read Request .......................................................................................... Combination Read Request ........................................................................................ Specifying What to Read and Where to Store It ................................................................ Read Holding or Input Register, Store in Analog Tag ............................................... Read Holding or Input Register, Store in Digital Tag ................................................ Read Holding Register, Store in Floating-Point or Long Analog Tag ....................... Read Holding Register, Store in Message Tag ........................................................... Read Coil or Input Status Register, Store in Digital Tag ........................................... Read Memory Register, Store in Analog Tag ............................................................. Read Statistics Word, Store in Analog Tag ................................................................. Read Global Data Word, Store in Analog Tag ........................................................... Sample Read Requests ....................................................................................................... Sample Triggered Read Request ................................................................................ Sample Unsolicited Read Request ............................................................................. 74 75 76 76 79 80 81 83 85 86 87 88 89 90 91 92 92 94

iv / FactoryLink Device Interfaces Using EDI Technology

Chapter 7

Writing Data to a Device............................................................................ 97
Block Write Request ........................................................................................................... 98 Exception Write Request .................................................................................................... 99 Defining the Table Type and Triggers .............................................................................. 100 Block Write Request ................................................................................................. 100 Exception Write Request .......................................................................................... 103 Combination Write Request ..................................................................................... 105 Specifying What to Write and Where to Write It ............................................................. 106 Write Analog Tag Value to Holding Register ........................................................... 108 Write Digital Tag Value to Holding Register ........................................................... 109 Set Bits in Holding Register Using Mask Write ....................................................... 111 Write Floating-Point or Long Analog Tag Value to Holding Register .................... 112 Write Message Tag Value to Holding Register ........................................................ 113 Write Digital Tag Value to Coil Register ................................................................. 114 Write Analog Tag Value to Memory Register ........................................................... 115 Write Analog Tag Value to Global Data Word ......................................................... 116 Sample Write Requests ..................................................................................................... 117 Sample Triggered Block Write Request .................................................................... 117 Sample Exception Write Request ............................................................................. 120 Sample Combination Write Request ........................................................................ 123

Chapter 8

Application Design Tips and Techniques ............................................... 127
Grouping of Data .............................................................................................................. Processing Differences in Read and Write Operations .................................................... Processing of Read Operations ............................................................................... Processing of Write Operations ............................................................................... Specifying Priority ........................................................................................................... Overtriggering .................................................................................................................. Efficient Triggering .......................................................................................................... Timed ........................................................................................................................ Cascaded .................................................................................................................. Self-Triggered .......................................................................................................... 128 130 130 131 133 133 134 134 134 136

Chapter 9

Testing and Troubleshooting................................................................... 139
EDI Flowcharts ................................................................................................................. 140 Basic Troubleshooting ............................................................................................. 141

FactoryLink Device Interfaces Using EDI Technology / v

• • • • Common Errors ....................................................................................................... Testing Your Application .......................................................................................... Verifying Proper Communications ................................................................................... Program Arguments .......................................................................................................... 142 143 144 146

Chapter 10 Messages and Codes ................................................................................ 147
Message Formats .............................................................................................................. EDI Run-Time Manager Line Format ..................................................................... Tag Message Format ............................................................................................... Messages .......................................................................................................................... EDI Messages .......................................................................................................... Start-Up Messages ................................................................................................... 148 148 149 150 150 156

Chapter 11 Allen-Bradley ........................................................................................... 157
Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... Configuring the Read/Write Control Table ...................................................................... Configuring the Read/Write Information Table .............................................................. Allen-Bradley Data Types ................................................................................................ Conversion of Data Types for Read Operations ............................................................... Digital Tags .............................................................................................................. Analog Tags ............................................................................................................. Floating-Point Tags ................................................................................................. Longana Tags ........................................................................................................... Message Tags ........................................................................................................... Conversion of Tags for Write Operations ......................................................................... Digital Tags .............................................................................................................. Analog Tags ............................................................................................................. Floating-Point Tags ................................................................................................. Longana Tags ........................................................................................................... Message Tags ........................................................................................................... Allen-Bradley Address Entries ......................................................................................... PLC-2 Addresses ...................................................................................................... PLC-3 Addresses ...................................................................................................... PLC-5 Addresses ...................................................................................................... PLC 5-250 Native Mode Addresses ......................................................................... 158 162 164 171 173 174 174 174 175 176 177 178 178 178 179 180 181 182 182 183 187 189

vi / FactoryLink Device Interfaces Using EDI Technology

Allen-Bradley Switch Setup ............................................................................................. 1770-KF2 Series B ................................................................................................... 1771-KA2 ................................................................................................................. 1771-KE ................................................................................................................... 1771-KG .................................................................................................................. 1785-KA ................................................................................................................... Run-Time Application Messages ..................................................................................... Single-Digit Codes ................................................................................................... Double-Digit Codes .................................................................................................

192 192 192 192 193 193 194 194 195

Chapter 12 General Electric ....................................................................................... 199
Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... Configuring the Read/Write Control Table ...................................................................... Configuring the Read/Write Information Table ............................................................... Run-Time Application Messages ..................................................................................... Single-Digit Codes ................................................................................................... Double-Digit Codes ................................................................................................. 199 201 203 210 213 214 216

Chapter 13 General Purpose Interface ...................................................................... 217
Application Programs ....................................................................................................... Capabilities, Limitations, and Trade-Offs ........................................................................ Capabilities .............................................................................................................. Limitations ............................................................................................................... Trade-Offs and Compromises in Design .................................................................. Accessing the Configuration Tables ................................................................................. Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... GPI Command/Response Table ........................................................................................ Command Table ....................................................................................................... Response Table ......................................................................................................... Configuring the Command/Response Control Table ....................................................... Configuring the Command/Response Information Table ................................................. Flexibility and Design of the GPI ..................................................................................... Formatting an Outgoing Message .................................................................................... Format and Sources of Information in the Outgoing Message ................................ Sample Information Table for a Command Table .................................................... 217 218 218 218 218 219 219 222 223 224 224 225 229 236 237 237 239

FactoryLink Device Interfaces Using EDI Technology / vii

• • • • Debugging Tools .............................................................................................................. Status/Debug Levels ................................................................................................. RAW VALUE ............................................................................................................ STAT_TAG ................................................................................................................ Summary of Basic Concepts ............................................................................................ GPI Functions ................................................................................................................... Principles of Operation ........................................................................................... Defining the Outgoing Message .............................................................................. Formatting the Incoming Response ......................................................................... Associating an Outgoing Message with an Incoming Response ............................. Specifying Methods to Detect an End-of-Response ................................................. Non-Printable or “Do Not Care” Characters ......................................................... Initiating a Transmission ......................................................................................... Putting the Protocol Module in Unsolicited Mode .................................................. Reporting Message Status ........................................................................................ Converting a Field’s Value ....................................................................................... Using Process Functions .................................................................................................. Associating a Digital Tag to a Bit ............................................................................ Determining the Sources of Field Values ................................................................. Modifying a Previously Defined Field ..................................................................... GPI Configuration ............................................................................................................ Configuration Example ............................................................................................ Command/Response Information Table Entries ...................................................... Defining the Outgoing Message to the GPI ............................................................. Defining Response Termination and Status Tags ..................................................... Defining the Incoming Response to the GPI ............................................................ Using Process Functions .................................................................................................. Process Functions Table .......................................................................................... Using Conversion Functions ............................................................................................ Sample Protocols .............................................................................................................. Response Protocols .................................................................................................. Command Protocols ................................................................................................ Network Response Protocols ................................................................................... Network Command Protocols .................................................................................. Run-Time Application Messages ..................................................................................... GPI Error Codes ...................................................................................................... 240 240 240 241 241 243 243 243 246 247 249 250 251 251 252 253 254 254 255 256 257 257 258 267 269 270 271 271 274 276 276 278 279 281 284 284

viii / FactoryLink Device Interfaces Using EDI Technology

Chapter 14 Modbus Plus ............................................................................................ 291
Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... Configuring the Read/Write Control Table ...................................................................... Configuring the Read/Write Information Table ............................................................... Modbus Plus Cable Diagram ............................................................................................ Run-Time Application Messages ..................................................................................... Logical Port Messages ............................................................................................ Logical Station Messages ........................................................................................ 292 293 295 301 307 308 309 310

Chapter 15 Modbus Serial .......................................................................................... 313
Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... Configuring the Read/Write Control Table ...................................................................... Configuring the Read/Write Information Table ............................................................... Run-Time Application Messages ..................................................................................... Run-Time Manager Codes ....................................................................................... In Message Tags ....................................................................................................... 313 315 316 323 327 327 329

Chapter 16 OMRON Host Link.................................................................................. 331
Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... Configuring the Read/Write Control Table ...................................................................... Configuring the Read/Write Information Table ............................................................... Technical Notes: Monitor Mode ....................................................................................... OMRON Data Types and PLC Data Areas ...................................................................... Run-Time Application Messages ..................................................................................... OMRON Error Codes .............................................................................................. 331 333 335 341 344 345 347 348

Chapter 17 Opto 22 OPTOMUX ................................................................................ 355
Configuring the Logical Station Control Table ................................................................ Accessing ................................................................................................................. Field Descriptions ................................................................................................... Configuring the Logical Station Information Table ......................................................... Accessing ................................................................................................................. Field Descriptions ................................................................................................... 355 355 355 357 357 357

FactoryLink Device Interfaces Using EDI Technology / ix

• • • • Configuring the Read/Write Control Table ...................................................................... Accessing ................................................................................................................. Field Descriptions ................................................................................................... Configuring the Read/Write Information Table ............................................................... Accessing ................................................................................................................. Field Descriptions ................................................................................................... Configuring the OPTOMUX Initialization Information Table ......................................... Accessing ................................................................................................................. Field Descriptions ................................................................................................... Technical Notes ................................................................................................................ Cable Diagrams ....................................................................................................... Read/Write Information Init Data Field Notes ........................................................ Initialization Sequence ............................................................................................. Write Operations ...................................................................................................... Read Operations ..................................................................................................... Error Messages ................................................................................................................. Opto 22 OPTOMUX Error Message Format .......................................................... EDI Error Codes ...................................................................................................... Opto 22 OPTOMUX Error Codes ........................................................................... 359 359 359 365 365 365 367 367 367 368 368 370 372 373 375 377 377 378 379

Chapter 18 Siemens CP525 ........................................................................................ 381
Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... Configuring the Read/Write Control Table ...................................................................... Configuring the Read/Write Information Table ............................................................... Siemens CP525 Switches ................................................................................................. Siemens CP525 Data Types .............................................................................................. Run-Time Application Messages ..................................................................................... 381 384 385 392 395 395 398

Chapter 19 Siemens Sinec H1 .................................................................................... 401
Siemens H1 Communications .......................................................................................... Types of Communication .......................................................................................... Defining a TSAP Pair .............................................................................................. TSAP IDs and ASCII Equivalents ............................................................................ Accessing the Siemens H1 Tables .................................................................................... Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... 401 401 403 404 405 405 409

x / FactoryLink Device Interfaces Using EDI Technology

Configuring the Read/Write Control Table ...................................................................... Configuring the Read/Write Information Table ............................................................... Logical Station Commands .............................................................................................. Activate/Deactivate Station Command .................................................................... Set Remote Parameters Command .......................................................................... Set Logical Station Variables Command ................................................................. Cable Diagrams ................................................................................................................ Thick Net Bus ........................................................................................................... Thin Net Bus ............................................................................................................ Siemens H1 Data Types .................................................................................................... Siemens H1 Adapter Display Utility (H1MPDISP) ......................................................... Run-Time Application Messages ..................................................................................... Run-Time Logical Station Command Error Codes ..................................................

413 420 429 429 430 435 440 440 441 441 445 446 448

Chapter 20 Square D Serial/Ethernet Symax ............................................................ 451
Configuring the Logical Station Control Table ................................................................ Configuring the Logical Station Information Table ......................................................... Configuring the Read/Write Control Table ...................................................................... Configuring the Read/Write Information Table .............................................................. Cable Diagram .................................................................................................................. Run-Time Application Messages ..................................................................................... SQRD8023 Messages ............................................................................................... SQRDRCOM and SQRDSCOM Messages .............................................................. SQRDRCOM, SQRDSCOM and SQRDENET Messages ........................................ 452 455 458 465 467 468 468 469 469

Chapter 21 Telemecanique ......................................................................................... 471
PLC Interface Overview ................................................................................................... Principles of Operation ........................................................................................... Configuration Tables ............................................................................................... External Device Definition Table ..................................................................................... Telemecanique Configuration Tables ............................................................................... Configuring the External Device Definition Table .................................................. Telemecanique Logical Station Table ...................................................................... Telemecanique Read/Write Table ............................................................................. System Configuration Table ............................................................................................. Reference .......................................................................................................................... Connecting to XWAY Networks ................................................................................ 471 471 473 475 477 477 477 483 490 493 493

FactoryLink Device Interfaces Using EDI Technology / xi

...................................................................................................................... Loop Indexing ............................................................................... Run-Time Application Messages .................... Error Messages ................... Accessing the Texas Instruments Tables ............................................................... Diagram A: Bit Layout for 16-bit Sequencer Word ..................................................................... Configuring the Unilink Setup Table ................. Diagram C: Sample Computations ...................................................................... DIP Switches ....................................................................... Unsolicited Data Configuration Example ............................................... Timeout .......................... LRDS..................... 517 Texas Instruments Setup ........................................................................ Diagram B: Binary Weight Tables for Bits 10-15 ........... FactoryLink and TSX/PMX PLC Data Objects ...................................................................................................... 518 518 520 521 522 523 523 526 528 531 537 543 543 552 552 553 554 554 555 555 556 556 557 559 567 xii / FactoryLink Device Interfaces Using EDI Technology ................................................................... DCP ..................................................................... Case 1: EDI Task or Protocol Module Errors .................................... Additional Parameters for TI Data Types .......................• • • • Configuring Telemecanique Networks ........................................... Case 2: TIWAY Serial Unilink Network or Point-to-Point TI PLC Errors ....................................................................................................... and LSDB .............................................................................................................. Configuring the Logical Station Control Table ....................................................................................................................... Configuring the Slaves and the TW7 Data Fields .................................................................................... 493 494 497 500 509 512 Chapter 22 Texas Instruments TIWAY................................................................... DIP Switches for TIWAY NIM .................................. Texas Instruments Message Strings ..... LRST......................................................................................................................................................................................... Network Examples ................................................................................................................................................................ Configuring the Logical Station Information Table ..................................................... Computations for 5TI Sequencer Ladder Logic Code ............................................................................................................... Configuring the Read/Write Control Table ...................................... Configuring the Read/Write Information Table ................................................................................................................. Baud Rate ................................................................................................................................................................................... LRRC.................... Decoding ER ..... Configuring Tables for Loop Indexing ..........................................

Remote Terminal Units (RTUs). so you will find the documentation for your driver in the manual with its associated driver technology. when machines are turned on/off. Virtually all industries. you can automate tasks associated with processes. easy-to-use interface into the FactoryLink Real-time Database. The following table lists the drivers that are available in FactoryLink. FactoryLink provides several technologies that work with these drivers. Rapid Application Protocol Driver (RAPD). use these devices. These technologies aid in providing a consistent. By sending messages between FactoryLink and these devices. These technologies include External Device Interface (EDI).Chapter 1 • • • Device Interface Overview FactoryLink provides a number of device drivers that allow you to communicate with remote devices that monitor and control processes. Each device uses a specific communication protocol. from the production of goods at a factory to the movement of liquid or gas down a pipeline. S UPPORTED D RIVERS FactoryLink supplies a set of protocol-specific drivers for communicating with these devices. Each protocol driver translates messages sent from FactoryLink into a format understood by the device and translates messages sent from the device to a format understood by FactoryLink. The FactoryLink documentation set is centered around these technologies. or when data like temperature or pressure is collected. such as when valves are opened/closed. These devices include Programmable Logic Controllers (PLCs). or custom devices. • FactoryLink Device Interfaces Using EDI Technology / 1 . and others. OLE for Process Control (OPC).

and 05 by remote bridging) SEMI Host Communication Standard (SECS) devices GE Devices Non-specific RAPD RSLinx v2. 2003 2000. 2003 RSLinx v2. Data Highway PLC-5/250. Highway Plus. PLC-1774 Allen-Bradley Device PLC-2. PLC-3. Quantum. PLC-4. PLC-3. PLC-5. RS232 QnA-series. PLC-5. RS232. 2003 2000 2000. optional Allen Bradley PKTC card. 05). Data Interface PLC-5/250. Ethernet Beijer QnA-series.42 FLGEM Semiconductor Interface General Electric Fanuc General Purpose Interface Mitsubishi MECOM Serial Mitsubishi MECOM Serial and Ethernet RS232. Data PLC-5/xxE. XP. XP. Quantum. and Momentum ModBus Plus EDI 2000. XP. XP. 2003 Requires PLC-2. 2003 RS232 RS232 EDI EDI Beijer 2000. XP 2 / FactoryLink Device Interfaces Using EDI Technology . RS232 PLC-5. SLC-500 (series 03. FX-series Mitsubishi A-series. PLC-5/xx Highway-485 ControlNet. XP Modbus Plus RAPD ModBus Plus RAPD 2000. XP. Highway Plus PLC-5/xxE. 2003 RSLinx v2. Plus. XP. PLC-250. PLC-5. 2003 2000.• • • • 1 | DEVICE INTERFACE OVERVIEW Supported Drivers Driver Allen-Bradley Async PLC Protocol Technology Windows OS EDI 2000. optional Allen Bradley PLC Emulation Software KTDTL 2000. Ethernet.42: optional Allen-Bradley PKTX card. PLC-5/xxE. Ethernet GW 2000. 04. SLC-500 (series 03. optional Allen Bradley Soft PLC.42: Allen-Bradley PKTX card or PKTC ControlNet card Allen-Bradley NetDTL NetDTL 2000. and Momentum Modicon 984. PLC-3. Soft 5 or 500 PLC. PLC-5/xx RS232 ControlNet. 04) PLC-2. and ControlLogix Allen-Bradley KTDTL PLC-2. PLC-3. XP. FX-series Modbus Plus Modicon 984. Data PLC-5/250. SLC-500 (series 05 ethernet) and (series 03. Ethernet. PLC 5 or 500 Emulation. XP AJ71C24 Computer Link Module (optional) AJ71C24 Computer Link Module or AJ71E71 Ethernet Interface Module (optional) SA85 or PC85 card with low-level protocol specific driver SA85 or PC85 card with low-level protocol specific driver Mitsubishi A-series. 04.

XP SECS with GW Libraries HSMS/Ethernet SECS with GW Libraries RS 232/Serial SEMI Host Communication Standard (SECS) devices SEMI Host Communication Standard (SECS) devices Ethernet GW 2000. C1000. or PC mounted PLC/PCX57 Schneider TE Load TSX-37. 2003 2000. 384. 2003 Requires Modbus TCP/IP Ethernet Ethernet RAPD 2000. and Momentum Modicon 984 (using Modicon TCP/IP MBP+ Bridge). UNI-TELWAY) Telemecanique Direct Requests 2000. C2000 Opto 22 Optomux devices Protocol RS232 Technology Windows OS EDI 2000. XP.DEVICE INTERFACE OVERVIEW | 1 Supported Drivers Driver Modbus Serial PLC Modicon 184. XP Telemecanique UNITE-XWAY Low-level drivers with special Fipway card. TSX-57. C500. 984. A350/A500 TSX-37. XP. XP. Quantum. 584. Quantum. 2003 FactoryLink Device Interfaces Using EDI Technology / 3 . C200H. 2003 2000 Telemecanique Low-level drivers with special Ethway card Schneider ETHWAY April Line Schneider KS Function Schneider Modnet 1 SFB Schneider TE COM A120/A250 A120/A250. PCX57 Custom 2000. XP 2000. XP. or PC mounted PLC/PCX57 Telemecanique UNITE-XWAY Low-level drivers with special Fipway card. TSX-57. 884. XP. XP. TSX-57. PCX57 RS232 Ethernet 2000. and Momentum C120. 2003 Omron Host Link Opto 22 Optomux RS232 RS232 Ethernet EDI EDI EDI/ Custom EDI/ Custom EDI/ Custom EDI/ Custom 2000. XP Bit Bus card Wnt-bik003Treiber with v. M84.12 Low-level driver Telemecanique UNITE-XWAY Low-level drivers with special Fipway card. 484. PCX57 Telemecanique File Transfer Custom 2000. ISAWAY FIPWAY. 2003 RS232 GW 2000. or PC mounted PLC/PCX57 Telemecanique XWAY communication protocols (XIPWAY. XP Schneider TE DRQ TSX-37.

565. 2003 2000 2000. 5TI. 545. 530T. 530T. S7 S7 S5. when proper triggering techniques are used. PM550C EDI 2000. Factors include the hardware being used or whether you have an existing or new application. 560.• • • • 1 | DEVICE INTERFACE OVERVIEW Guidelines for Driver Technology Selection Driver Siemens CP525 Siemens H1 Siemens Sinec H1 Siemens S7 Driver Siemens 3964R Square D Serial/Ethernet Symax S5. TIWAY supports TI 520C. S7 PLC Protocol RS232 Ethernet Ethernet Ethernet RS232 Technology Windows OS EDI EDI RAPD ECI RAPD 2000. • EDI is more vulnerable to problems from overtriggering than RAPD. such as serial or Ethernet. RS232 EDI SQRD RS232 SQRD Ethernet REQ DLC Protocol Stack TIWAY Serial Unilink (optional) Texas Instruments TIWAY RS232 supports TI RS232. Serial Unilink 540. However. RTU. EDI performs as well as RAPD. 2003 G UIDELINES FOR D RIVER TECHNOLOGY S ELECTION This section provides guidelines for determining whether to use an EDI or RAPD driver in your FactoryLink application. XP. 530C. TIWAY 525. XP 2000. not supported on 2003 yet Square D SY/MAX Ethernet. XP. XP. you have the option of using the ECI task rather than the IOX task. XP. 2003 2000. we suggest that you continue with the EDI technology. your selection may depend on the driver availability for the specific protocol/hardware. 525. Depending on the protocol selected to communicate with the hardware device. PM550. one of which is the ability to 4 / FactoryLink Device Interfaces Using EDI Technology . • EDI is relatively easier to configure than RAPD. 2003 2000. 2003 2000 Requires DLC Protocol only ISO TP2000 Protocol Siemens Softnet. XP. 535. The ECI task has many powerful features. • With all RAPD drivers. Use the following guidelines to determine whether to use EDI or RAPD technology: • If you are using EDI in an existing application and it works. S7 S5 S5. 530C.

you must synchronize the servers through VRN on a tag-by-tag basis.DEVICE INTERFACE OVERVIEW | 1 Guidelines for Driver Technology Selection read and write to the same tag. However. Control Net. you may wish to use ODX. Note that if you use RAPD. you must create two tags for reading/writing to the same PLC address. if you want to use Control Net. • If you will implement redundant FactoryLink servers. • If you have an existing application that works using Allen-Bradley hardware. SLC. the OPC client may be the best choice. or one of the other newer Allen-Bradley technologies. and so on using the same tables. • If you are using Modicon hardware. use: Serial – EDI driver Modbus Plus – EDI driver Ethernet – RAPD driver FactoryLink Device Interfaces Using EDI Technology / 5 . but if you are implementing redundant servers. To implement redundancy with EDI. you can communicate with serial. you must create different tables with EDI for each. we recommend using RAPD technology. continue using the same technology. In EDI. an OPC client that is actually a RAPD protocol driver. • For new applications. you may use either the RAPD or EDI driver. you must use RAPD. This allows you to use the ECI task with your RAPD protocol driver and implement mailbox marshalling through the VRN task to synchronize the servers. However. The standard OPC client works for most applications. Hardware-specific considerations include: • For most Allen-Bradley hardware devices.

• • • • 1 | DEVICE INTERFACE OVERVIEW Guidelines for Driver Technology Selection 6 / FactoryLink Device Interfaces Using EDI Technology .

This chapter introduces the concepts you need to understand so that you can configure communications between FactoryLink and a remote device.Chapter 2 • • • External Device Interface Overview The External Device Interface (EDI) task allows you to configure FactoryLink to communicate with remote devices. the movement of liquid or gas down a pipeline. such as the production of goods at a factory. Remote devices like programmable controllers and remote terminal units are used in virtually every type of industry to monitor and control processes. or when data such as temperature or pressure is collected. Each remote device uses a specific communication protocol. or the periodic collection of data. By sending messages to remote devices via the EDI task. • FactoryLink Device Interfaces Using EDI Technology / 7 . The protocol used by a device varies from one device type to another. FactoryLink must be able to translate a particular device’s protocol to ensure an accurate exchange of data with the device. when machines are turned on or off. A set of protocol-specific modules is supplied with FactoryLink to address these protocol translation needs. you can use FactoryLink to automate tasks associated with processes. such as when valves are opened or closed. therefore. Each protocol module translates messages sent from FactoryLink into a format understood by the supported device type and translates messages sent from the device to a format understood by FactoryLink.

Below and on the next page are two sequential lists and illustrations of events explaining FactoryLink’s process for retrieving and sending device data. The protocol module translates the response to a format FactoryLink understands. The protocol module sends the translated message to the device. The device processes the message.• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Communications Methodology C OMMUNICATIONS M ETHODOLOGY FactoryLink can retrieve (or read) data from a remote device and send (or write) data to a device. A protocol module translates the message to a format the device understands. EDI stores the received data as tags in FactoryLink’s real-time database. The protocol module sends the device’s translated response message to EDI. Open Closed 0 1 1 0 1 0 1 0 EDI sends a message requesting data from a remote device. The device returns a message to the protocol module containing the requested data. 8 / FactoryLink Device Interfaces Using EDI Technology .

The device performs the instruction contained in the message. A protocol module translates this message into a format the device understands. such as to open or close a valve or to start a motor. The protocol module sends the translated message to the device.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Communications Methodology A MTR SOL 1 0 1 0 1 0 EDI sends a message containing data that can be interpreted as instructions. FactoryLink Device Interfaces Using EDI Technology / 9 .

Through one communications port. FactoryLink Computer Port Port Each communications port supports one type of protocol.• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Communicating with Multiple Devices C OMMUNICATING WITH M ULTIPLE D EVICES FactoryLink communicates with multiple devices of the same or different communication protocols concurrently. FactoryLink Computer Port Using an additional port. The number of supported devices per port depends on your hardware configuration. 10 / FactoryLink Device Interfaces Using EDI Technology . Multiple Devices. This means only one protocol module can be used per port. One Protocol. FactoryLink can communicate with devices that share another communications protocol Multiple Ports. Multiple Protocols. See “Device Topologies” on page 16 for descriptions of various types of hardware configuration. FactoryLink communicates with multiple devices that share the same communications protocol One Port.

as shown by the following topology. FactoryLink Device Interfaces Using EDI Technology / 11 . EDI can provide a common interface to the real-time database for one or more instances of the same protocol module or one or more unique modules that support devices of varying manufacturers and types.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Communicating with Multiple Protocol Modules C OMMUNICATING WITH M ULTIPLE P ROTOCOL M ODULES EDI is the interface to FactoryLink and the protocol module is the interface to the device. However. Use more than one protocol module when you need to communicate with different types of devices through separate ports. A FactoryLink application requires only one EDI task running to communicate with multiple devices. as shown in the graphics “Communicating with Different Protocols” and “Communication Through Multiple Unique Protocol Modules” .

and at the same time communicating through a different port with another protocol module that controls and monitors a different process. 12 / FactoryLink Device Interfaces Using EDI Technology .• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Communicating with Multiple Protocol Modules The following graphic illustrates EDI communicating through one port with a protocol module for a group of devices that controls and monitors a particular process. The next graphic illustrates FactoryLink communicating with three devices from one port. Communicating with Different Protocols Port Port FactoryLink Computer EDI and one protocol module can communicate with devices that share the same protocol.

When you use instances of a protocol module. This type of configuration is typical in point-to-point communications. the distribution of system resources allows better throughput. thus speeding up communications. The graphic “Communication Through Multiple Instances of One Protocol Module” illustrates FactoryLink communicating with devices via three different ports. discussed in “Device Topologies” on page 16. FactoryLink Device Interfaces Using EDI Technology / 13 . EDI and multiple instances of one protocol module can communicate with devices that share the same communication protocol.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Communicating with Multiple Protocol Modules Communication Through One Protocol Module Note These examples are for network or multi-drop communications.

14 / FactoryLink Device Interfaces Using EDI Technology .• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Communicating with Multiple Protocol Modules Communication Through Multiple Instances of One Protocol Module EDI and multiple unique protocol modules can communicate with devices that support the different communication protocols. The graphic “Communication Through Multiple Unique Protocol Modules” illustrates FactoryLink communicating with the devices via three different ports.

FactoryLink can only communicate with as many devices as your hardware configuration will support.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Communicating with Multiple Protocol Modules Communication Through Multiple Unique Protocol Modules Note Regardless of the number of protocol modules in use and whether they are alike or different. FactoryLink Device Interfaces Using EDI Technology / 15 .

An interface module can be an RS232-to-RS422 external converter or a device that bridges an RS232 communications link to a proprietary network.• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Device Topologies D EVICE TOPOLOGIES The diagrams in this section illustrate some possible ways FactoryLink communicates with devices. Point-To-Point Connection FactoryLink COM Computer Port COM Port Interface Module Connection RS422 or proprietary network FactoryLink Computer COM Port RS232 16 / FactoryLink Device Interfaces Using EDI Technology . For information about communications with devices using specific protocol modules. see the “Supported Ports” table. FactoryLink can communicate with devices in two ways: directly (one point to one point) or through a network interface module. Serial Port For a serial system unit communications (COM) port connection.

The graphic below illustrates simultaneous communications with four devices: three are linked via a network through an RS232-to-RS422 converter and one device is connected directly to a COM port. FactoryLink Computer Ethernet Board Port Combination Topologies can be combined. FactoryLink Device Interfaces Using EDI Technology / 17 . and FactoryLink. The way in which you successfully combine topologies depends on a combination of limitations in hardware. system resources.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Device Topologies Ethernet Board Port FactoryLink can communicate with devices across an Ethernet network through an Ethernet adapter board.

• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Device Topologies Point-To-Point and Network Module Connection FactoryLinkCOM Computer Port COM Port RS232 RS422 The following table lists the ECS device interface protocol module base set and the ports supported by each. Supported Ports Ports Protocol Module Serial Ethernet Allen-Bradley General Electric Fanuc General Purpose Interface Modicon Modbus™ Modicon Modbus Plus™ OMRON™ Host Link Protocol Siemens CP525® Siemens Sinec H1 Square D Texas Instruments™ TIWAY/Point-to-Point ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ 18 / FactoryLink Device Interfaces Using EDI Technology .

the two components are the device and the board port to which it is connected. the number you assign to each device is called a “logical station number. FactoryLink Device Interfaces Using EDI Technology / 19 . every COM or board port on the computer through which a device communicates must be assigned a unique logical number. Two Components of a COM Port Connection FactoryLink COM Computer Port Port Device For an Ethernet board port connection.” The number you assign to each port is called a “logical port number.” Some examples of possible numbering schemas are illustrated in the next two diagrams. Two Components of an Ethernet Port Connection FactoryLink Computer Ethernet Board Port Device Port Each component and its attributes must be uniquely identified.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Components of a Communication Path C OMPONENTS OF A C OMMUNICATION P ATH The communication path to each device is identified to FactoryLink by its components. For a COM port connection. the two components are the device and the COM port to which it is connected. Every device that communicates with FactoryLink must be assigned a unique logical number.” When you begin configuring the communication path. devices are referred to interchangeably as “stations. as shown below. Likewise. For purposes of this discussion.

• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Components of a Communication Path Point-To-Point Connection Logical Port 0 FactoryLink COM Computer Port COM Port Logical Station 0 Logical Station 1 Logical Port 1 Interface Module Connection with RS-232 to RS-422 Converter Logical Port 1 FactoryLink Computer COM Port Logical Station 1 Logical Station 2 Logical Station 3 Additional schemas are illustrated in the following graphics. 20 / FactoryLink Device Interfaces Using EDI Technology .

COM2. but this correspondence is not required. a number assigned to represent a port need not correspond to the actual physical port number. For example. for example. FactoryLink Device Interfaces Using EDI Technology / 21 . can be logical port 1. In the same way. a device with a network address of 10 can be logical station 1. a logical station number assigned to represent a device can differ from the configured address for the device. Thus.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Components of a Communication Path Ethernet Connection Logical Station 1 Logical Station 2 Logical Station 3 FactoryLink Computer Ethernet Board Port Logical Port 1 Point-To-Point and Interface Module Connection Logical Station 1 Logical Port 1 FactoryLinkCOM Computer Port COM Port Logical Station 2 Logical Station 3 Logical Port 2 Logical Station 4 These arbitrary logical numbers can match physical or configurable numbers.

The logical port number you assign to represent a port can match a logical station number assigned to a device (you can have logical port 1 and logical station 1). Logical Port Numbers Tied to Logical Device Numbers First Device. Logical Port 2 is Logical Station 4 Logical Port 2 22 / FactoryLink Device Interfaces Using EDI Technology . No logical station number assigned to a device can match the station number of another device for a given protocol type. but device numbers for a given protocol type must be unique (you cannot assign logical station number 1 to two different devices). Logical Port 1 is Logical Station 1 Logical Port 1 FactoryLinkCOM Computer Port COM Port Second Device.• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Components of a Communication Path The number you assign to a device (the logical station number) is tied to the number you assign to represent the port through which communications with the device occurs (the logical port number). Logical Port 1 is Logical Station 2 Third Device. Logical Port 1 is Logical Station 3 First Device.

Selected protocol modules support unsolicited read operations. FactoryLink requests data from a device. then stored in FactoryLink as tags. First. See the “Supported Read and Write Operations” table for protocol-specific read and write information. FactoryLink Device Interfaces Using EDI Technology / 23 . FactoryLink requests data from specific locations (registers or addresses) in a device. the data is read. FactoryLink stores the data as tags in the real-time database. Next. You configure requests for read and write operations in one device protocol-specific configuration table designed for defining both types of operations.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Retrieving and Transferring Data R ETRIEVING AND TRANSFERRING D ATA EDI uses read and write operations to retrieve and transfer data between FactoryLink and devices for which a communication path is established. Triggered Read Operations In a triggered read operation. data is retrieved from a device and transferred to the real-time database. The device returns the requested data to FactoryLink. Each protocol module in the FactoryLink device interface base set supports triggered read operations and write operations.

then stores the data in the real-time database. it accepts certain types of data from specified locations in a device. • Event-Driven Read – a read request based on an event instructs FactoryLink to collect data only when a defined event occurs. Unsolicited Read Operations FactoryLink does not initiate the reading of data in an unsolicited read operation.• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Retrieving and Transferring Data EDI triggered read operations occur based on either timed intervals or events. FactoryLink recognizes the device data because its starting address and length match an identical address and expected data length configured in FactoryLink. FactoryLink ensures the incoming data matches configuration parameters. • Timed-Interval Read – a read request based on a timed interval instructs FactoryLink to collect data at defined intervals. a change in the value of a trigger tag prompts FactoryLink to read data in specific locations in a device. such as several times a minute or at a given time each day. FactoryLink stores the data in the realtime database. such as when an operator selects a new graphic window or when an alarm condition occurs. Instead. In both types of operations. 24 / FactoryLink Device Interfaces Using EDI Technology . The device sends data to FactoryLink.

FactoryLink reads the values of tags. a change in the value of a trigger tag prompts FactoryLink to write one or more tag values to specific device locations. These types of EDI write operations can occur: block and exception. data is retrieved from the real-time database and transferred to a device. The device stores the values. The difference between these operations is the way each is triggered. then writes them to specific locations in a device. The following table lists the read and write operations available for each protocol-specific module in the base set. FactoryLink reads tags and sends their values to a device. For a block write. • Exception Write – in an exception write request.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Retrieving and Transferring Data Write Operations In a write operation. Both operations write data from FactoryLink to the device when a trigger is activated. • Block Write – in a block write request. the trigger is the change in status of the tag to be written. a change in the value of a tag prompts FactoryLink to write that value to a specific device location. FactoryLink Device Interfaces Using EDI Technology / 25 . the trigger is a tag defined specifically for prompting a write operation. For an exception write.

• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Tag Naming Considerations for EDI Supported Read and Write Operations Protocol Module Read Operations Triggered Unsolicited ✔ Write Operations ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Allen-Bradley General Electric Fanuc General Purpose Interface Modicon Modbus Modicon Modbus Plus OMRON Host Link Protocol Siemens CP525 Siemens Sinec H1 Square D Texas Instruments TIWAY/Point-to-Point ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ TAG N AMING C ONSIDERATIONS FOR EDI Tag names for tags in EDI are essentially the same as in any other FactoryLink task. 26 / FactoryLink Device Interfaces Using EDI Technology . Brackets can be used. however. An array is a FactoryLink tag name assigned to a group of tags. The one difference is EDI does not recognize brackets in tag names as FactoryLink array specifiers.

depict shared memory as a mailbox. If your configuration includes more than one protocol module. Mail can go into and be retrieved from a mailbox. The diagram below. and subsequent diagrams in this section.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Triggering Considerations TRIGGERING C ONSIDERATIONS The way in which read and write operations are triggered can determine the success or failure of an application. Read and write operations use a limited area of the computer’s system memory shared by a protocol module and the EDI module. outgoing messages from EDI and incoming responses from a device are filtered through shared memory. In the same way. Shared Memory with Each Protocol Module FactoryLink Device Interfaces Using EDI Technology / 27 . The success of the application can depend on triggering rates due to the way these operations are processed. a separate area of shared memory is associated with each module.

How Shared Memory Works The diagram below shows how EDI and a protocol module use shared memory when sending commands to and receiving responses from a device. Steps 1 through 5 are defined further on the following pages. When you understand how shared memory works.• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Triggering Considerations The concept of shared memory is significant for these reasons: • Because a shared memory area is associated with each protocol module or instance of a protocol module. you can apply this knowledge and use work-around triggering schemes (these are described later on) that result in an efficiently operating application. or when the protocol module sends requested data to EDI faster than EDI can process it. This discussion focuses on how the filling up of shared memory affects triggering rates in your server application. • Because the capacity of a shared memory area is limited (like a mailbox). A shared memory area fills up when the protocol module does not process data as fast as EDI requests it. nothing more can be added to it. 28 / FactoryLink Device Interfaces Using EDI Technology . you can run multiple protocol modules simultaneously with a certain amount of independence. when the memory fills up. “Communicating with Multiple Devices” on page 10 provides details about how this works.

and response is cleared from memory EDI puts a data transfer command into shared memory. gets the command from shared memory and sends it to the device. EDI Puts Command into Shared Memory The protocol module. which constantly monitors shared memory for communications from EDI. FactoryLink Device Interfaces Using EDI Technology / 29 . writes it to FactoryLink. As EDI puts data into shared memory. This command could contain a request to read data in the device and write it to FactoryLink or to write data stored in FactoryLink to the device. sends to device. once the protocol module retrieves it. and command is cleared from memory Device returns acknowledgment and data Protocol module puts data into shared memory EDI gets data. it begins to fill up. The command and any associated data. is cleared from shared memory.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Triggering Considerations Function of Shared Memory in Read and Write Operations EDI puts command into shared memory Protocol module gets command.

• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Triggering Considerations Protocol Module Gets Command and Sends to Device If the operation is successful. acknowledgment. 30 / FactoryLink Device Interfaces Using EDI Technology . the device returns an error message. the device returns the following: • The requested data to the protocol module (if the command is for a read operation). or error message into shared memory. Device Returns Requested Data or Acknowledgment The protocol module matches the incoming data to the command and puts the requested data. If the operation is not successful. the protocol module will indicate a time-out error. • An acknowledgment that the command was received and processed (if the command is for a write operation). If the device does not respond.

EDI Gets Data. and then clears the device’s response from memory. EDI retrieves the data. Likewise. writes it to the real-time database. Writes It to FactoryLink.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Triggering Considerations Protocol Module Puts Data into Shared Memory When EDI finds a response to the data transfer command in shared memory. shared memory fills up. FactoryLink Device Interfaces Using EDI Technology / 31 . when a device sends blocks of data requested by EDI back to FactoryLink in intervals too close together. Clears Data and Command How to Avoid Filling Up Shared Memory When numerous commands for read or write operations are being sent to a device within the same time frame (as can happen when an application is configured to trigger data too frequently). shared memory fills up.

but identical tags are defined across tables to create a “self-triggering” effect. One involves daisy chaining the operations by assigning identical tag names for two types of digital tags (a trigger and a state tag) in the protocol-specific configuration table for the operation. no room is left in shared memory for other messages that might need to use the shared memory area. The other method is similar.• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Triggering Considerations Process of Retrieving and Returning Data If shared memory fills up with messages to or from a device. define read and write operations using two specific methods. 32 / FactoryLink Device Interfaces Using EDI Technology . To avoid filling up shared memory (overtriggering). See “Efficient Triggering” on page 168 for more information.

configure a table with timed reads that occur every five seconds for tags with values that change frequently. For example.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Configuration Considerations C ONFIGURATION C ONSIDERATIONS This section provides guidelines and examples to help you determine which types of read and write operations work best for specific situations and how to configure these operations to optimize FactoryLink’s performance. For example. each reading at a different interval and only as often as necessary. If a graphic screen contains a large number of variables that are only useful on that screen (that is. The tag that detects the alarm condition can trigger EDI to collect additional information from the device about the status of related processes. Event If events occur infrequently. FactoryLink Device Interfaces Using EDI Technology / 33 . and every thirty seconds for tags with values that change less frequently. you could configure FactoryLink to trigger a particular read table only if an alarm condition occurs. Using this technique can reduce traffic between FactoryLink and the device when an application has a large number of graphic screens. you can increase FactoryLink’s efficiency by configuring several read tables. each triggered by a different event. you can reduce the number of requests sent between FactoryLink and the device and increase overall efficiency by configuring several read tables. Interval If an application does not require all data to be collected at the same time. As another example of an event-driven read operation. FactoryLink will only read the tags on that screen when the operator triggers this read table by selecting the graphic screen for viewing. they are not alarm points and are not being trended). you could configure a separate read table containing only these variables. Use the following types of triggered read operations under the described circumstances. Triggered Read Operations A triggered read operation is the best choice for reading data that changes frequently and at regular intervals.

use an exception write operation. you might design an application to notify FactoryLink whenever an unexpected event occurs. a new user-entered setpoint). A block write is most efficient when your application writes a group of tags at one time to the device (for example. Block If an application writes values of tags that change frequently to the device. When defining unsolicited read operations. if supported by the protocol module. For each exception write. use a block write operation because FactoryLink sends the minimum number of write commands necessary to write the specified data. EDI sends one packet of data per tag. 34 / FactoryLink Device Interfaces Using EDI Technology .• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Configuration Considerations Unsolicited Read Operations An unsolicited read operation. is the best choice for reading values that change infrequently and at unspecified intervals. See the table “Supported Read and Write Operations” to determine whether unsolicited read operations are supported by the protocol module you are using. For example. such as an electrical unit power surge of a specified magnitude. Write Operations Use the following types of write operations under the described circumstances. See the discussion of data organization in “Optimization Guidelines” on page 36 for more information about data packets. Unsolicited reads occurring too frequently and at irregular intervals can cause excessive traffic leading to a jam on the communication link. when the application requires a new recipe). consider the frequency in which unsolicited read operations are expected to execute. Exception If an application writes values of tags that change infrequently to the device or if the application only needs to change one value at a time (for example.

• Combine Unsolicited Read Operations – if each item in a list of data is being read from a device as an unsolicited read operation. consider merging the data into a block read request. fewer data packets are required and the transmission time is quicker. You can then trigger the block read operation with an unsolicited forced write of a digital tag to the device. the timing of the events in the application. • Only Trigger When on Specific Screens – trigger data needed more often at faster rates while slowing down other requests. a separate data packet is sent for each item. FactoryLink Device Interfaces Using EDI Technology / 35 . If each item on the list is configured as an unsolicited read. however. “Efficient Triggering” provides additional details. Note See “Supported Read and Write Operations” table to determine whether the protocol module you are using supports unsolicited read operations. consider the following triggering guidelines: • Only Trigger When Data is Needed – how often you choose to trigger data to be read or written depends on several factors. including how often the data changes and whether the changes occur regularly. and the types of reads and write operations the device supports. If each list item is combined and put into a block read. The discussion of cascaded tables in Chapter 8. • Daisy Chain Tables – link or daisy chain tables together in several loops by defining tags in such a way that the completion of one task triggers the beginning of another.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Configuration Considerations Triggering Guidelines Keeping in mind the discussion of read and write configuration considerations beginning on page 33.

Refer to the device manufacturer’s documentation for device programming guidelines. Table entries are grouped according to the following criteria: logical station number. • Keep Addresses Contiguous – whenever possible. For a discussion and examples of the differences in read and write table processing. For a discussion and examples of how FactoryLink groups data being read from or written to contiguous addresses into messages. and address. In a read table. • Recognize Processing Differences in Read and Write Operations – FactoryLink processes data being read differently than it processes data being written. see “Grouping of Data” on page 128. Only the data FactoryLink is configured to store is saved. If an error occurs in table processing. see “Processing Differences in Read and Write Operations” on page 130. keep addresses contiguous to reduce the number of messages FactoryLink must generate to process a table. only the specified data is written. 36 / FactoryLink Device Interfaces Using EDI Technology . The messages FactoryLink creates are based on the results of the grouped table entries. • Program the Device for Efficiency – careful planning in the programming of the devices in your configuration can enhance the performance of your application and optimize transmission speed. you can readily identify the source of the error. • Logically Group Table Entries – FactoryLink creates messages to send to a device based on entries in a read or write table. FactoryLink actually reads the entire range of addresses — even those you do not specifically define. when you specify selected addresses of like data type to be read that are close in proximity and configure tag names for like tags in which to store the data read from these addresses. attempt to group read and write table entries the same way in which FactoryLink internally groups them. Another benefit of organizing table entries as FactoryLink does is it makes debugging your application easier. Tip “Application Design Tips and Techniques” on page 127 provides more information about some of these guidelines plus other information. For maximum efficiency. when you specify tag names for tags to be written to selected addresses. In a write table.• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Configuration Considerations Optimization Guidelines Consider the following guidelines for configuring read and write operations to make the most efficient use of EDI’s capabilities. FactoryLink data type. device data type.

separate from entries that will not be disabled. • Keep Disabled Messages Together – put entries that might need to be disabled periodically in their own table. For more information about how you can use priority queues to improve an application’s performance. EDI places each read and write table you define into a user-specified priority queue. see “Specifying Priority” on page 133. FactoryLink Device Interfaces Using EDI Technology / 37 . • Prioritize Read and Write Operations – the priority of read and write operations can affect the speed and performance of an application. EDI gives preference to high priority read and write tables if it receives more than one table at a time. Each additional table you define results in more messages the task must generate. the longer the read or write operation takes to complete. The more messages generated.EXTERNAL DEVICE INTERFACE OVERVIEW | 2 Configuration Considerations • Define Multiple Operations in a Single Table – because the EDI task can process multiple messages destined for a single device simultaneously. you can define several read or write operations (within reason and based on the architecture of the application) in a single table for maximum throughput. You can assign a high priority to the most critical data to be read or written.

because handshaking signals need to be “tied back.” This can be effectively done using a modem eliminator. 38 / FactoryLink Device Interfaces Using EDI Technology . once FactoryLink communications are attempted communications can fail. in most instances (unless a leased-line modem is being used).• • • • 2 | EXTERNAL DEVICE INTERFACE OVERVIEW Cable Connection C ABLE C ONNECTION The signals in the cable supplied with the device might differ from those required by FactoryLink. also called a null modem cable. which contains handshaking tie-backs. See “Configuring Communication Paths” on page 57 for more information about cable connections as well as serial communications reference material. Although the device might communicate with your computer without a problem using the supplied cable. This failure is.

4 Click Install. Note: Windows XP does not support the DLC Protocol. 3 Right-click Local Area Connection and select Properties..Chapter 3 • • • Setting Operating System Parameters This chapter contains information for setting up the Windows 2000 Ethernet operating system environment for FactoryLink communications. • FactoryLink Device Interfaces Using EDI Technology / 39 . 5 Select Protocol and click Add. Perform the following steps to add the DLC Protocol: 1 Open the Windows Control Panel. 6 Select DLC Protocol and click OK. W INDOWS 2000 E THERNET Setting up a Windows 2000 Ethernet environment for FactoryLink EDI communications involves adding the DLC Protocol to the network. 7 Select Close in the Local Area Connection Properties. 2 Open Network and Dial-up Connections..3 compliant. Note: The ethernet adapter used must be fully IEEE 802.

• • • • 3 | SETTING OPERATING SYSTEM PARAMETERS Windows 2000 Ethernet 40 / FactoryLink Device Interfaces Using EDI Technology .

when available. • “Cable Description and Diagrams” on page 46 includes diagrams of two common types of cabling scenarios used in device communications with FactoryLink. • FactoryLink Device Interfaces Using EDI Technology / 41 . • “RS-232 Mechanical Interface Standard Reference” on page 43 describes RS-232 standard signal names and their corresponding pin settings for 25-pin and 9-pin connectors. • “Electrical Interface Signals” on page 42 contains a table describing general information about the electrical modem interface control signals the device interface hardware and software configuration uses to establish and maintain communication.Chapter 4 • • • Setting Up Serial Communications This chapter contains reference information to help you set up serial system unit COM port communications between FactoryLink and your devices. Additional cable information. • “Using ComWiz to Configure Ports” on page 51 provides information about the different com port control signals and also gives you some hints on how to use COMWiz. • “Worksheet for Cable Connections” on page 49 provides a worksheet and sample pin-out diagrams designed to help you connect a device to a host computer’s COM port. is provided in the protocol-specific reference chapters.

it sends this signal to the DCE. Data set ready. computers. This CD signal indicating the DCE has received a signal from a remote modem is required by FactoryLink. When the DTE is powered on. and terminate a connection. When the DCE is powered on. the device must first transmit a CTS signal to FactoryLink. Data communications equipment (DCE) provides all the functions needed to establish. it sends an RTS to the data communications equipment (DCE). RTS and CTS must be tied together. data terminal equipment (DTE) is a generic term used to describe terminals. For FactoryLink communications with devices other than modems. Before data can be received or transmitted. this signal remains set high. and printers. DCE refers to the external device. DTE refers to the FactoryLink computer. CTS is a response to an RTS. it sends this signal to the DTE to indicate it is ready to transmit. Before FactoryLink can receive data from a device. If the port is open. Carrier detect (CD) is also referred to as DCD or received line signal detect (RLSD). Modem Control Signals Signal Description RTS Request to send. When the data terminal equipment (DTE) has something to transmit. When the DCE receives a signal from a remote modem. In this discussion. indicating the DTE device can begin transmitting.• • • • 4 | SETTING UP SERIAL COMMUNICATIONS Electrical Interface Signals E LECTRICAL I NTERFACE S IGNALS The following table provides general information about the electrical modem interface control signals that the device interface hardware and software configurations use to establish and maintain communication. the DCE must first set the CD signal high in the DTE. In this discussion. After the DTE sends the RTS to the DCE. Data terminal ready. Before proceeding to the table. the DCE returns a CTS to the DTE. Clear to send. it sends a CD signal to notify the DTE. CTS CD DSR DTR 42 / FactoryLink Device Interfaces Using EDI Technology . maintain.

SETTING UP SERIAL COMMUNICATIONS | 4 RS-232 Mechanical Interface Standard Reference RS-232 M ECHANICAL I NTERFACE STANDARD R EFERENCE The following tables and pin reference diagrams describe the RS-232 mechanical interface standard. Use this information to determine the correct connections for the device. DB-25 Pin Reference for RS-232 Standard. See “Electrical Interface Signals” on page 42 for descriptions of the referenced signal names. DB-25 Description Signal Name 2 3 4 5 6 7 8 20 Transmit Data Receive Data Request to Send Clear to Send Dataset Ready Signal Ground Carrier Detect Data Terminal Ready TxD RxD RTS CTS DSR SG CD DTR FactoryLink Device Interfaces Using EDI Technology / 43 .

• • • • 4 | SETTING UP SERIAL COMMUNICATIONS RS-232 Mechanical Interface Standard Reference Location of 25-Pin Signals 2 3 4 5 6 7 8 20 TxD (Transmitted Data) RxD (Received data) RTS (Request to send) CTS (Clear to send) DSR (Data set ready) SG (Signal ground) CD (Carrier detect) or RLSD (Receive line signal detector) DTR (Data terminal ready) 1 14 2 15 3 16 4 17 5 18 6 19 7 20 8 21 9 22 10 23 11 24 12 25 13 DB-9 Pin Reference for RS-232 Standard DB-9 Description Signal Name 3 2 7 8 6 5 1 4 Transmit Data Receive Data Request to Send Clear to Send Dataset Ready Signal Ground Carrier Detect Data Terminal Ready TxD RxD RTS CTS DSR SG DCD DTR 44 / FactoryLink Device Interfaces Using EDI Technology .

SETTING UP SERIAL COMMUNICATIONS | 4 RS-232 Mechanical Interface Standard Reference Location of 9-Pin Signals 1 2 3 4 5 6 7 8 9 RLSD (Receive line signal detector) or CD (Carrier detect) RxD (Received data) TxD (Transmitted data) DTR (Data terminal ready) SG (Signal ground) DSR (Data set ready) RTS (Request to send) CTS (Clear to send) Ring indicator 1 6 2 7 3 8 4 9 5 FactoryLink Device Interfaces Using EDI Technology / 45 .

and DTR must also be tied back to both connectors. Because handshaking signals are tied back.0) configuration requires that the RTS signal be tied back to the CTS signal for FactoryLink and the device connectors. The following diagram illustrates a current (before 6. RS-232 Cable to Device FactoryLink Port Shield Device TxD RxD SG RTS CTS DSR CD DTR Device-Dependent Signals TxD RxD SG RTS CTS DSR CD DTR Using COMWiz the port can be configured to not need handshaking signals.• • • • 4 | SETTING UP SERIAL COMMUNICATIONS Cable Description and Diagrams C ABLE D ESCRIPTION AND D IAGRAMS The FactoryLink connector’s TxD signal must be connected to the device connector’s RxD signal and vice versa. this cable does not rely on the device for proper signal manipulation. CD. shown in the following graphics. DSR. 46 / FactoryLink Device Interfaces Using EDI Technology .6. The current (before version 6.6. allowing the use of a standard null modem cable or a minimum 3-wire cable. if the external device supports it.0) RS-232 cable connection.

SETTING UP SERIAL COMMUNICATIONS | 4 Cable Description and Diagrams RS-232 Cable to Device (Null Modem Type) FactoryLink Port Shield Device TxD RxD SG RTS CTS DSR CD DTR TxD RxD SG RTS CTS DSR CD DTR RS-232 Cable to Device (Null Modem Type) FactoryLink Port Shield Device TxD RxD SG RTS CTS DSR CD DTR Device-Dependent Signals TxD RxD SG RTS CTS DSR CD DTR The diagram below illustrates an RS-422 cable connection between the FactoryLink computer’s serial port and a device. FactoryLink Device Interfaces Using EDI Technology / 47 . The RS-422 is an electrical rather than a mechanical interface standard and specifies no pin assignments.

RS-485 Two Wire Cable to Device FactoryLink Port Shield Device + - TxD+ TxDRxD+ RxDCOM COM 48 / FactoryLink Device Interfaces Using EDI Technology .• • • • 4 | SETTING UP SERIAL COMMUNICATIONS Cable Description and Diagrams RS-422 Cable to Device FactoryLink Port Shield Device TxD+ TxDRxD+ RxDCOM TxD+ TxDRxD+ RxDCOM The next diagram illustrates an RS-485 two-wire cable connection between FactoryLink computer’s serial port and a device. The RS-485 is an electrical rather than a mechanical interface standard and specifies no pin assignments.

and the ones shown in these examples will not necessarily match the numbers in your FactoryLink and device hardware configuration. perform the following steps: 1 Note the number of pins on the cable connectors for the FactoryLink station port and the device port.SETTING UP SERIAL COMMUNICATIONS | 4 Worksheet for Cable Connections W ORKSHEET FOR C ABLE C ONNECTIONS Use the following worksheet when establishing cable connections for the devices. Complete a worksheet for each device in the configuration. however. Pin numbers can vary. Record this information in the blanks next to FactoryLink Port and Device Port at the top of the worksheet. FactoryLink Port_____ Pin ___ ___ ___ ___ ___ ___ ___ Signal Device Port_____ Signal Pin ___ ___ ___ ___ ___ ___ ___ TxD RxD RTS CTS SG DSR DCD RxD TxD RTS CTS SG DSR DCD Note Some examples of worksheet entries are provided for your reference. FactoryLink Device Interfaces Using EDI Technology / 49 . For example. To complete the worksheet. write 25-pin next to FactoryLink Port and 9-pin next to Device Port.

For example.• • • • 4 | SETTING UP SERIAL COMMUNICATIONS Worksheet for Cable Connections 2 Record the pin numbers corresponding to the cable on the FactoryLink side of the configuration in the blanks next to the appropriate signals on the worksheet. 4 Create the cable from the resulting configuration. write 2 in the first row of the first Pin column to indicate the FactoryLink TXD is 2. 50 / FactoryLink Device Interfaces Using EDI Technology . 3 Enter the pin numbers corresponding to the cable on the device side of the configuration in the blanks next to the appropriate signals. For example. write 2 in first row of the second Pin column to indicate the device RxD is 2.

allows you to configure each serial port on your FactoryLink station. The COMPort Extended Setup dialog box. Note COMWiz was designed to allow you the freedom to configure the type of handshaking that allows you to use various cable connections and RS-422/485 ports.6. Not all of the PLCs supported by FactoryLink are this dialog box. click the Standard button on the COMPort Extended Setup and the settings for the standard cable will be restored. You must keep in mind the communication requirements for the external devices with which FactoryLink will be communicating. If at anytime during the configuration you want to change the settings back to default. the serial options that you selected are restored with it. It can be accessed by selecting the Com Port Setup in Configuration Explorer. Most of the options are described at the end of this section. Because not all external devices support all types of communication options available. or if you want to use the standard FactoryLink cable. Any changes that you make while using COMWiz are stored in your server application (FLAPP) and are saved with this application. More PLC types will be added in future releases. When your saved application file is restored.SETTING UP SERIAL COMMUNICATIONS | 4 Using ComWiz to Configure Ports U SING C OM W IZ TO C ONFIGURE P ORTS ComWiz is a utility that allows you to configure your serial communications to allow a variety of handshaking and interface options for serial communications with your external device. Expand Device Interfaces to select recommended configurations for specific PLC types. The default settings for COMWiz are for use with this cable. FactoryLink Device Interfaces Using EDI Technology / 51 . you do not need to use COMWiz. If you are converting an application that was created in a version of FactoryLink prior to 6. research and test all applications before committing to a specific setup. shown in the two graphics below. This dialog box is found at Device Interfaces > COM Port Setup.

• • • • 4 | SETTING UP SERIAL COMMUNICATIONS Using ComWiz to Configure Ports Handshaking Choices Application Directory Choices for Handshaking This button refers to pre-FactoryLink 6.0 cable configurations 52 / FactoryLink Device Interfaces Using EDI Technology .6.

the output is suspended until CTS is resent. The following table lists each COMWiz parameter. and the setup tool automatically selects the recommended port configuration for that driver. its value(s). Parameter Values Description cts_out On Off Specifies whether the clear-to-send (CTS) signal is monitored for output flow control. and describes how the parameter works. If this member is TRUE and CTS is disabled. FactoryLink Device Interfaces Using EDI Technology / 53 .SETTING UP SERIAL COMMUNICATIONS | 4 Using ComWiz to Configure Ports Selecting a Driver You can select a driver.

• • • •

4 | SETTING UP SERIAL COMMUNICATIONS Using ComWiz to Configure Ports

Parameter

Values

Description

dsr_out

On Off

Specifies whether the data-set-ready (DSR) signal is monitored for output flow control. If this member is TRUE and DSR is disabled, output is suspended until DSR is resent. Specifies whether the communications driver is sensitive to the state of the DSR signal. If the member is TRUE, the driver ignores any bytes received, unless the DSR modem input line is high. Disables the DTR line when the device is opened and leaves it disabled. Enables the DTR line when the device is opened and leaves it on. Enables DTR handshaking. Disables the RTS line when the device is opened and leaves it disabled. Enables the RTS line when the device is opened and leaves it enabled. Enables RTS handshaking. The driver raises the RTS line when the “type-ahead” (input) buffer is less than one-half full and lowers the RTS line when the buffer is more than three-quarters full. Specifies that the RTS line will be high if bytes are available for transmission. After all buffered bytes are sent, the RTS line will be low. Specifies whether to use xon/xoff flow control on output. Specifies whether to use xon/xoff flow control on output.

dsr_in

On Off

dtr_control

None Enabled Hand Shake

rts_control

None Enabled Hand Shake

Toggle

x_out x_in

On Off On Off

54 / FactoryLink Device Interfaces Using EDI Technology

SETTING UP SERIAL COMMUNICATIONS | 4 Using ComWiz to Configure Ports

Parameter

Values

Description

x_on x_off x_on_lim x_off_lim

Numeric value (decimal) of character to send for XON. Typical is 17 (decimal). Numeric value (decimal) of character to send for XOFF. Typical is 19 (decimal). Specifies the minimum number of bytes allowed in the input buffer before the XON character is sent. Specifies the maximum number of bytes allowed in the input buffer before the XOFF character is sent. The maximum number of bytes allowed is calculated by subtracting this value from the size, in bytes, of the input buffer. Typical settings are x_off when the buffer is 75% full and x_on when the buffer is 25% empty.

FactoryLink Device Interfaces Using EDI Technology / 55

• • • •

4 | SETTING UP SERIAL COMMUNICATIONS Using ComWiz to Configure Ports

56 / FactoryLink Device Interfaces Using EDI Technology

Chapter 5

Configuring Communication Paths
Once each device is connected properly and communicating with the computer running FactoryLink, you are ready to establish the paths (or routes) over which FactoryLink will communicate with the devices. This chapter describes how to establish these communication paths by configuring these tables: External Device Definition and Logical Station. • On the External Device Definition table, you identify your device to the FactoryLink system and define each logical port in your configuration. For a description of the steps involved in filling out the External Device Definition table, see “Identifying Protocol Types and Defining Logical Ports” on page 58. • On the protocol-specific Logical Station table, you define the paths to be used for communications between the devices and FactoryLink. For a description of the steps involved in filling out the Logical Station table, see “Creating Logical Station Definitions” on page 61.

FactoryLink Device Interfaces Using EDI Technology / 57

• • • •

5 | CONFIGURING COMMUNICATION PATHS Identifying Protocol Types and Defining Logical Ports

I DENTIFYING P ROTOCOL TYPES

AND

D EFINING L OGICAL P ORTS

You configure FactoryLink to recognize the protocol module and each logical port through which communications will occur by completing the External Device Definition table, found at Device Interfaces > External Device Definition. For FactoryLink to recognize the protocol module, you specify a protocol-specific identifier. For FactoryLink to recognize each physical port that is part of the system configuration, you create a logical definition for each port. To identify the protocol and define the logical ports, perform the following steps: If your FactoryLink application will communicate with devices via several different ports, complete the Logical Station Worksheet.
Note

This worksheet can be used with any protocol module in the FactoryLink 7.5 base set. It can be especially helpful, however, in documenting numbering schemes for hardware configurations that not only include multiple ports but that also use one or more network interface modules to route communications to devices across a proprietary network. Allen-Bradley and Square D are examples of protocol modules that provide this type of support. A sample worksheet is provided in which the Allen-Bradley protocol module is used as an example. Create the logical port definitions for each physical port. See “Creating the Logical Port Definitions” on page 58 for details. Creating the Logical Port Definitions The following steps describe the procedure for creating a logical port definition for each port that is part of the system configuration. 1 Ensure the current domain selection is Shared in the Configuration Explorer 2 Choose External Device Definition. The External Device Definition table is displayed. Using the field descriptions provided below, complete a row in the table for each port to which a device in the configuration is connected. Sample entries are provided in “Sample External Device Definition Table Entries” on page 60.

58 / FactoryLink Device Interfaces Using EDI Technology

CONFIGURING COMMUNICATION PATHS | 5 Identifying Protocol Types and Defining Logical Ports

Logical Port

Enter a unique number to logically represent each port to which a device is connected.
Valid Entry: 0 - 999

Physical Port

For each logical port number, enter a number referencing the physical port to which the device is connected.
Valid Entry: 0 - 32

Serial Ports – for each logical port, enter the number matching the physical port to which the device is connected. Be sure to enter an appropriate number for your hardware configuration. If the system unit does not contain an expansion card, not all valid port number entries can be used.
Device Name

For each logical port, enter the protocol-specific acronym that identifies the protocol module communicating through the port. Entry Definition AB Allen-Bradley GENE General Electric ASYN General Purpose Interface MODP Modbus Plus MBUS Modicon Modbus OMRN OMRON Host Link SIEM Siemens CP525 H1MP Siemens H1 SQRD Square D TI Texas Instruments TIWAY

Function

For each logical port, identify the type of communications. For the protocol modules in the FactoryLink 7.5 base set, specify SYSCOM for serial communications or ETHERNET for Ethernet communications, if supported for the protocol module.
Valid Entry: Ctrl+K

Comment

Optionally, enter descriptive information about this logical port.
Valid Entry: alphanumeric string of up to 14 characters

FactoryLink Device Interfaces Using EDI Technology / 59

• • • •

5 | CONFIGURING COMMUNICATION PATHS Identifying Protocol Types and Defining Logical Ports

When each logical port is defined, click the Save icon to validate the information. Create logical station definitions for each logical port. These define the paths to be used for communications between each device and FactoryLink. For details, see “Creating Logical Station Definitions” on page 61. Sample External Device Definition Table Entries A completed table for two COM ports might resemble the sample table below.
Logical Port 0
FactoryLink COM Computer Port COM Port

Logical Port 1 This sample table configures two instances of the Allen-Bradley protocol module communicating via two system unit COM ports in a Windows operating environment. Logical port 0 identifies COM1 and Logical port 1 identifies COM2.

60 / FactoryLink Device Interfaces Using EDI Technology

CONFIGURING COMMUNICATION PATHS | 5 Creating Logical Station Definitions

C REATING L OGICAL S TATION D EFINITIONS
To create logical station definitions, you associate the logical ports defined in the External Device Definition table with the actual physical stations (the devices) to communicate with FactoryLink. This association defines and initializes the routes over which data will travel between the devices and the interface software. The logical station definitions identify sources and destinations for the read and write requests you will configure later in read and write tables, and can include FactoryLink tags to which system messages from the EDI task and the device protocol module will be written. The Logical Station table, where you create these definitions, consists of two tables, Logical Station Control and Logical Station Information.
Note

To show the correspondence between the External Device Definition table and the Logical Station table and how the entries you make in these tables create the logical station definitions, the Modicon Modbus Plus protocol module is used as an example. The following steps describe how to create logical station definitions for each logical port that communicates with a device. 1 Ensure the current domain selection is Shared in the Configuration Explorer. 2 Choose the option for the protocol module you are configuring. 3 Display the Logical Station Control table by clicking on its title bar in the display of all tables. 4 On the Logical Station Control table, you define pertinent information about each communication path to a device so FactoryLink can establish communications with all the devices. This information varies from one protocol module to another. In general, however, a definition for a communication path can include (but is not limited to) the following information: • The logical port number, to create the association with the External Device Definition table

FactoryLink Device Interfaces Using EDI Technology / 61

• • • •

5 | CONFIGURING COMMUNICATION PATHS Creating Logical Station Definitions

• For the port represented by the logical port number, communication protocols (such as baud rate and parity) that match protocols defined in the device • The amount of time the protocol module communicating through the port will wait to receive a device response to a read or write request before timing out • A particular communication mode, internal data path specified on a proprietary network card, or other needed protocol-specific parameter for the port • Message tags to which values can be written to indicate communications errors associated with the port 5 See your completed logical station worksheet to help you identify logical ports and associate them with logical stations. The table below lists references to instructions for creating the logical station definitions for each protocol-specific module in the base set. To create the definitions for the protocol module your devices will communicate with, go to the specified page in the appropriate reference.
Note

Before going to the section describing the Logical Station table entries for the protocol module you are configuring, you may want to first review the procedure for creating logical station definitions for Modbus Plus in “Modicon Modbus Plus Logical Station Table” on page 64. The information in the sections describing the table entries for the other protocol modules is presented in a reference format and will not necessarily show the associations and results of the entries as the information in this section does.

62 / FactoryLink Device Interfaces Using EDI Technology

CONFIGURING COMMUNICATION PATHS | 5 Creating Logical Station Definitions

Protocol Module

Go To

Allen-Bradley General ElectricFanuc General Purpose Interface Modicon Modbus Modicon Modbus Plus

“Configuring the Logical Station Control Table” on page 158 “Configuring the Logical Station Control Table” on page 199 “Configuring the Logical Station Control Table” on page 219 “Configuring the Logical Station Control Table” on page 313 “Configuring the Logical Station Control Table” on page 292

OMRON™ Host Link Protocol “Configuring the Logical Station Control Table” on page 331 Siemens CP525 Siemens Sinec H1 Square D Texas Instruments TIWAY/Point-to-Point “Configuring the Logical Station Control Table” on page 381 “Configuring the Logical Station Control Table” on page 405 “Configuring the Logical Station Control Table” on page 452 Before completing the Logical Station table, you must complete the Unilink Setup table. For details, see “Configuring the Unilink Setup Table” on page 523. Once the Unilink Setup table is completed, see “Configuring the Logical Station Control Table” on page 526.

6 When the Logical Station Control table is complete, click the Save icon to validate the data. The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink.

FactoryLink Device Interfaces Using EDI Technology / 63

• • • •

5 | CONFIGURING COMMUNICATION PATHS Creating Logical Station Definitions

7 For each tag name, choose the type of data to be stored in the tag for Type and accept the default of Shared for domain. See the tag’s field description for the valid data types. 8 Select the row for the logical port you are configuring. Then display the Logical Station Information table. The logical port number displays in the Logical Port field. On the Logical Station Information table, you define logical station numbers which identify the address and device type for each device in the configuration and long analog tags to which error codes for particular devices (logical stations) will be written. For some protocol modules, the Logical Station Information table requires other entries, such as limits or additional device-specific addressing information. 9 Complete a row in the table for each device to communicate through this logical port. 10 Click the Save icon to validate the data. The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink. 11 For each tag name, choose the type of data to be stored in the tag for Type and accept the default of Shared for domain. See the tag’s field description for the valid data types. 12 To configure another logical port, return to the Logical Station Control table and repeat the appropriate steps. 13 When you are ready to define the read and write operations expected to occur between this logical port and the associated Modbus Plus devices configured as logical stations, see “Reading Data from a Device” on page 73 or “Writing Data to a Device” on page 97. Modicon Modbus Plus Logical Station Table The following steps describe the procedure for completing the Modicon Modbus Plus Logical Station table. 1 Using the following field descriptions, complete a row in the Logical Station Control table for each logical port defined in the External Device Definition table you want to

64 / FactoryLink Device Interfaces Using EDI Technology

SYS file. In a Windows environment. The Logical Station Control table logical port definition links with the EDI port definition to further define communication parameters. 1 LPORT Status Message Tag Optionally. defined in the External Device Definition table Logical Port field.CONFIGURING COMMUNICATION PATHS | 5 Creating Logical Station Definitions include in the communication path. the Adapter Number entry must match the /n parameter of the line for the SA85 device assignment (MBHOST. Adapter Number Enter either 0 or 1 to logically represent the SA85 host adapter. to represent a particular communication path to a Modbus Plus device. Logical Port Enter a number. The default is 0. enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. Valid Entry: previously defined logical port number The External Device Definition table logical port definition identifies the port to EDI as a designated Modbus Plus port. Valid Entry: tag name Valid Data Type: message Data Master Paths Enter a number from 1 to 8 to represent the number of communications channels to be used for command/response transactions between the SA85 card and the Modbus Plus device this FactoryLink Device Interfaces Using EDI Technology / 65 . Valid Entry: 0. Sample entries are provided in “Sample Logical Station Table Entries” on page 69.SYS for Windows) in the CONFIG.

. DS8 Define each data slave (DS) path to this logical port over which unsolicited data can be transmitted from a device to FactoryLink. Data master paths provide avenues for getting data back and forth between FactoryLink and Modicon devices. 6 On the Logical Station Information table. to define six data slave paths. logical station numbers that identify the device address. Be sure the number of slave paths you define does not conflict with paths defined for other software using the card. 5 Display the Logical Station Information table. you define the following information: • Long analog tags to which error codes for particular devices (logical stations) will be written • For each logical port.• • • • 5 | CONFIGURING COMMUNICATION PATHS Creating Logical Station Definitions logical port represents. DS2. .8 (default = 3) DS1.. When multiple channels are open to a single device. Valid Entry: numeric value from 1 . and the device type for each device in the configuration 66 / FactoryLink Device Interfaces Using EDI Technology . Each additional path you define increases the throughput of messages to and from a device. choose MESSAGE for Type and accept the default of Shared for domain. For instance. The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink. 4 Select the row for the logical port you are configuring. For more information about data slave paths. refer to the Modicon Modbus Plus Network Programming Guide. click the Save icon to validate the data. Valid Entry: yes. the transactions required for a read or write operation can occur simultaneously over several paths rather than one at a time as they would over only one path. Be sure the number of master paths you define does not conflict with paths defined for other software (such as the device programming software) using the card. 3 For each tag name. network router address. specify YES in six DSn fields. no (default = no) 2 When the Logical Station Control table is complete.

Valid Entry: numeric value from 0 . This address must match the configured address of the equipment. Valid Entry: unique numeric value from 0 .64 (default = 0) Define the Modbus Plus network address of each router or bridge to a logical station. A130. Valid Entry: Ctrl+K (default = 984) Physical Station Router1.999 (default = 0) PLC Type Define the type of Modbus Plus device to which communications are to be directed: 984 or 984BITWRITE for devices that support the mask write function (A120. A141. 685E.. the amount of time FactoryLink will wait before retrying a transmission attempt. and VM4). Valid Entry: tag name Valid Data Type: analog Logical Station (Decimal) Enter a number to identify the logical station to which the information in this row pertains. and tag names for tags reporting the success or failure of these attempts 7 Using the following field descriptions. LSTA Status Analog Tag Optionally..64 (default = 0) FactoryLink Device Interfaces Using EDI Technology / 67 . You will later enter this logical station number in a read or write table to represent the device defined in this row. A145. complete a row in the table for each device to communicate through this logical port. Assign a unique number to each device communicating through this logical port. Valid Entry: numeric value from 0 . enter a tag name for an analog tag to receive communication error codes associated with this device (logical station). A logical station represents the combination of a logical port with a physical station. AT4. Router4 Enter the physical address of the Modbus Plus device. this number will identify the device to or from which data is to be sent or received. In a read or write table. Up to four routers can be defined for each physical station. This number must be unique among all Modicon devices across all ports.CONFIGURING COMMUNICATION PATHS | 5 Creating Logical Station Definitions • The number of consecutive times FactoryLink will send a read or write command to a logical station after an unsuccessful transmission attempt. 785E.

This tag works in conjunction with the LSTA Failure Digital Tag field to display a meaningful error message for the operator on the Alarm Supervisor screen.01 sec Enter a number between 1 and 300 that defines the length of time. The timeout occurs after each retry of the transmission attempt (as specified in the Number of Retries field). define a tag name for a message tag to receive text describing the status of communication attempts for this logical station. Valid Entry: numeric value from 0 . in hundredths of a second. for example. 68 / FactoryLink Device Interfaces Using EDI Technology . the communication attempt to this logical station was successful. If the value of this tag is 0 (OFF). If the value of this tag is 1 (ON).• • • • 5 | CONFIGURING COMMUNICATION PATHS Creating Logical Station Definitions Response Timeout 0. If all three retries are exhausted. Valid Entry: tag name Valid Data Type: digital LSTA Failure Message Tag Optionally. If you specify 300 for Response Timeout 0.10 (default = 3) LSTA Failure Digital Tag Optionally. Valid Entry: tag name Valid Data Type: message Comment Optionally. the communication attempt to this logical station failed.300 (default = 1) Number of Retries Define the maximum number of consecutive times a read or write command will be sent to a logical station after an unsuccessful first transmission attempt. the total duration of the transmission attempt is nine seconds. the protocol module will wait to receive a device response to a read or write command before timing out. Valid Entry: alphanumeric string of up to 30 characters 8 Click the Save icon to validate the data. transmission attempts cease for that command. If the device does not respond after the third retry. define a tag name for a digital tag to receive the status of communication attempts for this logical station. a three-second timeout occurs after each retry. You can also specify this tag name in the Alarm Supervisor for an alarm tag to indicate a communications failure. Valid Entry: numeric value from 1 .01 sec and 3 for Number of Retries. enter reference information about this logical station.

the table resembles the following example: In this example. choose the type of data to be stored in the tag for Type and accept the default of Shared for domain.CONFIGURING COMMUNICATION PATHS | 5 Creating Logical Station Definitions The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink. 10 To configure another logical port.SYS file has six allocated data master paths over which command/response transactions for FactoryLink Device Interfaces Using EDI Technology / 69 . 9 For each tag name. see “Reading Data from a Device” on page 73 or “Writing Data to a Device” on page 97. See the tag’s field description for the valid data types. 11 When you are ready to define the read and write operations expected to occur between this logical port and the associated Modbus Plus devices configured as logical stations. logical port 0 of the SA85 card configured as 0 in the CONFIG. Sample Logical Station Table Entries When all Logical Station Control table information is specified. return to the Logical Station Control table and repeat the appropriate steps.

30. All attempts to transmit instructions to the device are documented in a pair of tags. When all Logical Station Information table information is specified. the analog tag MODP_STATION0_STATUS is configured to hold port errors for logical station 0. that work together to provide a meaningful operator message for display purposes. which communicates with a Modicon 984 device at address 10. the table resembles the following example: Figure 5-1 Sample Logical Station Information Table In this example. logical station 0 defined on the Logical Station Information table). Additionally.• • • • 5 | CONFIGURING COMMUNICATION PATHS Creating Logical Station Definitions read and write operations can travel. 70 / FactoryLink Device Interfaces Using EDI Technology . Four data slave paths are available for transmission of unsolicited data from any device communicating with FactoryLink through this logical port (in this instance. FactoryLink makes up to three more one-second attempts (three total seconds) then ceases trying to send the data to the device. the EDI task will store communications error messages associated with this logical port in a message tag. After an initial unsuccessful attempt to transmit an instruction for a read or write operation. MODP_LPORT0_MSG.31. MODP_LS0_FAIL_DIG and MODP_LS0_FAIL_MSG.

FactoryLink Device Interfaces Using EDI Technology / 71 . you assign a logical port number to each physical port in the External Device Definition table.CONFIGURING COMMUNICATION PATHS | 5 Table Entries for Sample Worksheet TABLE E NTRIES FOR S AMPLE WORKSHEET The External Device Definition and Logical Station table entries corresponding to the sample configuration recorded on the logical station worksheet are shown in the following figure. you further define these logical ports in the Logical Station Control table. First. Then.

• • • • 5 | CONFIGURING COMMUNICATION PATHS Table Entries for Sample Worksheet 72 / FactoryLink Device Interfaces Using EDI Technology .

This chapter describes how to define a request to read locations in a device and store the information read in FactoryLink tags. you specify in which tags the device data read during the operation will be stored. the next step is to define information about the data to be read from and written to the devices. or a combination of these. triggered and unsolicited. you can configure two types of read requests. • FactoryLink Device Interfaces Using EDI Technology / 73 . Note The Modicon Modbus Plus protocol module is used as an example throughout this chapter to describe basic read operation concepts. To define a read request. you specify: • The tag name assigned to the FactoryLink tags storing the data • The logical station from which the data will be read • The register address in that logical station containing the data to be read Depending on the protocol module used. see the appropriate reference chapter. See “Writing Data to a Device” on page 97 for procedures describing how to define a request to write the values of FactoryLink tags to locations in a device. For protocol-specific information. the Read/Write tables are part of the cascading protocol-specific tables displayed when you choose the option for the protocol module you are configuring in the Device Interfaces folder.Chapter 6 • • • Reading Data from a Device After setting up the communication paths in the External Device Definition and Logical Station configuration tables. For each tag. When filling out a read request. Like the Logical Station tables. you configure the Read/Write table which consists of two tables: Read/Write Control and Read/Write Information.

. FactoryLink reads the values read then stores them in tags for which you specify tag names in the Read/Write Information table.. When the block read trigger is forced on. ..the task reads each defined address... a digital tag you configure in the Read/Write Control table as a trigger to initiate a block read operation causes FactoryLink to read the values at device addresses you specify in the associated Read/Write Information table each time the value of the trigger tag is forced to 1 (ON). 74 / FactoryLink Device Interfaces Using EDI Technology ..• • • • 6 | READING DATA FROM A DEVICE Triggered Read Request TRIGGERED R EAD R EQUEST In a triggered read request. ...then stores the value read in the tag specified to receive the value..

When FactoryLink receives a value that matches the criteria. FactoryLink Device Interfaces Using EDI Technology / 75 . In the Read/Write Information table..the EDI task is prepared to recognize the data structure of the value at each defined address according to its data type.. In the Read/Write Control table.. you indicate this is an unsolicited read. you specify the addresses from which data is expected and the type of data expected. . When you enter YES in the Unsolicited Read field... it stores the value in the specified tag. the data is stored in tags for which you specify tag names in the Read/Write Information table. When FactoryLink receives data from the device that matches this criteria.READING DATA FROM A DEVICE | 6 Unsolicited Read Request U NSOLICITED R EAD R EQUEST In an unsolicited read request. you configure FactoryLink to recognize and accept data of a particular structure.

identify the table type. You assign a name for the table. and define one or more trigger tags if the table is for a triggered read operation. Define one request (table) per line and do not include spaces in the name. Try to make the table name reflective of the operation it represents. add a table entry. You can define as many requests as available memory allows. 3 For each read request you want transmitted over a device communication path.• • • • 6 | READING DATA FROM A DEVICE Defining the Table Type and Triggers D EFINING THE TABLE TYPE AND TRIGGERS To begin configuring a read table. 1 Using the following field descriptions. The information you provide depends on the type of request you are defining. perform the following steps. 76 / FactoryLink Device Interfaces Using EDI Technology . or on. you fill out the Read/Write Control table. Valid Entry: alphanumeric string of up to 16 characters Unsolicited Read For EDI to interpret this operation as a triggered block read. the tag prompts FactoryLink to process this read table and any other read table with a Table Name entry associated with the same trigger. Leave all other fields blank. accept the default of NO. When the Block Read Trigger tag defined for this table is forced to 1. Sample entries are provided in “Sample Triggered Read Request” on page 92. add a table entry for each triggered read request you want to define. Table Name Give this read request a name. 1 Ensure the current domain selected is Shared in the Configuration Explorer. 2 Open the Read/Write Control table. The following steps describe how to fill out the Read/Write Control table. See the appropriate section for the type of read request you are defining: • “Triggered Read Request” below • “Unsolicited Read Request” on page 79 • “Combination Read Request” on page 80 Triggered Read Request To fill out a control table for a triggered read request.

and assign the same tag name to a Block Read Trigger tag. Math and Logic. you can define a Block Read Trigger tag as a Block Read State tag.” Valid Entry: tag name Valid Data Type: digital FactoryLink Device Interfaces Using EDI Technology / 77 . For efficient performance in larger applications. For example. The highest priority is 1. relative to other read operations. causing a daisy-chain effect within one table or across several tables. see Chapter 8. Valid Entry: no Enter a number to indicate the priority of this table. you could define a digital tag in the Event or Interval Timer. Valid Entry: 1 . This number influences the order in which the EDI task handles the queuing of block read requests. When this tag’s value is forced to 1 (ON). When you give identical names to a Block Read State and a Block Read Trigger tag. For a description and examples of how to create a daisy-chain read operation. When the tag’s value changes to 1 (as the result of a math operation or a defined event taking place.READING DATA FROM A DEVICE | 6 Defining the Table Type and Triggers Valid Entry: no Exception Write Block Read Priority To indicate this is not an exception write. “Application Design Tips and Techniques. it prompts an EDI task read operation. accept the default of NO. the completion of one read operation triggers the start of another.4 (default=1) Block Read Trigger Enter a tag name for a digital tag to initiate a block read of the register addresses specified in the associated Read/Write Information table. FactoryLink reads the addresses. or Client Builder. it processes the request with the highest priority first. The tag you use for the Block Read Trigger can also be defined in another FactoryLink task. If EDI receives two requests at the same time. A Block Read Trigger is required to prompt FactoryLink to process this table for a triggered read operation. for example).

choose DIGITAL for Type and accept the default of Shared for domain. 78 / FactoryLink Device Interfaces Using EDI Technology . After the tags defined in the associated Read/Write Information table are updated in the FactoryLink database. To re-enable a cascaded loop or a self-triggered read table. See “Application Design Tips and Techniques” on page 127 for further details. EDI forces the tag back to 1. The triggering cycle will cease upon disabling. Valid Entry: tag name Valid Data Type: digital 2 When you have finished filling out the information on this table. enter a tag name for a digital tag the EDI task forces to 1 (ON). it sets the tag to 0 (OFF). and each time it receives and processes a read request from a device protocol module. enter a tag name for a digital tag the EDI task forces to 1 (ON). When this tag’s value is forced to 1 (ON). the Block Read Trigger tag must be toggled or forced to 1. the read operation is not executed. and each time it receives and processes a read request from a device protocol module.• • • • 6 | READING DATA FROM A DEVICE Defining the Table Type and Triggers Block Read Disable Optionally. create a separate table for each port. click the Save icon. when it starts up. when it starts up. This tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered. enter a tag name for a digital tag to disable a block read of the tags specified in this table. After the tags defined in the associated Read/Write Information table are updated in the FactoryLink database. Valid Entry: tag name Valid Data Type: digital Note: If you are defining a Block Read Complete or Block Read State tag to be used for more than one logical port. however. even when the block read trigger is set. Block Read Complete Optionally. During EDI's transmission of the request. EDI forces the tag to 1 again. Valid Entry: tag name Valid Data Type: digital Block Read State Optionally. 3 For each tag name. The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink.

which indicates this is not an exception write. Table Name Assign a name to this read request. The change-status indicator is set only if the tag’s value has changed since the most recent write to the tag. If.READING DATA FROM A DEVICE | 6 Defining the Table Type and Triggers 4 Define the data to be read and the target addresses in the Read/Write Information table. the change-status indicator is unaffected. Valid Entry: alphanumeric string of up to 16 characters Unsolicited Read Enter YES. Sample entries are provided in “Sample Unsolicited Read Request” on page 94. the value being written to the tag is a new value. 3 Define the data to be read and the target addresses in the Read/Write Information table. Leave all other fields blank. click the Save icon. add a table entry for each unsolicited read request you want to define. You can define as many requests as available memory allows. If the current value of the tag is equal to the value being written. The data is written to the tag specified in the Read/Write Information table. Valid Entry: yes Exception Write Block Read Priority Accept the default of NO. EDI will interpret this operation as an unsolicited read and emulate the device’s addressing structure based on entries you make in the Read/Write Information table. perform the following steps. Unsolicited Read Request To fill out a control table for an unsolicited read request. however. Define one request (table) per line and do not include spaces in the name. Try to make the table name reflective of the operation it represents. Valid Entry: no Accept the default of 1. See “Specifying What to Read and Where to Store It” on page 81. See “Specifying What to Read and Where to Store It” on page 81 for details. 1 Using the following field descriptions. This field is ignored for unsolicited read operations. it will overwrite the existing value and the tag’s change-status indicator will be set to 1 (ON). Valid Entry: 1 2 When you have finished filling out the information on this table. FactoryLink Device Interfaces Using EDI Technology / 79 .

For example. but enter YES in the Unsolicited Read field instead of NO. you may want to configure a read operation to execute in two ways: by a trigger and by unsolicited processing. To configure a combination read request. click the Save icon. 80 / FactoryLink Device Interfaces Using EDI Technology . See “Specifying What to Read and Where to Store It” on page 81 for details. 3 Define the data to be read and the target addresses in the Read/Write Information table.• • • • 6 | READING DATA FROM A DEVICE Defining the Table Type and Triggers Combination Read Request In some cases. 1 Fill out a control table with the information described in “Triggered Read Request” on page 76. perform the following steps. you could configure a combination triggered block read and unsolicited read table if you want to read a register and write its value to a tag upon start up and thereafter. only update that tag when the register value changes. 2 When you have finished filling out the information on this table.

Additional sample entries are provided in “Sample Read Requests” on page 92. For a read request. you add an entry in the Read/Write Information table for each tag to which data will be written when the operation is executed. Here. 4 To configure another read request. select the row for the read request you are defining. Click Next to display the Read/Write Information table.READING DATA FROM A DEVICE | 6 Specifying What to Read and Where to Store It S PECIFYING W HAT TO R EAD AND W HERE TO S TORE I T Once the Read/Write Control table is complete. The information you provide in this table depends on the type of register to be accessed and the type of data to be read. and where the data is stored in the FactoryLink database. return to the Read/Write Control table and complete the appropriate steps. you indicate what data is transferred from the device to FactoryLink during the operation. See the tag’s field description for the valid data types. Each section listed in the table provides sample table entries for a specific type of read request. 1 On the Read/Write Control table. choose the type of data to be stored in the tag for Type and accept the default of Shared for domain. go to the Read/Write Control table and define the write requests required for your application. See “Writing Data to a Device” on page 97 for details. FactoryLink Device Interfaces Using EDI Technology / 81 . 2 When you have finished defining all the register addresses to be read and all the FactoryLink database tags to which the data is to be written. See the data type reference table below to determine where to go for instructions on filling out this table for your particular application. 5 When all read requests are complete. 3 For each tag name. Each address that will be read from a memory location in a device is represented by a separate tag name for a tag in the FactoryLink database. The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink. click the Save icon to validate the data. The following steps describe how to fill out the Read/Write Information table. fill out the Read/Write Information table.

Store in Analog Tag” on page 83 “Read Holding or Input Register. see the “Maximum Contiguous Registers in a Single Message. 82 / FactoryLink Device Interfaces Using EDI Technology . Store in Message Tag” on page 87 “Read Holding or Input Register. Store in Digital Tag” on page 88 “Read Memory Register. Store in Digital Tag” on page 88 “Read Coil or Input Status Register. Store in Analog Tag” on page 89 “Read Statistics Word. Store in Digital Tag” on page 85 “Read Holding Register.• • • • 6 | READING DATA FROM A DEVICE Specifying What to Read and Where to Store It Register Type FactoryLink Data Type Where to Go for Configuration Instructions Holding Analog Digital Float Longana Message “Read Holding or Input Register. Store in Analog Tag” on page 90 Input Analog Digital Input Status Coil Memory Statistics Global Data Digital Digital Analog Analog Analog Note: For the maximum number of contiguous registers that can be included in a single block read message for each supported register type.” table. Store in Floating-Point or Long Analog Tag” on page 86 “Read Holding Register. Store in Digital Tag” on page 85 “Read Coil or Input Status Register. Store in Analog Tag” on page 90 “Read Statistics Word. Store in Analog Tag” on page 83 “Read Holding or Input Register. Store in Floating-Point or Long Analog Tag” on page 86 “Read Holding Register.

If more than the maximum number of contiguous register addresses are defined. FactoryLink Device Interfaces Using EDI Technology / 83 . Tag Name Specify a tag name for an analog tag in which FactoryLink will store the data read from the device. two messages are generated. Store in Analog Tag To fill out an information table for a request to read a holding register or an input register and store the data in an analog tag. multiple messages are generated for the operation. The first message reads the first 125 addresses (addresses 100 to 124). The following table lists the maximum number of contiguous registers included in a single block read message for each supported register type.READING DATA FROM A DEVICE | 6 Specifying What to Read and Where to Store It A read table should not contain more than the maximum number of contiguous registers allowed for a single message accessing a type of register. Maximum Contiguous Registers in a Single Message. Type of Register Maximum Number For Block Read Coil Holding Global Input Status Input Statistics Word Memory 2000 125 32 global data words 2000 125 54 words 100 Read Holding or Input Register. if a block read table for a holding register in a 984 device contains entries that access contiguous addresses from 100 to 127. Using the following field descriptions. For example. add a table entry for each tag in which data read from the device will be stored when the operation executes. The second message reads addresses 125 through 127. The maximum number allowed varies from one register type to the next. perform the following steps.

..the Logical Station number defined on the Logical Station information table for this device’s Logical Port number. which is specified in the Data Type field. for holding register address 400001. IREG 84 / FactoryLink Device Interfaces Using EDI Technology . Valid Entry: 1 . Valid Entry: tag name Valid Data Type: analog Logical Station Enter the number representing the device from which the data is to be read. Valid Entry: 1 Specify the type of register to be read as HREG for holding register or IREG for input register.. Address Enter the register address in the device’s memory where the value to be stored in this tag is located. .• • • • 6 | READING DATA FROM A DEVICE Specifying What to Read and Where to Store It The Logical Station number defined on the Read/Write Information table must match. Do not include the register address prefix (4 for holding and 3 for input) or leading zeros. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. For example. just enter 1. The prefix indicates the register type. for input register address 345902. Valid Entry: HREG. Valid Entry: previously defined logical station number Reg..65535 Bit Offset/ MSG Length Data Type Accept the default of 1. enter 45902.

Valid Entry: tag name Valid Data Type: digital Logical Station Enter the number representing the device from which the data is to be read. for holding register address 400001. add a table entry for each tag in which data read from the device will be stored when the operation executes. Address Enter the register address in the device’s memory where the value to be stored in this tag is located. Valid Entry: HREG. Do not include the register address prefix (4 for holding and 3 for input) or leading zeros.READING DATA FROM A DEVICE | 6 Specifying What to Read and Where to Store It Read Holding or Input Register. Store in Digital Tag To fill out an information table for a request to read a holding register or an input register and store the data in a digital tag.65535 Bit Offset/ MSG Length Specify the bit offset within a register word that contains the value to be read. For example. just enter 1. IREG FactoryLink Device Interfaces Using EDI Technology / 85 . This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. The prefix indicates the register type. Valid Entry: previously defined logical station number Reg. enter 45902. Bit 1 is the most significant bit (MSB) and bit 16 is the least significant bit (LSB). Tag Name Specify a tag name for a digital tag in which FactoryLink will store the data read from the device.16 Data Type Specify the type of register to be read as HREG for holding register or IREG for input register. perform the following. MSB 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 LSB 16 Valid Entry: 1 . Using the following field descriptions. which is specified in the Data Type field. for input register address 345902. Valid Entry: 1 .

. Try to maintain consistency when using register addresses for floating-point and long analog tag types. 8. Store in Floating-Point or Long Analog Tag To fill out an information table for a request to read a holding register and store the data in a floating-point or long analog tag. 7. Enter the address for only the starting register in a register pair. 4.• • • • 6 | READING DATA FROM A DEVICE Specifying What to Read and Where to Store It Read Holding Register. Valid Entry: previously defined logical station number Reg.. 6. 3. for holding register address 400001. or 2. Do not include the register address prefix (4) or leading zeros. Valid Entry: 1 .65535 Bit Offset/ MSG Length Data Type Accept the default of 1. which is specified in the Data Type field. For example. add a table entry for each tag in which data read from the device will be stored when the operation executes. 5. perform the following. Address Enter the register address in the device’s memory where the value to be stored in this tag is located. just enter 1. 10.. For example. Adopt either an odd or even starting register sequence and maintain that sequence. Tag Name Specify a tag name for a floating-point or long analog tag in which FactoryLink will store the data read from the device. The companion register is implied. The first register in the pair contains the high order word... 1. Valid Entry: 1 Specify HREG as the type of register to be read. Valid Entry: HREG 86 / FactoryLink Device Interfaces Using EDI Technology . Using the following field descriptions. Floating-point or long analog tag types are addressed in pairs.. 9. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. The prefix indicates the register type. longana Logical Station Enter the number representing the device from which the data is to be read. Valid Entry: tag name Valid Data Type: float. the second register contains the low order word..

Valid Entry: HREG FactoryLink Device Interfaces Using EDI Technology / 87 . Do not include the register address prefix (4) or leading zeros. For example. The number of registers to be read is defined in the Bit Offset/MSG Length field of this table. Using the following field descriptions. which is specified in the Data Type field. Valid Entry: tag name Valid Data Type: message Logical Station Enter the number representing the device from which the data is to be read. just enter 1. starting from the location specified in the previous field. Store in Message Tag To fill out an information table for a request to read a holding register and store the data in a message tag. Valid Entry: 1 . for holding register address 400001. FactoryLink does not perform verification on these bytes to ensure the data is printable ASCII. add a table entry for each tag in which data read from the device will be stored when the operation executes. Address.READING DATA FROM A DEVICE | 6 Specifying What to Read and Where to Store It Read Holding Register. Tag Name Specify a tag name for a message tag in which FactoryLink will store the data read from the device. Enter the first address in the group of registers containing the message characters. The prefix indicates the register type. Valid Entry: 1 .80 Data Type Specify HREG as the type of register to be read. Valid Entry: previously defined logical station number Reg.65535 Bit Offset/ MSG Length Specify the number of bytes in the device’s memory containing the message. Reg. perform the following. Address Enter the register address in the device’s memory where the value to be stored in this tag is located. are read and the values are stored in the Tag Name message tag as raw binary data. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. These bytes.

perform the following. INP 88 / FactoryLink Device Interfaces Using EDI Technology . Do not include the register address prefix (0 for coil and 3 for input status) or leading zeros. For example. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. Valid Entry: 1 Specify the type of register to be read as COIL for coil register or INP for input status register. for input status register address 300001. Address Enter the register address in the device’s memory where the value to be stored in this tag is located. add a table entry for each tag in which data read from the device will be stored when the operation executes. just enter 1. for coil address 023451. Valid Entry: 1 . Tag Name Specify a tag name for a digital tag in which FactoryLink will store the data read from the device. Valid Entry: tag name Valid Data Type: digital Logical Station Enter the number representing the device from which the data is to be read. enter 23451. Valid Entry: COIL. The prefix indicates the register type. Store in Digital Tag To fill out an information table for a request to read a coil or input status register and store the data in a digital tag. Valid Entry: previously defined logical station number Reg.• • • • 6 | READING DATA FROM A DEVICE Specifying What to Read and Where to Store It Read Coil or Input Status Register. which is specified in the Data Type field. Using the following field descriptions.65535 Bit Offset/ MSG Length Data Type Accept the default of 1.

For example. Valid Entry: tag name Valid Data Type: analog Logical Station Enter the number representing the device from which the data is to be read.65535 FactoryLink Device Interfaces Using EDI Technology / 89 . Valid Entry: 1 . The prefix indicates the register type. Do not include the register address prefix (6) or leading zeros.. which is specified in the Data Type field. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. Read Memory Register. add a table entry for each tag in which data read from the device will be stored when the operation executes. Address Enter the register address in the device’s memory where the value to be stored in this tag is located.the Logical Station number defined on the Logical Station Information table. for memory address 600001. just enter 1.READING DATA FROM A DEVICE | 6 Specifying What to Read and Where to Store It The Logical Station number defined on the Read/Write Information table must match. Tag Name Specify a tag name for an analog tag in which FactoryLink will store the data read from the device. Store in Analog Tag To fill out an information table for a request to read a memory register and store the data in an analog tag.. perform the following steps.... Valid Entry: previously defined logical station number Reg. . Using the following field descriptions..

add a table entry for each tag in which data read from the device will be stored when the operation executes.• • • • 6 | READING DATA FROM A DEVICE Specifying What to Read and Where to Store It Bit Offset/ MSG Length Data Type Accept the default of 1. Tag Name Specify a tag name for an analog tag in which FactoryLink will store the data read from the device. Valid Entry: tag name Valid Data Type: analog Logical Station Enter the number representing the device from which the data is to be read. use FactoryLink Math & Logic to “OR” the words together. Valid Entry: 1 Specify the type of register to be read as XMEMnn where nn is a numeric value from 1 to 10. To access the high and low bytes of a single word. Note Reference the high and low bytes of a statistics word in one block read table to ensure the information retrieved for a single word is synchronized. Valid Entry: XMEM1 . Address Enter the register address in the device’s memory where the value to be stored in this tag is located. Valid Entry: previously defined logical station number Reg. Specify STATHI in the Data Type field for the first tag and STATLO for the second tag. Valid Entry: 1 . Store in Analog Tag To fill out an information table for a request to read the high or low bytes of a network statistics word and store the data in an analog tag. enter the same register address twice for two separate analog tags.65535 90 / FactoryLink Device Interfaces Using EDI Technology . This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. Using the following field descriptions. To create a single word value.XMEM10 Read Statistics Word. perform the following.

Valid Entry: previously defined logical station number Reg. perform the following. Valid Entry: 1 Specify STATHI to access a high byte of a statistics word and STATLO to access a low byte. Using the following field descriptions. Valid Entry: GLBL FactoryLink Device Interfaces Using EDI Technology / 91 .32 Bit Offset/ MSG Length Data Type Accept the default of 1. Valid Entry: tag name Valid Data Type: analog Logical Station Enter the number representing the device from which the data is to be read. Valid Entry: 1 Specify GLBL to access a global data word. and so on. an error is generated. Address Enter the register address in the device’s memory where the value to be stored in this tag is located. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. Valid Entry: STATHI. Refer to the IBM documentation for Modbus Plus network-based statistics word assignments. the second is word 2. add a table entry for each tag in which data read from the device will be stored when the operation executes. Valid Entry: 1 . STATLO Read Global Data Word. If you specify a register address larger than the total number of global data words that will actually be received. Store in Analog Tag To fill out an information table for a request to read a global data word and store the data in an analog tag. The first global data word received is always assumed to be word 1. Tag Name Specify a tag name for an analog tag in which FactoryLink will store the data read from the device.READING DATA FROM A DEVICE | 6 Specifying What to Read and Where to Store It Bit Offset/ MSG Length Data Type Accept the default of 1.

MODP_READ_STATE. In this example. and to the Block 92 / FactoryLink Device Interfaces Using EDI Technology . Sample Read/Write Control Table for Triggered Read READ is discussed in this example. FactoryLink reads the configured register address and writes its value to the tag configured for this table (in the Read/Write Information table). The table entries provided in the following pages illustrate the way in which FactoryLink processes read requests. Sample Triggered Read Request This section provides descriptions of some possible Read/Write Control and Read/Write Information table entries for a triggered read request. MODP_READ_TRIGGER. the READ table is configured as follows: • When the value of the digital Block Read Trigger tag MODP_READ_TRIGGER is 1. and does not process the READ table. • Once FactoryLink reads the data and writes it to the tag defined to receive it (HOLD_MSG1 in the Read/Write Information table). the highest priority. The block read priority. which is set automatically if you do not enter a value. FactoryLink forces a value of 1 to the digital Block Read State tag. is set to the default of 1.• • • • 6 | READING DATA FROM A DEVICE Sample Read Requests S AMPLE R EAD R EQUESTS This section provides descriptions of some possible Read/Write Control and Read/Write Information table entries for a read request. • When the value of the digital tag MODP_READ_DISABLE is 1. FactoryLink disregards the trigger tag.

. MODP_READ_STATE is set to 0. MODP_READ_COMPLETE. then writes the values read into a message tag. FactoryLink Device Interfaces Using EDI Technology / 93 .. Sample Read/Write Information Table for Triggered Read In this example. FactoryLink reads holding registers 200 through 230 in the device configured as logical station 0. when the READ table is triggered by MODP_READ_TRIGGER. During the read operation.then stores the values read in HOLD_MSG1.. FactoryLink processes the table.READING DATA FROM A DEVICE | 6 Sample Read Requests Read Complete tag. How This Triggered Block Read Request Works When the value of MODP_READ_TRIGGER is 1.. HOLD_MSG1. FactoryLink reads thirty holding registers beginning with address 200. . READ.

the UNSOL_READ table is configured to accept unsolicited data of the data type specified on the corresponding Read/Write Information table from the specified addresses associated with these entries. The entries shown in the above for Exception Write. Sample Read/Write Control Table for Unsolicited Read UNSOL_READ is discussed in this example. Block Read Priority. 94 / FactoryLink Device Interfaces Using EDI Technology . In this example. and Block Write Priority are system defaults. The only required user entries for an unsolicited read request on the Read/Write Control table are Table Name and Unsolicited Read.• • • • 6 | READING DATA FROM A DEVICE Sample Read Requests Sample Unsolicited Read Request This section provides descriptions of some possible Read/Write Control and Read/Write Information table entries for an unsolicited read request.

HOLD_MSG1. FactoryLink reads the incoming data upon its arrival then stores it in a message tag. HOLD_MSG1. FactoryLink Device Interfaces Using EDI Technology / 95 . FactoryLink reads the data then stores it in the message tag. UNSOL_READ.READING DATA FROM A DEVICE | 6 Sample Read Requests Sample Read/Write Information Table for Unsolicited Read In this example. it processes the table. How This Unsolicited Read Request Works When FactoryLink receives data from holding registers 200 through 230 in the device configured as logical station 0.

• • • • 6 | READING DATA FROM A DEVICE Sample Read Requests 96 / FactoryLink Device Interfaces Using EDI Technology .

Like the Logical Station tables. you specify the following basic information: • The tag name assigned to the FactoryLink tag containing the data to be written • The logical station to which the data will be written • The register address in that logical station to which the data will be written FactoryLink can write data to a device in two ways: as a block write when prompted by a digital trigger tag or as an exception write when prompted by the data changing. For protocol-specific information. Note The Modicon Modbus Plus protocol module is used as an example throughout this chapter to describe basic write operation concepts. you configure the Read/Write table. To define a write request. the Read/Write tables are part of the cascading protocol-specific tables displayed when you choose the option for the protocol module you are configuring from the Configuration Explorer. When filling out a write request. which consists of two tables: Read/Write Control and Read/Write Information. see the appropriate reference chapter. • FactoryLink Device Interfaces Using EDI Technology / 97 .Chapter 7 • • • Writing Data to a Device This chapter describes how to define a request to write the values of FactoryLink tags to specified locations in a device. See “Reading Data from a Device” on page 73 for procedures describing how to define a request to read specified locations in a device and store the values read in FactoryLink tags.

. How a Block Write Operation Works When the block write trigger is forced on. a digital tag you configure in the Read/Write Control table as a trigger to initiate a block write operation causes the EDI task to write tag values specified in the Read/Write Information table to their associated device addresses each time the value of the tag is forced to 1 (ON)... .to the defined address..the task writes the value of each defined tag..• • • • 7 | WRITING DATA TO A DEVICE Block Write Request B LOCK WRITE R EQUEST In a block write request. 98 / FactoryLink Device Interfaces Using EDI Technology ..... .

When the value of each defined tag changes. Optionally. .. the EDI task writes those values to the defined device addresses. Each defined exception write results in a separate write command. but both are required if you do plan to disable the table.. the EDI task writes the values of the tags associated with this table only when they change. you can define a digital tag to disable and re-enable an exception write table and a trigger tag to update the equipment once the table is re-enabled.WRITING DATA TO A DEVICE | 7 Exception Write Request E XCEPTION WRITE R EQUEST In an exception write request. you can use a block write trigger to update any values in the device that changed while the table was disabled. Neither are required unless you plan to periodically disable the table. How an Exception Write Operation Works When the Exception Write field is YES... FactoryLink Device Interfaces Using EDI Technology / 99 . A disable trigger disables an exception write table.to the defined device address. Once a table is re-enabled. when any of the values of the tags defined in the Read/Write Information table change. the EDI task writes it.

you give the table a name. Here. add a table entry for each block write request you want to define. Valid Entry: no 100 / FactoryLink Device Interfaces Using EDI Technology . 1 Using the following field descriptions. Table Name Assign a name to this write request. Valid Entry: alphanumeric string of up to 16 characters Unsolicited Read To indicate this is not an unsolicited read. You can define as many requests as available memory allows. Define one request (table) per line and do not include spaces in the name. 2 Open the Read/Write Control table. 3 For each write request you want transmitted over a device communication path. Leave all other fields blank. 1 Ensure the current domain selection is Shared in the Configuration Explorer. the tag prompts FactoryLink to process this write table and any other write table with a Table Name entry associated with the same trigger.• • • • 7 | WRITING DATA TO A DEVICE Defining the Table Type and Triggers D EFINING THE TABLE TYPE AND TRIGGERS To begin configuring a write table. The information you provide depends on the type of request you are defining. and define any needed trigger tags. accept the default of NO. The following steps describe how to fill out the Read/Write Control table. Try to make the table name reflective of the operation it represents. you fill out the Read/Write Control table. Sample entries are provided in “Sample Triggered Block Write Request” on page 117. When the Block Write Trigger tag defined for this table is forced to 1. See the appropriate section for the type of write request you are defining: • “Block write request” on page 100 • “Exception write request” on page 103 • “Combination write request” page 105 Block Write Request To fill out a control table for a block write request. perform the following steps. or on. identify the table type. add a table entry.

When the tag’s value changes to 1 (as the result of a math operation or a defined event taking place.” Valid Entry: tag name Valid Data Type: digital FactoryLink Device Interfaces Using EDI Technology / 101 . you can define a Block Write Trigger tag as a Block Write State tag. causing a daisy-chain effect within one table or across several tables. You define these tags the task will read from the FactoryLink database and then write to the device in the Read/Write Information table. “Application Design Tips and Techniques. For example. To indicate this is not an exception write. it processes the request with the highest priority first. When this tag’s value is forced to 1 (ON). accept the default of NO. Math and Logic. The highest priority is 1. and assign the same tag name to a Block Write Trigger tag. or Client Builder.WRITING DATA TO A DEVICE | 7 Defining the Table Type and Triggers Exception Write Specify how the EDI task will write the values of tags containing information to be transmitted to a device. For efficient performance in larger applications. The tag you use for the Block Write Trigger can also be defined in another FactoryLink task. for example). block and exception. A Block Write Trigger is required to prompt FactoryLink to process this table for a write operation.4 (default = 1) Block Write Trigger Enter a tag name for a digital tag to initiate a block write of the tag values specified in the associated Read/Write Information table to the register addresses defined to receive the values. see Chapter 8. FactoryLink writes the values. For a description and examples of how to create a daisy-chain write operation. This number influences the order in which the EDI task handles the queuing of all write requests. it prompts an EDI task write operation. you could define a digital tag in the Event or Interval Timer. Valid Entry: 1 . When you give identical names to a Block Write State and a Block Write Trigger tag. relative to other write operations. the completion of one write operation triggers the start of another. Valid Entry: no Block Write Priority Enter a number to indicate the priority of this table. If EDI receives two requests at the same time.

102 / FactoryLink Device Interfaces Using EDI Technology . when it starts up. The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink. During EDI's transmission of the request. however. when it starts up. If you are defining a Block Write State tag to be used for more than one logical port. create a separate table for each port. and each time it receives and processes a write request from a protocol module. Valid Entry: tag name Valid Data Type: digital Block Write State Optionally. even when the block write trigger is set. If you are defining a Block Write Complete tag to be used for more than one logical port. 3 For each tag name. After the data is written to the device. the write operation is not executed. Valid Entry: tag name Valid Data Type: digital 2 When you have finished filling out the information on this table.• • • • 7 | WRITING DATA TO A DEVICE Defining the Table Type and Triggers Block Write Disable Optionally. EDI forces the tag to 1 again. it sets the tag to 0 (OFF). To re-enable a cascaded loop or a self-triggered write table. and each time it receives and processes a write request from a protocol module. After the data is written to the device. enter a tag name for a digital tag the EDI task forces to 1 (ON). enter a tag name for a digital tag the EDI task forces to 1 (ON). When this tag’s value is forced to 1. This tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. click the Save icon. The triggering cycle will cease upon disabling. EDI force-writes the tag back to 1. create a separate table for each port. enter a tag name for a digital tag to disable a block write to the device addresses specified in this table. choose DIGITAL for Type and accept the default of Shared for domain. the Block Write Trigger tag must be toggled or forced to 1. Valid Entry: tag name Valid Data Type: digital Block Write Complete Optionally.

Valid Entry: no For the task to write tag values only when those values change. EDI writes this tag’s value to the device. Leave all other fields blank.WRITING DATA TO A DEVICE | 7 Defining the Table Type and Triggers 4 Define the data to be written and the target addresses in the Read/Write Information table. Valid Entry: yes FactoryLink Device Interfaces Using EDI Technology / 103 . To fill out a control table for an exception write request. You can define as many requests as available memory allows. perform the following steps. Sample entries are provided in “Sample Exception Write Request” on page 120. accept the default of NO. Unsolicited Read Exception Write To indicate this is not an unsolicited read. Exception Write Request In an exception write. enter YES. See “Specifying What to Write and Where to Write It” on page 106 for details. 1 Using the following field descriptions. Define one request (table) per line and do not include spaces in the name. Try to make the table name reflective of the operation it represents. an internal change-status indicator within the tag containing the data to be written prompts the write operation. add a table entry for each exception write request you want to define. FactoryLink processes this exception write table and any other exception write table with a Table Name entry associated with the same tags. When the values of the tags you define in the associated Read/Write Information table change. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). Table Name Give this write request a name.

it disables an exception write of the defined tags to the device addresses specified in the Read/Write Information table. click the Save icon. Valid Entry: 1 Note If you plan to periodically disable this table. Valid Entry: tag name Valid Data Type: digital 2 When you have finished filling out the information on this table. 4 Define the data to be written and the target addresses in the Read/Write Information table. Valid Entry: tag name Valid Data Type: digital Block Write Disable Enter a tag name for a digital tag to temporarily disable this table. When the tag's value is set to 0 again. 3 For each tag name. The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink. 104 / FactoryLink Device Interfaces Using EDI Technology . When the value of this tag is 1. choose DIGITAL for Type and accept the default of Shared for domain. If you do not plan to disable this table. Once a table is re-enabled. do not define either of these tags. See “Specifying What to Write and Where to Write It” on page 106 for details. the table is re-enabled.• • • • 7 | WRITING DATA TO A DEVICE Defining the Table Type and Triggers Block Write Priority Accept the default of 1. both a Block Write Trigger and a Block Write Disable tag are required. a Block Write Trigger tag can be used to write any values that changed while the table was disabled. Block Write Trigger Enter a tag name for a digital tag to trigger the table once it is disabled then subsequently re-enabled by a Block Write Disable tag. This field is ignored for exception write operations. See the following field descriptions.

only write the tag’s value to the device when it changes. you could configure a combination block write and exception write table if you want to write the current value of a tag to a register address in the device upon start up and thereafter. 3 Define the data to be written and the target addresses in the Read/Write Information table. FactoryLink Device Interfaces Using EDI Technology / 105 . perform the following steps. 1 Fill out a control table with the information described in“Block Write Request” on page 100. click the Save icon. See “Specifying What to Write and Where to Write It” on page 106 for details. you may want to configure a write operation to execute in two ways: by a digital trigger tag and by exception processing. For example. 2 When you have finished filling out the information on this table.WRITING DATA TO A DEVICE | 7 Defining the Table Type and Triggers Combination Write Request In some cases. To configure a combination write request. Sample table entries are provided in “Sample Combination Write Request” on page 123. but enter YES in the Exception Write field instead of NO.

Each section listed in the table provides sample table entries for a specific type of write request. The following steps describe how to fill out the Read/Write Information table. you indicate the data to be written to the device during the operation. click the Save icon to validate the data. 2 When you have finished defining all the FactoryLink database tags and the register addresses to which their contents are to be written. 3 For each tag name. and to which register addresses it will be written. go to the Read/Write Control table and complete the write requests 106 / FactoryLink Device Interfaces Using EDI Technology . The Tag Definition dialog box displays for each specified tag name that is not defined elsewhere in FactoryLink. select the row for the write request you are defining. Display the Read/Write Information table. See the tag’s field description for the valid data types. Here.• • • • 7 | WRITING DATA TO A DEVICE Specifying What to Write and Where to Write It S PECIFYING W HAT TO W RITE AND W HERE TO W RITE I T Once the Read/Write Control table is complete. See the “Register and FactoryLink Data Type Configuration Reference” table to determine where to go for instructions on filling out this table for your particular application. The data to be written is represented by one or more tags in the FactoryLink database. 4 To configure another write request. For a write request. The information you provide in this table depends on the type of register to be accessed and the type of data to be written. Additional sample entries are provided in “Sample Write Requests” on page 117. you add an entry in the Read/Write Information table for each tag to be written when the operation is executed. fill out the Read/Write Information table. choose the type of data to be stored in the tag for Type and accept the default of Shared for domain. 1 On the Read/Write Control table.

WRITING DATA TO A DEVICE | 7 Specifying What to Write and Where to Write It Register and FactoryLink Data Type Configuration Reference Register Type FactoryLink Data Type Where to Go for Configuration Instructions Holding Analog Digital “Write Analog Tag Value to Holding Register” on page 108 “Write Digital Tag Value to Holding Register” on page 109 To set or clear bits. A write table should not contain more than the maximum number of contiguous registers allowed for a single message accessing a type of register. “Set Bits in Holding Register Using Mask Write” on page 111 Floating-point Longana Message Coil Memory Global Digital Analog Analog “Write Floating-Point or Long Analog Tag Value to Holding Register” on page 112 “Write Floating-Point or Long Analog Tag Value to Holding Register” on page 112 “Write Message Tag Value to Holding Register” on page 113 “Write Digital Tag Value to Coil Register” on page 114 “Write Analog Tag Value to Memory Register” on page 115 “Write Analog Tag Value to Global Data Word” on page 116 Note: For the maximum number of contiguous registers that can be included in a single block write message for each supported register type. multiple messages are generated for the operation. The maximum number allowed varies from one register type to the next. FactoryLink Device Interfaces Using EDI Technology / 107 . see the “Maximum Contiguous Registers in a Single Message” table. If more than the maximum number of contiguous register addresses are defined.

• • • •

7 | WRITING DATA TO A DEVICE Specifying What to Write and Where to Write It

The following table lists the maximum number of contiguous registers included in a single block write message for each supported register type.
Maximum Contiguous Registers in a Single Message

Type of Register

Maximum Number For Block Write

Coil Holding Global Statistics Word Memory

800 100 1 exception write for mask operation 32 global data words 1 exception write for clear statistics operation 100

Write Analog Tag Value to Holding Register To fill out an information table for a request to write the value of an analog tag to a holding register, perform the following. Using the following field descriptions, add a table entry for each tag to be written and define the register addresses to receive each tag value when the operation executes.
Tag Name

Specify a tag name for an analog tag containing a value to be written to the device.
Valid Entry: tag name Valid Data Type: analog

Logical Station

Enter the number representing the device to which the tag’s value will be written. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.
Valid Entry: previously defined logical station number

108 / FactoryLink Device Interfaces Using EDI Technology

WRITING DATA TO A DEVICE | 7 Specifying What to Write and Where to Write It

The Logical Station number defined on the Read/Write Information table must match...

...the Logical Station number defined on the Logical Station Information table for this device’s Logical Port number.

Reg. Address

Enter the register address in the device’s memory to which the tag value will be written. Do not include the register address prefix (4) or leading zeros. The prefix indicates the register type, which is specified in the Data Type field. For example, for holding register address 400001, just enter 1.
Valid Entry: 1 - 65535

Bit Offset/ MSG Length Data Type

Accept the default of 1.
Valid Entry: 1

Specify HREG as the type of register to which the tag value will be written.
Valid Entry: HREG

Write Digital Tag Value to Holding Register To fill out an information table for a request to write the value of a digital tag to a holding register, perform the following. Using the following field descriptions, add a table entry for each tag to be written and define the register addresses to receive each tag value when the operation executes.

FactoryLink Device Interfaces Using EDI Technology / 109

• • • •

7 | WRITING DATA TO A DEVICE Specifying What to Write and Where to Write It

When a digital tag is written to a holding register, two messages are sent to the device. The first message reads the entire holding register; the second message writes the new value to the specified bit.

Tag Name

Specify a tag name for a digital tag containing a value to be written to the device.
Valid Entry: tag name Valid Data Type: digital

Logical Station

Enter the number representing the device to which the tag’s value will be written. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.
Valid Entry: previously defined logical station number

Reg. Address

Enter the register address in the device’s memory to which the tag value will be written. Do not include the register address prefix (4) or leading zeros. The prefix indicates the register type, which is specified in the Data Type field. For example, for holding register address 400001, just enter 1.
Valid Entry: 1 - 65535

Bit Offset/ MSG Length

Specify the bit offset within a register word to which the tag value will be written. Bit 1 is the most significant bit (MSB) and bit 16 the least significant bit (LSB).
MSB 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 LSB 16

Valid Entry: 1 - 16

110 / FactoryLink Device Interfaces Using EDI Technology

WRITING DATA TO A DEVICE | 7 Specifying What to Write and Where to Write It

Data Type

Specify HREG as the type of register to which the tag value will be written.
Valid Entry: HREG

Go back to step 2 on page 106. Set Bits in Holding Register Using Mask Write In devices that support this operation, a mask write sets or clears bits within a holding register. A mask write is sent to the device as an exception write operation; therefore, it generates a single write message. The following Modicon model types support mask write operations: A120, A130, A141, A145, 685E, 785E, AT4, and VM4. To fill out an information table for a request to send a mask write to a holding register, perform the following steps. Using the following field descriptions, add a table entry for each for each bit to be set or cleared when the value of any bit defined in the table changes. Each bit is referenced by a separate tag name on the Read/Write Information table.
Tag Name

Specify a tag name for a digital tag containing a value to be written to the device. When a digital tag is written to a holding register, two messages are sent to the device. The first message reads the entire holding register; the second one writes the new value to the specified bit.
Valid Entry: tag name Valid Data Type: digital

Logical Station

Enter the number representing the device to which the tag value will be written. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.
Valid Entry: previously defined logical station number

Reg. Address

Enter the register address of the word containing the bit to be set or cleared. Do not include the register address prefix (4) or leading zeros. The prefix indicates the register type, which is specified in the Data Type field. For example, for holding register address 400001, just enter 1.
Valid Entry: 1 - 65535

FactoryLink Device Interfaces Using EDI Technology / 111

• • • •

7 | WRITING DATA TO A DEVICE Specifying What to Write and Where to Write It

Bit Offset/ MSG Length

Specify the bit within the register word that will change as a result of the mask write. Bit 1 is the most significant bit (MSB) and 16 the least significant bit (LSB).
MSB 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 LSB 16

Valid Entry: 1 - 16

Data Type

Specify MASK to indicate the type of operation.
Valid Entry: MASK

Go back to step 2 on page 106. Write Floating-Point or Long Analog Tag Value to Holding Register To fill out an information table for a request to write the value of a floating-point or long analog tag to a holding register, perform the following steps. Using the following field descriptions, add a table entry for each tag to be written and define the register addresses to receive each tag value when the operation executes.
Tag Name

Specify a tag name for a floating-point or a long analog tag containing a value to be written to the device.
Valid Entry: tag name Valid Data Type: float, longana

Logical Station

Enter the number representing the device to which the tag’s value will be written. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.
Valid Entry: previously defined logical station number

Reg. Address

Enter the register address in the device’s memory to which the tag value will be written. Floating-point or long analog tag types are addressed in pairs. The first register in the pair contains the high order word; the second register contains the low order word. Enter the address for only the starting register in a register pair. The companion register is implied.

112 / FactoryLink Device Interfaces Using EDI Technology

WRITING DATA TO A DEVICE | 7 Specifying What to Write and Where to Write It

Try to maintain consistency when using register addresses for floating-point and long analog tag types. Adopt either an odd or even starting register sequence and maintain that sequence. For example, 1, 3, 5, 7, 9,... or 2, 4, 6, 8, 10,.... Do not include the register address prefix (4) or leading zeros. The prefix indicates the register type, which is specified in the Data Type field. For example, for holding register address 400001, just enter 1.
Valid Entry: 1 - 65535

Bit Offset/ MSG Length Data Type

Accept the default of 1.
Valid Entry: 1

Specify HREG as the type of register to which the tag value will be written.
Valid Entry: HREG

Write Message Tag Value to Holding Register To fill out an information table for a request to write the value of a message tag to a holding register, perform the following. Using the following field descriptions, add a table entry for each tag to be written and define the register addresses to receive each tag value when the operation executes.
Tag Name

Specify a tag name for a message tag containing a value to be written to the device.
Valid Entry: tag name Valid Data Type: message

Logical Station

Enter the number representing the device to which the tag’s value will be written.This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.
Valid Entry: previously defined logical station number

Reg. Address

Enter the register address in the device’s memory to which the tag value will be written. Enter the first address in the group of registers to which the value will be written. The number of registers to which the data is to be written is defined in the Bit Offset/MSG Length field of this table.

FactoryLink Device Interfaces Using EDI Technology / 113

• • • •

7 | WRITING DATA TO A DEVICE Specifying What to Write and Where to Write It

Do not include the register address prefix (4) or leading zeros. The prefix indicates the register type, which is specified in the Data Type field. For example, for holding register address 400001, just enter 1.
Valid Entry: 1 - 65535

Bit Offset/ MSG Length Data Type

Specify the number of bytes in the device’s memory to which the tag value will be written.
Valid Entry: 1 - 80

Specify HREG as the type of register to which the tag value will be written.
Valid Entry: HREG

Write Digital Tag Value to Coil Register To fill out an information table for a request to write the value of a digital tag to a coil register, perform the following. Using the following field descriptions, add a table entry for each tag to be written and define the register addresses to receive each tag value when the operation executes.
Tag Name

Specify a tag name for a digital tag containing a value to be written to the device.
Valid Entry: tag name Valid Data Type: digital

Logical Station

Enter the number representing the device to which the tag’s value will be written.This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.
Valid Entry: previously defined logical station number

Reg. Address

Enter the register address in the device’s memory to which the tag value will be written. Do not include the register address prefix (0) or leading zeros. The prefix indicates the register type, which is specified in the Data Type field. For example, for coil address 023451, enter 23451.
Valid Entry: 1 - 65535

114 / FactoryLink Device Interfaces Using EDI Technology

WRITING DATA TO A DEVICE | 7 Specifying What to Write and Where to Write It

Bit Offset/ MSG Length Data Type

Accept the default of 1.
Valid Entry: 1

Specify COIL as the type of register to which the tag value will be written.
Valid Entry: COIL

Write Analog Tag Value to Memory Register To fill out an information table for a request to write the value of an analog tag to a memory register, perform the following. Using the following field descriptions, add a table entry for each tag to be written and define the register addresses to receive each tag value when the operation executes.
Tag Name

Specify a tag name for an analog tag containing a value to be written to the device.
Valid Entry: tag name Valid Data Type: analog

Logical Station

Enter the number representing the device to which the data in this tag will be written.This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.
Valid Entry: previously defined logical station number

Reg. Address

Enter the register address in the device’s memory to which the tag value will be written. Do not include the register address prefix, 6, or leading zeros. The prefix indicates the register type, which is specified in the Data Type field. For example, for memory address 600001, just enter 1.
Valid Entry: 1 - 65535

Bit Offset/ MSG Length Data Type

Accept the default of 1.
Valid Entry: 1

Specify the type of register to which the tag value will be written as XMEMnn where nn is a numeric value from 1 to 10.
Valid Entry: XMEM1 - XMEM10

FactoryLink Device Interfaces Using EDI Technology / 115

• • • •

7 | WRITING DATA TO A DEVICE Specifying What to Write and Where to Write It

Write Analog Tag Value to Global Data Word To fill out an information table for a request to write the value of an analog tag to a global data word, perform the following.
Note

Although global data is considered contiguous in block write tables, you can define register addresses that do not appear contiguous on the information table. For example, if you specify register address 1, 5, 7, 20, and 25 for a write operation, a message is generated for registers 1 through 25. A value of 0 is stored for those registers within the range that do not appear in the read/write information table. Using the following field descriptions, add a table entry for each tag to be written and define the register addresses to receive each tag value when the operation executes.
Tag Name

Specify a tag name for an analog tag containing a value to be written to the device.
Valid Entry: tag name Valid Data Type: analog

Logical Station

Enter the number representing the device to which the data in this tag will be written.This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.
Valid Entry: previously defined logical station number

Reg. Address

Enter the register address in the device’s memory to which the tag value will be written. The first global data word received is always assumed to be word 1, the second is word 2, and so on. If you specify a register address larger than the total number of global data words that will actually be received, an error is generated.
Valid Entry: 1 - 32

Bit Offset/ MSG Length Data Type

Accept the default of 1.
Valid Entry: 1

Specify GLBL to access a global data word.
Valid Entry: GLBL

116 / FactoryLink Device Interfaces Using EDI Technology

WRITING DATA TO A DEVICE | 7 Sample Write Requests

S AMPLE WRITE R EQUESTS
The table entries provided in the following pages illustrate the way in which FactoryLink processes write requests. Sample Triggered Block Write Request This section provides descriptions of some possible Read/Write Control and Read/Write Information table entries for a triggered block write request.
Read/Write Control Table for Triggered Block Write

WRITE is discussed in this example.

In this example, the WRITE table is configured in the following way: • When the value of the digital Block Write Trigger tag MODP_WRITE_TRIGGER is 1, FactoryLink reads the tag configured for this table (in the Read/Write Information table) and writes its value to the configured register address. The block write priority, which is set automatically if you do not enter a value, is set to the default of 1, the highest priority. • When the value of the digital tag MODP_WRITE_DISABLE is 1, FactoryLink disregards the trigger tag, MODP_WRITE_TRIGGER, and does not process the WRITE table.

FactoryLink Device Interfaces Using EDI Technology / 117

• • • •

7 | WRITING DATA TO A DEVICE Sample Write Requests

• Once FactoryLink writes the tag values, it forces a value of 1 to the digital Block Write State tag, MODP_WRITE_STATE, and to the Block Write Complete tag, MODP_WRITE_COMPLETE. During the read operation, MODP_WRITE_STATE is set to 0.
Read/Write Information Table for Triggered Block Write

In this example, when the WRITE block write table is triggered by MODP_WRITE_TRIGGER, FactoryLink writes the value of a message tag, HOLD_MSG1, to holding registers 200 through 230 in the device configured as logical station 0.

118 / FactoryLink Device Interfaces Using EDI Technology

..into 30 holding registers beginning with address 200. FactoryLink writes the value of HOLD_MSG1.. . FactoryLink Device Interfaces Using EDI Technology / 119 .. FactoryLink processes the table. WRITE.WRITING DATA TO A DEVICE | 7 Sample Write Requests How This Triggered Block Write Request Works When the value of MODP_WRITE_TRIGGER is 1.

The table is re-enabled when MODP_EXCEPTION_DISABLE is 0. will only perform this operation when the tag’s value changes. is 1 and the Block Write Trigger tag.• • • • 7 | WRITING DATA TO A DEVICE Sample Write Requests Sample Exception Write Request This section provides descriptions of some possible Read/Write Control and Read/Write Information table entries for an exception write request. The table is disabled when the Block Write Disable tag. MODP_EXCEPTION_TRIGGER is 0. 120 / FactoryLink Device Interfaces Using EDI Technology . In this example. the EXCEPTION table is configured to read the tag configured for this table (in the Read/Write Information table) and write its value to the configured register address. Read/Write Control Table for Exception Write EXCEPTION is discussed in this example. FactoryLink. MODP_EXCEPTION_DISABLE. however.

This table writes the value of HOLD_DIG1 to holding register 140 in the device configured as logical station 0. whenever the value of the digital tag HOLD_DIG1 changes. FactoryLink processes the EXCEPTION table. holding register 140 is updated with the value of HOLD_DIG1 if the value has changed since the table was disabled. If the table is disabled then re-enabled and MODP_EXCEPTION_TRIGGER is set to 1. FactoryLink Device Interfaces Using EDI Technology / 121 .WRITING DATA TO A DEVICE | 7 Sample Write Requests Read/Write Information Table for Exception Write In this example.

. . When the value of MODP_EXCEPTION_ TRIGGER is 1 and the table is disabled. FactoryLink writes the value of HOLD_DIG1 if it has changed since the table was disabled.• • • • 7 | WRITING DATA TO A DEVICE Sample Write Requests How This Exception Write Request Works When the value of MODP_EXCEPTION _DISABLE is 1.FactoryLink writes its value into holding register address 140. Because this is an exception write table. when the value of HOLD_DIG1 changes.. 122 / FactoryLink Device Interfaces Using EDI Technology ... EXCEPTION. FactoryLink does not process the table.

is not used in this table. (The Block Write Disable tag. its value remains 0. Read/Write Control Table for Combination Write EXCEPTION is discussed in this example. MODP_EXCEPTION_TRIGGER will trigger FactoryLink to read the tag configured for this table (in the Read/Write Information table) and write its value to the configured register address. FactoryLink Device Interfaces Using EDI Technology / 123 .) • After startup. the EXCEPTION table is configured in the following way: • When FactoryLink starts up. therefore. In this example.WRITING DATA TO A DEVICE | 7 Sample Write Requests Sample Combination Write Request This section provides descriptions of some possible Read/Write Control and Read/Write Information table entries for a combination write request. MODP_EXCEPTION_DISABLE. FactoryLink only writes the tag’s value to the device when it changes.

• • • • 7 | WRITING DATA TO A DEVICE Sample Write Requests Read/Write Information Table for Combination Write In this example. when FactoryLink starts up and whenever the value of the analog tag HOLD_ANA1 changes. This table writes the value of HOLD_ANA1 to holding register address 200 in the device configured as logical station 0. FactoryLink processes the EXCEPTION table. 124 / FactoryLink Device Interfaces Using EDI Technology .

. whenever the value of HOLD_ANA1 changes. when FactoryLink starts up and forces MODP_EXCEPTION_TRIGGER to 1.. it writes the value of HOLD_ANA1 to the device.. .WRITING DATA TO A DEVICE | 7 Sample Write Requests How This Combination Write Request Works Because a block write trigger is defined. ... Because this is an exception write table.... FactoryLink Device Interfaces Using EDI Technology / 125 .FactoryLink writes its value into holding register address 200.

• • • • 7 | WRITING DATA TO A DEVICE Sample Write Requests 126 / FactoryLink Device Interfaces Using EDI Technology .

These techniques involve the order in which you specify read and write table entries. and methods of triggering the tables and tags defined in the Read/Write Control table. • FactoryLink Device Interfaces Using EDI Technology / 127 . specification of the priority in which the task processes read and write operations.Chapter 8 • • • Application Design Tips and Techniques This chapter describes application tips and techniques that can improve the throughput and efficiency of data communications between the EDI task and the devices in your configuration. The concepts discussed. however. others are for a fictitious protocol module called Widget. apply to all the protocol modules in the FactoryLink base set. Note Many of the configuration tables used in the examples throughout this section are for the Modbus Plus protocol module.

The fewer messages FactoryLink must generate to process a table. • Contiguous Addresses – keep data being read from or written to contiguous or near contiguous addresses together. • The data is read from or written to contiguous addresses. 128 / FactoryLink Device Interfaces Using EDI Technology . if the following conditions are met. that is. If your goal is to minimize the number of messages generated. the faster the table is processed. • The data is of the same protocol-specific data type. • Data Types – keep like data types (FactoryLink and protocol-specific) together. • The data is stored in tags of the same FactoryLink data type. For example. When grouping table entries. do not define more than one logical station in a table. for best results. The figures below illustrate tables in which all or some of these conditions are met. FactoryLink can process a table in one message: • The table only contains data of an amount not exceeding the maximum size the device can handle for one transmission. keep the following types of information together: • Logical Stations – keep data being read from or written to a particular logical station together.• • • • 8 | APPLICATION DESIGN TIPS AND TECHNIQUES Grouping of Data G ROUPING OF D ATA Carefully consider the way in which you group data in a read or write table because it can determine the number of messages or packets of data FactoryLink needs to generate to complete the operation. Tip Naturally. Any break in data type results in the generation of an additional packet. attempt to group read and write table entries the same way in which FactoryLink internally groups and processes them. all conditions cannot be met for each table you define.

FactoryLink must generate two messages.APPLICATION DESIGN TIPS AND TECHNIQUES | 8 Grouping of Data All four conditions are met in the following read table: Read Operation Completed in One Message FactoryLink would only need to generate one message to process this table because conditions 1 through 4 are met. 2. Read Operation Completed in Two Messages FactoryLink would need to generate two messages to process this table: one to read the specified holding registers and another to read the memory registers. FactoryLink Device Interfaces Using EDI Technology / 129 . only conditions 1. and 4 are met. To process this table. In the read table illustrated below.

• • • • 8 | APPLICATION DESIGN TIPS AND TECHNIQUES Processing Differences in Read and Write Operations P ROCESSING D IFFERENCES IN R EAD AND WRITE O PERATIONS FactoryLink processes data being read differently than it processes data being written. Processing of Read Operations Addresses defined in a read table that contain the same data type are read based on the specified range. The difference is in how FactoryLink handles the range of addresses specified for a single transmission. but only the values at addresses 201 and 208 are stored in tags. the table illustrated below reads all addresses in the range 201 to 208 but only stores values read from addresses 201 and 208. 130 / FactoryLink Device Interfaces Using EDI Technology . Table That Reads an Address Range but Stores Selected Values FactoryLink generates one message to process this table. All data at addresses ranging from 201 to 208 are read. FactoryLink reads the data at all addresses in the range (provided the range is within the limit for a single transmission) but only stores the data it needs. For example.

as shown below. If the same entries made in the read table “Table That Reads an Address Range but Stores Selected Values” are made in a write table. in the previous tables. you would need to define each address separately. Both Tables Read the Same Addresses Processing of Write Operations In a write table.APPLICATION DESIGN TIPS AND TECHNIQUES | 8 Processing Differences in Read and Write Operations Note that. each row generates a separate message resulting in two messages being sent to the device. the data FactoryLink reads is identical. To send a message to write to addresses 201 through 208. as shown in the first table of the following graphic. as shown in the second table of the following graphic. Only contiguous groups of data (up to the maximum allowed by the device) are put in one message for a write operation. Each table results in FactoryLink reading addresses 201 through 208. addresses to which FactoryLink data is to be written are not accessed based on range unless the addresses are contiguous. The difference in the tables is the data FactoryLink stores in tags. FactoryLink Device Interfaces Using EDI Technology / 131 . One table stores eight of the values read. the other table stores only two values.

FactoryLink generates one message to process this table. 132 / FactoryLink Device Interfaces Using EDI Technology .• • • • 8 | APPLICATION DESIGN TIPS AND TECHNIQUES Processing Differences in Read and Write Operations Table That Sends Four Messages to Four Addresses FactoryLink generates two messages to process this table.

you could assign priority 1 or 2 to tables containing more important data and priority 3 or 4 to tables containing less important data. FactoryLink Device Interfaces Using EDI Technology / 133 . or when an exception write table contains tag names for rapidly changing tags. The priority of an operation can range from 1 to 4. The priority 1 queue is polled the most frequently and the priority 4 queue is polled the least frequently. assign a high priority to an exception write table for an operation that acknowledges a loud annoying alarm.APPLICATION DESIGN TIPS AND TECHNIQUES | 8 Specifying Priority S PECIFYING P RIORITY The Read/Write Control table contains two columns for specifying the priority of block reads and block or exception writes: Block Read Priority and Block Write Priority. you would. When an application contains a large number of tables. The queues are polled for tables according to the rank of the priority. the priority 1 queue can fill up. and a low priority to a block write table that downloads a batch recipe once a day. When shared memory is full. These values correspond to four first-in/first-out (FIFO) priority queues which are set up in order of importance. for instance. All tables are placed by default in the priority 1 queue. which is appropriate in most cases. Using this logic. O VERTRIGGERING Overtriggering occurs when tables are being placed in shared memory faster than the EDI task or protocol module can pull the tables out and process them. Every table is eventually processed but the ones in the priority 4 queue are not processed as often as the tables in the priority 1 queue. To more evenly distribute tables across the four priority queues (thus reducing the priority 1 queue’s burden of handling all the pending I/O requests). an additional request to place a table in it results in the generation of an error message reporting an overtriggered state. Priority queue 1 has the highest priority. however.

The use of prime numbers quickly solves this problem. a 15-second. Timed The basic way to trigger a block read or write operation is with a timed tag. enter a tag name for a Block Read Trigger or Block Write Trigger tag in the Read/Write Control table that matches the tag name of an interval timer tag (defined in the Interval Timer Information table). Each table is placed in its designated queue every 30 seconds when the various triggers line up. however. can solve potential overtriggering situations in many cases. For instance. the timed method works best for tables that do not need to be updated at the highest possible rate. These methods. might not be appropriate for every read or write table you define. if the trigger rate causes tables to be placed into shared memory faster than EDI or the protocol module can process them. A situation in which triggers overlap can occur as well. that table is not triggered 134 / FactoryLink Device Interfaces Using EDI Technology . If you define this tag to change once per second. suppose 5-second. In the Read/Write Control table. which are reset to 1 after EDI processes the table. Cascaded The cascading of tables is an alternative to using timed triggers. however. An overtriggering situation can occur. and a 30-second timed tags are used to trigger various tables.• • • • 8 | APPLICATION DESIGN TIPS AND TECHNIQUES Efficient Triggering E FFICIENT TRIGGERING To design your application for optimum performance and avoid overtriggering. the table is placed in its shared memory once each second. It uses the Block Read State and Block Write State tags. but a more effective method follows. consider the following triggering techniques. if either the complete or state tag is defined as the trigger tag for the table in the row below the current table. cascaded and self-triggered. For example. Note The next two triggering methods. Using timed tags as triggers is acceptable in most cases. To define a timed trigger tag.

Since r1_state is defined as the read trigger for the READ2 table. A table is placed into shared memory only after the previous table is processed. READ2 is the next table triggered. If you use the Block Read Complete or Block Write Complete tag to perform the cascade. If you use the Block Read State or Block Write State tag to perform the cascade. The following graphic illustrates a series of read tables created using the cascading technique. but overtriggering is prevented. If the table defined in the final row of the Read/Write Control table contains a tag name for a complete or state tag that matches the tag name of the trigger tag for the table defined in the first row. Consequently. is forced back to 1. This endless loop results in the sequential processing of tables at an optimal rate. Regardless of communications. the completion of the final table triggers the first table. the value of the state tag for that table does not change.) FactoryLink Device Interfaces Using EDI Technology / 135 . (A time-out error occurring somewhere in the loop slows the performance of the cascade. In this case. If a table is to be placed into shared memory that has become full. r1_state. When the READ1 table is processed. the loop continues to process. the next table is not triggered until room is available in shared memory for the current table. its state tag.APPLICATION DESIGN TIPS AND TECHNIQUES | 8 Efficient Triggering and placed into shared memory until the preceding table is processed. the successful processing of a table prior to the next table in the loop being triggered is not guaranteed. the next table in the loop is placed into shared memory after the previous table is successfully communicated. This type of table setup is also referred to as a “daisy chain” of tables. successful processing of the transaction is guaranteed.

When the complete or state tag is set again as a result of the operation. because a table destined for a device is placed into shared memory only after the previous table is processed. the fastest rate at which the tables can be placed into queues is naturally set by the tables themselves. this scenario represents a timer-initiated cascade. In a self-triggered table. Overtriggering does not occur with a self-triggered table. the complete or state tag is automatically set to 1. a state or complete tag serves as a Block Read Trigger or Block Write Trigger tag for the table in which it is defined. one tag name is defined for both the trigger tag and the complete or state tag in a single table: When FactoryLink starts.2-second timed digital tag is used as the same trigger tag for a number of tables. shown below. creates the cascaded triggering effect.• • • • 8 | APPLICATION DESIGN TIPS AND TECHNIQUES Efficient Triggering A parallel between timed and cascaded triggering further illustrates this method’s effectiveness. For example. To restart after the disable tag is set to 0 again. If each instance of the timed tag is replaced by a tag that. Self-Triggered The use of self-triggered tables can increase the throughput and efficiency of read and write operations. the tables are processed sequentially (starting with the beginning row of the table) on each occurrence of the trigger. Essentially. the application can trigger the tables without the overtrigger message appearing. Note The continuation of a cascaded loop or self-triggered table ceases if the Block Read Disable or Block Write Disable tag is set to 1. rather than a state or complete tag serving as a trigger for the next table in a cascaded loop. 136 / FactoryLink Device Interfaces Using EDI Technology . If you have defined this same tag as the trigger tag. When the same timed trigger tag is used to trigger each of several tables defined in the Read/Write Control table. the table is also placed in its priority queue at startup. experimentation determines that when one 3. the Block Read Trigger or Block Write Trigger tag must be reset to 1. when combined with other tags. the cycle starts over and the table is placed in its priority queue again (because the complete or state tag is also the trigger). In other words.

selftrig (as a state tag) is set to 1. selftrig (as a state tag) is set to 1. When the state tag. selftrig (as a trigger tag) never gets set for queuing the table again. At FactoryLink startup. If selftrig (as a state tag) remains 0 because the table does not complete successfully. selftrig also places the R_AGAIN table into queue 1 at startup. is set to 1. During processing of the R_AGAIN table. selftrig (as a state tag) is set to 0.APPLICATION DESIGN TIPS AND TECHNIQUES | 8 Efficient Triggering The following graphic illustrates the methodology of a self-triggered read table that uses the state tag to self trigger. selftrig. If the table completes successfully (the data is read then stored in the tags defined in the Read/Write Information table). As a trigger tag. the table is placed into its queue again because selftrig is also the trigger tag. FactoryLink Device Interfaces Using EDI Technology / 137 .

• • • • 8 | APPLICATION DESIGN TIPS AND TECHNIQUES Efficient Triggering 138 / FactoryLink Device Interfaces Using EDI Technology .

see “EDI Flowcharts” on page 140. • FactoryLink Device Interfaces Using EDI Technology / 139 . • For a series of flowcharts to assist you in identifying and solving problems with EDI. and correct problems with EDI and the device task.Chapter 9 • • • Testing and Troubleshooting This chapter contains information to help you prevent. identify. The sections included are listed below. • For information about configuring and testing a simple triggered read table. see “Verifying Proper Communications” on page 144.

140 / FactoryLink Device Interfaces Using EDI Technology .• • • • 9 | TESTING AND TROUBLESHOOTING EDI Flowcharts EDI F LOWCHARTS Use the following flowcharts to identify and solve problems with your FactoryLink application configured for the EDI task.

TESTING AND TROUBLESHOOTING | 9 EDI Flowcharts Basic Troubleshooting FactoryLink Device Interfaces Using EDI Technology / 141 .

• • • • 9 | TESTING AND TROUBLESHOOTING EDI Flowcharts Common Errors 142 / FactoryLink Device Interfaces Using EDI Technology .

TESTING AND TROUBLESHOOTING | 9 EDI Flowcharts Testing Your Application FactoryLink Device Interfaces Using EDI Technology / 143 .

You will watch the activity of this tag in RTMON to verify it is being updated. or on. 144 / FactoryLink Device Interfaces Using EDI Technology . address 140 in the device configured as logical station 1). VALUE1) to hold the value read from a known address in one of the devices in your configuration (in the sample table. as shown in the following example. RTMON. 2 In the read table.• • • • 9 | TESTING AND TROUBLESHOOTING Verifying Proper Communications VERIFYING P ROPER C OMMUNICATIONS To ensure the device can properly communicate with FactoryLink. • A tag (in the sample table. define: • A trigger tag (in the sample table. perform the following steps: 1 Configure two tables: a triggered read table and an exception write table. using the FactoryLink Real-Time Monitor. TEST_RTRIG) you will manually force to 1.

The next steps in the procedure involve the use of the FactoryLink Real-Time Monitor. If the value read differs from the tag’s current value. see the Fundamentals Guide. You can watch the value of the trigger change in the watch list. the tag defined to hold the value read (VALUE1 in the sample table) is updated with the current value of the specified register address. To create a watch list. you will see it change in the watch list. use the Watch option on the RTMON Options menu. 4 In RTMON..its value in the watch list changes from 0to 1.. . create a watch list containing the tags defined in the two tables (TEST_RTRIG. VALUE1..TESTING AND TROUBLESHOOTING | 9 Verifying Proper Communications 3 In the write table... When the triggered read table is processed. You will change this tag’s value in RTMON to prompt the processing of this table. When you force the read trigger to 1. 5 Prompt the processing of the triggered read table by forcing a 1 to the read trigger using the Tag Input option on the RTMON Options menu. the value of VALUE1 is updated. For detailed instructions on using RTMON. define a tag (in the sample table. FactoryLink Device Interfaces Using EDI Technology / 145 . When the read table is triggered. and VALUE2 in the sample tables). VALUE2) to hold a value that will be written to the same address configured in the read table.

P ROGRAM A RGUMENTS Argument Description -C or -c -S<#> or –s<#> -Q<#> or –q<#> Clear change. When you change the tag value in this way. the exception write table is processed and the value is written to the specified register address. Set IPC data size (# = 65535 to 1048576) set queue size (# = 128 to 4096) 146 / FactoryLink Device Interfaces Using EDI Technology .• • • • 9 | TESTING AND TROUBLESHOOTING Program Arguments Use RTMON to prompt FactoryLink to process the exception write table. Tag Input. This argument prevents the ping-pong effect of a read immediately after an exception write causing another exception write when a table is defined as both block read and exception write. Warning: Use this argument with extreme caution. Change the value of the tag to be written (VALUE2 in the sample table) using the same option you used to trigger the read table.

and the devices in your server application configured for FactoryLink communications. FactoryLink generates and displays messages for the EDI task. To view the stored messages.Chapter 10 • • • Messages and Codes During normal operations and upon detecting an error condition. These messages are briefly displayed on the Run-Time Manager screen. you define database tags to which the messages are written when they occur. as well as a descriptive list of the potential messages FactoryLink can generate and display for EDI at startup and while an application is running. For FactoryLink to store system messages. This chapter explains the formats for system messages. see the protocol-specific reference chapter. These database tags are configured in the Logical Station Control and Information tables. the device protocol module. you configure these tags as graphic objects using Client Builder. • FactoryLink Device Interfaces Using EDI Technology / 147 . For descriptions of protocol module messages.

and how the line format translates to the tag format. see “Messages” on page 150. is the logical station number assigned to the physical station experiencing the error. 148 / FactoryLink Device Interfaces Using EDI Technology . the tag message format for displayed messages. For example. this message LPORT:000 LSTA:02 ER:02 TBL:03 PKT:02 means an error code 2 occurred for port 0. is the number of the message packet experiencing the error. For descriptions of the FactoryLink EDI messages containing this information. involving the third table in the Read/Write Control table for the second message packet generated. These messages can contain the following information: LPORT:xxx LSTA:xx ER:xxxx TBL:xxx PKT:xxx where LPORT:xxx LSTA:xx ER:xxxx TBL:xxx PKT:xxx is the logical port number assigned to the physical port experiencing the error. is the number of the read or write table experiencing the error. is an error code in decimal format.• • • • 10 | MESSAGES AND CODES Message Formats M ESSAGE F ORMATS This section contains a description of the Run-Time Manager line format for EDI and protocol module messages. EDI Run-Time Manager Line Format Messages that report normal operations and error conditions in read and write operations are displayed on the EDI line of the Run-Time Manager screen. See the protocol-specific reference chapter for details on the error code generated. logical station 2.

nnnn where n: is the number assigned to the logical port causing the message. In a message tag. the LPORT field of an EDI Run-Time Manager message is stored in the following format: Lsta n: MessageText. For example: Lsta 2: Read Response Error. nnnn is the code number assigned to the message generated.MESSAGES AND CODES | 10 Message Formats Tag Message Format To capture these Run-Time Manager messages for viewing on an application screen. 0x03 FactoryLink Device Interfaces Using EDI Technology / 149 . A message tag is defined in the Logical Station Control table.) To view the contents of a message tag on an application screen. MessageText is a description of the condition causing the error. see the protocol module reference chapter. (This tag is not available for the OMRON protocol module. you define the tag as a graphic object using Client Builder. For information about the protocol-specific codes. you can log them to message tags.

EDI Messages The following messages report operations and error conditions specific to EDI. This section describes each type of message. This is only an information message. “Run-Time Application Messages. Abnormal shutdown of EDI drivers Cause: A protocol module was experiencing an error at the time the EDI task was shutting down. These messages appear opposite the Shared Task description for EDI in the message area under Last Message. In messages you see in your server application. messages generated by the device protocol module are displayed on the system monitor as the conditions prompting each message occur. Action: None. • EDI Messages – system messages generated by the EDI task at run time are displayed on the Run-Time Manager screen. • Startup Messages – during the startup of a FactoryLink application.” in a flowchart that describes how to respond to some common error messages generated and displayed by the EDI task. information in Italics will be replaced by information specific to your application (for example.” in the protocol-specific reference chapter. the directory where your FactoryLink application resides is referred to as FLAPP. For information about these messages. “Testing and Troubleshooting. The information in Italic text in the message descriptions varies depending on certain factors. port or table number). 150 / FactoryLink Device Interfaces Using EDI Technology . see the section. messages generated by the device protocol module are displayed on an application screen.• • • • 10 | MESSAGES AND CODES Messages M ESSAGES FactoryLink can generate and display various types of messages during the start up of an application or while the application is running. • Run-Time Application Messages – while the FactoryLink application is running. Some of the messages described in this chapter can also be found in Chapter 9. In the message descriptions.

or the External Device Definition table may not have any entries. Action: Delete the files from FLAPP\DCT and restart FactoryLink. Action: Verify the External Device Definition tables are correct and contact your system administrator.DCT file generated by the EDI task for the specified logical port and Read/Write table is corrupt. Bad 'DCT' file filename Cause: Internal error. Bad read on file filename Cause: A read operation on the named file failed. Action: See the description for the hexadecimal number that is displayed after err: in the protocol-specific reference chapter for information about correcting the error. Action: None.DCT files.DCT file is corrupt. Block rd n block wr n excpt wr n unsol n Cause: The EDI task is displaying the total number of communication transactions configured for each type of operation defined in the .MESSAGES AND CODES | 10 Messages Bad block 'DCT' file. This is only an information message. Bad return code from operation err:hexcode Cause: A program error occurred.CT Cause: The file may be corrupt or absent. LPORT logical port table table Cause: The block . Action: Ensure the External Device Definition table is configured and the entries are correct. Action: Delete the files from FLAPP\DCT and restart FactoryLink. The specified . Can’t open EDI_DEV. FactoryLink Device Interfaces Using EDI Technology / 151 .

For example. If this does not solve the problem. enter SYSCOM for serial communications. 152 / FactoryLink Device Interfaces Using EDI Technology . A spawn of the protocol module was attempted but failed. or has not been created. Action: In the Function field on the External Device Definition table. Action: Verify the External Device Definition tables are correct and contact your system administrator. Action: Verify the External Device Definition table entries are correct. Error opening port definition file Cause: One of the necessary port definition files for the EDI task either does not exist or is corrupt. Can’t spawn system unit task for LPORT logical port Cause: The Function field of the External Device Definition table contains an invalid entry. Action: In the External Device Definition table. Action: Verify the system has the correct task protection bit configured. Error opening device definition file Cause: One of the necessary device definition files for the EDI task either does not exist or is corrupt. EDI task: Can’t obtain task number Cause: The wrong option bit was detected. define the appropriate logical port to be used for read and write operations. contact Customer Support. Can’t resolve IPC for LPORT logical port Cause: The EDI task was unable to allocate shared memory for the specified logical port. enter the appropriate communication type. Action: Verify the External Device Definition table entries are correct.• • • • 10 | MESSAGES AND CODES Messages Can’t open file filename Cause: This may be a log file that is opened by another process.

FactoryLink Device Interfaces Using EDI Technology / 153 . Action: The error code specified after err is associated with the port. Error reading port definition Cause: A necessary port definition file for the EDI task is corrupt. Invalid operation to uninitialized LPORT logical port Cause: The EDI task could not perform a read or a write operation because the specified logical port has not been defined. See the description for the hexadecimal number that is displayed after err in the protocol-specific reference chapter for information about correcting the error. and packet indicated. Action: Verify the External Device Definition table entries are correct. Action: None. External Device Interface startup Cause: The EDI task is starting up normally. LPORT logical port connected Cause: This logical port has successfully connected to a device. This is only an information message.MESSAGES AND CODES | 10 Messages Error reading device definition Cause: A necessary device definition file for the EDI task is corrupt. This is only an information message. LPORT logical port connecting Cause: This logical port is connecting to an external device. Action: None. station. Action: Define the logical port number specified. LPORT logical port LSTA logical station err hexcode table table pkt:packet Cause: An error occurred during a read or write operation to the specified logical station. This is only an information message. Action: Verify the External Device Definition table entries are correct. Action: None. table.

No reads.DCT files were not properly built. Cause: The EDI task does not recognize any read or write operations because the . If necessary. Normal shutdown Cause: The EDI task is shutting down in response to a normal FactoryLink termination request. Action: None. 154 / FactoryLink Device Interfaces Using EDI Technology .• • • • 10 | MESSAGES AND CODES Messages LPORT logical port disconnected Cause: This logical port has successfully disconnected from a device. Action: Verify the entries in the External Device Definition table and device-specific configuration tables and correct as needed. Action: None.DCT files were built. Action: Create a read or write table. Action: None. Action: Check the FLAPP\DCT directory to verify the . Cause: The EDI task does not recognize any read or write operations they are not defined. Grant these privileges if necessary. This is only an information message. execute EDISTART -R -V to regenerate the files. LPORT logical port disconnecting Cause: This logical port is disconnecting from a device. This is only an information message. Cause: The EDI task does not recognize any read or write operations because the task is unable to read the FLAPP\DCT directory. Action: Verify the FLAPP\DCT directory has read and write privileges. This is only an information message. no writes >>> nothing to do Cause: The EDI task does not recognize any read or write operations because the configuration tables contain incorrect entries.

This is only an information message. Action: None.DCT file. FactoryLink Device Interfaces Using EDI Technology / 155 . WARNING: n of TBL: n DEV: n refused Cause: The EDI task was unable to allocate shared memory to process the specified read or write operation. Action: Define the logical port number specified. see the description for the hexadecimal number that is displayed after err: in the protocol-specific reference chapter for information about correcting the error. Action: None.CT file and packetizing information from the specified internal . This is only an information message. This is only an information message.MESSAGES AND CODES | 10 Messages Out of RAM EDI task function Cause: The EDI task cannot perform the specified function because the system has run out of memory. Action: Increase the amount of virtual memory. Processing DCT filename Cause: The EDI task is reading the preconfigured . Action: None. Termination flag acknowledgment Cause: The EDI task is shutting down normally. Send of operation failed LPORT logical port err:hexcode Cause: The EDI task was unable to perform a read or a write operation on the specified logical port because the port was not properly defined. If this does not solve the problem.

nn Cause: The protocol module has started up successfully.nn protocol module EDI Module Ver: n. This is only an informational message. Action: Install the option bit. These messages display as shown. protocol module: Protection bit failure Cause: The option key is missing the protocol-specific option bit. Action: None. not in error code or message format. Action: Install the required option bits in the master key. protocol module: Software Protection bit failure. bits (x) and number (y) required Cause: One or both of the option bits (where x and y are decimal values) required to run this protocol module are missing. FactoryLink Ver: n EDI Ver: n. the device protocol module can generate messages and display them on the console.• • • • 10 | MESSAGES AND CODES Messages Start-Up Messages During FactoryLink application startup. 156 / FactoryLink Device Interfaces Using EDI Technology .

Chapter 11 • • • Allen-Bradley This chapter contains information needed to set up and configure bidirectional communications between the FactoryLink real-time database and the following devices. • FactoryLink Device Interfaces Using EDI Technology / 157 . open Device Interfaces > Allen-Bradley. either directly or through the Allen-Bradley Data Highway protocol: • PLC-2 • PLC-3 • PLC-4 • PLC-5 • PLC-250 • PLC-1774 In your server application.

8 (default=8) Stop Bits Enter the number of bits sent after a character to create a pause before the start of the next character. defined in the External Device Definition table Logical Port column. Refer to the device manufacturer’s documentation for details. Valid Entry: none. to represent a particular communication path to a device. 2 (default=1) 158 / FactoryLink Device Interfaces Using EDI Technology . Refer to the device manufacturer’s documentation for details. This entry must match the configuration of the devices communicating via this port. Logical Port Enter a number. This entry must match the configuration of the devices communicating via this port. you must complete the External Device Definition table. This entry must match the baud rate configuration of the devices. This entry must match the configuration of the devices communicating via this port. Refer to the device manufacturer’s documentation for details. Valid Entry: 1.• • • • 11 | ALLEN-BRADLEY Configuring the Logical Station Control Table C ONFIGURING Note THE L OGICAL S TATION C ONTROL TABLE Before completing the protocol-specific Allen-Bradley configuration tables.115200 (default=9600) Parity Enter the parity error correction during transmission via this logical port. odd (default=none) Data Bits Enter the number of data bits used during transmission via this logical port. See “Identifying Protocol Types and Defining Logical Ports” on page 58 for details. even. Valid Entry: 110 . Open the Logical Station Control Table. Valid Entry: previously defined logical port number Baud Rate Enter the speed at which the protocol module communicates with the devices linked to FactoryLink via this logical port. Refer to the device manufacturer’s documentation for details. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. Valid Entry: 7.

) Duplex LRC Error Detection Enter the type of Allen-Bradley protocol support. CRC (default=CRC) Retry Request (For use with BCC longitudinal error checking only. BCC. the protocol module will wait to receive a response to a read or write command before timing out.32767 (default=10) FactoryLink Device Interfaces Using EDI Technology / 159 .) Enter the maximum number of times the protocol module will retry a read or write command to a device communicating through this logical port if the command response is invalid or is not received.001 Sec ENQ Retry Count Enter the length of time in milliseconds to wait for link-level response (ACK/NAK) from the asynchronous interface. Some older Allen-Bradley Data Highway interface modules may require their Data Highway address. Valid Entry: 0 .ALLEN-BRADLEY | 11 Configuring the Logical Station Control Table Response Timeout 0. Valid Entry: B. enter 0. C. Ensure that the communication device matches the setting you choose. If you specify no setting. You must enter a value greater than 0 for the protocol module to timeout.32767 (default=3) LINK Timeout 0. in tenths of seconds.1 sec Enter the length of time. Valid Entry: 0 . the LRC error detection defaults to CRC. Valid Entry: 0-9999 (default=55) Data Highway I/F Address (Octal) Enter the address of the asynchronous communications module on the Data Highway. Valid Entry: full (default) Enter the type of longitudinal range error checking used by the Allen-Bradley asynchronous communications interface.377 (unless specifically required by the Data Highway interface.65536 (default=150) Enter the number of times for the EDI task to re-send ENQs after a timeout before aborting a request. Valid Entry: 0 . Valid Entry: 0 . Most current modules accept or require 0.

The EDI task will store communications error messages associated with this logical port in a message tag.1 sec Data Highway I/F address (OCTAL) Entry 0 9600 NONE 8 1 55 0 160 / FactoryLink Device Interfaces Using EDI Technology . Define the data type (message) for any tag names displayed in the Tag Definition dialog box. click the Save icon to validate the information.5-second response timeout. For information about displaying the text stored in a Status Msg Tag tag for an operator using this application. LRC Error detection is CRC. The following table provides sample entries for the Allen-Bradley Logical Station Control table. The Data Highway I/F address is 0. 1 stop bit. In this example. and a 5. Valid Entry: 0 . Valid Entry: tag name Valid Data Type: message When the table is complete.• • • • 11 | ALLEN-BRADLEY Configuring the Logical Station Control Table NAK Retry Count Enter the number of times for the EDI task to retransmit a send request after receipt of a negative acknowledgment (NAK) before aborting the request. no parity. AB_LPORT0_MSG Field Logical Port Baud Rate Parity Data Bits Stop Bits Response Timeout 0. using FULL duplex. the retry request is 3 with a link timeout of 150 seconds. 8 data bits. logical port 0 is configured for a baud rate of 9600. The ENQ Retry count is 10 and the NAK Retry Count is 3.32767 (default=3) Status Msg Tag Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. see the Application Editor for ECS Graphics Guide.

001 sec ENQ Retry Count NAK Retry Count Status Msg Tag Entry FULL CRC 3 150 10 3 AB_LPORT0_MSG FactoryLink Device Interfaces Using EDI Technology / 161 .ALLEN-BRADLEY | 11 Configuring the Logical Station Control Table Field Duplex LRC Error Detection Retry Request Link Timeout 0.

Later. Valid Entry: PLC (valid for 1774-PLC and PLC-4). you will enter this logical station number in a read or write table to represent the device defined in this row. For some Data Highway types. Valid Entry: 0 . PLC-250 Station Address (Octal) Enter the physical Data Highway address of the Allen-Bradley device. In a read or write table.999 Device Type Enter the type of Allen-Bradley device to which communications are to be directed. PLC-3.• • • • 11 | ALLEN-BRADLEY Configuring the Logical Station Information Table C ONFIGURING THE L OGICAL S TATION I NFORMATION TABLE From the Logical Station Control table. For information about displaying the codes stored in an Error/Status Tag Name tag for an operator using this application. Error/Status Tag Name (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station). Complete a row for each device to communicate through this logical port. A logical station represents the combination of a logical port with a physical station. Valid Entry: 0 .377 (octal) Comment (Optional) Enter reference information about this logical station. Assign a unique number to each device communicating through this logical port. PLC-2 (also valid for 1774-PLC and PLC-4). see the ECS Graphics and WebClient Reference Guide. select the row for the logical port you are configuring and open the Logical Station Information table. Valid Entry: tag name Valid Data Type: analog Logical Station (Decimal) Enter a number to identify the logical station to which the information in this row pertains. For further information about valid addresses for a specific Data Highway type. some addresses may be invalid. this number identifies the device to or from which data is to be sent or received. refer to the Allen-Bradley documentation. Valid Entry: alphanumeric string of up to 21 characters 162 / FactoryLink Device Interfaces Using EDI Technology . PLC-5.

ALLEN-BRADLEY | 11 Configuring the Logical Station Information Table When the table is complete. logical station 0 is a PLC-5 on logical port 0. In this example. is configured to hold port errors for logical station 0. The following table provides sample entries for the Allen-Bradley Logical Station Information table. click the Save icon to validate the information. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box. The analog tag defined in the Error/Status Tag Name field. AB_STATION0_STATUS. Field Error/Status Tag Name Logical Station (Decimal) Device Type Station Address (OCTAL) Comment Entry AB_STATION0_STATUS 0 PLC-5 1 FactoryLink Device Interfaces Using EDI Technology / 163 . with a data highway address of 1.

Define one request (table) per line and do not include spaces in the name. Complete a row for each read or write table. see “Application Design Tips and Techniques” on page 127. the data is stored in the specified tag and the change-status indicator is automatically set to 1. regardless of whether the current value matches the new value. You can define as many tables as available memory allows. enter YES or FORCE. accept the default of NO. no. the change-status indicator is unaffected. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). If the current value of the tag is equal to the new value. If you enter FORCE. If you enter YES. EDI will interpret this operation as an unsolicited read and emulate the device’s addressing structure based on entries you make in the Read/Write Information table. Table Name Give this read or write request a name. Tip For information about triggering schemes using tags defined in this table.• • • • 11 | ALLEN-BRADLEY Configuring the Read/Write Control Table C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Next. the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. If this is an unsolicited read operation. however. open the Allen-Bradley Read/Write Control. Valid Entry: yes. Try to make the table name reflective of the operation it represents. it will overwrite the current value and the tag’s change-status indicator will be set to 1 (ON). the incoming data will be stored in the tag represented by the tag name specified in the Read/Write Information table. If this is a triggered read or a block write table. The incoming data will be stored in the real-time database as specified in this field. force (default=no) 164 / FactoryLink Device Interfaces Using EDI Technology . If a different value is being stored the tag. Valid Entry: alphanumeric string of up to 16 characters Unsolicited Read For EDI to interpret this operation as a triggered block read or as a write operation.

If EDI receives two requests at the same time.ALLEN-BRADLEY | 11 Configuring the Read/Write Control Table Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. Do not define these tags for unsolicited read operations or for write operations. The highest priority is 1. Block Read Disable. and Block Read State tags apply only to triggered read operations. relative to other read operations. an internal change-status indicator within the tag containing the data to be written prompts the write operation. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). Valid Entry: yes. it processes the request with the highest priority first. EDI writes this tag’s value to the device. accept the default of NO. In an exception write. Any tag specified will be written to the device in its own packet (message) each time it changes. Defining tags that change value frequently as exception writes can slow down communications or result in an error message. For EDI to interpret this operation as an exception write and write tag values to the device only when those values change. FactoryLink Device Interfaces Using EDI Technology / 165 . enter a number to indicate the priority of this table. enter YES. no (default=no) Tip Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. accept the default of 1. This field defaults to 1 regardless of whether the operation being defined is a block read. Block Read Priority If this is a block read operation. This number influences the order in which the EDI task handles the queuing of block read requests. The default is 1. If this is an unsolicited read or a write operation.4 (default=1) Note The Block Read Trigger. Valid Entry: 1 . Block Read Complete.

even when the block read trigger is set to 1. this field is optional. If you need a digital tag to disable a block read of the tags specified in this table. enter a tag name. If this is a triggered read operation. enter a tag name. the Block Read Trigger tag must be toggled or forced to 1. ignore this field. Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. If this is a triggered read operation. this field is required. Valid Entry: tag name Valid Data Type: digital Tip This tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered. set this tag back to 0 (OFF). Do not use this tag when more than one logical port is specified in a single table. Valid Entry: tag name Valid Data Type: digital 166 / FactoryLink Device Interfaces Using EDI Technology . Block Read Complete If this is an unsolicited read or a write operation. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. ignore this field. this field is optional. To re-enable a cascaded loop or a self-triggered read table. the read operation is not executed. however. See “Application Design Tips and Techniques” on page 127 for further details. The triggering cycle will cease upon disabling. ignore this field.• • • • 11 | ALLEN-BRADLEY Configuring the Read/Write Control Table Block Read Trigger If this is an unsolicited read or a write operation. When this tag’s value is forced to 1 (ON). If this is a triggered read operation. To reenable a block read table that is disabled. Valid Entry: tag name Valid Data Type: digital Block Read Disable If this is an unsolicited read or a write operation. the addresses are read. This tag is forced to 1 (ON) at startup. If you need a digital tag to indicate when this operation is complete. the complete tag is forced to 1 again. When this tag’s value is forced to 1 (ON).

The highest priority is 1. accept the default of 1. ignore this field. the state tag is forced back to 1. If you need a digital tag to indicate the state of this operation (in progress or complete). Block Write Complete. This number influences the order in which the EDI task handles the queuing of write requests. If this is a block write table or an exception write table you plan to periodically disable. If EDI receives two requests at the same time. FactoryLink writes the values. This field defaults to 1 regardless of whether the operation being defined is a block or exception write.ALLEN-BRADLEY | 11 Configuring the Read/Write Control Table Block Read State If this is an unsolicited read or a write operation. Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. Valid Entry: tag name Valid Data Type: digital Block Write Priority If this is a block or exception write operation. While the table is being processed. If this is a triggered read operation. the tag is set to 0 (OFF). enter a tag name. relative to other write operations. Block Write Disable. Do not define these tags for read operations.4 (default=1) Note The Block Write Trigger. Valid Entry: 1 . ignore this field. enter a number to indicate the priority of this table. it processes the request with the highest priority first. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. this field is required. If this is a read operation. this field is optional. This tag is forced to 1 (ON) at startup. When this tag’s value is forced to 1 (ON). Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. and Block Write State tags apply only to write operations. Valid Entry: tag name Valid Data Type: digital FactoryLink Device Interfaces Using EDI Technology / 167 . The default is 1.

To re-enable a cascaded loop or a self-triggered write table. this field is optional. If this is a block write operation. Do not use this tag when more than one logical port is specified in a single table. ignore this field. ignore this field. If you need a digital tag to indicate the state of this operation (in progress or complete). ignore this field. If this is a block write table or an exception write table you plan to periodically disable. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. enter a tag name. Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. 168 / FactoryLink Device Interfaces Using EDI Technology . Block Write Complete If this is a read or exception write operation. After the data defined in this table’s Read/Write Information table is written to the device. even when the block write trigger is set to 1. See “Application Design Tips and Techniques” on page 127 for further details.• • • • 11 | ALLEN-BRADLEY Configuring the Read/Write Control Table Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. This tag is forced to 1 (ON) at startup. the write operation is not executed. This tag is forced to 1 (ON) at startup. If you need a digital tag to indicate when this operation is complete. set this tag back to 0 (OFF). however. the Block Write Trigger tag must be toggled or forced to 1. enter a tag name. When this tag’s value is forced to 1 (ON). To reenable a block write table that is disabled. the complete tag is forced to 1 again. If this is a block write table. this field is optional. The triggering cycle will cease upon disabling. Valid Entry: tag name Valid Data Type: digital Tip This tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. this field is optional.

In this example. After the data defined in this table’s Read/Write Information table is written to the device. Valid Entry: tag name Valid Data Type: digital When the table is complete. FactoryLink disregards the trigger tag. the highest priority. and to the Block Read Complete tag. and does not process the READ_MSG table. • When the value of the digital tag AB_READ_DISABLE is 1. FactoryLink forces a value of 1 to the digital Block Read State tag. click the Save icon to validate the information. AB_READ_COMPLETE. which is set automatically if you do not enter a value. AB_READ_STATE. During the read operation. FactoryLink reads the configured register address and writes its value to the tag configured for this table (in the Read/Write Information table).ALLEN-BRADLEY | 11 Configuring the Read/Write Control Table While the table is being processed. Do not use this tag when more than one logical port is specified in a single table. AB_READ_TRIGGER. Field Table Name Unsolicited Read Exception Write Block Read Priority Block Read Trigger Entry READ YES YES 1 AB_READ_TRIGGER FactoryLink Device Interfaces Using EDI Technology / 169 . the READ table is configured as follows: • When the value of the digital Block Read Trigger tag AB_READ_TRIGGER is 1. Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. AB_READ_STATE is set to 0. The block read priority. The table below provides sample entries for the Allen-Bradley Read/Write Control table. the tag is set to 0 (OFF). the state tag is forced back to 1. is set to the default of 1. • Once FactoryLink reads the data and writes it to the tag defined to receive it (MBRDR1 in the Read/Write Information table).

Because this is a read table. the tags specific to write requests are not defined. 170 / FactoryLink Device Interfaces Using EDI Technology .• • • • 11 | ALLEN-BRADLEY Configuring the Read/Write Control Table Field Block Read Disable Block Read Complete Block Read State Block Write Priority Block Write Trigger Block Write Disable Block Write Complete Block Write State Entry AB_READ_DISABLE AB_READ_COMPLETE AB_READ_STATE The write priority for this table is set to 1 by default.

the EDI task automatically selects an Allen-Bradley data type compatible with the FactoryLink data type of the Tag Name tag. Valid Entry: “Allen-Bradley Address Entries” on page 182 Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. if you enter BIN as the data type for an analog tag. For a Read Table—Add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes. enter the address in the device’s memory where the value to be stored in this tag is located. For example. analog. For a write table. Valid Entry: “Allen-Bradley Data Types” on page 173 FactoryLink Device Interfaces Using EDI Technology / 171 . longana. Valid Entry: tag name Valid Data Type: digital. float. the task interprets BIN as INT2 and reads or writes to the tag as if the data type had been entered as INT2. specify a tag name for a tag containing a value to be written to the device.ALLEN-BRADLEY | 11 Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. Tag Name For a read table. For a Write Table—Add a table entry for each tag to be written when the operation executes. enter the address in the device’s memory to which the tag value will be written. select the row for the table you are configuring and open the Read/Write Information table to the foreground. For a write table. If you enter the data type BIN. specify a tag name for a tag in which FactoryLink will store the data read from the device. Valid Entry: previously defined logical station number Address For a read table. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. message Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written.

The data is stored in a digital tag. Define the data type (digital. Field Tag Name Logical Station Address Data Type Entry MBRDR1 0 310/00 BIN 172 / FactoryLink Device Interfaces Using EDI Technology . In this example. The following table provides sample entries for the Allen-Bradley Read/Write Information table. The protocol module transfers this untranslated binary value (BIN) to the real-time database without conversion. the protocol module reads data from address 310/00 in the PLC configured as logical station 0. or message) for any tag names displayed in the Tag Definition dialog box. analog. click the Save icon to validate the information.• • • • 11 | ALLEN-BRADLEY Configuring the Read/Write Information Table When the table is complete. long analog. floating-point. MBRDR1.

2-byte word representing 3 BCD digits Binary Coded Decimal value Unsigned. 4-byte floating-point number Signed.ALLEN-BRADLEY | 11 Allen-Bradley Data Types A LLEN -B RADLEY D ATA TYPES The following table describes the formats of the PLC data types that the Allen-Bradley protocol module supports: Data Type Description BIN INT2 INT4 BCD3 BCD4 UBCD FLT4 FLT8 ASC Signed. 4-byte binary integer Unsigned. 2-byte word representing 4 BCD digits most significant nibble ignored for reads. zero on writes Signed. 2-byte binary integer Untranslated binary value Signed. 2-byte word representing 4 BCD digits Binary Coded Decimal value Unsigned. second character in most significant byte FactoryLink Device Interfaces Using EDI Technology / 173 . 8-byte floating-point number Two ASCII characters stored in one word: first character in least significant byte.

Analog Tags The Allen-Bradley protocol module supports only the following analog conversions: BIN to Analog The value of the word at the specified address is transferred to the analog tag without conversion. the value of bit 0 at the specified address is transferred to the digital tag. 174 / FactoryLink Device Interfaces Using EDI Technology . INT4 to Analog The value of the 4-byte integer at the specified address is converted to a 2-byte integer value and is transferred to the analog tag. Digital Tags The Allen-Bradley protocol module supports only the following digital conversion: BIN to Digital The value (1 or 0) of the bit at the specified address is transferred to the digital tag without conversion. INT2 to Analog The value of the word at the specified address is transferred to the analog tag without conversion. See “Allen-Bradley Data Types” on page 173 for a list of data types. If no bit number is specified. BCD3 to Analog The 3-digit BCD value at the specified address is converted to a 2-byte integer value and is transferred to the analog tag.• • • • 11 | ALLEN-BRADLEY Conversion of Data Types for Read Operations C ONVERSION OF D ATA TYPES FOR R EAD O PERATIONS This section describes how the Allen-Bradley protocol module converts data types to tags for read operations.

BCD3 to Floating Point The value of the 3-digit BCD word at the specified address is converted to an 8-byte floating-point value and is transferred to the floating-point tag. FLT4 to Analog The 4-byte floating-point value at the specified address is converted to a 2-byte integer value and is transferred to the analog tag. INT2 to Floating Point The value of the 2-byte integer at the specified address is converted to an 8-byte floating-point value and is transferred to the floating-point tag. UBCD to Analog The 3-digit BCD value at the specified address is converted to a 2-byte integer value and is transferred to the analog tag. FactoryLink Device Interfaces Using EDI Technology / 175 . INT4 to Floating Point The value of the 4-byte integer at the specified address is converted to an 8-byte floating-point value and is transferred to the floating-point tag. FLT8 to Analog The 8-byte floating-point value at the specified address is converted to a 2-byte integer value and is transferred to the analog tag.ALLEN-BRADLEY | 11 Conversion of Data Types for Read Operations BCD4 to Analog The 4-digit BCD value at the specified address is converted to a 2-byte integer value and is transferred to the analog tag. Floating-Point Tags The Allen-Bradley protocol module supports only the following floating-point conversions: BIN to Floating Point The 8-byte floating-point value at the specified address is transferred to the floating-point tag without conversion.

FLT8 to Floating Point The 8-byte floating-point value at the specified address is transferred to the floating-point tag without conversion. BCD3 to Longana The 3-digit BCD value at the specified address is converted to a 4-byte integer value and is transferred to the longana tag.• • • • 11 | ALLEN-BRADLEY Conversion of Data Types for Read Operations BCD4 to Floating Point The value of the 4-digit BCD word at the specified address is converted to an 8-byte floating-point value and is transferred to the floating-point tag. UBCD to Floating Point The value of the 3-digit BCD word at the specified address is converted to an 8-byte floating-point value and is transferred to the floating-point tag. Longana Tags The Allen-Bradley protocol module supports only the following longana conversions. FLT4 to Floating Point The 4-byte floating-point value at the specified address is converted to an 8-byte floating-point value and is transferred to the floating-point tag. INT2 to Longana The value of the word at the specified address is transferred to the longana tag without conversion. INT4 to Longana The value of the 4-byte integer at the specified address is transferred to the longana tag without conversion. 176 / FactoryLink Device Interfaces Using EDI Technology . BIN to Longana The value of the 4-byte integer at the specified address is transferred to the longana tag without conversion.

UBCD to Longana The 3-digit BCD value at the specified address is converted to a 4-byte integer value and is transferred to the longana tag. FLT4 to Longana The 4-byte floating-point value at the specified address is converted to a 4-byte integer value and is transferred to the longana tag. ASC to Message The values of the words specified in the address are copied to the message tag with low-order and high-order bytes inverted. Message Tags The Allen-Bradley protocol module supports only the following message conversions BIN to Message The values of the words specified in the address are transferred to the message tag without conversion.ALLEN-BRADLEY | 11 Conversion of Data Types for Read Operations BCD4 to Longana The 4-digit BCD value at the specified address is converted to a 4-byte integer value and is transferred to the longana tag. FLT8 to Longana The 8-byte floating-point value at the specified address is converted to a 4-byte integer value and is transferred to the longana tag. FactoryLink Device Interfaces Using EDI Technology / 177 .

Analog to BCD3 The analog value is converted to a 3-digit BCD value and is transferred to the specified address. the value of the digital tag is transferred to bit 0 at the specified address. If no bit number is specified. 178 / FactoryLink Device Interfaces Using EDI Technology . Analog to BCD4 The analog value is converted to a 4-digit BCD value and is transferred to the specified address. Analog to INT2 The value of the analog tag is transferred to the specified address without conversion. Digital to BIN The value (1 or 0) of the digital tag is transferred to the bit at the specified address without conversion. Digital Tags The Allen-Bradley protocol module supports only the following digital conversion.• • • • 11 | ALLEN-BRADLEY Conversion of Tags for Write Operations C ONVERSION OF TAGS FOR W RITE O PERATIONS This section describes how tags map to the data types listed on page 173 for the Allen-Bradley protocol module for write operations. Analog to INT4 The value of the analog tag is converted to a 4-byte integer value and is transferred to the specified address. Analog to BIN The value of the analog tag is transferred to the specified address without conversion. Analog Tags The Allen-Bradley protocol module supports only the following analog conversions.

Analog to FLT4 The analog value is converted to a 4-byte floating-point value and is transferred to the specified address. Floating Point to INT2 The value of the floating-point tag is converted to a 2-byte integer and is transferred to the specified address. Floating Point to BIN The value of the floating-point tag is transferred to the four-word address without conversion. Floating Point to INT4 The value of the floating-point tag is converted to a 4-byte integer and is transferred to the specified address. Floating Point to BCD4 The value of the floating-point tag is converted to a 4-digit BCD word and is transferred to the specified address. Floating-Point Tags The Allen-Bradley protocol module supports only the following floating-point conversions. Floating Point to BCD3 The value of the floating-point tag is converted to a 3-digit BCD word and is transferred to the specified address.ALLEN-BRADLEY | 11 Conversion of Tags for Write Operations Analog to UBCD The analog value is converted to a 3-digit BCD value and is transferred to the specified address. FactoryLink Device Interfaces Using EDI Technology / 179 . Analog to FLT8 The analog value is converted to an 8-byte floating-point value and is transferred to the specified address.

180 / FactoryLink Device Interfaces Using EDI Technology . Longana to BIN The value of the longana tag is transferred to the specified address without conversion. Floating Point to FLT4 The value of the floating-point tag is converted to a 4-byte floating-point value and is transferred to the specified address. Longana to INT4 The value of the longana tag is transferred to the specified address without conversion.• • • • 11 | ALLEN-BRADLEY Conversion of Tags for Write Operations Floating Point to UBCD The value of the floating-point tag is converted to a 3-digit BCD word and is transferred to the specified address. Longana to INT2 The value of the longana tag is converted to a 2-byte integer value and is transferred to the specified address. Longana to BCD3 The longana value is converted to a 3-digit BCD value and is transferred to the specified address. Longana to BCD4 The longana value is converted to a 4-digit BCD value and is transferred to the specified address. Floating Point to FLT8 The value of the floating-point tag is transferred to the specified address without conversion. Longana Tags The Allen-Bradley protocol module supports only the following longana conversions.

Message Tags The Allen-Bradley protocol module supports only the following message conversions. FactoryLink Device Interfaces Using EDI Technology / 181 . Longana to FLT8 The longana value is converted to an 8-byte floating-point value and is transferred to the specified address. Message to ASC The values of the message tags are written to the words specified in the address with the low-order and high-order bytes inverted.ALLEN-BRADLEY | 11 Conversion of Tags for Write Operations Longana to UBCD The longana value is converted to a 3-digit BCD value and is transferred to the specified address. Longana to FLT4 The longana value is converted to a 4-byte floating-point value and is transferred to the specified address. Message to BIN The values of the message tags are written to the words specified in the address without conversion.

PLC-2 Addresses For the Allen-Bradley PLC-2. these addresses are also valid for PLC-3 and PLC-5.) bit (Optional) Bit address of the specified word in octal Valid Entry: 0 .• • • • 11 | ALLEN-BRADLEY Allen-Bradley Address Entries A LLEN -B RADLEY A DDRESS E NTRIES This section contains information about the Allen-Bradley addresses that FactoryLink supports. 182 / FactoryLink Device Interfaces Using EDI Technology . length where word (Required) Word address of the data table in octal Valid Entry: 0 . 17 most significant bit) length Examples 17 23/17 7/7 0.100 Note (Optional) Number of words in a message string in decimal Word 15 decimal Bit 17 of word 23 (word 19 decimal) Bit 7 of word 7 (word 15 decimal) First 100 decimal words If you configure PLC-3 and PLC-5 for PLC-2 compatibility.17 (octal) (0 least significant bit. FactoryLink supports the following address formats: word word/bit word.7777 (octal) (The actual high address depends on the specific PLC that is addressed.

length] where W filetype (Optional) Logical word addressing – default if no other addressing type is specified (Required) One of the letters specifying a PLC-3 file type shown in the following table.ALLEN-BRADLEY | 11 Allen-Bradley Address Entries PLC-3 Addresses The Allen-Bradley PLC-3 uses the following types of address formats: • Logical word addressing • Logical file addressing • Symbolic word addressing • Symbolic file addressing Logical Word Addressing Logical word addressing uses the following address formats: [W]filetype[filenumber:][tag][. Description Section # Words/Tag Type O I T C N F D B A Output image Input image Timer Counter Integer Floating-point BCD Binary ASCII 1 2 3 4 5 6 7 8 9 1 1 3 3 1 2 1 1 1 FactoryLink Device Interfaces Using EDI Technology / 183 .subtag][.subtag][/bit] [W]filetype[filenumber:][tag][.

Bit 16 refers to the least significant bit of the next word in the PLC’s memory.10 010:10.subtag][/bit] F filetype[filenumber:][tag][.• • • • 11 | ALLEN-BRADLEY Allen-Bradley Address Entries Type Description Section # Words/Tag H P S filenumber tag subtag bit length High-order integer Pointer Status 10 11 13 2 2 1 (Optional) File number in decimal Valid Entry: 0 .10 WT10:8. which are octal (Optional) Subtag in decimal (Optional) Bit address in octal (Optional) Number of words in decimal Least significant bit of word 8 (decimal) of input file 12 (decimal) Bit 17 of word 11 (decimal) of input file 0 First 10 (decimal) words of output file 0 Words 8 . except types I and O. Logical file addressing uses the following address formats: F filetype[filenumber:][tag][.subtag][.17 (decimal) inclusive of output file 10 Bit 17 of second word in timer 8 (the ninth timer structure timer file number 10) Examples (Logical Word Addressing) WI12:10/0 I13/17 O0.length] where F (Required) Logical file addressing 184 / FactoryLink Device Interfaces Using EDI Technology .1/17 Logical File Addressing When you use logical file addressing. regardless of file type. all numbers are in decimal.999 (default=0) (Optional) Tag number in specified file in decimal.

Valid Entry: 999 (default=0) Type Description Section # Words/Tag O I T C N F D B A H P S filenumber tag subtag bit length Output image Input image Timer Counter Integer Floating-point BCD Binary ASCII High-order integer Pointer Status 1 2 3 4 5 6 7 8 9 10 11 13 1 1 3 3 1 2 1 1 1 2 2 1 (Optional) File number in decimal (Optional) Tag number in specified file in decimal (Optional) Subtag in decimal (Optional) Bit number (Optional) Number of words in decimal Bit 15 of word 15 of output file 0 (Word 15 is the 16th word in the file.) Examples (Logical File Addressing) FO/255 FI5:/256 FactoryLink Device Interfaces Using EDI Technology / 185 .ALLEN-BRADLEY | 11 Allen-Bradley Address Entries filetype (Required) One of the letters specifying a PLC-3 file type shown in the table below.) Bit 0 of word 16 of input file 5 (Word 16 is the 17th word in the file.

length where @ (Required) The symbolic addressing flag character 186 / FactoryLink Device Interfaces Using EDI Technology .) Bit 0 of word 26 of input file 5 (Word 26 is the 27th word in the file.• • • • 11 | ALLEN-BRADLEY Allen-Bradley Address Entries FI10/256 FI5:10/256 FF3:2 Bit 0 of word 26 of input file 0 (Word 26 is the 27th word in the file.20 Symbolic File Addressing Symbolic file addressing uses three address formats. floating-point file 3 (Floating-point value number 2 is the 5th and 6th words in this file.) Symbolic Word Addressing Symbolic word addressing uses the following formats: @AAAAAAAA @AAAAAAAA/bit @AAAAAAAA.to 8-character symbolic name defined in the PLC (use only uppercase characters) (Optional) Bit number in octal (Optional) Number of words in message string in decimal Symbol Most significant bit of the word at SYMBOL 20 words starting at SYMBOL Examples (Symbolic Word Addressing) @SYMBOL @SYMBOL/17 @SYMBOL.length where @ AAAAAAAA bit length (Required) The symbolic addressing flag character (Required) 1. @AAAAAAAA:word @AAAAAAAA:word/bit @AAAAAAAA:word.) Floating-point value 2.

even if it is 0) (Optional) Bit number in decimal (Optional) Number of words in message string in decimal First word of PLC ASCII symbol file Least significant bit of word at SYMBOL + 11 20 words starting at SYMBOL + 10 Examples (Symbolic File Addressing) @SYMBOL:0 @SYMBOL:10/16 @SYMBOL:10.length] where filetype wordnumber bit length I:34/17 O:/0 I:.to 8-character symbolic name defined in the PLC (use only uppercase characters) (Required) Word number (offset) from symbol in decimal (specify a word. the Allen-Bradley protocol module supports two formats for addressing PLC-5s.777 (default=0) (Optional) Bit address in octal (Optional) Number of words in decimal Bit 17 of word 28 in the Input Image table Bit 0 of Word 0 in the Output Image table First 100 word of the Input Image table FactoryLink Device Interfaces Using EDI Technology / 187 .20 PLC-5 Addresses Depending on the file type being addressed.ALLEN-BRADLEY | 11 Allen-Bradley Address Entries AAAAAAAA word bit length 1. The Allen-Bradley PLC-5 Input and Output Image tables use the following address formats: filetype:[wordnumber][/bit] filetype:[wordnumber][.100 (Required) One of the letters (I or O) specifying a PLC-5 Input or Output Image table (Optional) Word number in octal Valid Entry: 0 .

(Optional) Bit address in decimal.999 tag subtag bit length N7:23/15 (Optional) Tag number in specified file in decimal (default=0). Bit 15 of word 23 of integer file 7. (Word 23 is the 24th word in the file.subtag][/bit] filetype[filenumber]:[tag][.) 188 / FactoryLink Device Interfaces Using EDI Technology . (Optional) Number of words in decimal.• • • • 11 | ALLEN-BRADLEY Allen-Bradley Address Entries The remaining Allen-Bradley PLC-5 data table files use the following address formats: filetype[filenumber]:[tag][.subtag][. Valid Entry: 0 . file number is assumed to be the default file number for the file type specified.length] where filetype (Required) One of the letters specifying a PLC-5 file type shown in the following table Description Default File # # Words/Tag Type S B T C R N F A D filenumber Status Binary Timer Counter Control Integer Floating-point ASCII BCD 2 3 4 5 6 7 8 N/A N/A 1 1 3 3 3 1 2 1 1 (Optional) File number in decimal. (Optional) Subtag number in decimal (default=0). If not specified.

PLC Type PLC-250 Use the PLC type PLC-250 in the Logical Station table to describe a logical station as a PLC5-250. Unsolicited Read Support Create a logical station with a PLC type of PLC-2 for unsolicited reads from the PLC5-250. If you try to use other features. This PLC type supports limited native addressing to a PLC5-250. (Float word 17 is the 18th float word. FactoryLink application errors will occur.) PLC 5-250 Native Mode Addresses The Allen-Bradley protocol module supports a limited subset of PLC5-250 native mode addresses. FactoryLink Device Interfaces Using EDI Technology / 189 . (Bit 15 is the most significant bit. Word 15 is the 16th word. (Bit 15 is the most significant bit.) Bit 15 of Word 15 of Bit file 17.ALLEN-BRADLEY | 11 Allen-Bradley Address Entries F8:17 B17:/255 B3/255 Float value 17 in Floating-point file 8. Native Addressing Specify all numbers in the address in decimal. The PLC5-250 may then send Unprotected Write (PLC-2 format) commands to the protocol module. It supports only those features specifically described in this document. The following are limitations on the data that can be accessed: • The data must reside either in the resource manager or a logic processor addressable from the resource manager. • The file’s native tag must not contain subtags. Word 15 is the 16th word. The protocol module ignores any definitions of unsolicited reads on a station with a PLC type of PLC-250.) Bit 15 of word 15 of Bit file 3. • The file identifier must consist of a single character.

It consists of a 1. it is assumed to equal 0. It consists of a single uppercase alphabetic character. If a logic processor is specified. it is assumed to equal 0. this number is the value set on the thumbwheel on the front of the logic processor. If the FILE_TAG is omitted. the MODULE_ID is the resource manager.• • • • 11 | ALLEN-BRADLEY Allen-Bradley Address Entries Address Format Use the following address format: [module_id] file_id [file_number]: [file_tag][/bit_number] [. the resource manager will be assumed. if 1-8.to 4-character decimal number ranging from 0 to 9999. If the MODULE_ID is omitted.to 4-character decimal number ranging from 0 to 9999.msg_length] where spaces brackets [ ] colon (:) MODULE_ID Are for readability only. 190 / FactoryLink Device Interfaces Using EDI Technology . It consists of a 1. If the FILE_NUMBER is omitted. FILE_ID The FILE_ID specifies the type of file. MODULE_ID is a logic processor. FILE_TAG The FILE_TAG specifies which tag in the file is addressed. Valid FILE_IDs are: B N L F FILE_NUMBER Binary files Integer files Long integer files Floating-point files The FILE_NUMBER specifies which file of the FILE_ID file is addressed. do not include them in the actual address string Are optional in the address string Are required in the address string If 0.

INT4. FactoryLink Device Interfaces Using EDI Technology / 191 .) as those with logical stations of type PLC-5. See “PLC-5 Addresses” on page 187 for more information. . except that the BIT_NUMBER must range between 0 and 15.ALLEN-BRADLEY | 11 Allen-Bradley Address Entries BIT_NUMBER and MESSAGE_LENGTH The BIT_NUMBER and MESSAGE_LENGTH are the same as the other PLC types. Example The following sample strings illustrate PLC5-250 native mode addressing format: Address 0B14:10/15 B14:10/15 3N5:3 Description The most significant bit of the 11th binary word (address 10) of the 15th binary file (address 14) in the resource manager Same as previous The fourth (address 3) integer tag of the sixth (address 5) integer file in logic processor 3 PLC Tag Type to FactoryLink Tag Type Conversion Use the same conversions (INT2. bit 15 is the most-significant bit. . Bit 0 is the least-significant bit.

Address DH/DH+ 422/232 SW1 SW2 SW3 123 SW4 123 SW5 12 UU SW6 1234 DUUD SW7 1 2/1 2 DD/UD SW8 1 2/1 2 UD/DU 1 2 3 4 5 12 DUDD D 1771-KA2 As needed The following are the switch settings for the 1771-KA2. SW1 SW2 SW3 SW4 SW5 12345 UUUUU 1771-KE 12 123 123 12 As needed As needed As needed UU The following are the switch settings and addresses for the 1771-KE.• • • • 11 | ALLEN-BRADLEY Allen-Bradley Switch Setup A LLEN -B RADLEY S WITCH S ETUP 1770-KF2 Series B The following are the switch settings and addresses for the 1770-KF2 Series B. SW1 Address SW5 SW6 12345 DDDDD 12 As needed 123 123 12 UU 1234 UDDU 192 / FactoryLink Device Interfaces Using EDI Technology .

SW1 SW2 SW3 SW4 SW5 SW6 12 DD 12 DD 12 DD 12 DD 123 UDD 123 DUD FactoryLink Device Interfaces Using EDI Technology / 193 .ALLEN-BRADLEY | 11 Allen-Bradley Switch Setup 1771-KG The following are the switch settings and addresses for the 1771-KG. SW1 SW2 Address 123 DUU 1785-KA 12345 DDUUD 12 As needed 123 123 The following are the switch settings for the 1785-KA.

Single-Digit Code Format ER:xxxN is a single-digit format in which one digit represents a single error condition. For information about configuring an analog tag. For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. In following descriptions. Double-Digit Code Format ER:xxNN is a double-digit format in which two digits represent a single error condition. two individual codes appear within a string to indicate multiple error conditions. The ER:xxxx string in a message can contain a single-digit or a double-digit error code. N represents significant digits and x represents digits not significant to the error. writes them to message or analog tags. FactoryLink generates and displays messages for the Allen-Bradley protocol module on the Run-Time Manager screen and. see “Configuring the Logical Station Control Table” on page 158. see “Configuring the Logical Station Information Table” on page 162. described in the following table. Single-Digit Codes Hexadecimal error codes 0001 through 000F are Allen-Bradley protocol module internal errors. In some cases.• • • • 11 | ALLEN-BRADLEY Run-Time Application Messages R UN -TIME A PPLICATION M ESSAGES During EDI run time. see Chapter 11. if so configured. For information about configuring a message tag. Error Message Description 0001 0002d 0003 Internal error (invalid rcv/xmt state) Unable to transmit request to Data Highway Interface Unable to receive request response from Data Highway Interface 194 / FactoryLink Device Interfaces Using EDI Technology . “Messages and Codes”.

Read the least significant nibble of the EDI error code to obtain the local error code. Extended. Local STS Error Codes EDI error codes from 0010 through 001F denote Local STS errors received from the Data Highway Interface. or Remote STS errors.ALLEN-BRADLEY | 11 Run-Time Application Messages Error Message Description 0004 0007 0008 000A Double-Digit Codes Internal error (CPT translate error) Internal error (DSF translate error) Invalid extended status (above 080h) from Data Highway Interface Invalid length retry count exceeded Error codes received from the Data Highway interface can signify Local. Error Message Description 0011 0012 0013 0014 Designate node out of buffer space Remote node specified does not acknowledge (ACK) the command message Duplicate token holder detected Local port is disconnected FactoryLink Device Interfaces Using EDI Technology / 195 .

Subtract 0030 from the EDI error code to obtain the Extended error code. disconnected. Error Message Description 0031 0032 0033 Error in converting block address Fewer levels specified in address to address More levels specified in address than system supports 196 / FactoryLink Device Interfaces Using EDI Technology . Read the least significant nibble of the EDI error code as the most significant nibble of the remote error code to obtain the remote error code.• • • • 11 | ALLEN-BRADLEY Run-Time Application Messages Remote STS Error Codes EDI error codes from 0020 through 002F denote Remote STS errors received from the Data Highway Interface. Error Code Description 0021 0022 0023 0024 0025 0026 0027 0028 0029 002B Illegal command or format The host has a problem and will not communicate The remote node host is missing. or shut down The host could not complete function because of hardware fault Addressing problem or memory protect rings Function disallowed because of command protection selection Processor is in program mode Compatibility mode file missing or communication zone problem Remote node cannot buffer command Remote node problem caused by download Extended STS Error Codes EDI error codes above 002F denote Extended STS errors received from the Data Highway interface.

FactoryLink Device Interfaces Using EDI Technology / 197 . situation has changed since the start of the command The file is too large The transaction size plus word address is too large Access denied. resource is not available (some have upload active) Condition already exists. noprivilege Histogram overflow Illegal data type Bad parameter An address reference(s) exists to a deleted data table(s) The EDI protocol module uses command code OF.ALLEN-BRADLEY | 11 Run-Time Application Messages Error Message Description 0034: 0035 0036 0037 0038 0039 003A 003B 003C 003D 003E 003F 0040 0041 0042 0043 Note Symbol not found The symbol is of improper format Address does not point to something usable The file is the wrong size Cannot complete request. resource is already available The shutdown could not be executed Requestor does not have upload or download access. improper privilege Condition cannot be generated.

• • • • 11 | ALLEN-BRADLEY Run-Time Application Messages 198 / FactoryLink Device Interfaces Using EDI Technology .

This entry must match the configuration of the devices communicating via this port. See “Identifying Protocol Types and Defining Logical Ports” on page 58 for details.115200 (default=9600) Parity Enter the parity error correction during transmission via this logical port. Valid Entry: previously defined logical port number (default=0) Baud Rate Enter the speed at which the protocol module communicates with the devices linked to FactoryLink via this logical port. open Device Interfaces > GE Fanuc. even.Chapter 12 • • • General Electric This chapter contains information needed to set up and configure bidirectional communications between the FactoryLink real-time database and one or more General Electric devices. you must complete the External Device Definition table. Open the Logical Station Control Table. Logical Port Enter a number. C ONFIGURING Note THE L OGICAL S TATION C ONTROL TABLE Before completing the protocol-specific General Electric configuration tables. to represent a particular communication path to a device. odd (default=none) • FactoryLink Device Interfaces Using EDI Technology / 199 . Valid Entry: 110 . This entry must match the baud rate configuration of the devices. using GE CCM protocol. Valid Entry: none. In your server application. defined in the External Device Definition table Logical Port column. Refer to the device manufacturer’s documentation for details. Refer to the device manufacturer’s documentation for details. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations.

Valid Entry: 1 Timeout Enter the length of time. You must enter a value greater than 0 for the protocol module to timeout. Valid Entry: 8 Stop Bits Enter the number of bits sent after a character to create a pause before the start of the next character. This entry must match the configuration of the devices communicating via this port. This entry must match the configuration of the devices communicating via this port. click the Save icon to validate the information. the protocol module will wait to receive a response to a read or write command before timing out. Refer to the device manufacturer’s documentation for details.• • • • 12 | GENERAL ELECTRIC Configuring the Logical Station Control Table Data Bits Enter the number of data bits used during transmission via this logical port. 200 / FactoryLink Device Interfaces Using EDI Technology . Define the data type (message) for any tag names displayed in the Tag Definition dialog box. Refer to the device manufacturer’s documentation for details. in tenths of a second. Valid Entry: tag name Valid Data Type: message When the table is complete. Valid Entry: 0 .9999 (default=20 or 2 seconds) Status Msg Tag Name (Optional) Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port.

GENERAL ELECTRIC | 12 Configuring the Logical Station Information Table The following table provides sample entries for the General Electric Logical Station Control table. Valid Entry: tag name Valid Data Type: analog Logical Station (Decimal) Enter a number to identify the logical station to which the information in this row pertains. select the row for the logical port you are configuring and open the Logical Station Information table. Field Logical Port Entry Description 0 Baud Rate Parity Data Bits Stop Bits Timeout 9600 NONE 8 1 10 Status Msg Tag Name GENE_LPORT0_ MSG Specifies the logical communication path configured by this table Specifies the communication rate No parity checking Specifies 8 data bits in the transmission Specifies 1 stop bit in the transmission The response timeout 1 second Error messages written to the message tag GENE_LPORT0_MSG C ONFIGURING THE L OGICAL STATION I NFORMATION TABLE From the Logical Station Control table. Assign a unique number to each device communicating through this logical port. Complete a row for each device to communicate through this logical port. Error/Status Tag Name (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station). A logical station represents the combination of a logical port with a physical station. FactoryLink Device Interfaces Using EDI Technology / 201 .

In a read or write table. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box. SERIES_1 GE Series One PLC SERIES _3 SERIES _5 SERIES _6 S1_JR S1_PLUS SRS_9070 SRS_9030 GE Series Three PLC GE Series Five PLC GE Series Six PLC GE Series One JR PLC GE Series One PLUS PLC GE Series 9070 GE Series 9030 Physical Station Comment Enter the physical address of the General Electric device. you will enter this logical station number in a read or write table to represent the device defined in this row.255 Device Type Enter the type of General Electric device to which communications are to be directed. Valid Entry: alphanumeric string of up to 16 characters When the table is complete. Valid Entry: 0 . Valid Entry: 0 . this number will identify the device to or from which data is to be sent or received. click the Save icon to validate the information.• • • • 12 | GENERAL ELECTRIC Configuring the Logical Station Information Table Later.255 (Optional) Enter reference information about this logical station. 202 / FactoryLink Device Interfaces Using EDI Technology .

If this is a triggered read or a block write table. Define one request (table) per line and do not include spaces in the name. Specifies the physical station number associated with this logical station. enter YES. For EDI to interpret this operation as an exception write and write tag values to the device only when those values change.GENERAL ELECTRIC | 12 Configuring the Read/Write Control Table The following table provides sample entries for the General Electric Logical Station Information table: Field Error/Status Tag Name Logical Station Device Type Physical Station Entry Description GENE_STATION0_ STATUS 0 SERIES_1 0 Contains information about communication errors. Complete a row for each read or write table. FactoryLink Device Interfaces Using EDI Technology / 203 . the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. You can define as many tables as available memory allows. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Open the Read/Write Control table. Specifies the physical device type associated with this logical station. accept the default of NO. Valid Entry: alphanumeric string of up to 16 characters Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. Table Name Assign a name to this read or write request. Try to make the table name reflective of the operation it represents. Specifies the logical communication path.

Valid Entry: 1 .4 (default=1) Note for write operations. no Tip Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. EDI writes this tag’s value to the device. it processes the request with the highest priority first. accept the default of 1. and Block Read State tags apply only to triggered read operations. Block Read Complete. an internal change-status indicator within the tag containing the data to be written prompts the write operation.• • • • 12 | GENERAL ELECTRIC Configuring the Read/Write Control Table In an exception write. The default is 1. enter a number to indicate the priority of this table. This number influences the order in which the EDI task handles the queuing of block read requests. Defining tags that change value frequently as exception writes can slow down communications or result in an error message. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). The Block Read Trigger. Block Read Priority If this is a block read operation. Valid Entry: yes. This field defaults to 1 regardless of whether the operation being defined is a block read. If EDI receives two requests at the same time. If this is a write operation. Do not define these tags 204 / FactoryLink Device Interfaces Using EDI Technology . Block Read Disable. relative to other read operations. The highest priority is 1. Any tag specified will be written to the device in its own packet (message) each time it changes.

To re-enable a cascaded loop or a self-triggered read table. enter a tag name. Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. set this tag back to 0 (OFF). If this is a triggered read operation. Valid Entry: tag name Valid Data Type: digital Block Read Trigger Block Read Disable If this is a write operation. ignore this field. the addresses are read. If this is a triggered read operation. If you need a digital tag to disable a block read of the tags specified in this table. FactoryLink Device Interfaces Using EDI Technology / 205 . the read operation is not executed. The triggering cycle will cease upon disabling. this field is required. See “Application Design Tips and Techniques” on page 127 for further details. ignore this field. even when the block read trigger is set to 1. To re-enable a block read table that is disabled. however. Valid Entry: tag name Valid Data Type: digital Tip This tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered.GENERAL ELECTRIC | 12 Configuring the Read/Write Control Table Field Tag Name Logical Station Address Data Type Entry MBRDR1 0 310/00 BIN If this is a write operation. When this tag’s value is forced to 1 (ON). this field is optional. When this tag’s value is forced to 1 (ON). the Block Read Trigger tag must be toggled or forced to 1.

relative to other write operations. this field is optional. ignore this field. the tag is set to 0 (OFF).• • • • 12 | GENERAL ELECTRIC Configuring the Read/Write Control Table Block Read Complete If this is a write operation. this field is optional. This tag is forced to 1 (ON) at startup. enter a tag name. If this is a triggered read operation. If you need a digital tag to indicate when this operation is complete. Valid Entry: tag name Valid Data Type: digital Block Write Priority If this is a block or exception write operation. Do not use this tag when more than one logical port is specified in a single table. the state tag is forced back to 1. Block Write Complete. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. accept the default of 1. Valid Entry: tag name Valid Data Type: digital Block Read State If this is a write operation. If EDI receives two requests at the same time. enter a number to indicate the priority of this table. While the table is being processed. This tag is forced to 1 (ON) at startup. Block Write Disable.4 (default=1) Note The Block Write Trigger. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. the complete tag is forced to 1 again. If you need a digital tag to indicate the state of this operation (in progress or complete). 206 / FactoryLink Device Interfaces Using EDI Technology . and Block Write State tags apply only to write operations. If this is a read operation. This number influences the order in which the EDI task handles the queuing of write requests. Valid Entry: 1 . If this is a triggered read operation. The default is 1. Do not define these tags for read operations. The highest priority is 1. This field defaults to 1 regardless of whether the operation being defined is a block or exception write. ignore this field. enter a tag name. it processes the request with the highest priority first.

GENERAL ELECTRIC | 12 Configuring the Read/Write Control Table Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. FactoryLink Device Interfaces Using EDI Technology / 207 . To re-enable a cascaded loop or a self-triggered write table. If this is a block write table or an exception write table you plan to periodically disable. When this tag’s value is forced to 1 (ON). even when the block write trigger is set to 1. ignore this field. If this is a block write table or an exception write table you plan to periodically disable. Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. See “Application Design Tips and Techniques” on page 127 for further details. The triggering cycle will cease upon disabling. however. FactoryLink writes the values. the Block Write Trigger tag must be toggled or forced to 1. Valid Entry: tag name Valid Data Type: digital Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. the write operation is not executed. this field is required. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. set this tag back to 0 (OFF). To reenable a block write table that is disabled. When this tag’s value is forced to 1 (ON). Valid Entry: tag name Valid Data Type: digital Tip This tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. ignore this field. this field is optional.

Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. the tag is set to 0 (OFF).• • • • 12 | GENERAL ELECTRIC Configuring the Read/Write Control Table Block Write Complete If this is a read or exception write operation. enter a tag name. ignore this field. Do not use this tag when more than one logical port is specified in a single table. Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. If this is a block write operation. the state tag is forced back to 1. While the table is being processed. After the data defined in this table’s Read/Write Information table is written to the device. this field is optional. ignore this field. If this is a block write table. After the data defined in this table’s Read/Write Information table is written to the device. Do not use this tag when more than one logical port is specified in a single table. this field is optional. If you need a digital tag to indicate the state of this operation (in progress or complete). 208 / FactoryLink Device Interfaces Using EDI Technology . If you need a digital tag to indicate when this operation is complete. Valid Entry: tag name Valid Data Type: digital When the table is complete. This tag is forced to 1 (ON) at startup. This tag is forced to 1 (ON) at startup. click the Save icon to validate the information. enter a tag name. the complete tag is forced to 1 again.

Since this is a read table. The value of GENE_READ_ COMPLETE is set to 1 when the read is complete. This is not an exception write. The write priority for this table is set to 1 by default. When triggered. When the value of GENE_READ_TRIGGER is 1. Block Read Disable GENE_READ_ DISABLE GENE_READ_ COMPLETE 1 Block Read Complete Block Write Priority Block Write Trigger Block Write Complete Block Write Disable Block Write State FactoryLink Device Interfaces Using EDI Technology / 209 .GENERAL ELECTRIC | 12 Configuring the Read/Write Control Table The following table provides sample entries for the General Electric Read/Write Control table: Field Table Name Exception Write Block Read Priority Block Read Trigger Entry Description READ NO 1 GENE_READ_ TRIGGER Name of the read/write table. The block read priority for the READ table is set to 1. the tags specific to write requests are not defined. a block read of values specified in the Read/Write Information table associated with this table occurs. GENE_READ_ DISABLE disables the block read operation.

9070 OUTPUT Series 6 Output Status Table. analog. Tag Name For a read table. For a Read Table – Add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes. Valid Entry: tag name Valid Data Type: digital. specify a tag name for a tag containing a value to be written to the device. 9070 INPUT Series 6 Input Status Table. 9070 REAL_O Series 6 Real Output points REAL_I Series 6 Real Input points DESC_O Series 6 Internal Discrete Output Reference DESC_I Series 6 Internal Discrete Input Reference DIAG Diagnostic status area 1+_INP 2+_INP Series 5I1+Inputs Series 5I2+Inputs 210 / FactoryLink Device Interfaces Using EDI Technology . 9030. select the row for the table you are configuring and open the Read/Write Information table. For a write table. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. REG Series 5/6 Register Table. For a Write Table – Add a table entry for each tag to be written when the operation executes.• • • • 12 | GENERAL ELECTRIC Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. specify a tag name for a tag in which FactoryLink will store the data read from the device. 9030. float. message Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written. Valid Entry: previously defined logical station number Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. 9030.

1+ JR. 9030. Valid Entry: 0 . Valid Entry: 1 . and 3 Data Registers Port ON/OFF TIMER Series 1. REAL_I. DESC_O. 1+ and 3 Timer and Counter Enter the channel number in the controller on which the address is located. 1JR.GENERAL ELECTRIC | 12 Configuring the Read/Write Information Table LC_INP Series 5 Local Inputs SP_INP 1+_OUT 2+_OUT LC_OUT 1-_OUT 2-_OUT EXT_IO INT_IO S_REG D_REG PORT Channel Series 5 Special Inputs Series 5 O1+Outputs Series 5 O2+Outputs Series 5 Local Outputs Series 5 Internal Coils O1Series 5 Internal Coils O2Series 1. 1+ and 3 External I\O Series 1. 1JR. 9070) Address Octal For a read table.10000 (octal address for Series 1. and DESC_I. enter the address in the device’s memory to which the tag value will be written. Address Dec For a read table.16384 (decimal address for Series 5 and 6. Valid Entry: 1 .15 This channel number is valid for Series 6 and the following data types: REAL_O. enter the address in the device’s memory where the value to be stored in this tag is located. and 3) FactoryLink Device Interfaces Using EDI Technology / 211 . 1JR. 1+ and 3 Internal I/O Series 1. enter the address in the device’s memory to which the tag value will be written. For a write table. enter the address in the device’s memory where the value to be stored in this tag is located. 1+ and 3 Shift Registers Series 1. 1JR. For a write table.

it is ignored.• • • • 12 | GENERAL ELECTRIC Configuring the Read/Write Information Table Bit Offset Name column) associated with this entry is digital. or floating-point) for any tag names displayed in the Tag Definition dialog box. Decimal address of the word being read.15 If you enter a FactoryLink digital tag in the Tag Name field and specify the data type as REG. the protocol module reads the Bit Offset. analog. Specifies the channel in the controller where the address is located. The following table provides sample entries for the General Electric Read/Write Information table: Field Table Name Tag Name Logical Station Data Type Channel Entry Description READ GERDR1 0 REG 1 Display only. Specifies the path to send the request. When the table is complete. Bit 1 is the most significant bit (MSB) and bit 16 is the least significant bit. specifies the Read/Write table name. The value read from the device will be stored in GERDR1. Valid Entry: 0 . otherwise. Leave this field blank for all other FactoryLink data types. enter the bit This field is required for digital data type. Address Dec 10 212 / FactoryLink Device Interfaces Using EDI Technology . If the tag (entry in the Tag offset within the word that contains the value to be read or to which the tag value is to be written. or D_REG. TIMER. long analog. Define the data type (digital. Data type for this controller. click the Save icon to validate the information.

see “Configuring the Logical Station Information Table” on page 201. if so configured. see “Configuring the Logical Station Control Table” on page 199. GE error: [2] where [1] is one of the message codes 1 . The ER:xxxx string can contain a single-digit or a double-digit error code.GENERAL ELECTRIC | 12 Run-Time Application Messages R UN -T IME A PPLICATION M ESSAGES During EDI runtime. For information about configuring an analog tag. Double-Digit Code Format ER:xNNx is a double-digit format in which two digits represent a single error condition. GE error: [2] GENE read response for write request: [1]. In the examples shown below. Single-Digit Code Format ER:xxxN and ER:xxNx are single-digit formats in which one digit represents a single error condition. This message code is displayed as a text string. For information about configuring a message tag. N represents significant digits and x represents digits insignificant to the error. GE error: [2] GENE write response: [1]. see “Messages and Codes” on page 147. FactoryLink Device Interfaces Using EDI Technology / 213 . the protocol module copies these error messages in the following format: GENE read request status: [1].4 listed in the “Single-Digit Error Code Format ER:xxxN” table. For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. If you define message tags in the General Electric Logical Station Control table for all logical stations on this logical port. writes them to message or analog tags. FactoryLink generates and displays messages for the General Electric protocol module on the Run-Time Manager screen and.

F listed in “Single-Digit Error Code Format ER:xxNx” table. Example: GENE read request status: IO_ERROR GE error: RCV_FDB_ERR This example indicates an input/output error in receiving an FDB message. Single-Digit Error Code Format ER:xxxN Code xxx1 xxx2 xxx3 xxx4 Text String Description IO_ERROR IO_ABORTED IO_XLATE_ERR UNKNOWN_ERR Transmission error Transmission aborted Invalid transmit message length or transmit buffer too short Unknown error Single-Digit Error Code Format ER:xxNx Code xx1x xx2x xx3x xx4x xx5x Text String Description XMIT_ERR RCV_ERR RCV_ENQ_ERR RCV_HDR_ERR RCV_FDB_ERR Error occurred during transmit Error occurred during receive Error receiving ENQ message Error receiving HDR message Error receiving FDB message 214 / FactoryLink Device Interfaces Using EDI Technology .• • • • 12 | GENERAL ELECTRIC Run-Time Application Messages [2] is one of the message codes 1 . This message code is displayed as a text string. Single-Digit Codes The following tables list the single-digit error codes that can be generated and displayed by the General Electric protocol module.

GENERAL ELECTRIC | 12 Run-Time Application Messages Code xx6x xx7x xx8x xx9x xxAx xxBx xxCx xxDx xxEx xxFx Text String Description RCV_ACK_ERR XMIT_ENQ_ERR XMIT_HDR_ERR XMIT_ACK_ERR XMIT_FDB_ERR XMIT_NAK_ERR RCV_ENQ_TIMEOUT RCV_HDR_TIMEOUT RCV_FDB_TIMEOUT RCV_ACK_TIMEOUT Error receiving ACK message Error transmitting ENQ message Error transmitting HDR message Error transmitting ACK message Error transmitting FDB message Error transmitting NAK message Timeout error receiving ENQ message Timeout error receiving HDR message Timeout error receiving FDB message Timeout error receiving ACK message FactoryLink Device Interfaces Using EDI Technology / 215 .

Double-Digit Error Code Format ER:xNNx Code x10x x11x Text String Description RCV_EOT_TIMEOUT RCV_EOT_ERR Timeout error receiving EOT message Error receiving ENQ message 216 / FactoryLink Device Interfaces Using EDI Technology . This format contains a 1 in the hundredth’s position (ER: x1Nx). The following table lists the double-digit error codes that can be generated and displayed by the General Electric protocol module.• • • • 12 | GENERAL ELECTRIC Run-Time Application Messages Double-Digit Codes The double-digit format is displayed in the error string’s middle two digits.

The FactoryLink application performs the following additional tasks: • Defines and implements the general FactoryLink application. The FactoryLink application controls overall transactions. asynchronous devices. The GPI is a general purpose protocol module that was written for no specific external device. The information provided in the “Application Programs”and “Capabilities. • Provides correct information in the command tables and ensures the information is triggered at the appropriate time. see the “Configuring the Command/Response Control Table” on page 225. To determine the cable connections needed to set up your particular external device.) • Monitors the communication response status and FactoryLink data returned from the GPI communication interface. • FactoryLink Device Interfaces Using EDI Technology / 217 . such as retries and error recovery. • Logs and/or manipulates the data received by the FactoryLink real-time database. refer to the documentation available from the manufacturer. You can use the GPI protocol module with a variety of devices. Limitations. A PPLICATION P ROGRAMS The GPI protocol module provides a set of options and capabilities to support many. and Trade-Offs”sections can help you determine if the GPI is suitable for your application. though not all.Chapter 13 • • • General Purpose Interface The General Purpose Interface (GPI) protocol module provides a communication interface between a FactoryLink application and external devices using asynchronous communication techniques and protocols such as ASCII or binary. (For information about command tables.

(For example. This consideration had priority in matters such as speed and ease of use. • Communicates with more than one device at a time. While it is flexible. The GPI provides a variety of options that allow you to implement many different types of asynchronous protocols at the FactoryLink application level. • Makes available a wide selection of checksum routines. Flexibility was the major goal for the GPI protocol module. to determine if the GPI is suitable for your particular application. Since the GPI was not written for a specific device. the GPI protocol module cannot support every asynchronous protocol. evaluate it based on the information provided in this section. Capabilities The GPI has the following capabilities: • Handles more than one protocol at a time. • Handles up to eight different response formats for an outgoing message. the GPI has the following limitations: • Permits only single handshaking protocols • Lacks support for protocols which require checksums to handle special-character sequences • Lacks support for protocols which require character substitutions for special-character sequences Trade-Offs and Compromises in Design Any engineering design makes trade-offs and compromises in design. AND TRADE -O FFS The GPI protocol module provides bidirectional asynchronous communications between a FactoryLink application and external devices. Each response must share the same end-of-response indicator.• • • • 13 | GENERAL PURPOSE INTERFACE Capabilities. each table might have the response data length in field 2). Limitations In general. and Trade-Offs C APABILITIES . Limitations. if eight response tables define the response formats. 218 / FactoryLink Device Interfaces Using EDI Technology . L IMITATIONS .

you must complete the External Device Definition table. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. defined in the External Device Definition table Logical Port column. to represent a particular communication path to a device.115200 (default=9600) FactoryLink Device Interfaces Using EDI Technology / 219 . Valid Entry: previously defined logical port number (default=0) LPORT Status Message Tag (Optional) Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. See “Identifying Protocol Types and Defining Logical Ports” on page 58 for details. This entry must match the baud rate configuration of the devices. C ONFIGURING THE L OGICAL STATION C ONTROL TABLE Open the Logical Station Control table. Valid Entry: tag name Valid Data Type: analog Baud Rate Enter the speed at which the protocol module communicates with the devices linked to FactoryLink via this logical. Valid Entry: 110 . Logical Port Enter a number. Valid Entry: tag name Valid Data Type: message LPORT Status Analog Tag (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this logical port. In your server application. Refer to the device manufacturer's manual for details. open Device Interfaces > General Purpose Interface.GENERAL PURPOSE INTERFACE | 13 Accessing the Configuration Tables A CCESSING THE C ONFIGURATION TABLES Note Before completing the protocol-specific Allen-Bradley configuration tables.

in tenths of a second. none (default=none) Data Bits Enter the number of data bits used during transmission via this logical port. Valid Entry: 1 . you must enter a value greater than 0. Refer to the device manufacturer's manual for details.32000 (default=30 or 3 seconds) 220 / FactoryLink Device Interfaces Using EDI Technology . you must enter a value greater than 0. For the protocol module to time out.• • • • 13 | GENERAL PURPOSE INTERFACE Configuring the Logical Station Control Table Parity Enter the parity error correction during transmission via this logical port.32000 (default=30 or 3 seconds) Inter Char Timeout (0. the protocol module allows between the reception of two consecutive characters. This entry must match the configuration of the devices communicating via this port.1 Sec) Enter the maximum amount of time. in tenths of a second. Valid Entry: 1. This entry must match the configuration of the devices communicating via this port. even. 8 (default=8) Stop Bits Enter the number of bits sent after a character to create a pause before the start of the next character. Refer to the device manufacturer's manual for details.1 Sec) This field is required for the protocol module to time out while in unsolicited mode. Valid Entry: 5. Valid Entry: odd. 7. Enter the maximum amount of time. the protocol module will wait to receive the first character of a device response after an outgoing command table that puts the GPI in unsolicited mode is triggered. Valid Entry: 1 . Valid Entry: 1 . Refer to the device manufacturer's manual for details. the protocol module will wait to receive the first character of a device response after an outgoing command table is triggered. This entry must match the configuration of the devices communicating via this port. For the protocol module to time out.1 Sec) Enter the maximum amount of time. 6.32000 (default=30 or 3 seconds) Unsolicited Timeout (0. in tenths of a second. 2 (default=1) Response Timeout (0.

Valid Entry: 256 .32000 (default=1024 bytes) Receive Buff Size Device Type Protocol Type Port On/Off Specify the size of the buffer required to hold the incoming response (the response data). disable the Status Debug Level feature. STAT_OFF Reports only analog error values to the LSTA Status Analog Tag tag STAT_ON Reports analog error values and error message text to the screen FactoryLink Device Interfaces Using EDI Technology / 221 .32000 (default=1024 bytes) (Optional) Enter reference information about the device type. the bytes of the incoming response after they are received (before they are parsed). or LOG2 (depending on the desired debug level) to specify how to log: the bytes of the outgoing message just before they are transmitted.GENERAL PURPOSE INTERFACE | 13 Configuring the Logical Station Control Table Send Buff Size Specify the size of the buffer required to hold the outgoing message (the response command). enter STAT_OFF. When this tag's value is 1. enter either STAT_ON. Valid Entry: tag name Valid Data Type: digital CAUTION During normal operations. Enable this feature only when debugging an application. Valid Entry: alphanumeric string of up to 10 characters (Reserved for future use) Enter a tag name for a digital tag to temporarily disable the sending and receiving of messages to and from devices communicating via this port. LOG1. Valid Entry: 256 . When debugging your application. the port is disabled for GPI messages. Status/ Debug Level During normal operations.

In a command or response table. Later. 222 / FactoryLink Device Interfaces Using EDI Technology . Define the data type (message) for any tag names displayed in the Tag Definition dialog. Valid Entry: tag name Valid Data Type: analog Logical Station [Decimal] Enter a number to identify the logical station to which the information in this row pertains. this number identifies the device to or from which data is to be sent or received. You can animate output-text objects to display the codes stored in an Error/Status Tag Name tag on a graphics screen.• • • • 13 | GENERAL PURPOSE INTERFACE Configuring the Logical Station Information Table LOG1 Performs the functions of STAT_ON and also prints the outgoing and incoming message protocols in hexadecimal bytes LOG2 Performs the functions of LOG1 and also prints the analog error value and error message text to the screen When the table is complete.999 When the table is complete. Assign a unique number to each device communicating through this logical port. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box. click the Save icon to validate the information. click the Save icon to validate the information. Complete a row for each device to communicate through this logical port. A logical station represents the combination of a logical port with a physical station. select the row for the logical port you are configuring and open the Logical Station Information table. Valid Entry: 0 . you will enter this logical station number in a command or response table to represent the device defined in this row. LSTA Status Analog Tag (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station). C ONFIGURING THE L OGICAL S TATION I NFORMATION TABLE From the Logical Station Control table.

For example.” which you configure as a command). A GPI Command/Response table consists of two tables: GPI Command/Response Control and GPI Command/Response Information. you must configure separate command and response tables for both the outgoing message and for the incoming response. in a discussion of the GPI Command/Response Information table for a command table. FactoryLink Device Interfaces Using EDI Technology / 223 . Because you use the same type of GPI Command/Response table to configure both commands and responses. and a response coming from the external device to the GPI (an “incoming response. This protocol contains both a message sent by the GPI to the external device (an “outgoing message. respectively. Use the GPI Command/Response table to define the following: • The outgoing message sent by the GPI (in a command table) • The information needed to parse the incoming response from the external device (in a response table) Note If you expect a response from the external device. The table name is displayed in regular italicized text when the table referred to could apply to either a command or a response table. it is important to be able to distinguish between a command table and a response table. the table is referred to as GPI Command/Response Information. italicized type to help you readily identify the type of table being discussed in this chapter. The tables are referred to with the type of table being configured in boldfaced.” which you configure as a response).GENERAL PURPOSE INTERFACE | 13 GPI Command/Response Table GPI C OMMAND /R ESPONSE TABLE The GPI Command/Response table defines the protocol needed to communicate with an external device.

The commands can be triggered by the FactoryLink application. converted. the command table initiates either a command or response operation to the external device. checksumming. The GPI then extracts the relevant data from the incoming response and writes it to FactoryLink tags. The entries in the command table consist of the following information: • Data from FactoryLink tags • Special characters like preamble/postamble strings or delimiters • Special processing. or mathematical functions If you expect a response to the outgoing message. and returned to FactoryLink tags • Special characters like preamble/postamble strings or delimiters • Special processing. For example. Response Table The response table defines the information needed to parse an incoming response to an asynchronous communication (outgoing message). in an outgoing message. 224 / FactoryLink Device Interfaces Using EDI Technology .• • • • 13 | GENERAL PURPOSE INTERFACE GPI Command/Response Table Command Table The command table defines the complete asynchronous communication protocol and processing needed to format an outgoing message to the external device. or mathematical functions The GPI parses the incoming response from the external device and matches it to the incoming response formats. such as checking embedded message lengths. data format conversions. The entries consist of the following information: • Data to be parsed out of the response. If the command or response operation requires a response from the external device. such as computed message lengths. you must configure this command table to define the end-of-response delimiter of the data from that external device and specify which other table contains the response format. The section “Summary of Basic Concepts” on page 241 contains a diagram that shows how these concepts relate to one another. checksumming. data format conversions. you must configure the command table to specify one or more other response tables that define the possible responses to the outgoing message. It formats (but does not process) any incoming response data.

You can define as many tables in this table as available memory allows. the incoming message will be processed as specified in the GPI Command/Response Information table. it will overwrite the current value and the tag's change-status indicator will be set to 1 (ON). The incoming data is stored and the change-status indicator in each tag is automatically set to 1. accept the default of NO. enter YES or FORCE to indicate whether all change-status indicators are to be set to 1 (ON) when an incoming response occurs. however. If you enter YES. The message will serve as a valid check against the incoming data response and change-status indicators will only be set for tags with values that have changed since the last incoming response. Table Name Assign a name to this command or response table. Define one table per line and do not include spaces in the name. Try to make the table name reflective of the operation it represents. if the values have not changed since the last incoming response. If you enter FORCE. that is. Valid Entry: alphanumeric string of up to 16 characters Enable Response For EDI to interpret this table as an outgoing command. Valid Entry: yes.GENERAL PURPOSE INTERFACE | 13 Configuring the Command/Response Control Table C ONFIGURING THE C OMMAND /R ESPONSE C ONTROL TABLE Open the Command/Response Control table. FactoryLink processes this table and any other table in which the same trigger is defined. and (for a command table) one or more trigger tags. the indicators are still set. Complete a row for each command or response table you want transmitted to a device. or just the ones for values that have changed. if the current value of the tag is equal to the new value. If a different value is being stored the tag. no. the change-status indicator is unaffected. that is. table type. Each row represents a table and includes the table name. regardless of whether the current value matches the new value. When the Command Trigger tag is forced to 1 (ON). For EDI to interpret this table as an incoming response. the incoming message will be processed as specified in the GPI Command/Response Information table. force (default=no) FactoryLink Device Interfaces Using EDI Technology / 225 .

this field is required. Command Trigger If this is an incoming response table. FactoryLink processes the table. and Command Complete tags apply only to outgoing messages. Enter a tag name for a digital tag to disable the operation defined in the Command/Response Information table. Command Disable. it processes the one with the highest priority first. If EDI receives two tables at the same time. Command Sent. Enter a tag name for a digital tag to initiate the operation defined in the Command/Response Information table. this field is optional. When this tag's value is forced to 1 (ON).• • • • 13 | GENERAL PURPOSE INTERFACE Configuring the Command/Response Control Table Command Priority If this is an outgoing command table. 226 / FactoryLink Device Interfaces Using EDI Technology . relative to other command tables.4 (default=1) Note The Command Trigger. ignore this field. Valid Entry: 1 . This number influences the order in which the EDI task handles the queuing of command tables. enter a number to indicate the priority of this table. When this tag's value is forced to 1 (ON). ignore this field. even when the Command Trigger tag is set to 1. the operation is not executed. If this is an outgoing command table you plan to periodically disable. This field defaults to 1 regardless of whether the table being defined is for a command or for a response. Valid Entry: tag name Valid Data Type: digital Command Disable If this is an incoming response table. The highest priority is 1. If this is an outgoing command table. If this is an incoming response table. Do not define these tags for incoming responses. accept the default of 1.

After the data defined in this table's Command/Response Information table is written to the device.GENERAL PURPOSE INTERFACE | 13 Configuring the Command/Response Control Table To reenable a command table that is disabled. The triggering cycle will cease upon disabling. Do not use this tag when more than one logical port is specified in a single table. this field is optional. If this is an outgoing command table and you need a digital tag to indicate when this operation is complete. ignore this field. Valid Entry: tag name Valid Data Type: digital Command Complete If this is an incoming response table. Valid Entry: tag name Valid Data Type: digital Command Sent If this is an incoming response table. this field is optional. Enter a tag name. If this is an outgoing command table and you need a digital tag to indicate the state of this operation (in progress or complete). Valid Entry: tag name Valid Data Type: digital FactoryLink Device Interfaces Using EDI Technology / 227 . however. ignore this field. To reenable a cascaded loop or a self-triggered command table. the Command Trigger tag must be toggled or forced to 1. This tag is forced to 1 (ON) at startup. Enter a tag name. Tip The Command Disable tag can be used to disable a command table that is either part of a cascaded loop or is self-triggered. set this tag back to 0 (OFF). the Command Sent tag is forced to 1 again. the tag is set to 0 (OFF). This tag is forced to 1 (ON) at startup. the Command Complete tag is forced back to 1. After the data defined in this table's Command/Response Information table is written to the device. While the table is being processed. Do not use this tag when more than one logical port is specified in a single table.

If this is an outgoing command table. If this is an incoming response table. 228 / FactoryLink Device Interfaces Using EDI Technology . Valid Entry: previously defined logical station number When the table is complete.• • • • 13 | GENERAL PURPOSE INTERFACE Configuring the Command/Response Control Table Logical Station This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. click the Save icon to validate the information. enter the number representing the device sending the response back to the GPI protocol module. enter the number representing the device to which the operation defined in the Command/Response Information table will be sent.

or mathematical functions. FactoryLink Device Interfaces Using EDI Technology / 229 . special characters such as preamble/postamble strings or delimiters. Each GPI Command/Response Information table defines the complete communication protocol and the processing needed to format one outgoing message to the external device. you must configure at least one FactoryLink tag for each GPI Command/Response table. the GPI Command/Response Information table identifies one or more responses to the communication. The entries in the GPI Command/Response Information table consist of data from FactoryLink tags. see “Associating an Outgoing Message with an Incoming Response” on page 247. FactoryLink tags associated with the STAT_TAG option of the GPI do not satisfy this EDI task requirement. In addition. data format conversions. checksumming. CAUTION To satisfy current EDI task requirements. and special processing such as computed message lengths.GENERAL PURPOSE INTERFACE | 13 Configuring the Command/Response Information Table C ONFIGURING THE C OMMAND /R ESPONSE I NFORMATION TABLE You can configure the GPI Command/Response Information table for commands that can be triggered by the FactoryLink application. Each line of the GPI Command/Response Information table specifies one of the following GPI functions: • Defines a field of the outgoing message or incoming response • Modifies a previously defined field • Specifies a method to detect the end-of-expected-response to the outgoing message in this table • Defines STAT_TAG tags to report the status of transactions • Defines the connector (unique response ID) between the outgoing message and its plausible incoming response For a diagram of these relationships.

and a “dummy” FactoryLink tag name in the Tag Name column. Use this table to define an outgoing message (command) to a device or the parameters of an expected incoming response from a device. select the row for the table you are configuring and open the Command/Response Information table. Valid Entry: tag name Valid Data Type: digital. For a write table. an end-of-response. The tag name associated with this field satisfies the EDI task requirement. From the Command/Response Control table. the command/ response table link. longana. and a “dummy” FactoryLink tag name in the Tag Name column. specify a tag name for a tag in which FactoryLink will store the data read from the device. enter STRING in the Field Type column. To determine what to enter. to satisfy current EDI task requirements. 230 / FactoryLink Device Interfaces Using EDI Technology . • In a command table. specify a tag name for a tag containing a value to be written to the device. do one of the following things: • Enter TAGVALUE in the Field Type column. The field's value comes from the tag specified in the Tag The field's value is specified in the Constant String column for this row. use the following descriptions: To specify the source of the field value: TAGVALUE STRING Name column for this row. NUMERIC. if you configure the GPI for the unsolicited mode. analog. Tag Name For a read table. 0 (zero) in the Field Length column. The GPI will ignore this FactoryLink “dummy” tag. the debug status of the outgoing message or incoming response. float. or PROCESS in the Field Type column. • Enter STRING. message Field Type Specify either the source of the field value.• • • • 13 | GENERAL PURPOSE INTERFACE Configuring the Command/Response Information Table When you configure a GPI Command/Response table. or notification to the application that database updates for the response are done. see “Putting the Protocol Module in Unsolicited Mode” on page 251. For further information about configuring the GPI for the unsolicited mode.

TM column. in the Field Type column for this row. enter the position of the byte giving the response length. In the Response LN. enter RESP_FXD. PROCESS is only valid in a command table. If the entire response can be received in a reasonable amount of time. enter RESP_TM. The field's value is the result of some computation or processing at run time. POS. enter the string. enter the length of the expected response. enter the response time. In the Response LN. POS. TM column. enter RESP_STR. If the expected response is terminated by a string of special characters. Define a tag name for a message tag in the Tag Name column for this row. PROCESS To specify the end-of-response: RESP_FXD If the expected response is known in advance. Define this computation in the Process Function column for this row. RESP_VAR RESP_TM RESP_STR FactoryLink Device Interfaces Using EDI Technology / 231 .GENERAL PURPOSE INTERFACE | 13 Configuring the Command/Response Information Table NUMERIC RAW VALUE The field's value is specified in the Constant Numeric column for this row. in the Field Type column for this row. unparsed response. POS. TM column. in the Field Type column for this row. The field's value is the whole. If the length of the expected response is not known in advance but is given in the incoming response itself. in the Field Type column for this row. In the Response LN. In the Constant String column. enter RESP_VAR.

configure an analog tag and a message tag. long analog.• • • • 13 | GENERAL PURPOSE INTERFACE Configuring the Command/Response Information Table To specify a command/response table link: RESP_ID Enter RESP_ID when specifying a unique response format identification number that identifies the command/response tables in which the protocol module compares a received response with associated response formats. The analog tag reports a numeric value. Enter STAT_TAG in the Field Type column and the tag name in the Tag Name column. The specified tag is set after any values extracted from the incoming message are returned or any status tag is updated with the result of processing (as the result of a STAT_TAG entry). The tag is set to 1 or “1” for a message tag. the incoming response can define only one. To specify application notification of response data completion: DB_DONE (Optional) This field allows you to enter the name of a tag to be set to 1 (one) when the response message is processed. To specify the debug status: STAT_TAG For each outgoing message and incoming response. or message. While you can reference up to eight IDs. The message tag reports an informative message. Note that because of the DB_DONE tag is only set when tag values are updated. float. see “Associating an Outgoing Message with an Incoming Response” on page 247. it cannot be used with a response packet type of MULT_RSP (see definition of Response Packet). Allowed DB_DONE tag types are digital. To indicate which response format from a GPI Command/Response Information table to use to parse the reply to this command. For more information. It is the responsibility of the application to clear the tag if required. complete the Response ID field. analog. 232 / FactoryLink Device Interfaces Using EDI Technology .

for the process function SLxx (shift left xx-bit positions).8 Process Function If you enter PROCESS in the Field Type column. The numbers 1 and 10 define the range of fields over which the XOR function is computed. or map eight bits of an incoming response to eight FactoryLink digital tags. Valid Entry: 1 . In general.999 Field Len. this field is required. this field is required.999 Arg. Process functions perform specific operations on specified fields of a table. l in the first Fld# column. Valid Entry: -32768 . Define the process function and the scope of that function.GENERAL PURPOSE INTERFACE | 13 Configuring the Command/Response Information Table Field Pos. see “Using Process Functions” on page 254. For example. Valid Entry: 1 . you can map up to eight digital tags into a single byte of the outgoing message. For a complete list of process functions and descriptions. Valid Entry: 1 . enter SL in the Process Function column and xx (a decimal number) in the Arg column. If you enter PROCESS in the Field Type column. Enter a decimal number to identify the field's length in bytes. For example.999 (bytes) Enter a decimal number that defines the specific bit of a byte. this field is required. to compute the exclusive-or (XOR) function for fields 1 through 10 (inclusive). enter XOR in Process Function column. Specify a decimal value to be used as a process function argument.+32767 FactoryLink Device Interfaces Using EDI Technology / 233 . and 10 in the second Fld# column. Enter a decimal number to identify this field's position in the completed communication message. Specify a number to indicate the starting range of decimal field numbers over which the process function operates. Valid Entry: 1 . Bit Pos. Fld# If you enter PROCESS in the Field Type column.

Valid Entry: For a list of possible conversion functions. Depending upon the conditions. this field is required. this field is required. RESP_VAR. Valid Entry: 1 .. Every incoming response defines one unique identifier (ID). Define a unique numeric identifier that specifies which response format from a GPI Command/Response Information table to use to parse the reply to this command.• • • • 13 | GENERAL PURPOSE INTERFACE Configuring the Command/Response Information Table Conversion Function Specify the conversion performed on this field after its value is obtained from a FactoryLink tag (as the result of a process function operation) or from incoming data from an external device or process function. POS.255 Response LN. Format String If you enter TSPRINTF in the Conversion Function column. or both. the Constant String column.. and the response length in this column RESP_VAR in the Field Type column. or RESP_STR in the Field Type column. see “Using Conversion Functions” on page 274. or timeout of the expected response. TM If you enter RESP_FXD. position. Valid Entry: 1 . RESP_TM.. Define the length. Valid Entry: alphanumeric string of up to 16 characters Response ID If you enter RESP_ID in the Field Type column. and RESP_TM in the Field Type column 234 / FactoryLink Device Interfaces Using EDI Technology . You know the expected response length in advance You do not know the response length in advance but it is given at the beginning of the response The end of response must be detected by the protocol module from a string of special characters It is not possible to specify the length of the response or a terminating string for the response RESP_FXD in the Field Type column. Enter. Specify information about formatting the field of an outgoing message.. and the string of special characters in the Constant String column RESP_STR in the Field Type column. you might also need to enter information in the Field Type column.999 If. Every outgoing message references from 1 to 8 response Ids. this field is required. and the position of the byte specifying the length in this column RESP_STR in the Field Type column.

Constant Numeric (Optional) If the entry in the Field Type column is NUMERIC. Valid Entry: 0 . define a field value in an outgoing message or a delimiter to parse/match in the incoming response.32657 Constant String (Optional) If you enter STRING or RESP_STR in the Field Type column. FactoryLink Device Interfaces Using EDI Technology / 235 . RESP_TM. RESP_VAR. MULT_RSP You expect a multiple-packet response. SNGL_RSP You expect a single-packet response. When the table is complete. RESP_TM. repeated calls may be necessary to take information from the internal buffer. RESP_VAR. Specify how an incoming response is grouped when it returns to the GPI protocol module: NO_RSP You expect no response. BUFR_RSP GPI processes buffered response data and returns it to FactoryLink. The protocol module will ignore the Field Type entry. define a field value in an outgoing message or a delimiter to parse/match in the incoming response. If you enter NO_RSP. Valid Entry: alphanumeric string of up to 30 characters Comment (Optional) Enter reference information about this table. or RESP_STR in the Field Type column. enter RESP_FXD. for the GPI protocol module to process the table. click the Save icon to validate the information. GPI queues the entire received response in its internal buffer for later retrieval via the BUFR_RSP delimiter in a different outgoing message. or RESP_STR in the Field Type column. this field is required.GENERAL PURPOSE INTERFACE | 13 Configuring the Command/Response Information Table Response Packets If you enter RESP_FXD. GPI processes the received response and returns it to FactoryLink in a single packet.

the value must come either from a FactoryLink tag or from the result of a calculation on other fields. If you know the value at configuration. which specifies the field’s position in the outgoing message or incoming response Note Throughout this chapter. When you enter information in the columns of a command or response table. 236 / FactoryLink Device Interfaces Using EDI Technology . See “Using Process Functions” on page 254 for further information about the process function XOR. For example.• • • • 13 | GENERAL PURPOSE INTERFACE Flexibility and Design of the GPI F LEXIBILITY AND D ESIGN OF THE GPI The primary goal in designing the GPI protocol module was the flexibility to use it with a variety of external devices. you are configuring an outgoing message or an incoming response containing fields that are composed of bytes. then specify it as a constant (numeric or string). To describe each byte. a checksum value may be the result of an exclusive-or (XOR) on the bytes of an outgoing message. the outgoing message from the communication port is just a series of bytes. Enter the following information in the columns of the command tables you configure to describe these bytes: • The Field Type. the term “column” refers to areas for data within the GPI configuration tables. which specifies where to obtain or enter the field’s value • The Field Pos. If you do not know the value of a field or byte at configuration. If the field’s value must be calculated at run time. In simple terms. and the term “field” refers to the fields of a communication message. the GPI needs to know only the byte’s value and its position in the message. the value must be calculated at run time.

Checksum. Using other features of the GPI. LRC. you could construct other divisions or combinations. and Modulo 256. such as CRC.) The illustration describes only one possible scenario. Device Address. including Preamble. FactoryLink Device Interfaces Using EDI Technology / 237 . In this diagram. (The term checksum refers to all error checking schemes. and Postamble. the breakdown of the outgoing message into fields and the length of each field is provided to clarify and to demonstrate the various parts of an outgoing message.GENERAL PURPOSE INTERFACE | 13 Formatting an Outgoing Message F ORMATTING AN O UTGOING M ESSAGE The following components typically comprise the format of the outgoing message: • Preamble • Device Address • Data • Checksum • Postamble The next sections provide the following information for these components: • A diagram of the format and sources of information in the outgoing message • A discussion of the field entries • A sample GPI Command/Response Information table for a command table Format and Sources of Information in the Outgoing Message The outgoing message illustrated in the following diagram consists of several parts. Data.

One-byte digital Data field consisting of 8-bits where only bit6. Two-byte Device Address whose value comes from the analog tag. DTAG4. Ten-byte Data area whose value comes from the message tag. ATAG. Field Description Field 1 Field 2 Field 3 Field 4 Field 5 One-byte constant used as the start-of-command character. 238 / FactoryLink Device Interfaces Using EDI Technology . these correspond to digital tags DTAG6. The other bits do not change. STX. respectively. and bit2 change during the command. the Preamble is a special character whose value you know at configuration. FTAG. MTAG. Four-byte Data area whose value comes from the floating point tag. and DTAG2. bit4.• • • • 13 | GENERAL PURPOSE INTERFACE Formatting an Outgoing Message The fields described in the following table correspond to the fields in the outgoing message illustrated in the previous diagram.

this will be the XOR of all bytes of the message. at configuration. you know the value of the special character Postamble is a special character. Process Funct. see “Configuring the Command/Response Control Table” on page 225. Fld# Fld# Arg. Except for the preamble and postamble fields.GENERAL PURPOSE INTERFACE | 13 Formatting an Outgoing Message Field Description Field 6 Field 7 One-byte Checksum whose value is computed using process function XOR (exclusive-or) on the bytes of fields 2 through 5. Note: An asterisk (*) indicates an entry the GPI does not need and will not use. For a complete GPI Command/Response Information table. ETX. Sample Information Table for a Command Table The format and sources of information for the outgoing message establish a basis for understanding the entries in the table below. FactoryLink Device Interfaces Using EDI Technology / 239 . some of the columns in this table are omitted. Tag Name Field Type Field Pos Field Len Bit Pos. inclusive. One-byte end-of-command character. Constant Numeric Constant String Comment STRING atag dtag2 dtag4 dtag6 ftag mtag * TAGVALUE TAGVALUE TAGVALUE TAGVALUE TAGVALUE TAGVALUE PROCESS 1 2 3 3 3 4 5 6 1 2 1 1 1 4 10 1 * * 2 4 6 * * * * * * * * * * XOR * * * * * * * 2 * * * * * * * 5 * * * * * * * * * * * * * * * * \x02 * * * * * * * STX DEVICE ADDR Data Data Data Data Data Checksum * STRING 7 1 * * * * * * \x03 ETX For simplification purposes.

Disable this feature during normal operations. RAW VALUE This feature allows up to 255 bytes of the incoming response to be read into a FactoryLink message tag before parsing the response. Status/Debug Levels When enabled. this feature logs information about the steps the GPI protocol module takes to compose each outgoing message and to parse each incoming response. 240 / FactoryLink Device Interfaces Using EDI Technology . The following table describes the various levels of status/debug information logged or displayed: Debug Entry Description STAT_OFF STAT_ON LOG1 LOG2 Reports only analog error values to the tag Reports analog error values and message error text to the FactoryLink tag Reports STAT_ON plus prints the outgoing and incoming messages in hexadecimal bytes to the screen Reports LOG2 plus prints the analog error value and error message to the screen For further information about the Debug/Status Level. see the “Configuring the Command/Response Control Table” on page 225. You can use the logged information to debug the application.• • • • 13 | GENERAL PURPOSE INTERFACE Debugging Tools D EBUGGING TOOLS The following tools aid you in debugging the application.

• The position of each field/byte is always known at configuration. • The format of the incoming response is described to the GPI protocol module via an incoming response configured in a response table. FactoryLink Device Interfaces Using EDI Technology / 241 . the value and position of these bytes is of major concern. The following diagram illustrates how to configure two GPI Command/Response tables for an expected response and how to link these tables together with a unique ID (configured in the ID field of the GPI Command/Response Information table). through unique identifiers (IDs). This information is then passed on via FactoryLink analog and message tags. you correlate the command and response tables. S UMMARY OF B ASIC C ONCEPTS The following summarizes the basic concepts of the GPI protocol module: • An outgoing communication message is made up of bytes. • The value of the bytes is either known at the time of configuration or the value is obtained at run time. • The format of the outgoing message is described to the GPI protocol module via an outgoing message configured in a command table. When constructing this outgoing message.GENERAL PURPOSE INTERFACE | 13 Summary of Basic Concepts STAT_TAG This feature provides alphanumeric status information at different stages of the GPI response or command operation. • At configuration.

• • • • 13 | GENERAL PURPOSE INTERFACE Summary of Basic Concepts Diagram of a Complete Communication and Response Command Table Outgoing Message to the External Device ID 101 External Device Response Table Incoming Response Data returned to FactoryLink ID 101 Response 242 / FactoryLink Device Interfaces Using EDI Technology .

FactoryLink Device Interfaces Using EDI Technology / 243 . Completing the Command/Response Information Table You need to define an outgoing message in a command table if your application requires that the GPI protocol module request data from an external device. including specifying packet responses you expect to receive from the external device.” See “Putting the Protocol Module in Unsolicited Mode” on page 251 for information about the unsolicited mode. The GPI Command/Response table describes the external device protocol to the GPI in a “language” the GPI understands. Defining the Outgoing Message Defining the outgoing message involves completing specific columns in the GPI Command/Response Information table for the command table. This puts the GPI protocol module in the “solicited mode. Principles of Operation You must configure the GPI Command/Response tables with the following information to enable communications to occur between a FactoryLink application and an external device via the GPI protocol module: • The format of the outgoing message • The format of the incoming response from the external device Configuring the GPI Command/Response tables requires an understanding of the external device protocol and the options that the GPI protocol module provides.GENERAL PURPOSE INTERFACE | 13 GPI Functions GPI F UNCTIONS This section describes the functions of the GPI protocol module and shows the relationships among the different columns of the GPI configuration tables. See “Configuring the Command/Response Control Table” on page 225 for complete descriptions of the entries in the GPI configuration tables. The sample tables omit some fields to simplify some of the discussions in this section. The GPI provides this language as a set of tools for you to use to set up communications.

RESP_STR Response has a special terminating character defined in Constant field (such as POSTAMBLE “EXT. TM field and the type of packet in the Response Packets field. POS. Specifies the operations performed to produce results which will be substituted for a defined field. RESP_VAR Response length (in bytes) is given in the response itself. STRING String entered at configuration. POS. RESP_TM Response received in a specified amount of time. NUMERIC Constant value entered at configuration. PROCESS Computed value entered at run-time through use of a predefined process function. RESP_FXD Response length (in bytes) is known at configuration. POS. Field Type Defines the following delimiters of an outgoing message: TAGVALUE Tag used for data retrieval or storage. such as XOR (exclusive-or).”). TM field. the response time is defined in the Response LN. Field Pos Field Len Process Function Constant Numeric Constant String Specifies the sequence of the bytes in the outgoing message (external device protocol). 244 / FactoryLink Device Interfaces Using EDI Technology . number of bytes is defined in the Response LN. RESP_ID Unique number assigned to the outgoing message Response ID which matches an incoming message’s Response ID field. TM field. byte position for the response length is defined in the Response LN. Specifies a value used in an outgoing message. Specifies the size of the field in bytes. Specifies a string used in an outgoing message.• • • • 13 | GENERAL PURPOSE INTERFACE GPI Functions Use the following columns in the GPI Command/Response Information table to define the message in the command table for the outgoing message.

) FactoryLink Device Interfaces Using EDI Technology / 245 . Field Type Specify an entry (RESP_FXD.GENERAL PURPOSE INTERFACE | 13 GPI Functions Specifying Packet Responses Use the following columns in the outgoing message command table’s GPI Command/Response Information table to specify packet responses. specify which of the following types of response packets you expect to receive from the external device: • No response – If you do not expect a response to the outgoing message. the collection of data may be too large for a single response table (incoming message) to handle. RESP_VAR. Response Packet In the command table. • Single-packet response – If you expect a single-packet response. the GPI protocol module can return the entire incoming response to the FactoryLink real-time database as the response to a single outgoing message. The MULT_RSP command sets up the queues for the internal buffer but returns no packets until another outgoing message with BUFR_RSP is triggered. or RESP_STR) in the Field Type column for the protocol module to process the table. you may need to trigger the response table several times. enter MULT_RSP in the Response Packet column of the outgoing message. RESP_TM. To do this. RESP_VAR. do not configure a response table (so there will be no unique response identifier). RESP_TM. you must also enter an End-of-Response indicator (RESP_FXD. or RESP_STR) in the Field Type column for each entry in the Response Packets column. • Multiple packet and buffered responses – If you expect a multiple-packet response. To transfer large amounts of data to the FactoryLink real-time database from the GPI internal buffers. (The protocol module will ignore this Field Type entry. The table below describes the valid entries for the Response Packet column in the GPI Command/Response Information table of a command table: Note If you enter NO_RSP. Repeat this triggering as needed until the GPI processes all the buffered data in the Response Packet column.

Processes the received response and returns it to FactoryLink all at once. Processes buffered response data and returns it to FactoryLink. Like the outgoing message. repeated calls may be necessary to take all information from the internal buffer. the incoming response is composed of fields or bytes. Indicate the position of each field of the incoming response by configuring the position in the Field Pos column of the response table’s GPI Command/Response Information table.• • • • 13 | GENERAL PURPOSE INTERFACE GPI Functions Valid Response Type Description NO_RSP SNGL_RSP MULT_RSP Expects no response to the outgoing message. Returns no data to FactoryLink at this time. BUFR_RSP Formatting the Incoming Response Use the following columns in the GPI Command/Response Information table to define the format of the expected response from the external device in the response table for the incoming response: • Field Type • Field Pos • Field Len • Conversion Function • Response Packets • Constant Numeric • Constant String Define the format of the incoming message (the expected response) in the GPI Command/Response Information table for the response table using tags so the GPI can return the response to the FactoryLink database. Queues the entire received response in its internal buffer for later retrieval via the BUFR_RSP delimiter. 246 / FactoryLink Device Interfaces Using EDI Technology .

• If the field’s value is to be returned to FactoryLink. See “Defining the Outgoing Message” on page 243 for further information about entries for the columns of the incoming response. Assign each response format a unique identification (ID) number. enter a -1 in the Field Len column and a delimiter in the Constant String column. • If the field type is NUMERIC or STRING. you can reference up to eight ID numbers. • If you do not know the field length. enter the keyword TAGVALUE in the Field Type column and a tag name in the Tag Name column. then the GPI protocol module parses the field as a response delimiter and expects to find the content of the field in the Constant Numeric and Constant String columns. use a different ID for each response. The GPI protocol module compares the received response with all response formats associated with the RESP_ID in the GPI Command/Response Information table for the corresponding response table (incoming response) and processes it appropriately. enter an identification (ID) number in the Response ID column and the keyword RESP_ID in the Field Type column. enter the length in bytes in the Field Len column.GENERAL PURPOSE INTERFACE | 13 GPI Functions Configure the incoming response using the following guidelines: • If you know the field length. FactoryLink Device Interfaces Using EDI Technology / 247 . In the GPI Command/Response Information table for the command table. If a GPI Command/Response Information table for a command table that defines an outgoing message contains more than one RESP_ID entry. This relationship is illustrated in the following diagram. the incoming response can define only one. Associating an Outgoing Message with an Incoming Response Use the Field Type and Response ID columns in the GPI Command/Response Information table to associate an outgoing message with its incoming (expected) response: In the GPI Command/Response Information table. for the outgoing message and incoming response.

108 Outgoing Message Format Response IDs: 1. 65. 66 Incoming Response Tables Incoming Response Format Unique Response ID: 1 Incoming Response Format Unique Response ID: 21 Incoming Response Format Unique Response ID: 50 Incoming Response Format Unique Response ID: 63 Incoming Response Format Unique Response ID: 65 Incoming Response Format Unique Response ID: 66 Incoming Response Format Unique Response ID: 97 Incoming Response Format Unique Response ID: 108 248 / FactoryLink Device Interfaces Using EDI Technology . 50. 63.• • • • 13 | GENERAL PURPOSE INTERFACE GPI Functions Outgoing Message Tables Outgoing Message Format Response IDs: 1. 97. 65 Outgoing Message Format Response IDs: 21. 21. 63. 66.

To determine the type of response. If the GPI receives the response length in a reasonable amount of time.GENERAL PURPOSE INTERFACE | 13 GPI Functions Specifying Methods to Detect an End-of-Response Use the following columns in the GPI Command/Response Information table for the command table defining the outgoing message to specify various methods to detect an end-of-response. refer to documentation for your specific external device. POS. In the Field Type column of the GPI Command/Response Information table. Also. In the Response LN. TM column: RESP_FXD If the external device returns a fixed response. TM column. TM column. If special characters terminate the response. POS. enter RESP_VAR in the Field Type column. TM column. enter one of the end-of-responses described. POS. Also. If the external device returns a variable length response. enter RESP_STR in the Field Type column. To determine the type of response. POS. also enter corresponding information in the Response LN. POS. enter the response time in the Response LN. TM • Constant Numeric • Constant String Define how the GPI protocol module detects an end-of-response for each outgoing message. • Field Type • Response LN. enter the special characters in the Constant String column. refer to documentation for your specific external device. enter RESP_FXD in the Field Type column. enter the byte position in the response that specifies the number of bytes to follow before you reach the end of the response. if indicated. enter the length of the response in bytes. enter RESP_TM in the Field Type column. In the Response LN. RESP_VAR RESP_TM RESP_STR FactoryLink Device Interfaces Using EDI Technology / 249 .

• • • • 13 | GENERAL PURPOSE INTERFACE GPI Functions Non-Printable or “Do Not Care” Characters Use the following columns in the GPI Command/Response Information table in both the outgoing message and the incoming response for non-printable or “do not care” characters: • Format String • Constant Numeric • Constant String If you enter a string containing non-printable or “do not care” characters in the Constant String column. using this format. ending with D. it can be used in these different ways: • To detect the end-of-response (in conjunction with the RESP_STR option) • As a field delimiter (with the STRING option in a GPI Command/Response Information table) Characters in a string may be one of the following types: • Printable characters – if all characters of the string are printable. followed by the non-printable characters EOT. 250 / FactoryLink Device Interfaces Using EDI Technology .”) Note After the entry \x. you must enter two hexadecimal digits. F. the string A. For example. B. For example. enter ABCD. • Non-printable characters – if one or more of the characters in a string are non-printable. if the string is ABCD. simply enter the string as it appears. (04 is the hexadecimal ASCII value of “EOT. enter \x followed by the Hexadecimal ASCII value of the character. becomes AB\x04DF.

Putting the Protocol Module in Unsolicited Mode Use the following columns in the outgoing message command table’s GPI Command/Response Information table to put the protocol module in the unsolicited mode: • Field Type • Format String • Response Packets • Response ID If your application requires that the GPI receive data from an external device without requesting it. then you must configure and trigger a GPI Command/Response Information table with no field positions specified in a manner that sends a zero (0) length command. Initiating a Transmission Use the Command Trigger column in the outgoing message command table’s GPI Command/Response Control table to initiate a transmission. To initiate the transmission of an outgoing message. some are fixed and some are variable (such as a checksum). trigger the command table’s GPI Command/Response Information table that defines the outgoing message. (See “Configuring the Command/Response Information Table” on FactoryLink Device Interfaces Using EDI Technology / 251 . but ignore the variable characters.GENERAL PURPOSE INTERFACE | 13 GPI Functions The following table lists special non-printable characters used with the GPI protocol module. Use the fixed characters to detect the end of a response. Treat the variable characters like “do not care” characters and enter \xxx in the variable character’s position(s) in the string. Non-Printable Characters \t or \T \n or \N \r or \R \\ Tab New line Carriage return Backslash (\) A response can be terminated by a special string of characters.

enter the same response format information as required for a solicited table. and RESP_STR – describes how to detect the end-of-response • SNGL_RSP. This puts the GPI in unsolicited mode. For the outgoing message. configure two tags — one analog and one message — which are defined in the following manner: • The message tag reports information about status of the outgoing message or incoming response. Reporting Message Status Use the following columns in the GPI Command/Response Information table to report the status of the outgoing message or the incoming response: • Tag Name • Field Type If you configure the proper tags. 252 / FactoryLink Device Interfaces Using EDI Technology . • The analog tag reports a numeric value and can be used in Math and Logic applications. See the Task Configuration Reference Guide for more information.) In other words. RESP_VAR. do not build an outgoing message. the GPI can report the status of each outgoing message or incoming response to FactoryLink.• • • • 13 | GENERAL PURPOSE INTERFACE GPI Functions page 229 for additional information. • RESP_ID – describes which command/response tables to use for parsing the response • RESP_FXD. and MULT_RSP – describes the type of incoming response For information about putting the protocol module in solicited mode. To do this. for each outgoing message or incoming response. see “Defining the Outgoing Message” on page 243.

convert them to a required format using the conversion functions. If you use the same set of tags for the STAT_TAG in different tables. if the device protocol requires ASCII conversion. from a FactoryLink tag Before substituting these values in a field. FactoryLink Device Interfaces Using EDI Technology / 253 . information from one table overwrites information from another table. when parsing the received response and returning values to FactoryLink. For example. Converting a Field’s Value Use the following columns in the GPI Command/Response Information table in both the outgoing message and the incoming response to convert a field’s value: • Tag Name • Field Type • Field Pos • Field Len • Conversion Function In an outgoing message. as a constant • At run time.GENERAL PURPOSE INTERFACE | 13 GPI Functions Enter the tag name in Tag Name column of the GPI Command/Response Information table and the keyword STAT_TAG in the Field Type column. In the incoming response. similar conversions are possible. Note Use different tags for the STAT_TAG entry for different tables. see “Using Conversion Functions” on page 274. the binary value of a field whose source is a FactoryLink tag can be converted to ASCII before transmission. Define a separate set of tags for each outgoing message and incoming response. For a complete list of conversion functions. the values of a field come from two sources: • During configuration.

Calculates the exclusive-or (XOR) of the range of bytes between the first Fld#. The following information describes some of these tasks: LEN Calculates the length of the range of bytes between the first Fld#.• • • • 13 | GENERAL PURPOSE INTERFACE Using Process Functions U SING P ROCESS F UNCTIONS Use the following columns in the outgoing message command table’s GPI Command/Response Information table with process functions: • Field Pos • Process Function • Fld# • Arg Process functions perform several tasks. inclusive and the second Fld# and substitutes the result for the current field. to the value in the current field. Associating a Digital Tag to a Bit Use the following columns in the GPI Command/Response Information table in both the outgoing message and the incoming response to associate a digital tag to a bit: • Tag Name • Field Type • Field Len • Bit Pos 254 / FactoryLink Device Interfaces Using EDI Technology . process functions perform specific operations on entries in the FLD# and Argument columns. Adds the value given in Arg. inclusive and the second Fld# and substitutes the result for the current field. see “Using Process Functions” on page 271. Depending on their functionality. XOR ADD For further information about each process function. The results that these operations produce are substituted for the value in the field being defined.

To link a digital tag to a bit of a field. enter the FactoryLink digital tag in the Tag Name column of the GPI Command/Response Information table. For example. Determining the Sources of Field Values To determine the sources of field values. an LRC value is the result of XOR (exclusive-or) on specific bytes of an outgoing message. you can associate a FactoryLink digital tag to a bit and can also map up to eight FactoryLink digital tags into a single byte. Enter one (1) in the Field Len column. use the following columns in the GPI Command/Response Information table in both the outgoing message and the incoming response: • Tag Name • Field Type • Process Function • Constant Numeric • Constant String Note For the incoming response. the field position will be the same. If the value must be determined at runtime. then it either comes from a FactoryLink tag or results from a calculation. then you can specify it as a numeric constant or string constant. the Process Function is not valid. Note Bit 1 is the LSB (Least Significant Bit) and bit 8 is the MSB (Most Significant Bit) of the byte. If you know the value of a field at configuration.GENERAL PURPOSE INTERFACE | 13 Using Process Functions In the outgoing message and the incoming response. and the position of the bit (1 through 8) in the Bit Pos column. FactoryLink Device Interfaces Using EDI Technology / 255 . For all digital tags accessing the same byte.

use the process function LEN to calculate the number of bytes in a range of fields. and the process function in the Process Function column TAGVALUE in Field Type column. and the specific value of the field for Constant Numeric or Constant String TAGVALUE for Field Type. For example.. Enter the result in the field being defined. and the length of the field for Field Len Extracted from a FactoryLink tag at run-time Computed Returned to FactoryLink from data from the device PROCESS for Field Type. the tag name for Tag Name. Finally. Known at configuration NUMERIC or STRING for Field Type... 256 / FactoryLink Device Interfaces Using EDI Technology . you can modify the same field more than once. use either the process function ADD or SUB to add or subtract a number from this value.. the FactoryLink tag name in Tag Name column. Enter. use the following guidelines: If the Field Value Is. and the length of the field in the Field Len column Modifying a Previously Defined Field Use the following columns in the outgoing message command table’s GPI Command/Response Information table to modify a previously defined field: • Tag Name • Field Type • Process Function By making multiple entries that reference the same Field Position column in the command table.• • • • 13 | GENERAL PURPOSE INTERFACE Using Process Functions To determine the sources of field values. For further information about process functions. see “Using Process Functions” on page 271.

The PMD 300 is an intelligent. and fault indications. The device provides complete information about machine or process diagnostics. The incoming response parameters and tags prepare FactoryLink for the expected reply from the device. FactoryLink Device Interfaces Using EDI Technology / 257 . Configuration Example This section provides configuration table entries for an outgoing message from the GPI and for an expected incoming response from a PMD 300 programmable device. refer to the manufacturer’s documentation. operator prompting. For further information about the PMD 300. alphanumeric display table that interfaces with any type of controller. The outgoing message contains instructions for displaying operator messages.GENERAL PURPOSE INTERFACE | 13 GPI Configuration GPI C ONFIGURATION This section illustrates how to configure an outgoing message for the GPI to communicate with the PMD 300 Programmable Message Display.

For an explanation of the outgoing message format for the PMD 300 device. OUTGOING_MSG. Bit Pos.. sample Command/Response Information table entries for an outgoing message table. Entries for the Outgoing Message Table The following series of tables lists. Table Name: OUTGOING_MSG Field Tag Name Field Type Field Pos. by row. In this section. the entries are presented in several tables to accommodate the numerous table entry columns. Field Len. see “Defining the Outgoing Message to the GPI” on page 267.. NUMERIC PROCESS NUMERIC NUMERIC NUMERIC NUMERIC PROCESS cb1_0 (digital) cb1_4 (digital) cb1_6 (digital) cb2_4 (digital) TAGVALUE TAGVALUE TAGVALUE TAGVALUE 1 2 3 4 5 6 7 8 8 8 9 1 1 1 1 1 1 1 1 1 1 1 258 / FactoryLink Device Interfaces Using EDI Technology .• • • • 13 | GENERAL PURPOSE INTERFACE GPI Configuration Command/Response Information Table Entries The Command/Response Information table entries illustrated in this section instruct the GPI device protocol module to display a message on a PMD 300 display table..

.... Fld# Fld# FactoryLink Device Interfaces Using EDI Technology / 259 .. cb2_6 (digital) cb3_0 (digital) cb3_1 (digital) cb3_2 (digital) cb3_3 (digital) cb3_4 (digital) cb3_5 (digital) cb3_6 (digital) scrlmsg (message) TAGVALUE TAGVALUE TAGVALUE TAGVALUE TAGVALUE TAGVALUE TAGVALUE TAGVALUE TAGVALUE 9 10 10 10 10 10 11 12 13 1 1 1 1 1 1 56 1 1 RESP_VAR RESP_ID stat_msg (message) stat_ana (analog) STAT_TAG STAT_TAG 11 12 56 1 Process Function Tag Name.Process Function Range Arg.. Bit Pos. Field Len..GENERAL PURPOSE INTERFACE | 13 GPI Configuration Field Tag Name Field Type Field Pos... ..

... ...• • • • 13 | GENERAL PURPOSE INTERFACE GPI Configuration Process Function Tag Name.. Fld# Fld# LEN 2 13 LEN cb1_0 (digital) cb1_4 (digital) cb1_6 (digital) cb2_4 (digital) cb2_6 (digital) cb3_0 (digital) cb3_1 (digital) cb3_2 (digital) cb3_3 (digital) cb3_4 (digital) cb3_5 (digital) cb3_6 (digital) scrlmsg (message) 7 11 260 / FactoryLink Device Interfaces Using EDI Technology ..Process Function Range Arg.

Fld# Fld# XOR ONESCOMP 2 12 11 stat_msg (message) stat_ana (analog) Conversion Function Tag Name. . POS..GENERAL PURPOSE INTERFACE | 13 GPI Configuration Process Function Tag Name.. cb1_0 (digital) cb1_4 (digital) cb1_6 (digital) FactoryLink Device Interfaces Using EDI Technology / 261 .Process Function Range Arg........... TM.Conversion Function Format String Response Response ID Response LN.. .

. TM..Conversion Function Format String Response Response ID Response LN.. .• • • • 13 | GENERAL PURPOSE INTERFACE GPI Configuration Conversion Function Tag Name.. POS... cb2_4 (digital) cb2_6 (digital) cb3_0 (digital) cb3_1 (digital) cb3_2 (digital) cb3_3 (digital) cb3_4 (digital) cb3_5 (digital) cb3_6 (digital) scrlmsg (message) 2 111 stat_msg (message) stat_ana (analog) 262 / FactoryLink Device Interfaces Using EDI Technology .

Response Packets Command/Response Constant Numeric Constant String Comment 170 Hex AA CMD Length 16 2 2 1 Unit Addr Unit Addr Msg Len Ctrl Msg Len cb1_0 (digital) cb1_4 (digital) cb1_6 (digital) cb2_4 (digital) cb2_6 (digital) cb3_0 (digital) cb3_1 (digital) cb3_2 (digital) cb3_3 (digital) cb3_4 (digital) cb3_5 (digital) cb3_6 (digital) scrlmsg (message) Ctrl Byte 1 Ctrl Byte 1 Cntrl Byte 1 Ctrl Byte 2 Ctrl Byte 2 Ctrl Byte 3 Ctrl Byte 3 Ctrl Byte 3 Ctrl Byte 3 Ctrl Byte 3 Ctrl Byte 3 Ctrl Byte 3 Scroll Message FactoryLink Device Interfaces Using EDI Technology / 263 ...GENERAL PURPOSE INTERFACE | 13 GPI Configuration Response Tag Name.. ..

..• • • • 13 | GENERAL PURPOSE INTERFACE GPI Configuration Response Tag Name..Analog The following series of tables lists sample Command/Response Information table entries for an incoming response table. that defines parameters for the various types of expected PMD 300 replies to the outgoing message defined in OUTGOING_MSG. . 264 / FactoryLink Device Interfaces Using EDI Technology .Message Status . INCOMING_RSP..Response Packets Command/Response Constant Numeric Constant String Comment Exclusive-Or One’s Complement sngl_rsp Response Variable Response ID stat_msg (message) stat_ana (analog) Entries for Incoming Response Table Status .

......Process Function Range Arg. Fld# Fld# length uaddr reply FactoryLink Device Interfaces Using EDI Technology / 265 .. . Field Len..GENERAL PURPOSE INTERFACE | 13 GPI Configuration Table Name: INCOMING_RSP Field Tag Name Field Type Field Pos. Bit Pos. NUMERIC length uaddr TAGVALUE TAGVALUE NUMERIC reply error cksum TAGVALUE TAGVALUE TAGVALUE RESP_ID astring mstring STAT_TAG STAT_TAG 1 2 3 4 5 6 7 1 1 2 1 1 1 2 Process Function Tag Name...

.. Fld# Fld# error cksum astring mstring Conversion Function Tag Name.... .. length uaddr HI-LOW16 reply error cksum HI-LOW16 astring mstring 266 / FactoryLink Device Interfaces Using EDI Technology . TM...Conversion Function Format String Response Response ID Response LN.....Process Function Range Arg..• • • • 13 | GENERAL PURPOSE INTERFACE GPI Configuration Process Function Tag Name. POS..

Response Packets Command/Response Constant Numeric Constant String Comment 170 length uaddr 0 reply error cksum Hex AA Length Unit Address Place Holder (Delimiter) Reply Code Error Code Error Checking Response ID astring mstring Analog Status Tag Analog Status Tag Defining the Outgoing Message to the GPI The field entries described below are for the sample GPI configuration: 1 2 One-byte numeric constant with a value of 170 (Hex AA).GENERAL PURPOSE INTERFACE | 13 GPI Configuration Response Tag Name..13 (inclusive). Use the result of the calculation as the value of the second field of the outgoing message. 3. 4.. .. 5. The process function LEN calculates the number of bytes in Fields 2 .. Enter their corresponding values in the Constant Numeric column. Size equals the length of the entire outgoing message except for the first byte (Hex AA). 6 FactoryLink Device Interfaces Using EDI Technology / 267 . One-byte numeric types whose values you know at configuration.

FactoryLink message tag STAT_MSG and analog tag STAT_ANA. and CB1_6—to bits 1. therefore. 9. contains the string that the PMD 300 will display on screen. 268 / FactoryLink Device Interfaces Using EDI Technology . These are control bytes. CB3_3. The LEN process function calculates the number of bytes of fields 7 . and 10. This example defines the digital tags in the following manner: The FactoryLink application links three digital tags—CB1_0.11 (inclusive). Process functions that calculate the checksum using the PMD 300 protocol. 8. use process function XOR on this range of fields.• • • • 13 | GENERAL PURPOSE INTERFACE GPI Configuration 7 The length of the string to be displayed on the device plus the number of control bytes. which is 56 bytes long and linked to field 11.11 (inclusive).) The FactoryLink application links seven digital tags—cb3_0. The FactoryLink message tag SCRLMSG. The PMD 300 customizes the string displayed on its screen using the value of these control bytes. 13 RESP_ID RESP_VAR STAT_TAG The unique response ID is 111. (Field 7 in this example is the second control byte for the PMD 300 protocol. Field 13 is the one's complement of the previous field. and 7 of field 8 (control byte 1). Field 12 is the exclusive-or (XOR) of all the bytes from fields 2 . This provides much flexibility at the application level. The FactoryLink application controls the PMD device's capabilities by linking various digital tags (up to eight per byte) to individual bits of these control bytes. The following three entries for the sample GPI configuration do not require field positions: 12. CB3_2. Three control bytes occupy fields 8. CB1_4. The result is the value of Byte 7. The FactoryLink links two digital tags—CB2_4 and CB2_6—to bits 5 and 7 of Field 9 (control byte 2). CB3_4. CB3_1. Single packet response. length is the second byte of the response data. 5. CB3_5. and CB3_6—to field 3 (control byte 3). 10 11 TAGVALUE. 9.

111. specifies a variable-length response. In the Response Packet column. SNGL_RSP. According to the PMD 300 protocol. the single-packet response.GENERAL PURPOSE INTERFACE | 13 GPI Configuration Defining Response Termination and Status Tags The PMD 300 example illustrates how to define response termination and status tags. enter a 2 (for the second byte) in the Response LN. the single-packet response SNGL_RSP is an example of a common response. The next line in the table matches the response to the response format required by the outgoing message with the unique response ID. The GPI protocol module then relays this status/error information about the outgoing message which is transmitted to the device. This allows the GPI protocol module to report the status of the outgoing message to the FactoryLink application. The number of bytes in the response begins with third byte. In the Field Type column of the PMD 300 GPI Command/Response table. FactoryLink Device Interfaces Using EDI Technology / 269 . POS. the second byte of the response specifies the length of the response. For the GPI protocol module to detect the end-of-response. The last two lines of the table define FactoryLink analog and message tags. TM column.

• • • • 13 | GENERAL PURPOSE INTERFACE GPI Configuration Defining the Incoming Response to the GPI The following field entries describe the sample GPI configuration: 1 2 3 4 5 6 7 One-byte numeric constant with a value of 170 (hexadecimal value AA) One-byte length of the incoming message stored in a FactoryLink analog tag Two-byte unit address received in HILOW format One-byte numeric place holder (delimiter) One-byte reply code that will be stored in a FactoryLink analog tag One-byte error code that will be stored in a FactoryLink analog tag Two-byte checksum received in HILOW format that will be stored in a FactoryLink analog tag The unique response ID is 111 FactoryLink tags ASTRING and MSTRING The following entries do not require field positions: RESP_ID STAT_TAG 270 / FactoryLink Device Interfaces Using EDI Technology .

process functions perform various operations on entries in the GPI tables. Note For the Field Type PROCESS. Also. then. Uses Arg to set the initial value. CRCCC_RV CRCCC_RV FLD#.GENERAL PURPOSE INTERFACE | 13 Using Process Functions U SING P ROCESS F UNCTIONS This section contains information about the process functions to use with the GPI protocol module. Arg ADDS the value given in Arg to the present value of the current field. enter a specific process function in the FLD# and Arg columns. Arg Computes the CRC of the specified range using a CRC_SEED=0x8408 (inclusive). the Field Length can only be 1 or 2 bytes. if a PROCESS FUNCTION has entries in the FLD# or Arg columns. To produce the desired value. Bit-wise AND operation on FLD#. FactoryLink Device Interfaces Using EDI Technology / 271 . FLD# CRCCCITT FLD#. Depending on their functionality. it is a “char” (1-byte) or a “short” (2-bytes). Process Functions Table The table below describes operations of each process function: Name Use Description ADD AM AND CRCCCITT ADD Arg AM Arg AND. AND MASKS (AM) the value of the current field with the value in Arg. Uses Arg to set the initial value. Computes the CRC of the specified range using a CRC_SEED=0x1021 (inclusive). depending on the value specified in the Field Length.

FLD#. uses Arg to set the initial value. inclusive. Puts the ONE'S COMPLEMENT of FLD# notice current field. Uses Arg to set the initial value. Arg MOD256 EM EOR LEN MOD256. Uses Arg to set the initial value. Bit-wise OR operation on FLD#. FLD# OM ONESCOMP OM Arg ONESCOMP FLD# TWOSCOMP FLD# OR SL OR. Arg EM Arg EOR. SHIFTS LEFT (SL) the value of the current field Arg number of times. Computes Modulo 256 checksum. Computes the LENGTH in bytes of a range of fields in a message starting with number in the first FLD# through the second FLD#. Arg Computes the CRC of the specified range using a CRC_SEED=0x8005 (inclusive). FLD# SL Arg 272 / FactoryLink Device Interfaces Using EDI Technology . (ONESCOMP is the same as negation.• • • • 13 | GENERAL PURPOSE INTERFACE Using Process Functions Name Use Description CRC16 CRC16 FLD#. Bit-wise EXCLUSIVE-OR operation on FLD#. Exclusive-or the value of the current field with the value in Arg. CRC16_RV CRC16_RV FLD#. OR MASKS (OM) the value of the current field with the value in Arg. Computes the CRC of the specified range using a CRC_SEED=0xA001 (inclusive). Substitutes the result for the current field. FLD# LEN.) Puts the TWO'S COMPLEMENT of FLD# into the current field.

SWAPs the two consecutive bytes in the current field. and substitutes the result for the current field. Computes the EXCLUSIVE-Or of the range of bytes between FLD#. inclusive. SUBtracts the value given in Arg from the present value of the current field.GENERAL PURPOSE INTERFACE | 13 Using Process Functions Name Use Description SR SUB SWAP XOR R Arg SUB Arg SWAP XOR. FLD# SHIFTS RIGHT (SR) the value of the current field Arg number of times. FactoryLink Device Interfaces Using EDI Technology / 273 .

from a constant Before substituting these values in the field. you can convert them to some other type of value. the GPI uses ANSI C standard functions to convert ASCII numerals to appropriate FactoryLink data types as follows: GPI Conversion FunctionName ANSI C Function FactoryLink Data Type A_TO_FL A_TO_FL A_TO_FL atoi( ) atol( ) atof( ) ANALOG LONGANA FLOAT ASCII BCD BINARY DECASC DECIMAL HEX Converts like %s format Binary Coded Decimal Base 2 Converts like %0d format Base 10 Base 16 274 / FactoryLink Device Interfaces Using EDI Technology . the binary value of a field whose source is a FactoryLink tag can be converted to ASCII before transmission. The table below shows various conversion functions to use with the GPI protocol module: Name Description A_TO_FL When parsing the response used to convert ASCII numerals to the appropriate FactoryLink data type. For example. from a FactoryLink tag • During configuration. it is possible to perform similar conversions.• • • • 13 | GENERAL PURPOSE INTERFACE Using Conversion Functions U SING C ONVERSION F UNCTIONS The contents of a field in an outgoing message can come from a two sources: • At run time. When parsing the incoming message or returning values to the FactoryLink tags.

Longana.). FactoryLink Device Interfaces Using EDI Technology / 275 . LSDW is the least-significant double word. It recognizes width and pad specifications (%3d. %lX. %03d. etc. MSW is the most-significant word. %lu. and Message types with the appropriate format string. %g) and minimum widths. %u. %d. LSW is the least-significant word. Double Word is a 4-byte entity.GENERAL PURPOSE INTERFACE | 13 Using Conversion Functions Name Description HEXASC HILOW16 HILOW32 IEEEHL4 IEEELH4 IEEEHL8 IEEELH8 LOWHI16 LOWHI32 Converts like %0x format Converts to a 2-byte MSB LSB Converts to a 4-byte MSW LSW Converts to a 4-byte IEEE MSW LSW Converts to a 4-byte IEEE LSW MSW Converts to an 8-byte IEEE MSDW LSDW Converts to an 8-byte IEEE LSDW MSDW Converts to a 2-byte LSB MSB Converts to a 4-byte LSW MSW MBUSFLOT Converts to a Modicon float format where: LSB is the least-significant byte. Note: Because the TSPRINTF function does not recognize floating-point formats (%e. %lx. %0. and %%. NONE OCTASC TSPRINTF No conversion necessary Converts like %0 format Converts according to the explicit format given in the Format String column. %x. the TSPRINTF function is a “tiny” sprintf( ) that handles %s. %f. long values. %l0. and left or right justification. Word is a 2-byte entity. use this function with FactoryLink Analog. MSDW is the most-significant double word. MSB is the most-significant byte.

Use these as examples of protocols and not in your specific application. Response Protocols Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 @ 0001 Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 RESP_ID xxxx xxxx FCS * CR (1 byte) Preamble Constant value (2 byte) PLC device address Constant value (2 byte) Response chars Constant value or FactoryLink analog tag (2 byte) Response header charsd Constant value or FactoryLink analog tag (2 byte) Frame check sequence PROCESS (1 byte) Command terminator Constant value (1 byte) Postamble Constant value 101 Constant value “CR” RESP_STR 276 / FactoryLink Device Interfaces Using EDI Technology .• • • • 13 | GENERAL PURPOSE INTERFACE Sample Protocols S AMPLE P ROTOCOLS This section provides sample protocols that illustrate the format of various messages and responses.

digital. or float tag (1 byte) FCS Checksum codes Constant value (Optional) (1 byte) Command terminator Constant value (Optional) (1 byte) Postamble Constant value (Optional) 101 FactoryLink Device Interfaces Using EDI Technology / 277 .GENERAL PURPOSE INTERFACE | 13 Sample Protocols Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 # 0001 Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 RESP_ID xxxx xxxx xxxx FCS * CR (1 byte) Preamble Constant value (2 byte) PLC device address Constant value (2 byte) Response chars FactoryLink analog tag (2 byte) Response header chars FactoryLink analog tag (2 byte) Frame check sequence FactoryLink analog.

• • • • 13 | GENERAL PURPOSE INTERFACE Sample Protocols Command Protocols Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 @ 0001 Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 RESP_ID xxxx xxxx xxxx FCS * CR (1 byte) Preamble Constant value (2 byte) PLC device address Constant value (2 byte) Command chars Constant value or FactoryLink analog tag (2 byte) Command header chars Constant value or FactoryLink analog tag (?-byte) Command data FactoryLink analog. or float tags (2 byte) Frame check sequence Process function (1 byte) Command terminator Constant value (1 byte) Postamble Constant value 222 Length of 11 bytes constant value RESP_FXD Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 # 0001 Field 1 Field 2 xxxx xxxx FCS * CR (1 byte) Preamble Constant value (2 byte) PLC device address Constant value 278 / FactoryLink Device Interfaces Using EDI Technology . digital.

GENERAL PURPOSE INTERFACE | 13 Sample Protocols Field 3 Field 4 Field 5 Field 6 Field 7 RESP_ID (2 byte) Response chars FactoryLink analog tag (2 byte) Response header chars FactoryLink analog tag (2 byte) Frame check sequence Constant value (Optional) (1 byte) Response terminator Constant value (Optional) (1 byte) Postamble Constant value (Optional) 222 Network Response Protocols Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 Field 9 Field 10 Field 11 : xxxx Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 01 xx 0006 20 xx xxxx xxxx xxxx . (1 byte) Preamble Constant value (2 byte) Length of network command Constant value (1 byte) Network send data command Constant value (1 byte) Secondary network address Constant value (2 byte) Response length Constant value (1 byte) Response code Constant value (1 byte) Response memory type Constant value FactoryLink Device Interfaces Using EDI Technology / 279 .

(1 byte) Preamble Constant value (2 byte) Length of network command Constant value (1 byte) Network send data command Constant value (1 byte) Secondary network address Constant value (2 byte) Response length Constant value (1 byte) Response command code Constant value (1 byte) Response memory type Constant value (1 byte) # of data tags Constant value 280 / FactoryLink Device Interfaces Using EDI Technology .• • • • 13 | GENERAL PURPOSE INTERFACE Sample Protocols Field 8 Field 9 Field 10 Field 11 RESP_ID RESP_STR (1 byte) # of data tags Constant value (?-byte) Address of response data Constant value (2 byte) Checksum codes Process function (1 byte) Postamble Constant value (Optional) 1 Constant string (.) Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 Field 9 Field 10 Field 11 : xxxx Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 01 xx 0006 20 xx xxxx xxxx xxxx .

or float tag (2 byte) Checksum codes Process function (1 byte) Postamble Constant value (Optional) 1 Network Command Protocols Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 Field 9 Field 10 Field 11 : xxxx 01 Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 Field 9 xx 0006 20 xx xxxx DDDD xxxx . digital. or float tag(s) FactoryLink Device Interfaces Using EDI Technology / 281 .GENERAL PURPOSE INTERFACE | 13 Sample Protocols Field 9 Field 10 Field 11 RESP_ID (?-byte) Response data from device FactoryLink analog. digital. (1 byte) Preamble Constant value (2 byte) Length of network command Constant value (1 byte) Network send data command Constant value (1 byte) Secondary network address Constant value (2 byte) Command length Constant value (1 byte) Command code Constant value (1 byte) Command memory type Constant value (1 byte) # of data tags Constant value (?-byte) Command data FactoryLink analog.

• • • • 13 | GENERAL PURPOSE INTERFACE Sample Protocols Field 10 Field 11 RESP_ID RESP_STR (2 byte) Checksum codes Process function (1 byte) Postamble Constant value 555 Constant string (.) Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 Field 9 Field 10 Field 11 Field 12 : xxxx 01 xx Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 Field 9 0005 xx 30 HH EE FF xxxx . (1 byte) Preamble Constant value (2 byte) Length of network command Constant value (1 byte) Network send data command Constant value (1 byte) Secondary network address Constant value (2 byte) Command length Constant value (1 byte) Command error code FactoryLink analog or digital tag (1 byte) Command code Constant value (Place holder) (1 byte) Attached device status FactoryLink analog tag or digital tag (1 byte) Device auxiliary power source FactoryLink analog or digital tag (1 byte) NIM status code FactoryLink analog or digital tag Field 10 282 / FactoryLink Device Interfaces Using EDI Technology .

GENERAL PURPOSE INTERFACE | 13 Sample Protocols Field 11 Field 12 RESP_ID (2 byte) Checksum codes FactoryLink analog (Optional) (1 byte) Postamble Constant value (Optional) 555 FactoryLink Device Interfaces Using EDI Technology / 283 .

• The GPI reports an alphanumeric description via FactoryLink message tags. Following are the formats for the GPI error codes: • The GPI reports a numeric code via FactoryLink analog tags. writes them to message or analog tags. At startup. • The GPI uses odd-numbered codes as error codes. see “Messages and Codes” on page 147. if so configured. FactoryLink generates and displays messages for the Allen-Bradley protocol module on the Run-Time Manager screen and. the FactoryLink application checks their status. • The GPI uses even-numbered codes as information or acknowledgment codes. GPI Error Codes The remainder of this section describes the status/error codes written to FactoryLink analog and message tags and defined through the STAT_TAG feature of the GPI protocol module. These codes apply to the operation of the logical port (the GPI protocol module) as a whole. • The GPI uses 1xx codes for making or transmitting the outgoing message. 284 / FactoryLink Device Interfaces Using EDI Technology . For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. They are not related to the individual transactions. see “Configuring the Logical Station Control Table” on page 219 and “Configuring the Logical Station Information Table” on page 222. • The GPI uses 2xx codes for parsing the response. • The GPI uses 3xx codes for the logical port and reports them to the logical port MSG STATUS tags. For information about configuring these tags.• • • • 13 | GENERAL PURPOSE INTERFACE Run-Time Application Messages R UN -TIME A PPLICATION M ESSAGES During EDI runtime.

FLD #%D ASYNDSF.C(WRT_DO_NUMERIC): Invld cnvr Func %d NUMERIC.C(WRT_DO_PROCESS): Invld PROCESS Func %d. FLD #%D ASYNDSF.C(WRT_DO_PROCESS): Invld PROCESS Func %d.c(DSF_WRITE): Start to make the cmnd asyncpt(xmit) xmitED MSG SUCCESSFULLY 1xx: Odd-Numbered Error Codes for Building/Transmitting the Outgoing Message Analog Message Tag 101 103 105 107 109 111 113 115 117 119 121 123 125 ASYNDSF.C(WRT_DO_PROCESS): Invld cnvr FUNC%D for PROCESS.C(DSF_WRITE): MAX_TERM_STR reached ASYNDSF. fld #%d for for ASYNDSF.C(DSF_WRITE): dsf_t_q_mail returned ERROR ASYNDSF.C(WRT_DO_STRING): Invld cnvr FUNC %D STRING.C(DSF_WRITE): cmnd length of %d exceeds SND_BUF_LEN.C(WRT_DO_PROCESS): Invld cnvr Func %d PROCESS.GENERAL PURPOSE INTERFACE | 13 Run-Time Application Messages 1xx: Even-Numbered Information/Acknowledge Codes for Building/Transmitting the Outgoing Message Analog Message Tag 100 102 asyndsf.fld #%d ASYNDSF. FLD#%D ASYNDSF. #%d ASYNDSF.C(WRT_DO_PROCESS): Invld fld len%d for a PROC_FUNC FLD #%D ASYNCPT(XMIT): xmit error for fld FactoryLink Device Interfaces Using EDI Technology / 285 . fld #%d ASYNDSF.C(GET_BUF_INX): Invalid INFO_TYPE=%D IN DIV_DEF ASYNDSF. FLD %d ASYNDSF.C(DSF_WRITE): Invalid FLD TYPE %d.

C(PROCESS_RESPONSE): Start to PROC RESP #%D ASYNDSF. not found ASYNDSF. not found ASYNDSF.INFO_TYPE=%D. RSP ID #%D. Exceeded 255.C(PROCESS_RESPONSE): MULT_RSP Completed ASYNDSF. RSP ID #%D.C(PROCESS_RESPONSE): RSP_TM_OUT ASYNDSF.C(PROCESS_RESPONSE): RESPONSE ERROR ASYNDSF.• • • • 13 | GENERAL PURPOSE INTERFACE Run-Time Application Messages 2xx: Even-Numbered Informative/Acknowledge Codes for Parsing the Response Analog Message Tag 200 202 204 ASYNDSF.C(RD_DO_TAGVALUE): Fld. Len.C(GET_USL_BUF_INX): DLMTR FOR FLD #%D. RSP ID #%D ASYNDSF.C(RD_DO_TAGVALUE): Invalid CNVR for digital.C(GET_USL_BUF_INX): DLMTR FOR FLD # %D. RPS_ID =%D ASYNDSF. INX%D.C(MATCH_RSP): Invalid DIV-DS.C(PROCESS_RESPONSE): ProcessED Resp ID# %d AOK 2xx: Odd-Numbered Error Codes for Parsing the Response Analog Message Tag 201 203 205 207 209 211 213 215 217 219 221 ASYNDSF.C(GET_USL_BUF_INX): End of RSP_BUF reached INX %D. FLD# %D 286 / FactoryLink Device Interfaces Using EDI Technology . RESP #%D ASYNDSF. RSP ID #%D ASYNDSF.C(GET_USL_BUF_INX): End of RSP_BUF REACHED. FLD #%D. FLD #%D.C(PROCESS_RESPONSE): inter char time out ASYNDSF.C(PROCESS_RESPONSE): RSP_BUF too short %d ASYNDSF.

GENERAL PURPOSE INTERFACE | 13 Run-Time Application Messages Analog Message Tag 223 225 227 229 231 233 235 237 239 241 243 ASYNDSF. FLD# %D ASYNDSF(RD_DO_TAGVALUE): Invalid cnvr for float. FLD# %D ASYNDSF. Resp #%d ASYNDSF. Parser failed FLD# %D ASYNDSF.C(RD_DO_RAWVALUE): Fld. FLD# %D ASYNDSF. Len. Exceeded 255.C(RD_DO_RAWVALUE): Invalid FL_TYPE %d for RAWVALUE ASYNDSF.C(RD_DO_TAGVALUE): Invalid cnvr for MESSAGE Tag.C(PROCESS_RESPONSE): USL_TM_OUT FactoryLink Device Interfaces Using EDI Technology / 287 .C(RD_DO_TAGVALUE): Invalid cnvr for lanalog.C(RD_DO_STRING): STRING. Parser failed. FLD# %D ASYNDSF.C(RD_DO_TAGVALUE): Invalid fl_type%d for FLD# %D ASYNDSF.C(RD_DO_TAGVALUE): Invalid cnvr for analog.C(RD_DO_NUMERIC): NUMERIC.C(RD_DO_RAWVALUE): Invalid cnvr for MESSAGE Tag fld#%d ASYNDSF. FLD#%D ASYNDSF.

C(ALLOC_MEM_ON_ARTIC): Unable to alloc mem on ARTIC for RCV BUFR %D bytes ASYNDSF.C(ALLOC_MEM_ON_ARTIC): AllocED %d bytes on Artic for RCV BUFR ASYNDSF.C(ALLOC_MEM_ON_ARTIC): AllocED %d bytes on ARTIC for SND bufr ASYNDSF.C(ALLOC_MEM_ON_SU): Unable to alloc mem for SND BUFR ASYNDSF.C (DSF_START): PORT_SETUP_AOK 3xx: Odd-Numbered Error Codes for the Logical Port Analog Message Tag 301 303 305 307 311 313 315 317 ASYNDSF.• • • • 13 | GENERAL PURPOSE INTERFACE Run-Time Application Messages 3xx: Even-Numbered Informative/Acknowledge Codes for the Logical Port Analog Message Tag 302 304 306 308 310 314 ASYNDSF.C(CPT_START): Protection bit failure (ASYNCPT) ASYNCPT.C(ALLOC_MEM_ON_SU): ALLOCED %D bytes for RCV BUFR ASYNDSF.C(FREE_MEM_ON_SU): freed mem for send and RCV BUFRS ASYNDSF.C(CPT_TSLICE): unknown state: %d ASYNCPT.C(XMIT): xmit error 288 / FactoryLink Device Interfaces Using EDI Technology .C(ALLOC_MEM_ON_ARTIC): Unable to alloc mem on Artic for SND BUFR %D bytes ASYNDSF.C(ALLOC_MEM_ON_SU): Unable to alloc mem for RCV BUFR ASYNCPT.C(CPT_START): PORT_SETUP failed%04Xh ASYNCPT.C(ALLOC_MEM_ON_SU): ALLOCED %D bytes for SND BUFR ASYNDSF.

C(XMIT): CPT_SND_USL returned: %04XH ASYNCPT.GENERAL PURPOSE INTERFACE | 13 Run-Time Application Messages Analog Message Tag 319 321 323 325 327 329 331 333 335 337 ASYNCPT.C(RCV_FINITO): CPT_SND_USL returned: %04XH FactoryLink Device Interfaces Using EDI Technology / 289 .C(RCV_CHAR): TOTAL_TM_OUT reached ASYNCPT.C(RCV_CK_RSP_TM): RSP_TM_OUT error ASYNCPT.C(RCV_CHAR): ICH_TM_OUT error ASYNCPT.C(RCV_RSP_TM): TOTAL_TM_OUT reached ASYNCPT.C(RCV_CK_RSP_TM): USL_TM_OUT error ASYNCPT.C(XMIT): INVALID PKT_TYPE: %04XH ASYNCPT.C(RCV_CHAR): receive character error %04Xh ASYNCPT.C(RCV_CK_RSP_TM): receive character error %04XH ASYNCPT.

• • • • 13 | GENERAL PURPOSE INTERFACE Run-Time Application Messages 290 / FactoryLink Device Interfaces Using EDI Technology .

Chapter 14 • • • Modbus Plus The FactoryLink EDI task allows you to configure bidirectional communications between the FactoryLink real-time database and any Modicon Modbus Plus PLC. Sample table entries are provided in “Reading Data from a Device” on page 73 and “Writing Data to a Device” on page 97. open Device Interfaces > Modicon Modbus Plus. you must complete the External Device Definition table. • FactoryLink Device Interfaces Using EDI Technology / 291 . In your server application. Note Before completing the protocol-specific Modbus configuration tables. See “Identifying Protocol Types and Defining Logical Ports” on page 58 for details.

click the Save icon to validate the information. 292 / FactoryLink Device Interfaces Using EDI Technology . Valid Entry: previously defined logical port number Adapter Number Enter the number assigned to the SA85 host adapter. defined in the External Device Definition table Logical Port column.8 DS1 through DS8 Specify whether or not this path can be used as a data slave (DS) path for unsolicited data. follow the installation procedure in the appropriate LNET (LocalNet Library) software manual to set up the SA85 driver for your specific hardware system. Define the data type (message) for any tag names displayed in the Tag Definition dialog box. refer to the Modicon Modbus Plus documentation. This can be one of the following: YES This path can be used as a data slave path. Valid Entry: 1 . to represent a particular communication path to a device. Valid Entry: 0 or 1 LPORT Status Message Tag (Optional) Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. NO This path cannot be used as a data slave path. Configure the SA85 card as adapter 0 or 1. These fields enable you to specify up to eight paths. For information about data slave paths.• • • • 14 | MODBUS PLUS Configuring the Logical Station Control Table C ONFIGURING THE L OGICAL S TATION C ONTROL TABLE Open the Logical Station Control table. In a Windows environment. When the table is complete. Valid Entry: tag name Valid Data Type: message Data Master Paths Enter a number between 1 and 8 that defines the number of internal master paths on the SA85 device for command/response transactions. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. Logical Port Enter a number.

You can specify 984-BITWRITE for the following Modicon models: A120. 685E. You can animate output-text objects to display the codes stored in an Error/Status tag on a graphics screen. LSTA Status Analog Tag (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station). Be sure this number corresponds to the actual address setting of the device. this number will identify the device to or from which data is to be sent or received. Assign a unique number to each device communicating through this logical port.999 (default=0) PLC Type Enter the type of Modicon device represented by this entry. You will later enter this logical station number in a read or write table to represent the device defined in this row. Use 984-BITWRITE if mask write operations are supported by this device. select the row for the logical port you are configuring and open the Logical Station Information table. Valid Entry: 0 . A logical station represents the combination of a logical port with a physical station. Valid Entry: 1 . Valid Entry: tag name Valid Data Type: analog Logical Station Decimal Enter a number to identify the logical station to which the information in this row pertains. Valid Entry: 984 or 984-BITWRITE Physical Station Enter the physical address of the Modicon device represented by this entry. VM4. Complete a row for each device to communicate through this logical port.MODBUS PLUS | 14 Configuring the Logical Station Information Table C ONFIGURING THE L OGICAL STATION I NFORMATION TABLE From the Logical Station Control table. A145. 785E. Valid Entry: 1 .64 (default=1) Router 1 .64 FactoryLink Device Interfaces Using EDI Technology / 293 . A130.Router 4 Enter a number between 1 and 64 that defines the Modbus Plus network address of a router/bridge. Up to four routes can be defined for each physical station. A141. AT4. In a read or write table.

• • • • 14 | MODBUS PLUS Configuring the Logical Station Information Table Response Timeout 0. Valid Entry: alphanumeric string of 1 to 16 characters When the table is complete. timeout occurs after 3 seconds has elapsed. This tag works in conjunction with the LSTA Failure Digital Tag field to display a meaningful error message for the operator on the Alarm Supervisor screen. Valid Entry: 0 . Define the data type (analog) for any tag names displayed in the Tag Definition dialog box.01 sec Enter the length of time.300 (default=100) Number of Retries Enter a number between 0 and 10 that defines the maximum number of consecutive times a read or write command is sent before communications between FactoryLink and the device terminates for that transmission attempt. If the value of this tag is 0 (off). Valid Entry: tag name Valid Data Type: message Comment (Optional) Enter reference information about this logical station. communications terminates in 9 seconds for that transmission attempt. Valid Entry: 1 . You must enter a value greater than 0 for the protocol module to timeout. Valid Entry: tag name Valid Data Type: digital LSTA Failure Message Tag (Optional) Enter a tag name assigned to reference a message tag that contains text describing the status of communication attempts for this logical station. in hundredths of a second. if you specify 300. For example. the communication attempt to this logical station failed. If the value of this tag is 1 (on). that the protocol module will wait to receive a response to a read or write command before timing out. You can employ this tag to create an alarm in the Alarm Supervisor that indicates a communication failure. click the Save icon to validate the information. the communication attempt to this logical station was successful. If the number of retries is 3.10 (default=3) LSTA Failure Digital Tag (Optional) Enter a tag name assigned to reference a digital tag that contains the status of communication attempts for this logical station. 294 / FactoryLink Device Interfaces Using EDI Technology .

multiple messages are generated for the operation. The second message reads addresses 125 through 127.MODBUS PLUS | 14 Configuring the Read/Write Control Table C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Open the Read/Write Control table. The maximum number allowed varies from one register type to the next. A read or write table should not contain more than the maximum number of contiguous registers allowed for a single message accessing a type of register. The first message reads the first 125 addresses (addresses 100 to 124). For example. If more than the maximum number of contiguous register addresses are defined. if a block read table for a holding register in a 984 device contains entries that access contiguous addresses from 100 to 127. Type of Register Maximum Number For Block Read Maximum Number For Block Write Coil Holding Global Input Status Input Mask Statistics Word Memory 2000 125 32 global data words 2000 125 800 100 32 global data words Exception write: 1 54 words 100 100 Complete a row for each read or write table. FactoryLink Device Interfaces Using EDI Technology / 295 . The following table lists the maximum number of contiguous registers included in a single block read or write message for each supported register type. two messages are generated.

For EDI to interpret this operation as an exception write and write tag values to the device only when those values change. Any tag specified will be written to the device in its own packet (message) each time it changes.• • • • 14 | MODBUS PLUS Configuring the Read/Write Control Table Table Name Assign a name to this read or write request. If a different value is being stored the tag. In an exception write. enter YES. Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. You can define as many tables as available memory allows. the change-status indicator is unaffected. Valid Entry: yes. the incoming data will be stored in the tag represented by the tag name specified in the Read/Write Information table. Defining tags that change value frequently as exception writes can slow down communications or result in an error message. Valid Entry: alphanumeric string of up to 16 characters Unsolicited Read For EDI to interpret this operation as a triggered block read or as a write operation. If the current value of the tag is equal to the new value. If this is an unsolicited read operation. enter YES. however. EDI will interpret this operation as an unsolicited read and emulate the device’s addressing structure based on entries you make in the Read/Write Information table. If a tag is configured for an exception write and EDI recognizes this 296 / FactoryLink Device Interfaces Using EDI Technology . when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). Define one request (table) per line and do not include spaces in the name. the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. If this is a triggered read or a block write table. an internal change-status indicator within the tag containing the data to be written prompts the write operation. accept the default of NO. it will overwrite the current value and the tag’s change-status indicator will be set to 1 (ON). The incoming data will be stored in the real-time database as specified in this field. no (default=no) Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. Try to make the table name reflective of the operation it represents. accept the default of NO. If you enter YES.

If this is an unsolicited read or a write operation. accept the default of 1. the addresses are read. the Block Read Trigger tag must be toggled or forced to 1. If EDI receives two requests at the same time. it processes the request with the highest priority first. Block Read Disable. relative to other read operations. The default is 1. Do not define these tags for unsolicited read operations or for write operations. Block Read Trigger If this is an unsolicited read or a write operation. Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. and Block Read State tags apply only to triggered read operations.4 (default = 1) Note The Block Read Trigger. ignore this field. Block Read Complete. This field defaults to 1 regardless of whether the operation being defined is a block read. EDI writes this tag’s value to the device. The highest priority is 1. this field is required. This number influences the order in which the EDI task handles the queuing of block read requests.MODBUS PLUS | 14 Configuring the Read/Write Control Table indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). FactoryLink Device Interfaces Using EDI Technology / 297 . Valid Entry: tag name Valid Data Type: digital Tip The Block Read Disable tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered. The triggering cycle will cease upon disabling. Valid Entry: yes. Valid Entry: 1 . See “Application Design Tips and Techniques” on page 127 for details. enter a number to indicate the priority of this table. To reenable a cascaded loop or a self-triggered read table. When this tag’s value is forced to 1 (ON). If this is a triggered read operation. no (default=no) Block Read Priority If this is a block read operation. however.

ignore this field. Valid Entry: tag name Valid Data Type: digital Block Read Complete If this is an unsolicited read or a write operation. this field is optional. When this tag’s value is forced to 1 (ON). This tag is forced to 1 (ON) at startup. This number influences the order in which the EDI task handles the queuing of write requests. Do not use this tag when more than one logical port is specified in a single table. ignore this field. The highest priority is 1. ignore this field. If you need a digital tag to disable a block read of the tags specified in this table. the read operation is not executed. even when the block read trigger is set to 1. enter a tag name. The default is 1. While the table is being processed. Valid Entry: tag name Valid Data Type: digital Block Read State If this is an unsolicited read or a write operation. this field is optional. it processes the request with the highest priority first. If this is a triggered read operation. set this tag back to 0 (OFF). the tag is set to 0 (OFF). enter a tag name. 298 / FactoryLink Device Interfaces Using EDI Technology . This tag is forced to 1 (ON) at startup. this field is optional. the state tag is forced back to 1. If EDI receives two requests at the same time. After the tags defined in the Read/Write Information table are updated in the FactoryLink database.• • • • 14 | MODBUS PLUS Configuring the Read/Write Control Table Block Read Disable If this is an unsolicited read or a write operation. If you need a digital tag to indicate the state of this operation (in progress or complete). After the tags defined in the Read/Write Information table are updated in the FactoryLink database. enter a number to indicate the priority of this table. the complete tag is forced to 1 again. To reenable a block read table that is disabled. Valid Entry: tag name Valid Data Type: digital Block Write Priority If this is a block or exception write operation. enter a tag name. If you need a digital tag to indicate when this operation is complete. relative to other write operations. If this is a triggered read operation. If this is a triggered read operation.

the Block Write Trigger tag must be toggled or forced to 1. FactoryLink Device Interfaces Using EDI Technology / 299 . If this is a block write table or an exception write table you plan to periodically disable. and Block Write State tags apply only to write operations. To reenable a cascaded loop or a self-triggered write table. See “Application Design Tips and Techniques” on page 127 for details. The triggering cycle will cease upon disabling. Valid Entry: tag name Valid Data Type: digital Tip The Block Write Disable tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. this field is required. Valid Entry: 1 . If this is a block write table or an exception write table you plan to periodically disable. ignore this field. Do not define these tags for read operations. the write operation is not executed.MODBUS PLUS | 14 Configuring the Read/Write Control Table If this is a read operation. Block Write Disable. This field defaults to 1 regardless of whether the operation being defined is a block or exception write. however. Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. even when the block write trigger is set to 1. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. ignore this field. Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. FactoryLink writes the values. this field is optional. Block Write Complete. Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. When this tag’s value is forced to 1 (ON). When this tag’s value is forced to 1 (ON). accept the default of 1.4 (default = 1) Note The Block Write Trigger.

ignore this field. This tag is forced to 1 (ON) at startup.• • • • 14 | MODBUS PLUS Configuring the Read/Write Control Table To reenable a block write table that is disabled. Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. this field is optional. Do not use this tag when more than one logical port is specified in a single table. Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. the complete tag is forced to 1 again. Do not use this tag when more than one logical port is specified in a single table. If you need a digital tag to indicate when this operation is complete. Valid Entry: tag name Valid Data Type: digital When the table is complete. 300 / FactoryLink Device Interfaces Using EDI Technology . click the Save icon to validate the information. If this is a block write operation. the tag is set to 0 (OFF). If you need a digital tag to indicate the state of this operation (in progress or complete). If this is a block write table. After the data defined in this table’s Read/Write Information table is written to the device. set this tag back to 0 (OFF). enter a tag name. enter a tag name. After the data defined in this table’s Read/Write Information table is written to the device. Valid Entry: tag name Valid Data Type: digital Block Write Complete If this is a read or exception write operation. This tag is forced to 1 (ON) at startup. ignore this field. While the table is being processed. this field is optional. the state tag is forced back to 1.

767 HREG GLBL IREG STATHI STATLO XMEMnn COIL HREG INP IREG Digital A tag that stores a binary that indicates either a set (1) or unset (0) bit FactoryLink Device Interfaces Using EDI Technology / 301 . For a Write Table – add a table entry for each tag to be written when the operation executes.MODBUS PLUS | 14 Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. select the row for the table you are configuring and open the Read/Write Information table.) Tag Type Tag Description Valid for Register Types Analog A tag that stores a signed 16-bit integer with a value range between -32.768 and +32. Valid Entry: tag name Valid Data Type: The following table lists valid tag types for each register type. For a write table. (See the Data Type field of this table for a discussion on register types. Tag Name For a read table. specify a tag name for a tag containing a value to be written to the device. specify a tag name for a tag in which FactoryLink will store the data read from the device. For a Read Table – add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes.

302 / FactoryLink Device Interfaces Using EDI Technology . For example. For a write table. Valid Entry: previously defined logical station number Reg Address For a read table. The prefix indicates the register type.• • • • 14 | MODBUS PLUS Configuring the Read/Write Information Table Tag Type Tag Description Valid for Register Types Float A tag that stores a floating point integer HREG with a value that can range up to 31 places to the right side of the decimal point A tag that stores a signed 32-bit integer HREG with a value range between + or . The leading zeros are extraneous. The format of a register address is: paaaaa where p The address prefix that identifies the Modicon register type aaaaa The actual address of the register When defining register addresses.2 billion A tag that stores ASCII text HREG Longana Message Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written. for holding register address 400001. The 4 indicates the register type. and the leading zeros are not necessary. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. enter the address in the device’s memory where the value to be stored in this tag is located. enter 1. and this information is specified in the Data Type field of this table. enter the address in the device’s memory to which the tag value will be written. do not include the address prefix or leading zeros.

6.HREG 2000 If you are defining an address for global data words. Try to maintain consistency when using register addresses for floating-point and long analog FactoryLink data types. Adopt either an odd or even starting register sequence and maintain that sequence. Examples: LSTA 1 . the second register contains the low-order word. the address specifies the first in a group of registers that contains the message characters. For example.. 5. The message length is specified in the Bit Offset/MSG Length field. . and so on. the register addresses for each logical station must be unique. or 2.MODBUS PLUS | 14 Configuring the Read/Write Information Table If you are defining an address for floating-point or long analog tag types. 5. if you specify register address 1. For example: 1. use the register address range of 1 to 32. For global data word read operations. If you are defining an address to read the high or low byte of a statistical word. an error is generated. .. and 25. If you are defining an address for a message tag type. 7. LSTA 2 . it is assumed the first global data word received is always word 1. 9. 20. 8. 4. 10. Enter the address for the starting register in a register pair. a message is generated for registers 1 through 25. the second is word 2.HREG 1000. FactoryLink Device Interfaces Using EDI Technology / 303 . the companion register is implied. keep in mind these tag types are addressed in pairs... A value of 0 is stored for those registers within the range that do not appear in the information table. you can define register addresses that do not appear contiguous on the information table. The first register in the pair contains the high-order word. Although global data is considered contiguous in block write tables. If you specify a register address in the block read table that is larger than the total number of global data words that will actually be received. 3. If you are defining the register address for an unsolicited read table. each pair addresses a single register between 1 and 54. 7.

or exception write operation may read or write multiple register addresses for the same register file. a block read. enter the same register address twice for two separate analog tags. this is the bit offset between 1 and 16 within a register word that contains the value of the tag.• • • • 14 | MODBUS PLUS Configuring the Read/Write Information Table To access the low and high bytes of a single word. This number of bytes. between 1 and 80. The purpose of this field depends on the tag type of the tag. starting from the location specified in the Address field of this table. follow Modicon’s convention for bit ordering. block write. Bit Offset/MSG Length Name column) associated with this entry is digital. When defining this offset. this is the number of bytes in the device’s memory. Define STATHI in the Data Type field for the first tag and STATLO in the Data Type field for the second tag. For digital tags that reference an address in memory from a holding register or input register (see Data Type field description). do not specify a register address. If you are reading or writing to extended memory. If the tag (entry in the Tag offset within the word that contains the value to be read or to which the tag value is to be written. Bit 1 is the most significant bit (MSB) and bit 16 is the least significant bit. you must define them in the same block read table or the values retrieved may not be synchronized. containing the message. For message tags. If you are defining a STATCLR exception write operation. enter the bit This field is required for digital data type. If you want to access the high and low bytes of a common register. 304 / FactoryLink Device Interfaces Using EDI Technology . You can only address one bit per tag entry. Accept the default of 1. where bit 1 is the most significant bit (MSB) and bit 16 is the least significant bit (LSB). If you want to create a single word value. use Math & Logic to “OR” the bytes together. MSB 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 LSB 16 For digital tags that reference mask write functions. use this field to indicate which bit between 1 and 16 will change in the register as a result of a mask write command.

This requires that the local computer with the SA85 adapter be assigned as a logical station with a physical station address of 0. FactoryLink Device Interfaces Using EDI Technology / 305 . Data Type Valid Operations COIL Block read operations read current value of the tag. the digital tag must be set to 1 (ON) and to clear a bit. it must be set to 0 (OFF). INP IREG MASK Block read operations read the ON/OFF status of discrete inputs. Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. Input is stored in a controller as bits. Block write and exception write operations are used to force the state of coils to either on or off. Block write and exception write operations are used to set the contents of a holding register.MODBUS PLUS | 14 Configuring the Read/Write Information Table is read into the message tag as raw binary data. HREG Block read operations are used to get contents of a holding register. For additional information about Modicon register types. The following table describes the register types supported by the FactoryLink Modbus protocol module. Exception write operations are used to set or clear bits within a holding register. GLBL or GL Block read operations are used to read global data. Block write operations are used to write global data. The FactoryLink Modbus Plus protocol module does not perform verification on these bytes to see if they are printable ASCII. Block read operations are used to read the binary contents of an input register. The current state of the digital tag determines the ON/OFF setting of the bit within the holding register. refer to the Modicon controller manuals. To set a bit within the holding register.

Define the data type (digital. Block write and exception write operations write to extended memory. analog. click the Save icon to validate the information. long analog.• • • • 14 | MODBUS PLUS Configuring the Read/Write Information Table Data Type Valid Operations STATHI. STATLO STATCLR XMEMnn Block read operations read the high or low bytes of a statistics word. 306 / FactoryLink Device Interfaces Using EDI Technology . or floating-point) for any tag names displayed in the Tag Definition dialog box. When the table is complete. Exception write operations clear statistics data. Block read operations read the contents of extended memory.

MODBUS PLUS | 14 Modbus Plus Cable Diagram M ODBUS P LUS C ABLE D IAGRAM This section contains a pin-out diagram for connecting an SA85 card to a 984 Modicon controller. refer to the Modicon Modbus Plus documentation. Figure 14-1 Pin-out Diagram—Connecting an SA85 Card to a Modicon Controller Continuity from Black Wires to PIN 3 Continuity from Bare Wires To PIN1 Continuity from White Wires to PIN 2 . For complete information about Modbus Plus cable diagrams. O O O O O O O O O 321 Trim Wires after checking Continuity Note: Wiring direction shown for 984-685/785 Controller FactoryLink Device Interfaces Using EDI Technology / 307 .

For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. Action: Install the required option bits in the master key. Action: Verify the path for MBHOST. bits (x) and number (y) required Cause: One or both of the option bits (where x and y are decimal values) required to run this protocol module are missing. a bad memory address switch settings.• • • • 14 | MODBUS PLUS Run-Time Application Messages R UN -TIME A PPLICATION M ESSAGES During EDI runtime. It is placed in the wrong slot in an EISA chassis.SYS is correct.SYS file. see “Messages and Codes” on page 147. FactoryLink generates and displays messages for the Modbus Plus protocol module on the Run-Time Manager screen and. if so configured. make the correction and restart the program. Modbus Plus: SA85 Adapter (x) identified as node (y) Cause: For Windows. For information about configuring a message tag. the SA85 card is incorrectly installed. Action: None 308 / FactoryLink Device Interfaces Using EDI Technology . the Windows SA85 Modbus Plus loaded successfully and the adapter (where x is a decimal value) shown is at the Modbus Plus address node number (where y is a decimal value). see “Configuring the Logical Station Information Table” on page 293. see “Configuring the Logical Station Control Table” on page 292. Modbus Plus: SA85 Adapter (n) not found Cause: For Windows. The following messages occur at startup: Modbus Plus: Software Protection bit failure. and check its parameters in the CONFIG. or a bad software interrupt setting. writes them to message or analog tags. If either is incorrect. For information about configuring an analog tag.

Action: Refer to the NetBIOS Error Return Codes in the Modicon documentation for details. Modbus Plus: Lsta n: Write Request Error. FactoryLink Device Interfaces Using EDI Technology / 309 . Action: Refer to the NetBIOS Error Return Codes in the Modicon documentation for details. a hexadecimal value. Modbus Plus: Lsta n: Write Response Error.MODBUS PLUS | 14 Run-Time Application Messages Logical Port Messages The EDI task writes logical port messages to the LPORT tag when this tag is defined on the Read/Write table. Modbus Plus: Communications OK Cause: Normal. Action: None. This error occurred on a READ table operation to a specific logical station. This error occurred on a WRITE table operation to a specific logical station. 0xnn Cause: A response to a WRITE operation was made to logical station (n) resulting in an error with a NetBIOS return code of 0xnn. 0xnn Cause: A READ operation request was made to logical station n resulting in a NetBIOS return code of 0xnn. 0xnn Cause: A command for a WRITE operation was made to logical station (n) resulting in a NetBIOS return code of 0xnn. Modbus Plus: Lsta n: Read Request Error. a hexadecimal value. These messages occur after the application starts up. Action: Refer to the NetBIOS Error Return Codes in the Modicon documentation for details. a hexadecimal value. This error occurred on a WRITE table operation to a specific logical station.

resulted from the send of a Modbus command. Action: Decrease the rate at which unsolicited data is sent to FactoryLink. Lsta: n Netbios Transmit Error 0xnn Cause: A NetBIOS error 0xnn. a hexadecimal value. Action: Refer to the NetBIOS Error Return Codes in the Modicon documentation for details.• • • • 14 | MODBUS PLUS Run-Time Application Messages Modbus Plus: Lsta n: Read Response Error. or be certain the PLC is attempting to send only function code 0x10 for unsolicited messages. Logical Station Messages The EDI task writes logical station messages to the LSTA tag when this tag is defined on the Read/Write table. 0xnn Cause: A response to a READ operation request was made to logical station n resulting in a NetBIOS return code of 0xnn. These messages occur after the application starts up. Action: Refer to the NetBIOS Error Return Codes in the Modicon documentation for details. a hexadecimal value. 310 / FactoryLink Device Interfaces Using EDI Technology . Lsta: n Communications OK Cause: Normal. Action: None. Modbus Plus: Illegal func code 0xnn rcvd for unsol data Cause: An illegal command function code was detected in an unsolicited message. Modbus Plus only expects the Preset Multiple Regs command—Modbus command function 0x10—as the only valid command for unsolicited operations.

Action: Either adjust the number of global data words broadcast by the controller. Action: Refer to the NetBIOS Error Return Codes in the Modicon documentation for details. or adjust the number of tags defined in the block READ table for global data. resulted from the request for a Modbus response to a previously sent Modbus command request. Lsta: n Insufficient number of global data words rcvd Cause: The number of words returned was less than expected during a read of global data. a no response to an interface table or communication difficulties with a slave. Lsta: n Incurred a Time-out Error Cause: All retries are exhausted in the attempt to get a response from logical station n. A controller encountered a programming or operation error while attempting to carry out a Modbus command request. off line. FactoryLink Device Interfaces Using EDI Technology / 311 . this error flags an illegal data reference in a message or controller problems. Action: Check on status of logical station n: Is it powered off. a hexadecimal value.MODBUS PLUS | 14 Run-Time Application Messages Lsta: n Netbios Receive Error 0xnn Cause: A NetBIOS error 0xnn. a hexadecimal value. The number expected is always equal to or greater than the largest register address specified in the READ table for global data. Action: Refer to the NetBIOS Error Return Codes in the Modicon documentation for details. was received from logical station n. or have a faulty cable connection? Lsta: n Exception Response Error x Cause: An exception response 0xnn. Typically.

• • • • 14 | MODBUS PLUS Run-Time Application Messages 312 / FactoryLink Device Interfaces Using EDI Technology .

Refer to the device manufacturer’s documentation for details. Note Before completing the protocol-specific Modbus Serial configuration tables. In your server application. to represent a particular communication path to a Modicon Modbus device. you must complete the External Device Definition table. See “Identifying Protocol Types and Defining Logical Ports” on page 58 for details. Logical Port Enter a number. or odd (default=odd) • FactoryLink Device Interfaces Using EDI Technology / 313 . This entry must match the configuration of the devices communicating via this port.115200 (default=9600) Parity Enter the parity error correction during transmission via this logical port. defined in the External Device Definition table Logical Port column. Refer to the device manufacturer’s documentation for details. open Device Interfaces > Modicon Modbus. This entry must match the baud rate configuration of the devices. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. Valid Entry: 110 . Valid Entry: previously defined logical port number Baud Rate Enter the speed at which the protocol module communicates with the devices linked to FactoryLink via this logical port. Valid Entry: none. even.Chapter 15 • • • Modbus Serial This chapter contains information needed to set up and configure bidirectional communications between the FactoryLink real-time database and any Modbus Serial PLC. C ONFIGURING THE L OGICAL S TATION C ONTROL TABLE Open the Logical Station Control table.

in tenths of a second. You must enter a value greater than 0 for the protocol module to timeout. 2 (default=1) Timeout Enter the length of time.• • • • 15 | MODBUS SERIAL Configuring the Logical Station Control Table Data Bits Enter the number of data bits used during transmission via this logical port. Valid Entry: 7. Valid Entry: 1 . Valid Entry: RTU. the protocol module will wait to receive a response to a read or write command before timing out. Refer to the device manufacturer’s documentation for details. 314 / FactoryLink Device Interfaces Using EDI Technology . This entry must match the configuration of the devices communicating via this port. 8 (default=8) Stop Bits Enter the number of bits sent after a character to create a pause before the start of the next character. ASCII (default=RTU) Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. This entry must match the configuration of the devices communicating via this port.32000 (default=30) RTU ASCII Message Tag Enter the communication mode for this logical port. Refer to the device manufacturer’s documentation for details. click the Save icon to validate the information. Define the data type (message) for any tag names displayed in the Tag Definition dialog box. Valid Entry: 1. Valid Entry: tag name Valid Data Type: message When the table is complete.

The following table lists the valid entries and their variations. You can animate output-text objects to display the codes stored in an Error/Status Tag Name tag on a graphics screen. Valid Entry: tag name Valid Data Type: analog Logical Station Enter a number to identify the logical station to which the information in this row pertains. 8. select the row for the logical port you are configuring and open the Logical Station Information table. or 48 584. Complete a row for each device to communicate through this logical port. A logical station represents the combination of a logical port with a physical station. 3. 9. You can specify any of the valid entry variations in this field. 5. or 38 484. 1. or 88 984.MODBUS SERIAL | 15 Configuring the Logical Station Information Table C ONFIGURING THE L OGICAL STATION I NFORMATION TABLE From the Logical Station Control table. Valid Entry Variation 184 384 484 584 884 984 184. or 98 FactoryLink Device Interfaces Using EDI Technology / 315 . or 58 884. Valid Entry: 0 . or 18 384. You will later enter this logical station number in a read or write table to represent the device defined in this row. Assign a unique number to each device communicating through this logical port. In a read or write table. this number will identify the device to or from which data is to be sent or received. 4.999 Device Type Enter the type of Modicon device represented by this entry. Error/Status Tag Name (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station).

or M8 M84 (Micro84) Station Address Enter the physical address of the Modicon device represented by this entry. A read or write table should not contain more than the maximum number of contiguous registers allowed for a single message accessing a type of register. Valid Entry: 1 . C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Open the Read/Write Control Table. Valid Entry: 1 .31 When the table is complete. The maximum number allowed varies from one register type to the next. The second message reads addresses 125 through 127. If more than the maximum number of contiguous register addresses are defined. The following table lists the maximum number of contiguous registers included in a single block read or write message for each supported register type. two messages are generated.24 (default=1) Comment (Optional) Enter reference information about this logical station. The first message reads the first 125 addresses (addresses 100 to 124). 316 / FactoryLink Device Interfaces Using EDI Technology . if a block read table for a holding register contains entries that access contiguous addresses from 100 to 127. click the Save icon to validate the information. For example.• • • • 15 | MODBUS SERIAL Configuring the Read/Write Control Table Valid Entry Variation 984BITWRITE (Used for mask writes) 984-BW M84. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box. multiple messages are generated for the operation. M.

MODBUS SERIAL | 15 Configuring the Read/Write Control Table Type of Register Modicon Model Number Maximum Number Maximum Number For Block Read For Block Write Coil Holding Input Status Input 184. 884. 884. Try to make the table name reflective of the operation it represents. 984 M84 184. 384 484 584. You can define as many tables as available memory allows. Valid Entry: alphanumeric string of up to 16 characters FactoryLink Device Interfaces Using EDI Technology / 317 . 984 M84 Memory 800 512 2000 64 100 254 125 32 800 512 2000 64 100 32 125 4 100 800 800 800 64 100 60 100 32 100 Complete a row for each read or write table. 384 484 584. 884. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). 384 484 584. Define one request (table) per line and do not include spaces in the name. the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. If this is a triggered read or a block write table. 984 M84 184. 984 M84 184. 884. 384 484 584. Table Name Assign a name to this read or write request.

relative to other read operations. In an exception write. Block Read Complete. This field defaults to 1 regardless of whether the operation being defined is a block read. If EDI receives two requests at the same time. Block Read Priority If this is a block read operation. an internal change-status indicator within the tag containing the data to be written prompts the write operation. Valid Entry: 1 . Defining tags that change value frequently as exception writes can slow down communications or result in an error message. This number influences the order in which the EDI task handles the queuing of block read requests. and Block Read State tags apply only to triggered read operations. The highest priority is 1. it processes the request with the highest priority first. Do not define these tags 318 / FactoryLink Device Interfaces Using EDI Technology . Block Read Disable. If this is a write operation.4 (default=1) Note for write operations. EDI writes this tag’s value to the device. For EDI to interpret this operation as an exception write and write tag values to the device only when those values change. accept the default of NO. Any tag specified will be written to the device in its own packet (message) each time it changes. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). The Block Read Trigger. The default is 1.• • • • 15 | MODBUS SERIAL Configuring the Read/Write Control Table Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. Tip Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. accept the default of 1. enter YES. enter a number to indicate the priority of this table.

The triggering cycle will cease upon disabling. Do not use this tag when more than one logical port is specified in a single table. enter a tag name. ignore this field. this field is optional. When this tag’s value is forced to 1 (ON). Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. See “Application Design Tips and Techniques” on page 127 for further details. If you need a digital tag to disable a block read of the tags specified in this table. If you need a digital tag to indicate when this operation is complete. Valid Entry: tag name Valid Data Type: digital Block Read Complete If this is a write operation. ignore this field. however. If this is a triggered read operation. Tip This tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered. the addresses are read.MODBUS SERIAL | 15 Configuring the Read/Write Control Table Block Read Trigger If this is a write operation. If this is a triggered read operation. the read operation is not executed. Valid Entry: tag name Valid Data Type: digital Block Read Disable If this is a write operation. If this is a triggered read operation. set this tag back to 0 (OFF). Valid Entry: tag name Valid Data Type: digital FactoryLink Device Interfaces Using EDI Technology / 319 . This tag is forced to 1 (ON) at startup. even when the block read trigger is set to 1. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. the complete tag is forced to 1 again. To reenable a block read table that is disabled. ignore this field. To reenable a cascaded loop or a self-triggered read table. When this tag’s value is forced to 1 (ON). this field is optional. enter a tag name. this field is required. the Block Read Trigger tag must be toggled or forced to 1.

Valid Entry: 1 .4 (default=1) Note The Block Write Trigger. accept the default of 1. This tag is forced to 1 (ON) at startup. enter a tag name. The highest priority is 1. and Block Write State tags apply only to write operations. this field is optional. If you need a digital tag to indicate the state of this operation (in progress or complete). ignore this field. it processes the request with the highest priority first.• • • • 15 | MODBUS SERIAL Configuring the Read/Write Control Table Block Read State If this is a write operation. FactoryLink writes the values. Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. If EDI receives two requests at the same time. If this is a block write table or an exception write table you plan to periodically disable. ignore this field. Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. this field is required. relative to other write operations. Block Write Disable. The default is 1. This number influences the order in which the EDI task handles the queuing of write requests. Valid Entry: tag name Valid Data Type: digital 320 / FactoryLink Device Interfaces Using EDI Technology . the tag is set to 0 (OFF). Do not define these tags for read operations. If this is a triggered read operation. This field defaults to 1 regardless of whether the operation being defined is a block or exception write. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. Block Write Complete. While the table is being processed. When this tag’s value is forced to 1 (ON). the state tag is forced back to 1. enter a number to indicate the priority of this table. Valid Entry: tag name Valid Data Type: digital Block Write Priority If this is a block or exception write operation. If this is a read operation.

To reenable a cascaded loop or a self-triggered write table. set this tag back to 0 (OFF). After the data defined in this table’s Read/Write Information table is written to the device. ignore this field. this field is optional. This tag is forced to 1 (ON) at startup. ignore this field. This tag is forced to 1 (ON) at startup. the write operation is not executed. this field is optional. the complete tag is forced to 1 again. Do not use this tag when more than one logical port is specified in a single table. even when the block write trigger is set to 1. If you need a digital tag to indicate the state of this operation (in progress or complete). FactoryLink Device Interfaces Using EDI Technology / 321 . The triggering cycle will cease upon disabling. the Block Write Trigger tag must be toggled or forced to 1. To reenable a block write table that is disabled. See “Application Design Tips and Techniques” on page 127 for details. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. this field is optional.MODBUS SERIAL | 15 Configuring the Read/Write Control Table Tip The Block Write Disable tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. enter a tag name. however. If this is a block write operation. If this is a block write table or an exception write table you plan to periodically disable. When this tag’s value is forced to 1 (ON). ignore this field. If you need a digital tag to indicate when this operation is complete. Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. Valid Entry: tag name Valid Data Type: digital Block Write Complete If this is a read or exception write operation. If this is a block write operation. Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. enter a tag name.

After the data defined in this table’s Read/Write Information table is written to the device. Do not use this tag when more than one logical port is specified in a single table. Valid Entry: tag name Valid Data Type: digital When the table is complete. the tag is set to 0 (OFF).• • • • 15 | MODBUS SERIAL Configuring the Read/Write Control Table While the table is being processed. Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. the state tag is forced back to 1. 322 / FactoryLink Device Interfaces Using EDI Technology . click the Save icon to validate the information.

768 and +32. For a Write Table – add a table entry for each tag to be written when the operation executes. Tag Name For a read table. Tag Type Tag Description Valid for Register Types: Analog A tag that stores a signed 16-bit integer with a value range between -32.MODBUS SERIAL | 15 Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. specify a tag name for a tag containing a value to be written to the device.2 billion A tag that stores ASCII text Longana HREG Message HREG FactoryLink Device Interfaces Using EDI Technology / 323 . For a Read Table – add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes. specify a tag name for a tag in which FactoryLink will store the data read from the device.767 A tag that stores a binary that indicates either a set (1) or unset (0) bit HREG IREG XMEMnn COIL HREG INP IREG HREG Digital Float A tag that stores a floating-point integer with a value that can range up to 31 places to the right side of the decimal point A tag that stores a signed 32-bit integer with a value range between + or . select the row for the table you are configuring and open the Read/Write Information table. For a write table.

do not include the address prefix or leading zeros. 7. 8.. 324 / FactoryLink Device Interfaces Using EDI Technology . for holding register address 400001. 9. 6. keep in mind that these tag types are addressed in pairs. Try to maintain consistency when using register addresses for floating-point and long analog FactoryLink data types. The prefix indicates the register type. Valid Entry: previously defined logical station number Reg Address Enter the register address in Modicon memory where this tag’s value is located. .. The format of a register address is: paaaaa where p Address prefix that identifies the Modicon register type aaaaa Actual address of the register When defining register addresses.. the companion register is implied. 10. or 2. If you are defining an address for floating-point or long analog tag types. 4. enter 1. 3. Adopt either an odd or even starting register sequence and maintain that sequence. For example. For example: 1. . The first register in the pair contains the high-order word.• • • • 15 | MODBUS SERIAL Configuring the Read/Write Information Table Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written. the second register contains the low-order word. The leading zeros are extraneous. Enter the address for the starting register in a register pair. and this information is specified in the Data Type field of this table.. 5. and the leading zeros are not necessary. The 4 indicates the register type. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs.

this is the number of bytes in the device’s memory. block write. Bit 1 is the most significant bit (MSB) and bit 16 is the least significant bit. Leave this field blank for all other FactoryLink data types. For digital tags that reference an address in memory from a holding register or input register (see Data Type field description).16 if data type is digital FactoryLink Device Interfaces Using EDI Technology / 325 . a block read. containing the message. For message tags. enter the bit This field is required for digital data type. is read into the message tag as raw binary data. follow Modicon’s convention for bit ordering. Valid Entry: 1 . You can only address one bit per tag entry. If the tag (entry in the Tag offset within the word that contains the value to be read or to which the tag value is to be written. the address specifies the first in a group of registers that contain the message characters. Bit Offset/MSG Length Name column) associated with this entry is digital. The message length is specified in the Bit Offset/MSG Length field. If you are reading or writing to extended memory. When defining this offset. this is the bit offset between 1 and 16 within a register word that contains the value of the tag. starting from the location specified in the Address field of this table.MODBUS SERIAL | 15 Configuring the Read/Write Information Table If you are defining an address for a message tag type. between 1 and 80. The FactoryLink Modbus Plus protocol module does not perform verification on these bytes to see if they are printable ASCII. or exception write operation may read or write multiple register addresses for the same register file. where bit 1 is the most significant bit (MSB) and bit 16 is the least significant bit (LSB). use this field to indicate which bit between 1 and 16 will change in the register as a result of a mask write command. MSB 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 LSB 16 For digital tags that reference mask write functions. This number of bytes.

INP Block read operations read the ON/OFF status of discrete inputs. IREG MASK XMEMnn When the table is complete. it must be set to 0 (OFF). Each bit has an address. Block write and exception write operations are used to force the state of coils to either on or off. Valid Operations Data Type COIL Block read operations read current value of the tag. Block read operations are used to read the binary contents of an input register. Input is stored in a controller as bits. Block write and exception write operations are used to set the contents of a holding register. The current state of the digital tag determines the ON/OFF setting of the bit within the holding register. Block read operations read the contents of extended memory. Block write and exception write operations write to extended memory. 326 / FactoryLink Device Interfaces Using EDI Technology . HREG Block read operations are used to get the contents of a holding register. analog.• • • • 15 | MODBUS SERIAL Configuring the Read/Write Information Table Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. Define the data type (digital. long analog. click the Save icon to validate the information. the digital tag must be set to 1(ON) and to clear a bit. or floating-point) for any tag names displayed in the Tag Definition dialog box. To set a bit within the holding register. Exception write operations are used to set or clear bits within a holding register.

FactoryLink generates and displays messages for the General Electric protocol module on the Run-Time Manager screen and. 2 (Decimal equivalent: 2) Cause: I/O error in transmitting or receiving data. The FactoryLink configuration tables must contain the proper station addresses and parameters. the second number is the decimal equivalent. For information about the messages displayed for the EDI task. see Chapter 11. Action: Verify the device configuration and cabling. parity. and data format parameters. 1 (Decimal equivalent: 1) Cause: Unknown I/O state. The Logical Station Control table must contain the proper baud rate. if so configured. see “Configuring the Logical Station Control Table” on page 313. Run-Time Manager Codes The following error codes can appear in messages displayed on the Run-Time Manager screen. writes them to message or analog tags. “Messages and Codes”. Action: See the description of code 1. The first number refers to the hexadecimal code. Action: See the description of code 1. For information about configuring a message tag.MODBUS SERIAL | 15 Run-Time Application Messages R UN -T IME A PPLICATION M ESSAGES During EDI run time. FactoryLink Device Interfaces Using EDI Technology / 327 . see “Configuring the Logical Station Information Table” on page 315. For information about configuring an analog tag. 3 (Decimal equivalent: 3) Cause: I/O aborted because of a time-out while the protocol module is waiting for a device response.

verify each tag value is valid for the specified data type. 25 (Decimal equivalent: 37) Cause: Exception response – the data address received in the query by the device is not valid. 35 (Decimal equivalent: 53) Cause: Exception response – an invalid data value in the query is detected by the device.• • • • 15 | MODBUS SERIAL Run-Time Application Messages 4 (Decimal equivalent: 4) Cause: I/O data translation error. Action: Depending on the data type of the table in error. 45 (Decimal equivalent: 69) Cause: Exception response – the device has experienced an unrecoverable error while executing a requested action. Action: Determine whether the device is in proper working order. Action: Check the read and write tables and verify the data types are valid for the destination device. it can result in time-consuming processing of requests. Action: Verify the register addresses in the table experiencing the error. Action: See the description of code 1. 15 (Decimal equivalent: 21) Cause: Exception response – the slave cannot respond to the function code given in the query. 55 (Decimal equivalent: 85) Cause: Exception response – the device requires a long time to carry out the requested action. It might require servicing. Action: If the ladder logic programmed into the device is inefficient. 328 / FactoryLink Device Interfaces Using EDI Technology . Reprogram the device according to the manufacturer’s recommendations.

Lessen the frequency of requests sent to the device. FactoryLink Device Interfaces Using EDI Technology / 329 . Action: The device needs more time to finish processing the current request before it begins processing the next one. Action: Determine whether the device is in proper working order. 85 (Decimal equivalent: 113) Cause: Exception response – the device attempted to read extended memory but detected a memory parity error. Action: None. Action: The specified error is the decimal equivalent of a hexadecimal error code. Modbus: Communications OK Cause: Normal. For details. see “Run-Time Manager Codes” on page 327. Action: Use the Modicon diagnostic software to determine the cause of the problem. It might require servicing. This is only an information message. Modbus: Exception error decimalcode on write to Lsta logical station Cause: An error occurred on a write request to the specified logical station.MODBUS SERIAL | 15 Run-Time Application Messages 65 (Decimal equivalent: 101) Cause: Exception response – the device is busy carrying out a previously requested action. In Message Tags This section describes the run-time messages as they appear in the message tags. 75 (Decimal equivalent: 117) Cause: Exception response – the device cannot perform the program function received in the query.

Modbus: Read error decimalcode to Lsta logical station Cause: An error occurred on a read request to the specified logical station. For details. For details.• • • • 15 | MODBUS SERIAL Run-Time Application Messages Modbus: Exception error decimalcode on read to Lsta logical station Cause: An error occurred on a read request to the specified logical station. see “Run-Time Manager Codes” on page 327. see “Run-Time Manager Codes” on page 327. Action: The specified error is the decimal equivalent of a hexadecimal error code. Action: The specified error is the decimal equivalent of a hexadecimal error code. 330 / FactoryLink Device Interfaces Using EDI Technology . Modbus: Write error decimalcode to Lsta logical station Cause: An error occurred on a write request to the specified logical station. see “Run-Time Manager Codes” on page 327. For details. Action: The specified error is the decimal equivalent of a hexadecimal error code.

See “Identifying Protocol Types and Defining Logical Ports” on page 58 for details. Valid Entry: previously defined logical port number (default=0) • FactoryLink Device Interfaces Using EDI Technology / 331 . Logical Port Enter a number.Chapter 16 • • • OMRON Host Link This chapter contains information needed to set up and configure bidirectional communications between the FactoryLink real-time database and the following devices. C ONFIGURING Note THE L OGICAL S TATION C ONTROL TABLE Before completing the protocol-specific General Electric configuration tables. defined in the External Device Definition table Logical Port column. either directly or using the OMRON Host Link: • C120 • C200H • C500 • C1000 • C2000 In your server application. Open the Logical Station Control table. to represent a particular communication path to a device. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. you must complete the External Device Definition table. open Device Interfaces > OMRON.

Specifies the communication rate.115200 (default=9600) Parity Enter the parity error correction during transmission via this logical port. Refer to the device manufacturers documentation for details. The following table provides sample entries for the OMRON Logical Station Control table: Field Logical Port Entry Description 0 Baud Rate 9600 Specifies the logical communication path configured by this table. This entry must match the baud rate configuration of the devices. Valid Entry: 1 Timeout Enter the length of time the protocol module will wait to receive a response to a read or write command before timing out. Define the data type (message) for any tag names displayed in the Tag Definition dialog box. This entry must match the configuration of the devices communicating via this port. Refer to the device manufacturer’s documentation for details. Valid Entry: 110 . Refer to the device manufacturers documentation for details. Valid Entry: odd Data Bits Enter the number of data bits used during transmission via this logical port.• • • • 16 | OMRON HOST LINK Configuring the Logical Station Control Table Baud Rate Enter the speed at which the protocol module communicates with the devices linked to FactoryLink via this logical port. This entry must match the configuration of the devices communicating via this port. 332 / FactoryLink Device Interfaces Using EDI Technology . Valid Entry: 1 . Refer to the device manufacturers documentation for details. This entry must match the configuration of the devices communicating via this port.32767 (default=10) When the table is complete. click the Save icon to validate the information. Valid Entry: 8 Stop Bits Enter the number of bits sent after a character to create a pause before the start of the next character. You must enter a value greater than 0 for the protocol module to timeout.

A logical station represents the combination of a logical port with a physical station. Valid Entry: 0 . Valid Entry: tag name Valid Data Type: analog Logical Station Enter a number to identify the logical station to which the information in this row pertains. C20 C120 PLC FactoryLink Device Interfaces Using EDI Technology / 333 . You will later enter this logical station number in a read or write table to represent the device defined in this row. this number will identify the device to or from which data is to be sent or received. You can animate output text objects to display the codes stored in an Error/Status Tag Name tag on a graphics screen.OMRON HOST LINK | 16 Configuring the Logical Station Information Table Field Parity Data Bits Stop Bits Response Timeout (0.999 Device Type Enter the type of OMRON device to which communications are to be directed. The response timeout is 1 second. Complete a row for each device to communicate through this logical port. select the row for the logical port you are configuring and open the Logical Station Information table. C ONFIGURING THE L OGICAL STATION I NFORMATION TABLE From the Logical Station Control table. Specifies 1 stop bit in the transmission.1 Sec) Entry Description EVEN 8 1 10 No parity checking. Assign a unique number to each device communicating through this logical port. Error/Status Tag Name (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station). In a read or write table. Specifies 8 data bits in the transmission.

Valid Entry: alphanumeric string of up to 21 characters When the table is complete. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box. C60K. C20P. C40K. C28P. C40P.31 Comment (Optional) Enter reference information about this logical station.• • • • 16 | OMRON HOST LINK Configuring the Logical Station Information Table K/P-SR K & P-Series PLCs (C20K. The following table provides sample entries for the OMRON Logical Station Information table: Field Error/Status Tag Name Logical Station Physical Station Entry Description OMRN_STATION0_ STATUS 0 0 Contains information about communication errors Specifies the logical communication path Specifies the physical station address associated with this logical station Specifies the external device type associated with this logical station Device Type C200H 334 / FactoryLink Device Interfaces Using EDI Technology . C28K. Valid Entry: 0 . click the Save icon to validate the information. C60P) C120 C120 & C120F PLCs C200H C200H PLC (default) C500 C500 PLC C500F C500F PLC C1000H C1000H PLC C2000H C2000H PLC Physical Station Enter the physical station address of the OMRON device with which the EDI task communicates when using this logical station in a Read/Write table.

You can define as many tables as available memory allows. Table Name Assign a name to this read or write request. enter YES. Valid Entry: alphanumeric string of up to 16 characters Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. an internal change-status indicator within the tag containing the data to be written prompts the write operation. Define one request (table) per line and do not include spaces in the name. In an exception write. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). If this is a triggered read or a block write table. Complete a row for each read or write table. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). FactoryLink Device Interfaces Using EDI Technology / 335 . accept the default of NO. the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. Tip See “Application Design Tips and Techniques” on page 127 for information about triggering schemes using tags defined in this table. EDI writes this tag’s value to the device.OMRON HOST LINK | 16 Configuring the Read/Write Control Table C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Open the Read/Write Control table. Try to make the table name reflective of the operation it represents. For EDI to interpret this operation as an exception write and write tag values to the device only when those values change.

this field is required. Block Read Disable. The highest priority is 1. it processes the request with the highest priority first. Block Read Complete. When this tag’s value is forced to 1 (ON). This number influences the order in which the EDI task handles the queuing of block read requests. relative to other read operations. Do not define these tags If this is a write operation. If this is a triggered read operation. Valid Entry: 1 . Block Read Priority If this is a block read operation. and Block Read State tags apply only to triggered read operations.• • • • 16 | OMRON HOST LINK Configuring the Read/Write Control Table Tip Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. Block Read Trigger The Block Read Trigger. If this is a write operation. ignore this field. The default is 1. If EDI receives two requests at the same time. accept the default of 1. Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. enter a number to indicate the priority of this table. Any tag specified will be written to the device in its own packet (message) each time it changes. Defining tags that change value frequently as exception writes can slow down communications or result in an error message. the addresses are read. Valid Entry: tag name Valid Data Type: digital 336 / FactoryLink Device Interfaces Using EDI Technology . This field defaults to 1 regardless of whether the operation being defined is a block read.4 (default=1) Note for write operations.

If this is a triggered read operation. enter a tag name. this field is optional. If this is a triggered read operation. If you need a digital tag to indicate when this operation is complete. even when the block read trigger is set to 1. While the table is being processed. This tag is forced to 1 (ON) at startup. the complete tag is forced to 1 again. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. enter a tag name. FactoryLink Device Interfaces Using EDI Technology / 337 . enter a tag name. To reenable a cascaded loop or a self-triggered read table. the state tag is forced back to 1. however. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. the read operation is not executed. When this tag’s value is forced to 1 (ON). This tag is forced to 1 (ON) at startup. ignore this field. If you need a digital tag to disable a block read of the tags specified in this table. ignore this field. Valid Entry: tag name Valid Data Type: digital Tip This tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered.OMRON HOST LINK | 16 Configuring the Read/Write Control Table Block Read Disable If this is a write operation. this field is optional. Do not use this tag when more than one logical port is specified in a single table. See “Application Design Tips and Techniques” on page 127 for further details. To reenable a block read table that is disabled. Block Read Complete If this is a write operation. If you need a digital tag to indicate the state of this operation (in progress or complete). this field is optional. If this is a triggered read operation. ignore this field. The triggering cycle will cease upon disabling. Valid Entry: tag name Valid Data Type: digital Block Read State If this is a write operation. set this tag back to 0 (OFF). the tag is set to 0 (OFF). the Block Read Trigger tag must be toggled or forced to 1.

accept the default of 1.• • • • 16 | OMRON HOST LINK Configuring the Read/Write Control Table Valid Entry: tag name Valid Data Type: digital Block Write Priority If this is a block or exception write operation. Block Write Complete. and Block Write State tags apply only to write operations. The default is 1. enter a number to indicate the priority of this table. When this tag’s value is forced to 1 (ON).4 (default=1) Note The Block Write Trigger. FactoryLink writes the values. Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. If this is a read operation. ignore this field. ignore this field. relative to other write operations. this field is required. The highest priority is 1. If EDI receives two requests at the same time. This field defaults to 1 regardless of whether the operation being defined is a block or exception write. Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. This number influences the order in which the EDI task handles the queuing of write requests. If this is a block write table or an exception write table you plan to periodically disable. Block Write Disable. 338 / FactoryLink Device Interfaces Using EDI Technology . Valid Entry: 1 . Valid Entry: tag name Valid Data Type: digital Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. Do not define these tags for read operations. it processes the request with the highest priority first.

After the data defined in this table’s Read/Write Information table is written to the device. this field is optional. enter a tag name. Block Write Complete If this is a read or exception write operation. the Block Write Trigger tag must be toggled or forced to 1. The triggering cycle will cease upon disabling. the write operation is not executed. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. This tag is forced to 1 (ON) at startup. the complete tag is forced to 1 again. If this is a block write table. enter a tag name. This tag is forced to 1 (ON) at startup. While the table is being processed. set this tag back to 0 (OFF). ignore this field. To reenable a cascaded loop or a self-triggered write table. this field is optional. however. the state tag is forced back to 1.OMRON HOST LINK | 16 Configuring the Read/Write Control Table If this is a block write table or an exception write table you plan to periodically disable. Do not use this tag when more than one logical port is specified in a single table. FactoryLink Device Interfaces Using EDI Technology / 339 . To reenable a block write table that is disabled. See “Application Design Tips and Techniques” on page 127 for further details. Valid Entry: tag name Valid Data Type: digital Tip This tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. After the data defined in this table’s Read/Write Information table is written to the device. If this is a block write operation. When this tag’s value is forced to 1 (ON). the tag is set to 0 (OFF). Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. If you need a digital tag to indicate when this operation is complete. If you need a digital tag to indicate the state of this operation (in progress or complete). ignore this field. even when the block write trigger is set to 1. this field is optional.

The write priority for this table is set to 1 by default. Field Table Name Exception Write Block Read Priority Block Read Trigger Entry Description READ NO 1 OMRN_READ_ TRIGGER OMRN_READ_ DISABLE Block Read Complete OMRN_READ_ COMPLETE Block Read Disable Block Read State OMRN_READ_ STATE Block Write Priority Block Write Trigger Block Write Complete Block Write Disable Block Write State 1 Specifies the table name. The block read priority for the table will be 1. The following table provides sample entries for the OMRON Read/Write Control table. When the value of OMRN_ READ_TRIGGER is 1 or (on). Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. The value of OMRN_READ_ COMPLETE is set to 1 when the read is complete. Valid Entry: tag name Valid Data Type: digital When the table is complete. This tag is defined to disable the block read operations. The table will not perform exception writes. Since this is a read table. click the Save icon to validate the information. the tags specific to write requests are not defined. 340 / FactoryLink Device Interfaces Using EDI Technology . and the value is 0 if it is inactive. The value for OMRN_READ_ STATE is set to 1 if a read operation of table 1 is in progress. a block read of values specified by the Read/Write Information table associated with table 1 occurs.• • • • 16 | OMRON HOST LINK Configuring the Read/Write Control Table Do not use this tag when more than one logical port is specified in a single table.

Valid Entry: tag name Valid Data Type: digital. respectively. For a Write Table – add a table entry for each tag to be written when the operation executes. For a write table. ER PLC errors. specify a tag name for a tag in which FactoryLink will store the data read from the device. specify a tag name for a tag containing a value to be written to the device. Valid Entry: previously defined logical station number Data Area Enter the data area of the OMRON controller to be read/written. Use tag type A and data type BIN1. analog. Use data type BIN1. channel number is ignored.OMRON HOST LINK | 16 Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. FactoryLink Device Interfaces Using EDI Technology / 341 . See “OMRON Data Types and PLC Data Areas” on page 345 for more information about these data areas. ST PLC operating status. Use tag type D and data type TCTR. select the row for the table you are configuring and open the Read/Write Information table. float Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written. Tag Name For a read table. Link relay area. channel number must be 0 or 1 for error word 1 or 2. Auxiliary relay area. IR HR AR LR TC I/O and internal relay area. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. Holding relay area. For a Read Table – add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes. Timer/counter area.

Present value area. Use tag type A or F and data type BCD1. Valid Entry: 0 .1 second (0. 342 / FactoryLink Device Interfaces Using EDI Technology . Bit 1 is the most significant bit (MSB) and bit 16 is the least significant bit. 16-bit high-speed timer BCD value with units of 0.• • • • 16 | OMRON HOST LINK Configuring the Read/Write Information Table DM PV Channel Data memory area. One-bit timer/counter value (0 or 1). Leave this field blank for all other FactoryLink data types. Use tag type F. 15 (most significant bit) Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. or floating-point) for any tag names displayed in the Tag Definition dialog box.0 to 999. Two consecutive 16-bit BCD values or 32-bit BCD value (0 to 9999999). TIM.9).9999 Bit Offset Name column) associated with this entry is digital. enter the bit This field is required for digital data type. Use tag type F. analog. Use tag type D or A. click the Save icon to validate the information.00 to 99. Use tag type F.01 second (0. Use tag type D and data area TC. 16-bit BCD value (0 to 9999). BCD2. Define the data type (digital. Valid Entry: 0 (least significant bit). Two consecutive 16-bit binary values or 32-bit binary value (0 to 4294967295). When the table is complete. Use tag type F. 16-bit timer BCD value with units of 0. Enter the channel number within the data area of the value to be read or written. or TIMH. BIN1 BIN2 BCD1 BCD2 TIM TIMH TCTR 16-bit binary value (-32768 to 32767). Use tag type A. If the tag (entry in the Tag offset within the word that contains the value to be read or to which the tag value is to be written.99). See “OMRON Data Types and PLC Data Areas” on page 345 for valid data types.

FactoryLink Device Interfaces Using EDI Technology / 343 . Specific location of information to read. Data type read from or written to this controller. The value read from the device is stored in OMRNRDR1. Channel number in the external device. Data area of the controller to be read/written.OMRON HOST LINK | 16 Configuring the Read/Write Information Table The following table provides sample entries for the OMRON1 Read/Write Information table: Field Table Name Tag Name Logical Station Data Area Channel Bit Offset Data Type Entry Description READ OMRNRDR1 0 IR 10 1 BIN1 Specifies the Read/Write table name. Specifies the path to send the request.

To change the operating mode of the PLC to the MONITOR mode. Some OMRON factory configurations operate normally in MONITOR mode. ensure that the OMRON PLC is in the MONITOR mode by setting the switch on the OMRON Programming Console to MONITOR. override the setting on the Programming Console and place the PLC in MONITOR mode using the following procedure: In the OMRON Read/Write Information table. To avoid manually performing this procedure each time you start FactoryLink. configure an analog tag. If this is necessary. Enter ST in the Data Area field (for the OMRON PLC operating status) and enter BIN1 in the Data Type field. For the FactoryLink OMRON protocol module to write to an external device. 344 / FactoryLink Device Interfaces Using EDI Technology . the OMRON PLC monitors bit or channel data from the data areas or specific program addresses and reads it to the FactoryLink real-time database. In this mode.• • • • 16 | OMRON HOST LINK Technical Notes: Monitor Mode TECHNICAL N OTES : M ONITOR M ODE The OMRON PLC operates in the RUN. force write an 02 (which represents MONITOR mode in the ST area) to the FactoryLink analog tag. MONITOR. refer to the OMRON documentation. writes to the PLC will occur normally and no other actions are needed. In this case. For further information about the OMRON Status Write and changing the operating mode. Other OMRON factory configurations may require that the PLC operate in RUN or PROGRAM mode. configure Math and Logic to perform this operation automatically at startup. or PROGRAM modes.

HR. HR. FactoryLink Device Interfaces Using EDI Technology / 345 . HR. AR LR and DM PV IR. AR LR and DM LR and DM LR and DM PV PV A BIN1 BIN1 BIN1 BCD1 BCD1 F BIN2 BCD2 TIM TIMH BCD2 TIM This table shows the data area maximum channel ranges for each OMRON PLC type. AR TC ST ER IR.OMRON HOST LINK | 16 OMRON Data Types and PLC Data Areas OMRON D ATA TYPES AND PLC D ATA A REAS The following table shows the FactoryLink data types and the OMRON data types that are to be used for each OMRON PLC data area: FactoryLink Data Type OMRON Data Type OMRON PLC Data Area D BIN1 BIN1 TCTR ER IR.

• • • • 16 | OMRON HOST LINK OMRON Data Types and PLC Data Areas Data Area PLC Type PLC Number ST 0 ER 1 IR 2 HR 3 AR 4 LR 5 TC 6 DM 7 PV 8 C20 K/P-Series C120 & C120F C200H C500 C500F C1000H C2000H 0 1 2 3 4 5 6 7 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 19 19 63 255 63 63 255 255 09 09 31 99 31 31 99 99 ---27 --27 27 --31 63 31 31 63 63 47 47 127 511 127 127 511 511 -63 511 1999 511 4095 4095 6655 47 47 127 511 127 127 511 511 346 / FactoryLink Device Interfaces Using EDI Technology .

In some cases. Double-Character Code Format (MSD). if so configured. FactoryLink generates and displays messages for the General Electric protocol module on the Run-Time Manager screen and. Single-Character Code Format ER:000n is a single-character format in which one character represents a single error condition. For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. the leftmost integer. n represents the significant characters of the error. and least significant digit (LSD). In the following descriptions.” The ER: string in a message can contain either a single-character or a double-character error code. writes them to message or analog tags. For information about configuring an analog tag.OMRON HOST LINK | 16 Run-Time Application Messages R UN -T IME A PPLICATION M ESSAGES During EDI runtime. ER:00nn is a double-character format in which two characters represent a single error condition. Decode the ER:00nn string by interpreting nn’s most significant digit FactoryLink Device Interfaces Using EDI Technology / 347 . “Messages and Codes. two individual codes appear within a string to indicate multiple error conditions. see “Configuring the Logical Station Control Table” on page 331 of this guide. the rightmost integer. see “Configuring the Logical Station Information Table” on page 333 of this guide. see Chapter 10. For information about configuring a message tag.

• • • • 16 | OMRON HOST LINK Run-Time Application Messages OMRON Error Codes The following error code values occur in the LSD. 348 / FactoryLink Device Interfaces Using EDI Technology . 2 Cause: Not executable in MONITOR mode. Action: Command request cannot be performed with the device in RUN mode. 3 Cause: Not executable with PROM mounted. 4 Cause: B Address over (data overflow). Action: Command request cannot be performed with the device in PROGRAM mode. Example: If: Then: ER:0043 MSD = 4 LSD = 3 Case 0: ER:000e OMRON Response Errors 1 Cause: Not executable in RUN mode. Action: Command request cannot be performed with the device with PROM mounted. Cause: Not executable in PROGRAM mode. Action: Command request cannot be performed with the device in MONITOR mode.

FactoryLink Device Interfaces Using EDI Technology / 349 . Action: Command request cannot be performed with the device in LOCAL mode. Action: Command request cannot be performed with the device with PROM mounted. D Cause: Not executable in LOCAL mode. Action: Verify the Read/Write configuration table entries are valid for device parameter. 2 Cause: Overrun. 3 Cause: FCS error. Action: Verify the parity and the number of data and stop bits setup matches the device. Action: Verify the parity setup matches the device. Action: Verify the number of data and stop bits setup matches the device. 4 Cause: Format error (parameter length error). 1 Cause: Framing error. Contact Customer Support if the problem persists. Action: Verify the number of data and stop bits set up matches the device. Case 1: ER:001e OMRON Response Errors 0 Cause: Parity error.OMRON HOST LINK | 16 Run-Time Application Messages C Cause: Not executable with PROM mounted.

non-registration of I/O table. or others. data length error). Action: Contact OMRON for more information. or duplication of Optical Transmitting I/O Unit. Contact Customer Support if the problem persists. 6 Cause: Instruction not found. Action: Verify the Read/Write configuration table entries are valid for device parameter. data code error. Action: Contact OMRON for more information. Action: Verify the Read/Write configuration table entries are valid for device parameter. Action: Verify the cable is constructed properly and that it is connected to the logical port and device. Case 3: ER:003e Read/write Request Aborted 1 Cause: Transmit error. 8 Cause: Frame length error. Contact Customer Support if the problem persists.• • • • 16 | OMRON HOST LINK Run-Time Application Messages 5 Cause: Entry number data error (parameter error. Action: Verify the Read/Write configuration table entries are valid for device parameter. 350 / FactoryLink Device Interfaces Using EDI Technology . Contact Customer Support if the problem persists. channel over. 9 Cause: Command not executable due to non-executable error clear. Case 2: ER:002e OMRON Response Errors 0 Cause: I/O table generation impossible due to unrecognized Remote I/O Unit.

verify the parity and the number of data and stop bits are configured properly for the device and that the cable ground wire is connected properly. 4 Cause: Reception buffer overflow. verify the cable ground wire is connected properly. Also. Response too large for reception buffer. FactoryLink Device Interfaces Using EDI Technology / 351 . Action: Contact Customer Support immediately. 3 Cause: Received invalid response character. check that the timeout period is defined for the recommended time. Also. Action: Verify the parity and the number of data and stop bits are configured properly for the device. Action: Verify the cable is connected to the logical port and device. Action: Verify the parity and the number of data and stop bits are configured properly for the device. Also.OMRON HOST LINK | 16 Run-Time Application Messages Case 4: ER:004e Read/Write Request Reception Error 2 Cause: Timeout error. 5 Cause: Received invalid start of data response character. 6 Cause: Received NAK response for command request. Action: Verify the Read/Write configuration table entries are valid for device parameter.

Action: Verify the IBM RIC/ARTIC board and the OMRON protocol module have sufficient data storage defined. 3 Cause: OMRON read/write response produced an unknown error. Contact Customer Support if the problem persists. 1 Cause: Aborted due to framing error in transmit data. Contact Customer Support if the problem persists. 1 Cause: Queuing write request error. 2 Cause: Read or write request too large for the transmit buffer. Action: Verify the number of data and stop bits setup matches the device. Action: Verify the IBM RIC/ARTIC board and the OMRON protocol module have sufficient data storage defined. Action: Contact Customer Support immediately. Action: Verify the parity setup matches the device. Case A: ER:00Ae OMRON Response Errors 0 Cause: Aborted due to parity error in transmit data. 352 / FactoryLink Device Interfaces Using EDI Technology .• • • • 16 | OMRON HOST LINK Run-Time Application Messages Case 5: ER:005e OMRON Response Packet Errors 0 Cause: Queuing read request error. Action: Contact Customer Support immediately.

OMRON HOST LINK | 16 Run-Time Application Messages 2 Cause: Aborted due to overrun in transmit data. 4 Cause: Aborted due to format error in transmit data. FactoryLink Device Interfaces Using EDI Technology / 353 . Action: Verify the Read/Write configuration table entries are valid for device parameter. 8 Cause: Aborted due to frame length error in transmit data. Action: Verify the number of data and stop bits set up matches the device. Contact Customer Support if the problem persists. Case B: ER:00Be OMRON Response Errors 0 Cause: Not executable because program area is not 16K bytes. Contact Customer Support if the problem persists. Contact Customer Support if the problem persists. Action: Verify the Read/Write configuration table entries are valid for device parameter. 5 Cause: Aborted due to entry number data error in transmit data. Action: Verify the Read/Write configuration table entries are valid for device parameter.

• • • • 16 | OMRON HOST LINK Run-Time Application Messages 354 / FactoryLink Device Interfaces Using EDI Technology .

19200 (default = 9600) Parity Parity of the transmission. See “Configuring Communication Paths” on page 57 for details. 300. Enter the information as specified with one exception: in the Device Name column. 1200. Note: Before completing the Opto OPTOMUX configuration tables. 7200.Chapter 17 • • • Opto 22 OPTOMUX The External Device Interface (EDI) task allows you to configure FactoryLink to This chapter contains information needed to set up and configure bidirectional communications between the FactoryLink real-time database and one or more Opto 22 OPTOMUX devices. Field Descriptions Logical Port Enter a number. 600. enter OMUX. Valid Entry: 110. defined in the External Device Definition table Logical Port column. 150.99 • (default = 0) Baud Rate Speed at which the task communicates with an Opto 22 OPTOMUX device. Valid Entry: none. open Device Interfaces > Opto 22 OPTOMUX > OPTOMUX Logical Station Control. even. 3600. 2400. odd (default = none) FactoryLink Device Interfaces Using EDI Technology / 355 . 4800. to represent a particular communication path to an Opto 22 OPTOMUX device. you must complete the External Device Definition table. Valid Entry: previously defined logical port number 0 . C ONFIGURING Accessing THE L OGICAL S TATION C ONTROL TABLE In your server application. 9600.

Valid Entry: 7. click Save to validate the information. Valid Entry: tag name Valid Data Type: message When the table is complete.1 to 99. enter a tag name for a message tag to which a text string is written to indicate a communication error associated with this logical port. Baud Rate Parity Data Bits Stop Bits Timeout 0. Column Logical Port Entry 10 Description The communication path used for read and write operations between FactoryLink and devices communicating via this port is represented as 10. The driver communicates to the device using 1 stop bit in the transmission. 8 (default = 8) Number of stop bits used in the transmission. LP1ERR. The driver waits 3 seconds for a response to a read or write command before timing out.1 Sec Number of data bits used in the transmission. the driver waits to receive a response to a read or write command. The driver communicates to the device using 8 data bits in the transmission. Valid Entry: 1. No parity checking.999 (0.• • • • 17 | OPTO 22 OPTOMUX Configuring the Logical Station Control Table Data Bits Stop Bits Timeout 0.1 Sec Status Msg Tag Name 9600 NONE 8 1 30 LP1ERR The EDI task stores communication error messages associated with this logical port in a message tag.9 seconds) Status Message Tag Name Optionally. The following table shows sample Logical Station Control Table entries. 356 / FactoryLink Device Interfaces Using EDI Technology . Define the data type (message) for any tag names displayed in the Tag Definition dialog box. 2 Length of time. Valid Entry: 1 . in tenths of a second. This specifies the communication rate as 9600.

open Device Interfaces > Opto 22 OPTOMUX > OPTOMUX Logical Station Control > “your logical port” > OPTOMUX Logical Station Information. Valid Entry: 0 .999 (default = 0) Device Type Define the type of Opto 22 OPTOMUX device to which communications are to be directed. A logical station represents the combination of a logical port with a physical station. This number must be unique among all Opto 22 OPTOMUX devices across all ports. In a read or write table. enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station). Assign a unique number to each device communicating through this logical port. Valid Entry: Enter one of the following values: DIG4 ANA4 DIG8 ANA8 DIG16 ANA16 Station Address Enter the physical network address of the Opto 22 OPTOMUX device.255 (default = 0) FactoryLink Device Interfaces Using EDI Technology / 357 . Valid Entry: tag name Valid Data Type: analog Logical Station Enter a number to identify the logical station to which the information in this row pertains. You will later enter this logical station number in a read or write table to represent the device defined in this row. this number identifies the device to or from which data is sent or received.OPTO 22 OPTOMUX | 17 Configuring the Logical Station Information Table C ONFIGURING Accessing THE L OGICAL STATION I NFORMATION TABLE In your server application. Valid Entry: unique numeric value from 0 . Field Descriptions Error/Status Tag Name Optionally.

PORT1_ERR1. Column Error/Status Tag Name Logical Station Device Type Station Address Comment Entry PORT1_ERR1 Description Communication error codes generated for this logical station are stored in an analog tag. Station address 0 specifies the physical station address associated with this logical station. User reference 10 DIG16 0 Unload Station 358 / FactoryLink Device Interfaces Using EDI Technology . click Save to validate the information. Valid Entry: alphanumeric string of up to 21 characters When the table is complete. DIG16 specifies the device type associated with this logical station. A device communicating with FactoryLink via logical port 0 is assigned a logical number of 10.• • • • 17 | OPTO 22 OPTOMUX Configuring the Logical Station Information Table Comment (Optional) Reference information about this logical station. The following tables shows sample Logical Station Information Table entries. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box.

Field Descriptions Complete a row for each read or write table. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). open Device Interfaces > Opto 22 OPTOMUX > OPTOMUX Read/Write Control. 0-9 Exception Write If this is an exception write operation in which tag values are written to the device only upon change. If this is a triggered read or a block write table. You can define as many tables in this table as available memory allows. Defining tags that change value frequently as exception writes can slow down communication or result in an error message. Try to make the table name reflective of the data and operation it represents. the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. FactoryLink Device Interfaces Using EDI Technology / 359 . Define one request (table) per line and do not include spaces in the name. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON).OPTO 22 OPTOMUX | 17 Configuring the Read/Write Control Table C ONFIGURING Accessing THE R EAD /WRITE C ONTROL TABLE In your server application. Valid Entry: alphanumeric string of up to 16 characters A-Z. _. Valid Entry: no. In an exception write. an internal change-status indicator (the change status bit) within the tag containing the data to be written prompts the write operation. @. Any specified tag is written to the device in its own packet (message) each time it changes. yes (default = no) Note: Do not specify tags expected to change at frequent intervals in an exception write table. EDI writes this tag’s value to the device. Table Name Give this read and/or write request a name. $. a-z. See “Reading Data from a Device” on page 73 and “Writing Data to a Device” on page 97 for specific instructions on configuring each type of read and write operation. enter YES.

however. The highest priority is 1. enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. To re-enable a cascaded loop or a self-triggered read table. When the value of the block read trigger is forced to 1 (ON). Of these tags. and Block Read Priority fields only apply to Triggered Read Operations. Block Read State. Tip The Block Read Disable tag can disable a block read operation that is either part of a cascaded loop or is self-triggered. To re-enable a block read table that is disabled. the others are optional. 360 / FactoryLink Device Interfaces Using EDI Technology . Block Read Disable. enter a tag name. relative to other read operations. Block Read Trigger If this table is configured for triggered read operations. set this tag back to 0 (OFF). Do not define these block read tags for unsolicited read operations or for write operations.4 (default = 1) Note: The Block Read Trigger. Valid Entry: tag name Valid Data Type: digital Block Read Disable If this table is configured for triggered read operations and you need a digital tag to disable a block read of the tags specified in this table. Block Read Complete. Block Read Disable. Do not define these block read tags for unsolicited read operations or for write operations. When the value of the tag represented by this tag name is forced to 1 (ON). and Block Read Priority fields only apply to Triggered Read Operations. The triggering cycle ceases upon disabling.• • • • 17 | OPTO 22 OPTOMUX Configuring the Read/Write Control Table Block Read Priority If this table is configured for block read operations. the read operation is not executed. it processes the request with the highest priority first. enter a number to indicate the priority of this table. This number influences the order in which the EDI task handles the queuing of block read requests. only Block Read Trigger is required. the others are optional. the addresses are read. only Block Read Trigger is required. If EDI receives two requests at the same time. Of these tags. the Block Read Disable tag must be changed to 0 and the Block Read Trigger tag must be forced to 1. Valid Entry: tag name Valid Data Type: digital Note: The Block Read Trigger. Block Read State. Valid Entry: 1 . even when the block read trigger is set to 1. Block Read Complete.

ignore this column. or a triggered read table in which more than one logical port is specified. Block Read State If this is an unsolicited read operation. relative to other write operations. While the table is being processed. If this is table is configured for a triggered read operation and you need a digital tag to indicate when the operation is complete. ignore this column. or a triggered read table in which more than one logical port is specified. Valid Entry: tag name Valid Data Type: digital Note: Do not use the Block Read Complete if the associated information table contains logical stations assigned to more than one logical port. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. If this table is configured for a triggered read operation and you need a digital tag to indicate the state of the operation (in progress or complete). Valid Entry: tag name Valid Data Type: digital Note: Do not use the Block Read Complete if the associated information table contains logical stations assigned to more than one logical port. Block Write Priority If this table is configured for block or exception write operations.OPTO 22 OPTOMUX | 17 Configuring the Read/Write Control Table Block Read Complete If this is an unsolicited read operation. If EDI receives two requests at the same time. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. The value of the tag represented by this tag name is forced to 1 (ON) at startup. a write operation. the state tag is forced back to 1. The value of the tag represented by this tag name is forced to 1 (ON) at startup.4 (default = 1) FactoryLink Device Interfaces Using EDI Technology / 361 . enter a tag name. the complete tag is forced to 1 again. This number influences the order in which the EDI task handles the queuing of write requests. Valid Entry: 1 . the tag is set to 0 (OFF). enter a number to indicate the priority of this table. enter a tag name. it processes the request with the highest priority first. The highest priority is 1. a write operation.

the others are optional. When the value of the tag represented by this tag name is forced to 1 (ON). To re-enable a cascaded loop or a self-triggered read table. See “Application Design Tips and Techniques” on page 127 for details. Block Write Trigger If this table is to be configured for block write operations. 362 / FactoryLink Device Interfaces Using EDI Technology . Block Write Disable. Valid Entry: tag name Valid Data Type: digital Block Write Disable If this table is configured for block write operations or exception write operations. Of these tags. To disable exception writes you must also define a Block Write Trigger even if it is never used. set this tag back to 0 (OFF). enter a tag name for a digital tag to disable writes to the addresses specified in this table. you plan to periodically disable. Valid Entry: tag name Valid Data Type: digital Tip The Block Write Disable tag can disable a block write operation that is either part of a cascaded loop or is self-triggered. The triggering cycle ceases upon disabling. Block Write Complete. the write operations are not executed. however. Block Write and Block Write Priority tags apply only to write operations. State. enter a tag name for a digital tag to initiate a block write of the tag values represented by the tag names specified in the Read/Write Information table to the addresses defined to receive the values. the tag values are written.• • • • 17 | OPTO 22 OPTOMUX Configuring the Read/Write Control Table Note: The Block Write Trigger. only Block Write Trigger is required for a block write table. When the value of the block write trigger is forced to 1 (ON). Do not define these block write tags for read operations. the Block Write Disable tag must be changed to 0 and the Block Write Trigger tag must be forced to 1. even when the block write trigger is set to 1 or an exception value changes. To re-enable a block write table that is disabled.

After the data defined in the Read/Write Information table is written to the device. The block read priority. This is not an exception write table. The following table shows sample Read/Write Control Table entries. FactoryLink reads the specified address and stores its value in the tag configured for this table (in the Read/Write Information table). enter a tag name. enter a tag name. omux_rtrig1. Valid Entry: tag name Valid Data Type: digital Block Write State If this table is configured for block write operations and you need a digital tag to indicate the state of the operation (in progress or complete).OPTO 22 OPTOMUX | 17 Configuring the Read/Write Control Table Block Write Complete If this table is configured for block write operations and you need a digital tag to indicate when the operation is complete. Column Table Name Exception Write Block Read Priority Block Read Trigger Block Read Disable Entry READ Description The name of this table is READ. the state tag is forced back to 1. and does not process the READ table. click Save to validate the information. NO 1 omux_rtrig1 omux_rdbl1 When the value of omux_rdbl1 is 1. FactoryLink disregards the trigger tag. The value of the tag represented by this tag name is forced to 1 (ON) at startup. After the data defined in the Read/Write Information table is written to the device. the tag is set to 0 (OFF). FactoryLink Device Interfaces Using EDI Technology / 363 . the highest priority. the complete tag is forced to 1 again. which is automatically set if you do not enter a value. is 1. Valid Entry: tag name Valid Data Type: digital When the table is complete. When the value of omux_rtrig1 is 1. The value of the tag represented by this tag name is forced to 1 (ON) at startup. Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. While the table is being processed.

tag names for tags unique to write tables are not defined. omux_rst1 is set to 0. Leaving this field blank configures the table to not support triggered writes. tag names for tags unique to write tables are not defined. FactoryLink forces a value of 1 to omux_rcpt1. Since this is not configured as a write table. tag names for tags unique to write tables are not defined. Once the data is read and stored in the specified tag. FactoryLink forces a value of 1 to omux_rst1. During the read operation. Since this is not configured as a write table. Since this is not configured as a write table. The block write priority is set to 1 by default. omux_rst1 1 364 / FactoryLink Device Interfaces Using EDI Technology .• • • • 17 | OPTO 22 OPTOMUX Configuring the Read/Write Control Table Block Read Complete Block Read State Block Write Priority Block Write Trigger Block Write Disable Block Write Complete Block Write State omux_rcpt1 Once the data in the device is read and stored in the specified tag (defined in the Read/Write Information table).

see “Technical Notes” on page 368. float Logical Station Enter the number representing the device from which the data is read or to which the tag’s value is written. specify a tag name for a tag in which FactoryLink stores the data read from the device. Init Data Data to be read from or written to the memory address that you specify in the Module Position field. Valid Entry: tag name Valid Data Type: digital.999) Module Position Position on the Opto 22 OPTOMUX device to be read or written to by the EDI task. Valid Entry: 0 . For a write table. analog. Field Descriptions Tag Name For a read table. Valid Entry: For a list of valid entries. This number was originally defined in the Logical Station Information table for the logical port through which communication with this device occurs.OPTO 22 OPTOMUX | 17 Configuring the Read/Write Information Table C ONFIGURING Accessing THE R EAD /WRITE I NFORMATION TABLE In your server application. Valid Entry: previously defined logical station number (0 . Typical users can leave this field blank. See “Read/Write Information Init Data Field Notes” on page 370 for more information about this feature. Valid Entry: alphanumeric or hexadecimal string of up to four characters Note: The Init Data column is typically not used.15 Attribute Attribute name identifying the type of read or write command to send to the Opto 22 OPTOMUX device. FactoryLink Device Interfaces Using EDI Technology / 365 . specify a tag name for a tag containing a value written to the device. open Device Interfaces > Opto 22 OPTOMUX > OPTOMUX Read/Write Control > “your table name” > OPTOMUX Read/Write Information.

Column Table Name Tag Name Entry READ PROCVAR Description The table name defined in the Read/Write Control table is displayed. float) for any tag names displayed in the Tag Definition dialog box. click Save to validate the information. The following table shows sample Read/Write Information Table entries. The value read from the device is stored in PROCVAR. Define the data type (digital. FactoryLink processes the table.• • • • 17 | OPTO 22 OPTOMUX Configuring the Read/Write Information Table When the table is complete. When the READ table is triggered by omux_rtrig1 (defined in the Read/Write Control table). This specifies the position on the Opto 22 OPTOMUX device to access. The value stored in this tag is read from the device configured as logical station 1. Data to read from or write to the memory address you specified in the Module Position column. analog. This specifies the type of command to execute using this device. Logical Station Module Position Attribute Init Data 1 0 digital 0101 366 / FactoryLink Device Interfaces Using EDI Technology .

Valid Entry: 0 . Valid Entry: For a list of valid entries. open Device Interfaces > Opto 22 OPTOMUX > OPTOMUX Initialization Information. Valid Entry: 0 .000 entries through the OPTOMUX Initialization Information table. Field Descriptions Logical Station Number Module Position Enter a number to identify the logical station to which initialization commands are sent. Accessing In your server application. click the Save to validate the information. “Technical Notes” on page 368. FactoryLink Device Interfaces Using EDI Technology / 367 .999 Position the Opto 22 OPTOMUX device to be written to by the EDI task.OPTO 22 OPTOMUX | 17 Configuring the OPTOMUX Initialization Information Table C ONFIGURING THE OPTOMUX I NITIALIZATION I NFORMATION TABLE You can configure one OPTOMUX Initialization table with up to 1. Init Data Data to be written to the memory address specified in the Module Position field. The EDI task executes this table at startup of the EDI task or when the Opto 22 OPTOMUX protocol module receives a Power Up Clear Expected message from a logical station. When the table is complete. Valid Entry: alphanumeric or hexadecimal string of up to four characters.15 Attribute Attribute name identifying the type of write command to send to the Opto 22 OPTOMUX device.

Note: Always think of the previous Opto 22 OPTOMUX as the Host. create an RS232-C cable with the following pinout.• • • • 17 | OPTO 22 OPTOMUX Technical Notes TECHNICAL N OTES Cable Diagrams This section contains pin-out diagrams for cables required to connect the Opto 22 OPTOMUX devices to the serial cards. The last Opto 22 OPTOMUX has only 5 wires — “To Host.” “From Host. Serial Connections To connect a serial card to an Opto 22 OPTOMUX AC-7.” and common. 368 / FactoryLink Device Interfaces Using EDI Technology . RS 232 Cable .Serial Card to Opto 22 OPTOMUX AC-7 Serial Card 2 TxD 3 RxD 4 RTS CTS 5 Ground 7 DSR 6 RLSD 8 DTR 20 OPTOMUX AC-7 2 3 4 5 7 6 8 20 TxD RxD RTS CTS Ground DSR RLSD DTR Serial RS-422 The following diagram shows the connection between adjacent Opto 22 OPTOMUX controllers on the serial link and serial RS-422 cards.

OPTO 22 OPTOMUX | 17 Technical Notes FactoryLink Device Interfaces Using EDI Technology / 369 .

370 / FactoryLink Device Interfaces Using EDI Technology . This list provides the Attributes used in the Init Data column. From the OPTO 22 operations manual. Refer to the OPTO 22 operations manual for valid entries for the Attribute. assume a table is configured for exception writes and the record is configured with an analog tag with an Attribute of ANAOUT and Init Data of 284. For example. The Attributes are grouped based on how the data entered in the Init Data column is interpreted. leave it blank. To determine how the data is interpreted by the device you must look up the command sent in the OPTO 22 operations manual. its value is discarded by the driver and the value of 284 is sent in its place. It is not used in read operations. The Init Data is placed in the [data] portion of the command. Commands using One ASCII Character are: CFGDWDOG and CFWAWDOG.• • • • 17 | OPTO 22 OPTOMUX Technical Notes Read/Write Information Init Data Field Notes These are detailed notes for users who want to use of the Init Data feature of the driver. Valid Entry: Accepted character is any character accepted in the field. Refer to the OPTO 22 operations manual for the Attributes valid entries. If an Attribute is not listed. the Init Data is not used. Valid characters to enter are based on the selected Attribute. (See below to determine the command sent for the entered attribute). the value in the related tag is ignored and the data in the Init Data column is sent in its place. If additional characters are entered in the field. In the above example. One ASCII Character The first character entered is sent as the write data. Typical users can leave this field blank and skip this discussion. a command ‘S’ accepts “[data] contains three ASCII-Hex digits” and so the 284 is interpreted as hexadecimal. the Attribute ANAOUT send a command ‘S’. When used in a table designated as write. The Init Data column is used to send static data to the logical station and module number specified in the Read/Write Information record. When the analog value changes. then an error is generated by the driver when the command is to be issued and the write is aborted. Valid characters to enter are based on the selected Attribute.

DELAY2. Valid characters to enter are based on the selected Attribute. One to Four ASCII Characters One to four entered characters are sent as the write data. Commands using Four ASCII Characters are CFGOFFST. If less than two or more than two characters are entered in the field. 000B is sent. Valid characters to enter are based on the selected Attribute. If more than three characters are entered in the field. and OFFPULSE. If less than four are entered. LRESSQWV and HRESSQWV. If more than four characters are entered in the field. DELAY1. FactoryLink Device Interfaces Using EDI Technology / 371 . Refer to the OPTO 22 operations manual for valid entries for the Attribute. then an error is generated by the driver when the command is to be issued and the write is aborted. DELAY3. then an error is generated by the driver when the command is to be issued and the write is aborted. Refer to the OPTO 22 operations manual for valid entries for the Attribute. then an error is generated by the driver when the command is to be issued and the write is aborted. CFGGAIN. Commands using Two ASCII Characters are TIMERRES and RDAVERAG.OPTO 22 OPTOMUX | 17 Technical Notes Two ASCII Characters The first two characters entered are sent as the write data. One to Three ASCII Characters One to three entered characters are sent as the write data. Valid characters to enter are based on the selected Attribute. DELAY4. Refer to the OPTO 22 operations manual for valid entries for the Attribute. For example. Commands using One to Four ASCII Characters are CFGTMPRB. then leading zeros (0)s are added to the data sent. Valid Entry: Accepted characters are any characters accepted in the field. if a B is entered. then an error is generated by the driver when the command is to be issued and the write is aborted. Commands using One to Three ASCII Characters are ANAOUT. Valid Entry: Accepted characters are any character accepted in the field. Valid Entry: Accepted characters are any character accepted in the field. Four ASCII Characters Four entered characters are sent as the write data. ONPULSE. If more than four characters are entered in the field.

Valid characters to enter are based on the selected Attribute. If the initialization data cannot be sent to a particular brain board successfully.5. initialization was treated on a per port bases. then no read or writes will be attempted until all stations are successfully initialized. Note: Prior to driver version 6. If a character other than 0 or 1 is entered. that is. If initialization is unsuccessful.1. only the first is used. Each time a read or write is requested from the EDI task. Initialization Sequence The data from the initialization tables is sent to each configured brain board at start up. the driver checks the station’s initialization status. 0 or 1 Character Either a 0 or a 1 must be entered. the read or write response is returned to EDI as failed due to a PUC error and the station is marked as requiring initialization. the results are unpredictable. a command ‘K’ Activate Outputs is sent. then the initialization data is sent. If the initialization cannot be completed successfully. if any station configured on the port fails. If the status is initialization required. a command ‘L’ Deactivate Outputs is sent. then that station is marked as requiring initialization. If more than one character is entered in the field. a brain board returns a Power Up Clear (PUC) error. the read or write is marked as failed due to power up clear error and returned to EDI. Valid Entry: 0 or 1 If a 0 is entered. No further read or write commands will be attempted until the initialization data is successfully sent again. the driver will attempt to send the initialization data to that station again and then retry the command that had the PUC error response. Commands using 0 or 1 Character are digital. If. during normal read and write operations. Refer to the OPTO 22 operations manual for valid entries for the Attribute.• • • • 17 | OPTO 22 OPTOMUX Technical Notes Valid Entry: Accepted characters are any character accepted in the field. If the status is initialized successfully. then the additional characters are ignored. the read or write commands are sent immediately. If a 1 is entered. 372 / FactoryLink Device Interfaces Using EDI Technology .

digital or both types of boards. The table lists the configuration table Attribute entries along with the actual OPTOMUX command letter issued by the driver and whether the command is for analog. the following entries are valid for the Attribute field in both the OPTOMUX Initialization Information table and in the OPTOMUX Read/Write Information table for tables configured for write operations. delay Configure digital watchdog. Consult this manual to determine the function for each of the issued commands. It is highly recommended that before configuring the OPTOMUX driver that you obtain the Brain Board operations manual for the appropriate device. Valid Entry ANAOUT OPTOMUX Command Letter Issued S D D Y H P O W I k L Y Command Type analog analog digital analog both digital digital analog both analog digital digital Description Read/write analog output (can be used in read table as well) Configure analog watchdog.OPTO 22 OPTOMUX | 17 Technical Notes Write Operations For write operations. delay Set gain coefficients Configure input Configure latch to off Configure latch off to on Set offset Configure output Configure temperature probe Deactivate output Clear pulse counter CFGAWDOG CFGDWDOG CFGGAIN CFGINP CFGLCHOF CFGLCHON CFGOFFST CFGOUT CFGTMPRB CLEAR CLRCOUNT FactoryLink Device Interfaces Using EDI Technology / 373 .

• • • • 17 | OPTO 22 OPTOMUX Technical Notes Valid Entry CLRDURAT CLRLATCH DELAYOFF DELAY1 DELAY2 DELAY3 DELAY4 DIGITAL OPTOMUX Command Letter Issued g S Z/G Z/H Z/I Z/J Z/K K or L Z/M Z/L c b A B K or L U V n Command Type digital digital digital digital digital digital digital digital digital digital digital digital both both digital digital digital digital Description Clear pulse duration counter Clear latch Set Time Delay with G modifier Set Time Delay with H modifier Set Time Delay with I modifier Set Time Delay with J modifier Set Time Delay with K modifier K sent if digital tag data = 1 L sent if digital tag data = 0 Set Time Delay with M modifier Set Time Delay with L modifier Trigger on negative pulse (configure duration measurement for negative pulses) Trigger on positive pulse (configure duration measurement for positive pulses) Power up clear Reset K sent if digital tag data = 1 L sent if digital tag data = 0 Start pulse counter Stop pulse counter Set timer resolution HRESSQWV* LRESSQWV* NEGATRIG POSITRIG POWERUP RESET SET STARTCNT STOPCNT TIMERRES 374 / FactoryLink Device Interfaces Using EDI Technology .

lower 2) which sets an On time of (1 * TRS * 2. digital or both types of boards. Consult this manual to determine the function for each of the issued commands. It is highly recommended that before configuring the OPTOMUX driver that you obtain the Brain Board operations manual for the appropriate device. Read Operations For read operations. The table lists the configuration table Attribute entries along with the actual OPTOMUX command letter issued by the driver and whether the command is for analog.56 sec). High Resolution (HRESSQWV) value of 12875 decimal = 324B hexadecimal (upper nibble value 50. the following entries are valid for the Attribute field in the OPTOMUX Read/Write Information table for tables configured for write operations.56 sec) and an Off time of (2 * TRS * 2.OPTO 22 OPTOMUX | 17 Technical Notes Note: * Write value is split into two components: * Upper nibble used for On time * Lower nibble used Off time Examples: Low Resolution (LRESSQWV) value of 256 decimal = 0102 hexadecimal (upper nibble value 1. lower 75) which sets an On time of (50 * TRS * 10 msec) and an Off time of (75 * TRS * 10 msec). Valid Entry ANAIN ANAOUT OPTOMUX Command Letter Issued L K d W Command Type analog analog digital digital Description Read analog input Read/write analog output (can be used in write table as well) Read pulse measurement complete bit Read counter CMPLTBIT COUNTER FactoryLink Device Interfaces Using EDI Technology / 375 .

See DIGITAL in the Write Operations table.) Read and clear pulse duration measurement Read pulse duration counter Calculate Gain Coefficient Read latch Read and clear latch Instructs Opto 22 OPTOMUX to deactivate the selected modules for a specified period of time and then reactivate the modules Calculate offset Instructs Opto 22 OPTOMUX to activate selected modules for a specified period of time Reads and averages the analog value of a single position over a specified number of samples Calculate and set gain Calculate and set offset Read temperature probe input DURATCLR f e X Q R l digital digital analog digital digital digital DURATION GAIN LATCH LATCHCLR OFFPULSE OFFSET ONPULSE g k analog digital RDAVERAG M analog SETGAIN SETOFF TEMPPROB Z h l analog analog analog 376 / FactoryLink Device Interfaces Using EDI Technology .• • • • 17 | OPTO 22 OPTOMUX Technical Notes Valid Entry COUNTCLR DIGTIAL OPTOMUX Command Letter Issued X M Command Type digital digital Description Read and clear counter Read/write digital output (Can be used in write table as well.

The Read/Write Table experiencing the error The number of the packet experiencing the error TBL:XXX PKT:XXX FactoryLink Device Interfaces Using EDI Technology / 377 .OPTO 22 OPTOMUX | 17 Error Messages E RROR M ESSAGES During EDI run time. FactoryLink generates and displays messages for the Opto 22 OPTOMUX protocol module on the Run-Time Manager screen. These error codes come from the EDI task or the Opto 22 OPTOMUX external devices. These messages are stored in FactoryLink tags. Opto 22 OPTOMUX Error Message Format Opto 22 OPTOMUX run-time error messages appear on the Run-Time Manager screen in the following format: DEV:XXX LSTA:XXX ER:XXX TBL:XXX PKT:XXX where DEV:XXX LSTA:XXX ER:XXX The device The logical station number The error code that identifies the communication error. You define the tag names for these tags in the Logical Station table. See “Messages and Codes” on page 147 for information about the messages displayed for the EDI task and the format in which protocol module messages are generated and for a list of the error messages generated by the FactoryLink EDI task.

Verify the device configuration and cabling. Invalid echo. Received invalid message ID. 2. Description Action 1. Error Code Code 06H 07H 08H 0AH 14H 15H 16H 17H 18H 19H Cause Received invalid read length.• • • • 17 | OPTO 22 OPTOMUX Error Messages EDI Error Codes The EDI task generates the following error codes. 3. Transmit error. and data format parameters. 378 / FactoryLink Device Interfaces Using EDI Technology . Check that FactoryLink configuration tables contain the proper station addresses and parameters. Buffer overflow error. Turn around error. parity. Received translate error. Checksum error on returned data. Received bad data error. Verify the OPTOMUX Logical Station Control table contains the proper baud rate. (For Error Code 15H only) 4. Verify the brain board’s power supply is set at the proper voltage level. Invalid data returned.

Action: Refer to the brain board operations manual for the appropriate Opto 22 OPTOMUX device. 25H Cause: Specified limits invalid. 23H Cause: Data field error (not enough characters). Action: Refer to the brain board operations manual for the appropriate Opto 22 OPTOMUX device. FactoryLink Device Interfaces Using EDI Technology / 379 .OPTO 22 OPTOMUX | 17 Error Messages Opto 22 OPTOMUX Error Codes Opto 22 OPTOMUX devices generate the following error codes. 24H Cause: Communications link watchdog timeout. 20H Cause: Checksum error. Action: Refer to the brain board operations manual for the appropriate Opto 22 OPTOMUX device. Error Code 1EH Description Cause: Unexpected power up clear. Action: Refer to the brain board operations manual for the appropriate Opto 22 OPTOMUX device. 22H Cause: Non-printable ASCII character. Action: Refer to the brain board operations manual for the appropriate Opto 22 OPTOMUX device. 1FH Cause: Undefined command. Action: Refer to the brain board operations manual for the appropriate Opto 22 OPTOMUX device. Action: Refer to the brain board operations manual for the appropriate Opto 22 OPTOMUX device. 21H Cause: Input buffer overrun. Action: Refer to the brain board operations manual for the appropriate Opto 22 OPTOMUX device.

• • • • 17 | OPTO 22 OPTOMUX Error Messages 380 / FactoryLink Device Interfaces Using EDI Technology .

Logical Port Enter a number. Valid Entry: none. you must complete the External Device Definition table. This entry must match the baud rate configuration of the devices. Refer to the device manufacturer’s documentation for details. C ONFIGURING THE L OGICAL S TATION C ONTROL TABLE Open the Logical Station Control Table. Refer to the device manufacturer’s documentation for details.115200 (default=9600) Parity Enter the parity error correction during transmission via this logical port. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. See “Identifying Protocol Types and Defining Logical Ports” on page 58for details. This entry must match the configuration of the devices communicating via this port. Valid Entry: previously defined logical port number Baud Rate Enter the speed at which the protocol module communicates with the devices linked to FactoryLink via this logical port.Chapter 18 • • • Siemens CP525 This chapter contains information to set up and configure bidirectional communications between the FactoryLink real-time database and the Siemens CP525 using RK512 with either 3964 or 3964R protocol. defined in the External Device Definition table Logical Port column. odd (default=even) • FactoryLink Device Interfaces Using EDI Technology / 381 . In your server application. open Device Interfaces > Siemens CP525. to represent a particular communication path to a device. Note Before completing the protocol-specific Siemens CP525 configuration tables. Valid Entry: 110 . even.

the protocol module will wait to receive a response to a read or write command before timing out. None Siemens Procedure 3964 BCC (Default) Siemens Procedure 3964R Retry Request Enter the maximum number of times the protocol module will retry a read or write command to a device communicating through this logical port if the command response is invalid or is not received.65535 (default=3) Master/Slave Indicate whether the FactoryLink station is the Master or the Slave of the communications channel. 2 (default=1) Response Timeout 0. This entry must match the configuration of the devices communicating via this port. in tenths of a second. Refer to the device manufacturer’s documentation for details. Valid Entry: standard Siemens timeouts. Refer to the device manufacturer’s documentation for details. based on the baud rate (default=0) LRC Error Detection Enter the type of error detection protocol. Valid Entry: 0 . 8 (default=8) Stop Bits Enter the number of bits sent after a character to create a pause before the start of the next character.1 Sec Enter the length of time. You must enter a value greater than 0 for the protocol module to timeout. M (Default) Master S Slave Status Msg Tag (Optional) Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. Valid Entry: 1. This entry must match the configuration of the devices communicating via this port. Valid Entry: 7. Valid Entry: tag name Valid Data Type: message 382 / FactoryLink Device Interfaces Using EDI Technology .• • • • 18 | SIEMENS CP525 Configuring the Logical Station Control Table Data Bits Enter the number of data bits used during transmission via this logical port.

Specifies the error checking method. click the Save icon to validate the information. Specifies the communication rate. Message tag containing Siemens error messages. Master (default). Adds a parity bit to the sum of the transmitted bits to make it even. The response timeout is 10 seconds.1 Sec) LRC Error Detection Retry Request Master/Slave Status Msg Tag 9600 EVEN 8 1 100 BCC 3 M SIEM_LPORT0_ MSG FactoryLink Device Interfaces Using EDI Technology / 383 . Attempt the request three times before generating a timeout. Baud Rate Parity Data Bits Stop Bits Response Timeout (0. Define the data type (message) for any tag names displayed in the Tag Definition dialog box.SIEMENS CP525 | 18 Configuring the Logical Station Control Table When the table is complete. The following table provides sample entries for the Siemens 525 Logical Station Control table: Field Logical Port Entry Description 0 Specifies the logical communication path configured by this table. Specifies 1 stop bit in the transmission. Specifies 8 data bits in the transmission.

A logical station represents the combination of a logical port with a physical station. You will later enter this logical station number in a read or write table to represent the device defined in this row. Most devices can transmit 256 bytes. 384 / FactoryLink Device Interfaces Using EDI Technology . select the row for the logical port you are configuring and open Logical Station Information table Complete a row for each device to communicate through this logical port. 64 Comment (Optional) Enter reference information about this logical station. Assign a unique number to each device communicating through this logical port. Error /Status Tag Name (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station).3) does not affect the maximum packet size. Valid Entry: alphanumeric string of up to 21 characters When the table is complete. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box. this number will identify the device to or from which data is to be sent or received. You can animate output-text objects to display the codes stored in an Error/Status Tag Name tag on a graphics screen. The protocol being used (point-to-point or IEEE 802. Valid Entry: 32. Valid Entry: 0 .• • • • 18 | SIEMENS CP525 Configuring the Logical Station Information Table C ONFIGURING THE L OGICAL S TATION I NFORMATION TABLE From the Logical Station Control table. click the Save icon to validate the information. Valid Entry: tag name Valid Data Type: analog Logical Station Enter a number to identify the logical station to which the information in this row pertains. In a read or write table. or 128 registers of data.999 Max Packet Length Define the maximum number of bytes the device defined in this row can transmit in one message.

the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. Specifies the logical communication path. Table Name Assign a name to this read or write request. accept the default of NO. Complete a row for each read or write table. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). If this is a triggered read or a block write table. FactoryLink Device Interfaces Using EDI Technology / 385 . Try to make the table name reflective of the operation it represents. Define one request (table) per line and do not include spaces in the name. Maximum packet length is 64. Valid Entry: alphanumeric string of up to 16 characters Unsolicited Read For EDI to interpret this operation as a triggered block read or as a write operation.SIEMENS CP525 | 18 Configuring the Read/Write Control Table The following table provides sample entries for the Siemens 525 Logical Station Information table: Field Error/Status Tag Name Logical Station Max Packet Length Entry Description SIEM_STATION0_ STATUS 0 64 Contains information about communication errors. Tip See “Application Design Tips and Techniques” on page 127 for information about triggering schemes using tags defined in this table. C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Open the Read/Write Control table. You can define as many tables as available memory allows.

If you enter FORCE. The incoming data will be stored in the real-time database as specified in this field. the data is stored in the specified tag and the change-status indicator is automatically set to 1.• • • • 18 | SIEMENS CP525 Configuring the Read/Write Control Table If this is an unsolicited read operation. no. no (default=no) 386 / FactoryLink Device Interfaces Using EDI Technology . the incoming data will be stored in the tag represented by the tag name specified in the Read/Write Information table. If the current value of the tag is equal to the new value. EDI writes this tag’s value to the device. enter YES. For EDI to interpret this operation as an exception write and write tag values to the device only when those values change. If a different value is being stored the tag. the change-status indicator is unaffected. enter YES or FORCE. If you enter YES. Valid Entry: yes. In an exception write. regardless of whether the current value matches the new value. Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. EDI will interpret this operation as an unsolicited read and emulate the device’s addressing structure based on entries you make in the Read/Write Information table. an internal change-status indicator within the tag containing the data to be written prompts the write operation. Valid Entry: yes. accept the default of NO. Defining tags that change value frequently as exception writes can slow down communications or result in an error message. force (default=no) Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. however. Any tag specified will be written to the device in its own packet (message) each time it changes. it will overwrite the current value and the tag’s change-status indicator will be set to 1 (ON). If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed).

however.SIEMENS CP525 | 18 Configuring the Read/Write Control Table Block Read Priority If this is a block read operation. Block Read Complete. Do not define these tags for unsolicited read operations or for write operations. The default is 1. the Block Read Trigger tag must be toggled or forced to 1.4 (default=1) Note The Block Read Trigger. See “Application Design Tips and Techniques” on page 127 for details. accept the default of 1. The triggering cycle will cease upon disabling. Block Read Trigger If this is an unsolicited read or a write operation. and Block Read State tags apply only to triggered read operations. This field defaults to 1 regardless of whether the operation being defined is a block read. the addresses are read. To reenable a cascaded loop or a self-triggered read table. relative to other read operations. This number influences the order in which the EDI task handles the queuing of block read requests. Block Read Disable. FactoryLink Device Interfaces Using EDI Technology / 387 . Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. ignore this field. When this tag’s value is forced to 1 (ON). enter a number to indicate the priority of this table. If this is a triggered read operation. it processes the request with the highest priority first. Valid Entry: tag name Valid Data Type: digital Tip The Block Read Disable tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered. this field is required. The highest priority is 1. Valid Entry: 1 . If EDI receives two requests at the same time. If this is an unsolicited read or a write operation.

After the tags defined in the Read/Write Information table are updated in the FactoryLink database. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. the complete tag is forced to 1 again. relative to other write operations. Valid Entry: tag name Valid Data Type: digital Block Write Priority If this is a block or exception write operation. This number influences the order in which the EDI task handles the queuing of write requests. enter a tag name.• • • • 18 | SIEMENS CP525 Configuring the Read/Write Control Table Block Read Disable If this is an unsolicited read or a write operation. Valid Entry: tag name Valid Data Type: digital Block Read State If this is an unsolicited read or a write operation. If this is a triggered read operation. ignore this field. enter a tag name. ignore this field. this field is optional. set this tag back to 0 (OFF). 388 / FactoryLink Device Interfaces Using EDI Technology . This tag is forced to 1 (ON) at startup. To reenable a block read table that is disabled. the state tag is forced back to 1. Valid Entry: tag name Valid Data Type: digital Block Read Complete If this is an unsolicited read or a write operation. The highest priority is 1. If EDI receives two requests at the same time. While the table is being processed. If this is a triggered read operation. even when the block read trigger is set to 1. If this is a triggered read operation. If you need a digital tag to disable a block read of the tags specified in this table. ignore this field. If you need a digital tag to indicate the state of this operation (in progress or complete). it processes the request with the highest priority first. the tag is set to 0 (OFF). If you need a digital tag to indicate when this operation is complete. Do not use this tag when more than one logical port is specified in a single table. this field is optional. enter a number to indicate the priority of this table. The default is 1. When this tag’s value is forced to 1 (ON). This tag is forced to 1 (ON) at startup. the read operation is not executed. this field is optional. enter a tag name.

however. FactoryLink Device Interfaces Using EDI Technology / 389 . Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. accept the default of 1. Do not define these tags for read operations.4 (default=1) Note The Block Write Trigger. If this is a block write table or an exception write table you plan to periodically disable. the Block Write Trigger tag must be toggled or forced to 1. See “Application Design Tips and Techniques” on page 127 for further details.SIEMENS CP525 | 18 Configuring the Read/Write Control Table If this is a read operation. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. To reenable a cascaded loop or a self-triggered write table. Block Write Complete. The triggering cycle will cease upon disabling. Valid Entry: 1 . Block Write Disable. the write operation is not executed. When this tag’s value is forced to 1 (ON). ignore this field. Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. If this is a block write table or an exception write table you plan to periodically disable. even when the block write trigger is set to 1. ignore this field. When this tag’s value is forced to 1 (ON). This field defaults to 1 regardless of whether the operation being defined is a block or exception write. this field is optional. and Block Write State tags apply only to write operations. FactoryLink writes the values. this field is required. Valid Entry: tag name Valid Data Type: digital Tip The Block Write Disable tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered.

the state tag is forced back to 1. If this is a block write table. This tag is forced to 1 (ON) at startup. set this tag back to 0 (OFF). This tag is forced to 1 (ON) at startup. the tag is set to 0 (OFF). Valid Entry: tag name Valid Data Type: digital Block Write Complete If this is a read or exception write operation. enter a tag name. While the table is being processed. Define the data type (digital) for any tag names displayed in the Tag Definition dialog box.• • • • 18 | SIEMENS CP525 Configuring the Read/Write Control Table To reenable a block write table that is disabled. enter a tag name. ignore this field. Valid Entry: tag name Valid Data Type: digital When the table is complete. After the data defined in this table’s Read/Write Information table is written to the device. Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. click the Save icon to validate the information. ignore this field. the complete tag is forced to 1 again. If this is a block write operation. 390 / FactoryLink Device Interfaces Using EDI Technology . If you need a digital tag to indicate the state of this operation (in progress or complete). Do not use this tag when more than one logical port is specified in a single table. Do not use this tag when more than one logical port is specified in a single table. After the data defined in this table’s Read/Write Information table is written to the device. this field is optional. If you need a digital tag to indicate when this operation is complete. this field is optional.

Table will not perform unsolicited reads. Block Write Priority Block Write Trigger Block Write Complete Block Write Disable Block Write State 1 FactoryLink Device Interfaces Using EDI Technology / 391 . The write priority for this table is set to 1 by default. Since this is a read table. Table will not perform exception writes. When the value of SIEM_READ_ TRIGGER is 1 or (on). Priority for tables set to 1.SIEMENS CP525 | 18 Configuring the Read/Write Control Table The following table provides sample entries for the Siemens 525 Read/Write Control table: Field Table Name Unsolicited Read Exception Write Block Read Priority Block Read Trigger Entry Description READ NO NO 1 SIEM_READ_ TRIGGER Specifies the table name. a block read of values specified by the Read/Write Information table associated with SIEMBRD occurs. the tags specific to write requests are not defined.

For a Write Table – add a table entry for each tag to be written when the operation executes. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. Tag Name For a read table. For read operations: CB DB DX FB IB OB PB TB Counters Data block Extended data block Flag bytes Input bytes Output bytes Peripheral blocks Timers For write operations: DB Data block DX Extended data block 392 / FactoryLink Device Interfaces Using EDI Technology . For a Read Table – add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes. message Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written. For a write table. Valid Entry: previously defined logical station number PLC Region Enter the data area of the PLC to be read/written.• • • • 18 | SIEMENS CP525 Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. Valid Entry: tag name Valid Data Type: digital. longana. specify a tag name for a tag in which FactoryLink will store the data read from the device. select the row for the table you are configuring and open the Read/Write Information table. float. analog. specify a tag name for a tag containing a value to be written to the device.

analog.255 Enter the address of word in word regions or address of byte in byte regions that is read or written. or floating-point) for any tag names displayed in the Tag Definition dialog box.7 (default=NONE) When the table is complete. Valid Entry: NONE. click the Save icon to validate the information. OB Bit/Length (For digital tags) Bit in the word or byte that is read or written. 0 . DX.SIEMENS CP525 | 18 Configuring the Read/Write Information Table Data Block Word/ Byte Enter the data block number of the address to be read or written. 0 . Length in words: (For word regions) Limited to the packet size for the station: 64 = 64 words. 32 = 32 words Length in bytes: (For byte regions) Limited to the packet size for the station: 64 = 128 bytes.7 (MSB): For byte regions (For message tags) Length in word or byte that is read or written. Define the data type (digital. Valid Entry: NONE. DB. 0-255 CB. Valid Entry: 3 . TB 0-127 IB. 32 = 64 bytes Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. Valid Entry: NONE.4 (default=NONE) Specify the byte number of the coordination flag or enter NONE if no coordination flag is set. 0 . 0 (LSB) . PB. FB. long analog. FactoryLink Device Interfaces Using EDI Technology / 393 .15 (MSB): For word regions 0 (LSB) . Coordination Flag CPU Coordination Flag Byte Coordination Flag Bit Specify the number of the CPU that is to process the read or write operation or enter NONE for no CPU. Valid Entry: See “Siemens CP525 Data Types” on page 395.254 (default=NONE) Specify the bit number of the coordination flag or enter NONE if no coordination flag is set.

Word/byte in the PLC to write the value of SIEMDIG1. Data block. The value read from the device will be stored in SIEMDIG1. 394 / FactoryLink Device Interfaces Using EDI Technology . Defaults to Siemens data type BIN. Data block in the PLC to write the value of SIEMDIG1.• • • • 18 | SIEMENS CP525 Configuring the Read/Write Information Table The following table provides sample entries for the Siemens 525 Read/Write Information table. Specifies the path to send the request. Field Table Name Tag Name Logical Station PLC Region Data Block Word/Byte Bit/Length Data Type Coordination Flag CPU Coordination Flag Byte Coordination Flag Bit Entry Description READ SIEMDIG1 0 DB 10 6 3 DW NONE NONE NONE Specifies the Read/Write table name. Bit/length of the value written.

You may choose to specify a Siemens PLC data type. release 05. By using the PLC data type BIN.SIEMENS CP525 | 18 Siemens CP525 Switches S IEMENS CP525 S WITCHES For information about setting Siemens CP525 switches. FactoryLink Data Types Siemens PLC Data Types Digital Analog Longana Float Message DIG INT2 INT4 FLT LOHI Each FactoryLink data type also has a range of valid Siemens PLC data types.4 of Siemens COM525 for CP524 and CP525 (S5-DOS). the Data Type DW defaults to BIN. (For compatibility with previous versions. Volume 1. each FactoryLink data type has a default Siemens PLC data type. you may specify the default entry in configuration table.) The following table shows the default conversions for each of the FactoryLink data types. The following tables show the FactoryLink data types and the corresponding Siemens PLC data types FactoryLink Device Interfaces Using EDI Technology / 395 . S IEMENS CP525 D ATA TYPES When you configure the Data Type field of the Siemens CP525 Read/Write Information table. refer to Section 3. order number 6ES5998-1DB21.

binary-coded decimal 396 / FactoryLink Device Interfaces Using EDI Technology . unsigned. unsigned. binary-coded decimal Converts the FactoryLink value to or from a 4-byte. three-digit. signed integer Converts the FactoryLink value to or from a 2-byte.• • • • 18 | SIEMENS CP525 Siemens CP525 Data Types Digital Conversion PLC Type Conversion DIG Single bit of a word or byte is read or written Analog Conversion PLC Type Conversion INT2 INT4 BCD3 BCD7 FLT BYTE Converts the FactoryLink value to or from a 2-byte. Siemens PLC floating-point (Valid only in byte PLC regions) Converts the FactoryLink value to or from a single unsigned byte (0 . unsigned. unsigned. signed integer Converts the FactoryLink value to or from a 4-byte signed integer Converts the FactoryLink value to or from a 2-byte.255) Longana Conversion PLC Type Conversion INT2 INT4 BCD3 BCD7 Converts the FactoryLink value to or from a 2-byte. seven-digit. signed integer Converts the FactoryLink value to or from a 4-byte. binary-coded decimal Converts the FactoryLink value to or from a four-digit. seven-digit. three-digit. binary-coded decimal Converts the FactoryLink value to or from a 4-byte.

SIEMENS CP525 | 18 Siemens CP525 Data Types PLC Type Conversion FLT BYTE Converts the FactoryLink value to or from a 4-byte Siemens PLC floating-point (Valid only in byte PLC regions) Converts the FactoryLink value to or from a single unsigned byte (0 . unsigned byte (0 . binary-coded decimal Converts the FactoryLink value to or from a 4-byte. unsigned.255) Message Conversion PLC Type Conversion HILO Consecutive bytes in the FactoryLink message tag are read or written to the PLC as a high-order (HI) byte followed by a low-order (LO) byte. binary-coded decimal Converts the FactoryLink value to or from a 4-byte. seven-digit. signed integer Converts the FactoryLink value to or from a 2-byte. signed integer Converts the FactoryLink value to or from a 4-byte. unsigned three-digit.255) Floating-Point Conversion PLC Type Conversion INT2 INT4 BCD3 BCD7 FLT BYTE Converts the FactoryLink value to or from a 2-byte. LOHI FactoryLink Device Interfaces Using EDI Technology / 397 . Consecutive bytes in the FactoryLink message tag are read or written to the PLC as a low-order (LO) byte followed by a high-order (HI) byte. Siemens PLC Floating-point (Valid only in byte PLC regions) Converts the FactoryLink value to or from a single.

data bits. Action: Contact Customer Support. if so configured. two individual codes appear within a string to indicate multiple error conditions. writes them to message or analog tags.• • • • 18 | SIEMENS CP525 Run-Time Application Messages R UN -TIME A PPLICATION M ESSAGES During EDI runtime. FactoryLink generates and displays messages for the General Electric protocol module on the Run-Time Manager screen and. For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. Action: Contact Customer Support. 398 / FactoryLink Device Interfaces Using EDI Technology . see Chapter 10. cable. In some cases. “Messages and Codes. 0001h Cause: Internal error. see “Configuring the Logical Station Control Table” on page 381. N represents significant digits and x represents digits not significant to the error. For information about configuring a message tag. etc. 0004h Cause: Internal error. 0002h Cause: Unable to successfully communicate with PLC. see “Configuring the Logical Station Information Table” on page 384. Action: Check line parameters (baud rate. 0003h Cause: Unable to receive response to read/write request. For information about configuring an analog tag. ER:xxxN is a single-digit format in which one digit represents a single error condition. Action: Check CP525 programming.” The ER:xxxN string in a message contains a single-digit error code.). CP525 programming.

FactoryLink Device Interfaces Using EDI Technology / 399 . Action: Contact Customer Support. Action: Refer to Siemens CP525 documentation. 0006h Cause: After retry count. received more or fewer bytes than requested in read request packet. Action: Contact Customer Support.SIEMENS CP525 | 18 Run-Time Application Messages XX05h Cause: Received error code XXh from Siemens PLC in response packet. 0007h Cause: Internal error.

• • • • 18 | SIEMENS CP525 Run-Time Application Messages 400 / FactoryLink Device Interfaces Using EDI Technology .

CP-1434 • Ethernet interface card over an Ethernet network Note: The Siemens Since H1 driver does not work on Microsoft Windows XP platforms. with one TSAP on each side of the communication link. Types of Communication On one side of the communication link. S IEMENS H1 C OMMUNICATIONS Communication in the Siemens H1 protocol module occurs between the Siemens Ethernet Interface and the Device Control Module (DCM) using logical entities called Transport Service Access Points (TSAPs). • S5 – the Read Active/Passive TSAP pair consists of a Fetch active TSAP in the DCM and a Fetch passive TSAP in the Siemens Ethernet Interface card.Chapter 19 • • • Siemens Sinec H1 This chapter contains information needed to set up and configure bidirectional communications between the FactoryLink real-time database and any Siemens Simatic S5 or S505 PLC. • S505 – the Read Active/Passive TSAP pair consists of a Read active TSAP in the DCM and a Read passive TSAP in the Siemens Ethernet Interface card. Each type of communication has an associated TSAP pair. • FactoryLink Device Interfaces Using EDI Technology / 401 . However. TSAPs are communication points that link the Siemens Ethernet Interface and the DCM. A DCM TSAP works with a Siemens Ethernet Interface TSAP. The DCM performs the following types of communication: • Solicited Reads – Block reads of data from the Siemens PLC to the real-time database. using one of the following interfaces: • CP-535. TSAPs work in pairs. this driver can be used on Windows 2000 platforms. the DCM performs three types of communication. CP-143 card • CP-1433. because Microsoft removed the DLC protocol stack from XP.

TSAP Pair Type of Communication Initiator of the Communication Siemens PLC Ethernet Interface DCM Type of Data Exchanged Solicited Reads/ Siemens Read Active/Passive Solicited Writes/ Siemens Write Active/Passive Unsolicited Reads/ Siemens Write Active/Passive FactoryLink Fetch passive (S5) Read passive (S505) Receive passive (S5) Write passive (S505) Send active Fetch active (S5) Block reads Read active (S505) Send active (S5) Write active (S505) Receive passive Block and exception writes Siemens PLCgenerated writes FactoryLink External Device 402 / FactoryLink Device Interfaces Using EDI Technology . The Write Active/Passive TSAP pair consists of a Write passive in the DCM and a Write active in the Siemens Ethernet Interface card. • S5 – the Write Active/Passive TSAP pair consists of a Send active TSAP in the DCM and a Receive passive TSAP in the Siemens Ethernet Interface card. • Unsolicited Reads S5 – Siemens PLC-generated writes sending data from the Siemens PLC to the real-time database. • S505 – the Write Active/Passive TSAP pair consists of a Write active TSAP in the DCM and a Write passive TSAP in the Siemens Ethernet Interface card. The Write Active/Passive TSAP pair consists of a Receive passive in the DCM and a Send active in the Siemens Ethernet Interface card.• • • • 19 | SIEMENS SINEC H1 Siemens H1 Communications • Solicited Writes – Block and exception writes of data from the real-time database to the Siemens PLC. The following table describes the relationships between the three types of communication performed by the DCM and the TSAP pairs. S505 – Siemens PLC-generated writes sending data from the Siemens PLC to the real-time database.

you must first obtain the following information: • The DCM FactoryLink platform Ethernet adapter address • The Siemens PLC Ethernet adapter address • The Remote TSAP ID • The Local TSAP ID Note The terms local and remote are relative to your configuration. These are Active only. FactoryLink Device Interfaces Using EDI Technology / 403 . see “Siemens H1 Adapter Display Utility (H1MPDISP)” on page 445. To define a TSAP pair. These are Passive only. designate the FactoryLink side of the communications link as local and the Siemens Ethernet Interface side as remote. When you configure the Siemens H1 tables. Describes the Siemens Interface coprocessor jobs that receive information from an external device. Send Receive Defining a TSAP Pair Each line you configure in the Siemens H1 Logical Station Information table corresponds to a specific Siemens Ethernet Interface on the LAN.SIEMENS SINEC H1 | 19 Siemens H1 Communications where: Active Passive Fetch Describes the Siemens Interface coprocessor jobs and denotes the initiator or master of the link. The information you configure in each line enables the Device Control Module to allocate TSAPs and to connect each DCM TSAP with its corresponding Siemens Ethernet Interface TSAP. You must program the Ethernet adapter address of the FactoryLink platform in the Siemens Ethernet Interface. Describes the Siemens Interface coprocessor jobs that transmit information to an external device. Describes the Siemens Interface coprocessor jobs that request information from an external device. Describes the Siemens Interface coprocessor jobs and denotes the receiver or slave of the link. These are either Active or Passive. For further information about the Ethernet address of the FactoryLink platform.

The following examples illustrate the TSAP IDs and their eight-character ASCII equivalents: TSAP ID 8-Character ASCII “1623” “1623^” “1623_” “12_4” “12_4” “0^1” “^^^^1623” “^^^^1623” “^^^1623^” “^^^^12^4” “^^^^12^4” “^^^^^0^1” Note: The “^” is a space and the “_” is a forced-space. the TSAP ID defaults to either: ____SSAA (COM535) or ____SS_AA (COM143) where “_” SS _S AA _A Is a space character in Siemens software programming displays Is the SSNR (card) number if two-digits Is the SSNR (card) number if one-digit Is the ANR (job) number if two-digits Is the ANR (card) number if one-digit TSAP IDs and ASCII Equivalents The EDI task processes the TSAP ID fields by space-padding-right-justifying the 8-byte string to the right-most non-space character. As long as the Device Control Module and the Siemens Ethernet Interface are programmed with corresponding values. fixed-length ASCII string. Depending on the version of Siemens programming software used.• • • • 19 | SIEMENS SINEC H1 Siemens H1 Communications The TSAP ID is an eight-character. The Siemens Ethernet Interface programming software defaults the TSAP ID based on the Ethernet Interface's SSNR (CP board number) and ANR (CP job number). 404 / FactoryLink Device Interfaces Using EDI Technology . these fields can be any eight-character ASCII string.

C ONFIGURING THE L OGICAL STATION C ONTROL TABLE Open the Logical Station Control table. to represent a particular communication path to a device.) FactoryLink Device Interfaces Using EDI Technology / 405 . the remaining fields of the Siemens H1 Logical Station Control table (except for the Status Message Tag field) control the system resources used by the Device Control Module (DCM) task. Valid Entry: previously defined logical port number (default=0) Ethernet Adapter Number Enter the Ethernet adapter installed in the FactoryLink system for use with this logical port. open Device Interfaces > Siemens Sinec H1. Valid Entry: 0 or 1 (default=0) At run time. you must complete the External Device Definition table. In your server application. Logical Port Enter a number. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. (The DCM task runs outside FactoryLink and provides the interface between the FactoryLink EDI task and the external device. For more information about the DCM task. defined in the External Device Definition table Logical Port column.SIEMENS SINEC H1 | 19 Accessing the Siemens H1 Tables A CCESSING THE S IEMENS H1 TABLES Note Before completing the protocol-specific Siemens H1 configuration tables. See “Identifying Protocol Types and Defining Logical Ports” on page 58” for details. see “Siemens H1 Communications” on page 401.

250 (default=30) Solicited Idle Disconnect Timeout (Seconds) Enter the amount of time in seconds a logical station’s solicited connections remain active without solicited transactions occurring. At startup. the DCM task allocates memory for the number of solicited tables specified in this field.100 (default=10) Number Unsolicited Buffers Enter the shared pool of memory available for all logical stations with configured unsolicited operations. Solicited operations to disconnected stations require additional overhead to reconnect 406 / FactoryLink Device Interfaces Using EDI Technology .100 (default=10) Maximum Concurrent Requests Enter the number of solicited requests (individual read or write transactions) on which the DCM task can operate simultaneously. Enter a number that is equal to or smaller than the Maximum Concurrent Requests. If you enter a number larger than the number specified in the Maximum Concurrent Requests field. Valid Entry: 5 .• • • • 19 | SIEMENS SINEC H1 Configuring the Logical Station Control Table Maximum Concurrent Tables Enter the number of tables configured to perform reads/writes on which the DCM task can operate simultaneously. Valid Entry: 5 . Valid Entry: 5 . The DCM has a structure similar to the solicited request for each concurrently active unsolicited write command received from the PLC transaction. Each of these solicited tables contains one or more solicited requests. In the DCM. Valid Entry: 5 . a block write table. Each request requires slightly over 4 kilobytes of memory.100 (default=10) Unsolicited Queue Size Enter the internal queue size of unsolicited write commands (number of tags on queue) received from the PLC awaiting formatting for the FactoryLink database. Valid Entry: 5 . Each buffer contains slightly over 4 kilobytes of memory. A table can be a block read table. you are using memory inefficiently.100 (default=10) Number Ethernet Buffers Enter the shared pool of DCM allocated buffers used by all logical stations to transmit or receive Ethernet packets. or an exception write entry in a Read/Write Control table. Each buffer is slightly over 1500 bytes in length. each connected logical station requires periodic processing to maintain the connection while no actual solicited transactions take place with the PLC.

Valid Entry: tag name Valid Data Type: message When the table is complete. In the DCM. Therefore. Valid Entry: 0 (never) . Define the data type (message) for any tag names displayed in the Tag Definition dialog box. set this time according to the needs of your application. Unsolicited operations to disconnected stations require additional overhead to reconnect before a transaction can take place.32767 (default=120) Unsolicited Idle Disconnect Timeout (Seconds) Enter the amount of time in seconds a logical station's unsolicited connections remain active without unsolicited transactions occurring. set this time according to the application. Valid Entry: 0 (never) . each connected logical station requires periodic processing to maintain the connection while no actual unsolicited transactions are taking place with the PLC. click the Save icon to validate the information. set the unsolicited idle disconnect timeout to 12 seconds or more (to keep the connection active) or less than 10 seconds (to disconnect).SIEMENS SINEC H1 | 19 Configuring the Logical Station Control Table before a transaction can take place. set this field to 12 seconds or more (to keep the connection active) or less than 10 seconds (to disconnect). when reading from a station on a 10. For example. if the PLC sends messages every 10 to 11 seconds). when reading from a station on a 10to 11-second trigger.to 11-second trigger (that is.32767 (default=300) Status Msg Tag (Optional) Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. For example. FactoryLink Device Interfaces Using EDI Technology / 407 . The following table provides sample entries for the Siemens H1 Logical Station Control table: Field Logical Port Ethernet Adapter Number Entry Description 0 0 Communications path specified for this configuration. Number of the Ethernet adapter used in this configuration. Therefore.

The DCM can operate 10 solicited requests at the same time.• • • • 19 | SIEMENS SINEC H1 Configuring the Logical Station Control Table Field Maximum Concurrent Tables Maximum Concurrent Requests Number Unsolicited Buffers Unsolicited Queue Size Entry Description 10 10 10 Number Ethernet Buffers Solicited Idle Disconnect Timeout (Seconds) Unsolicited Idle Disconnect Timeout (Seconds) Status Msg Tag 30 120 300 H1MP_LPORT0_ MSG The DCM can operate 10 solicited tables at the same time. The EDI task writes errors for this logical port 0 to this message tag. Thirty DCM allocated buffers are configured for use by all logical stations for Ethernet packets. Ten tags will be on queue from unsolicited requests awaiting formatting in the FactoryLink real-time database. Ten buffers will be used for storage of data from unsolicited requests for all the logical stations. The logical station’s solicited connection remains active for 120 seconds without solicited transactions occurring. 408 / FactoryLink Device Interfaces Using EDI Technology . The logical station’s unsolicited connections remain active for 300 seconds without unsolicited transactions occurring.

Later. this number will identify the device to or from which data is to be sent or received. FactoryLink Device Interfaces Using EDI Technology / 409 .SIEMENS SINEC H1 | 19 Configuring the Logical Station Information Table C ONFIGURING THE L OGICAL STATION I NFORMATION TABLE From the Logical Station Control table. A logical station represents the combination of a logical port with a physical station. select the row for the logical port you are configuring and open the Logical Station Information table. In a read or write table. Assign a unique number to each device communicating through this logical port. Error/Status Tag Name (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station). You can animate output-text objects to display the codes stored in an Error/Status Tag Name tag on a graphics screen. Valid Entry: previously defined logical station number PLC Type Type of Siemens device associated with this logical station. you will enter this logical station number in a read or write table to represent the device defined in this row. Complete a row for each device to communicate through this logical port. Valid Entry: tag name Valid Data Type: analog Logical Station Enter a number to identify the logical station to which the information in this row pertains. S5 (Default) Siemens S5 series PLC with either CP-535 or CP-143 S505 Siemens 505 family stations with the following Ethernet cards installed: CP-1433 CP-1434 Remote Adapter Address (hexadecimal) Enter the 6-byte (12-nibble) Ethernet address of the Siemens H1 Ethernet defined on this line.

Valid Entry: any 8-character ASCII string Solicited Wr Local SEND TSAP ID Enter the TSAP ID for the send active TSAP provided by the Device Control Module with which the DCM communicates for solicited write operations on this logical station. A value of 1 (ON) indicates connection.• • • • 19 | SIEMENS SINEC H1 Configuring the Logical Station Information Table Valid Entry: six address bytes (set by the Ethernet) 080006 -----01 -0 000 --Byte 5 (right nibble) and Byte 6 Hexadecimal number of each module Byte 5 (left nibble) systems identifier for Siemens system each position Byte 4 Siemens area UBE Byte 1-3 number for Siemens Solicited Rd Remote FCHP TSAP ID Enter the TSAP ID for the Fetch Passive TSAP on the Siemens Interface Card with which the Device Control Module communicates for solicited read operations on this logical station. Valid Entry: tag name Valid Data Type: digital Solicited Wr Remote RECV TSAP ID Enter the TSAP ID for the receive passive TSAP on the Siemens Interface Card with which the DCM communicates for solicited write operations on this logical station. Valid Entry: any 8-character ASCII string Solicited Rd Local FCHA TSAP ID Enter the TSAP ID for the Fetch Active TSAP provided by the Device Control Module with which the DCM communicates for solicited read operations on this logical station. Valid Entry: any 8-character ASCII string 410 / FactoryLink Device Interfaces Using EDI Technology . A value of 0 (OFF) indicates no connection. Valid Entry: any 8-character ASCII string Solicited Rd Station Status Tag Name (Optional) Enter the name of a tag that reports the connection status of the two TSAPs for solicited (block) reads.

The following table provides sample entries for the Siemens H1 Logical Station Information table: Field Error Status Tag Name Logical Station Entry Description H1MP_STATION0_ STATUS 0 (Optional) Errors for this logical station are written to this analog tag. Valid Entry: any 8-character ASCII string Unsolicited Rd Local RECV TSAP ID Enter the TSAP ID for the Receive Passive TSAP provided by the DCM with which the DCM communicates for unsolicited read operations on this logical station. Valid Entry: any 8-character ASCII string Unsolicited Rd Station Status Tag Name (Optional) Enter the name of a tag that reports the connection status of the two TSAPs for unsolicited reads. click the Save icon to validate the information. A value of 1 (ON) indicates connection. Valid Entry: tag name Valid Data Type: digital Unsolicited Rd Remote SEND TSAP ID Enter the TSAP ID for the Send Active TSAP on the Siemens Interface Card with which the DCM communicates for unsolicited read operations on this logical station. A value of 0 (OFF) indicates no connection.SIEMENS SINEC H1 | 19 Configuring the Logical Station Information Table Solicited Wr Station Status Tag Name (Optional) Enter the name of a tag that reports the connection status of the two TSAPs for solicited (block and exception) writes. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box. Valid Entry: tag name Valid Data Type: digital Comment (Optional) Enter reference information about this logical station. A value of 0 (OFF) indicates no connection. A value of 1 (ON) indicates connection. Communications path for the communication. Valid Entry: alphanumeric string of up to 21 characters When the table is complete. FactoryLink Device Interfaces Using EDI Technology / 411 .

ANR 10. ANR 7. (Optional) Digital tag containing the status of the TSAP for solicited read operations for logical station 1. Has a value of 0 (OFF) when disconnected and 1 (ON) when connected. (Optional) Information about this logical station. Fetch Passive TSAP SSNR 8. Fetch Active TSAP SSNR 8. ANR 5. ANR 4. Receive Passive TSAP SSNR 8. Send Active TSAP SSNR 8. Solicited Wr Remote RECV TSAP ID Solicited Wr Local SEND TSAP ID Solicited Wr Station Status Tag Name 84 82 H1MP_LS0_W Unsolicited Rd Remote SEND TSAP ID Unsolicited Rd Local SEND TSAP ID Unsolicited Rd Station Status Tag Name 87 8 10 H1MP_LS0_U Comment 412 / FactoryLink Device Interfaces Using EDI Technology . (Optional) Digital tag containing the status of the TSAP for unsolicited read operations for logical station 1. (Optional) Digital tag containing the status of the TSAP for solicited write operations for logical station 1. ANR 2. ANR 1. Has a value of 0 (OFF) when disconnected and 1 (ON) when connected. Send Active TSAP SSNR 8. Receive Passive SSNR 8.• • • • 19 | SIEMENS SINEC H1 Configuring the Logical Station Information Table Field Remote Adapter Address (hexadecimal) Solicited Rd Remote FCHP TSAP ID Solicited Rd Local FCHA TSAP ID Solicited Rd Station Status Tag Name Entry Description 0800006010001 85 81 H1MP_LS0_R Remote Ethernet address (in hexadecimal). Has a value of 0 (OFF) when disconnected and 1 (ON) when connected.

regardless of whether the current value matches the new value. Tip See “Application Design Tips and Techniques” on page 127 for information about triggering schemes using tags defined in this table. the change-status indicator is unaffected. accept the default of NO. If a different value is being stored the tag. the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. If you enter YES. yes. If you enter FORCE. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). Table Name Assign a name to this read or write request. it will overwrite the current value and the tag’s change-status indicator will be set to 1 (ON). Complete a row for each read or write table.SIEMENS SINEC H1 | 19 Configuring the Read/Write Control Table C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Open the Read/Write Control table. EDI will interpret this operation as an unsolicited read and emulate the device’s addressing structure based on entries you make in the Read/Write Information table. Try to make the table name reflective of the operation it represents. You can define as many tables as available memory allows. Define one request (table) per line and do not include spaces in the name. the data is stored in the specified tag and the change-status indicator is automatically set to 1. Valid Entry: no. The incoming data will be stored in the real-time database as specified in this field. the incoming data will be stored in the tag represented by the tag name specified in the Read/Write Information table. If this is an unsolicited read operation. If this is a triggered read or a block write table. force (default=no) FactoryLink Device Interfaces Using EDI Technology / 413 . Valid Entry: alphanumeric string of up to 16 characters Unsolicited Read For EDI to interpret this operation as a triggered block read or as a write operation. however. enter YES or FORCE. If the current value of the tag is equal to the new value.

Block Read Complete. If this is an unsolicited read or a write operation. The highest priority is 1. The default is 1. enter YES. The Block Read Trigger. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). For EDI to interpret this operation as an exception write and write tag values to the device only when those values change. and Block Read State tags apply only to triggered read operations. Do not define these tags 414 / FactoryLink Device Interfaces Using EDI Technology . accept the default of NO. Block Read Priority If this is a block read operation. accept the default of 1. This number influences the order in which the EDI task handles the queuing of block read requests. In an exception write. Valid Entry: no.• • • • 19 | SIEMENS SINEC H1 Configuring the Read/Write Control Table Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. enter a number to indicate the priority of this table. This field defaults to 1 regardless of whether the operation being defined is a block read. an internal change-status indicator within the tag containing the data to be written prompts the write operation. relative to other read operations. Defining tags that change value frequently as exception writes can slow down communications or result in an error message. If EDI receives two requests at the same time. Block Read Disable. Any tag specified will be written to the device in its own packet (message) each time it changes. yes (default=no) Tip Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. EDI writes this tag’s value to the device. it processes the request with the highest priority first. Valid Entry: 1 .4 (default=1) Note for unsolicited read operations or for write operations.

If you need a digital tag to indicate when this operation is complete. even when the block read trigger is set to 1. Valid Entry: tag name Valid Data Type: digital FactoryLink Device Interfaces Using EDI Technology / 415 . Valid Entry: tag name Valid Data Type: digital Block Read Complete If this is an unsolicited read or a write operation. To reenable a block read table that is disabled. Do not use this tag when more than one logical port is specified in a single table. If this is a triggered read operation. If this is a triggered read operation. The triggering cycle will cease upon disabling. Valid Entry: tag name Valid Data Type: digital Tip The Block Read Disable tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered. Block Read Disable If this is an unsolicited read or a write operation. the addresses are read. this field is optional. set this tag back to 0 (OFF). the read operation is not executed. enter a tag name. ignore this field. When this tag’s value is forced to 1 (ON). the Block Read Trigger tag must be toggled or forced to 1. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. ignore this field. this field is optional. To reenable a cascaded loop or a self-triggered read table. Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. If this is a triggered read operation. the complete tag is forced to 1 again. See “Application Design Tips and Techniques” on page 127 for details.SIEMENS SINEC H1 | 19 Configuring the Read/Write Control Table Block Read Trigger If this is an unsolicited read or a write operation. however. ignore this field. When this tag’s value is forced to 1 (ON). enter a tag name. If you need a digital tag to disable a block read of the tags specified in this table. this field is required. This tag is forced to 1 (ON) at startup.

Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. While the table is being processed. Block Write Disable. it processes the request with the highest priority first. When this tag’s value is forced to 1 (ON). this field is required. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. If EDI receives two requests at the same time. Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. Do not define these tags for read operations. Valid Entry: tag name Valid Data Type: digital 416 / FactoryLink Device Interfaces Using EDI Technology . If this is a triggered read operation. ignore this field. this field is optional. ignore this field. accept the default of 1.• • • • 19 | SIEMENS SINEC H1 Configuring the Read/Write Control Table Block Read State If this is an unsolicited read or a write operation. and Block Write State tags apply only to write operations. If this is a read operation. This field defaults to 1 regardless of whether the operation being defined is a block or exception write. the tag is set to 0 (OFF). the state tag is forced back to 1. This tag is forced to 1 (ON) at startup. Valid Entry: 1 . enter a tag name. This number influences the order in which the EDI task handles the queuing of write requests. The highest priority is 1. Valid Entry: tag name Valid Data Type: digital Block Write Priority If this is a block or exception write operation.4 (default=1) Note The Block Write Trigger. enter a number to indicate the priority of this table. If this is a block write table or an exception write table you plan to periodically disable. relative to other write operations. Block Write Complete. The default is 1. If you need a digital tag to indicate the state of this operation (in progress or complete). FactoryLink writes the values.

enter a tag name. If this is a block write table or an exception write table you plan to periodically disable. Do not use this tag when more than one logical port is specified in a single table. FactoryLink Device Interfaces Using EDI Technology / 417 . See “Application Design Tips and Techniques” on page 127 for further details. If you need a digital tag to indicate when this operation is complete. ignore this field. This tag is forced to 1 (ON) at startup. enter a tag name. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. this field is optional. the Block Write Trigger tag must be toggled or forced to 1. Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. this field is optional. If you need a digital tag to indicate the state of this operation (in progress or complete). To reenable a cascaded loop or a self-triggered write table. even when the block write trigger is set to 1. however. the complete tag is forced to 1 again. After the data defined in this table’s Read/Write Information table is written to the device. If this is a block write operation. To reenable a block write table that is disabled. If this is a block write table. ignore this field. Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. set this tag back to 0 (OFF). The triggering cycle will cease upon disabling. ignore this field. this field is optional. When this tag’s value is forced to 1 (ON).SIEMENS SINEC H1 | 19 Configuring the Read/Write Control Table Tip The Block Write Disable tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. the write operation is not executed. Valid Entry: tag name Valid Data Type: digital Block Write Complete If this is a read or exception write operation. This tag is forced to 1 (ON) at startup.

the tag is set to 0 (OFF). Valid Entry: tag name Valid Data Type: digital When the table is complete. The block read priority. After the data defined in this table’s Read/Write Information table is written to the device. which is set automatically if you do not enter a value. and does not process the READ table. When the value of H1MP_READ_TRIGGER is 1. FactoryLink disregards the trigger tag. is set to the default of 1. The following table provides sample entries for the Siemens H1 Read/Write Control table: Column Table Name Unsolicited Read Exception Write Block Read Priority Entry Description READ NO NO 1 The name of this table is READ. the state tag is forced back to 1. Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. the highest priority. click the Save icon to validate the information. When the value of H1MP_READ_DISABLE is 1. Block Read Trigger H1MP_READ_TRIGGER Block Read Disable H1MP_READ_DISABLE 418 / FactoryLink Device Interfaces Using EDI Technology . Do not use this tag when more than one logical port is specified in a single table. This is not an exception write table. This is not an unsolicited read table. FactoryLink reads the configured address and writes its value to the tag configured for this table (in the Read/Write Information table).• • • • 19 | SIEMENS SINEC H1 Configuring the Read/Write Control Table While the table is being processed. H1MP_READ_TRIGGER.

During the read operation. the tags specific to write requests are not defined. H1MP_READ_STATE Once the data is read and stored in the tag defined to receive it.SIEMENS SINEC H1 | 19 Configuring the Read/Write Control Table Column Block Read Complete Entry Description H1MP_READ_COMPLETE Once the data is read and stored in the tag defined (in the Read/Write Information table) to receive it. Since this is a read table. H1MP_READ_STATE is set to 0. The write priority for this table is set to 1 by default. FactoryLink forces a value of 1 to H1MP_READ_COMPLETE. Block Read State Block Write Priority Block Write Trigger Block Write Complete Block Write Disable Block Write State 1 FactoryLink Device Interfaces Using EDI Technology / 419 . FactoryLink forces a value of 1 to H1MP_READ_STATE.

For a write table. see “Logical Station Commands” on page 429. For S505 stations. enter LSCMD. enter the region index number. or DE regions. select the row for the table you are configuring and open the Read/Write Information table. DX. specify a tag name for a tag in which FactoryLink will store the data read from the device. Tag Name For a read table. analog. For valid data regions. Region Index For DB. For a Read Table – add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes. Valid Entry: previously defined logical station number Data Region Enter the PLC region to be read or written. For a Write Table – add a table entry for each tag to be written when the operation executes. For further information. specify a tag name for a tag containing a value to be written to the device. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. float. Valid Entry: tag name Valid Data Type: digital. see the S5 and S505 Data Regions tables below. longana. For valid entries. Data regions that accept LSCMD and logical station variables are marked with an asterisk (*) in the data regions tables listed under the Region Index field. message Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written.• • • • 19 | SIEMENS SINEC H1 Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. see the Data Region tables listed under the Region Index field. 420 / FactoryLink Device Interfaces Using EDI Technology . enter the first index number. For special DCM commands for a specific logical station.

The S5 and S05 Data Regions tables (below) describe the data regions supported by the Siemens H1 protocol module. enter a nonzero negative number from -1 to -8. S5 Data Regions: Key Description Tag Size (Bytes) Max Region Index Max Tag Number Default Type Read Only CB DB DE DX EB FB IB OB QB PB TB RS Counters Data Block External Data Block Expanded Data Block Expanded Peripheral Flags Input Image Output Image Output Image Peripheral Timers System Data Area 2 2 2 2 1 1 1 1 1 1 2 2 0 255* 255* 255* 0 0 0 0 0 0 0 0 255 2047 2047 2047 255 255 127 127 127 255 255 511 BIN BIN BIN BIN BYTE BYTE BYTE BYTE BYTE BYTE BIN BIN No No No No No No No No No No No No Note: Max Region Index values with an asterisk (*) indicate data regions that accept logical station variables. FactoryLink Device Interfaces Using EDI Technology / 421 .SIEMENS SINEC H1 | 19 Configuring the Read/Write Information Table For regions that specify a logical station variable which you can modify at run time using a logical station command. See “Logical Station Commands” on page 429 for more information.

AACK AADB ACFH ACFL AERR AHA AHHA ALA ALLA AODA 422 / FactoryLink Device Interfaces Using EDI Technology .• • • • 19 | SIEMENS SINEC H1 Configuring the Read/Write Information Table S505 Data Regions Key Description Tag Size (Bytes) Max Region Index Max Tag Number Default Type Read Only Analog Alarm Ack Flags 2 0 65535* INT2 No Alarm Deadband 4 0 65535* FLT No High Word Alarm C-Flag 2 0 65535* INT2 No Low Word Alarm C-Flag 2 0 65535* INT2 No Error 4 0 65535* FLT Yes High Alarm Limit 4 0 65535* FLT No High-High Alarm Limit 4 0 65535* FLT No Low Alarm Limit 4 0 65535* FLT No Low-Low Alarm Limit 4 0 65535* FLT No Orange Deviation Alarm 4 0 65535* FLT No Limit APV Process Variable 4 0 65535* FLT No APVH PV High Limit 4 0 65535* FLT No APVL PV Low Limit 4 0 65535* FLT No ARCA Rate of Change Alarm Limit 4 0 65535* FLT No ASP Setpoint 4 0 65535* FLT No ASPH Setpoint High Limit 4 0 65535* FLT No ASPL Setpoint Low Limit 4 0 65535* FLT No ATS Sample Rate in Seconds 4 0 65535* FLT No AVF V-Flags 2 0 65535* BIN Yes AYDA Yellow Deviation Alarm 4 0 65535* FLT No Limit C Control Register Boo1 0 16383 BIN No DCC Drum Current Count 4 255* 255 BIN Yes DCP Drum Count Preset 2 255* 255 INT2 No Note: Max Region Index values and Max Tag Numbers with an asterisk (*) indicate data regions that accept logical station variables.

SIEMENS SINEC H1 | 19 Configuring the Read/Write Information Table Key Description Tag Size (Bytes) Max Region Index Max Tag Number Default Type Read Only Drum Step Current 2 255* 255 INT2 No Drum Step Preset 2 255* 255 INT2 No G (Local App global 2 0 65535 INT2 No Variables) GA G (App A global Variables) 2 0 65535 INT2 No GB B (App B global Variables) 2 0 65535 INT2 No GC G (App C global Variables) 2 0 65535 INT2 No GD G (App D global Variables) 2 0 65535 INT2 No GE G (App E global Variables) 2 0 65535 INT2 No GF G (App F global Variables) 2 0 65535 INT2 No GG G (App G global Variables) 2 0 65535 INT2 No GH G (App H global Variables) 2 0 65535 INT2 No GI G (App I global Variables) 2 0 65535 INT2 No GJ G (App J global Variables) 2 0 65535 INT2 No GK G (App K global Variables) 2 0 65535 INT2 No GL G (App L global Variables) 2 0 65535 INT2 No GM G (App M global Variables) 2 0 65535 INT2 No GN G (App N global Variables) 2 0 65535 INT2 No GO G (App O global Variables) 2 0 65535 INT2 No GP G (App P global Variables) 2 0 65535 INT2 No GQ G (App Q global Variables) 2 0 65535 INT2 No GR G (App R global Variables) 2 0 65535 INT2 No GS G (App S global Variables) 2 0 65535 INT2 No GT G (App T global Variables) 2 0 65535 INT2 No GU G (App U global Variables) 2 0 65535 INT2 No GV G (App V global Variables) 2 0 65535 INT2 No Note: Max Region Index values and Max Tag Numbers with an asterisk (*) indicate data regions that accept logical station variables. DSC DSP G FactoryLink Device Interfaces Using EDI Technology / 423 .

GW GX GY GZ K LACK 424 / FactoryLink Device Interfaces Using EDI Technology .• • • • 19 | SIEMENS SINEC H1 Configuring the Read/Write Information Table Key Description Tag Size (Bytes) Max Region Index Max Tag Number Default Type Read Only G (App W global Variables) 2 0 65535 INT2 No G (App X global Variables) 2 0 65535 INT2 No G (App Y global Variables) 2 0 65535 INT2 No G (App Z global Variables) 2 0 65535 INT2 No Constant 2 0 16777215 INT2 No 2 0 65535* INT2 No Loop Alarm Acknowledge Flags LADB Alarm Deadband 4 0 65535* FLT No LCFH High Word Loop C-Flags 2 0 65535* INT2 No LCFL Low Word Loop C-Flags 2 0 65535* INT2 No LERR Error 4 0 65535* FLT Yes LHA High Alarm Limit 4 0 65535* FLT No LHHA High-High Alarm Limit 4 0 65535* FLT No LKC Gain 4 0 65535* FLT No LKD Derivative Gain Limiting 4 0 65535* FLT No Coefficient LLA Low Alarm Limit 4 0 65535* FLT No LLLA Low-Low Alarm Limit 4 0 65535* FLT No LMN Output (percent) 4 0 65535* FLT No LMX Bias 4 0 65535* FLT No LODA Orange Deviation Alarm 4 0 65535* FLT No Limit LPV Process Variable 4 0 65535* FLT No LPVH PV High Limit 4 0 65535* FLT No LPVL PV Low Limit 4 0 65535* FLT No LRCA Rate of Change Alarm Limit 4 0 65535* FLT No Note: Max Region Index values and Max Tag Numbers with an asterisk (*) indicate data regions that accept logical station variables.

Region Index. or a floating-point-number in floating-point-regions.SIEMENS SINEC H1 | 19 Configuring the Read/Write Information Table Key Description Tag Size (Bytes) Max Region Index Max Tag Number Default Type Read Only RAMP/SOAK Status Flags 2 0 65535* BIN Yes RAMP/SOAK Step Number 2 0 65535* INT2 No Setpoint 4 0 65535* FLT No Setpoint High Limit 4 0 65535* FLT No Setpoint Low Limit 4 0 65535* FLT No Rate Time (minutes) 4 0 65535* FLT No Reset Time (minutes) 4 0 65535* FLT No Sample Rate (seconds) 4 0 65535* FLT No V-Flags 2 0 65535* BIN No Yellow Deviation Alarm 4 0 65535* FLT No Limit STW System Status Words 2 0 65535 BIN No TCC Timer/Counter Current 2 0 65535 BCD4 No TCP Timer/Counter Preset 2 0 65535 BCD4 No V Variable Memory 2 0 16777215 INT2 No WX Word Input 2 0 65535 INT2 No WY Word Output 2 0 65535 INT2 No X Discrete Input Boo1 0 16383 BIN No Y Discrete Output Boo1 0 16383 BIN No Note: Max Region Index values and Max Tag Numbers with an asterisk (*) indicate data regions that accept logical station variables. a byte-number in byte-regions. see the data region tables in the description for the previous field. Valid Entry: For valid data regions. a word-number in word-regions. FactoryLink Device Interfaces Using EDI Technology / 425 . Tag LRSF LRSN LSP LSPH LSPL LTD LTI LTS LVF LYDA Enter the tag in the data region to be read or written: a bit-number in bit-regions.

DIG The bit specified to be read or written to or from a FactoryLink tag. INT4 4-byte signed integer. peripheral 1 . BCD7 4-byte. For digital tags – the bit to be read or written.32 (S505) Double word (4 byte) tag regions 0 .8 (S505) Byte regions 1 . FLT 4-byte Siemens Floating Point Representation.127 Word regions: message length in words 1 .63 (S505) Double word region message length PLC Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. 3-digit signed Binary Coded Decimal in the high-order nibble. timers 1 .255 Byte regions: message length in bytes 1 . PLC regions. BYTE (Use with PLC byte-regions only) 1-byte unsigned integer. 426 / FactoryLink Device Interfaces Using EDI Technology . and PLC data types.7 (S5) Byte regions: flags. For more information about valid combinations of FactoryLink data types.• • • • 19 | SIEMENS SINEC H1 Configuring the Read/Write Information Table Bit or Length (Use with digital or message tags only) Enter the bit or length in the PLC the Siemens H1 protocol module reads. INT2 2-byte signed integer. counters. timers 1 .16 (S505) Word regions: data block. 7-digit signed Binary Coded Decimal in the high-order nibble. The bit or length denotes the number of PLC tags to place in the message. output.15 (S5) Word regions: data block. For message tags – the message length to be read or written. BIN Default conversion based on the type of FactoryLink tag. 0 . input. counters. see “Siemens H1 Data Types” on page 441. BCD3 2-byte.

UINT2 2-byte unsigned integer. see “Siemens H1 Data Types” on page 441. LOHI A character string low-order byte followed by a high-order byte. FactoryLink Device Interfaces Using EDI Technology / 427 . UINT4 4-byte unsigned integer. When the table is complete. click the Save icon to validate the information. DEF The default PLC data type for the data region. Define the data type (digital.SIEMENS SINEC H1 | 19 Configuring the Read/Write Information Table HILO A character-string high-order byte followed by a low-order byte. Four-bytes to or from the communication packet will be transferred to or from the highest 4-bytes (in memory) of the FactoryLink tag. analog. TRNS4 Transparent 4-byte entity. TRNS2 Transparent 2-byte entity. Any additional space in the tag will be zeroed on reads and ignored on writes. or floating-point) for any tag names displayed in the Tag Definition dialog box. BCD4 Two bytes containing four Binary Coded Decimal (BCD) digits. long analog. For definitions of the default types by data region. Two-bytes to or from the communication packet will be transferred to or from the highest 2-bytes (in memory) of the FactoryLink tag. Any additional space in the tag will be zeroed on reads and ignored on writes.

428 / FactoryLink Device Interfaces Using EDI Technology .• • • • 19 | SIEMENS SINEC H1 Configuring the Read/Write Information Table The following table provides sample entries for the Siemens H1 Read/Write Information table: Field Table Name Tag Name Entry Description READ The table name defined in the Read/Write Control table is displayed. FactoryLink processes the table. Logical Station PLC Region Region Index Tag Bit or Length PLC Data Type FB 100 3 DIG The data being read from the device is digital. H1MPDIG1 When the READ table is triggered by H1MP_READ_TRIGGER (defined in the Read/Write Control table). PLC region that is being read. 0 The value stored in this tag is read from the General Electric device configured as logical station 0. The value read from the device is stored in H1MPDIG1.

true) Deactivate (reset. • Set Remote Parameters – reconfigures information in the Logical Station Information table so a single logical station can access multiple remote stations. This command is valid only in exception write tables. To specify these commands in the Siemens H1 Logical Station Information table. Activate/Deactivate Station Command At runtime. 0. This command is valid only in block write tables. the following command activates or deactivates the logical station. • Set Logical Station Variables – provides flexible indexing that allows you to access multiple data regions within a PLC by changing a logical station variable referenced by the Region Index field or tag in a Read/Write table. 1.999 (station to activate or deactivate) LSCMD 1 Not applicable Not applicable Not applicable FactoryLink Device Interfaces Using EDI Technology / 429 . LSCMD (logical station command).SIEMENS SINEC H1 | 19 Logical Station Commands L OGICAL STATION C OMMANDS The Siemens H1 protocol module supports the following run-time logical station commands: • Activate/Deactivate Station – activates or deactivates the logical station and stops or resumes operation of a specified logical station. For other information about the PLC data region. see “Configuring the Read/Write Information Table” on page 420. enter the following information in the Siemens H1 Read/Write Information table: Field Name Tag Name Entry Logical Station PLC Region Data Block Word or Byte Bit or Length PLC Data Type Digital tag containing the desired station state. either: Activate (set. To configure this command. false) 0 . use the special PLC data region.

If you change remote physical stations of different device types (such as redefining an S5 logical station as an S505 physical station or an S505 logical station as an S5 physical station).• • • • 19 | SIEMENS SINEC H1 Logical Station Commands Active/inactive Status At runtime. disconnects all TSAPs for that logical station. • During the transition between active and inactive. 430 / FactoryLink Device Interfaces Using EDI Technology . Note Use the Set Remote Parameters command only when changing the parameters of remote physical stations of the same device type. The EDI task does support nor check for dissimilar device-type changes. the logical station aborts any new or pending solicited request. Set Remote Parameters Command To allow a single logical station access to multiple remote stations. Once the command is complete. undesirable results may occur in your server application. configure information in the Siemens H1 Logical Station Information table using the Set Remote Parameters command. and handles the transition from inactive to active in the same way as it handles recovery from a disconnected station. While processing a Set Remote Parameters command. the status of each logical station is either active or inactive. • Inactive logical stations abort solicited operations and reject any attempts by a remote station to connect. the Siemens H1 protocol module reactivates the logical station. The following conditions define the status of each logical station: • Active logical stations (set at program initiation) respond to solicited or remote station requests. the Siemens H1 protocol module deactivates the logical station.

enter the following information in the Siemens H1 Read/Write Information table: Field Name Tag Name Logical Station PLC Region Region Index Tag Bit or Length PLC Data Type Entry Message tag 0 .SIEMENS SINEC H1 | 19 Logical Station Commands Configuring the Set Remote Parameters Command To set the logical station remote parameters. Each ASCII string in the message tag is separated by a semicolon.999 (logical station to reconfigure set parameters) LSCMD 2 Not applicable Not applicable Not applicable If a block write table with the Set Remote Parameters command contains any other commands. FactoryLink Device Interfaces Using EDI Technology / 431 . Each field in the Logical Station Information table is represented in the message tag by an ASCII string. When reconfiguring the Logical Station Information table using this message tag. For information about row errors. see “Set Logical Station Commands and Row Errors” on page 439. you only specify the fields you want to change. If one of the Logical Station Information fields is unchanged. This message tag is used to reconfigure the logical station at run time. Format The message tag you configured as a Set Remote Parameters command in the Siemens H1 Read/Write Information table contains an ASCII representation of the Siemens Logical Station Information table. a semicolon place holder must be used in the Set Remote Parameters command message tag. see “Siemens H1 Communications” on page 401. When reconfiguring the Logical Station Information table using the Set Remote Parameters command. a row error may occur.

RMT_SEND. LCL_REC . Is the hexadecimal remote adapter address of the Siemens H1 Ethernet Is the Solicited Rd Remote FCHP TSAP ID Is the Solicited Rd Local FCHA ID TSAP ID Is the Solicited Wr Remote RECV TSAP ID Is the Solicited Wr Local SEND TSAP ID Is the Unsolicited Rd Remote SEND TSAP ID Is the Unsolicited Rd Local RECV TSAP ID (Semicolon) Terminates the message string Delimit each remote parameter field with a semicolon. Field Name Remote Adapter Address Solicited Rd Remote FCHP TSAP ID Solicited Rd Local FCHA TSAP ID Solicited Wr Remote RECV TSAP ID Solicited Wr Local SEND TSAP ID Unsolicited Rd Remote SEND TSAP ID Unsolicited Rd Local RECV TSAP ID Description Enter 12-hexadecimal digits Any 8-character ASCII string Any 8-character ASCII string Any 8-character ASCII string Any 8-character ASCII string Any 8-character ASCII string Any 8-character ASCII string Example 1: Message Tag The following is a Set Remote Parameters message tag example: 080006010005. 432 / FactoryLink Device Interfaces Using EDI Technology .• • • • 19 | SIEMENS SINEC H1 Logical Station Commands Always construct the message tag to be the following ASCII representation of the Siemens H1 Logical Station Information table fields. RMT_RECV.LCL_FCHA.RMT_SEND. LCL_FCH. RMT_FCHP. LCL_SEND. where 080006010005.RMT_FCHP.LCL_REC.RMT_RECV.LCL_SEND.

read/write table 2 is configured to read ten 2-byte integers from an external PLC.SIEMENS SINEC H1 | 19 Logical Station Commands Example 2: Message Tag Using the Current TSAP ID The Set Remote Parameters command is configured as a message tag. you can trigger table 1 which will override the Siemens Logical Station Information table fields. allowing you access to different PLCs at runtime without configuring separate Read/Write and Logical Station tables. . the following message tag changes the Ethernet address of a logical station but keeps the current TSAP ID (does not change the TSAP IDs): 80006010005... In this example.. Then. where 080006010005 .. You must always construct the message tag to be an ASCII representation of the Siemens Logical Station Information table. you only need to specify the fields that change. before table 1 is triggered. Set Remote Parameters.. In Siemens read/write table 1.. FactoryLink Device Interfaces Using EDI Technology / 433 . the message tag set_param_msg is configured to be logical station command. Is the hexadecimal remote adapter address of the Siemens H1 Ethernet (Six semicolons) Are placeholders for the unchanged fields in the Siemens Logical Station Information table (Semicolon) Terminates the message string Set Remote Parameters Example The Siemens H1MP allows you to use logical station commands to change the physical station address within the logical station at runtime using the Set Remote Parameters command. Change this tag at runtime to represent the new field values for the Siemens Logical Station Information table.. If one of the Siemens Logical Station Information table fields remains unchanged. The logical station number is configured as 1.. a semicolon place holder must be used in the Set Remote Parameters command message tag.. The value of each field is separated by a semicolon. For example.. When reconfiguring the Siemens Logical Station Information table using the Set Remote Parameters command. This means you can construct set_param_msg to alter the physical station address inside logical station 1..

table 1 declares the tag set_param_msg as a Set Remote Parameters command (LSCMD 2) .• • • • 19 | SIEMENS SINEC H1 Logical Station Commands Protocol Module Base Module set_param_msg CML To take advantage of the H1MP protocol module’s Set Remote Parameters command. 434 / FactoryLink Device Interfaces Using EDI Technology . you must configure at least two read/write tables. In this example.

enter the following information in the Siemens H1 Read/Write Information table: Field Name Tag Name Logical Station PLC Region Region Index Tag. The set_param_msg tag in table 1 is configured to change the physical station configured as logical station 1 at run time.999 LSCMD 3 Not applicable FactoryLink Device Interfaces Using EDI Technology / 435 . PLC Data Type Entry Message tag 0 . Set Logical Station Variables Command The Set Logical Station Variables command provides flexible indexing that allows you to access multiple data areas at run time without having to configure a separate Read/Write table for each one. Therefore.SIEMENS SINEC H1 | 19 Logical Station Commands Table 2 defines a read/write table to access ten 2-byte integers in logical station 1. Bit or Length. Configuring the Set Logical Station Variables Command To configure a message tag as a Set Logical Station Variables command. Table 2 alone can be used to read ten 2-byte integers from any external device by setting set_param_msg and triggering table 1 before you trigger table 2. you do not need to configure any more read/write tables to read ten 2-byte integers.

(For example. they are unsigned-bytes with values ranging from 0 . The S505 variable index values default to 1..255.) • For S505 stations with zero-based addressing on the communications line and one-based addressing (addresses begin with one) in the address description. the variable value is 3. These variables have the following characteristics: • For both the S5 and S505 logical stations.” 436 / FactoryLink Device Interfaces Using EDI Technology . Format The Set Logical Station Variables command is configured as a message tag. You must always construct the message tag to be an ASCII representation of the logical station variables. If one of the logical station variables is unchanged. a semicolon place holder must be used in the Set Logical Station Variables command message tag. the Set Logical Station Variables command allows each logical station to have eight variable index values called logical station variables. You change this tag at run time to represent the new values for the logical station variables..) • At DCM startup. (For example. the S5 variable index values default to 0.• • • • 19 | SIEMENS SINEC H1 Logical Station Commands Logical Station Variables Rather than hard-coding the index values into a line of the Siemens H1 Read/Write Information table. When reconfiguring the logical station variables using the Set Logical Station Variables command. for a specified value of 3.. you only need to specify the variables that change. for a specified value of 3..12..15. • For S5 logical stations with zero-based addressing (addresses begin with zero) on the communications line. the variable index values equal the value specified. to set the logical station variables for an S5 logical station at startup to: 1 2 3 4 5 6 7 8 5 0 0 0 0 12 0 15 Create the following message tag string: Set_Station_Msg =“5. For example. the variable value is 2. the variable index values equal the specified value decremented by one. The value of each variable is separated by a semicolon.

This provides the flexibility to change the data blocks you access within the PLC at run time using a Math and Logic procedure without having to configure a new read/write table. set_sta_msg. or as the first index in double index regions in either S5 or S505 logical stations. In this example. Set Logical Station Variables Example The Siemens H1MP allows you to use logical station variables to control the Region Index in the Read/Write Information table at run time. This means when table 2 is triggered.SIEMENS SINEC H1 | 19 Logical Station Commands You can use these variables for the tag number in S505 Loop and Alarm variables. is configured as a Set Logical Station Variable command 3 in read/write table 1. A message tag. table 1 is triggered to set the logical station variable 3. This allows you to access a different data region in the PLC with each triggered read because you have the power to change the value of logical station variable 3 where the read/write table Region Index field is pointing to get its value. FactoryLink Device Interfaces Using EDI Technology / 437 . it will look in the third logical station variable for the Region Index value. In this example. set_sta_msg is used in the Math and Logic procedure to change the value of the logical station variables. The Region Index value is configured to be logical station variable number 3. read/write table 2 is configured to read ten 2-byte integers from an external PLC. Note Ensure this message contains seven semicolons plus a terminating semicolon. Before read/write table is 2 is triggered to read the ten 2-byte integers.

You can use this tag at runtime to dynamically set Region Index 3 for table 2. you must configure at least two read/write tables. You then trigger table 2 and read the ten 2-byte integers. Once you set the value of set_sta_msg in an IML procedure and trigger the table. table 1 declares the tag set_sta_msg as a Set Logical Station Variables (LSCMD) 3. the logical station variables take on the values as specified in the tag set_sta_msg. In this example. 438 / FactoryLink Device Interfaces Using EDI Technology . Notice in table 2 the Region Index starts with a negative number.• • • • 19 | SIEMENS SINEC H1 Logical Station Commands Logical Station Variables 1 2 3 4 5 6 7 8 PLC Protocol Module Base Module set_sta_msg CML To take advantage of the H1MP protocol module’s Logical Station Variables command. This indicates that logical station variable 3 contains the actual Region Index table 2 will read.

Therefore. for example. • If a table does not contain a logical station command as its first entry (by logical port) and a logical station command is given. and a command other than a Set Parameters command is given. To avoid row errors. FactoryLink Device Interfaces Using EDI Technology / 439 . ensure you enter only Set Parameters commands in block write tables containing Set Parameters commands. In a single block write table. Note: The last command entered may not be the last command processed. Row errors may result from any of the following conditions: • If a table has a Set Parameters command as its first entry (by logical port).SIEMENS SINEC H1 | 19 Logical Station Commands Set Logical Station Commands and Row Errors A block write table which contains logical station commands can only contain logical station commands. If a row error is detected during start up. the Siemens H1 protocol module can define multiple logical station Set Parameters commands (instead of defining multiple logical stations in multiple block write tables). otherwise row errors occur. For further information about logical station command error codes that can be generated and displayed at startup. if multiple commands are made to the same logical station. the last command processed defines the values for the logical station. no provisions are made in the Siemens H1 to check for multiple commands to the same logical station. However. an error message is displayed on the screen and the entry is ignored. see “Run-Time Application Messages” on page 446. A row error is a line in the Siemens H1 Read/Write Information table containing an invalid entry.

PC with FactoryLink CP535/CP143 Siemens S5 PLC Bus Cable (Thick to Thin) Transceiver Cable Transceiver Cable Bus Cable Thick Net Transceiver PC with FactoryLink Thin Net Coax Transceiver Transceiver 440 / FactoryLink Device Interfaces Using EDI Technology . The second PC uses a thin net coax cable through a thick-to-thin transceiver to connect with the Ethernet bus. A transceiver cable through a transceiver to the Ethernet bus connects the Siemens S5 PLC with a CP535 or CP143 card.• • • • 19 | SIEMENS SINEC H1 Cable Diagrams C ABLE D IAGRAMS This section contains information about connecting the Siemens H1 Ethernet system using a thick net or thin net bus. Thick Net Bus The example below illustrates two PCs running FactoryLink. The first PC uses a transceiver cable through a transceiver to connect to the Ethernet bus. using a thick net bus.

SIEMENS SINEC H1 | 19 Siemens H1 Data Types Thin Net Bus The example below illustrates a PC running FactoryLink using a cable connected to an Ethernet thin net coax cable. The specific conversion performed depends on the FactoryLink data type and the specific PLC type. A second part of the diagram illustrates a Siemens S5 PLC with a CP535 or CP143 card connected using a transceiver cable through a transceiver to the Ethernet thin net coax cable. This section lists the data conversions for FactoryLink tags: • Digital • Analog • Floating-point • Floating long analog • Message FactoryLink Device Interfaces Using EDI Technology / 441 . Coax Cable (Thin Net) PC with FactoryLink CP535/CP143 Siemens S5 PLC Thin Transceiver Transceiver Cable S IEMENS H1 D ATA TYPES The Siemens H1 multiplatform protocol module provides data conversions between the FactoryLink real-time database and the Siemens PLC.

minimum: -32768 Valid only in byte regions. minimum: -32768 4-byte signed integer maximum: 32767. unsigned byte maximum: 0. minimum: -999 4-byte 7-digit Binary Coded Decimal with sign maximum: 32767. minimum: 255 Invalid PLC type for analog 4-byte signed Siemens floating-point maximum: 32767. minimum: -32768 442 / FactoryLink Device Interfaces Using EDI Technology .• • • • 19 | SIEMENS SINEC H1 Siemens H1 Data Types Digital Conversion PLC Type Conversion BIN BCD3 BCD7 BYTE DIG FLT INT2 INT4 HILO LOHI Same as DIG Invalid PLC type for digital Invalid PLC type for digital Invalid PLC type for digital Specified bit read or write to or from the FactoryLink tag Invalid PLC type for digital Invalid PLC type for digital Invalid PLC type for digital Invalid PLC type for digital Invalid PLC type for digital Analog Conversion PLC Type Conversion BIN BCD3 BCD7 BYTE DIG FLT INT2 INT4 Same as INT2 2-byte 3-digit Binary Coded Decimal with sign maximum: 999. minimum: -32768 2-byte signed integer maximum: 32767.

unsigned byte maximum: 0.SIEMENS SINEC H1 | 19 Siemens H1 Data Types PLC Type Conversion HILO LOHI Invalid PLC type for analog Invalid PLC type for analog Floating Point Conversion PLC Type Conversion BIN BCD3 BCD7 BYTE DIG FLT INT2 INT4 HILO LOHI Same as FLT 2-byte 3-digit Binary Coded Decimal with sign maximum: 999. minimum: -2147483648 Invalid PLC type for float Invalid PLC type for float FactoryLink Device Interfaces Using EDI Technology / 443 . minimum: -9999999 Valid only in byte regions. minimum: 255 Invalid PLC type for float 4-byte Siemens floating-point 2-byte signed integer maximum: 32767. minimum: -999 4-byte 7-digit Binary Coded Decimal with sign maximum: 9999999. minimum: -32768 4-byte signed integer maximum: 2147483647.

unsigned byte maximum: 0. minimum: -2147483648 2-byte signed integer maximum: 32767. minimum: -2147483648 Invalid PLC type for long analog Invalid PLC type for long analog Message Conversion PLC Type Conversion BIN BCD3 BCD7 BYTE DIG FLT INT2 INT4 HILO LOHI Same as HILO Invalid PLC type for message Invalid PLC type for message Invalid PLC type for message Invalid PLC type for message Invalid PLC type for message Invalid PLC type for message Invalid PLC type for message Character string high-order byte followed by low-order byte Character string low-order byte followed by high-order byte 444 / FactoryLink Device Interfaces Using EDI Technology . minimum: -999 4-byte 7-digit Binary Coded Decimal with sign maximum: 9999999. minimum: -9999999 Valid only in byte regions.• • • • 19 | SIEMENS SINEC H1 Siemens H1 Data Types Floating Long Analog Conversion PLC Type Conversion BIN BCD3 BCD7 BYTE FLT INT2 INT4 HILO LOHI Same as INT4 2-byte 3-digit Binary Coded Decimal with sign maximum: 999. minimum: -32768 4-byte signed integer maximum: 2147483647. minimum: 255 4-byte signed Siemens floating-point maximum: 2147483647.

then the adapter can be accessed and is valid for the Siemens H1. CP Address Is a 12-character hexadecimal address you must program into the Siemens CP535/CP143 Ethernet Interface card. the Siemens H1 EDI package contains an adapter display utility. For each FactoryLink platform. If NO. It is the remote adapter address for each job (ANR) that communicates with this adapter.EXE. HLMPDISP. The program displays the following information: Adapter# Accessible CP Address 00 01 YES NO AA0004003105 ————— where: Adapter# Accessible Is the LAN adapter number of the LAN adapter described in the remainder of the line.SIEMENS SINEC H1 | 19 Siemens H1 Adapter Display Utility (H1MPDISP) S IEMENS H1 A DAPTER D ISPLAY U TILITY (H1MPDISP) This section discusses the adapter display utility. The method for invoking the program depends on the platform in use. H1MPDISP. Indicates whether the adapter is properly configured and accessible to the DCM task: If YES. then the adapter cannot be accessed and is either not installed or improperly configured. FactoryLink Device Interfaces Using EDI Technology / 445 . that provides the following services: • Verifies the configuration of the Ethernet adapter • Provides the proper address to be programmed into the Siemens Ethernet Interface card This utility program resides in the ${FLINK}/EDI/H1MP directory.

see “Configuring the Logical Station Information Table” on page 409. For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. For information about configuring a message tag. “Messages and Codes. Action: Verify you have properly configured the External Device Definitions and Logical Station Information tables and the Ethernet installation and the Siemens CP535 programming parameters are correct. Action: Call Customer Support for assistance. see “Configuring the Logical Station Control Table” on page 405. Action: Verify the Siemens CP535 and the PLC programming parameters are correct.” 0001h Cause: Internal protocol module error. see Chapter 10. 0002h Cause: Communication error. For information about configuring an analog tag. writes them to message or analog tags. FactoryLink generates and displays messages for the General Electric protocol module on the Run-Time Manager screen and. 0003h Cause: Communication error. 0004h Cause: Internal protocol module error.• • • • 19 | SIEMENS SINEC H1 Run-Time Application Messages R UN -TIME A PPLICATION M ESSAGES During EDI run time. Action: Call Customer Support for assistance. 446 / FactoryLink Device Interfaces Using EDI Technology . if so configured.

0006h Cause: 0007h Invalid response packet length. Order No. see “Run-Time Logical Station Command Error Codes” on page 448. Action: Call Customer Support for assistance. Action: Allow sufficient time to establish communication before initiating a solicited operation. FactoryLink Device Interfaces Using EDI Technology / 447 .” Cause: Inactive station.SIEMENS SINEC H1 | 19 Run-Time Application Messages XX05h Cause: Received Siemens error code 'XX'h in response packet. consult the Siemens Communication Processor CP535 with COM 535 Programming Package (S5 DOS Version). Cause: 0008h Internal protocol module error. Cause: 0009h A “FLT” value in the PLC contains invalid floating-point data. Chapter 8. Action: Verify the value being read is an “FLT. Verify the station has not been disabled through a logical station activate/deactivate command. Action: Call Customer Support for assistance. 6ES5998-6SA21. This may occur at start up of the protocol module. ensure the Siemens H1 Logical Station Information table and Siemens CP programming parameters match. AXXXh Cause: Invalid value was entered for the logical station commands (set parameters or activate/deactivate station). A solicited (read or write) operation was requested to an inactive station. Correct the value in the field that is specified by the error code. Release 04. Action: For a list of the logical station command error codes. Action: For a list of error codes that correspond to the XX values in this error message. If the error persists.

are both valid. For the Activate/Deactivate Station command. the only errors possible for the logical station commands come from invalid tag values for the set parameters and activate/deactivate station commands at run time. the logical station generates error code 0xA101. set and reset. for consistency in error reporting. 448 / FactoryLink Device Interfaces Using EDI Technology . Theoretically. To free the station from this unknown state. and the logical station becomes inactive. However. The logical station generates two commands: • 0xAyXX • 0xA101 For an invalid tag value. issue a set parameters command for that logical station or restart the logical port. the Activate/Deactivate command cannot produce errors since it uses only digital tags whose values. the logical station generates this error code. it puts the logical station in an unknown configuration state. The logical station generates error code 0xA2XX for the Set Parameters command.• • • • 19 | SIEMENS SINEC H1 Run-Time Application Messages Run-Time Logical Station Command Error Codes For the Siemens H1 Ethernet. the logical station generates the error code 0xAyXX where A y Is an error from a logical station command Is the specific command y = 1 is the Activate/Deactivate Station command y = 2 is the Set Remote Parameters command y = 3 is the Set Logical Station Variables command XX Is the error code for the specified field in error When the protocol module detects an error.

set parameters commands. rmt sol write TSA ID Invalid field 5. lcl sol write TSA ID Invalid field 6. lcl usl read TSA ID For further information about activate/deactivate station commands. rmt usl read TSA ID Invalid field 7. and row errors. lcl sol read TSA ID Invalid field 4. see “Siemens H1 Adapter Display Utility (H1MPDISP)” on page 445. adapter address Invalid field 2. FactoryLink Device Interfaces Using EDI Technology / 449 .SIEMENS SINEC H1 | 19 Run-Time Application Messages The following list defines the codes for both the Activate/Deactivate and Set Parameters commands: Code Description 0xA101 0xA2XX 0xA200 0xA201 0xA202 0xA203 0xA204 0xA205 0xA206 0xA207 Activate/Deactivate command Set Logical Station parameters Invalid number of fields Invalid field 1. rmt sol read TSA ID Invalid field 3.

• • • • 19 | SIEMENS SINEC H1 Run-Time Application Messages 450 / FactoryLink Device Interfaces Using EDI Technology .

See “Identifying Protocol Types and Defining Logical Ports” on page 58 for details. In your server application. Note Before completing the protocol-specific Square D configuration tables.Chapter 20 • • • Square D Serial/Ethernet Symax This chapter contains information needed to set up and configure bidirectional communications between the FactoryLink real-time database and Square D Serial/Ethernet SY/MAX devices using the IEEE 802. because Microsoft removed the DLC protocol stack from XP. Note: The Square D Serial/Ethernet Symax driver can be used on Windows XP platforms with RS232 communications only. • FactoryLink Device Interfaces Using EDI Technology / 451 . you must complete the External Device Definition table. you can use this driver on Windows 2000 platforms using both Ethernet and RS232 serial communications. open Device Interfaces > Square D.3 communications protocol or SY/MAX point-to-point serial communications. However.

For Ethernet communications. defined in the External Device Definition table Logical Port column.255 (default=255) 452 / FactoryLink Device Interfaces Using EDI Technology . enter the source drop number (see the description for Source Drop Number). Valid Entry: 0 .99 (default=3) Source Route Address SR1 A text string that identifies the source route address defined in the SR1 column is displayed. Logical Port Enter a number. to represent a particular communication path to a device. If you do not need additional routing. Note In this table. Valid Entry: leave blank (display only) Enter the source route address or drop number of a network interface module not being used on the Sylink network. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. enter the source route address. accept the system default of 255. source refers to the FactoryLink station and destination refers to the Square D device. Valid Entry: 0 . For serial communications. Valid Entry: previously defined logical port number Device Message Tag Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. Valid Entry: tag name Valid Data Type: message Number of Retries Define the maximum number of consecutive times a read or write command will be sent to a logical station after an unsuccessful first transmission attempt.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Configuring the Logical Station Control Table C ONFIGURING THE L OGICAL S TATION C ONTROL TABLE Open the Logical Station Control table.

refer to the device manufacturer’s documentation. Baud Rate Enter the speed at which the protocol module communicates with the devices linked to FactoryLink via this logical port. For serial communications.115200 (default=9600) Parity Enter the parity error correction during transmission via this logical port. Valid Entry: 110 . To determine the proper settings. accept the system default of 255. Valid Entry: 8 Stop Bits Enter the stop bit interval that provides the destination a pause before the start of the next character. This entry must match the baud rate configuration of the devices. enter the source drop number on the Ethernet network. SR1. be sure to enter values that correspond to the device hardware configuration for all devices communicating through the specified logical port. FactoryLink Device Interfaces Using EDI Technology / 453 . Define the data type (message) for any tag names displayed in the Tag Definition dialog box.255 (default=0) Note For the fields Baud Rate through Stop Bits. If you enter a number in this column. Valid Entry: 0 .SQUARE D SERIAL/ETHERNET SYMAX | 20 Configuring the Logical Station Control Table Source Drop Number For Ethernet communications. enter the same number in the previous column. Refer to the device manufacturer’s documentation for details. enter descriptive reference information about this logical station. Valid Entry: even Data Bits Enter the number of data bits used during transmission via this logical port. click the Save icon to validate the information. Valid Entry: alphanumeric string of up to 21 characters When the table is complete. Valid Entry: 1 Comment Optionally.

Data Bits 8 The devices configured for communications via logical port 0 require 8 data bits. Baud Rate 9600 This baud rate entry (the speed at which the FactoryLink station communicates with the device) of 9600 must match the baud rate configuration of the Square D devices communicating with FactoryLink via logical port 0. SR1 126 The network source route address for the device is 126. Source Drop 126 The source drop number on the network is Number 126. Stop Bits 1 The devices configured for communications via logical port 0 require a stop bit of 1. Parity EVEN The parity error correction for transmission via logical port 0 is even and must match the parity configuration of the devices using this port. Number of 3 A read or write command to any device Retries communicating via this port will be retried three times before an error message is generated. SQRD_LPORT0_MSG.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Configuring the Logical Station Control Table The following table provides sample entries for a row defining an Ethernet logical port (the entry in the Function column in the External Device Definition table is ETHERNET): Column Logical Port Entry Description The communication path to be used for read and write operations between FactoryLink and devices communicating via this port is represented as 0. 0 454 / FactoryLink Device Interfaces Using EDI Technology . Device SQRD_LPORT0_MSG The EDI task will write communications Message Tag error messages associated with this logical port to a message tag.

255 (default=255) FactoryLink Device Interfaces Using EDI Technology / 455 . accept the system default of 255. enter the destination route address. A logical station represents the combination of a logical port with a physical station. Valid Entry: tag name Valid Data Type: analog Logical Station A number to identify the logical station to which the information in this row pertains. Assign a unique number to each device communicating through this logical port. Complete a row for each device to communicate through this logical port. Valid Entry: 0 . For serial communications. you will enter this logical station number in a read or write table to represent the device defined in this row. select the row for the logical port you are configuring and open the Logical Station Information table. If you do not need additional routing. in milliseconds. enter the destination drop number (see the description for Destination Drop Number). you must enter a value greater than 0. In a read or write table. this number will identify the device to or from which data is to be sent or received. Error/Status Tag Name A tag name for an analog tag in which to store communications error codes associated with this device (logical station).1 second) Destination Route Address DR1 A text string that identifies the destination route address defined in the DRn column for this row is displayed. For the protocol module to time out. For Ethernet communications. Valid Entry: leave blank (display only) Enter the destination route address or drop number of a network interface module connecting to a separate Sylink network. Valid Entry: 0 .999 Timeout m sec The maximum amount of time. Later.9999 (default=100 or 0. the protocol module will wait to receive a response to a read or write command before timing out.SQUARE D SERIAL/ETHERNET SYMAX | 20 Configuring the Logical Station Information Table C ONFIGURING THE L OGICAL STATION I NFORMATION TABLE From the Logical Station Control table. Valid Entry: 0 .

enter the same number in the DRn column for this row.256 (default=256) When the table is complete. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box. 0 456 / FactoryLink Device Interfaces Using EDI Technology . click the Save icon to validate the information. If you enter a number in this column. Valid Entry: 0 . The protocol being used (point-to-point or IEEE 802.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Configuring the Logical Station Information Table DR2 through DR7 Destination Drop Number If needed. accept the system default of 255. Valid Entry: 0 .255 (default=255) For Ethernet communications. accept each field’s default of 255. Column Logical Port Entry Description The logical port number defined in the Logical Station Control table is displayed. SQRD_STATION0_STATUS. or 128 registers of data. define up to six additional destination route addresses. Error/Status SQRD_STATION0_ Communications error codes generated for Tag Name STATUS this logical station will be stored in an analog tag. If not needed. DR1 54 Destination route address of the device is 54. enter the destination drop number on the Ethernet network.255 (default=255) Maximum Packet size Define the maximum number of bytes the device defined in this row can transmit in one message.3) does not affect the maximum packet size. Most Square D devices can transmit 256 bytes. The following table provides sample entries for a row defining a logical station communicating via the logical port specified on the Logical Station Control table. Timeout m 100 Each of the retries (3) specified in the sec Logical Station Control table will time out after 100 milliseconds if the device does not respond. For serial communications. Logical 0 A device communicating with FactoryLink Station via logical port 0 is assigned a logical number of 0. Valid Entry: 0 .

The device defined as logical station 0 can transmit up to 256 bytes in one message.SQUARE D SERIAL/ETHERNET SYMAX | 20 Configuring the Logical Station Information Table Column DR2 Entry Description 255 This configuration only requires one destination route address so the additional DRn fields default to 255. DR3 DR4 DR5 DR6 DR7 Destination Drop Number Maximum Packet Size 255 255 255 255 255 54 256 Drop location of the device on the network path is 54. FactoryLink Device Interfaces Using EDI Technology / 457 .

If a different value is being stored the tag. enter YES. If the current value of the tag is equal to the new value. the change-status indicator is unaffected. 458 / FactoryLink Device Interfaces Using EDI Technology . EDI will emulate the device's addressing structure based on entries you make in the Read/Write Information table. Valid Entry: alphanumeric string of up to 16 characters Unsolicited Read If this is a triggered block read or as a write operation. Define one request (table) per line and do not include spaces in the name. accept the default of NO. Table Name Assign a name to this read or write request.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Configuring the Read/Write Control Table C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Open the Read/Write Control table. If this is an unsolicited read operation. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). enter YES. however. Tip See “Application Design Tips and Techniques” on page 127 for information about triggering schemes using tags defined in this table. the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. Try to make the table name reflective of the operation it represents. For EDI to interpret this operation as an exception write and write tag values to the device only when those values change. accept the default of NO. Valid Entry: yes. no (default=no) Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. Complete a row for each read or write table. If this is a triggered read or a block write table. You can define as many tables as available memory allows. it will overwrite the current value and the tag’s change-status indicator will be set to 1 (ON). The incoming data will be stored in the tag represented by the tag name specified in the Read/Write Information table.

SQUARE D SERIAL/ETHERNET SYMAX | 20 Configuring the Read/Write Control Table In an exception write. an internal change-status indicator within the tag containing the data to be written prompts the write operation. This number influences the order in which the EDI task handles the queueing of block read requests. and Block Read State tags apply only to triggered read operations. relative to other read operations.4 (default=1) Note The Block Read Trigger. EDI writes this tag’s value to the device. enter a number to indicate the priority of this table. Block Read Complete. ignore this field. If EDI receives two requests at the same time. If this is an unsolicited read or a write operation. Do not define these tags for unsolicited read operations or for write operations. accept the default of 1. Block Read Priority If this is a block read operation. no (default=no) Tip Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. Valid Entry: 1 . The highest priority is 1. the addresses are read. The default is 1. Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. this field is required. Any tag specified will be written to the device in its own packet (message) each time it changes. Valid Entry: tag name Valid Data Type: digital FactoryLink Device Interfaces Using EDI Technology / 459 . it processes the request with the highest priority first. Defining tags that change value frequently as exception writes can slow down communications or result in an error message. Block Read Disable. Valid Entry: yes. If this is a triggered read operation. This field defaults to 1 regardless of whether the operation being defined is a block read. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). Block Read Trigger If this is an unsolicited read or a write operation. When this tag’s value is forced to 1 (ON).

To reenable a block read table that is disabled. the Block Read Trigger tag must be toggled or forced to 1.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Configuring the Read/Write Control Table Block Read Disable If this is an unsolicited read or a write operation. See “Application Design Tips and Techniques” on page 127 for further details. If this is a triggered read operation. Valid Entry: tag name Valid Data Type: digital Block Read State If this is an unsolicited read or a write operation. This tag is forced to 1 (ON) at startup. When this tag’s value is forced to 1 (ON). enter a tag name. Block Read Complete If this is an unsolicited read or a write operation. however. enter a tag name. ignore this field. set this tag back to 0 (OFF). enter a tag name. If you need a digital tag to indicate the state of this operation (in progress or complete). this field is optional. ignore this field. If you need a digital tag to disable a block read of the tags specified in this table. the read operation is not executed. even when the block read trigger is set to 1. this field is optional. The triggering cycle will cease upon disabling. ignore this field. If this is a triggered read operation. Valid Entry: tag name Valid Data Type: digital Tip This tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered. If this is a triggered read operation. the complete tag is forced to 1 again. this field is optional. To reenable a cascaded loop or a self-triggered read table. This tag is forced to 1 (ON) at startup. Do not use this tag when more than one logical port is specified in a single table. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. If you need a digital tag to indicate when this operation is complete. 460 / FactoryLink Device Interfaces Using EDI Technology .

ignore this field. This field defaults to 1 regardless of whether the operation being defined is a block or exception write. Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. FactoryLink writes the values. the tag is set to 0 (OFF). This number influences the order in which the EDI task handles the queuing of write requests. The default is 1. the state tag is forced back to 1. enter a number to indicate the priority of this table.SQUARE D SERIAL/ETHERNET SYMAX | 20 Configuring the Read/Write Control Table While the table is being processed. Valid Entry: tag name Valid Data Type: digital Block Write Priority If this is a block or exception write operation. relative to other write operations. If this is a read operation. ignore this field. Do not define these tags for read operations. Valid Entry: tag name Valid Data Type: digital Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. it processes the request with the highest priority first. Block Write Complete. and Block Write State tags apply only to write operations. When this tag’s value is forced to 1 (ON). FactoryLink Device Interfaces Using EDI Technology / 461 . accept the default of 1.4 (default=1) Note The Block Write Trigger. If this is a block write table or an exception write table you plan to periodically disable. Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. The highest priority is 1. Block Write Disable. If EDI receives two requests at the same time. Valid Entry: 1 . this field is required. After the tags defined in the Read/Write Information table are updated in the FactoryLink database.

If you need a digital tag to indicate when this operation is complete. however. this field is optional. set this tag back to 0 (OFF). Block Write Complete If this is a read or exception write operation. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. this field is optional. This tag is forced to 1 (ON) at startup. To reenable a block write table that is disabled. the write operation is not executed. ignore this field. After the data defined in this table’s Read/Write Information table is written to the device. If this is a block write operation. Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. the state tag is forced back to 1. When this tag’s value is forced to 1 (ON). While the table is being processed. the Block Write Trigger tag must be toggled or forced to 1. If you need a digital tag to indicate the state of this operation (in progress or complete). Valid Entry: tag name Valid Data Type: digital Tip This tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. After the data defined in this table’s Read/Write Information table is written to the device. See “Application Design Tips and Techniques” on page 127 for further details. Do not use this tag when more than one logical port is specified in a single table. 462 / FactoryLink Device Interfaces Using EDI Technology . ignore this field. this field is optional. the complete tag is forced to 1 again. enter a tag name. This tag is forced to 1 (ON) at startup. the tag is set to 0 (OFF). To reenable a cascaded loop or a self-triggered write table.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Configuring the Read/Write Control Table If this is a block write table or an exception write table you plan to periodically disable. even when the block write trigger is set to 1. enter a tag name. If this is a block write table. The triggering cycle will cease upon disabling.

is set to the default of 1. FactoryLink disregards the trigger tag. Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. This is not an exception write table. click the Save icon to validate the information. The following table provides sample entries for a row defining a triggered read table: Column Table Name Unsolicited Read Exception Write Block Read Priority Entry Description READ NO NO 1 Block Read Trigger SQRD_READ_TRIGGER Block Read Disable SQRD_READ_DISABLE The name of this table is READ. and does not process the READ table. The block read priority. When the value of SQRD_READ_TRIGGER is 1.SQUARE D SERIAL/ETHERNET SYMAX | 20 Configuring the Read/Write Control Table Do not use this tag when more than one logical port is specified in a single table. FactoryLink reads the configured address and writes its value to the tag configured for this table (in the Read/Write Information table). When the value of SQRD_READ_DISABLE is 1. This is not an unsolicited read table. which is set automatically if you do not enter a value. Valid Entry: tag name Valid Data Type: digital When the table is complete. the highest priority. SQRD_READ_TRIGGER. FactoryLink Device Interfaces Using EDI Technology / 463 .

Block Read State SQRD_READ_STATE Once the data is read and stored in the tag defined to receive it. During the read operation. FactoryLink forces a value of 1 to SQRD_READ_COMPLETE. SQRD_READ_STATE is set to 0. Block Write Priority 1 The write priority for this table is set to 1 by default. the Block Write tags specific to write requests Complete are not defined. FactoryLink forces a value of 1 to SQRD_READ_STATE.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Configuring the Read/Write Control Table Column Block Read Complete Entry Description SQRD_READ_COMPLETE Once the data is read and stored in the tag defined (in the Read/Write Information table) to receive it. Block Write Trigger Since this is a read table. Block Write Disable Block Write State 464 / FactoryLink Device Interfaces Using EDI Technology .

Valid Entry: 1 .SQUARE D SERIAL/ETHERNET SYMAX | 20 Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. leave this field blank. analog. For all other FactoryLink data types. For a write table. For a write table.16 if data type is digital FactoryLink Device Interfaces Using EDI Technology / 465 . Valid Entry: previously defined logical station number Data Type For each tag defined in the Tag Name field. enter the bit offset within the word that contains the value to be read or to which the tag value is to be written. enter the address in the device's memory to which the tag value will be written. For a Write Table – add a table entry for each tag to be written when the operation executes. Valid Entry: 1 . longana.8192 Bit Offset If the tag (entry in the Tag Name column) associated with this entry is digital. specify the type of data being read from or written to the device. specify a tag name for a tag containing a value to be written to the device. status (default=register) Address For a read table. Valid Entry: register. Bit 1 is the most significant bit (MSB) and bit 16 is the least significant bit. enter the address in the device's memory where the value to be stored in this tag is located. Tag Name For a read table. For a Read Table – add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes. float Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written. select the row for the table you are configuring and open the Read/Write Information table. Valid Entry: tag name Valid Data Type: digital. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. specify a tag name for a tag in which FactoryLink will store the data read from the device.

• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Configuring the Read/Write Information Table Priority If this is an unsolicited read operation (that is. normal (default=normal) When the table is complete. The bit offset containing the value being read is 12. Valid Entry: priority. When the READ table is triggered by SQRD_READ_TRIGGER (defined in the Read/Write Control table). Field Table Name Tag Name Entry Description READ REG_DIG1 The table name defined in the Read/Write Control table is displayed. Define the data type (digital. enter PRIORITY. long analog. The following table provides sample Read/Write Information table entries for the triggered read table. This read operation will be processed according to the priority specified in the Read/Write Control table. Logical Station Data Type Address Bit Offset Priority 0 REGISTER 426 12 NORMAL 466 / FactoryLink Device Interfaces Using EDI Technology . FactoryLink processes the table. The value stored in this tag is read from the Square D device configured as logical station 0. Otherwise. you entered YES in the Unsolicited Read field on the Read/Write Control table). The address of the register is 426. click the Save icon to validate the information. or floating-point) for any tag names displayed in the Tag Definition dialog box. A register address is being read. analog. accept the default of NORMAL. The value read from the device is stored in REG_DIG1.

FactoryLink RS-232 null modem cable RDRD+ SDSD+ FactoryLink Device Interfaces Using EDI Technology / 467 . Pins 7 and 8 are jumped together. Host RS-232 25-pin RS-232 to RS-422 converter Square D 9-pin Pin 1 is TXPin 2 is TX+ Pin 3 is RXPin 4 is RX+ Pins 5 and 6 are jumped together. through the converter’s four-wire RW-422 cable to the Square D’s 9-pin port.SQUARE D SERIAL/ETHERNET SYMAX | 20 Cable Diagram C ABLE D IAGRAM The following figure illustrates how to connect the computer running FactoryLink to a Square D device. This connection occurs from the host through an RS-232 25-pin ribbon cable to a 25-pin converter.

Action: Verify that bit 51 was properly installed. This command is part of initialization and terminates with this error. For information about configuring an analog tag. see “Configuring the Logical Station Information Table” on page 455. SQRD8023: Process unsolicited XMIT_ERROR Cause: Task error attempting to process an unsolicited message. writes them to message or analog tags. “Messages and Codes. Action: No action is required. see Chapter 10.” SQRD8023 Messages SQRD8023: Error closing Multicast Service Access Point Cause: Task was unsuccessful in closing the SAP address. if so configured. SQRD8023: Error sending connect command Cause: Task was unsuccessful in sending the connect command. Action: Device address of drop may be incorrect. For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. This error may occur when stopping the task. For information about configuring a message tag. 468 / FactoryLink Device Interfaces Using EDI Technology . Action: Change the format of the message sent from the PLC. but the FactoryLink protection bit 51 could not be located. SQRD8023: Protection bit failure Cause: Task has attempted to start. FactoryLink generates and displays messages for the Square D protocol module on the Run-Time Manager screen and.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Run-Time Application Messages R UN -TIME A PPLICATION M ESSAGES During EDI runtime. see “Configuring the Logical Station Control Table” on page 452.

The following information is also returned to the Device Message Tag tag defined in the Logical Station Control table: SQRDDST: LSTA .yyy Error .3 Ethernet communication protocol module: SQRDDSF: LSTA . This error indicates that a physical problem has occurred. They appear in the format described in “EDI Run-Time Manager Line Format” on page 148. SQRDRCOM.yyy Error .xxx:sss FactoryLink Device Interfaces Using EDI Technology / 469 . SQRDDSF: PPORT-%d start failed Cause: Task has unsuccessfully attempted to configure the physical port indicated by the %d. the following messages can appear: SQRDCPT: PPORT-%d port setup failed Cause: Task has unsuccessfully attempted to configure the physical port indicated by the %d. Action: Verify that the physical port is correctly defined. SQRDSCOM and SQRDENET Messages Error messages in the following format can occur with the SY/MAX point-to-point serial communication or with the 802. Action: Verify that the physical port is correctly defined.xxx: sss These errors are associated with return data to the FactoryLink EDI task and the logical port error message tag. SQRDCPT: Protection bit failure Cause: Task has attempted to start. This error indicates that a physical problem has occurred. Action: Verify that bit 51 was properly installed.SQUARE D SERIAL/ETHERNET SYMAX | 20 Run-Time Application Messages SQRDRCOM and SQRDSCOM Messages If using SY/MAX point-to-point serial communications. but the FactoryLink protection bit 51 could not be located.

An error occurred during the transmission of the packet.• • • • 20 | SQUARE D SERIAL/ETHERNET SYMAX Run-Time Application Messages where: yyy zzz sss Is the logical station where the error occurred Is the error number Is the ASCII string describing the error message. Invalid error code. . Received an unsupported Unsolicited Opcode-YYY. Resent the packet the retry number without receiving ACK. Invalid FactoryLink tag type. See the following table. XXX-SY/MAX error (see Bulletin 30598-713-01). If xxx is: sss is an ASCII String Meaning: Description 1 2 3 4 5 6 7 8 Receive error Timeout Invalid error code Invalid FactoryLink type for conversion SY/MAX error XXX Received too many NAKs Received unsupported Unsolicited Opcode-YYY Transmit error An error occurred while the packet was being received. 470 / FactoryLink Device Interfaces Using EDI Technology . Did not receive a response from the request.

The PLC interface task controls communication using data entered by the user in the various configuration tables.Chapter 21 • • • Telemecanique PLC I NTERFACE O VERVIEW The Telemecanique programmable logic controller (PLC) interface for FactoryLink allows the user to configure two-way communication between the FactoryLink real-time database and one or more external devices. A single FactoryLink system can run more than one driver for simultaneous communication with various external devices. The generic communication task is run by the same microcomputer as FactoryLink. If the retransmission counter reaches the maximum number of sends allowed. the task considers the interface as having failed and displays an error code in the Task Manager screen. or system events. if it is correct. The read/write operations can be run periodically or be controlled by triggers. The interface consists of a generic communication task and a specific communication card device driver. The error code identifies the device causing the communication problems. If the response time is exceeded or if an incorrect response is received. the task repeats the command. Principles of Operation The PLC interface reads/writes data to/from external devices via a specific driver and one or more communication ports located on one or more communication cards. The PLC interface task also checks the response is received within a set time-out. it checks the response and acknowledges it. operator actions. The specific device driver is run by the co-processor card or by the microcomputer and works with FactoryLink to establish the link between the real-time database and PLC data objects. When the PLC interface task receives a response to a command from an external device. • FactoryLink Device Interfaces Using EDI Technology / 471 .

the user specifies a “trigger” tag in the real-time database that will be used to initiate read operations. In this case the exchange is initiated by the external device. The PLC interface task sends these requests as “packets” separated by type of data and groups of packets separated by logical station. Unsolicited read (unsolicited data): The PLC interface task can await data sent by an external device for better operation with some external devices. the write command from the PLC must apply to a specified type of data object. otherwise. the PLC interface task sends a command to the device driver for it to read the objects specified by the user in a Read/Write Configuration table. the PLC interface task reads the addresses specified in the read/write table. the PLC interface task emulates the addressing structure of PLC objects to write to the real-time database. so it can write data to the real-time database. 472 / FactoryLink Device Interfaces Using EDI Technology . In order to receive unsolicited data. This type of operation means a minimum number of block read requests lets the user collect the data specified in the configuration table. These write commands are treated as read actions as the data is received by the FactoryLink real-time database in the same way as when objects are read from a PLC. independently of FactoryLink.• • • • 21 | TELEMECANIQUE PLC Interface Overview Read When a read operation is requested. When the trigger value is 1 (ON) and has changed state since it was last sampled. For this reason. The read process continues until the last block read activated by the current trigger is performed. The block read operations ensure maximum performance levels for the PLC interface task. the task will not write its contents to the FactoryLink real-time database. For a triggered read block. The packet size depends on the protocol used by the peripheral. There can be two types of read operations: Read block (triggered): Reads the values of all PLC objects specified in the Read/Write Configuration table and writes them to the real-time database.

TELEMECANIQUE | 21 PLC Interface Overview

Write

When a write operation is requested, the PLC interface task sends a command for the driver program to write the data objects specified by the user in a Read/Write Configuration table to the appropriate peripheral. Two write operations are possible: Block writes (triggered): Writes the values of all of the tags in the database specified in a Read/Write Configuration table to a PLC. When a block write is performed, the user specifies a trigger tag taken from the FactoryLink real-time database. The trigger starts the write operations. When the trigger value is 1 (ON) and has changed state since it was last sampled, the PLC interface task sends a command to the driver program to write to the PLC the data objects specified by the user in the Read/Write Configuration table. The block write operations ensure maximum performance levels for the PLC interface task. This type of operation means a minimum number of block read requests lets the user collect the data specified in the configuration table. The PLC interface task sends these requests as packets separated by type of data and groups of packets separated by logical station. The packet size depends on the protocol used by the peripheral. The read process continues until the last block read activated by the current trigger is performed. Write on change of state (not triggered): Write on change of state is used only to write tags whose value has changed (or tags that have a change of state indicator set) since the last time the database was sampled by the task. Configuration Tables The user configures the FactoryLink PLC interface option by entering the required information in a number of configuration tables that let the system read and write data to/from an external device and initialize the communication parameters. Although various types of external devices may be used, the PLC interface task normally uses five types of configuration tables: External Device Definition table: This table lets the user specify up to 1000 logical port numbers. These numbers simplify the configuration of communication access paths by grouping communication co-processors, their physical interface ports, and the external devices in various combinations.

FactoryLink Device Interfaces Using EDI Technology / 473

• • • •

21 | TELEMECANIQUE PLC Interface Overview

Logical Station Control and Information tables: These two tables let the user define communication parameters and establish the link between logical stations and physical stations. The user can configure up to 1000 logical station control and information tables (one for each logical port). Read/Write Control and Information tables: These two tables let the user specify the PLC data objects to be read and transferred to the FactoryLink real-time database and the PLC data objects to be written from the FactoryLink real-time database. The number of read/write control information and configuration tables the user can configure is limited by the amount of memory available. The number of read/write tables is limited to 200 tables per type (200 block read tables, 200 block write tables, 200 exception write tables). The number of entries in each read/write table cannot exceed 1309 tags.

474 / FactoryLink Device Interfaces Using EDI Technology

TELEMECANIQUE | 21 External Device Definition Table

E XTERNAL D EVICE D EFINITION TABLE
This table allows the user to assign the logical port numbers to the various combinations required: device type (UNI-TE, MODBUS protocols), and function to perform (UNI-TELWAY communication). This table is configured before defining the communication parameters or the read/write operations. In your server application, open Device Interfaces > Define External Devices. This table lets the user define up to 1000 logical ports. A single logical port is usually adequate for most applications. If an application uses a large number of different devices, multiple logical port numbers can be useful so data can be sent from the FactoryLink real-time database to a number of devices on one or more networks. Specify the following information to initialize each logical port:
Logical Port

Logical port number representing a specific access path used for communication.
Valid Entry: 0 to 999

Physical Port

Physical port number. This number is not significant for XWAY network interface cards or for COM ports.

Device Name

The identification of the driver program loaded for the selected logical port. The number of characters allowed is 1 to 4.
Valid Entry: alphanumeric string of 1-4 characters: TE__ for

Telemecanique XWAY communication protocols (MAPWAY, ETHWAY, FIPWAY, UNI-TELWAY)

Function

The type of communication performed by the application, via the logical port.
Valid Entry: CUSTOM for any Telemecanique XWAY protocol

ETHWAY, MAPWAY, UNI-TELWAY COM Port, FIPWAY

Memory

Not used for Telemecanique XWAY protocol.
Valid Entry: 16 to 128 Kbytes

FactoryLink Device Interfaces Using EDI Technology / 475

• • • •

21 | TELEMECANIQUE External Device Definition Table

Comment

(Optional) Comment for the logical port.
Valid Entry: alphanumeric string of up to 14 characters

The following table shows an example of the various entries.

• Logical port 1: Comprising the ETHWAY card • Logical port 2: Comprising the UNI-TELWAY COM port When the information is entered, click the Save icon to validate the entries.

476 / FactoryLink Device Interfaces Using EDI Technology

TELEMECANIQUE | 21 Telemecanique Configuration Tables

TELEMECANIQUE C ONFIGURATION TABLES
The PLC Interface task allows the user to configure two-way communication between the FactoryLink real-time database and one or more Telemecanique drivers via a network interface card. After completing the External Device Definition table, complete the following Telemecanique configuration tables: • Logical Station Control table • Logical Station Information table • Read/Write Control table • Read/Write Information table Configuring the External Device Definition Table Type TE in the Device Name field and CUSTOM in the Function field. In your server application, open Device Interfaces > Telemecanique. Telemecanique Logical Station Table The Logical Station Control table allows the user to specify information required to initialize read/write communication between FactoryLink and a PLC. The Logical Station Information table allows the user to establish a link between logical ports and physical stations.
Logical Port

The logical port number specified in the External Device Definition table corresponding to a specific communication channel.
Valid Entry: 0 to 999

Baud Rate

Communication transmission speed in Baud.
Valid Entry: 4800, 9600, 19200 (default=9600)

Use only 4800 or 19200 settings if the TSX SCM module is programmed for these values.
Parity

Type of parity used by the transmission.
Valid Entry: odd, even, none (default=odd)

FactoryLink Device Interfaces Using EDI Technology / 477

• • • •

21 | TELEMECANIQUE Telemecanique Configuration Tables

Use only EVEN or NONE if the TSX SCM module is programmed for these settings.
Data Bits

Number of data bits used in the transmission.
Valid Entry: 7, 8 (default=8)

Use only 7 if the TSX SCM module is programmed for this setting.
Stop Bits

Number of stop bits used in the transmission.
Valid Entry: 1, 2 (default=1)

Use only 2 if the TSX SCM module is programmed for this setting.
TYPE

Type of card that supports the logical port.
Valid Entry:

TEMAP1 for the MAPWAY 1 card TEMAP2 for the MAPWAY 2 card TEUTW1 for the UNI-TELWAY and COM port TEETH1 for the ETHWAY 1 card TEETH2 for the ETHWAY 2 card TEFIP1 for the FIPWAY 1 card TEFIP2 for the FIPWAY 2 card TEPCS for the PLC programming port (usually used to communicate with a PCX PLC board. TEISA1 and TEISA2 for ISAWAY1 and ISAWAY2 driver TEIP1 and TEIP2 for tcp/ip1 and tcp/ip2 driver).
First Slave Address

Number of the lowest slave address assigned to FactoryLink communication on a Uni-Telway bus. This slave address is reserved for unsolicited data. The slave addresses used for transmission/reception of other types of messages start with the address defined in this field + 1 and end with the address of the last slave, defined in the next field. Between 1 and 15 slave addresses can be assigned to FactoryLink. For best performance, Telemecanique recommends entering the default value. See “Configuring Telemecanique Networks” on page 493 for more information.
Valid Entry: 1 to 249 (default=1)

478 / FactoryLink Device Interfaces Using EDI Technology

TELEMECANIQUE | 21 Telemecanique Configuration Tables

Last Slave Address

The number of the highest slave address assigned for FactoryLink communication on the UNI-TELWAY bus. Between 1 and 15 slave addresses can be assigned to FactoryLink. For best performance, Telemecanique recommends entering the default value. See “Configuring Telemecanique Networks” on page 493 for more information.
Valid Entry: 5 to 253 (default=15)

MSG Tag Name

(Optional) Tag of the tag that contains the report on communication status on this logical port.
Valid Entry: tag name Valid Data Type: message

The MAPWAY/ETHWAY/FIPWAY/ISAWAY/XWAYIP interface cards do not use the Baud Rate, Parity, Data Bits, Stop Bits fields. These fields must remain blank or retain their default values. If this table was previously configured for a UNI-TELWAY protocol and if it is now to be configured for a MAPWAY/ETHWAY/FIPWAY/ISAWAY/XWAYIP protocol, it is not necessary to change the initial value set in these fields. When a non UNI-TELWAY protocol is used, First and Last Slave Address fields are used to determine the number of communication sockets. From the Logical Station Control table, select the row for the logical port you are configuring and open the Logical Station Information table. The information entered in this table is assigned to the logical port whose number is displayed in the Logical Port field. If this number is incorrect, return to the Logical Station Control screen, and move the cursor to the logical port to be configured, then once again call-up the display of the Logical Station Information table.
Logical Port Error/Status Tag

Reminds the user of the number of the logical port to which the information displayed in this table is assigned. (Optional) The name of the tag assigned to the tag that contains the error code for logical station communication applications.
Valid Entry: tag name

FactoryLink Device Interfaces Using EDI Technology / 479

• • • •

21 | TELEMECANIQUE Telemecanique Configuration Tables

Valid Data Type: analog

0 - running 1 - The PLC target is not connected or a request is refused by the PLC configuration to verify its availability 3 - Timeout. The response from the logical station was not received within the configuration timeout period. Increase the timeout value in the Telemecanique Logical Station configuration table. 6 - PLC Object cannot be reached or is not configured. Check to ensure the PLC is configured with the correct range. 7 - Unsolicited message of a non-configured station is received, or a response can’t be linked with any solicited requests. Check to ensure the PLC address is a configured logical station. 9 - Internal Error. A response isn’t coherent, one request can’t be sent, an error occurred during sending, sending buffers are full, or datagram error.

Logical Station

A number entered by the user in a read/write table specifying a logical port/physical station combination. A logical station number can only be used for a single PLC.
Valid Entry: 0 to 999 (default=0)

Station Name Device Type

Comment field to associate the logical station number to the corresponding XTEL station name. The type of PLC (TSX/PMX V3/V4/V5) used for communication.
Valid Entry: 17-20, 67-40, 47-400, 67-420, TSXV3, 37-10,

47-20, 87-10, 47-410, 87-410, TSXV6, 37-21, 47-30, 87-20, 47-411, 87-420, TSXV5, 37-22, 67-20, 87-30, 47-420, 107-410, PMXV4, 67-30, 67-410, 107-420, PMXV5, 57-10, 57-20, 50-30, 50-xx, 37-xx, PCX57, NUM10x0

The next five fields define the five level XWAYaddress. Refer to the corresponding documentation for more information.
Network Number

A hexadecimal value giving the network number.
Valid Entry: 0 to 7F (default=0)

480 / FactoryLink Device Interfaces Using EDI Technology

TELEMECANIQUE | 21 Telemecanique Configuration Tables

Station Number

A hexadecimal value for the network address station number.
Valid Entry: For UNI-TELWAY: 0 to FE (default=FE)

For MAPWAY/ETHWAY/FIPWAY/XWAYIP: 0 to 3F

Gate Number

A hexadecimal value for the network address gate number.
Valid Entry: 0 to F (default=0) depending on the address to enter

0 for a master address 5 for a slave address

For an unsolicited data, this number must be 10 + x, where x is the number of the text block which send the request.
Module Number

A hexadecimal value for the module number on the network. For a slave address, the two figures in hexadecimal notation correspond to the rack number and the position of the module in the rack.
Valid Entry: 0 to FF (default=0) depending on the address to

enter 0 for a master address

Location in the rack used by a TSX SCM module for a slave address. For example, 07 corresponds to slot 7 in rack 0.
Device Number

A hexadecimal value for the network address device number.
Valid Entry: 0 to FE (default=0) depending on the address to

enter 0 for a master address H'64' plus the target slave number for a slave address

Response Timeout Seconds

The time (in seconds) during which the driver waits for a response from the PLC. If this time is exceeded, the driver repeats the message sent or sends an error message.
Valid Entry: 0 to 30 (default=10)

TW7

An indicator that shows if data transits a Telway network betweenFactoryLink and a PLC.
YES The data transits via a Telway network NO (Default) The data does not transit via a Telway network

FactoryLink Device Interfaces Using EDI Technology / 481

• • • •

21 | TELEMECANIQUE Telemecanique Configuration Tables

Drop

The number of a group of stations that are opened via the same network interface. The same drop number must be assigned to all PLCs that are connected to a common lower level network. Each PLC equipped with a MAPWAY/ETHWAY/FIPWAY/XWAYIP/ISAWAY communication module must be assigned a different number. A different drop number has to be assigned to each station configured as receiving unsolicited data. If the same drop number is used for both normal read/write operation and unsolicited data, the performances for read/write operation will be affected.
Valid Entry: 0 to 99 (default=0)

Sample entries are provided in the following table:

482 / FactoryLink Device Interfaces Using EDI Technology

TELEMECANIQUE | 21 Telemecanique Configuration Tables

In this example, information is specified for logical port 0 defined in the Telemecanique Logical Station Control table. The error codes for logical station 2 (X-TEL symbolic name: LSTA2) are written to tag te_station2. Logical station 2 communicates with a TSX 17-20 PLC with network number 0, station number FE, gate number 5, module number 7 and device number 74. The driver waits up to 10 seconds for a response to a read or write request before declaring an error condition. The logical station is linked to station group 1 (drop 1) and data exchange does not transit via a Telway network. Telemecanique Read/Write Table These tables allow the user to specify the following information: • Exception write, block write, block read, or any combination of these read/write operations • Up to 200 tags used as block read triggers (with one read trigger per table) • Up to 200 tags used as block write triggers (with one write trigger per table) • Telemecanique objects to read and transfer to the FactoryLink real-time database • Tags that receive the contents of the PLC objects It is possible to configure up to 200 read/write tables with up to 1309 tags defined in each table.
Note

Different triggers must be used for each table, as well as for reads and writes in the same table.

FactoryLink Device Interfaces Using EDI Technology / 483

• • • •

21 | TELEMECANIQUE Telemecanique Configuration Tables

If message type tags are used for block read or write operations, it is recommended no more than 16 message type tags be entered in the same table.

Table Name Unsolicited Read

The user defined name of the read/write table to configure or modify.
Valid Entry: alphanumeric string of up to 16 characters

(Optional) Indicates reading unsolicited data from the logical stations specified in this table must be interpreted by the PLC Interface task. When an unsolicited data read is performed, the PLC Interface task emulates the addressing structure of the PLC objects to write to the real-time database. An unsolicited data table must only contain Message type tags and only read Text type PLC objects. See “FactoryLink and TSX/PMX PLC Data Objects” on page 500. FactoryLink listens for unsolicited data on the First Slave Address. In addition, the user must define a logical station whose address corresponds to the target address of the text block used by the PLC for this transmission.
Y A normal write to the real-time database F A forced write to the real-time database N Unsolicited data is not interpreted

Exception Write

This indicator shows whether writing is required each time the value of one of the tags specified in the Read/Write Information table changes.
Y A change of state of any tag generates a write request of its value, regardless of the specified triggers or of other values.

484 / FactoryLink Device Interfaces Using EDI Technology

TELEMECANIQUE | 21 Telemecanique Configuration Tables

N No exception writes. Write operations are only generated when the value of the write trigger and its change of state bit are forced to 1. All of the values are written, regardless of the status of their change of state bit.

It is possible to configure both exception write and block write actions in the same table.
Block Read Priority Block Read Trigger

(Optional) Not used. A FactoryLink real-time database digital tag that, when forced to 1 (ON), triggers a block read of the values specified in the Telemecanique Read/Write Information table. The Read Trigger is normally defined in another FactoryLink task such as the Event and Interval Timer, Math and Logic, or Client Builder.
Valid Entry: tag name Valid Data Type: digital

Block Read Disable

A digital tag that, when set to 1 (ON), disables the block read action on this table.
Valid Entry: tag name Valid Data Type: digital

Block Read Complete

A digital tag of the database forced to 1 (ON) by the PLC Interface task once the block read of this table is complete. If this tag is defined when the PLC Interface task is initialized, the value of this tag is forced to 1 (ON). The Read Completed tags are valid only if a different table is used for each logical port.
Valid Entry: tag name Valid Data Type: digital

Block Read State

A digital tag of the database with a value set to 0 (OFF) when a block read operation on the tags specified in the table are in progress. Once the block read operations on this table are complete, the value of this tag is set to 1 (ON). If this tag is defined when the PLC Interface task is initialized, the value of this tag is forced to 1 (ON). The Read State tags are valid only if a different table is used for each logical port.

FactoryLink Device Interfaces Using EDI Technology / 485

• • • •

21 | TELEMECANIQUE Telemecanique Configuration Tables

Valid Entry: tag name Valid Data Type: digital

Block Write Priority Block Write Trigger

(Optional) Not used A FactoryLink real-time database digital tag that, when forced to 1 (ON), triggers a block write of the values specified in the Telemecanique Read/Write Information table. The block write trigger is normally defined in another FactoryLink task such as the Event and Interval Timer, Math and Logic, or Client Builder.
Valid Entry: tag name Valid Data Type: digital

Block Write Disable

A digital tag that, when set to 1 (ON), disables the block write action on the tags specified in this table.
Valid Entry: tag name Valid Data Type: digital

Block Write Complete

A digital tag of the database forced to 1 (ON) by the PLC Interface task once the block write of this table is complete. If this tag is defined when the PLC Interface task is initialized, the value of this tag is forced to 1 (ON). The Block Write Complete tags are valid only if a different table is used for each logical port.
Valid Entry: tag name Valid Data Type: digital

Write State

A digital tag of the database with a value set to 0 (OFF) when a block write operation on the tags specified in the table are in progress. Once the block write operations on this table are complete, the value of this tag is set to 1 (ON). If this tag is defined when the PLC Interface task is initialized, the value of this tag is forced to 1 (ON). The Block Write State tags are valid only if a different table is used for each logical port.
Valid Entry: tag name Valid Data Type: digital

486 / FactoryLink Device Interfaces Using EDI Technology

TELEMECANIQUE | 21 Telemecanique Configuration Tables

The following table shows an example of entries in the various fields:

In this example, table te_rwtable1 is defined. Reading unsolicited data is not interpreted. A change of state by any tag causes the value of this tag to be written, regardless of the status of the triggers or of the other values (Exception Write = Y is set). The block read and write priority levels are set to the highest value, 1. When the value of tag te_read equals 1 (ON), a block read of the values specified in the Read/Write Information table is performed. When the value of tag te_rdisable equals 1 (ON), block reading of table te_rwtable1 is disabled. Once all of the block read operations for this table are complete, the PLC Interface task forces the value of the te_rcomp tag to 1. The value of the te_rstate tag changes to 0 while table te_rwtable1 is being read. When the value of tag te_write equals 1 (ON), a block write of the values specified in the corresponding Read/Write Information table is enabled. When the value of tag te_wdisable equals 1, block writing of the values specified in table te_rwtable1 is disabled. Once all block write operations for this table are complete, the PLC Interface task force the te_wcomp tag to 1. The value of the te_wstate tag is 0 when the table te_rwtable1 is being written. Once all of the information is entered, open the Read/Write Information table.

FactoryLink Device Interfaces Using EDI Technology / 487

• • • •

21 | TELEMECANIQUE Telemecanique Configuration Tables

The values entered in this table identify Telemecanique PLC objects that are: • Read and transferred to the real-time database when the block read trigger requests a block read of the table specified in the Table Name field • Written from the real-time database when the block write trigger requests a block write of the table specified in the Table Name field. The data entered in this table is assigned to the table whose name is specified in the Table Name field. If this name is incorrect, the user must return to the Read/Write Control screen, and place the cursor on the name of the table to be filled in, then display the Read/Write Information screen once again. Specify the following data for each PLC object to read or write:
Station Name Logical Station

Comment field to associate the logical station number to the corresponding XTEL station name. A number (defined in the Logical Station Configuration table) that identifies the physical attributes required by the read and write operations on the tag.
Valid Entry: 0 to 999 (default=0)

All logical station numbers entered must first be defined in the Logical Station Information table.
Tag Name

The name of the tag whose value is updated when a block read action is performed or which is sent to the PLC when a block write action is performed. Symbolic representation of the PLC object to read or write.
Valid Entry: See “FactoryLink and TSX/PMX PLC Data

PLC Object

Objects” on page 500.

488 / FactoryLink Device Interfaces Using EDI Technology

TELEMECANIQUE | 21 Telemecanique Configuration Tables

The following table shows an example of entries in the various fields:

In this example, the tag te_pl1 is updated when a block read or a block write operation is performed in relation to logical station 2 (the symbolic name of the X-TEL station is LSTA2). The Telemecanique object to read or write is word W0. Once all data is entered, click the Save icon to validate it. Exit to Configuration Explorer.

FactoryLink Device Interfaces Using EDI Technology / 489

depending on the type of configuration requested. In your server application. This field must be filled in according to the type of communications: Communications Type Valid Entry MAPWAY 1 card MAPWAY 2 card UNI-TELWAY COM port TEMAP1 TEMAP2 TEUTW1 490 / FactoryLink Device Interfaces Using EDI Technology . The following table is displayed.• • • • 21 | TELEMECANIQUE System Configuration Table S YSTEM C ONFIGURATION TABLE These tables allow the user to configure executable files to run. open System > System Configuration > System Configuration Information. Specify the following information: Flags Task Name This field must be filled in with FR to automatically start the task at run time.

Task Message. Display Name. Task Status.TELEMECANIQUE | 21 System Configuration Table Communications Type Valid Entry ETHWAY 1 card ETHWAY 2 card FIPWAY 1 card FIPWAY 2 card Programming port (PCX) TCP/IP 1 card TCP/IP 2 card ISAWAY 1 ISAWAY 2 Leave the following fields as previously completed. Start Trigger. Priority FactoryLink Device Interfaces Using EDI Technology / 491 . Start Order. Display Status. Display Description. TEETH1 TEETH2 TEFIP1 TEFIP2 TETSXPC TEIP1 TEIP2 TEISA1 TEISA2 Description.

you can start only one FactoryLink task at a specific time. 492 / FactoryLink Device Interfaces Using EDI Technology .• • • • 21 | TELEMECANIQUE System Configuration Table Executable File This field must be filled in with BIN/TECOM for the task to start. This field must be filled in according to the type of communications: Communications Type Valid Entry Program Arguments MAPWAY 1 card MAPWAY 2 card FIPWAY 1 card FIPWAY 2 card UNI-TELWAY COM port ETHWAY 1 card ETHWAY 2 card Programming port (PCX) XWAYIP 1 XWAYIP 2 ISAWAY1 ISAWAY2 1 2 3 4 5 6 7 8 11 12 13 14 Note: In case of redundancy where two physical networks are connected to the same PLC.

• XWAY-TCPI network: Contact your sales representative. Refer to the TSX DM ETH PC 10M documentation for full instructions on installing this board. Refer to the TSX DM FPC 10M documentation for full instructions on installing this board. It also lets the user determine the appropriate entries for the value of the first slave address. -XWAY Network Interface Cards • FIPWAY network: Use the half-length TSX FPC 10M interface board. FactoryLink Device Interfaces Using EDI Technology / 493 . • ISA-WAY network: Contact your sales representative. This software can be ordered using the reference TXT LF UTW V50. • ETHWAY network: Use the half-length TSX ETH PC10M interface board. last slave address. • MAPWAY network: Use the full-length TSX MAP PC7 42M interface board. and the TW7 fields in the Telemecanique Logical Station Configuration table described previously. Configuring Telemecanique Networks This subsection describes the various communication devices that can be connected to a FactoryLink system and to PLCs to form a network. • UNI-TELWAY COM Port network: A specific UNI-TELWAY software driver must be previously installed to use the standard Serial COM port for UNI-TELWAY communication protocol. Refer to the TSX DM MAP PC7 M documentation for full instructions on installing this board.TELEMECANIQUE | 21 Reference R EFERENCE Connecting to XWAY Networks The PC computer and its installed XWAY network interface card connect directly to the appropriate network.

FactoryLink is always seen as slave. To improve communication efficiency between FactoryLink and a PLC or a UNI-TELWAY bus.SYS configuration file. to the communication device. For other XWAY protocols.xx PLCs can only poll 8 addresses if connected through the TER port. Response time may be important if UNI-TE network has a lot of connection points. the first slave/cost slave addresses are used to define the number of communication sockets to be used. All FactoryLink requests travel through the master. Note the TSX 37. UNI-TE is a master-slave protocol. first slave and last slave are used to define the number of communication sockets to be used. The communication devices use the first slave address only for unsolicited messages and the successive addresses (from the first address + 1 to the last address) for message data. This allows FactoryLink to send/receive up to 15 messages at a time to/from the network. This protocol is used with PCX PLC board. 4 to 18. FactoryLink can send/receive requests to/from the master for between 2 to 15 slave addresses. For example. TSX programming port can handle a maximum of 2 communication sockets. assign the slave numbers. These settings must be compatible with “the number of addresses” declared in the CONFIG. To make use of this characteristic. This slave addresses characteristic does not apply to MAPWAY/ETHWAY/FIPWAY/ISAWAY/XWAYIP. 494 / FactoryLink Device Interfaces Using EDI Technology . 5-15 on ETHWAY asks for 10 communication sockets. specify the value 4 in the First Slave Address Field and the value 18 in the Last Slave Address Field in the Telemecanique Logical Station Control Information table. To do this.• • • • 21 | TELEMECANIQUE Reference Configuring the Slaves and the TW7 Data Fields This additional information is required to determine the appropriate data required for entry into the various fields in the Telemecanique Logical Station Control Information table: First and Last Slave Addresses A UNI-TELWAY bus can have up to 253 slave addresses as 0 is reserved for the master).

When running. and set the value to 50 7 Click "OK" to validate your modifications 8 Exit the Network Configuration Panel. FactoryLink Device Interfaces Using EDI Technology / 495 . The master will have to retry several times the request and to wait each time the response timeout. In fact. Note: The performance may degraded if a PLC on the network is broken. FactoryLink tries to connect to the PLCs defined in the configuration tables. Connections may take several minutes if the network has a significant number of slaves. XWAY Configuration Drivers Xway driver default settings (ETHWAY. UNI-TELWAY) must be tuned for FactoryLink: For ETHWAY driver.Number of Send Buffers". any slave declared and missing will have slow down the pool cycle. and set the value to 50 6 Select "8 . The new settings are now active. 2 Select the ETHWAY01 or ETHWAY02 protocol 3 Click "Properties" 4 Click the "Advanced" tab 5 Select "7 . one to collect the data and another where FactoryLink will be the only slave. This degradation can be minimized by changing the RetryPeriod parameter of the ETHWAY driver from the default of 800 to 100. For best performances.TELEMECANIQUE | 21 Reference It is recommended to declare the exact number of slaves in the master PLC. follow this procedure: 1 Open the Control Panel and double-click the Network Icon. install a PLC with two UNI-TEL networks. FIPWAY.Number of Receive Buffers".

1. 2 Double-click cnffip. if a message must transit via a TELWAY network to reach its final destination. Advanced Configuration. select ETHWAY01 or ETHWAY02. 3 Set the value 50 to SBUF et RBUF.exe.• • • • 21 | TELEMECANIQUE Reference For Windows 2000 1 Open the Control Panel and double-click the Network Icon. 2 On the Protocols tab of the Network property sheet. refer to the procedure for UNI-TELWAY. However. xdosdrv = Folder where the drivers XWAY are installed. For FIPWAY version 2. 496 / FactoryLink Device Interfaces Using EDI Technology . Messages transferred by a TELWAY network cannot be more than 32 bytes in length. where x:\ = Base folder where the driver fip is installed.1 or earlier 1 Rename the dll x:\xdosdrv\cnffip_y. 3 Click "Properties". specify YES in the TW7 field in the Telemecanique Logical Station Configuration table. 3 Select File. g for german. For UNI-TELWAY 1 Run icon UNI-TELWAY. _y= f for french. advanced configuration. 4 Set 50 to SBUF et RBUF For versions later than 2. 4 Set Retry Period field to 100.dll. TW7 Messages of up to 128 bytes in length can be transferred by UNI-TELWAY or MAPWAY. e for english. 2 Select File. 5 Click OK to enter the modification.dll in cnffip.

Example 1: 1 FactoryLink. or TELWAY (see Example 2). FactoryLink communicates with the PLCs on these lower level networks by way of the PLC common to both networks. control a lower level network of interconnected PLCs via UNI-TELWAY. ISAWAY. The drop number specifies which group of stations the messages are sent to. In this example. A lower level UNI-TELWAY bus is connected to LSTA4 and a lower level TELWAY network is connected to LSTA0. Network Example 1 FactoryLink X-WAY Network Device LSTAO Example 2: 1 FactoryLink system. Each PLC can. All other logical devices (LSTAx) are slaves. A MAPWAY/ETHWAY/FIPWAY/ISAWAY/XWAYIP network has neither master nor slave addresses. XWAYIP. In this example. 3 networks. 1 network. ETHWAY.TELEMECANIQUE | 21 Reference Network Examples FactoryLink communicates directly with the PLCs via UNI-TELWAY or MAPWAY/ETHWAY/FIPWAY (see example 1). and 1 PLC. A UNI-TELWAY bus has one master. and 8 PLCs. FactoryLink communicates with LSTA0 on the MAPWAY network. in turn. Each PLC on a network must be assigned the same drop number as the group of stations to which it belongs. FactoryLink communicates with LSTA0 and LSTA4 via a MAPWAY network. FIPWAY. MAPWAY. FactoryLink Device Interfaces Using EDI Technology / 497 .

• • • • 21 | TELEMECANIQUE Reference Network Example 2 Monitor 77/2 LSTA 8 TO 23 X-WAY Network (net = 1) (Sta (1)) (Sta (2)) Device LSTAO (Drop0) TELWAY Network (net = 2) (sta1) Device LSTA4 (Drop1) Device LSTA5 (Drop1) Device LSTA6 (Drop1) Device LSTA7 (Drop1) Slave 17 Slave 16 Master Device LSTA1 (Drop0) UNI-TELWAY Network (sta3) Device LSTA2 (Drop0) Device (sta5) Slave 18 LSTA3 (Drop0) 498 / FactoryLink Device Interfaces Using EDI Technology .

TELEMECANIQUE | 21 Reference The configuration of these networks and of the lower level networks is set in the Telemecanique Logical Stations Configuration table: TELEMECANIQUE Logical Stations Control Logical Port 1 Logical Network Station Number 0 1 2 3 4 5 6 7 1 2 2 2 1 1 1 1 Station Number TYPE TEMAP1 TELEMECANIQUE Logical Station Information Gate Number Module Device Number Number TW7 Drop 1 1 3 5 2 2 2 2 0 0 0 0 0 5 5 5 0 0 0 0 0 3 3 3 0 0 0 0 0 74 75 76 NO YES YES YES NO NO NO NO 0 0 0 0 1 1 1 1 FactoryLink Device Interfaces Using EDI Technology / 499 .

Data Type Conversion Each FactoryLink tag specified in the Tag Name field in the read and write tables is assigned a FactoryLink data type. the software interface converts the type of data from a FactoryLink data object to a PLC data object type. In the same way. The following types of data objects are supported by the PLCs: • Bit: BIT • Single-length word (16-bits): WORD • Double-length word (32-bits): DWORD • Double-length floating point word objects: FDWORD • Text (only for unsolicited data): TXT • FactoryLink supports the following data types: • Digital • Analog • Long Analog • Floating-point • Message (only for reading unsolicited data) 500 / FactoryLink Device Interfaces Using EDI Technology . a corresponding PLC memory address (specified in the PL7 Object field). when writing to a PLC memory location (PL7 Object) from a FactoryLink data tag. the software interface converts the type of data from a PLC data object to a FactoryLink data object type. However. The data types supported by FactoryLink are different from those supported by the PLCs. and a PLC data type. a logical station. It also provides instructions for filling in the PL7 Object field in the Read/Write Configuration table.• • • • 21 | TELEMECANIQUE Reference FactoryLink and TSX/PMX PLC Data Objects This section describes how the FactoryLink communication system converts the various types of data supported by Telemecanique PLCs for use with FactoryLink and vice-versa. when writing to a FactoryLink data tag from its corresponding memory location in the PLC (PL7 Object).

analog and floating-point tags. The sign extension is not implemented. FactoryLink Device Interfaces Using EDI Technology / 501 . The task then converts the complete 32-bit unsigned word into a FactoryLink data tag value. The task then converts the complete 32-bit unsigned word into a PLC data object value. the task performs the following conversion: data value equal to 0. then the bit is set to 1 (digital data tags equal 0 when inactive (OFF) and 1 when active (ON)). and double-length words respectively into FactoryLink digital. Data value not 0.TELEMECANIQUE | 21 Reference Conversion Process Bit. The task places the PLC data object to convert in the LSBs of a 32-bit word and assigns the value 0 to non-significant bits. The PLC text type tags and the FactoryLink message type tags do not require conversion. If the data object is a DWORD. then the bit is set to 0. the task performs the following conversion: the 32-bit word is reduced to a 16-bit length word. If a digital type data object is required. then copied to the analog data tag. If an analog data object is required. and double-length word data objects can be converted respectively to/from FactoryLink digital. then the tag takes the value 0 (OFF). single-length word. the task performs the following conversion: data value equal to 0. single-length words and double-length word data objects. analog and floating-point data objects. single-length words. then the tag takes the value 1 (ON). If a bit type data object is required. Converting a PLC Data Object to a FactoryLink Data Object The FactoryLink communication system converts PLC data object types: bits. analog and floating-point values respectively into PLC bit. Converting a FactoryLink Data Tag Into a PLC Data Object The PLC Interface task converts FactoryLink digital. the task performs the following conversion: the 32-bit word is converted into a floating-point positive value. then copied to the FactoryLink floating-point data tag. If a floating-point data object is required. The task places the FactoryLink data object to convert in the LSBs of a 32-bit word and assigns the value 0 to non-significant bits. the 16-bit MSB data is lost. Data value not 0.

so use the ATS syntax. Entry of the corresponding symbol in the PL7 Object field is not case sensitive.• • • • 21 | TELEMECANIQUE Reference If a word type data object is required. The sign extension is not implemented.).). If a double-word data object is required. and address of the data object. function. it is still possible to use the TSX V5 syntax (Wi.. Note: PCX57 is an ATS (TSX57-xx. depending on the type... In addition. 502 / FactoryLink Device Interfaces Using EDI Technology . the task performs the following conversion: the 32-bit word is reduced to a 16-bit length word. %Si. PLC data objects (memory addresses) can be placed in the following categories: • Bit objects • Single-length word objects (WORD) • Double-length word objects (DWORD) • Double-length floating point word objects (FDWORD) • I/O objects (I/O) The names of PLC objects are specified in the PL7 Object field in the Telemecanique Read/Write Configuration table in symbolic language. Space characters are not allowed.. it is recommended to use the standard IEC syntax (%MWi. the sign and the decimal part are lost. If a logical station is assigned to a TSX 37-xx PLC type. SYi. it is cropped. Telemecanique PLC Objects Depending on the type of data used. the task performs the following conversion: the 32-bit word is entirely written to a PLC double word data object. See the following tables to determine the symbolic representations valid for PLC objects. However. then copied to a PLC single-length word. this allows it to connect to a TSX 37-xx PLC without rewriting the communication tables of an existing application. if the integer part exceeds 216-1. TSX37-xx) PLC type. The available objects are the implemented objects for ATS PLCs. If a floating-point data object is selected...

b/%SWi.b / Not implemented i : station number j : common word number b : bit number in hex. CWi/%KWi i : constant word number CWi.j/Not implemented i : station number j : common word number COMi.b i : internal word number b : bit number in hex.b/%MWi.TELEMECANIQUE | 21 Reference Bit Objects Object Symbolic representation TXS Syntax/ATS Syntax Addressing range (TSX /ATS) Internal bit Read/Write System bit Read/Write Bi/%Hi/MI i: internal bit number SYi/Si i: system bit number i = 0 to 4095 / 0 to 255 i = 0 to 127/ idea Single-Length Word Objects (WORD) Object Symbolic representation TXS Syntax / ATS Syntax Addressing range (TSX /ATS) Internal word Read/Write Bit taken from an internal word read Constant word read Bit from constant word read System word read/write Bit from system word read Common word read/write Bit from commonword read Wi/% MWi i: internal word number Wi. i = 0 to 32597 / 0 to 16384 i = 0 to 32597 / 0 to 16384 b = 0 to F i = 0 to 26206 i = 0 to 26206 b = 0 to F i = 0 to 127 i = 0 to 127 b = 0 to F i = 0 to 63 j = 0 to 63 i = 0 to 63 j = 0 to 63 b = 0 to F FactoryLink Device Interfaces Using EDI Technology / 503 . SWi/%SWi i : system word SWi.j.b i : constant word number b : bit number in hex. COMi.b/%KWi.b i : system word number b : bit number in hex.

• • • • 21 | TELEMECANIQUE Reference Double-Length Word Objects (DWORD) Object Symbolic representation TXS Syntax / ATS Syntax Addressing range (TSX /ATS) Double-length internal word Read/Write DWi / %MDi i : double internal word number i = 0 to 32596 / 0 to 16384 i = 0 to 32596 / 0 to 16384 b = 0 to 1F i = 0 to 26206 Bit from double-length DWi.b internal word i : double internal word number read b : bit number in hex.b i : float internal word number i = 0 to 32596 / 0 to 16384 i = 0 to 32596 / 0 to 16384 The floating-point numbers are stored with IEEE single precision format (32 bits) inside the PLC and with IEEE double precision format (64 bits) inside FactoryLink. Double-Length Floating-Point Word Objects (FDWORD) i = 0 to 26206 b = 0 to 1F Object Symbolic representation TXS Syntax / ATS Syntax Addressing range (TSX /ATS) Double-length FCDWi / %KFi floating point constant i: constant float word number word read Double-length floating point word read/write FCDWi.b / %MFi.b constant word i : double constant word number read b : bit number in hex.b / %KDi. Double-length constant CDWi / % KDi word i : double constant word number read Bit from double-length CDWi. 504 / FactoryLink Device Interfaces Using EDI Technology .b / %MDi.

y : module number in hex. I/O objects (I/O) Object Symbolic representation TXS Syntax / ATS Syntax Addressing range (TSX /ATS) Discrete I/O module input bit read Discrete I/O module output bit write Register bit read Ixy. b : bit number in hex. i : word number IWxy.b / Not implemented x : rack number in hex. IWxy.i.TELEMECANIQUE | 21 Reference This may induce a lost of precision when exchanging data between the PLC and FactoryLink.b / Not implemented x : rack number in hex. b : bit number in hex.b / Not implemented x : rack number in hex. i : word number b : bit number in hex. y : module number in hex. y : module number in hex.i / Not implemented x : rack number in hex. y : module number in hex.P/V/R/D / Not Implemented i : timer number P : preset value V : current value R : timer running D : timer done x = 0 to F y = 0 to 7 b = 0 to F x = 0 to F y = 0 to 7 b = 0 to F x = 0 to F y = 0 to 7 i = 0 to 7 x = 0 to F y = 0 to 7 i = 0 to 7 b = 0 to F x = 0 to F y = 0 to 7 i = 0 to 7 i = 0 to 511 i = 0 to 127 Bit from read register word read Write register word Bit assigned to Grafcet read Read Timer FactoryLink Device Interfaces Using EDI Technology / 505 . i : word number Xi / Not implemented i : step number Ti.i / Not implemented x : rack number in hex. Oxy. y : module number in hex. OWxy.

The list is: • Saved variables ( %Mi ) • Non-saved variables ( %Vi ) • Common words ( %Si ) 506 / FactoryLink Device Interfaces Using EDI Technology .• • • • 21 | TELEMECANIQUE Reference I/O objects (I/O) (Continued) Object Symbolic representation TXS Syntax / ATS Syntax Addressing range (TSX /ATS) Timer Write preset word Monostable Read Ti.P / Not implemented i : counter number Ri.I / Not implemented i : register number i = 0 to 127 i = 0 to 31 Monostable Write preset word Read Up/Down Counter i = 0 to 31 i = 0 to 255 Up/Down Counter Write preset word Read register i = 0 to 255 i = 0 to 127 Register Input word write Num Objects i = 0 to 127 FactoryLink allows access to a sub-group of NUM programmed in ladder objects.P / Not implemented i : monostable number Ci.I/O/E/F / Not implemented i : register number I : input word O : output word E : empty register F : full register Ri.P/V/R / Not implemented i : monostable value P : preset value V : current value R : monostable running Mi.P/V/E/F / Not implemented i : counter number P : preset value V : current value E : upcount overflow F : downcount overflow Ci.P / Not implemented i : timer number Mi.

j i=< 77FE i=<= 77FC i=< 77FE. j<8 Read/Write %Si.W i=< 3F7E * i = Hexadecimal address of the object j = Number of the bit in the word * For this object. And in the same way two long words have to be separated by 4 unities.L %Mi.W %Vi.j i=< 77FE i=< 77FC i=< 77FE.W %Mi. only addresses where the low byte is lower or equal to H7E are allowed.L %Vi. Wi High Byte Low Byte Wi+1 Wi+2 high Byte Low Byte High Byte Low Byte FactoryLink Device Interfaces Using EDI Technology / 507 . Caution:For NUM two words are consecutive and disjoin if they are separated by 2 unities. j<8 %Vi.TELEMECANIQUE | 21 Reference Num Objects Object Symbolic Representation Num Syntax Addressing Range Saved Variables Word Double Word Bit from Word Unsaved Variables Word Double Word Bit from Word Common Word Word Read/Write Read/Write Read Read/Write Read/Write Read %Mi.

b2.L. writing of %M10A..W. Read table Tab1 = %M11.W.%M1D.W.L generates 4 requests. To take advantage of the algorithm that minimizes the number of requests.L. write a series of long word equal modulo 4.L. Wi Wi+1 b7. Writing of 3 long words from %M100.%M104.%S12.L.W generates 3 read requests.%M23.%M10D.%M10C. writing of %M10C. Write table Tab4 = %M100. Read table Tab2 = %V25.L and writing of 2 long words from %M10D.%M108. For long word. b3.%S17. writing word %S16.%M111.%M1B.L.%M10A. Write table Tab3 = %S10.%M20.L and Reading of long word %V34.W generates 1 read request of 60 words. Writing of 2 words from %S10.L.L.L.W. b2. Reading of 2 long words from %V2E.L .L.%V2E.%V2D. b0 ////////////////////////////////// b7.W.L generates 4 write requests.L.L.%V36. b5. b4.• • • • 21 | TELEMECANIQUE Reference As a result.W and writing word %S17.L. Reading of 3 long words from %V25. b6.%M25. it is recommended that you write odd word series or even word series. Reading of 7 words from %M11.W.W generates 3 write requests.%M2.W. Reading of long word %V32.%V34.W.W.W78. b5.W..L. b6.L.%V32. Examples Read table Tab0 = %M0. b4.L. b1. Reading of the word %M20 and reading of 2 words from %M23. b1.W. b0 508 / FactoryLink Device Interfaces Using EDI Technology .%M1A.%V29.L For NUM only the bits from 0 to 7 are available and are coded with the high byte of the word. b3.W.W.W.%S16.L.

L = Number of bytes to send.C = H’FC’ TXTi. Configure the CPL type text block TXT. otherwise. On a UNI-TELWAY bus. If a matching address is found.M = H’xx65’ where xx is the location of the TSX SCM module in the rack (FF for the built-in TSX SCI port) TXTi.g.L = 6 + number of usable bytes If the transmission buffer address = Wi Wi = H’network number/00’ Wi + 1 = H’gate number/station number’ Wi + 2 = H’ (64 + lowest Monitor 77 address) FE’ E.TELEMECANIQUE | 21 Reference Unsolicited Data Configuration Example When FactoryLink receives unsolicited data from a PLC. for OUTPUT with: TXTi. FactoryLink Device Interfaces Using EDI Technology / 509 . H’65FE’ Wi + 3 = Data to send Example: Master station on multi-drop bus 0. A single Message type tag must be assigned to a logical station. only the first tag encountered in the table with the lowest number will be updated.C = H’07FC’ Category/Request code TXTi. sender address + 64’ TXTi. Serial Port: • Master PLC: Unsolicited data is generated by a master PLC from a text block. it compares the UNI-TE address of the data received (a PLC and sender text block function) with the addresses of the logical stations assigned to the message type tags in the configuration tables. it automatically updates the tag assigned to this address using the data of the request received.M = H’TSX SCM slot. • Slave PLC: To send unsolicited data from a UNI-TELWAY slave to a FactoryLink system. configure the CPL type text block for OUTPUT with the following: TXTi.

sender address (H’64’ + ad1)) TXTi.T = 0 Monitor 77 reception text block number (always 0) TXTi. Configure the text block to send unsolicited data from a slave device to FactoryLink: TXTi for OUTPUT TXTi. station H’FE’) Wi + 2 = H’65FE’ (Monitor 77 address H’64’ + 1) Wi + 3 = data to send On a MAPWAY/FIPWAY/ETHWAY network: Configure the TXT type NET function block for OUTPUT with to send unsolicited data from a network station to the FactoryLink system: TXTi.A = H’Monitor 77 network/station address’ TXTi.• • • • 21 | TELEMECANIQUE Reference M77 addresses 1 to 15. ad2 = H ‘12’ (18). Slave station: ad0 = H ‘10’ (16). In these examples. ad1 = H ‘11’ (17).M = H’0375’ (slot 3. The UNI-TELWAY module is located in slot 3. the lowest FactoryLink address (H’65’) corresponds to the address of Slave 1. the lowest address is H’6E’ (100+10 in decimal notation).C = H’07FC’ (unsolicited data request code) TXTi.L = 2 + number of bytes to send Wi = H’07FC’ unsolicited data category/request code Wi + 1 = data to send 510 / FactoryLink Device Interfaces Using EDI Technology . If FactoryLink uses other slave addresses such as 10 to 25 (also referred to as data link addresses).L = 6 + n (n = number of bytes to send) Address of Buffer Wi : Wi = H’0000’ (network number 0) Wi + 1 = H’05FE’ (gate H’05’.

The third station is configured to receive unsolicited data from text block 1 of a PLC application connected to the network as station 7. the first station is configured to receive unsolicited data sent from slave 17.TELEMECANIQUE | 21 Reference Logical Station Information Table Entries Network Number Station Number Gate Number Module Number Device Number 0 0 1 FE FE 7 5 5 11 FE FE 0 74 74 0 In this example. FactoryLink Device Interfaces Using EDI Technology / 511 . The second station is configured to receive unsolicited data sent by text block 3 of the master PLC application. Unsol2: FactoryLink tag updated on reception of unsolicited data from master text block 3. Read/Write Information Table Entries for Unsolicited Read Logical Station Tag Name PL7 Object 1 2 3 Unsol1 Unsol2 Unsol3 TXT TXT TXT Unsol1: FactoryLink tag updated on reception of unsolicited data from slave 17. Unsol3: FactoryLink tag updated on reception of unsolicited data from text block 1 of station number 7 on XWAY network 1.

Ensure the UNI-TELWAY master PLC polls the range of communication slaves configured for the task.sys configuration in config. Delete the files from the FLAPP\DCT directory and restart FactoryLink. Cannot connect LPORT <lport number> Cause: Action: (UNI-TELWAY only) The master PLC does not poll the UNI-TELWAY slaves as expected. Configure the EDI table for the device.sys Cause: Action: TECOM is invoked on UNI-TELWAY.• • • • 21 | TELEMECANIQUE Error Messages E RROR M ESSAGES This section describes the messages reporting operations and error conditions that can be generated and displayed for the Telemecanique protocol module. Cannot open driver <driver name> Cause: Action: The communication task cannot open the requested associated communication driver. and the associated UNI-TELWAY driver is not installed in the system. Ensure the software driver is installed in the system. Configure the Telemecanique tables. Bad DCT file Cause: Action: The specified file is corrupt. 512 / FactoryLink Device Interfaces Using EDI Technology . Cannot read edi configuration Cause: Action: No external device definition is configured. Cannot read te__ configuration Cause: Action: No Telemecanique configuration is found. Install the UNI-TELWAY driver before invoking TECOM. Cannot find duntiw01.

Define the logical port on the Telemecanique table. Definitions on the EDI and Telemecanique tables do not match.TELEMECANIQUE | 21 Error Messages Cannot send request (no remote ack) Cause: Action: (ETHWAY only) An addressed PLC is not physically connected to the network.sys file. Cause: Action: (UNI-TELWAY only) An unexpected. Action: Logical port definition missing Cause: Action: The External Device Definition table does not have a TE__/CUSTOM logical port configured. Ensure the definitions match in both EDI and Telemecanique. Increase the timeout value in the Telemecanique Logical Station configuration table. The Telemecanique table does not define a logical port on the invoked XWAY network. unsolicited message is received. Ensure the PLC is sending unsolicited messages to the first UNI-TELWAY slave number reserved for this purpose. Modify the NBR field in the config. The physical link may have broken while requests were still waiting for a response.sys ‘NBR=’ parameter too small (mini = 2) Cause: Action: Link is spurious The UNI-TELWAY driver must be configured to respond for a minimum of two slaves. duntlw01. Link timeout from <LSTA xxx> Cause: The response from logical station <xxx> was not received within the configured timeout period. Cause: Action: Cause: Action: FactoryLink Device Interfaces Using EDI Technology / 513 . Configure the logical port on the External Device Definition table. Ensure all addressed PLCs are physically connected to the ETHWAY network.

Maximum table count reached for Exception Write Cause: Action: More than 200 exception write tables are configured. Configure the necessary read/write IO for the logical port. No response from <LSTA xxx> Cause: FactoryLink tried to read/write non-configured objects in a PLC. Action: 514 / FactoryLink Device Interfaces Using EDI Technology . Maximum table count reached for Block Read Cause: Action: More than 200 block read tables are configured. Ensure less than 200 exception write tables are configured. Ensure less than 200 block write tables are configured. Ensure less than 200 unsolicited read tables are configured. FactoryLink may have tried to read 43545 internal words but the PLC was configured for 32767 internal words. No DCT file for this port Cause: Action: No read/write IO is configured for this logical port. Check to ensure the PLC is configured with the correct range. Maximum table count reached for Unsolicited Read Cause: Action: More than 200 unsolicited read tables are configured. For example. Maximum table count reached for Block Write Cause: Action: More than 200 block write tables are configured. Ensure the first and last slave fields are configured properly.• • • • 21 | TELEMECANIQUE Error Messages Lport slaves range is too small (mini=2) Cause: Action: The Telemecanique communication task must use a minimum of two slaves. Ensure less than 200 block read tables are configured.

Install the option bit. Verify the PLC address. Unsol. Run option not found Cause: Action: The Telemecanique communications driver option bit is not validated.TELEMECANIQUE | 21 Error Messages Request refused (No station) Cause: Action: The configured PLC address does not exist on the network. Ensure the sender (PLC) addresses the message to a configured logical station. FactoryLink Device Interfaces Using EDI Technology / 515 . datagram received on unexcepted slave Cause: Action: An unsolicited message is received on an unexcepted communication socket.

• • • • 21 | TELEMECANIQUE Error Messages 516 / FactoryLink Device Interfaces Using EDI Technology .

Chapter 22 • • • Texas Instruments TIWAY This chapter contains information needed to set up and configure bidirectional communications between the FactoryLink real-time database and various devices in either of two ways: • Directly (point-to-point mode) via a COM port on the system unit • Over a TIWAY Serial Unilink network (TIWAY mode) via a COM port on the system unit through the TIWAY Host Adapter module The following table lists the supported device types for point-to-point and network communications: Point-to-Point TIWAY Serial Unilink Texas Instruments 525 Texas Instruments 530C Texas Instruments 530T Texas Instruments 535 Texas Instruments 540 Texas Instruments 545 Texas Instruments 565 Texas Instruments 545 Texas Instruments 560 Texas Instruments 565 Texas Instruments RTU Texas Instruments 5TI • Texas Instruments 520C Texas Instruments 525 Texas Instruments 530C Texas Instruments 530T Texas Instruments 535 PM550 PM550C FactoryLink Device Interfaces Using EDI Technology / 517 .

) switch 6 configurable (See Baud Rate Table.) switch 7 configurable (See Baud Rate Table.) switch 10 configurable (See Host Command Timeout Table. set up the devices as described in the following sections.) switch 9 configurable (See Host Command Timeout Table.) DIP switch 1 switch 1 up switch 2 up switch 3 down switch 4 down switch 5 configurable (See Baud Rate Table.) switch 7 configurable (See Baud Rate Table. DIP Switches Set the following switches on the Host Adapter.) switch 8 configurable (See Baud Rate Table.) switch 6 configurable (See Baud Rate Table.) switch 1 up switch 2 down switch 3 up switch 4 down switch 5 configurable (See Baud Rate Table.) switch 9 down switch 10 down DIP switch 2 518 / FactoryLink Device Interfaces Using EDI Technology .• • • • 22 | TEXAS INSTRUMENTS TIWAY Texas Instruments Setup TEXAS I NSTRUMENTS S ETUP Before completing the Texas Instruments protocol module configuration tables. (See Dip Switch Settings for NITP Protocol Table.) switch 8 configurable (See Baud Rate Table.

TEXAS INSTRUMENTS TIWAY | 22 Texas Instruments Setup Dipswitch Settings for NITP Protocol 1 2 3 4 5 6 7 8 9 10 Dipswitch 1 U P Host Command timeout TIWAY I Baud Rate Up Down Up Down Up Down Up Synchronous Asynchronous Full Duplex Half Duplex NRZI NRZ NITP U P 1 2 3 4 5 6 7 8 9 10 Dipswitch 2 Up Down Up Down Test Mode Run Mode HIU/EHA & IO Loop Test MHIU/EHA Host Port Baud Rate Up Down Up Down Up Down Up Down Synchronous Asynchronous Full Duplex Half Duplex Even Parity Odd Parity Parity Enabled Parity Disabled FactoryLink Device Interfaces Using EDI Technology / 519 .

and 8. 7. 7. Set the host PC's (PC running FactoryLink) port baud rate with DIP switch 2 switches 5. 6.• • • • 22 | TEXAS INSTRUMENTS TIWAY Texas Instruments Setup Baud Rate Set the TIWAY Serial Unilink network baud rate with DIP switch 1 switches 5. Baud rates for the TIWAY Serial Unilink network and the host PC's port may be configured differently. Use the following information to set the baud rate on DIP switches 1 and/or 2: Switches 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 0 1 0 1 1 = Up Baud Rate 110 150 300 600 1200 2400 4800 9600 19200 38400 57600* 115200* 0 = Down *These values are not available on the Host Port Up 1 Down 0 520 / FactoryLink Device Interfaces Using EDI Technology . and 8. 6.

TEXAS INSTRUMENTS TIWAY | 22 Texas Instruments Setup Timeout Use the following information to set the host PC's command timeout: DIPSWITCH 1 Position 9 10 Description 0 sec .Accepts No Host Commands (SANM) 10 sec Timeout 20 sec Timeout 40 sec Timeout Down Down Down Up Up Up Down Up FactoryLink Device Interfaces Using EDI Technology / 521 .

25/HDLC FULL/HALF SYNC/ASYNC BAUD NETWORK ADDRESS Desired Setting REMOTE (ONLINE) OFF OFF NRZI HDLC HALF ASYNC 115. 522 / FactoryLink Device Interfaces Using EDI Technology . change the corresponding switches for the Host Adapter.• • • • 22 | TEXAS INSTRUMENTS TIWAY Texas Instruments Setup DIP Switches for TIWAY NIM Use the following information to set DIP switches for each NIM: Dipswitch Settings for TIWAY NIM Switch LOCAL/REMOTE KEYDELAY LCKBIT NRZI/NRZ X.2K 1-254 ARE VALID ADDRESSES Note If you are changing the baud rate of the TIWAY Serial Unilink network.

Valid Entry: alphanumeric string of up to 31 characters The following table provides sample entries for the Texas Instruments TIWAY Unilink Setup table: Field Logical Port for UNILINK Entry Description 0 Specifies the logical communication path configured by this table Port 1 communicates with a TIWAY Host Adapter Comment Port 1 as MHIU FactoryLink Device Interfaces Using EDI Technology / 523 . open Device Interfaces > Texas Instruments. In your server application. to represent a particular communication path to a TI device. Specify the following information: Logical Port for UNILINK Enter a number. you do not need to configure this table. C ONFIGURING THE U NILINK S ETUP TABLE Open the Unilink Setup table.TEXAS INSTRUMENTS TIWAY | 22 Accessing the Texas Instruments Tables A CCESSING THE TEXAS I NSTRUMENTS TABLES Note Before completing the protocol-specific General Electric configuration tables. you must complete the External Device Definition table. See “Identifying Protocol Types and Defining Logical Ports” on page 58 for details. If you are communicating directly (point-to-point) with a single TI PLC. defined in the External Device Definition table Logical Port column. Valid Entry: previously defined logical port number Comment Enter reference information about this logical station.

Specify the following information: Adapter Mode Specify whether a Host Adapter is the network manager. select the row for the logical port you are configuring and open the Unilink Setup Information table. For a description of these optional parameters. For more information about optional parameters for this field. (default=0) 524 / FactoryLink Device Interfaces Using EDI Technology . Valid Entry: 1 . MHIU Network Manager HIU Any other Host Adapter on the network Adapter Station Enter the address of a Host Adapter on a network. refer to the section on configuring the network manager in the TIWAY documentation.254 NM Option 1 through NM Option E (Optional) Thirteen fields that allow you to configure optional parameters for an MHIU Host Adapter.• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Unilink Setup Table From the Unilink Setup table.254 Adapter Max Station Address Enter the number of the highest physical station address on the TIWAY Serial Unilink network associated with a logical station specified in the Texas Instruments Logical Station Table. refer to the section on configuring the HIU in the TIWAY documentation. Valid Entry: Refer to the section on configuring the MHIU command in the TIWAY documentation. Valid Entry: 1 . Each Host Adapter on a TIWAY network must have a unique address. Valid Entry: Refer to the section on configuring the HIU in the TIWAY documentation. (default=0) HIU Option 1 through HIU Option 3 (Optional) Three fields that allow you to configure optional parameters for an HIU Host Adapter.

A-E Entry Description MHIU 5 1 1 Host Adapter is configured for MHIU mode Address for Host Adapter on the network The highest NIM address on the network is 1 Not configured because the Host Adapter is configured in MHIU mode HIU Option 1-3 0 FactoryLink Device Interfaces Using EDI Technology / 525 .TEXAS INSTRUMENTS TIWAY | 22 Configuring the Unilink Setup Table The following table provides sample entries for the Texas Instruments TIWAY Unilink Setup Information table: Field Adapter Mode Adapter Station Adapter Max Station Address NM Option 1 .9.

150. However. 9600. This entry must match the configuration of the devices communicating via this port. This entry must match the configuration of the devices communicating via this port. Parity Enter the parity error correction during transmission via this logical port. 3600. to represent a particular communication path to a TI device. Valid Entry: 5. 7. Valid Entry: 110. Refer to the device manufacturers documentation for details. 1200. 300. 2400. 8 The recommended entry is 7. However. 19200 (default=9600) Recommended entry is 19200 if using a TI PLC on a TIWAY network or 9600 if using a point-to-point TI PLC. if using hardware requiring special parameters. Complete a row for each logical port specified in the External Device Definition table you want to define as a communication path for read and write operations. 7200. Refer to the device manufacturers documentation for details. Refer to the device manufacturers documentation for details. Logical Port Enter a number. defined in the External Device Definition table Logical Port column. 600. 526 / FactoryLink Device Interfaces Using EDI Technology . Valid Entry: previously defined logical port number Baud Rate Enter the speed at which the protocol module communicates with the devices linked to FactoryLink via this logical port. This entry must match the baud rate configuration of the devices. 6. none Data Bits Enter the number of data bits used during transmission via this logical port. Stop Bits Enter the number of bits sent after a character to create a pause before the start of the next character. if using hardware requiring special parameters.• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Logical Station Control Table C ONFIGURING THE L OGICAL S TATION C ONTROL TABLE Open the Logical Station Control table. you may need to enter a different baud rate. Valid Entry: odd. Refer to the device manufacturers documentation for details. 4800. you may need to enter a different data bit. even. This entry must match the configuration of the devices communicating via this port.

Valid Entry: 0 . Odd parity checking. Specifies the communication rate. click the Save icon to validate the information. FactoryLink Device Interfaces Using EDI Technology / 527 . The response timeout is 3 seconds. in tenths of a second. if using hardware requiring special parameters. Valid Entry: tag name Valid Data Type: message When the table is complete.32000 Error Msg Tag Name (Optional) Enter a tag name for a message tag to which a text string will be written to indicate a communications error associated with this logical port. Define the data type (message) for any tag names displayed in the Tag Definition dialog box. Specifies 7 data bits in the transmission. Error messages are written to the message tag logical port 0. Timeout Enter the length of time.TEXAS INSTRUMENTS TIWAY | 22 Configuring the Logical Station Control Table Valid Entry: 1. you may need to enter a different stop bit. However. The following table provides sample entries for the Texas Instruments Logical Station Control table: Field Logical Port Entry Description 0 Baud Rate Parity Data Bits Stop Bits Timeout Status Msg Tag 9600 ODD 7 1 30 TI_LPORT0_MSG Specifies the logical communication path configured by this table. the protocol module will wait to receive a response to a read or write command before timing out. 2 The recommended entry is 1. Specifies 1 stop bit in the transmission. You must enter a value greater than 0 for the protocol module to timeout.

• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Logical Station Information Table C ONFIGURING THE L OGICAL S TATION I NFORMATION TABLE From the Logical Station Control table. Valid Entry: 0 . Later. Valid Entry: tag name Valid Data Type: analog Logical Station Enter a number to identify the logical station to which the information in this row pertains. In a read or write table. this number will identify the device to or from which data is to be sent or received. Error/Status Tag Name (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station). You can animate output-text objects to display the codes stored in an Error/Status Tag Name tag on a graphics screen. A logical station represents the combination of a logical port with a physical station.999 528 / FactoryLink Device Interfaces Using EDI Technology . you will enter this logical station number in a read or write table to represent the device defined in this row. Complete a row for each device to communicate through this logical port. Assign a unique number to each device communicating through this logical port. select the row for the logical port you are configuring and open the Logical Station Information table.

FactoryLink Device Interfaces Using EDI Technology / 529 . the physical station number is the same as the logical station number. click the Save icon to validate the information. Define the data type (analog) for any tag names displayed in the Tag Definition dialog box.) Comment (Optional) Enter reference information about this logical station. Valid Entry: alphanumeric string of up to 31 characters When the table is complete.254 (Normally. Valid Entry: 1 . enter TWY565 or PLC 565.) Valid Entry Unilink Network TWY520C TWY525 TWY530C TWY530T TWY535 TWY560 TWY565 TWYRTU TWY5TI TWY550 TWY550C Physical Station PLC525 PLC530C PLC530T PLC535 PLC540 PLC565 (indicates PM550) (indicates PM550C) Physical station address of the device with which the EDI task communicates when using this logical station in a Read/Write table.TEXAS INSTRUMENTS TIWAY | 22 Configuring the Logical Station Information Table Device Type Enter the TI PLC type to which communications are to be directed. (When using a TI545.

• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Logical Station Information Table The following table provides sample entries for the Texas Instruments Logical Station Information table: Field Error/Status Tag Name Logical Station Device Type Entry Description TI_STATION0_ STATUS 0 TWY565 Contains information about communication errors Specifies the logical communication paths. Specifies the type of device connected to the communication path. Specifies the physical station numbers associated with the logical path. PORT 0 530 / FactoryLink Device Interfaces Using EDI Technology . Physical Station 1 Comment TI.

an internal change-status indicator within the tag containing the data to be written prompts the write operation. the tag prompts FactoryLink to process this table and any other table in which the same trigger is defined. Defining tags that change value frequently as exception writes can slow down communications or result in an error message. no (default = no) FactoryLink Device Interfaces Using EDI Technology / 531 . Valid Entry: alphanumeric string of up to 16 characters Exception Write For EDI to interpret this operation as a triggered block write or as a read operation. Valid Entry: yes. Table Name Assign a name to this read or write request. when the trigger tag (Block Read Trigger for a read operation or Block Write Trigger for a write operation) is forced to 1 (ON). Define one request (table) per line and do not include spaces in the name. Any tag specified will be written to the device in its own packet (message) each time it changes. Try to make the table name reflective of the operation it represents.TEXAS INSTRUMENTS TIWAY | 22 Configuring the Read/Write Control Table C ONFIGURING THE R EAD /WRITE C ONTROL TABLE Open the Read/Write Control table. EDI writes this tag’s value to the device. accept the default of NO. In an exception write. Tip See “Application Design Tips and Techniques” on page 127 for information about triggering schemes using tags defined in this table. enter YES. If a tag is configured for an exception write and EDI recognizes this indicator is set since the last scan of the real-time database (indicating the value of the tag has changed). You can define as many tables as available memory allows. Do not specify tags expected to change at frequent and unpredictable intervals in an exception write table. Complete a row for each read or write table. If this is a triggered read or a block write table. For EDI to interpret this operation as an exception write and write tag values to the device only when those values change.

To reenable a cascaded loop or a self-triggered read table. If EDI receives two requests at the same time. it processes the request with the highest priority first. the addresses are read. Block Read Disable. however. See “Application Design Tips and Techniques” on page 127 for details. The default is 1. Block Read Complete. The highest priority is 1.• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Read/Write Control Table Block Read Priority If this is a block read operation. 532 / FactoryLink Device Interfaces Using EDI Technology . Do not define these tags If this is a write operation. this field is required. Enter a tag name for a digital tag to initiate a block read of the addresses specified in the Read/Write Information table. accept the default of 1.4 (default = 1) Note for write operations. Valid Entry: tag name Valid Data Type: digital Tip The Block Read Disable tag can be used to disable a block read operation that is either part of a cascaded loop or is self-triggered. relative to other read operations. This field defaults to 1 regardless of whether the operation being defined is a block read. Block Read Trigger The Block Read Trigger. If this is a triggered read operation. The triggering cycle will cease upon disabling. If this is a write operation. and Block Read State tags apply only to triggered read operations. enter a number to indicate the priority of this table. ignore this field. This number influences the order in which the EDI task handles the queuing of block read requests. the Block Read Trigger tag must be toggled or forced to 1. When this tag’s value is forced to 1 (ON). Valid Entry: 1 .

This tag is forced to 1 (ON) at startup. the read operation is not executed. ignore this field. After the tags defined in the Read/Write Information table are updated in the FactoryLink database. enter a tag name. the tag is set to 0 (OFF). If you need a digital tag to indicate when this operation is complete. set this tag back to 0 (OFF). enter a tag name. the state tag is forced back to 1. this field is optional. the complete tag is forced to 1 again. Valid Entry: tag name Valid Data Type: digital FactoryLink Device Interfaces Using EDI Technology / 533 . Valid Entry: tag name Valid Data Type: digital Block Read State If this is a write operation. If this is a triggered read operation. Valid Entry: tag name Valid Data Type: digital Block Read Complete If this is a write operation. ignore this field.TEXAS INSTRUMENTS TIWAY | 22 Configuring the Read/Write Control Table Block Read Disable If this is a write operation. This tag is forced to 1 (ON) at startup. enter a tag name. If you need a digital tag to indicate the state of this operation (in progress or complete). While the table is being processed. this field is optional. If you need a digital tag to disable a block read of the tags specified in this table. To reenable a block read table that is disabled. this field is optional. When this tag’s value is forced to 1 (ON). After the tags defined in the Read/Write Information table are updated in the FactoryLink database. If this is a triggered read operation. ignore this field. If this is a triggered read operation. Do not use this tag when more than one logical port is specified in a single table. even when the block read trigger is set to 1.

Enter a tag name for a digital tag to initiate a block write of the tag values specified in the Read/Write Information table to the addresses defined to receive the values. To reenable a cascaded loop or a self-triggered write table. This field defaults to 1 regardless of whether the operation being defined is a block or exception write. Valid Entry: 1 . the Block Write Trigger tag must be toggled or forced to 1. See “Application Design Tips and Techniques” on page 127 for details. this field is required.4 (default = 1) Note The Block Write Trigger. ignore this field. FactoryLink writes the values. Do not define these tags for read operations. enter a number to indicate the priority of this table. This number influences the order in which the EDI task handles the queuing of write requests. however. Block Write Disable. If EDI receives two requests at the same time. it processes the request with the highest priority first. accept the default of 1. Valid Entry: tag name Valid Data Type: digital Tip The Block Write Disable tag can be used to disable a block write operation that is either part of a cascaded loop or is self-triggered. Block Write Complete. The highest priority is 1. relative to other write operations.• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Read/Write Control Table Block Write Priority If this is a block or exception write operation. The triggering cycle will cease upon disabling. If this is a read operation. Block Write Trigger If this is a read operation or an exception write operation you do not plan to periodically disable. and Block Write State tags apply only to write operations. When this tag’s value is forced to 1 (ON). 534 / FactoryLink Device Interfaces Using EDI Technology . The default is 1. If this is a block write table or an exception write table you plan to periodically disable.

Valid Entry: tag name Valid Data Type: digital When the table is complete. the complete tag is forced to 1 again. After the data defined in this table’s Read/Write Information table is written to the device. Enter a tag name for a digital tag to disable a block write to the addresses specified in this table. the state tag is forced back to 1. enter a tag name. This tag is forced to 1 (ON) at startup.TEXAS INSTRUMENTS TIWAY | 22 Configuring the Read/Write Control Table Block Write Disable If this is a read operation or an exception write operation you do not plan to periodically disable. Valid Entry: tag name Valid Data Type: digital Block Write Complete If this is a read or exception write operation. ignore this field. If this is a block write operation. After the data defined in this table’s Read/Write Information table is written to the device. When this tag’s value is forced to 1 (ON). Define the data type (digital) for any tag names displayed in the Tag Definition dialog box. While the table is being processed. FactoryLink Device Interfaces Using EDI Technology / 535 . this field is optional. this field is optional. If you need a digital tag to indicate when this operation is complete. To reenable a block write table that is disabled. Do not use this tag when more than one logical port is specified in a single table. If this is a block write table or an exception write table you plan to periodically disable. ignore this field. ignore this field. click the Save icon to validate the information. If you need a digital tag to indicate the state of this operation (in progress or complete). set this tag back to 0 (OFF). Valid Entry: tag name Valid Data Type: digital Block Write State If this is a read or exception write operation. enter a tag name. This tag is forced to 1 (ON) at startup. this field is optional. even when the block write trigger is set to 1. If this is a block write table. the write operation is not executed. the tag is set to 0 (OFF). Do not use this tag when more than one logical port is specified in a single table.

TI_READ_STATE The value for TI_READ_STATE is set to 1 if a read operation of table READ is in progress. TI_READ_DISABLE The tag TI_READ_ DISABLE disables the block read of table READ when the value is 1. a block read of values specified by the Read/Write Information table associated with table READ occurs. and the value is 0 if it is inactive. Priority is set to 1. TI_READ_TRIGGER When the value of TI_READ_TRIGGER is 1 or (on). Table READ will perform exception writes.• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Read/Write Control Table The following table provides sample entries for the Texas Instruments Read/Write Control table: Field Table Name Exception Write Block Read Priority Block Read Trigger Entry Description READ N 1 Name of the read/write table. Default=1 Block Read Disable Block Read State Block Write Priority Block Write Trigger Block Write State 1 536 / FactoryLink Device Interfaces Using EDI Technology .

For a write table. Tag Name For a read table.TEXAS INSTRUMENTS TIWAY | 22 Configuring the Read/Write Information Table C ONFIGURING THE R EAD /WRITE I NFORMATION TABLE From the Read/Write Control table. For a Write Table – add a table entry for each tag to be written when the operation executes. float Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written. analog. specify a tag name for a tag containing a value to be written to the device.X input packed No data type Analog Analog Digital FactoryLink Device Interfaces Using EDI Technology / 537 . see “Configuring Tables for Loop Indexing” on page 543 for information about valid entries for this field. Refer to the TIWAY documentation for valid data types for each channel. For a Read Table – add a table entry for each FactoryLink tag in which data read from the device will be stored when the operation executes. Valid Entry: tag name Valid Data Type: digital. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. select the row for the table you are configuring and open the Read/Write Information table. specify a tag name for a tag in which FactoryLink will store the data read from the device. If you are using the loop indexing feature. Valid Entry FactoryLink Type NONE .variable memory K .(default) V . Valid Entry: previously defined logical station number Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field.constant memory X .

drum step current DCP .drum step preset DSC .status word Digital Digital Analog Analog Analog Analog Analog Analog Analog Analog TI 545 or TI 565 PLCs with s-memory (special-function memory) can also use the following entries: Valid Entry Description FactoryLink Type ** ** *** LVF LRSF AVF AACF LCF LKC Loop V-flags Loop ramp/soak status Analog alarm V-flags Analog alarm C-flags Loop C-flags Loop gain Analog Analog Analog Floating-point Floating-point Floating-point * ** *** Read-only.Y input packed C .• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Read/Write Information Table Valid Entry FactoryLink Type Y .timer counter preset TCC . use AVF_ instead of AVF.word input WY .CR packed WX . For point-to-point protocol modules.timer counter current DSP .drum count preset STW .word output TCP . 538 / FactoryLink Device Interfaces Using EDI Technology . Exception write only. Read-only.

Read-only. use AVF_ instead of AVF. Exception write only. setpoint Loop ramp rate of change Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Read-only. FactoryLink Device Interfaces Using EDI Technology / 539 . For point-to-point protocol modules.TEXAS INSTRUMENTS TIWAY | 22 Configuring the Read/Write Information Table Valid Entry Description FactoryLink Type LTI LTD LHA LLA LPV LPVH LPVL LODA LYDA LTS LSP LMN ** LERR LMX LHHA LLLA LRCA LRDS LRRC * ** *** Loop reset Loop rate Loop high alarm Loop low alarm Loop process variable Loop pv high limit Loop pv low limit Loop orange deviation Loop yellow deviation Loop sample rate Loop setpoint Loop output Loop error Loop bias Loop high alarm limit Loop low alarm limit Loop rate of change limit Loop ram dest.

use AVF_ instead of AVF. 540 / FactoryLink Device Interfaces Using EDI Technology . Exception write only. Read-only. For point-to-point protocol modules.• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Read/Write Information Table Valid Entry Description FactoryLink Type LRST LSDB AHA ALA APV APVH APVL AODA AYDA ATS ASP ** AERR AHHA ALLA ARCA LCFH LCFL ACFH ACFL * ** *** Loop soak time Loop soak deadband Analog alarm high limit Analog alarm low limit Analog alarm process variable Analog alarm PV high limit Analog alarm PV low limit Analog alarm orange deviation Analog alarm yellow deviation Analog alarm sample rate Analog alarm setpoint Analog alarm error Analog alarm high limit Analog alarm low limit Analog alarm rate of change Analog C flags high order Analog C flags low order Analog C flags high order Analog C flags low order Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Analog Analog Analog Analog Read-only.

including the PLC model and the amount of memory installed in the system. If you are using the loop indexing feature. 1 .TEXAS INSTRUMENTS TIWAY | 22 Configuring the Read/Write Information Table Valid Entry Description FactoryLink Type *** * ** *** Note PORT Port ON/OFF tag type Digital Read-only. LRST.64 (used with TI 545 or TI 565 PLCs with s-memory. For point-to-point protocol modules. Address Enter the address of the memory location (word) being read or written to. leave this field blank. the Address field may need to be left blank. The system reads the value at the address and transfers it to the tag specified in the Tag Name column. FactoryLink Device Interfaces Using EDI Technology / 541 . The amount of memory assigned to each PLC data type depends on several factors. DCP. No further reads or writes occur. do not configure more than one Read/Write table to write to the same address. Exception write only.32767. If not using the loop indexing feature. After the port is reopened. see additional data types listed in the preceding table) Loop Index If you are not using loop indexing. Use of the TIWAY Network reinitializes the Unilink Host Adapter before further reads or writes occur. Valid Entry: 1 . A 0 (zero) written to this tag opens the port. A 1 (one) written to this tag closes the port associated with the logical station for this tag. Use the PORT data type only with an exception write tag. See “Loop Indexing” on page 543 for information about configuring tables for loop indexing. LRDS. and LSDB data types require you employ additional parameters to determine the Address field entry. LRRC. See “Additional Parameters for TI Data Types” on page 552 for information about these parameters. Read-only. use AVF_ instead of AVF. reads and writes will operate normally.

use only with TI 545 or TI 565 PLCs having s-memory) Alphanumeric string representing an analog tag whose value determines the loop tag. The value of this loop index variable designates one of the tags specified in the Tag Name field. The following table provides sample entries for the Texas Instruments Read/Write Information table: Field Table Name Tag Name Entry Description READ TX_DIG_01 Specifies the Read/Write table name Destination tags in the real-time database for the addresses read from the PLC Specifies the path to send the request Variables in memory addresses 1 and 50 Memory addresses Logical Station Data Type Address Loop Index 0 Y 1 NONE 542 / FactoryLink Device Interfaces Using EDI Technology . See the Data Type field description on page 537 for valid s-memory data types. LOOP5. See “Configuring Tables for Loop Indexing” on page 543 for more information about loop indexing.• • • • 22 | TEXAS INSTRUMENTS TIWAY Configuring the Read/Write Information Table (Optional. LOOP10. LOOP11. analog. LOOP8. LOOP16 (default = NONE) When the table is complete. LOOP4. LOOP6. LOOP9. LOOP15. LOOP13. The loop index variable is valid only for s-memory data types such as loop variable and analog alarms. click the Save icon to validate the information. LOOP14. LOOP12. The system reads the PLC address specified in the Logical Station and Data Type fields and writes the returned data to the loop tag specified by the value of the loop index variable. LOOP1. LOOP2. Valid Entry: NONE. LOOP3. LOOP7. or floating-point) for any tag names displayed in the Tag Definition dialog box. Define the data type (digital.

Valid Entry: tag name Valid Data Type: analog FactoryLink Device Interfaces Using EDI Technology / 543 . Configuring Tables for Loop Indexing To implement the loop indexing option. A loop index variable is an analog tag whose value specifies which of up to 64 tags (loop tags) in the real-time database that it will read or write to. The table can include up to 16 loop index variables.TEXAS INSTRUMENTS TIWAY | 22 Loop Indexing L OOP I NDEXING You can configure a TI PLC to read and write to a maximum of 64 loop tags in the FactoryLink real-time database. Next. in the Texas Instruments Read/Write Control table. configure either a write trigger or enable the exception write. A maximum of 16 loop index variables can be defined. using a loop index variable. You can animate output-text objects to display the codes stored in an Error/Status Tag Name tag on a graphics screen. Configure only one Texas Instruments Read/Write Information table to identify these loop index variables. The value of each loop index variable specifies a different loop tag in the FactoryLink real-time database. to implement the loop indexing option. The entries in the loop indexing Texas Instruments Read/Write Information table identify the analog loop index variables. configure the following tables: • One initial Read/Write table that references up to 16 loop index variables • One or more Read/Write tables that reference the loop index variables specified in the initial Read/Write table Initial Read/Write Table First. configure one Texas Instruments Read/Write table that references up to 16 loop index variables. These loop index variables constitute a loop index. Specify the following information for each loop index variable: Tag Name (Optional) Enter a tag name for an analog tag in which to store communications error codes associated with this device (logical station).

• • • • 22 | TEXAS INSTRUMENTS TIWAY Loop Indexing Logical Station Enter a number to identify the logical station to which the information in this row pertains. (default = NONE) 544 / FactoryLink Device Interfaces Using EDI Technology . LOOP11. LOOP5.999 Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. LOOP7. LOOP14. Loop index variable used only with TI 545 or TI 565 PLCs having s-memory. this number will identify the device to or from which data is to be sent or received. LOOP2.8192 Loop Index Enter an alphanumeric string representing a real-time database analog tag whose value determines the TI 545 or TI 565 loop tag. LOOP10. Valid Entry: NONE. LOOP1. You will later enter this logical station number in a read or write table to represent the device defined in this row. enter the address in the device’s memory to which the tag value will be written. LOOP9. LOOP8. LOOP16. Valid Entry: 1 . Valid Entry: 0 . LOOP6. LOOP3. enter the address in the device’s memory where the value to be stored in this tag is located. In a read or write table. A logical station represents the combination of a logical port with a physical station. LOOP15. Assign a unique number to each device communicating through this logical port. status Address For a read table. LOOP4. Valid Entry: register. LOOP12. LOOP13. For a write table.

the table resembles the following: In this example. click the Save icon to accept the information. These entries also use the loop index variable specified in the initial Read/Write table to identify loop tags in the FactoryLink real-time database to be read or written to.000 entries. FactoryLink Device Interfaces Using EDI Technology / 545 . When the Texas Instruments Read/Write table is complete. The entries in the loop indexing Texas Instruments Read/Write Information table reference each loop index variable referenced in the initial Read/Write table and the corresponding loop tags read by this variable. Specify the following information for each loop tag: Tag Name For a read table. specify a tag name for a tag in which FactoryLink will store the data read from the device. if a loop indexing Read/Write table needs to reference the analog value contained in the tag LOOPNDX1. The entries in the Loop Index field reference the loop tags in the Tag Name field that are used by the loop indexing Read/Write tables. Loop Indexing Read/Write Table Next. table FB references the 16 loop tags (listed in the Tag Name field) previously defined in the Graphics Mode Input task. The table can include up to 1. For example. you must enter LOOP1 in its Loop Index field.TEXAS INSTRUMENTS TIWAY | 22 Loop Indexing When all appropriate information is specified. configure one or more Read/Write tables for each loop index variable defined in the initial Read/Write table.

For valid data types for each channel. analog. This number was originally defined in the Logical Station Information table for the logical port through which communications with this device occurs. floating-point Logical Station Enter the number representing the device from which the data is to be read or to which the tag’s value will be written. Valid Entry: tag name Valid Data Type: digital.• • • • 22 | TEXAS INSTRUMENTS TIWAY Loop Indexing For a write table. specify a tag name for a tag containing a value to be written to the device. refer to the TIWAY documentation. Valid Entry: previously defined logical station number Data Type Specify the type of data being read from or written to the device for each tag defined in the Tag Name field. Valid Entry Description FactoryLink Type V K X Y C WX WY TCP TCC DSP DSC DCP3 STW Variable memory Constant memory X input packed Y input packed CR packed Word input Word output Timer counter preset Timer counter current Drum step preset Drum step current Drum count preset Status word Analog Analog Digital Digital Digital Analog Analog Analog Analog Analog Analog Analog Analog 546 / FactoryLink Device Interfaces Using EDI Technology .

Exception write only. For point-to-point protocol modules. Read-only.TEXAS INSTRUMENTS TIWAY | 22 Loop Indexing TI 545 or TI 565 PLCs with s-memory (special-function memory) can also use the following entries: Valid Entry Description FactoryLink Type ** ** *** LVF LRSF AVF AACF LCF LKC LTI LTD LHA LLA LPV LPVH LPVL LODA LYDA LTS LSP Loop V-flags Loop ramp/soak status Analog alarm V-flags Analog alarm C-flags Loop C-flags Loop gain Loop reset Loop rate Loop high alarm Loop low alarm Loop process variable Loop pv high limit Loop pv low limit Loop orange deviation Loop yellow deviation Loop sample rate Loop setpoint Analog Analog Analog Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point * ** *** Read-only. use AVF_ instead of AVF. FactoryLink Device Interfaces Using EDI Technology / 547 .

use AVF_ instead of AVF. Exception write only. 548 / FactoryLink Device Interfaces Using EDI Technology . setpoint Loop ramp rate of change Loop soak time Loop soak deadband Analog alarm high limit Analog alarm low limit Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Floating-point Analog alarm process variable Floating-point Analog alarm PV high limit Analog alarm PV low limit Floating-point Floating-point Analog alarm orange deviation Floating-point Analog alarm yellow deviation Floating-point Analog alarm sample rate Floating-point Read-only.• • • • 22 | TEXAS INSTRUMENTS TIWAY Loop Indexing Valid Entry Description FactoryLink Type LMN ** LERR LMX LHHA LLLA LRCA LRDS LRRC LRST LSDB AHA ALA APV APVH APVL AODA AYDA ATS * ** *** Loop output Loop error Loop bias Loop high alarm limit Loop low alarm limit Loop rate of change limit Loop ram dest. For point-to-point protocol modules. Read-only.

reads and writes will operate normally. Read-only. Use of the TIWAY Network reinitializes the Unlink Host Adapter before further reads or writes occur. A 1 (one) written to this tag closes the port associated with the logical station for this tag. No further reads or writes occur. For point-to-point protocol modules. use AVF_ instead of AVF. enter the address in the device’s memory to which the tag value will be written. After the port is reopened. Use the PORT data type only with an exception write tag. enter the address in the device’s memory where the value to be stored in this tag is located. For a write table. FactoryLink Device Interfaces Using EDI Technology / 549 .TEXAS INSTRUMENTS TIWAY | 22 Loop Indexing Valid Entry Description FactoryLink Type ASP ** AERR AHHA ALLA ARCA LCFH LCFL ACFH ACFL *** * ** *** Note Analog alarm setpoint Analog alarm error Analog alarm high limit Analog alarm low limit Analog alarm rate of change Loop C flags high order Loop C flags low order Analog C flags high order Analog C flags low order Port ON/OFF digital tag Floating-point Floating-point Floating-point Floating-point Floating-point Analog Analog Analog Analog Digital PORT Read-only. Exception write only. Address For a read table. A 0 (zero) written to this tag opens the port.

The loop index variable is valid only for s-memory data types such as loop variables and analog alarms. and LSDB data types require you employ additional parameters to determine the Address field entry. LOOP4. LOOP9. see the Data Type field description earlier in this section. Valid Entry: NONE. LOOP3. Valid Entry: 1 . LOOP1. see “Additional Parameters for TI Data Types” on page 552. For example. For valid s-memory data types. The value of this loop index variable designates one of the tags specified in the Tag Name field. LOOP6. LOOP13. DCP. LOOP8. LRDS. LOOP16. LOOP14. LOOP2. enter LOOP1. when used with the loop indexing feature. LRST. LRRC. 1 . LOOP10. For information about these parameters. LOOP12. LOOP7. which is the corresponding loop index variable specified in the Loop Index field in the initial Read/Write table. if referencing the loop tag LOOPNDX1 specified in the Tag Name field in the initial Read/Write table. LOOP5.64 (use with TI 545 or TI 565 PLCs with s-memory. see additional data types listed in the preceding table) Loop Index (Loop index variable used only with TI 545 or TI 565 PLCs having s-memory) Alphanumeric string representing a real-time database analog tag whose value determines the TI 545 or TI 565 loop tag.• • • • 22 | TEXAS INSTRUMENTS TIWAY Loop Indexing If no loop index variables have yet been specified.32767. (default = NONE) 550 / FactoryLink Device Interfaces Using EDI Technology . LOOP11. LOOP15. The system reads the PLC address specified in the Logical Station and Data Type fields and writes the returned data to the loop tag specified by the value of the loop index variable. This entry must be the same as the loop index field entry in the initial Read/Write table that corresponds to the loop tag being referenced. this field acts as a default address for the real-time database to write to at startup.

click the Save icon to validate the information. the table resembles the following sample: In this example. the value of LOOP1 designates which loop tag. The protocol module reads or writes to address 1 only if the loop index variable is 0. This prevents a meaningless read of loop tag 0. is to be read or written to. The system reads the PLC address specified in the Logical Station. When the table is complete. FactoryLink Device Interfaces Using EDI Technology / 551 . and Loop Index fields and writes the returned data to the appropriate loop tag. defined in the Tag Name field. When FactoryLink initializes the database at startup.TEXAS INSTRUMENTS TIWAY | 22 Loop Indexing When all appropriate information is specified. all tags' values are set to 0 and address 1 acts as a default loop tag number because the loop write tag's values have not yet been written. Data Type.

5 Append the converted drum and step numbers to create a four-digit hexadecimal value. DCP 1 Determine which drum to use.• • • • 22 | TEXAS INSTRUMENTS TIWAY Additional Parameters for TI Data Types A DDITIONAL P ARAMETERS FOR TI D ATA TYPES To use certain TI data types. refer to the Programming Instruction Manual for the appropriate TI PLC. 4 Convert the step number to a two-digit hexadecimal value. step 11 = 0B = 0A0B Example 2:drum 2 = 02. For information about drums. The following is a list of TI data types requiring these special parameters: • DCP • LRDS • LRRC • LRST • LSDB To determine the correct address field entry for each data type. the hexadecimal drum value must precede the step value. refer to the Programming Instruction Manual for the appropriate TI PLC. Example 1:drum 10 = 0A. you must enter a value in the Address field of the Texas Instruments Read/Write information table containing a drum and a step number or a loop and a ramp number. follow the corresponding procedure. Note In this four-digit number. step 1 = 01 = 0201 552 / FactoryLink Device Interfaces Using EDI Technology . 2 Convert the drum number to a two-digit hexadecimal value. For information about steps. 3 Determine which step to use.

the hexadecimal loop value must precede the ramp value.1 ramp 1 = 00 = 0100 Example 2: loop 10 = 0A. Use any of the loops configured in the Read/Write tables. LRRC. 2 Convert the loop number to a two-digit hexadecimal value. LRDS. Example 2:Enter 513 in the Address field in the Read/Write tables. 3 Determine which ramp to use. For information about ramps. Example 1:0A0B = 2571 Example 2:0201 = 513 Enter the decimal value in the Address field. Example 1: loop 1 = 0. LRST. refer to the Programming Instruction Manual for the appropriate TI PLC. Note In this four-digit number. 5 Append the converted loop and ramp numbers to create a four-digit hexadecimal value. and LSDB 1 Determine which loop to use. 4 Convert the ramp number to a two-digit hexadecimal value. Example 1:Enter 2571 in the Address field in the Read/Write tables. ramp 11 = 0A = 0A0A 6 Convert this hexadecimal value to decimal.TEXAS INSTRUMENTS TIWAY | 22 Additional Parameters for TI Data Types Convert this hexadecimal value to decimal. Example 1:0100 = 256 Example 2:0A0A = 2570 FactoryLink Device Interfaces Using EDI Technology / 553 .

4 Compute the 16-bit word representing the ladder logic. and display digits on the 5TI programmer to check the accuracy of the computation.• • • • 22 | TEXAS INSTRUMENTS TIWAY Computations for 5TI Sequencer Ladder Logic Code Enter the decimal value in the Address field. 3 Enter the ladder logic program address in the Address field. The construction of the 16-bit word is described in Diagram A. Use the following steps to update the ladder logic in the 5TI Sequencer: 1 Define a FactoryLink analog tag in the Read/Write Information table. 15 bits are available. The binary weights for each bit are described in Diagram B. 6 Use the tag type LEDS. Example 2:Enter 2570 in the Address field in the Read/Write tables. 2 Enter an L in the Data Type field of the Texas Instruments Read/Write Information table. In the 1010 series sequencer. C OMPUTATIONS Note FOR 5TI S EQUENCER L ADDER L OGIC C ODE This information was extracted from the 5TI2000 Programmer Operator's Manual. Example 1:Enter 256 in the Address field in the Read/Write tables. Diagram A: Bit Layout for 16-bit Sequencer Word B15 B14 B13 <Tag Type> B11 B10 <Opcode> B9 B8 B7 B6 B5 B4 B3 B2 B1 B0 <—————-Digit Keys————-> 554 / FactoryLink Device Interfaces Using EDI Technology . The 5TI Sequencer has a 16-bit word that represents the ladder logic code. Sample computations are given in Diagram C. and in the 1020 series. opcode LEDSD. 14 of these 16 bits are available for use. 5 Write IML logic to store computation into the analog tag.

511 20480+ 3072+511 -24063 FactoryLink Device Interfaces Using EDI Technology / 555 . 511 STR CR 511 4096+3072 +511 =7679 STR NOT CR 511 STRNOT CR.TEXAS INSTRUMENTS TIWAY | 22 Computations for 5TI Sequencer Ladder Logic Code Diagram B: Binary Weight Tables for Bits 10-15 Tag & Opcode B15 B14 16384 B13 8192 B12 4096 B11 2048 B10 1024 Binary Value X 7 CR STR CTR OUT MCAR S TR NOT TMR OUT NOT 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 1 1 0 0 1 1 0 0 0 1 0 1 0 1 0 1 0 1 1 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 1024 2048 3072 4096 8192 12288 16384 20480 24576 28672 Diagram C: Sample Computations STR CR.

Single-Digit Code Format ER:xxxN is a single-digit format in which one digit represents a single error condition. The ER:xxxx string in a message can contain a single-digit or a double-digit error code. Double-Digit Code Format ER:xxNN is a double-digit format in which two digits represent a single error condition. Example: err0043 4= 3= If the MSD is less than eight. two individual codes appear within a string to indicate multiple error conditions. see Chapter 11. Decoding ER Decode the ER: string by interpreting the least significant digit (LSD – rightmost integer) and the most significant digit (MSD – leftmost integer) of NN. In some cases. “Messages and Codes”.• • • • 22 | TEXAS INSTRUMENTS TIWAY Run-Time Application Messages R UN -TIME A PPLICATION M ESSAGES During EDI runtime. For information about the messages displayed for the EDI task and the format in which protocol module messages are generated. In following descriptions. if so configured. see “Configuring the Logical Station Control Table” on page 526. use Case 2 for decoding. FactoryLink generates and displays messages for the TIWAY protocol module on the Run-Time Manager screen and. see “Configuring the Logical Station Information Table” on page 528. use Case 1 for decoding. If the MSD is eight or higher. 556 / FactoryLink Device Interfaces Using EDI Technology . writes them to message or analog tags. For information about configuring an analog tag. For information about configuring a message tag. N represents significant digits and x represents digits not significant to the error.

2 Cause: Turnaround error / timeout error. Action: See the action for Error Code 01. and data format parameters.TEXAS INSTRUMENTS TIWAY | 22 Run-Time Application Messages Case 1: EDI Task or Protocol Module Errors The LSD of the xx in err 00xx identifies the error. Decode the err 00xx code according to the following guidelines: MSD The MSD of xx signifies one of the following conditions: 1 Cause: Invalid data returned. Check that the Texas Instruments Logical Station Control table contains the proper baud rate. Action: Verify device configuration and cabling. 5 Cause: Transmit error. 3 Cause: Buffer overflow. 4 Cause: Checksum error on return data. and the MSD identifies its cause. Action: See the action for Error Code 01. parity. FactoryLink Device Interfaces Using EDI Technology / 557 . Action: See the action for Error Code 01. Action: See the action for Error Code 01. Check that FactoryLink configuration tables contain the proper station addresses and template parameters.

7 Cause: Receive DSF translate error. 2 Cause: Receiver error. 3 Cause: Receiver abort. Action: Use the action specified for the error code's MSD. 558 / FactoryLink Device Interfaces Using EDI Technology . Action: Use the action specified for the error code's MSD. Action: Use the action specified for the error code's MSD. 6 Cause: Receive invalid read length.• • • • 22 | TEXAS INSTRUMENTS TIWAY Run-Time Application Messages LSD The LSD of xx signifies one of the following conditions: 1 Cause: Unknown error detected. Action: Use the action specified for the error code's MSD. 5 Cause: Texas Instruments exception error. Action: Use the action specified for the error code's MSD. Action: Use the action specified for the error code's MSD. 4 Cause: Receiver CPT translation error. Action: Use the action specified for the error code's MSD.

Case 2: TIWAY Serial Unilink Network or Point-to-Point TI PLC Errors Use the following error code for TIWAY Serial Unilink or Point-to-Point: err 0009 Cause: Read or write is issued when the port is closed. 81 (TIWAY code: 0001) Cause: A command was timed out by the HIU function. 82 (TIWAY code: 002) Cause: TIWAY 1 HDLC ERROR . incorrect DIP switch settings. Action: Force-write a 0 to the port on/off tag defined to reopen the port. locate the TI code in the list below and refer to the TIWAY documentation. Action: Reissue the command.RESET SECONDARY. Reset the Network Manager if the error continues. For more information about TIWAY errors. or other hardware-related problems. TIWAY Serial Unilink Network exception code errors are listed below. FactoryLink Device Interfaces Using EDI Technology / 559 . Action: Consult page 6-1 in the TIWAY 1 UNILINK Host Adapter User's Manual. Action: Reset the secondary device.TEXAS INSTRUMENTS TIWAY | 22 Run-Time Application Messages Sample protocol module error err 0023 0 0 2 3 receiver abort (LSD) timeout error (MSD) This error indicates cabling problems. 83 (TIWAY code: 0003) Cause: The wrong secondary address was returned.

Action: Retransmit the command with the correct secondary address. 85 (TIWAY code: 0008) Cause: The network manager can't process secondary bits. Action: Consult the TIWAY documentation. 89 (TIWAY code: 000E) Cause: An uneven number of bytes was received from a secondary. Action: Consult the TIWAY documentation. 88 (TIWAY code: 000B) Cause: A secondary/max poll timeout occurred. in the TIWAY documentation for information about adjusting this value. command code 30. Action: Reset the adapter with the NM function. Action: Consult the TIWAY documentation. Action: Adjust the maximum poll-time value. Call the Texas Instruments Technical Services Hotline at (615) 461-2501 if the error continues. 87 (TIWAY code: 000A) Cause: A secondary timed out in the middle of a message. 8A (TIWAY code: 0010) Cause: A Data-Carrier-Detect was lost. 560 / FactoryLink Device Interfaces Using EDI Technology . Refer to Chapter 5.• • • • 22 | TEXAS INSTRUMENTS TIWAY Run-Time Application Messages 84 (TIWAY code: 0006) Cause: The command cannot use secondary address 00. 86 (TIWAY code: 0009) Cause: There is an incorrect HDLC checksum. Action: Consult the TIWAY documentation.

8C (TIWAY code: 0084) Cause: The command processor found an unrecognized command code in a command string. Action: Consult the TIWAY documentation. 90 (TIWAY code: 0088) Cause: A secondary device is not connected. Then. Action: Reconfigure the Host Adapter. 91 (TIWAY code: 0089) Cause: A colon (:) is missing from the beginning of an NITP message frame. Action: Add a colon to the frame and retransmit it.TEXAS INSTRUMENTS TIWAY | 22 Run-Time Application Messages 8B (TIWAY code: 0011) Cause: A Clear-to-Send was lost. 8E (TIWAY code: 0086) Cause: The command is too long for the command code. Action: Consult the TIWAY documentation. issue a connect secondary command or enable a macro that was previously defined to connect that secondary. FactoryLink Device Interfaces Using EDI Technology / 561 . Action: Check the address in the command string and the addresses of the secondary devices. Action: Consult the TIWAY documentation. Action: Consult the TIWAY documentation. 8D (TIWAY code: 0085) Cause: An invalid field was received with the command. e8F (TIWAY code: 0087) Cause: The command frame is too short.

96 (TIWAY code: 100C) Cause: Not enough memory for the requested secondary. de-allocate resources for a source ID. Action: To gain enough memory for the secondary status information. Action: Contact Customer Support.• • • • 22 | TEXAS INSTRUMENTS TIWAY Run-Time Application Messages 92 (TIWAY code: 008B) Cause: The char count field value does not match the received count. Refer the TIWAY documentation for information about de-allocating resources. 97 (TIWAY code: 100D) Cause: Not enough memory for another source ID. 94 (TIWAY code: 008D) Cause: An invalid character is detected. Action: Check for faulty ports and cable connections. Refer to the TIWAY documentation for information about de-allocating resources. 93 (TIWAY code: 008C) Cause: A checksum mismatch has occurred. Action: To gain enough memory for the secondary status information. Action: Contact Customer Support. 95 (TIWAY code: 100B) Cause: The HIU is not initialized. Action: Reset the Host Adapter and restart the protocol module. 562 / FactoryLink Device Interfaces Using EDI Technology . 98 (TIWAY code: 100E) Cause: The HIU is not initialized for bandwidth statistics. de-allocate resources for a source ID. Action: Consult the TIWAY documentation.

FactoryLink Device Interfaces Using EDI Technology / 563 . Action: Consult the TIWAY documentation. Action: Issue command code 30 to configure the network manager and command code 11 to configure the HIU. AD (TIWAY code: 2006) Cause: A command contains the same option code twice. AF (TIWAY code: 2008) Cause: There is a TIWAY I Ports RS232/Local Line mismatch. AB (TIWAY code: 2003) Cause: The network manager is not configured. Action: Issue command code 11. Action: Consult the TIWAY documentation. AE (TIWAY code: 2007) Cause: The HIU has already been configured. Action: Issue command code 30. AA (TIWAY code: 2002) Cause: The HIU is not configured for MHIU. AC (TIWAY code: 2004) Cause: The HIU of MHIU is not configured. Action: Consult the TIWAY documentation.TEXAS INSTRUMENTS TIWAY | 22 Run-Time Application Messages 99 (TIWAY code: 100F) Cause: You requested an illegal auto redundant mode command. Action: Correct and reissue the command.

B3 Cause: B4 Requested data not found.• • • • 22 | TEXAS INSTRUMENTS TIWAY Run-Time Application Messages TI PLC Point-to-Point errors are as follows: Note For developer actions for each error. Cause: B9 Keylock protect error. Cause: Incorrect amount of data with command. Cause: B5 Illegal task code request. B2 Cause: Address out of range. Cause: B7 Diagnostic fail upon power up. Cause: B8 Fatal error detected. B1 Action: Reset current transaction. Cause: B6 Request exceeds program memory size. 564 / FactoryLink Device Interfaces Using EDI Technology . Action: Correct the address entered in the Read or Write table. refer to the documentation for the appropriate Texas Instruments PLC.

Cause: C2 Invalid data sent with command. Cause: C0 Data not inserted. Cause: BE Illegal number of ASCII characters received. FactoryLink Device Interfaces Using EDI Technology / 565 . Cause: BD Write operation did not verify. Cause: BF Illegal write to program memory. Cause: No response from special function mode.TEXAS INSTRUMENTS TIWAY | 22 Run-Time Application Messages BA Cause: BB Illegal request in operational mode. Cause: C3 Invalid op with NIM Local/Remote mode. Cause: C4 Store and forward buffer is busy. Cause: C1 Data not written. Cause: BC Network not deleted.

memory is not mult. of block sz. 566 / FactoryLink Device Interfaces Using EDI Technology .cannot perform operation. Cause: D1 Port lockout is active. memory < minimum defined value. Cause: I/O configuration error. Cause: C8 No response from Programmable Controller. Cause: CC Req. memory < maximum defined value.• • • • 22 | TEXAS INSTRUMENTS TIWAY Run-Time Application Messages C5 Cause: C6 Illegal instruction in program mem. Cause: CD PLC busy . Cause: C7 Attempted write to protected variable. Cause: CB Req. Cause: C9 Requested memory size exceeds total memory. Cause: CA Req. Cause: CE Comm error in HOLD mode.

Code Message String B2 C6 8C 3 (MSD) 84 92 4 (MSD) 93 8B 91 Address out of range Attempted write to protected variable Bad command in string Buffer overflow Cannot use secondary address 00 Char count field doesn't match received count Checksum error on return data Checksum mismatch Clear to Send lost Colon (:) missing from start FactoryLink Device Interfaces Using EDI Technology / 567 . and all TI PLCs on the system can be written to a real-time database message tag for display as message strings on a developer-defined graphic screen. Locate the error code next to the message string to determine the cause and appropriate action for each message string. Texas Instruments Message Strings Error messages generated by the EDI task. use that code to see the Case 1 or Case 2 Errors in this chapter. Then. Error message strings and their corresponding codes appear alphabetically in the following table.TEXAS INSTRUMENTS TIWAY | 22 Run-Time Application Messages Sample Point-to-Point Error err 00B2 0 0 B 2 Address out of range This error indicates that the address specified in the Read/Write table is out of range. the protocol module.

• • • • 22 | TEXAS INSTRUMENTS TIWAY Run-Time Application Messages Code Message String CD 8F AD 81 8E 8A BF C0 B6 B7 AE 95 98 AA AC D1 99 C5 BD BA B4 BE B9 86 94 Comm error in HOLD mode Command frame too short Command has option code twice Command timed out by HIU function Command too long for command code Data Carrier Detect lost Data not inserted Data not written Diagnostic fail upon power up Fatal error detected HIU already configured HIU not initialized HIU not initialized for bandwidth statistics HIU not yet configured for MHIU HIU of MHIU not configured I/O configuration error Illegal auto redundant mode command Illegal instruction in program mem Illegal number of ASCII characters received Illegal request in operational mode Illegal task code request Illegal write to program memory Incorrect amount of data with command Incorrect HDLC checksum Invalid character detected 568 / FactoryLink Device Interfaces Using EDI Technology .

cannot perform operation Port Lockout is active Receive DSF translate error Receive invalid read length Receiver abort Receiver CPT translation error Receiver error Req. of block sz Req. memory < minimum defined value Req. memory > maximum defined value Request exceeds program memory size Requested data not found Requested memory size exceeds total memory FactoryLink Device Interfaces Using EDI Technology / 569 .TEXAS INSTRUMENTS TIWAY | 22 Run-Time Application Messages Code Message String 1 (MSD) C1 8D C2 B8 BB 85 AB C7 C4 97 96 CC CE 7 (LSD) 6 (LSD) 3 (LSD) 4 (LSD) 2 (LSD) CA C9 CB B5 B3 C8 Invalid data returned Invalid data sent with command Invalid field with command Invalid op with NIM Local/Remote mode Keylock protect error Network was not deleted NM can't process secondary bits NM is not configured No response from Programmable Controller No response from special function module Not enough memory for another source ID Not enough memory for requested secondary PLC busy . memory is not mult.

• • • • 22 | TEXAS INSTRUMENTS TIWAY Run-Time Application Messages Code Message String B1 90 87 88 C3 5 (LSD) 0009 0009 82 AF 5 (MSD) 2 (MSD) 89 1 (LSD) BC 83 Reset current transaction Secondary device not connected Secondary timed out in message Secondary/max poll timeout Store and forward buffer is busy Texas Instruments exception error ti__dsf dsf_read( ) error return .PORT CLOSED TIWAY 1 HDLC ERROR .PORT CLOSED ti__dsf dsf_write ( ) error return .RESET SECONDARY TIWAY 1 Ports RS232/Local Line mismatch Transmit error Turnaround error / timeout error Uneven # bytes from secondary Unknown error detected Write operation did not verify Wrong secondary address returned 570 / FactoryLink Device Interfaces Using EDI Technology .