Owner's manual

ManualsBrandsRockwell Automation ManualsEquipment5370 CVIM Communications Manual

ALLEN-BRADLEY

Bulletin 5370 CVIM

Configurable Vision Input Module

Communications Manual

Summary of content (202 pages)

PAGE 1
ALLEN-BRADLEY Bulletin 5370 CVIM Configurable Vision Input Module Communications Manual
PAGE 2
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.
PAGE 3
Table of Contents CVIM Module A–BCommunications Manual Using this Manual Chapter 1 Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Publications . . . . .
PAGE 4
Table of Contents CVIM Module Communications Manual Using the Remote I/O Link (Node Adapter) Chapter 4 Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Functions Can Be Performed Over the Remote I/O Network? . . Obtaining Inspection Result Information . . . . . . . . . . . . . . . . . . . . . . . CVIM Module Configuration Instructions . . . . . . . . . . . . .
PAGE 5
Table of Contents CVIM Module Communications Manual Using the RS–232 Ports Chapter 5 (continued) Trigger Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unlock Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Configuration (W), Write Configuration (WC) . . . . . . . . . . . Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Explanation of ASCII Programming Example . . . . . . . . . . .
PAGE 6
Table of Contents CVIM Module Communications Manual Results/Configuration Data Overview Appendix A Discrete Bit Results Bits (Host Input and Output Bits) Appendix B Numerical Results Data Appendix C Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fractional Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
Table of Contents CVIM Module Communications Manual Tables Table 1.A Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3.A CVIM Module I/O Connector: Series A CVIM Module . . . Table 3.B CVIM Module I/O Connector: Series B CVIM Module . . . Table 3.C I/O Interface Box (Catalog No. 2801-N21): RS–232 Connector with Series A CVIM Module . . . . . . . . . . . . . . Table 3.D I/O Interface Box (Catalog No. 2801-N21): RS–232 Connector with Series B CVIM Module . . . . . . .
PAGE 8
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.
PAGE 9
Chapter 1 Using this Manual 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 This manual describes how to communicate with a CVIM module (Catalog No. 5370–CVIM Series A or B) with at least firmware revision C03.
PAGE 10
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: • • • 1–2 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.
PAGE 11
Chapter 1 Using this Manual Related Publications Table 1.A lists related publications that you may require: Table 1.A Related Publications Publication No. Title Purpose of Publication Catalog No. 5370–ND003 CVIM Quick Start Manual Describes the basics of the CVIM user interface. Catalog No. 5370–ND001 CVIM User’s Manual Provides step–by–step procedures for the installation, configuration and operation of the CVIM module. 1772–6.8.
PAGE 12
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.
PAGE 13
Chapter 2 Introduction Chapter Objectives 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.
PAGE 14
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.
PAGE 15
Chapter 2 Introduction Remote I/O (Node Adapter) 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: • • RS–232 Ports 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.
PAGE 16
Chapter 2 Introduction What Types of Information can be Communicated? Depending upon the type of interface in use, you can access some or all of the information listed below: • • • Discrete Bit Information 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.
PAGE 17
Chapter 2 Introduction Results Blocks 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.
PAGE 18
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.
PAGE 19
Chapter 2 Introduction Host Designation 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. Multiple Hosts The CVIM module can operate with multiple hosts.
PAGE 20
Chapter A–B 3 Using Local I/O Chapter Objectives The objectives of this chapter are to help you plan: • • • • • Equipment Connections 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.
PAGE 21
Chapter 3 Using Local I/O Planning Output Line Assignments 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.
PAGE 22
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 Reference Tool Line No. Output Line Function Tool Set No. No. Rng. No. Rng. No. Rng. No. Rng. 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 4 Results 5 6 Gage Window Cam. Rng.
PAGE 23
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.
PAGE 24
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.
PAGE 25
Chapter 3 Using Local I/O Using the Output Line Planning Sheet (cont’d) 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.
PAGE 26
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 DATA VALID will always pulse high when inspection processing is complete MODULE BUSY Min. trigger ≈ 2ms* Trigger (Input) Trigger pulse #1 Trigger pulse #2 Max. lag ≈ 1ms Trigger pulse #3 Min.
PAGE 27
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.
PAGE 28
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 pulse #1 Trigger pulse #2 Trigger pulse #3 TRIGGER NAK goes high because trigger 2 cannot be processed.
PAGE 29
Chapter 3 Using Local I/O Planning Output Line Connections This section provides diagrams of electrical connections for correctly connecting your production equipment to the CVIM module’s discrete output and RS–232 lines. Connections to RS–232 Ports (2801–N27 Interface Box) 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) 5 P O R T 1 2 8 7 6 Cable connectors to RS–232 devices.
PAGE 30
Chapter 3 Using Local I/O Connections to RS–232 Port (2801–N21 Interface Box) 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) 8 9 18 7 17 26 6 16 25 5 4 15 24 14 23 3 13 22 1 2 12 21 10 11 20 19 Cable connector from Module I/O connector on CVIM Module. 5 4 9 3 8 1 2 7 6 Cable connectors to RS–232 devices. I/O Interface Box (Catalog No.
PAGE 31
Chapter 3 Using Local I/O CVIM Module I/O Interface Box Connections Tables 3.A through 3.H show the connector pin assignments with the various combinations of Series A and Series B CVIM modules connected to I/O Interface Boxes (Catalog Nos. 2801–N21, –N27) . Table 3.
PAGE 32
Chapter 3 Using Local I/O Table 3.
PAGE 33
Chapter 3 Using Local I/O CVIM Module I/O Interface Box Connections (cont’d) Table 3.E I/O Interface Box (Catalog No. 2801–N27) RS–232 Port A Connector Series A CVIM Module Pin Number Function Pin Number Function 1 No Connection 6 No Connection 2 RXD (Receive Data: RS–232 A) 7 + 5V DC 3 TXD (Transmit Data: RS–232 A) 8 No Connection 4 + 5V DC 9 No Connection 5 Ground (Signal) Table 3.F I/O Interface Box (Catalog No.
PAGE 34
Chapter 3 Using Local I/O Table 3.H I/O Interface Box (Catalog No. 2801–N27): RS–232 Port B Connector Series B CVIM Module Connections to 1771–JMB Interface Pin Number Function Pin Number Function 1 No Connection 6 No Connection 2 RXD (Receive Data: RS–232 B) 7 + 10V DC 3 TXD (Transmit Data: RS–232 B) 8 No Connection 4 + 10V DC 9 No Connection 5 Ground (Signal) The 1771–JMB interface board is designed for direct edge connection to the I/O Interface Box, Catalog Nos. 2801–N21, –N27.
PAGE 35
Chapter 3 Using Local I/O Connections to 1771–JMB Interface (cont’d) Figure 3.8 shows the layout of the 1771–JMB interface board and the adhesive–backed overlay. Figure 3.8 Local I/O Board ( Catalog No. 1771–JMB).
PAGE 36
Chapter 3 Using Local I/O Table 3.I shows the relationship between the I/O line and optic–isolator numbers shown in Figure 3.8. Table 3.
PAGE 37
Chapter 3 Using Local I/O OUTPUT LINE PLANNING SHEET Output Line Functions and Assignments Line No. 3–18 Output Line Function Gage No. Rng. Reference Tool Window No. Rng. No. Rng. No. Rng. Line Win.
PAGE 38
Chapter 4 Using the Remote I/O Link Chapter Objectives In this chapter we provide: • • • • • Remote I/O Communications Basic description of Remote I/O communications. Connection diagrams. Description of CVIM module setup requirements. Three example PLC programs for accessing CVIM module data. An example 6008–SI program. As stated earlier, the Remote I/O port is located on the front of the CVIM module and is labeled RIO.
PAGE 39
Chapter 4 Using the Remote I/O Link (Node Adapter) Remote I/O Communications (cont’d) Figure 4.1 PLC–5 to CVIM Module– Remote I/O Link 1771 I/O Rack PLC 5/15 5/25 5/30 5/40 5/60 CVIM Module Catalog No. 1770–CD Cable RIO Figure 4.2 6008 SI IBM PC/AT Scanner to CVIM Module– Remote I/O Link CVIM Module 6008 SI I/O Scanner IBM PC/AT RIO Catalog No. 1770–CD Cable Figure 4.3 6008 SV VME Scanner to CVIM Module– Remote I/O Link CVIM Module 6008 SV I/O Scanner Host Computer RIO Catalog No.
PAGE 40
Chapter 4 Using the Remote I/O Link (Node Adapter) Remote I/O Communications (cont’d) Figure 4.4 6008 SQH1/2 Q–BUS Scanner to CVIM Module–Remote I/O Link CVIM Module 6008 SQH1/2 I/O Scanner Host Computer RIO Catalog No. 1770–CD Cable Figure 4.5 Mini PLC–2 to CVIM Module– Remote I/O Link 1771 I/O Rack MINI PLC–2 2/02 2/15 2/16 2/17 CVIM Module Catalog No. 1771–SN Sub I/O Scanner Module Catalog No. 1770–CD Cable RIO Figure 4.6 PLC–2 to CVIM Module– Remote I/O Link CVIM Module Catalog No.
PAGE 41
Chapter 4 Using the Remote I/O Link (Node Adapter) Remote I/O Communications (cont’d) Figure 4.7 PLC–3 to CVIM Module–Remote I/O Link CVIM Module PLC–3 Catalog No. 1775– S4A/S4BS5/SR/SR5 I/O Scanners Catalog No. 1770–CD Cable RIO Figure 4.8 PLC–5/250 to CVIM Module– Remote I/O Link Pyramid Integrator Rack CVIM Module Remote Scanner PLC–5/250 Catalog No.
PAGE 42
Chapter 4 Using the Remote I/O Link (Node Adapter) Remote I/O Communications (cont’d) Figure 4.9 Typical Hardware Layout for Remote I/O 2705–P11J1 RediPANEL 2801 Note: You can also read the data valid signal over the remote I/O link.
PAGE 43
Chapter 4 Using the Remote I/O Link (Node Adapter) Remote I/O Communications (cont’d) When installed on a Remote I/O network, the CVIM module acts as a slave device. Another device such as a PLC or computer will act as a host device. This means that the CVIM module will not initiate the sending of any data until a request is made by the host.
PAGE 44
Chapter 4 Using the Remote I/O Link (Node Adapter) Obtaining Inspection Result Information You can obtain inspection result information for each of the inspection tools over the Remote I/O link. There are two levels of access to this information: • • Discrete Bits. These bits indicate pass/fail/warning data. Result Data Words. These words contain actual inspection result data such as measured lengths, number of black pixels, etc.
PAGE 45
Chapter 4 Using the Remote I/O Link (Node Adapter) Accessing Discrete Bit Information A PLC can directly access discrete bit information using a simple ladder program. For example: You can use the following rung to examine the data valid bit and energize an output if the data is valid. Refer to Chapter 3 for a description of the local I/O. This example assumes that the CVIM module is in Rack 02 and the output device is in Rack 01. Although the same basic information is provided in Appendix B, Tables 4.
PAGE 46
Chapter 4 Using the Remote I/O Link (Node Adapter) Accessing Discrete Bit Information (cont’d) Table 4.A CVIM Module Remote I/O Inputs (CVIM Module to PLC) if CVIM Module is Rack 02 BIT 07 ––– 17 06 ––– 16 05 ––– 15 04 ––– 14 03 ––– 13 02 ––– 12 01 ––– 11 00 ––– 10 (Not used) 1=Data Valid 0=First Bits Results 1 = Trigger Missed 1 = Module Busy 1 = PLC is Master 1 = Config.
PAGE 47
Chapter 4 Using the Remote I/O Link (Node Adapter) Accessing Discrete Bit Information (cont’d) Table 4.
PAGE 48
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program for Accessing/Setting Discrete Bit Data The following ladder logic program provides examples of: • • • • • Triggering an inspection from a PLC. Enabling/Disabling the user access to the setup mode using the lightpen. Checking for valid results. Reading and displaying pass/fail/warning tool results (Window 1, Toolset 1). Controlling screen display from a PLC.
PAGE 49
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program For Accessing/Setting Discrete Bit Data (cont’d) Ladder Listing 31 December 1989 Processor File: CVIM.ACH Page 1 Rung 2:4 Rung 2:4 When Data Valid bit is high, read the discrete results for window 1, then light the correct status light.
PAGE 50
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program For Accessing/Setting Discrete Bit Data (Cont’d) 31 December 1989 Page 1 Ladder Listing Processor File: CVIM.
PAGE 51
Chapter 4 Using the Remote I/O Link (Node Adapter) Accessing Results and Configuration Information A host also has access to actual results block information such as measured lengths, number of black pixels, etc. Transfer of result and configuration data is accomplished using block transfers.
PAGE 52
Chapter 4 Using the Remote I/O Link (Node Adapter) Transferring Results Blocks Results blocks are transferred using block transfer reads. These blocks contain inspection result information such as: tool results, fault data, etc. Of the four results blocks, three are pre–configured and one block is user configurable (refer to next section). This means that you can program the contents of the block to contain only the specific data you require.
PAGE 53
Chapter 4 Using the Remote I/O Link (Node Adapter) Configuring Results Block 4 and Statistics Block Formats Both the programmable results block and statistic blocks are configured to contain user specified results. To configure the data in results block #4: • • • • • Specify the information you want returned by setting the appropriate bits in the 10 word “programmable results / statistics block” in the PLC as shown in Table C.5 (Page C–15).
PAGE 54
Chapter 4 Using the Remote I/O Link (Node Adapter) Converting Results Data Some of the results data described in Appendix C is stored in a “16 point 16” format while other data is stored as a 32 bit integer. Refer to the following chart: WINDOW Luminance Object Pixels FORMAT 16.16* 32 bit 32bit GAGE Linear Measure Object Pixels Edge Angular Measure FORMAT 16.16 32 bit 32 bit 32 bit 16.16 Light Probe Reference Line Reference Window Reference Window Theta 16.16 16 bit 16 bit 16.16 *16.
PAGE 55
Chapter 4 Using the Remote I/O Link (Node Adapter) Converting Results Data (cont’d) Rung 2:0 This program converts CVIM 16.16 to PLC Floating Point.
PAGE 56
Chapter 4 Using the Remote I/O Link (Node Adapter) Converting Results Data (cont’d) Transferring Configuration Blocks You can transfer configuration block data between the CVIM module and CFG Host using block transfer reads and writes. These blocks contain the operating instructions for the CVIM module (refer to Appendix D).
PAGE 57
Chapter 4 Using the Remote I/O Link (Node Adapter) Transferring Configuration Blocks (cont’d) You must use the discrete I/O bits in conjunction with block transfers to inform the CVIM module of the Block Transfer Type, Toolset Number, Block Number and, Last Block by setting discrete bit information using simple ladder programming (refer to Table 4.B): • • • Set bit 1 of output word 3 to indicate a CONFIGURATION block transfer. Use bits 10 through 17 of output word 3 to indicate which block to transfer.
PAGE 58
Chapter 4 Using the Remote I/O Link (Node Adapter) Transferring Template Blocks (cont’d) Word 1, bits 8 – 15 of the first template block indicate the total number of template blocks of the configuration. You must always upload or download all of the template blocks as a unit. You cannot archive only a part of the template blocks. When uploading templates from the CVIM module, the program should read the first template block and check word 1, bits 8– 15 to determine the number of template blocks to follow.
PAGE 59
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program for Accessing Results Data, Cont’d 31 December 1989 Page 1 Ladder Listing Processor File: CVIMBLK.ACH Rung 2:0 Rung 2:0 Block Transfer Results, Toolset 1, Results Block 1.
PAGE 60
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program for Accessing Results Data, Cont’d 31 December 1989 Page 2 Ladder Listing Processor File: CVIMBLK.ACH Rung 2:5 Rung 2:5 Set n7:70 to the ”Total Triggers” Just Before Initiating this Inspection.
PAGE 61
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program for Accessing Results Data, Cont’d 31 December 1989 Page 3 Ladder Listing Processor File: CVIMBLK.ACH Rung 2:8 Rung 2:8 This Rung Resets All Flags and the Counter.
PAGE 62
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program For Accessing Configuration Data The following program provides an example of using bi–directional block transfers to: • • • Ladder Listing Rung 2:0 Transfer CVIM module configuration data to a PLC. Modify the data. In this program we move the location of Window 1, Toolset 1 up or down. Transfer the reconfigured data back to the CVIM module from the PLC. 31 December 1989 Processor File: CVIMCNFG.
PAGE 63
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program For Accessing Configuration Data Cont’d. 31 December 1989 Page 2 Ladder Listing Processor File: CVIMCNFG.ACH Rung 2:3 Rung 2:3 Read Present Configuration Data for Window 1 (42 words). | UP |BTR EN |BTW EN Window 1 DATA.
PAGE 64
Chapter 4 Using the Remote I/O Link (Node Adapter) 31 December 1989 Page 3 Ladder Listing Processor File: CVIMCNFG.
PAGE 65
Chapter 4 Using the Remote I/O Link (Node Adapter) Example Program For Accessing Configuration Data Cont’d. 31 December 1989 Page 4 Ladder Listing Processor File: CVIMCNFG.ACH Rung 2:7 Rung 2:7 Reset PB Requests, BTR BN Bit, Window 1 Data, Last Block Specifier.
PAGE 66
Chapter 4 Using the Remote I/O Link (Node Adapter) Example 6008–SI Program The following program was written using Microsoft C Version 5.10 with an Allen–Bradley 6008–SI Series B card. The program will: • • • • Prompt the user for the 6008–SI card address. This address is determined by the DIP switch settings on the card. Prompt the user for the 6008–SI card interrupt control line. This is determined by the jumper setting on the board itself.
PAGE 67
Chapter 4 Using the Remote I/O Link (Node Adapter) Example 6008–SI Program (cont’d) /* CVIM to 6008–SI sample communications program */ /* Copyright Allen–Bradley 1–12–90 jrm, */ /* This program was compiled using MicrosoftrC Version 5.1 */ #include #include /* Include the 6008–SI definitions */ #include
PAGE 68
Chapter 4 Using the Remote I/O Link (Node Adapter) /* Get CVIM rack address from the user */ printf (”Enter CVIM remote–I/O rack number (0–7): scanf (”%d”, &CVIM_rack); ”); g_oit[8*CVIM_rack + 2] |= 0x0001; /* post tool results */ /* Start of main loop */ do { printf printf printf printf printf printf (”\n\nOperations: \n\n”); (”1. Trigger Tool Set 1\n”); (”2. Read Results, Toolset 1\n”); (”3. Read Configuration\n”); (”4.
PAGE 69
Chapter 4 Using the Remote I/O Link (Node Adapter) block_num++) err = get_CVIM_block (CVIM_rack, 4 block_num+1, template[block_num], &templen{block_num]) } } break; case 4: { /* write configuration */ /* write all config.
PAGE 70
Chapter 4 Using the Remote I/O Link (Node Adapter) /* display msg for program monitoring */ printf (”get_CVIM_block %d(%d)\n”,block_type, block_num); /* Tell CVIM block number and type */ g_oit[8*CVIM_rack + 3] = block_type + block_num * 256; /* Initiate the block transfer read */ block_pkt.qbt_len = 0; /* request 0 words */ status = bt_read(16*CVIM_rack,&block_pkt); err = (status != OK); if (!err) { /* wait for completion of BTR */ while (!bt_done(&block_pkt)); err = (block_pkt.
PAGE 71
Chapter A–B 5 Using the RS-232 Ports Chapter Objectives In this chapter we describe how to: • • • Connect RS–232 device(s) to the CVIM module. Obtain results data using ASCII or DF1 protocols. Upload and download configurations. In addition, this chapter provides example programs. RS–232 Communications Using the RS–232 interface you can link a variety of devices to the CVIM module: • • • • Computers Operator Interfaces such as Allen–Bradley Industrial Computers and Terminals with serial ports.
PAGE 72
Chapter 5 Using the RS–232 Ports Equipment Connections As shown in Figure 5.1, the RS–232 ports (A & B) 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. You will need a communications cable to link your host device to the CVIM module. Refer to Figure 5.2 for diagrams of host to I/O Interface Box cabling. Figure 5.1 RS–232 Equipment Connections.
PAGE 73
Chapter 5 Using the RS-232 Ports Figure 5.2 RS–232 Cabling. DB25 Female (IBM PC/XT, VT–220, etc.) View from the back of the connector DB9 Female (IBM PC/AT) View from the back DB9 Male (CVIM) View from the back DB9 Male (CVIM) View from the back Note: Connections for Catalog No. 2801–N27 I/O Interface Box RS–232 Port A with CVIM Series B Module is shown in this illustration. Refer to Chapter 3 for other RS–232 Connections.
PAGE 74
Chapter 5 Using the RS–232 Ports CVIM Module Configuration Instructions If you are using the RS–232 ports (A or B), you must configure the CVIM module as follows: Set the Baud Rate(s) 1 1 1 1 1 Select the setup menu . Select the environment menu . Select the I/O menu . Select RS–232 communications or
PAGE 75
Chapter 5 Using the RS-232 Ports ASCII Protocol In describing the ASCII Protocol we use the following conventions: Non–printable ASCII control characters are represented as follows: [CR] = Carriage Return [LF] = Line Feed ___ = Space ASCII commands are provided in large bold characters: >RR, RB,3 [CR] Unless _ is specified, there are no spaces between characters. Some commands have fields which can contain variable data such as number of times a command is repeated, block numbers, data, etc.
PAGE 76
Chapter 5 Using the RS–232 Ports ASCII Character Set (cont’d) • Symbols: > (greater than) * (star) , (comma) – (dash) (space) represented by __ • Nonprintable control characters: CR (carriage return) LF (line feed) XON XOFF • Command Structure Numbers 0 through 9 Each command the host device sends to the CVIM module consists of an ASCII string of characters beginning with > and terminated with a [CR]. Characters in between are separated into fields by commas.
PAGE 77
Chapter 5 Using the RS-232 Ports Object Field– Object fields specify data that configures the operation of the CVIM module. There are two types of objects: 1) Toolset independent objects which do not require a toolset identifying number. 2) Toolset dependent objects which need a toolset identifying number. The object field contains alphanumeric characters which specify one or more objects. Individual objects are specified by name.
PAGE 78
Chapter 5 Using the RS–232 Ports Echoing Data (cont’d) of 1 is assumed. d is the data that is to be echoed. The command is valid at any time. For example: >E2,HELLO [CR] This example will cause the CVIM module to return the string: [CR] [LF] HELLO [CR] [LF] HELLO [CR] [LF] If you do not have the proper command structure the CVIM module will return: ?[CR] [LF] Enable/Disable Outputs Use this command to enable or disable outputs on the Local I/O Board (Catalog No. 1771–JMB).
PAGE 79
Chapter 5 Using the RS-232 Ports Another example: > F,O3–9,0 [CR] This example forces outputs 3 through 9 off. For example: > F,O4–6,1 [CR] Forces outputs 4–6 on. > F,O8,1 [CR] Forces output 8 on. >F,O1–4,0 [CR] Forces outputs 1–4 off. Notice that output #4 was forced on and then forced off. The force off takes precedence over the force on. After executing a command, the CVIM module will return: [CR][LF]. If you do not have the proper command structure the CVIM module will return: ?[CR][LF].
PAGE 80
Chapter 5 Using the RS–232 Ports Lock Command (cont’d) structure the CVIM module will return: ?[CR][LF]. Use the unlock command to enable the setup menu box. Read Output Status Use the read data command to read the status of the local I/O. This command has the following structure: >Rx,On [CR] Where n = 1 to 14 X-Y * (individual outputs) (range of outputs X through Y) (all of the outputs) This function can be executed more than once per command by specifying an x times value.
PAGE 81
Chapter 5 Using the RS-232 Ports This function can only be executed once per command. Refer to Appendix C for a description of the configuration blocks. You cannot use this command while the CVIM module is in the SETUP mode. Examples: >RC,CB135[CR] Reads configuration block 135. >RC,CB99,CB7,CB1[CR] Reads configuration blocks 1, 7, then 99. >RC,CB1–135[CR] Reads all the of configuration blocks (excluding templates). >RC,CB*[CR] Reads all the of configuration blocks (including templates).
PAGE 82
Chapter 5 Using the RS–232 Ports Read Inspection Results Use this command to read the results of the last inspection. Refer to Appendix B for a description of the results blocks. Use the following commands: >RRx,TSno,d [CR] Where: x n = = o = d = >RRx, TS1 [CR] Number of times command is repeated.
PAGE 83
Chapter 5 Using the RS-232 Ports The read operation can be executed more than once per command by specifying an x times value. The data in the read results block commands indicate which results block (1, 2, 3, or 4) is being read (refer to Appendix C). >RR0,TS1[CR] This command continuously reads the first discrete bit results for toolset 1. (24 bytes returned) >RR,TS2RB,3[CR] This command reads results block 3 for toolset 2. This operation is only performed once in this example.
PAGE 84
Chapter 5 Using the RS–232 Ports Read Inspection Results (cont’d) Numerical Results Block Returned Data Format [CR] [LF] 61_01_04_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00~00_[CR][LF] 00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00~00_[CR][LF] 00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_01_00_00_[CR][LF] 00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_32_00_00_00_00_[CR][LF] 00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_00_[CR][LF] 00_00_00_00_00_00_00_00_00_00_00_00_00_00_0
PAGE 85
Chapter 5 Using the RS-232 Ports For example: >S,CC,13 [CR] Transfers configuration data from the CVIM module RAM to the RAM card area 13. You cannot use this command when the CVIM module is in the SETUP mode. After executing a command, the CVIM module will return: [CR][LF]. No data is returned. If you do not have the proper command structure, the CVIM module will return: ?[CR][LF].
PAGE 86
Chapter 5 Using the RS–232 Ports Select Image Displayed (cont’d) Example: >W,D,2[CR] This example will display toolset 1 failed tools. After executing the command, the CVIM module will return: [CR][LF]. No data is returned. If you do not have the proper command structure, the CVIM module will return: ?[CR][LF]. Set Configurable Results Use this command to obtain a configurable results block. The results you want are specified by a list of tools and placed in results block #4.
PAGE 87
Chapter 5 Using the RS-232 Ports Set/Read Configurable Statistics Use the read command to read statistical data for the light probe, reference windows, gages, and windows. Use the separate set command to set the number of samples and configure the statistics block. The set statistics command has the following structure: >SSn,TSxd,TSxd,etc.[CR] (Set command) Where n = Number of samples Note: If n is 0, the CVIM module will continue to use the sample count configured during setup.
PAGE 88
Chapter 5 Using the RS–232 Ports Set/Read Configurable Statistics (cont’d) Example of Read Statistics Command: > RS5[CR] This example reads the statistics block five times. The data returned from the statistics block consists of: • Block signature Number of samples, maximum, minimum, average, and standard deviation for each tool configured in the block. The block signature is 2 bytes long. The number of samples is a 2 byte integer. The maximum and minimum values are each 4 bytes.
PAGE 89
Chapter 5 Using the RS-232 Ports Trigger Operation Use the trigger operation command to initiate an inspection by the CVIM module. Use the following commands: >T, TS1[CR] >T, TS2[CR] Triggers an inspection with toolset 1. Triggers an inspection with toolset 2. This function can only be executed once per command. Note: When using this command you should make sure that the CVIM module is configured for a “hosted trigger source”. After executing a command, the CVIM module will return: [CR][LF].
PAGE 90
Chapter 5 Using the RS–232 Ports Write Configuration (W) Write Configuration (WC) (cont’d) This function can only be executed once per command. Refer to Appendix D for a description of the configuration blocks. You cannot use this command when the CVIM module is in the setup mode. When the CVIM module is receiving configuration blocks from a Host, the CVIM module will leave the active run mode and ignore any input triggers (setup menu option is also disabled).
PAGE 91
Chapter 5 Using the RS-232 Ports Command Summary After you have become familiar with the ASCII commands, you can use the following command summary as a quick reference guide. Table 5.
PAGE 92
Chapter 5 Using the RS–232 Ports Command Summary (cont’d) Table 5.A ASCII Command Summary (Cont’d) Command Set Configurable Statistics Trigger Inspection Command Structure >SSn,TSxd,TSxd,etc. [CR] >T,TSn[CR] >W, D, data [CR] Field Descriptions n= x= d= number of samples. 1 or 2 G1, G2, W1, W2, RW1, LP, etc.
PAGE 93
Chapter 5 Using the RS-232 Ports Explanation of ASCII Programming Example The following sample program was written on an Allen-Bradley 1784-T50B terminal (IBM AT compatible) using GW basic. This program obtains discrete results from the CVIM module. A program user is prompted to select either toolset 1 or toolset 2. The program will then: • • • • • Trigger an inspection. Detect when new data is available. Read all pass/fail/warning data for the selected toolset.
PAGE 94
Chapter 5 Using the RS–232 Ports Explanation of ASCII Programming Example (cont’d) Assume the ASCII string from the CVIM module is: CR LF 2114 __ __ __ __ __ __389 __ __ __ __ __ B0__80__ A2__ 00__00__(etc.)CR LF Note: ( __ = space, LF = Line Feed, CR = Carriage Return) The 18 element hexadecimal array after the program receives the data: R1(0) = 2114 = Decimal representation of total triggers processed. R1(1) = 389 = Decimal representation of total master faults (failed inspections).
PAGE 95
Chapter 5 Using the RS-232 Ports ASCII Programming Example The following is a sample ASCII program written in BASIC: 1 REM RS–232 to CVIM COMMUNICATIONS SAMPLE PROGRAM 2 REM COPYRIGHT ALLEN–BRADLEY COMPANY, INC.
PAGE 96
Chapter 5 Using the RS–232 Ports DF1 Protocol The remainder of this chapter describes DF1 protocol. After you have made the equipment connections and configured the CVIM module for RS–232 communications, DF1 packets of data can be sent to the CVIM module. What is DF1? DF1 is an Allen–Bradley developed software convention used for RS–232 communications. DF1 provides some handshaking and data–packing formats which allow for fast communications with integrity of the data.
PAGE 97
Chapter 5 Using the RS-232 Ports Command Structure Each command the host device sends to the CVIM module is represented by a block of data beginning with DLE STX (Data Link Escape, Start of Transmission) and terminated with DLE ETX BCC (Data Link Escape, End Transmission, Block Check Character). The data between the header and trailer characters is the command data.
PAGE 98
Chapter 5 Using the RS–232 Ports ACK/NAK, BCC Characters After receiving a DF1 data packet, the CVIM module validates the Block Check Character. Note: The block check character is a technique used to check the integrity of of data packet. BCC are explained in the next section. Depending upon whether or not the BCC is validated, the following will occur: If the BCC is not acceptable, the CVIM module will reply with a DLE NAK (Negative Acknowledgment) character and discard the data packet.
PAGE 99
Chapter 5 Using the RS-232 Ports For example, if a message packet contained the data codes 8, 9, 6, 0, 2, 4, and 3, the message packet codes would be (in hex): 10 02 DLE STX 08 09 06 00 02 04 03 10 Data 03 E0 DLE ETX BCC The sum of the data bytes in this message packet is 20 hex. The BCC is the 2’s complement of this sum, or E0 hex.
PAGE 100
Chapter 5 Using the RS–232 Ports Deactivate Forces Use the deactivate force command to return outputs on the 1771–JMB local I/O board to the CVIM module assigned functions. The deactivate forces command is: If the BCC is not valid, the CVIM module will respond with a DLE NAK and the command will not be executed. If the BCC is valid, the CVIM module will respond with a DLE ACK. Then the CVIM module will validate the command structure.
PAGE 101
Chapter 5 Using the RS-232 Ports Enable/Disable Outputs Use this command to enable or disable discrete outputs or local Outputs I/O. Use the following commands: This command disables the outputs. This command enables the outputs. If the BCC is not valid, the CVIM module will respond with a DLE NAK and the command will not be executed. If the BCC is valid, the CVIM module will respond with a DLE ACK. Then the CVIM module will validate the command structure.
PAGE 102
Chapter 5 Using the RS–232 Ports Forcing Local I/O (cont’d) For example: This example will force all outputs on. FF sets all bits in byte 3 (outputs 1 through 8) and 3F sets bits 0 through 5 of byte 4 (outputs 9 through 14). It is possible to have outputs forced on and off at the same time. A force off takes precedence over the force on. If multiple force commands are sent, the forced on or off outputs will be added to those already forced.
PAGE 103
Chapter 5 Using the RS-232 Ports You cannot use these commands when the CVIM module is in the SETUP mode. If the BCC is not valid, the CVIM module will respond with a DLE NAK and the command will not be executed. If the BCC is valid, the CVIM module will respond with a DLE ACK. Then the CVIM module will validate the command structure. If the command is valid, the CVIM module will execute the command. If the command structure is invalid, the CVIM module will not execute the command or respond.
PAGE 104
Chapter 5 Using the RS–232 Ports Read Output Status (cont’d) For Example: This example will read the status of all fourteen outputs. FF sets all bits in byte 3 (outputs 1 though 8) and 3F sets bits 0 through 5 of byte 4 (outputs 9 through 14). One byte is returned to indicate the status of the output (1 = ON and 0 = OFF). The output bytes are transmitted in numerical order (output #1 then output #2, etc.). The amount of data returned depends upon the number of outputs being read.
PAGE 105
Chapter 5 Using the RS-232 Ports Use the read configuration command to read configuration data for the specified object.
PAGE 106
Chapter 5 Using the RS–232 Ports Read Configuration Block Command (cont’d) For example: To read configuration blocks 49 and 50 you would send: 06(hex) for byte 1– Indicates a read command. 07(hex) for byte 2– Specifies the configuration blocks. 00(hex) for bytes 4 through 8. 03(hex) for byte 9– Sets the first two bits of byte 9 to indicate blocks 49 and 50. 00(hex) for bytes 10 through 19. Refer to Appendix C for a description of the configuration blocks.
PAGE 107
Chapter 5 Using the RS-232 Ports After reading the selected blocks, the CVIM module will return the requested data. Each word of a configuration block is sent as two bytes with the high byte transmitted first. A DLE (10 hex) is converted to DLE DLE (10 hex 10 hex). Refer to Appendix D for block descriptions and sizes.
PAGE 108
Chapter 5 Using the RS–232 Ports Read Results Command Use this command to read the results of the last inspection. Refer to Appendix C for a description of the results blocks.
PAGE 109
Chapter 5 Using the RS-232 Ports The read results command can be executed more than once per command by specifying an n times value. This command is toolset dependent. Toolset 1 is specified by 04. Toolset 2 is specified by 05. Examples: 07 00 Operation 01 04 Count 18 01 Object This command reads the results of toolset 1, reference line #1 (4 data bytes returned) 07 00 Operation 01 05 Count 17 0B Object This command reads the results of toolset 2, window #11 (4 data bytes returned).
PAGE 110
Chapter 5 Using the RS–232 Ports Read Results Command (cont’d) 07 00 Operation 01 Count 08 Object This command reads the CVIM module status (2 data bytes returned). Note: Refer to Appendix B, Table B.1, RS–232 word 0 for a definition of CVIM module status. If the BCC is not valid, the CVIM module will respond with a DLE NAK and the command will not be executed. If the BCC is valid, the CVIM module will respond with a DLE ACK. Then the CVIM module will validate the command structure.
PAGE 111
Chapter 5 Using the RS-232 Ports Save Command Use the Save command to save CVIM module configuration data to the local storage area (EEPROM) or the external RAM card (credit card memory). Note: Depending upon the card size, up to 16 configurations can be saved to the RAM card (512K card). Use the following commands: Saves configuration to EEPROM. XX Where XX = card storage location (01 to 16). This function can only be executed once per command.
PAGE 112
Chapter 5 Using the RS–232 Ports Select Image Displayed (cont’d) 11 (hex) = Stats 2 page displayed – Toolset 1 12 (hex) = Page up same display – Toolset 1 13 (hex) = Page down same display – Toolset 1 15 (hex) = Image only displayed – Toolset 2 16 (hex) = Failed tools displayed – Toolset 2 17 (hex) = All tools displayed – Toolset 2 18 (hex) = I/O page displayed – Toolset 2 19 (hex) = Results page displayed – Toolset 2 1A (hex) = Stats 1 page displayed – Toolset 2 1B (hex) = Stats 2 page displayed – Toolse
PAGE 113
Chapter 5 Using the RS-232 Ports 15 (hex) = Resume – Toolset 2 16 (hex) = Reset Statistics – Toolset 2 17 (hex) = Reset counters – Toolset 2 18 (hex) = Page up – Toolset 2 19 (hex) = Page down – Toolset 2 Examples: 03 This example displays all tools in toolset 1. 01 This example selects go on reject in toolset 1. 0B Operation 14 Object 05 Data This example selects page down in toolset 2. If the BCC is not valid, the CVIM module will respond with a DLE NAK and the command will not be executed.
PAGE 114
Chapter 5 Using the RS–232 Ports Set Configurable Results Use this command to obtain a configurable results block. The results you want are specified by a list of tools and placed in results block #4. No data is returned until you use a read inspection results command for block #4. Use the following command: The flags indicate which toolsets are specified. Refer to Table C.5 in Appendix C. Set the bits to 1 for the tools you want.
PAGE 115
Chapter 5 Using the RS-232 Ports Set/Read Configurable Statistics Use the read command to read statistical data for the light probe, reference windows, gages, and windows. Use the separate set command to set the number of samples and configure the statistics block. The set configurable statistics command has the following structure: 16 00 nn x Flags (16 Bytes) Where nn specifies the number of samples and x specifies the toolset (04 = toolset 1, 05 = toolset2).
PAGE 116
Chapter 5 Using the RS–232 Ports Set/Read Configurable Statistics (cont’d) The block signature is 2 bytes long. The number of samples is a 2 byte integer. The maximum and minimum values are each 4 bytes. The format of the data depends upon the operation (e.g. pixel count is an integer and linear gaging is a 16.16 fixed point value). Refer to page C–24 for data formats. The average and standard deviation are also 4 bytes each but are always 16.16 fixed point values.
PAGE 117
Chapter 5 Using the RS-232 Ports valid, the CVIM module will execute the command and return the data. If the command structure is invalid, the CVIM module will not execute the command or respond. Note: When using this command you should make sure that the CVIM module is configured for a “hosted trigger source”. Unlock Command Use the unlock command to enable the user interface (monitor and keyboard) so that a user can access the SETUP.
PAGE 118
Chapter 5 Using the RS–232 Ports Write Configuration Blocks (cont’d) 8 32 56 80 7 31 55 79 104 103 128 127 6 30 54 78 Write Configuration Block Command Bytes 3–29 Byte 3 Byte 4 Byte 5 Bits 7 – 0 Bits 7 – 0 Bits 7 – 0 5 4 3 2 1 16 15 13 12 11 10 9 24 23 22 21 20 19 18 17 43 42 41 67 66 65 91 90 89 116 115 114 113 Byte 6 Byte 7 Byte 8 Bits 7 – 0 Bits 7 – 0 Bits 7 – 0 29 28 27 26 25 40 39 38 37 36 35 34 33 48 47 46 45 44 Byte 9 Byte
PAGE 119
Chapter 5 Using the RS-232 Ports This function can only be executed once per command. Each configuration block is sent in a separate data packet (Header/Data/Trailer). Refer to Appendix D for a description of the configuration blocks. You cannot use this command when the CVIM module is in the setup mode. After writing to the CVIM module, the CVIM module will validate all of the configuration blocks (refer to Chapter 4 for a description of memory validation).
PAGE 120
Chapter 5 Using the RS–232 Ports Command Summary After you have become familiar with the DF1 commands, you can use the following command summary as a quick reference guide. Table 5.
PAGE 121
Chapter 5 Using the RS-232 Ports Table 5.B DF1 Command Summary (Cont’d) Command Command Structure Field Descriptions n= x= y= 07 00 n x y z z= Read Results Block Save to EEPROM from RAM times repeated 04 (Toolset 1) 05 (Toolset 5) 16(Gages) 17 (Window) 18 (Reference Line) 19 (Reference Window 1A (Light Probe) Window, Gage, Reference Line, or Reference Window No.
PAGE 122
Chapter 5 Using the RS–232 Ports Command Summary (cont‘d) Table 5.
PAGE 123
Chapter 5 Using the RS-232 Ports DF1 Programming Example The following is a sample DF1 program written in C. The program configures the host computer’s serial port for 9600 Baud communications. The program then displays a menu which prompts the user to select one of the following operations: 0. Echo the word “HELLO” to test the communications port. 1. Trigger the CVIM module to perform an inspection using toolset #1. 2. Read the discrete bit results for toolset 1. 3.
PAGE 124
Chapter 5 Using the RS–232 Ports DF1 Programming Example (cont’d) /* CVIM RS–232 Communication example program using DF1 protocol */ /* Copyright Allen–Bradley 12-5-89 jrm, aes */ This sample program was compiled using Microsoft C Version 5.1 */ #include #include #include
PAGE 125
Chapter 5 Using the RS-232 Ports /* Print options menu on the screen */ do { printf (”\n\nOperations: \n\n”); printf (”0. Echo ’HELLO’\n”); printf (”1. Trigger Tool Set 1\n”); printf (”2. Read Discrete Results tool set 1\n”); printf (”3. Read Results Block 1, toolset 1\n”); printf (”4.
PAGE 126
Chapter 5 Using the RS–232 Ports DF1 Programming Example (cont’d) case 3: /* read results block 1, tool set 1 */ err = send_message (portnum, ”\007\000\001\020\001”,5); if (!err) { err = get_message(portnum, results, &reslen); if (!err) { printf (”Results block #1:\n”); */ Display the results block */ for (x=0; x
PAGE 127
Chapter 5 Using the RS-232 Ports err = get_message(portnum,reply, & replen); break; case 7: /* read results block 1 tool set 2 */ err =send_message(portnum,”\007\000\001\025\001”,5); if (!err) { err = get_message(portnum,results, & reslen); if (!err) printf (”Results block #1:\n”); /* Display the results block */ for (x=0; x
PAGE 128
Chapter 5 Using the RS–232 Ports DF1 Programming Example (cont’d) if (err) { /* read first template block */ err = get_message(portnum, template [0] & templen [0]); /* Determine how many template blocks follow */ numblocks = template [0] [2]; for (x=1 (X
PAGE 129
Chapter 5 Using the RS-232 Ports case 14: err =send_message(portnum,”\013\002\031”, 3); break; case 15: err =send_message(portnum,”\013\002\034”, 3); break; case 16: err =send_message(portnum,”\013\002\035”, 3); break; default: break; } /* End switch (op_num) statement */ if (err) printf (”Error code: %04xn”,err); if (replen) { printf (”Response ”); for (x=0; x=0); */ End do loop */ } /* Transmits the message pointed to by msg, con
PAGE 130
Chapter 5 Using the RS–232 Ports DF1 Programming Example (cont’d) /* send DLE STX to initiate message transfer */ _bios_serialcom(_COM_SEND,portnum,DLE); _bios_serialcom(_COM_SEND,portnum,STX); /* Send all bytes of the selected command & compute checksum */ for (x=chksum=0; x
PAGE 131
Chapter 5 Using the RS-232 Ports { int good_string = 0; int message_started = 0; int ch, err, retry=4; int length = 0; unsigned char *msg_start_ptr, df1_bcc; msg_start_ptr = msg; while ( !good_string && retry ) { ch = _bios_serialcom(_COM_RECEIVE,portnum, 0); err |= ch & COMMFLAGS; if (( ch & 0xFF ) == DLE ) { ch = _bios_serialcom(_COM_RECEIVE,portnum,0); err |= ch & COMMFLAGS; switch( ch & 0xFF ) { case STX: message_started = 1; break; case ETX: message_started = 0; ch = _bios_serialcom(_COM_RECEIVE,portn
PAGE 132
Chapter 5 Using the RS–232 Ports DF1 Programming Example (cont’d) case DLE: if ( message_started ) { if ( ++length > MAX_BUFFER ) { _bios_serialcom(_COM_SEND,portnum,DLE); _bios_serialcom(_COM_SEND,portnum,NAK); last_response = 0; message_started = 0; err = 0; length = 0; df1_bcc = 0; msg = msg_start_ptr; } else { *msg++ = ( ch & 0xFF ); df1_bcc += ( ch & 0xFF ); } } break; case ENQ: if ( last_response ) { _bios_serialcom(_COM_SEND,portnum,DLE); _bios_serialcom(_COM_SEND,portnum,NAK); } else { _bios_seria
PAGE 133
Chapter 5 Using the RS-232 Ports length = 0; df1_bcc = 0; msg = msg_start_ptr; } else { *msg++ = ( ch & 0xFF ); df1_bcc += ( ch & 0xFF ); } } } *len = length; return (err); } 5–63
PAGE 134
Chapter A–B 6 Using the Pyramid Integrator Backplane Chapter Objectives This chapter: • • • • Describes the Pyramid Integrator Backplane. Describes backplane communication techniques. Describes CVIM module setup requirements Contains a sample PLC–5/250 program. Note: Refer to Publication No. 5000–2.3 (Allen–Bradley Pyramid Integrator Technical Overview) for a description of the basic hardware components and valid configurations.
PAGE 135
Chapter 6 Using the Pyramid Integrator Backplane What Functions can be Performed Over the Backplane? A MicroVAX information processor, PLC–5/250, or other device in the Pyramid Integrator rack can request or manipulate the following data through the backplane. • • • Obtain CVIM module inspection result information. Refer to Appendix B & C (CFG or SYS Host). Upload or download CVIM module configurations for inspections. Refer to Appendix D (CFG Host).
PAGE 136
Chapter 6 Using the Pyramid Integrator Backplane If you are using the Pyramid Integrator backplane for communications, you must configure the CVIM module as follows: 7. Select the trigger source menu for the appropriate toolset . 8. Select either , trigger sources or . Note: When changing the host to/from the Pyramid Integrator, you must “pick” the selection twice and then reboot the CVIM module.
PAGE 137
Chapter 6 Using the Pyramid Integrator Backplane Obtaining Inspection Result Information Using a PLC–5/250 (cont’d) The address of CVIM module shared memory is always SD13, with the addressing as follows: CVIM Thumbwheel No. SD13 For example: Word/Bit No. Assume that the CVIM module has a thumbwheel setting of #2. The data that you want to read is window 1 fault flag in Toolset 1. Refer to Appendix B, the bit you want to read is bit 01 of word 17.
PAGE 138
Chapter 6 Using the Pyramid Integrator Backplane Figure 6.1 32 Bit Long Integer Files TS1 Pulse TS2 Pulse TS1 Pulse TS2 Pulse Use the message instruction (MSG) to transfer configuration data between the PLC and the CVIM. The message instruction can transfer up to 10,000 elements of data/commands. When used for Pyramid Integrator backplane instructions, the message instruction commands the resource manager module to transfer data between two module addresses.
PAGE 139
Chapter 6 Using the Pyramid Integrator Backplane Sample PLC–5/250 Program The following program shows how to trigger an inspection, and/or upload an entire CVIM configuration for archiving and later downloading. Rung #1 Triggers the CVIM to perform an inspection using toolset#1 upon false transition of 1N0:0/00. Rung #2 Reads the integer value of gage 1 and places value in 1N0:02. Rung #3 One shots 1N0:1/0 when 1N0:02 has a false to true transition.
PAGE 140
Chapter 6 Using the Pyramid Integrator Backplane 16 January 1990 Page 3 Ladder Listing Processor File: CVIM1, Addr: 003 Rung 1STEP0:0 Rung 1STEP0:0 | | +––––––––––––––––––––––––––––––––[TOP OF FILE]–––––––––––––––––––––––––––––––––+ | | Rung 1STEP0:1 | 1N0:0 1SD13:1023 | +––––] [––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––( )––+ | 0 10 | Rung 1STEP0:2 | 1N0:0 +CPT–––––––––––+ | +––––] [–––––––––––––––––––––––––––––––––––––––––––––––––––––+COMPUTE +––| | 1 |Dest 1NO:2| | | | 0| | | |Ex
PAGE 141
Chapter 6 Using the Pyramid Integrator Backplane Sample PLC–5/250 Program (cont’d) CONTROL BLOCK 0MSG0:0 F1 Requested Size(element): F2 Priority: F3 Local/Remote: F4 Local Link Type: F5 Remote Link Type: F6 Station ID: F7 Module ID: F8 Communication Command: F9 Internal Data Table Addr: F10External Data Table Addr: Parameters: 0 HIGH LOCAL DH+ N/A Node# = 0 Class = CVIM Tw# = 1 Port# = 1 TYPED READ 0L9:0 ”>rc,cb*” N/A CONTROL BLOCK OMSG0:1 F1 Requested Size(element): F2 Priority: F3 Local/Remote: F4 Loc
PAGE 142
Appendix A Results/Configuration Data Overview Introduction This appendix provides an overview of the word and bit addresses of data stored in memory if you are communicating with the CVIM through the REMOTE I/O, Backplane, or RS–232 port. Also provided is an explanation of how the CVIM stores fractional data. Overview Table A.1 provides an overview of shared memory.
PAGE 143
Appendix A Results/Configuration Data Overview Fractional Notation Inspections which produce results that are fractional are represented using two words (32 bits). The first 16 bits are the integer portion and the second 16 bits are the fractional portion: WORD N WORD N + 1 Bit: 31 30 . . . 17 16 Integer 15 14 . . . 1 0 Fraction The integer portion of the value is interpreted as a standard 16 bit signed integer where each bit is equal to: Integer Bit Value 2(n) Where n is the bit number.
PAGE 144
Appendix A Results/Configuration Data Overview We have provided the following chart to assist you: Figure A.1 Fractional Notation Bit # 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 1/65536 1/32768 1/16384 1/8192 1/4096 1/2048 1/1024 1/512 1/256 1/128 1/64 1/32 1/16 1/8 1/4 1/2 For example: 0000000000000011.0100000000000000 = 3.25 Note: For a sample PLC program which converts 16 point 16 values to floating point values, refer to Chapter 4.
PAGE 145
Appendix A Results/Configuration Data Overview Template Blocks A–4 The template blocks (part of configuration memory) contain previously learned image templates, not on-line configuration parameters. Word 1, bits 8-15 (third byte sent using RS-232 port) of the first template block indicate the total number of template blocks in the configuration. You must always upload or download all of the template blocks as a unit. You cannot archive only a part of the template blocks.
PAGE 146
Appendix A–B B Discrete IIO Results Bits (Host Input & Output Bits) Introduction This appendix lists the function of both the discrete bit inputs and outputs. These bits can be accessed through the Remote I/O port and Pyramid Integrator backplane. You cannot manipulate these bits through the RS–232 ports (A or B) but you can perform many of their functions. Discrete Bit Inputs With each inspection that the CVIM module performs, individual bits are set.
PAGE 147
Appendix B Discrete Bit Results Discrete Bit Inputs (cont’d) Table B.1 Discrete Bit Inputs Word# PI Backplane Toolset 1 Toolset 2 16 280 Bit# RS–232 and Remote I/O 0 D E C I M A L O C T A L PI PLC 0 0 Definition Usage Notes Not Used 0 = No Error 1 = Error Configuration error bit is set after any invalid configuration or template block write to the CVIM. This flag is also set after validation errors. 0 = Not Master 1 = Master The device which reads this bit as 1 is the host.
PAGE 148
Appendix B Discrete Bit Results Table B.
PAGE 149
Appendix B Discrete Bit Results Discrete Bit Inputs (cont’d) Table B.
PAGE 150
Appendix B Discrete Bit Results Table B.
PAGE 151
Appendix B Discrete Bit Results Discrete Bit Inputs (cont’d) Table B.
PAGE 152
Appendix B Discrete Bit Results Table B.
PAGE 153
Appendix B Discrete Bit Results Discrete Bit Inputs (cont’d) Table B.
PAGE 154
Appendix B Discrete Bit Results Discrete Bit Outputs There are 128 bits that can be set as outputs from a host device to control the operation of the CVIM. These bits control: • • • • • Monitor display. Camera trigger. Toolset selection. I/O forcing. Selection of operation after reject. • Memory storage location. RAM, EEPROM, RAM Card, or external host memory. Refer to Tables B.2 and B.3. Table B.2 only applies to Backplane communications. Table B.
PAGE 155
Appendix B Discrete Bit Results Discrete Bit Outputs (cont’d) Note: When using the backplane, don’t write directly to word 2. Write to word 1023. The CVIM will copy the data from word 1023 to word 2. Note: When communicating with a device through the Pyramid Integrator backplane, CVIM module results are posted in shared memory immediately after processing. When communicating with a device through the other ports, results are only available at the end of the inspection program. Table B.
PAGE 156
Appendix B Discrete Bit Results Table B.3 Discrete Bit Outputs Word # PI Backplane 2 Bit # RS–232 and Remote I/O 0 D E C I M A L O C T A L PI PLC 13 15 Definition Usage I/O Request 0 = No Request 1 = Request Notes Bit 13 commands are specified in: Output words 2, 4, and 5 (Remote I/O) Output words 4, 6, and 7 (Backplane) You must reset bit to 0, then back to 1 to repeat an I/O request.
PAGE 157
Appendix B Discrete Bit Results Discrete Bit Outputs (cont’d) Table B.
PAGE 158
Appendix B Discrete Bit Results Table B.
PAGE 159
Appendix B Discrete Bit Results Discrete Bit Outputs (cont’d) Table B.
PAGE 160
Appendix B Discrete Bit Results Table B.3 Discrete Bit Outputs Word # PI Backplane 5 Bit # RS–232 and Remote I/O 3 D E C I M A L O C T A L PI PLC N/A 0–2 Definition Block Transfer Type Reference only. Not used for Backplane. Usage 000 = Invalid Request 001 = Results Block 010 = Configuration Block 100 = Template Block 101 = Statistics Block – See Notes Notes This word only applies to Remote I/O interface.
PAGE 161
Appendix B Discrete Bit Results Discrete Bit Outputs (cont’d) Table B.3 Discrete Bit Outputs Word# PI Backplane B–16 Bit# RS–232 and Remote I/O D E C I M A L O C T A L PI PLC Definition Usage Notes 6 4 0 0 Local I/O Output 1 Force ON 0 = No Force 1 = Force On Refers to Catalog Number 1771–JMB Local I/O Board. 6 4 1 1 Local I/O Output 2 Force ON 0 = No Force 1 = Force On Refers to Catalog Number 1771–JMB Local I/O Board.
PAGE 162
Appendix B Discrete Bit Results Table B.3 Discrete Bit Outputs Word# PI Backplane Bit# RS–232 and Remote I/O D E C I M A L O C T A L PI PLC Definition Usage Notes 7 5 0 0 Local I/O Output 1 Force OFF 0 = No Force 1 = Force Off Refers to Catalog Number 1771–JMB Local I/O Board. 7 5 1 1 Local I/O Output 2 Force OFF 0 = No Force 1 = Force Off Refers to Catalog Number 1771–JMB Local I/O Board.
PAGE 163
Appendix B Discrete Bit Results Discrete Bit Outputs (cont’d) Table B.
PAGE 164
Appendix C Numerical Results Data Results Block Overview There are 4 results blocks for each toolset. The following is an overview of the blocks.
PAGE 165
Appendix C Numerical Results Data Block Transfer Signature The block transfer signature is for user information only. The CVIM places the signature in each block sent to the PLC for identification and does not care if the PLC changes the signature prior to sending a block back to the CVIM. Bits 0–7 designate the block number: 00000000 = Not Valid 00000001 = Block #1 00000010 = Block #2 ...
PAGE 166
Appendix C Numerical Results Data Results Block #1 Table C.1 shows the function of each word in Results Block #1. Table C.1 Numerical Results Data – Results Block 1 Word # Bit # Toolset 1 Toolset 2 RS–232 and Remote I/O 24 288 0 0 – 15 Block Transfer Signature 25 289 1 0 – 15 Reserved 26 290 2 0 – 15 Brightness Probe Integer 16 . 16 value. Refer to Appendix A. 27 291 3 0 – 15 Brightness Probe Fraction 16 . 16 value. Refer to Appendix A.
PAGE 167
Appendix C Numerical Results Data Results Block #1 (cont’d) Table C.1 Numerical Results Data – Results Block 1 Word # Bit # Toolset 1 Toolset 2 RS–232 and Remote I/O 44 308 20 0 Reference Window #1X1/Y1 Pass/Fail Bit 0 = Pass 1 = Fail Feature 1. 44 308 20 1 Reference Window #1X2/Y2 Pass/Fail Bit 0 = Pass 1 = Fail Feature 2. 44 308 20 2 Reference Window #1X3/Y3 Pass/Fail Bit 0 = Pass 1 = Fail Feature 3.
PAGE 168
Appendix C Numerical Results Data Table C.1 Numerical Results Data – Results Block 1 (cont’d) Word # PI Backplane Toolset 1 Toolset 2 RS–232 and Remote I/O Bit # Definition Usage Notes 64 – 65 328 – 329 40 – 41 0 – 15 Gage #1 Value Angular & Linear Measure – 16 . 16 Edge – 32 bit integer Object – 32 bit integer Pixel – 32 bit integer X Position & Y Position – 16 . 16 66 – 67 330 – 331 42 – 43 0 – 15 Gage #2 Value Same as Gage #1.
PAGE 169
Appendix C Numerical Results Data Results Block #2 Table C.2 shows the function of each word in results block #2. Table C.2 Numerical Results Data – Results Block 2 Word # Bit # Toolset 1 Toolset 2 RS–232 and Remote I/O 88 352 0 0 – 15 Block Transfer Signature 89 353 1 0 – 15 Reserved PI Backplane Definition Usage Notes 90 – 91 354 – 355 2–3 0 – 15 Window #9 Value Luminance – 16 .
PAGE 170
Appendix C Numerical Results Data Table C.2 Numerical Results Data – Results Block 2 Word # Bit # Toolset 1 Toolset 2 RS–232 and Remote I/O 128 – 129 392 – 393 40 – 41 0 – 15 Window #20 Value Same as Window #17. 130 – 131 394 – 395 42 – 43 0 – 15 Window #21 Value Same as Window #17. 132 – 133 396 – 397 44 – 45 0 – 15 Window #22 Value Same as Window #17. 134 – 135 398 – 399 46 – 47 0 – 15 Window #23 Value Same as Window #17.
PAGE 171
Appendix C Numerical Results Data Results Block #3 Table C.3 shows the function of each word in results block #3. Table C.3 Numerical Results Data – Results Block 3 Word # Bit # Toolset 1 Toolset 2 RS–232 and Remote I/O 152 416 0 0 – 15 Block Transfer Signature 153 417 1 0 – 15 Reserved PI Backplane Definition Usage Notes 154 – 155 418 – 419 2–3 0 – 15 Gage #23 Value Angular & Linear Measure – 16 .
PAGE 172
Appendix C Numerical Results Data Table C.3 Numerical Results Data – Results Block 3 Word # Bit # Toolset 1 Toolset 2 RS–232 and Remote I/O 182 446 30 0 – 15 Reference Window #2 Theta (Integer) 16 . 16 value. Refer to Appendix A. Only if 2 or 3 features are enabled. 183 447 31 0 – 15 Reference Window #2 (Fraction) Only if 2 or 3 features are enabled. 184 448 32 0 Reference Window #2X1/Y1 Pass/Fail Bit 0 = Pass 1 = Fail Feature #1.
PAGE 173
Appendix C Numerical Results Data Results Block #3 (cont’d) Table C.3 Numerical Results Data – Results Block 3 Word # Bit # Toolset 1 Toolset 2 RS–232 and Remote I/O 194 458 42 0 – 15 Reference Window #3X – Center Centroid of enabled feature. 16 bit integer. 195 459 43 0 – 15 Reference Window #3Y – Center Centroid of enabled feature. 16 bit integer. 196 460 44 0 – 15 Reference Window #3 Theta (Integer) 16 . 16 value. Refer to Appendix A. Only if 2 or 3 Features are enabled.
PAGE 174
Appendix C Numerical Results Data Table C.3 Numerical Results Data – Results Block 3 Word # Bit # Toolset 1 Toolset 2 RS–232 and Remote I/O 213 477 61 0 – 15 Task Master Faults – Least Significant Word 214 478 62 0 – 15 Task Triggers – Most Significant Word 215 479 63 0 – 15 Task Triggers – Least Significant Word PI Backplane Definition Usage Notes 32 bit integer. Refer to Appendix A.
PAGE 175
Appendix C Numerical Results Data Results Block #4 The fourth results block may be formatted and read through any of the communications ports. This block has user defined contents. This block may contain up to 64 words of data; see Table C.4. Table C.
PAGE 176
Appendix C Numerical Results Data Note: Words 2 through 5 select tools for Toolset 1. Words 6 through 9 select tools for Toolset 2. Note: Word 0, block signature and word 1 are not used. Use Table C.5 to set the contents of the programmable results block and statistics block. Table C.
PAGE 177
Appendix C Numerical Results Data Results Block #4 (cont’d) Table C.
PAGE 178
Appendix C Numerical Results Data Table C.
PAGE 179
Appendix C Numerical Results Data Statistics Block The Statistics Block can be formatted and read through any of the communications ports. The Statistics Block has user defined contents. This block may contain up to 64 words of data; see Table C.6. Table C.6 Statistics Block Word # Bit # Function 0 0 – 15 Block Transfer Signature 1 – 63 0 – 15 User Defined Statistics Data Notes Each type of statistic requires a specific number of words.
PAGE 180
Appendix D Configuration Data Configuration Block Overview There are 135 configuration blocks. The following is an overview of the blocks. Block Number 1 . . . . . . . . . . . . . . . . . . System Environment (45 words). Block Numbers 2 and 3 . . . . . . . . . . . . Camera A and B Definition (61 words each camera). Block Numbers 4 through 6 . . . . . . . . . Toolset 1 Reference Lines 1 through 3 (30 words). Block Numbers 7 through 9 . . . . . . . . . Toolset 1 Reference Windows 1 through 3 (36 words).
PAGE 181
Appendix D Configuration Data Configuration Block #1 Table D.1 shows the function of each word in the system environment configuration block. Table D.1 Configuration Block #1– System Environment Remote I/O & RS–232 Word #* Bit # 0 0–15 Block Transfer Signature 1–3 0–15 Reserved 4 0–7 Configuration ID (Char. 2) 4 8–15 Configuration ID (Char. 1) 5 0–7 Configuration ID (Char. 4) 5 8–15 Configuration ID (Char. 3) 6 0–7 Configuration ID (Char. 6) 6 8–15 Configuration ID (Char.
PAGE 182
Appendix D Configuration Data Table D.
PAGE 183
Appendix D Configuration Data Configuration Blocks 2 & 3 Tables D.2 shows the function of each word in the camera definition configuration blocks. Table D.2 Configuration Block #2 & 3 – Camera Definition Remote I/O & RS–232 Word #* Bit # 0 0–15 Block Transfer Signature 1 0–7 Camera Low Reference 0 = Minimum Value ... 100 = Maximum Value These values do not correspond with the display on the help screen. 1 8–15 Camera High Reference 105 = Minimum Value ...
PAGE 184
Appendix D Configuration Data Configuration Blocks 4–6 Tables D.3 shows the function of each word in the reference line 1–3 (Toolset 1) configuration blocks. Table D.3 Configuration Blocks #4–6 – Reference Lines 1–3 (Toolset 1) Remote I/O & RS–232 Word #* Bit # 0 0–15 Block Transfer Signature 1 0–7 Reserved 1 8 1 9–15 Reserved 2–7 0–15 Reserved 8 0–7 X–Line Low Threshold/Gray Scale Factor 0 – 63 0 – 39 If binary operation, value is used as the threshold.
PAGE 185
Appendix D Configuration Data Configuration Blocks 4 – 6 (cont’d) Table D.3 Configuration Blocks #4–6 – Reference Lines 1–3 (Toolset 1) continued Remote I/O & RS–232 Word #* Bit # 23 0–15 Reserved 24 0–15 X/Y–Line Head X Position From upper left corner. 25 0–15 X/Y–Line Head Y Position From upper left corner. 26 0–15 X/Y–Line Tail X Position From upper left corner. 27 0–15 X/Y–Line Tail Y Position From upper left corner.
PAGE 186
Appendix D Configuration Data Table D.4 Configuration Blocks #7–9 – Reference Windows 1–3 (Toolset 1) Remote I/O & RS–232 Word #* Bit # 20 0–15 Feature 2 Search Window Height 21–24 0–15 Reserved 25 0–7 Reserved 25 8–15 Feature 2 Score 26 0–15 Feature 3 Search Window X Location Relative to the upper left corner. 27 0–15 Feature 3 Search Window Y Location Relative to the upper left corner.
PAGE 187
Appendix D Configuration Data Configuration Blocks 10 – 41 (cont’d) Table D.
PAGE 188
Appendix D Configuration Data Configuration Blocks 42 – 65 Table D.6 shows the function of each word in the window 1–24 (Toolset 1) configuration blocks. Table D.6 Configuration Blocks #42–65 – Windows 1–24 (Toolset 1) Remote I/O & RS–232 Word # Bit # 0 0–15 1 0 1 1–15 Reserved 2–4 0–15 Reserved 5 0– 7 Window Low Threshold 0 = Low Limit ... 63 = High Limit 5 8–15 Window High Threshold 0 = Low Limit ...
PAGE 189
Appendix D Configuration Data Configuration Blocks 66 – 68 Table D.7 shows the function of each word in the reference line 1–3 (Toolset 2) configuration blocks. Table D.7 Configuration Blocks #66–68 – Reference Lines 1–3 (Toolset 2) Remote I/O & RS–232 Word # Bit # 0 0–15 Block Transfer Signature 1 0–7 Reserved 1 8 Enabled 1 9–15 Reserved 2–7 0–15 Reserved 8 0–7 X–Line Low Threshold/Gray Scale Factor 0 – 63 0 – 39 If binary operation, value is used as the threshold.
PAGE 190
Appendix D Configuration Data Table D.7 Configuration Blocks #37–39 – Reference Lines 1–3 (Toolset 2) Remote I/O & RS–232 Word # Bit # 23 0–15 Reserved 24 0–15 X/Y–Line Head X Position From upper left corner. 25 0–15 X/Y–Line Head Y Position From upper left corner. 26 0–15 X/Y–Line Tail X Position From upper left corner. 27 0–15 X/Y–Line Tail Y Position From upper left corner.
PAGE 191
Appendix D Configuration Data Configuration Blocks 69–71 (cont’d) Table D.8 Configuration Blocks #69–71 – Reference Windows 1–3 (Toolset 2) Remote I/O & RS–232 Word #* Bit # 19 0–15 Feature 2 Search Window Width 20 0–15 Feature 2 Search Window Height 21–24 0–15 Reserved 25 0–7 Reserved 25 8–15 Feature 2 Score 26 0–15 Feature 3 Search Window X Location Relative to the upper left corner. 27 0–15 Feature 3 Search Window Y Location Relative to the upper left corner.
PAGE 192
Appendix D Configuration Data Table D.
PAGE 193
Appendix D Configuration Data Configuration Blocks 104–127 Table D.10 shows the function of each word in the window 1–24 (Toolset 2) configuration blocks. Table D.10 Configuration Blocks #104–127 – Windows 1–24 (Toolset 2) Remote I/O & RS–232 Word #* Bit # 0 0–15 1 0 1 1–15 Reserved 2–4 0–15 Reserved 5 0–7 Window Low Threshold 0 = Low Limit ... 63 = High Limit 5 8–15 Window High Threshold 0 = Low Limit ...
PAGE 194
Appendix D Configuration Data Configuration Blocks 128–135 Table D.11 shows the function of each word in the polygon configuration blocks. Table D.11 Polygon Configuration Blocks #128–135 Remote I/O & RS–232 Word #* Bit # 1 0–15 Block Transfer Signature 2–36 0–15 Reserved Definition Usage Notes * Refer to Chapter 6 for Pyramid Integrator long word descriptions. Template Blocks 136– The template blocks begin at block #136. The number of template blocks stored in memory is variable.
PAGE 195
Appendix E ASCII Conversion Table ASCII or Control Char. Decimal Value Hex Value ASCll or Control Char. Decimal Value Hex Value ASCll or Control Char. Decimal Value Hex Value ASCll or Control Char.
PAGE 196
Glossary Bulletin 5370 CVIM Configurable Vision Input Module A C ACK An abbreviated term for Positive Acknowledgment. A control code that indicates that the previous transmission block was received. centroid Midpoint of x and y axis of an object. address A character or group of characters that identifies a register, a particular part of storage, or some other data source or destination. To refer to a device or an item of data by its address.
PAGE 197
Glossary Bulletin 5370 CVIM Configurable Vision Input Module H handshaking Two–way communication between two devices to effect a data transfer. Handshaking operations are based on a Data–Ready/Data–Received signal scheme that assures orderly data transfer. hex Abbreviated form of the word hexadecimal. hexadecimal A base 16 numbering system. hexadecimal numbering system A numbering system using the equivalent of the decimal number 16 as a base.
PAGE 198
Glossary Bulletin 5370 CVIM Configurable Vision Input Module PLC Allen-Bradley trademark for programmable logic controller. Q Q–bus A set of electrical conductors that carry specific signals to several other circuits. string A sequence of ASCII characters. subroutine A series of computer instructions which perform a specific task for other routines.
PAGE 199
Index Bulletin 5370 CVIM Configurable Vision Input Module 16 point 16, 4Ć17 1771ĆJMB interface board, 3Ć15 6008ĆSI, Example program, 4Ć29 A Accessing results data, 4Ć21 ACK/NAK characters, 5Ć28 Addressing, 2Ć5 ASCII Character set, 5Ć5 Command structure, 5Ć6 Command summary (table), 5Ć27 Field types, 5Ć6 Protocol, 5Ć1, 5Ć5 Sample program, 5Ć25 ATTENTION, 4Ć15, 4Ć16 B Backplane, 2Ć3, 6Ć1 Configuration, 6Ć2 Baud rate, 4Ć1 BCC (block check character), 5Ć28 Bit numbering, 2Ć6 Block check character, 5Ć28 Block
PAGE 200
Index Bulletin 5370 CVIM Configurable Vision Input Module E EEPROM, 4Ć6, 5Ć3 F Field Data, 5Ć6 Object, 5Ć6 Operation, 5Ć6 Firmware revision, 1Ć1 Flow control, 5Ć7 Format 16 point 16, 4Ć17 Data, 5Ć4 Statistics block, 4Ć16, 5Ć45 Function(s) Assignment, 3Ć2 Possible on backplane, 6Ć2 Possible on remote I/O network, 4Ć6 Possible over RSĆ232 interface, 5Ć4 H Host CFG, 4Ć19 Configuration, 2Ć7 Designation, 2Ć7 System, 2Ć7 I I/O lines, Number of, 2Ć1 Inspection cycle, 3Ć9 Interface board, 3Ć15 Interface box, 2
PAGE 201
Index Bulletin 5370 CVIM Configurable Vision Input Module R RAM, 2Ć1 Card, 4Ć6, 5Ć3 Remote I/O Configuration instructions, 4Ć6 Functions, 4Ć6 Port, 2Ć3, 4Ć1 Software revision, 1Ć1 Statistics block Configure, 5Ć17 Format, 4Ć16 Read, 5Ć17 Set, 5Ć17 SYS host, 2Ć7, 4Ć14, 5Ć3, 5Ć4, 6Ć2 Results Blocks transfer, 4Ć15 Data words, 4Ć7 Read, 5Ć12, 5Ć38 Testing, RSĆ232 links, 5Ć4 Results block #4, 5Ć16, 5Ć53 Timing data, using, 3Ć6 Results data, 2Ć5 Accessing, 4Ć21 Converting, 4Ć17 Tool(s), Assignment, 3Ć2 R
PAGE 202
Rockwell Automation helps its customers receive a superior return on their investment by bringing together leading brands in industrial automation, creating a broad spectrum of easy-to-integrate products. These are supported by local technical resources available worldwide, a global network of system solutions providers, and the advanced technology resources of Rockwell. Worldwide representation.