Rockwell Automation 5370 CVIM User Manual

ALLEN-BRADLEY

Bulletin 5370 CVIM Configurable Vision Input Module

Communications Manual

Important User Information

Solid state equipment has operational characteristics differing from those of electromechanical equipment. “Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls” (Publication SGI-1.1) describes some important differences between solid state equipment and hard–wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.

In no event will the Allen-Bradley Company be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, the Allen-Bradley Company cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Allen-Bradley Company with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of the Allen-Bradley Company is prohibited.

Throughout this manual we use notes to make you aware of safety considerations.

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property

damage, or economic loss.

Attentions help you:

• identify a hazard

• avoid the hazard

• recognize the consequences

Important: Identifies information that is especially important for successful application and understanding of the product.

PLC is a registered trademark of Allen-Bradley Company, Inc. Pyramid Integrator, DTL and CVIM are trademarks of Allen-Bradley Company, Inc. VAX is registered trademark of Digital Equipment Corporation.

CVIM Module Communications Manual

A–B

Using this Manual

Introduction

Chapter 1

Chapter Objectives 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Revision 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of this Manual 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Intended Audience 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related Publications 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Use this Manual 1–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Nomenclature 1–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Trademarks 1–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2

Chapter Objectives 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How is Data Stored in the CVIM Module? 2–1. . . . . . . . . . . . . . . . . . . . . .

How Does the Host Device Read Results/Configuration Information? 2–1

Remote I/O (Node Adapter) 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RS–232 Ports 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Local I/O 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pyramid Integrator Backplane 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What Types of Information Can Be Communicated? 2–4. . . . . . . . . . . . . .

Discrete Bit Information 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Results Blocks 2–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 2–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Communications Cables 2–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Memory Addressing 2–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Host Designation 2–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multiple Hosts 2–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using Local I/O

Chapter 3

Chapter Objectives 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipment Connections 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Planning Output Line Assignments 3–2. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the Output Line Planning Sheet 3–2. . . . . . . . . . . . . . . . . . . . . . .

Using Output Signal Timing Data 3–7. . . . . . . . . . . . . . . . . . . . . . . . . .

Planning Output Line Connections 3–10. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connections to RS–232 Ports (2807-N27 Interface Box) 3–10. . . . . . . .

Connections to RS–232 Ports (2807-N21 Interface Box) 3–11. . . . . . . .

CVIM Module I/O Interface Box Connections 3–12. . . . . . . . . . . . . . . .

Connections to 1771-JMB Interface 3–15. . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

CVIM Module Communications Manual

Using the Remote I/O Link (Node Adapter)

Using the RS–232 Ports

Chapter 4

Chapter Objectives 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote I/O Communications 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What Functions Can Be Performed Over the Remote I/O Network? 4–6. .

Obtaining Inspection Result Information 4–7. . . . . . . . . . . . . . . . . . . . . . .

CVIM Module Configuration Instructions 4–7. . . . . . . . . . . . . . . . . . . . . .

Accessing Discrete Bit Information 4–8. . . . . . . . . . . . . . . . . . . . . . . . .

Example Program for Accessing/Setting Discrete Bit Data 4–11. . . . . . .

Accessing Results and Configuration Information 4–14. . . . . . . . . . . . . . . .

Transferring Results Blocks 4–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Results Block 4 and Statistics Block Formats 4–16. . . . . . . . .

Converting Results Data 4–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transferring Configuration Blocks 4–19. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transferring Template Blocks 4–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Program for Accessing Results Data 4–21. . . . . . . . . . . . . . . . . . .

Example Program for Accessing Configuration Data 4–25. . . . . . . . . . . . . .

Example 6008-SI Program 4–29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5

Chapter Objectives 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RS–232 Communications 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASCII and DF1 Protocols 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipment Connections 5–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What Functions Can Be Performed Over the RS–232 Interfaces? 5–3. . . .

CVIM Module Configuration Instructions 5–4. . . . . . . . . . . . . . . . . . . . . .

ASCII Protocol 5–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview 5–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASCII Character Set 5–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Command Structure 5–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

XON/XOFF Flow Control 5–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deactivated Forces 5–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Echoing Data 5–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Enable/Disable Outputs 5–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Forcing Local I/O 5–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Loading Configurations 5–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Lock Command 5–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Read Output Status 5–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Read Configuration Blocks 5–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Read Inspection Results 5–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Save Configuration 5–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Select Image Displayed 5–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Set Configurable Results 5–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Set/Read Configurable Statistics 5–17. . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

CVIM Module Communications Manual

Using the RS–232 Ports

Chapter 5 (continued)

Trigger Operation 5–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Unlock Command 5–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Write Configuration (W), Write Configuration (WC) 5–19. . . . . . . . . . .

Command Summary 5–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Explanation of ASCII Programming Example 5–23. . . . . . . . . . . . . . . . .

ASCII Programming Example 5–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DF1 Protocol 5–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What is DF1? 5–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DF1 Character Set 5–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Command Structure 5–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACK/NAK, BCC Characters 5–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block Check Character 5–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deactivate Forces 5–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Echoing Data 5–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Enable/Disable Outputs 5–31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Forcing Local I/O 5–31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Loading Configurations 5–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Lock Command 5–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Read Output Status 5–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Read Configuration Block Command 5–34. . . . . . . . . . . . . . . . . . . . . . .

Read Results Command 5–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Save Command 5–41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Select Image Displayed 5–41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Set Configurable Results 5–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Set/Read Configurable Statistics 5–45. . . . . . . . . . . . . . . . . . . . . . . . . . .

Trigger Operation Command 5–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Unlock Command 5–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Write Configuration Blocks 5–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Command Summary 5–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DF1 Programming Summary 5–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the Pyramid Integrator Backplane

Chapter 6

Chapter Objectives 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What Information Can Be Accessed 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . .

Host Designation 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What Functions Can Be Performed Over the Backplane? 6–2. . . . . . . . . .

CVIM Module Configuration Instructions 6–2. . . . . . . . . . . . . . . . . . . . . .

Obtaining Inspection Results Information Using a PLC –5/250 6–3. . . . . .

Manipulating Configuration Data Using a PLC –5/250 6–4. . . . . . . . . . . .

Sample PLC–250 Program 6–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Obtaining Inspection Result Information Using a MicroVAX

Information Processor 6–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iii

Table of Contents

CVIM Module Communications Manual

Results/Configuration Data Overview

Discrete Bit Results Bits (Host Input and Output Bits)

Numerical Results Data

Appendix A

Introduction A–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview A–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fractional Notation A–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32 Bit Integer Format A–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Template Blocks A–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix B

Introduction B–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Discrete Bit Inputs B–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Discrete Bit Outputs B–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix C

Results Block Overview C–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block Transfer Signature C–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Results Block #1 C–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Results Block #2 C–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Results Block #3 C–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Results Block #4 C–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Statistics Block C–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Data

ASCII Conversion Table

Appendix D

Configuration Block Overview D–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Block 1 D–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 2 &3 D–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 4–6D–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 7–9D–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 10–41 D–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 42–65 D–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 66–68 D–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 69–71 D–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 72–103 D–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 104–127 D–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 128–135 D–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Blocks 136– D–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix E

Table of Contents

CVIM Module Communications Manual

Tables

Table 1.A Related Publications 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3.A CVIM Module I/O Connector: Series A CVIM Module 3–12. . . Table 3.B CVIM Module I/O Connector: Series B CVIM Module 3–13. . . Table 3.C I/O Interface Box (Catalog No. 2801-N21):

RS–232 Connector with Series A CVIM Module 3–13. . . . . . . . . . . . . .

Table 3.D I/O Interface Box (Catalog No. 2801-N21):

RS–232 Connector with Series B CVIM Module 3–13. . . . . . . . . . . . . .

Table 3.E I/O Interface Box (Catalog No. 2801-N27):

RS–232 Port A Connector with Series A CVIM Module 3–14. . . . . . . .

Table 3.F I/O Interface Box (Catalog No. 2801-N27):

RS–232 Port B Connector with Series A CVIM Module 3–14. . . . . . . .

Table 3.G I/O Interface Box (Catalog No. 2801-N27):

RS–232 Port A Connector with Series B CVIM Module 3–14. . . . . . . .

Table 3.H I/O Interface Box (Catalog No. 2801-N27):

RS–232 Port B Connector with Series B CVIM Module 3–14. . . . . . . . .

Table 3.I Output Numbering 3–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4.A CVIM Remote I/O Inputs (CVIM to PLC) if CVIM

is Rack 02 4–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4.B CVIM Remote I/O Inputs (PLC to CVIM) if CVIM

is Rack 02 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5.A ASCII Command Summary 5–21. . . . . . . . . . . . . . . . . . . . . . . . .

Table 5.B DF1 Command Summary 5–50. . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6.A Shared Memory Overview 6–3. . . . . . . . . . . . . . . . . . . . . . . . . .

Table B.1 Discrete Bit Inputs B–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table B.2 Backplane Handshake Bits B–9. . . . . . . . . . . . . . . . . . . . . . . . . .

Table B.3 Discrete Bit Outputs B–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table C.1 Numerical Results Data–Results Block 1 C–3. . . . . . . . . . . . . . .

Table C.2 Numerical Results Data–Results Block 2 C–6. . . . . . . . . . . . . . .

Table C.3 Numerical Results Data–Results Block 3 C–8. . . . . . . . . . . . . . .

Table C.4 Numerical Results Data–Results Block 4 C–12. . . . . . . . . . . . . . .

Table C.5 Programmable Results/Statistics Block Configuration C–13. . . . .

Table C.6 Statistics Block C–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table D.1 Configuration Block #1 System Environment D–2. . . . . . . . . . .

Table D.2 Configuration Blocks #2 & 3 Camera Definition D–4. . . . . . . . .

Table D.3 Configuration Blocks #4–6

Reference Lines 1–3 (Toolset 1) D–5. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table D.4 Configuration Blocks #7–9

Reference Windows 1–3 (Toolset 1) D–6. . . . . . . . . . . . . . . . . . . . . . . .

Table D.5 Configuration Blocks #10–41 Gages 1–32 (Toolset 1) D–7. . . . .

Table D.6 Configuration Blockss #42–65 Windows 1–24 (Toolset 1) D–9. Table D.7 Configuration Blocks #66–68

Reference Lines 1–3 (Toolset 2) D–10. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table D.8 Configuration Blocks #69–71

Reference Windows 1–3 (Toolset 2) D–11. . . . . . . . . . . . . . . . . . . . . . . .

Table D.9 Configuration Blocks #72–103 Gages 1–32 (Toolset 2) D–12. . . .

Table D.10 Configuration Blocks #104–135 Windows 1–24 (Toolset 2) D–14

Table D.11 Polygon Configuration Blocks #128–135 D–15. . . . . . . . . . . . . .

Table of Contents

CVIM Module Communications Manual

Figures

Figure 2.1 CVIM Module Communications Ports 2–2. . . . . . . . . . . . . . . .

Figure 2.2 Bit Numbering 2–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3.1 Local I/O Equipment Connections 3–1. . . . . . . . . . . . . . . . . . . .

Figure 3.2 Timing Diagram – Pulsed I/O 3–6. . . . . . . . . . . . . . . . . . . . . . .

Figure 3.3 Timing Diagram – Trigger #2 During Data Valid, Pulsed I/O 3–7

Figure 3.4 Timing Diagram – Non-Pulsed I/O 3–8. . . . . . . . . . . . . . . . . . .

Figure 3.5 Timing Diagram – Missed Trigger 3–9. . . . . . . . . . . . . . . . . . . .

Figure 3.6 Pinouts – I/O Interface Box (Catalog No. 2801-N27) 3–10. . . . .

Figure 3.7 Pinouts – I/O Interface Box (Catalog No. 2801-N21) 3–11. . . . .

Figure 3.8 Local I/O Board (Catalog No. 2801-JMB) 3–16. . . . . . . . . . . . .

Figure 4.1 PLC-5 to CVIM Module – Remote I/O Link 4–2. . . . . . . . . . . .

Figure 4.2 6008 SI IBM PC/AT Scanner to CVIM Module –

Remote I/O link 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4.3 6008 SV VME Scanner to CVIM Module –

Remote I/O link 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4.4 6008 SQH1/2 Q–Bus Scanner to CVIM Module –

Remote I/O link 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4.5 Mini PLC-2 to CVIM Module – Remote I/O link 4–3. . . . . . . .

Figure 4.6 PLC-2 to CVIM Module – Remote I/O link 4–3. . . . . . . . . . . .

Figure 4.7 PLC-3 to CVIM Module – Remote I/O link 4–4. . . . . . . . . . . .

Figure 4.8 PLC-5/250 to CVIM Module – Remote I/O link 4–4. . . . . . . . .

Figure 4.9 Typical Hardware Layout for Remote I/O 4–5. . . . . . . . . . . . . .

Figure 5.1 RS-232 Equipment Connections 5–2. . . . . . . . . . . . . . . . . . . . .

Figure 5.2 RS–232 Cabling 5–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6.1 32 Bit Long Integer Files 6–5. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure A.1 Fractional Notation A–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using this Manual

Chapter

Chapter Objectives

Read this chapter to familiarize yourself with the rest of the manual. You will learn about:

• Contents of the manual.

• Intended audience.

• How to use the manual.

Software Revision

Overview of this Manual

Chapter Title Purpose

1 Using This Manual Provides an overview. 2 Introduction Describes the basic options available for communications with the CVIM module. 3 Using Local I/O Describes how to use the discrete I/O module (Catalog No. 1771–JMB).

5 Using the RS–232 Ports

Appendix

Using the Remote I/O Link

(Node Adapter)

Using the Pyramid

Integrator Backplane

Results/Configuration Data

Overview

Discrete I/O Results Bits Provides a description of the 128 discrete input bits and 128 discrete output bits.

Numerical Results Data Provides a description of inspection results data.

Configuration Data Provides information on the configuration blocks.

ASCII Conversion Chart Provides equivalent values for the ASCII character set.

Glossary

Index

This manual describes how to communicate with a CVIM module (Catalog No. 5370–CVIM Series A or B) with at least firmware revision C03.

This manual explains how to communicate with the Bulletin 5370 Configurable Vision Input Module (CVIM) module using a variety of peripheral devices.

Describes how to access data through the remote I/O port with a PLC–2, or PLC–3, PLC–5. Includes sample programs.

Describes how to access data through the RS–232 interfaces using ASCII and DF1 formatted commands. Provides sample programs.

Describes how to access shared memory through the Pyramid Integrator backplane using a PLC-5/250 information processor and/or MicroVAX

Provides an overview of the configuration and results data. Describes data formats.



. Provides sample programs.

1–1

Chapter 1

Using this Manual

Intended Audience

This manual was written for an experienced PLCR user or computer programmer. The user of this manual should:

• Know how to program the host device being used to communicate with

the CVIM module. For example, if you are using a PLC–5 to communicate with the CVIM module, you must have a background in programming a PLC–5.

• Know terms common to the computer and programmable controller

industries.

• Understand how to operate and configure the CVIM module before using

this manual. You may not understand many of the terms being used unless you have read the CVIM User’s Reference Manual, Catalog No. 5370–ND001.

1–2

Chapter 1

Using this Manual

Related Publications

Publication No. Title Purpose of Publication

Catalog No. 5370–ND003

Catalog No. 5370–ND001

1772–6.8.1 PLC–2/20 Programming and Operations Manual

1772–6.8.3 PLC–2/30 Programming and Operations Manual

1772–6.8.6 Mini–PLC–2/05 Programming and Operations Manual

1772–6.8.2 Mini–PLC–2/15 Programming and Operations Manual

1775–6.7.1 PLC–3 Controller Installation and Operations Manual

1785–6.8.2 PLC–5 Family Processor Manual 5000–2.3 Allen–Bradley Pyramid Integrator Technical Overview Provides an overview of the Pyramid Integrator.

5000–2.17 Allen–Bradley Pyramid Integrator Technical Description Provides a technical description of the Pyramid Integrator. 5000–2.20 MicroVAX Information Processor Technical Description

5000–6.2.10 Allen–Bradley Pyramid Integrator Installation Manual

5000–6.2.10 Allen–Bradley Pyramid Integrator Start–up and Integration Manual

Table 1.A lists related publications that you may require:

Table 1.A Related Publications

CVIM Quick Start Manual Describes the basics of the CVIM user interface.

CVIM User’s Manual

Provides step–by–step procedures for the installation, configuration and operation of the CVIM module.

Provides instructions on how to program a PLC–2/20 programmable controller.

Provides instructions on how to program a PLC–2/30 programmable controller.

Provides instructions on how to program a Mini–PLC–2/05

Provides instructions on how to program a Mini–PLC–2/15

Provides instructions on how to program a PLC–3 programmable controller.

Provides instructions on how to program a PLC–5 programmable controller.

Provides a technical description of the MicroVAX Information Processor.

Provides instructions on installing Pyramid Integrator devices.

Provides instructions on how to use Pyramid Integrator devices.



programmable controller.



programmable controller.



1–3

Chapter 1

Using this Manual

How to Use this Manual

When using this manual, we recommend that you do the following.

1. Become familiar with the CVIM module by reading the User’s Manual, Catalog No. 5370–ND001. If possible, use the CVIM module to become familiar with its operation. Only with a thorough understanding of the CVIM module will you be able to interpret the data that is stored in its memory.

2. Read Chapters 1 and 2 of this manual. After reading these introductory chapters, you will be able to determine which of the remaining chapters, some or all, you will need to read. See note below.

Important Note: This manual is divided into chapters. It is not necessary to read all of the information contained in this manual. Chapters 1 and 2 are mandatory. You can read the remaining chapters on a “need to know basis” depending upon the information you want to read or write and the type of host device you are using.

3. Use the programming examples provided in each section as a guide to create your own programs. In some applications, you may be able to simply modify the example provided.

These examples are included solely for illustrative purposes. Because the many variables and special requirements associated with any particular installation, Allen–Bradley Company cannot assume responsibility or liability for their applicability to your own situation.

Nomenclature

Trademarks

1–4

In this Chapter and in subsequent chapters we refer to the Bulletin 5370 Configurable Vision Input Module as CVIM module. In some tables we use the abbreviation “PI” to indicate the PLC–5/250 Pyramid Integrator. We have also provided a glossary in the back of this manual. Use this glossary whenever you are unsure of the meaning of a word.

In this manual, we use the following trademarks:

CVIM is a trademark of Allen–Bradley PLC, PLC–2, PLC–2/20, PLC–2/30, PLC–2/05,



PLC–2/15

, and PLC–3 PLC– 5, PLC–5/250 Pyramid Integrator Dataliner RediPANEL DATAMYTE



is a trademark of Allen–Bradley



is a trademark of Allen–Bradley



is a registered trademark of Allen–Bradley



are registered trademarks of Allen–Bradley



are trademarks of Allen–Bradley



is a trademark of Allen–Bradley

Microsoft is a registered trademark of Microsoft Corporation MicroVAX is a registered trademark of Digital Equipment Corporation GW BASIC is a trademark of Microsoft Corporation

Introduction

Chapter

Chapter Objectives

How is Data Stored in the CVIM Module?

How Does the Host Device Read Configuration/Results Information?

In this chapter we provide you with an overview of the options for communicating with the CVIM module. We also describe the types of data that can be accessed or manipulated. The descriptions in this chapter will enable you to determine the type of communications most suitable for your application. You then can proceed to the chapter of this manual that describes the selected option.

The result and command data that you can access with a host device is stored in an area of Random Access Memory (RAM) inside the CVIM module. Configuration data which controls the operating instructions for the CVIM module is located in a separate area of memory which can be also be accessed through a host device. Refer to Appendix A for an overview of configuration/results memory. Appendix B, C, and D contain tables listing the information stored in results and configuration memory locations.

The remainder of this chapter describes the various options you have for accessing this information. Refer to Figure 2.1. In summary, your host device will be linked to the CVIM module through one of the following ports:

• Remote I/O (Node Adapter)

• RS–232 Interface(s)

• Pyramid Integrator Backplane

• Local I/O Board

Note: The local I/O board has sixteen discrete I/O lines. Fourteen of these lines are outputs only . One of the remaining lines is for input, and can be connected to a presence–sensing device to trigger an inspection process. The other line is not used.

2–1

Chapter 2

Introduction

How Does the Host Device Read Configuration/Results Information? (cont’d)

Figure 2.1 CVIM Module Communications Ports

However if you are using the 2801-N27

I/O Interface Box with CVIM Module Series A hardware,

only RS–232 port A is active.

1771

2–2

Chapter 2

Introduction

Remote I/O (Node Adapter)

RS–232 Ports

The remote I/O port (RIO) is located on the front of the CVIM module as shown in Figure 2.1. Using the remote I/O port, you can connect the following types of devices:

• Allen–Bradley Programmable Controllers (PLC–2, –3, and –5).

• Host Computers which have the Allen–Bradley IBM Bus Scanner

(Catalog No. 6008–SI). The 6008–SI bus scanner is compatible with the A–B 6121/22 Industrial Computer, Industrial Terminal (Catalog Nos. 1784– T50, 1784–T35), or other IBM PC/AT compatible devices.

As shown in Figure 2.1, the RS–232 ports are located on the I/O Interface Boxes (Catalog No. 2801–N21, –N27). The I/O Interface Box is connected to the MODULE I/O port on the front of the CVIM module. Using the RS–232 interface(s) you can connect a variety of devices which use the RS–232 standard:

• Computers

• Operator Interfaces such as Allen–Bradley Industrial Computers and

Terminals with serial ports.

Local I/O

Pyramid Integrator Backplane

• I/O modules such as the Basic module (Catalog No. 1771–RB) or ASCII

module (Catalog No. 1771–DA).

• DATAMYTE and Dataliner (requires USER-PAK Software (Catalog No.

5370-UPK)

As shown in Figure 2.1, the local I/O consists of an I/O Board (Catalog No. 1771–JMB), I/O Interface Box (Catalog No. 2801–N21, –N27), an input and up to 14 output modules as configured by the user. The Catalog No. 2801–NC17 cable connects the I/O interface box to the CVIM module.

Using the Pyramid Integrator backplane, you can directly communicate data between the CVIM module and other devices installed in the Pyramid Integrator chassis:

• Allen–Bradley PLC–5/250

• MicroVAX Information Processor

• Pyramid Integrator Resource Manager

2–3

Chapter 2

Introduction

What Types of Information can be Communicated?

Discrete Bit Information

Depending upon the type of interface in use, you can access some or all of the information listed below:

• Warning and Pass/Fail data.

• Numerical inspection results.

• Configuration data.

With each inspection that the CVIM module performs, individual bits are set. There are 128 bits that can be read as inputs to a host device. These bits (part of the inspection results) indicate:

• Master fault.

• Mastership.

• Configuration fault.

• Module Busy flag.

• Missed Trigger flag.

• Results Valid flag.

• Inspection Tool Pass/Fail/Warning flags.

There are 128 bits that can be set as outputs by a host device to control the operation of the CVIM module. These bits control:

• Monitor display.

• Inspection trigger.

• Toolset selection.

• Enable/disable and force discrete I/O.

• Selection of operation after reject.

• Memory storage location. RAM, EEPROM, RAM Card, or external host

memory.

For more information on the 128 discrete input and 128 discrete output bits

Note:

refer to Appendix B.

2–4

Chapter 2

Introduction

Results Blocks

Configuration Blocks

Communications Cables

The results data for each inspection are stored in Random Access Memory (RAM) and overwrite the results of the previous inspection. The data stored in results blocks contain information regarding reference windows, inspection gages, inspection windows, etc. For a complete description of the results blocks, refer to Appendix C.

The user developed inspection parameters of the CVIM module are stored in the CVIM module’s memory as configuration blocks. This area of memory can be read or manipulated through the Remote I/O port, RS–232 ports (A & B) or Pyramid Integrator backplane. Refer to Appendix D for a complete description of the configuration blocks and their contents.

If you are not using the Pyramid Integrator backplane for communications, you will have to physically link the CVIM module to the host device. If you need to create a communications cable, refer to the chapter that describes the communications port you are using.

Memory Addressing

Depending upon how you access the CVIM module results and configuration memory, you will have to address the data differently. If you refer to Appendix A, B, and C you will notice that separate columns are provided for Backplane, RS–232, and Remote I/O communications:

Note:

The RS–232 protocols (ASCII and DF1) do not access data using word and bit addresses. Data is read/written in blocks. We have grouped the RS–232 and Remote I/O ports together in Appendix B, C, and D (where appropriate) for your convenience. You can ignore word and bit addresses if you are using the RS–232 ports (A & B).

2–5

Chapter 2

Introduction

Memory Addressing (cont’d)

When you communicate through the Pyramid Integrator backplane all of the data words are numbered consecutively and grouped in blocks. When you use the Remote I/O port, you select a specific block and the first word in each block is word #0.

Example of Addressing Results Block 1

Word Number

Pyramid Integrator Backplane RS–232 and Remote I/O

Toolset 1 Toolset 2

24-87 288-351

0–63

In addition, PLC I/O bit numbers are entered in octal format when referencing 1771 I/O, while PLC files and backplane communications specify a decimal bit number. Figure 2.2 illustrates how bits are numbered.

Figure 2.2 Bit Numbering

Bit Number if Accessing Data Through Remote I/O as a 1771 I/O Rack. (Octal Value)

Bit Number if Accessing Data Through the Backplane or Remote I/O Port Using Integer Files. (Decimal V alue)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 17 16 15 14 13 12 11 10 7 6 5 4 3 2 1 0

1000100001001101

Example Word

2–6

Chapter 2

Introduction

Host Designation

Multiple Hosts

There are four communications ports which you can use simultaneously to access CVIM module data (Remote I/O, RS–232 Ports A & B, and Backplane). Only the host can issue commands to control the operation of the CVIM module. You can read discrete bits and numerical results information through any of the four communications ports, even through non–host devices.

The CVIM module can operate with multiple hosts. You can select one host to perform CVIM module/host configuration transfers, and another host to perform all other CVIM/host operations. These two hosts are referred to as the configuration host (CFG) and the system host (SYS). An example of using multiple hosts is to select RS–232 A as the CFG host, and Remote I/O as the SYS host.

Note: Any CVIM communications port can be used for reading results block data regardless of whether or not the device connected to the port is selected as a host.

Note: You can select the same host (Stand Alone, Pyramid, Remote I/O, RS–232 A or B) as both the configuration host and the system host.

2–7

Chapter

Chapter Objectives

Equipment Connections

A–B

Using Local I/O

The objectives of this chapter are to help you plan:

• The number of discrete output lines (up to 14) that your application will

require.

• The function that each output line will perform in your application.

• The assignment of analysis tool “results” to output lines.

• The assignment of status signals to output lines.

• The electrical and mechanical connections of the trigger (input) and

output lines to your production equipment.

The local I/O consists of:

• I/O Interface Box (Catalog No. 2801–N21, –N27)

• I/O Board (Catalog No. 1771–JMB)

• User specified I/O modules (plug into I/O board)

• Communications Cable (Catalog No. 2801–NC17)

As shown in Figure 3.1, the communications cable (Catalog No. 2801–NC17) is connected to the MODULE I/O port on the front of the CVIM module and the connector on the I/O Interface box. The I/O board connector slides into the connector slot on the I/O Interface Box.

Figure 3.1 Local I/O Equipment Connections

3–1

Chapter 3

Using Local I/O

Planning Output Line Assignments

Using the Output Line Planning Sheet

This section provides a planning sheet that you can use to lay out the function and tool assignments for output lines.

The term “function assignment” refers to the type of signal information that you want an output line to carry to your production equipment.

The term “tool assignment” refers to the tool(s) that you assign to an output line.

Note: Tools can be assigned only to output lines that you have assigned a “results” function. These output lines will carry the “pass/fail” results signals from the tools during each inspection.

The next section, Planning Output Line Connections, provides electrical and timing diagrams and data. You will need to use these diagrams to correctly identify and connect the output lines to your production equipment.

The Output Line Planning Sheet is a form on which you can lay out your plans for each output line. On this form you can account for:

• The 14 output lines.

• The six output line functions.

• The 64 gages and their warning and fault outputs.

• The 48 windows and their warning and fault outputs.

• The 6 reference tools and their “pass/fail” outputs.

• The light probe with its separate red, green, and blue warning and fault

outputs.

3–2

Chapter 3

Using Local I/O

Here is an example of how an Output Line Planning Sheet could be filled out:

Example CVIM Module Output Line Planning Sheet Output Line Functions and Tool Assignments

Line Output Line

No. Function

1 Results 1 1 W 2 W 1 W 2 W

″ ″ ″ 3 W 4 W

2 Results 1 1 F 2 F 1 F 2 F

″ ″ ″ 3 F 4 F 3 Results 1 1 1 4 Results 1 A W 5 Results 1 A F 6 Results 2 1 W 1 F

″ ″ ″ 2 W 2 F 7 Strobe 1 8 Trig. NAK 1 9 Master Fault 1

10 Data Valid 1 11 Module Busy NA 12 Not Used 13 Not Used 14 Not Used

Tool

Set

Set No.

No. Rng. No. Rng. No. Rng. No. Rng. Line Win. Cam. Rng.

Gage Window

Reference

Tool

Light Probe

The entries for the output lines have the following meanings:

• Output Line 1: The Results function is assigned to line 1. The Warning

Range results (W) for gages 1–4 and windows 1 and 2 of toolset #1 are assigned to output line 1.

• Output Line 2: The Results function is assigned to line 2. The Fault

Range results (F) for gages 1–4 and windows 1 and 2 of toolset #1 are assigned to output line 2.

• Output Line 3: The Results function is assigned to line 3. The “pass/fail”

results for reference line 1 of toolset #1 and reference window 1 are assigned to line 3.

• Output Line 4: The Results function is assigned to line 4. The Warning

Range result from the camera A light probe is assigned to line 4. Camera A is assigned to toolset #1.

3–3

Chapter 3

Using Local I/O

Using the Output Line Planning Sheet (cont’d)

• Output Line 5: The Results function is assigned to line 5. The Fault

Range result from camera A probe is assigned to line 5.

• Output Line 6: The Results function is assigned to line 6. The Warning

and Fault Range results for gages 1 and 2 of toolset #2 are assigned to line 6.

• Output Line 7: The Strobe function for toolset #1 is assigned to line 7.

• Output Line 8: The Trigger NAK function for toolset #1 is assigned to

line 8.

• Output Line 9: The Master Fault function for toolset #1 is assigned to

line 9.

• Output Line 10: The Data Valid function for toolset #1 is assigned to line

10.

• Output Line 11: The Module Busy function is assigned to line 11. (Note

that this function does not relate to a toolset).

• Output Lines 12–14: These lines are not used.

Note: Output lines 1–6 are assigned the Results function. These lines will

carry “pass/fail” results from the analysis tools to your production equipment. Lines 7–11 are assigned other functions. Lines 12–14 are not used.

Here is a brief explanation of the signal functions that you can assign to the output lines:

• Module Busy: This signal goes high when the CVIM system enters the

configuration mode and during a configuration download operation. Module Busy goes low when the system enters the run mode (whether or not triggers are present).

You can assign the Module Busy function to only one output line.

Note: When configurations are being downloaded to the CVIM module, the module busy signal at the JMB board is not active.

3–4

Note: All of the remaining signal functions (except Strobe, Module Busy, and Trigger NAKs) can be configured to produce a pulse whose duration depends on the number of milliseconds that you assign to the Duration/1 or Duration/2 parameter. (The ‘‘1’’ and ‘‘2’’ designate toolset #1 and toolset #2).

• 1/Results: This signal occurs when the results of a tool inspection exceed

the warning and/or fault limits. (The tool must be assigned to an output line that has already been assigned the Results function.)

Chapter 3

Using Local I/O

You can assign the Results signal function to any unassigned output line.

As noted above, the 1/Results signal function must be assigned to an output line before any tool can be assigned to that line. Thus, if you wanted inspection results from Ref. Line # 2 to be assigned to output line #10, you would first have to assign the Results signal function to output line #10.

Note: You can assign the inspection results from any tool in toolset #1 to an output line to which you have already assigned the 1/Results signal function.

• 1/Data Valid: This signal occurs when the CVIM system has completed an

inspection using toolset #1. 1/Data Valid signals (the “data”) are stable on all output lines assigned to the 1/Results signal function. 1/Data Valid goes low during the next inspection.

Note: 1/Data Valid does not indicate whether an inspection has passed or failed. That is the task of the output lines assigned to the 1/Results signal function.

You can assign the 1/Data Valid function to only one output line.

• 1/Trigger NAK: This signal occurs when the CVIM system receives a

trigger input signal for toolset #1, but cannot process that trigger. The signal goes low upon the next “accepted trigger”.

You can assign the 1/Trigger NAK function to only one output line.

• 1/Master Fault: This signal occurs when any (one or more) analysis tools

in the CVIM system detects a Fail condition. You can assign the 1/Master Fault function to only one output line.

• 1/Strobe: This signal is used to trigger the strobe flash unit (if used). The

signal occurs within 1 ms after the CVIM system receives a trigger input signal.

You can assign the 1/Strobe function to only one output.

• 1/Duration (n)ms: From 1msec to 2000msec. This value determines the

pulse duration, in milliseconds of all pulse–type signals. A setting of zero means the signal will remain in its present state until updated by a subsequent inspection.

Note: The output duration may vary if subsequent inspections occur before the specified output duration has elapsed.

In your application, the function and tool assignment(s) for each output line will of course depend on the specific requirements of your production equipment.

You will find a full–page, blank copy of the planning sheet on the last page of this chapter. We suggest that you do not mark that page, but use it instead as a copy master, and use the copies to prepare your output line plans.

3–5

Chapter 3

Using Local I/O

Using the Output Line Planning Sheet (cont’d)

Using Output Signal Timing Data

Keep in mind that a completed planning sheet can serve also as a record of your output line usage. You may find it desirable to store your filled–out planning sheets in a file folder or loose leaf binder.

To make proper use of the signal data available to the output lines, you must first understand the timing relationships that exist between the trigger input signal (which starts each inspection cycle) and the output signals.

Knowing these signal timing relationships enables you to accurately synchronize the inspection cycles with your production equipment.

Timing charts (Figures 3.2, 3.3, and 3.4) show the timing relationships in various circumstances.

Figure 3.2 shows the relationship between the trigger leading edge and the Strobe, Data Valid, and Results signals, where the last three appear as pulses whose duration you determine during configuration.

Figure 3.2 Timing Diagram — Pulsed I/O

MODULE

BUSY

Min. trigger ≈ 2ms*

Trigger

(Input)

STROBE

DATA

VALID

RESULTS

** Minimum acquisition time: 17ms for 256x256 and 512x256 Res; 34 ms for 512x512 res.

*** Analysis time (variable).

Trigger

pulse #1

Max. lag ≈ 1ms

***

Min. strobe ≈ 1ms

You can select a

pulse width of 1

to 2000ms

DATA VALID will always pulse high when inspection processing is complete.

RESULTS signal will pulse high if an analysis tool range limit is exceeded.

Trigger

pulse #2

3–6

Chapter 3

Using Local I/O

Using Output Signal Timing Data (cont’d)

In Figure 3.3, trigger pulse #2 occurs before the CVIM module has finished processing the inspection cycle started by trigger pulse #1.

Figure 3.3 Timing Diagram — Trigger #2 During Data Valid, Pulsed I/O

MODULE

BUSY

Trigger

(Input)

STROBE

DATA

VALID

RESULTS

Min. trigger ≈ 2ms*

Trigger

pulse #1

Max. lag ≈ 1ms

** ***

***

DATA VALID will always pulse high when inspection processing is complete

Trigger

pulse #2

Min. Strobe ≈ 1ms

For Trigger #1

You can select a pulse width of 1 to 2000 ms

***

For Trigger #2 For Trigger #3

Trigger

pulse #3

** Minimum acquisition time: 17ms for 256x256 and 512x256 Res; 34 ms for 512x512 res.

*** Analysis time (variable). ****RESULTS will pulse high if an analysis tool range is exceeded.

3–7

Chapter 3

Using Local I/O

Using Output Signal Timing Data (cont’d)

Whenever these signals go high, they will go low again at the end of the specified pulse duration (1 to 2000ms).

Note: The Local I/O Module Busy is high only during system configuration. In Figure 3.4, the Data Valid, and Results signals appear as changes in signal

levels. This will occur if, during system configuration, you select a pulse “duration” of 0 (zero) milliseconds. Data Valid will stay high until the leading edge of the next valid trigger signal (Trigger Pulse #2). Results stay in their current state until the leading edge of the next Trigger pulse, then change depending upon the results.

Figure 3.4 Timing Diagram — Non–Pulsed I/O

MODULE

BUSY

Trigger

(Input)

Trigger

pulse #1

Trigger

pulse #2

STROBE

DATA

VALID

RESULTS

** *

DATA VALID will go high when inspection

***

Minimum acquisition time: 17ms for 256x256 Res.; 34ms for 512x512 Res

Analysis time.

Data Valid (and results) will be sent for a minimum of 15 msec when 0

** *

pulse length is selected.

processing is complete, and will go low with the leading edge of the next valid trigger.

RESULTS signal will go high if an analysis tool range limit is exceeded.

3–8

Chapter 3

Using Local I/O

In Figure 3.5, trigger pulse #2 occurs before the CVIM system is finished processing the inspection cycle started by trigger pulse #1. This causes the Trigger NAK signal to go high. Trigger NAK will stay high until leading edge of the next valid trigger pulse (trigger pulse #3).

Figure 3.5 Timing Diagram– Missed Trigger

MODULE

BUSY

Trigger

(Input)

TRIGGER

NAK

STROBE

DATA

VALID

RESULTS

Trigger

pulse #1

Trigger

pulse #2

TRIGGER NAK goes high because trigger 2 cannot be processed. (Trigger 1 processing is not yet complete.)

TRIGGER NAK goes low because trigger 3

can be processed. (Trigger 1 processing is now complete.)

*Min. processing time:

17ms, 256x256 Res.

***

Results stay in their current state, hihg or low.

17ms, 512x256 Res. 34ms, 512x512 Res.

**Analysis time.

Trigger

pulse #3

3–9

Chapter 3

Using Local I/O

Planning Output Line Connections

Connections to RS–232 Ports (2801–N27 Interface Box)

P O R T

This section provides diagrams of electrical connections for correctly connecting your production equipment to the CVIM module’s discrete output and RS–232 lines.

Figure 3.6 shows the cable connectors and their pin numbers on the I/O Interface Box (Catalog No. 2801–N27).

Figure 3.6 Pinouts– I/O Interface Box (Catalog No. 2801–N27)

2345

789

Cable connectors to

RS–232 devices.

C V

Cable connector from Module

I/O connector on CVIM Module.

2345671089

11121314151617

20212223242526

3–10

I/O Interface Box (Catalog No.

2801–N27)

Chapter 3

Using Local I/O

Connections to RS–232 Port (2801–N21 Interface Box)

I/O Interface Box (Catalog No. 2801–N21)

Figure 3.7 shows the cable connectors and their pin numbers on the I/O Interface Box (Catalog No. 2801–N21).

Figure 3.7 Pinouts– I/O Interface Box (Catalog No. 2801–N21)

Cable connector from Module

I/O connector on CVIM Module.

2345

789

Cable connectors to

RS–232 devices.

234567

11121314151617

20212223242526

3–11

+ 172 hidden pages