Omron SYSMAC 3G8F5-CLK11-E Operation Manual
  1. Manuals
  2. Brands
  3. Omron Manuals
  4. Control Unit
  5. SYSMAC 3G8F5-CLK11-E
  6. Operation manual
Omron SYSMAC 3G8F5-CLK11-E Operation Manual

Omron SYSMAC 3G8F5-CLK11-E Operation Manual

Controller link support boards
Hide thumbs Also See for SYSMAC 3G8F5-CLK11-E:
Table of Contents

Advertisement

Quick Links

Download this manual
Cat.No. W307–E1–3
SYSMAC
3G8F5-CLK11-E
3G8F5-CLK21-E
Controller Link Support Boards
OPERATION MANUAL

Advertisement

Table of Contents
loading

Related Manuals for Omron SYSMAC 3G8F5-CLK11-E

Summary of Contents for Omron SYSMAC 3G8F5-CLK11-E

  • Page 1 Cat.No. W307–E1–3 SYSMAC 3G8F5-CLK11-E 3G8F5-CLK21-E Controller Link Support Boards OPERATION MANUAL...
  • Page 2 SYSMAC 3G8F5-CLK11-E 3G8F5-CLK21-E Controller Link Support Boards Operation Manual Revised February 1999...

  • Page 3: Omron Product References

    OMRON. No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice.
  • Page 4 TABLE OF CONTENTS PRECAUTIONS ....... . . 1 Intended Audience ............2 General Precautions .
  • Page 5 TABLE OF CONTENTS SECTION 8 Network Interconnections ......What is Network Interconnection? ......... . Routing Tables .
  • Page 6 Section 10 provides information on troubleshooting errors that occur during Controller Link Support Board operation, as well as daily inspection, cleaning, and other maintenance procedures. Appendix provides a list of standard OMRON products related to Controller Link Networks. WARNING Failure to read and understand the information provided in this manual may result in personal injury or death, damage to the product, or product failure.
  • Page 7 PRECAUTIONS This section provides general precautions for using the Controller Link Support Board and related devices. The information contained in this section is important for the safe and reliable application of the Controller Link Sup- port Board. You must read this section and understand the information contained before attempting to set up or oper- ate a Controller Link Support Board.

  • Page 8: Intended Audience

    You must consult with your OMRON representative before applying a Controller Link Support Board to the above mentioned applications.

  • Page 9: Application Precautions

    Application Precautions Where there is any corrosive or inflammable gas. Where there is excessive dust, saline air, or metal powder. Where the Controller Link Support Board is affected by vibration or shock. Where any water, oil, or chemical may splash on the Controller Link Support Board.
  • Page 10 Operating Environment Precautions Use crimp terminals for wiring. Do not connect bare stranded wires directly to terminals. Connection of bare stranded wires may result in burning. Double-check all the wiring before turning ON the power supply. Incorrect wir- ing may result in burning. Wire correctly.
  • Page 11 SECTION 1 Features This section outlines the features of the Controller Link Support Board, including the applications of the Controller Link Sup- port Board and the differences between the Controller Link Support Board and the Controller Link Unit. Overview ............. . . 1-1-1 What Is the Controller Link? .

  • Page 12: Specifications And Configurations

    1-1-1 What Is the Controller Link? The Controller Link is an FA network that can send and receive large data pack- ets flexibly and easily among advanced OMRON Programmable Controllers (CS1-series, C200HX/HG/HE-series, and CV-series PCs) and IBM PC/AT or compatible computers.
  • Page 13 Section Basic Procedures Optical System (Optical Fiber Cable) IBM PC/AT or CS1W-CLK11 CS1W-CLK11 CS1W-CLK11 compatible Controller Link Unit Controller Link Unit Controller Link Unit CS1-series PC CS1-series PC CS1-series PC Optical fiber cable 3G8F5-CLK11-E Controller Link Support Board 24-VDC Backup 24-VDC Backup Power Supply Power Supply...
  • Page 14 Section Specifications and Configurations Features of Optical Fiber Cable Optical Fiber Cable has superior noise resistance, so this system can provide highly reliable communications even in very noisy conditions. The communications distance can be up to 20 km in total (1 km max. between nodes), which allows long-distance or large-scale networks.
  • Page 15 The access methods for the Controller Link Support Board are different from those of a Controller Link Unit. The following two methods are used to access the Controller Link Support Board. Microsoft C library Functions from OMRON User program Language...
  • Page 16 Section Specifications and Configurations Direct Driver Access User program Driver call Driver Board Memory 1-1-5 Support Board vs Unit The following table shows a comparison between the Controller Link Support Board and a Controller Link Unit. Item Support Board Unit Communications cable Special connector Terminal block...

  • Page 17: Outline Of Features

    Section Basic Procedures 1-1-6 Outline of Features Data Links Data link data for each node is reflected in the shared memory area on the Board. When a data link cache is used, the data is edited according to the data link table and is stored in the data link cache area in memory.
  • Page 18 Section Specifications and Configurations Note Check the available memory. The data link cache area occupies 64 Kbytes of conventional memory or XMS memory. Data in area 1 and area 2 for each node is allocated consecutively in both the data link cache area and the shared memory data link buffer. When using data link cache areas, areas for each node are allocated in the order of node addresses set in the data link table.
  • Page 19 Section Basic Procedures The following table outlines the data link functionality for Controller Link Support Boards. Items Using a data link cache Not using data link cache Data link data Data link cache Data link buffer in shared memory storage area Offset 0 Data structure Offset 0...

  • Page 20: System Configuration

    Section Specifications and Configurations Specifications and Configurations 1-2-1 System Configuration Wired System IBM PC/AT or CS1W-CLK21 C200HW-CLK21 CVM1-CLK21 compatible Controller Link Unit Controller Link Unit Controller Link Unit CS1-series PC C200HX/HG/HE CV-series PC 3G8F5-CLK21-E Controller Link Support Board Maximum transmission distance: 1 km (at 500 Kbps) to 500 m (at 2 Mbps) Maximum number of nodes: 32 Optical System IBM PC/AT or...

  • Page 21: Communications Specifications

    Section Basic Procedures 1-2-2 Communications Specifications Items Wired system Optical system Communications method N:N token bus Code Manchester code Modulation Baseband code Synchronization Flag synchronization (conforms to HDLC frames) Transmission path form Multi-drop bus Daisy-chain Baud rate and maximum The maximum transmission distance varies 2 Mbps: 20 km transmission distance...

  • Page 22: External Dimensions

    Section Specifications and Configurations 1-2-4 External Dimensions Wired Model (Unit: mm) Optical Model (Unit: mm)

  • Page 23: Software Configuration

    Section Basic Procedures 1-2-5 Controller Link Support Board Configuration Contents Model Configuration Documentation Connectors 3G8F5-CLK21-E One Board Controller Link (Wired system) (3G8F5-CLK01, for Support Board communications IBM PC/AT or Operation Manual connector compatible) (W307) One 3.5-inch floppy Controller Link disk (1.44 Mbytes) Support Software Operation Manual 3G8F5-CLK11-E...
  • Page 24 Section Specifications and Configurations 1-2-8 Memory and Disk Requirements Hard Disk You must have at least 2 Mbytes of available space on your hard disk. Computer Memory Item Required free area Memory required for the Controller Link Driver Main memory (conventional): 2.5 Kbytes + number of send/receive buffers x 2 Kbytes min.

  • Page 25: Communications Cables

    Section Basic Procedures 1-2-10 Communications Cables Wired System The following shielded twisted-pair cable should be used for Controller Link Net- work connections. Model Manufacturer Li2Y-FCY2 x 0.56 qmm Kromberg & Schubert, Komtec Department 1 x 2 x AWG-20PE + Tr.CUSN + PVC Draka Cables Industrial #9207 Belden...
  • Page 26 Section Specifications and Configurations Note 1. Either full-lock or half-lock connectors can be used in a Controller Link Net- work, but we recommend full-lock connectors to prevent accidental discon- nections during operation. 2. The maximum distance between nodes is slightly shorter for connectors with crimp-cut cables compared to connectors assembled with adhesive.
  • Page 27 The following table shows the input specifications required for backup power Specifications supplies to Controller Link Units and Support Boards. Be sure that the backup power supply being used meets these specifications. (We recommend OMRON S82K-series Power Supplies.) Item Specification...
  • Page 28 Section Specifications and Configurations Terminating resistance Note Refer to 2-1-2 Setting Switches . 2. Install the Board into the computer. Note Refer to 2-1-3 Installing the Controller Link Support Board. 3. Wire and connect the cables. Note Refer to 2-2 Connecting W ired-system Cables for wired systems and 2-3 Connecting Optical-system Cables for optical systems.

  • Page 29: Applications Precautions

    Section Basic Procedures Applications Precautions Terminating Resistance Turn ON the terminating resistance switch only for the nodes at both ends of a Switch (Wired Systems wired Controller Link Network and turn OFF the switch for all other nodes. Only) Note Refer to 2-1 Installing the Support Board. Cables Turn OFF the power of all the nodes on the network before connecting or discon- necting a cable.
  • Page 30 SECTION 2 Setting, Installing, and Wiring Boards This section describes the methods for setting switches on the Controller Link Support Board, installing the Support Board in a computer, and wiring the Controller Link Network. Installing the Support Board ..........2-1-1 Support Board Components .
  • Page 31 Section Connecting Optical-system Cables Installing the Support Board This section describes the methods for setting and installing the Controller Link Support Board in an IBM PC/AT or compatible computer. 2-1-1 Support Board Components This section describes the name and function of each component. This section also describes the indicators.
  • Page 32 Section Connecting Optical-system Cables Optical Board DIP Switch (see page 25) Interrupt Line Selector (see page 26) Four-pin DIP switch. Set the memory area (base address) to be used by the Set the interrupt level from Board within the memory of the IBM the Board to the computer.
  • Page 33 Section Connecting Optical-system Cables Indicators Wired Board Name Color Status Meaning RUN Operating Green The Board is operating normally. Not lit A Board operating error (watchdog timer error) occurred. Communications One of the following errors occurred: error Communications error. Same node address used twice (i.e., address duplicate setting error).

  • Page 34: Setting Switches

    Section Connecting Optical-system Cables 2-1-2 Setting Switches The following settings must be made on on a Controller Link Support Board. Setting item Setting section Page Memory address Memory allocation switch Interrupt level Interrupt short pin Terminating resistance Terminating resistance switch (Wired Boards only) Note 1.
  • Page 35 Section Connecting Optical-system Cables 5. When using EMM386.EXE, set the memory area used by the Controller Link Support Board to a prohibited address. Parameter setting method:X = mmmm – nnnn mmmm: Starting address (leftmost 4 digits) nnnn: Ending address (rightmost 4 digits) Setting the Interrupt Set interrupt levels from the Controller Link Support Board to the computer using Level...

  • Page 36: Communications Cable

    Section Connecting Optical-system Cables Note 1. Turn OFF the power of the computer and all the peripheral devices before installing or removing the Board. 2. Utmost care is necessary when installing or removing the Board in order to prevent static electricity. Static electricity may damage the Board or com- puter.
  • Page 37 Section Connecting Optical-system Cables Connect all the shield lines of the communication cables and then ground the shield at one end of the network. The wiring method is shown below. End Board Intermediate Board End Board Terminating Terminating Terminating resistance resistance resistance with:ON...
  • Page 38 Section Connecting Optical-system Cables b) Use the connector attached to a Controller Link Support Board. 4. Strip the insulation far enough to attach the crimp terminals and twist the wire strands tight. 5. Apply electrical tape or heat-shrink tubing to the end of the cable cover that was peeled in step 1.
  • Page 39 Use a small flat-blade screwdriver with a constant width. The appropriate tightening torque is 0.2 N-m. Small flat-blade screwdriver with a constant width Note The following screwdriver is available from OMRON. Model XW4Z-00C Side Front 2-2-3 Connecting the Connector to the Board Connect the connector on the communications cable to the connector on the Board using the following procedure.
  • Page 40 Section Connecting Optical-system Cables Note 1. If the connector is disconnected, communications for the Board that was disconnected with other nodes in the network will be disabled and the net- work will be split into two at point of disconnection. Utmost care is necessary to prevent disconnection of a connector during communications.

  • Page 41: Connecting The Backup Power Supply

    Section Connecting Optical-system Cables Be sure that the backup power supply is providing sufficient current and voltage at the Board’s connector. See 1-2-11 Backup Power Supply (Optical System Only) for the backup power supply specifications. Connect the backup power supply to the power supply terminals at the bottom of the Controller Link Support Board.

  • Page 42: Installing Connectors

    Section Connecting Optical-system Cables 2-3-4 Installing Connectors A special connector is used to connect the Optical Fiber Cable to the Controller Link Support Board. Connect the nodes in order beginning with the highest node in the network and continuing on to lower nodes. This manual does not provide details on Optical Fiber Cable preparation.
  • Page 43 Section Connecting Optical-system Cables To prevent the Optical Fiber Cable from being pulled too forcefully, always use the cable securing bracket and provide space behind the Board as shown in the following diagram. Do not exceed the maximum tension for the cord and cable: Cord: 0 kg (Do not apply any tension.)
  • Page 44 Section Connecting Optical-system Cables Adjust the cables so that the tip of the cable extends a little bit past the brack- et’s pattern, check the direction of the connectors, and close the clamps. Press firmly on the tip of the clamp so that it contacts the bottom part of the clamp.

  • Page 45: Software Installation

    SECTION 3 Software Installation This section describes the procedure for installing the software necessary for using a Controller Link Support Board. Preparations ............. 3-1-1 File Structure .

  • Page 46: File Structure

    Section Confirming Normal Startup Preparations 3-1-1 File Structure The Controller Link Support Board files include the following: File name Contents INSTALL.EXE Installer INSTALL.INF Installation data file 1 DISK1 Installation data file 2 README.TXT File configuration description file CLK.CNF CONFIG.SYS sample CLKBIOS.SYS Controller Link BIOS CLKDRV.SYS...
  • Page 47 Use the copied disk for subsequent operation. If the copy is ever damaged, make a backup copy again. If the master disk is damaged, please return it to OMRON. OMRON will fix or replace the disk for a small charge.

  • Page 48: Installation Method

    Section Confirming Normal Startup 11. Press the N Key. Note Store the master installation disk carefully. Installation Method To enable application of the Controller Link Support Board, carry out the follow- ing tasks using the software installer. Copy the necessary files to the hard disk. Include device drivers (Controller Link BIOS and Controller Link drivers) in CONFIG.SYS.

  • Page 49: Starting The Installer

    Section Installation Method Example: Changing CONFIG.BAK to CONFIG.OLD. C:\>REN CONFIG.BAK CONFIG.OLD 2. The following key operations are effective with the installer. The installation method can be changed by returning control to the previous screen or instal- lation can be canceled during operation. The installation will not be com- plete if it is canceled, and the installation will need to be completed later before using the board.

  • Page 50: Copying Files

    Section Confirming Normal Startup Specifying the Process 1, 2, 3... 1. Specify the installer process when the installer has been started from a floppy disk. Move the cursor using the Up and Down Cursor Keys and press the Enter Key. Control is passed to the following process according to the selection that was made.
  • Page 51 Section Installation Method the existing directory name with the Backspace Key, enter the required directory name, and press the Enter Key. When the specified directory does not exist, it will be created automatically. 3. The files will be copies, and a bar indicating the progress will be displayed on the screen.
  • Page 52 Section Confirming Normal Startup Note This option cannot be omitted. Omitting this will cause an error when incorporat- ing the BIOS. If a value that is not within the specified range is designated, a Parameter Error will occur when the BIOS is incorporated. Unit Number Set the unit number of the Board on the computer in decimal.
  • Page 53 Section Installation Method Number of Buffers Set the number of send/receive buffers (2,014 bytes per buffer) to be used by the Board in decimal. An integer between 3 and 30 can be specified. Send and receive buffers are allocated as follows according to the number of buffers speci- fied: Send buffers: Always 1...
  • Page 54 Section Confirming Normal Startup 2. Specify whether CONFIG.SYS is to be overwritten. Move the cursor with the Up and Down Cursor Keys and press the Enter Key. When CONFIG.SYS is overwritten, the contents of the existing CONFIG.SYS are backed up in the file called CONFIG.BAK. When device drivers for Controller Link have already been entered in the existing CONFIG.SYS, the entries are invalidated by attaching “REM”...
  • Page 55 Section Installation Method Example: Change baud rate (“transmission rate”) for a Wired Board. Note The baud rate is fixed at 2 Mbps in Optical Boards, so this setting is ineffective for Optical Boards. 4. Move the cursor to the setting to be specified using the Up and Down Cursor Keys and press the Enter Key.
  • Page 56 Section Confirming Normal Startup 3-2-2 Installer Troubleshooting When an error occurs while the installer is used, take the necessary action according to the instructions listed below. Operation at time of an error Assumed cause and action The following error message was The directory containing INSTALL.EXE was specified.
  • Page 57 Section Installation Method /An — Memory Area For n, set the leftmost four digits in hexadecimal of the base address of the memory area that was set using the memory allocation setting switch on the Board. The following values can be specified for n C000, C200, C400, C600, C800, CA00, CC00, CE00, D000, D200, D400, D600, D800, DA00, DC00, DE00 Default when /An is omitted: C800 Hex.
  • Page 58 Section Confirming Normal Startup 2. If an illegal value is specified, a parameter error will occur when the BIOS is installed. /Un — Unit Number Set n to the unit number of the Board in the computer in decimal. The unit num- ber is used to identify the Board in the computer.
  • Page 59 Section Installation Method Controller Link Driver Format DEVICE=[ drive :][ directory \]CLKDRV.SYS[ option ] (Options: /Bn) For the drive and directory , specify the names of the drive and directory (abso- lute specification from the root directory) containing the driver file (CLKDRV.SYS).
  • Page 60 Link BIOS will be installed. The following message will be displayed if the Link BIOS starts normally. Controller Link BIOS Ver.1.10 (_____) (c)Copyright OMRON Corporation 1996–1998 The board type is displayed as “PC/AT” in the underlined section. Errors If a driver or a board cannot be started due to an error, the following message will be displayed.

  • Page 61: Board Indicators

    If the a driver or the Board cannot be started due to an error, the following mes- sage will be displayed. Controller Link DRIVER Ver.1.00 (c)Copyright OMRON Corporation 1996 not installed. (__________________) One of the error messages that are listed below will be displayed in underlined section.

  • Page 62: Creating Applications

    SECTION 4 Creating Applications This section describes how to create applications (user programs) that control the Controller Link Support Board. Basic Flow ............. . 4-1-1 Data Link Procedure .

  • Page 63: Basic Flow

    Section Driver Calls Basic Flow This section describes the basic procedural flow in creating the applications (user programs) necessary to use the Controller Link Support Board data link function and the message service function. Create the applications according to the flow charts in this section. The following explanations assume that the BIOS and driver have already been installed.

  • Page 64: Sample Program

    Section Sample Program Previous page Using the Support Software Programming driver calls Programming with the language library Open the driver. (See page 61) Initializing Initialize with 00 Hex (See page Enter the network using the Enter the network with 07 Hex Start the Support Software.
  • Page 65 Section Driver Calls Note *The data links can also be started or stopped from a Programming Device or by sending CV-mode commands (DATA LINK START and DATA LINK STOP) from other nodes. For details on various methods for making programs, refer to the following resources.
  • Page 66 Section Sample Program 4-1-2 Message Service Procedure The basic procedure for using the message service is outlined in the following flowchart. START Routing tables already written or not necessary Routing tables already written Write the routing tables using the Support Software. Writing routing tables Transfer the routing tables to the...
  • Page 67 Section Driver Calls For details on various methods for making programs, refer to the following refer- ences. Using the Microsoft C library: 4-2 MS-C Library Using driver calls: 4-3 Driver Calls Details on library functions and driver calls: Section 5 Commands and Driver Call Reference Usage example: 4-4 Sample Program Using the Support Software: Controller Link Support Software Operation...
  • Page 68 Section Sample Program Driver Calls Calls can be made directly to the Controller Link driver and the port controlled without using the MS-C library. The services listed in the following table are available in the Controller Link driver. Function Function code Page Initializes the Support Board.
  • Page 69 Section Driver Calls I/O Requests (Accessing After the Controller Link driver is open, Board control commands are written in the Driver) “user command packets.” Next, AX, BX, CX, DS, and DX registers are set and a DOS INT 21 Hex system call is made. Call Method User Command Packet = Board Control Command 4403 Hex...
  • Page 70 Section Sample Program Return Value Normal Completion Carry Flag: Clear (0) Error Completion Carry flag: Set (1) Error Code 06 Hex: File handle is not valid. See your DOS manual for further details. After closing the file the Controller Link Support Board cannot be controlled until the file is opened again.
  • Page 71 Section Driver Calls get_next_char: c = getch(); /* Key input */ switch (c) { case ’\n’: case ’\r’: goto get_next_char; /* If only Enter key is pushed,goes up to ’get_next_char’ */ default: continue; case ’0’: return; case ’1’: t_open(); break; case ’2’: t_close();...
  • Page 72 Section Sample Program int ret; /* Return value of this function */ printf(”\n\n2.clkclose”); ret = clkclose(); printf(”\n\nReturn value: %d”, ret); /* Display return value */ void t_send(void) /** Send a message **/ struct clkio snd; int c; /* Variable of key input int ret;...
  • Page 73 Section Driver Calls snd.text = buf; if (this_length == 0) this_length = n / 2; ret = clksend(&snd, this_length); printf(”\n\nReturn value: %d”, ret); /* Display return value */ void t_recv(void) /** Receive a message**/ struct clkio rcv; int ret; /* Return value of this function */ unsigned int len /* Message length /* Variable printf(”\n\n4.clkrecv”);...
  • Page 74 Section Sample Program ret = clkrcvw(&rcv, len, tim); printf(”\nReturn value: %d”, ret); /* Display return value */ if (ret > 0) { printf(”\n\nNet :%3d Node:%3d Unit:%3d Type:%3d Sid :%3d”, rcv.netadr, rcv.nodeadr, rcv.unitadr, rcv.type, rcv.sid); for (i = 0; i < len && i < (unsigned int)ret; i++) { if (i % 10 == 0) /* Insert ’Space’...
  • Page 75 Section Driver Calls do { /* Put the input character to character string(tmp) */ if (’0’ <= (c = getch()) && c <= ’9’ || ’a’ <= c && c <= ’f’) { putchar(c); tmp[i++] = (unsigned char)c; else if (c == ’\b’ && 0 < i) { printf(”\b \b”);...
  • Page 76 Section Sample Program if (i % 10 == 0) /* Insert ’Space’ every 10 characters */ printf (” ”); if (i % 30 == 0) /* Insert ’CR’ every 30 characters printf(”\n”); printf(”%02x”, buf[i]); void t_writ2(void) /** DataLink data write(no cache) **/ unsigned int siz /* Write data length ,off...
  • Page 77 Section Driver Calls void t_stat(void) /** Status read **/ unsigned int len /* Data length /* Variable int ret; /* Return value of this function */ printf(”\n\n8.clkstatrd”); printf(”\n\nLeng(1–68) : ”); gets(tmp); len = (unsigned int)atoi(tmp); ret = clkstatrd(buf, len); printf(”\nReturn value: %d”, ret); /* Display return value */ if (!ret) { printf(”\n”);...
  • Page 78 SECTION 5 Commands and Driver Call Reference This section gives details on the C-language library commands and the driver calls supported by the Controller Link Support Board. Library Commands and Driver Call List ........C Commands .
  • Page 79 Section C Commands Library Commands and Driver Call List Function C-library commands Driver call codes Initialize 00 Hex clkopen Opens the Controller Link driver and adds the Support Board to the network. Closes the Controller Link driver clkclose and removes the Support Board from the network.
  • Page 80 Section C Commands 5-2-1 DRIVER OPEN — clkopen The clkopen command opens the Controller Link driver and adds the Support Board to the network. Other C commands in the library can be executed after the clkopen command has been executed. Use the clkclose command to close the device driver and remove the Support Board from the network.
  • Page 81 Section C Commands response. Refer to Section 7 Message Service for details on FINS commands and responses. The destination information and command/response data are specified in the structure of clkio . Note The FINS command or response will not be sent when the command is executed in the program, but when the Support Board receives the token, giving it the right to send.
  • Page 82 Section C Commands 2. This command can be used not only to send FINS commands but also to send responses when FINS commands are received by the user program (set the type parameter to 1.) 3. When sending a response, be sure to attach the end code and a service ID (sid) that is the same as the command service ID (sid.) Responses The following table shows the possible responses when clksend is executed.
  • Page 83 Section C Commands Parameter Type IN/OUT Function nodeadr Integer Specifies the source node address. (0 to 126) Local Controller Link Support Board 1 to 32: Node on a Controller Link Network 1 to 62: Node on a SYSMAC LINK Network 1 to 126: Node on a SYSMAC NET Network unitadr...
  • Page 84 Section C Commands Responses The following table shows the possible responses when clkrecv is executed. Response Meaning Positive The number of bytes of data received in the reception buffer. (The number command was executed normally.) –1 Parameter error. –10 A system call error occurred. –16 A Support Board error has occurred.
  • Page 85 Section C Commands Parameter Type IN/OUT Function unitadr Integer Indicates the source unit address. 16 to 31: Controller Link Support Board (16 to 31: Board with unit numbers 0 to 15) or CPU Bus Unit. 254: The Board or Unit connected to the network. Computer ’s user program PC’s CPU Unit text...
  • Page 86 Section C Commands 5-2-6 DATA LINK READ — clkread The clkread command is used to read data from a data link area. This command can be used only when a data link cache has been set using the Controller Link BIOS option.
  • Page 87 Section C Commands Responses The following table shows the possible responses when clkread is executed. Response Meaning The command was executed normally. –1 Parameter error. –10 A system call error occurred. –11 Command could not be executed. –16 A Support Board error has occurred. Related Commands clkwrite () 5-2-7 DATA LINK WRITE —...
  • Page 88 Section C Commands Note 1. Data should be written only to the send area of the data link area allocated to the Support Board. 2. If a data link cache has not been set using the Controller Link BIOS option in the CONFIG.SYS file, an error will occur (command cannot be executed.) 3.
  • Page 89 Section C Commands the rcvbuf parameter. The structure of the operational status data is shown below. b7: Local node data 0: Not participating in data link or data link inactive. links 1: Participating in data link Operation mode 0:Inactive 1:Manual setting 2:Automatic setting 4: Local node data link not participating (Active data links in network but...
  • Page 90 Section C Commands 5-2-9 NETWORK ADD/REMOVE — clkcmd The clkcmd command is used to add the Support Board to the Network or remove it from the Network. Unlike the clkopen and clkclose commands, clkcmd does not open or close the Controller Link driver, it operates only when the Con- troller Link driver is already open.
  • Page 91 Section C Commands Parameters The parameters for the clkread command are described in the following table. Parameter Type IN/OUT Function linkbuf Character Indicates the area where the data link data is stored. string Data can be from 0 to FF Hex; two bytes equal one word.
  • Page 92 Section C Commands Responses The following table shows the possible responses when clkread is executed. Response Meaning The command was executed normally. –1 Parameter error. –10 A system call error occurred. –11 Command could not be executed. –16 A Support Board error has occurred. –26 No receive data clkwrite2 ()
  • Page 93 Section C Commands cated to nodes 1 and 2, so the offset parameter is set to 2 n bytes. All m words will be written, so the size parameter is set to 2 m bytes. Node address 32 Node address 2 Offset address Node address 1...
  • Page 94 Section Driver Calls Driver Calls This section describes driver calls which don’t use library files. The following table shows the driver calls that can be made for the Controller Link Support Board. Refer to Section 4 Creating Applications for details on driver calls Driver call Function code...
  • Page 95 Section Driver Calls 5-3-2 MESSAGE SEND — 01 Hex The MESSAGE SEND (01 Hex) driver call is used to send FINS commands and responses. A response is automatically returned to commands addressed to the Support Board, but not to commands addressed to the computer. For further details on FINS commands and responses refer to Section 7 Message Service.
  • Page 96 Section Driver Calls Parameter Function Service ID The “service ID number;” can be used to identify the process which is the source of the transmission. 00 to FF Hex When sending a response, use the same service ID as for the command. Destination network 00 to 7F Hex (00 Hex: Local network) address...
  • Page 97 Section Driver Calls 5-3-3 MESSAGE RECEIVE — 02 Hex The MESSAGE RECEIVE (02 Hex) driver call is used to read FINS commands and responses received in the reception buffer and store the data according to the parameters. You can specify whether or not to wait when there is no receive data to read.
  • Page 98 Section Driver Calls Parameters The parameters for MESSAGE RECEIVE (02 Hex) are described in the follow- ing table. Parameter Function Function code 02 Hex (fixed) Receive waiting mode Designates whether or not to wait to receive data. 00 Hex: No waiting (Completes operations without waiting to receive data.) 01 Hex: Waiting (Receives data for the “receive waiting time.”)
  • Page 99 Section Driver Calls 2. Use MESSAGE RECEIVE (02 Hex) as often as possible to read data from the reception buffer. If the reception buffer fills up, more data cannot be received. 3. The size of the reception buffer is specified using the /B option when instal- ling the Controller Link driver.
  • Page 100 Section Driver Calls Read Data Storage Area The read data storage area contains all data (No. of bytes of data read) from the read data storage address. Offset: Content Bytes +0 Read data Word data (bits 15 to 8) Word data (bits 7 to 0) +n–2 +n–1 n: Total No.
  • Page 101 Section Driver Calls Note 1. Before using DATA LINK READ (03 Hex), be sure to allocate enough memory to the read data storage area. 2. If a data link cache has not been set using the Controller Link BIOS option in the CONFIG.SYS file, an error will occur (command cannot be executed.) 3.
  • Page 102 Section Driver Calls Parameters The parameters for DATA LINK WRITE (04 Hex) are described in the following table. Parameter Function Function code 04 Hex (fixed) Write start address Indicates the offset from the beginning of the data link area. This parameter specifies the beginning address from which data will be written.
  • Page 103 Section Driver Calls Responses The following table shows the possible responses when DATA LINK WRITE (04 Hex) is executed. Response Meaning 00 Hex The command was executed normally. 31 Hex A Support Board error has occurred. 32 Hex Command cannot be executed. 41 Hex Parameter error.
  • Page 104 Section Driver Calls The structure of the operational status data is shown below. b7: Local node data 0: Not participating in data link or data link inactive. links 1: Participating in data link Operation mode 0:Inactive 1:Manual setting 2:Automatic setting 4: Local node data link not participating (Active data links in network but Operation mode...
  • Page 105 Section Driver Calls 5-3-7 NETWORK ADD/REMOVE — 07 Hex The NETWORK ADD/REMOVE (07 Hex) driver call is used to add the Support Board to the network or remove it from the network. Call Procedure 4403 Hex File handle (the return value when a file is opened) 0003 Hex (Total number of bytes in user command packet) DS:DX The first address storing the command packet (segment:offset)
  • Page 106 Section Driver Calls User Command Packet Offset: Content Bytes +0 20 Hex (function code) +1 Read start address (Low) (High) +3 Read data storage address Offset (Low) (High) +5 Read data storage address Segment (Low) (High) +7 No. of bytes of data read (Low) (High) +9 Read node address...
  • Page 107 Section Driver Calls after one transmission cycle.) If attempts are made to read the same data contin- uously, an error (no receive data) will result. In the example below, the m words of the data link area allocated to node 3 are read.
  • Page 108 Section Driver Calls User Command Packet Offset: Content Bytes +0 21 Hex (function code) +1 Write start address (Low) (High) +3 Write data storage address Offset (Low) (High) +5 Write data storage address Segment (Low) (High) +7 No. of bytes of write data (Low) (High) +9 Write node address...
  • Page 109 Section Driver Calls In the example below, data from the wlinkbuf area is written to the m words of the data link area allocated to the Support Board (node 3). There are n words allo- cated to nodes 1 and 2, so the write start parameter is set to 2 n bytes.
  • Page 110 SECTION 6 Data Links This section describes how to use data links in a Controller Link Network. What Are Data Links? ........... . . 6-1-1 Data Link Specifications .

  • Page 111: Checking Data Link Status

    Section Checking Data Link Status What Are Data Links? Data links automatically exchange data in the preset areas between nodes (PCs and/or computers) on one network. Data links can be freely created for C200HX/ HG/HE PCs, CV-series PCs, CS1-series PCs, and IBM PC/AT or compatible computers.
  • Page 112 Section Starting and Stopping Data Links Manual Setting Options The following options can be set when manually setting data links. Offsets Data of only the specified number of words can be received starting from the specified word position. The starting word is set as an offset from the beginning of the send data.

  • Page 113: Using Offsets

    Section Checking Data Link Status All nodes can be specified to either participate or not participate in the data link. The data link areas are exactly the same and common to all nodes participat- ing in the data links. Note The Controller Link Support Software contains a function called “Easy Setting”...

  • Page 114: Data Link Specifications

    Section Starting and Stopping Data Links Application Example of Using Offsets In the following example, the send data from node 1 is split into three parts and each part is received by a different node, i.e., each of the other nodes receives only part of the send data from node 1.

  • Page 115: Differences Between Manual And Automatic Setting

    Section Checking Data Link Status 6-1-2 Differences Between Manual and Automatic Setting Item Manual setting Automatic setting Determination of nodes Determined by setting data link tables. Determined by the data link parameters participating in a data set in the data link startup node (the link node used to start the data links).

  • Page 116: Manual Setting

    Section Starting and Stopping Data Links 2. When the Controller Link Support Board has been set as the startup node, data links must be manually set. 3. A data link mode can be set in a data link startup node only. The data link mode setting is determined by the data link mode of the startup node even if the data link mode settings of the nodes participating in the data links are different from the settings in the startup node.
  • Page 117 Section Checking Data Link Status 2. When transferring the data link tables to a Controller Link Unit for a CV-se- ries PC, set the System Protect Keyswitch on the CPU Unit to “NORMAL.” Otherwise, data link tables cannot be written normally. 3.
  • Page 118 Section Starting and Stopping Data Links Setting item Setting range Area 2 Data link CIO 0 to 2,555, LR 0 to 199, Dm d to 24,575, EM 0 to 32,765 (Banks 0 to 7) start word The Controller Link Support Board uses both area 1 and area 2, but the address set for the first link word is not used.
  • Page 119 Section Checking Data Link Status SAMPLE1.CLK: Same Allocation to All Nodes Data Link Area Structure C200HX C200HX C200HX C200HX Node 1 Node 2 Node 3 Node 4 Data Link Areas Area 1 LR000 LR010 LR020 LR030 LR049 Area 2 D00000 D00200 D00300 D00400...
  • Page 120 Section Starting and Stopping Data Links Checking the Data Link Tables Transferring the Data Link Tables Saving the Data Link Tables...
  • Page 121 Section Checking Data Link Status SAMPLE2.CLK: Different Allocations to Each Node Data links can be created so that one node does not receive from all other nodes or so that some nodes do not send or receive any data at all. In the following example, node 2 does not receive data from node 3 and node 3 does not receive data from node 1.
  • Page 122 Section Starting and Stopping Data Links Data Link Tables SAMPLE3.CLK: Creating Data Link Groups within a Network A data links consisting of multiple groups within a single network can be created by setting data link tables. Send and receive areas are created for only the nodes in each group, as shown below.
  • Page 123 Section Checking Data Link Status Device Information Setting Data Link Tables...
  • Page 124 Section Starting and Stopping Data Links SAMPLE4.CLK: Receiving Only Part of Send Data and Offsets Note Only area 2 is used in this example. Data Link Area Structure IBM PC/AT or C200HX C200HX C200HX compatible Node 1 Node 2 Node 3 Node 4 Data Link Areas (With Data Link Cache) IBM PC/AT or...
  • Page 125 Section Checking Data Link Status Device Information Setting Data Link Tables 6-2-4 Automatic Setting: “Select All” Data links can be automatically created by setting values in the DM parameter area of the PC’s CPU Unit of the startup node. The settings are made using a Programming Console “or the SYSMAC Support Software.
  • Page 126 Section Starting and Stopping Data Links Note 1. Parameters for automatically setting data links can only be set in PCs. Refer to the Controller Link Units Operation Manual (W309) for details. 2. An IBM PC/AT or compatible computer (Controller Link Support Board) can- not be the startup node for an automatically setting data links.
  • Page 127 Section Checking Data Link Status Caution Check the following items before starting data links. If incorrect data link tables or parameters are set, injury may result due to unexpected operation of the sys- tem. Even if the correct data link tables and parameters have been set, do not start or stop data links before verifying that there will be no adverse influence on the system.
  • Page 128 Section Starting and Stopping Data Links C200HX/HG/HE Startup Node 15 14 13 12 11 10 9 AR 07 Data link Start Bit for level 0 (AR 0700) Start: Changed from OFF to ON or set to ON when power is turned on Stop: Changed from ON to OFF Data link Start Bit of level 1 (AR 0704) Start: Changed from OFF to ON or set to ON...

  • Page 129: Led Indicators

    Section Checking Data Link Status Issuing the FINS Command from CV-series and CS1-series PCs FINS command: DATA LINK START/ DATA LINK STOP Node in data links Checking Data Link Status There are two methods for checking the status of active data links: Check the LED indicators on the front of the Units.
  • Page 130 Section Starting and Stopping Data Links Status Values Description PC status 0: Program execution stopped Indicates if the PC program is being executed or not. 1: Program being executed Always 1 for Controller Link Support Board nodes. CPU Unit error 0: No error Indicates if an error has occurred in the PC.

  • Page 131: Checking By Manipulating Bit/Word Status

    Section Checking Data Link Status 6-4-3 Checking by Manipulating Bit/Word Status Although the data link function itself may be operating correctly, the data link areas may have been input incorrectly. After you have confirmed that the data link function is operating normally, check to see whether or not the data link is operating as intended, i.e., check to see if the desired bits/words data is being transferred to the intended words at other nodes.
  • Page 132 SECTION 7 Message Service This section explains how to use the message service provided by a Controller Link Support Board. Introduction ............. 7-1-1 Message Service Specifications .
  • Page 133 Section Commands and Responses for the Support Board Introduction A message service is a command/response system used for data transmission between nodes on a network, i.e., PC to PC, PC to computer, and computer to PC. The message service can also be used to control operations, such as mode changes.

  • Page 134: Using The Message Service

    Section Commands and Responses for the Support Board SEND/RECV/CMND SEND(192), RECV(193), and CMND(194) can be employed when using CV-se- ries PC Controller Link Units. SEND(90) and RECV(98) can be used with C200HX/HG/HE PCs, but CMND(194) cannot. Command Features SEND(192) SEND is used to transfer data from any memory area at the source node to another node, and write the data to any memory area at that node.
  • Page 135 Section Commands and Responses for the Support Board Direction Data transmission Control by command Computer to Computer Computer Computer Computer Computer User User User User program program program program Library function or driver call Library function or Library function or driver Controller Link for sending message + FINS driver call for...

  • Page 136: Fins Command/Response Format

    Section Commands and Responses for the Support Board 7-1-5 FINS Commands for the Support Board Command code Name Page DATA LINK START DATA LINK STOP CONTROLLER DATA READ CONTROLLER STATUS READ NETWORK STATUS READ DATA LINK STATUS READ ECHOBACK TEST BROADCAST TEST RESULTS READ BROADCAST TEST DATA SEND ERROR LOG READ...

  • Page 137: Data Formats

    Section Commands and Responses for the Support Board Note All settings below are shown in hexadecimal except where otherwise indicated. Reserved. Set to 00. Gateway count. Set to 02. Destination network address. Specify within the following ranges. Local network 01 to 7F: Remote network (1 to 127 decimal) Destination node number.

  • Page 138: Command Codes

    Section Commands and Responses for the Support Board Responses When the library function or driver call for message reception is executed, the data from the command code to the end of the text (with the data determined by the individual command) is stored as reception data, as shown in the following diagram.

  • Page 139: Data Link Stop

    Section Commands and Responses for the Support Board 7-3-3 DATA LINK STOP Stops the Controller Link Network data links. Command Block Command code Response Block Command Response code code The DATA LINK STOP command can be received only while the data links is active.

  • Page 140: Controller Status Read

    Section Commands and Responses for the Support Board The first “V1.00” represents the Support Board version number, and the second represents the Communications Controller version number. Node address (response): The Support Board’s node address is returned between 01 and 20 Hex (1 to 32). Wired/Optical (response) Not used 0: Wired...
  • Page 141 Section Commands and Responses for the Support Board Status 3 (response): Error information. The configuration is as follows: 1: Error log exists 1: Node address setting error 1: Data link error stop 1: Duplicate node address setting error 1: Controller transmitter error 1: Network parameter error 1: Controller hardware error Note A network parameter error occurs if the registered network parameter contents...

  • Page 142: Network Status Read

    Section Commands and Responses for the Support Board 7-3-6 NETWORK STATUS READ Reads the operating status of the entire Controller Link Network. Command Block Command code Response Block 8 bytes 62 bytes 32 bytes Command Response Participation Actual Data link Data link data code code...

  • Page 143: Data Link Status Read

    Section Commands and Responses for the Support Board Data link recurring error status (response): Indicates whether an error con- tinues to occur at a node when data link data is received. If an error continues to occur at the same node when the data is received, the bit corresponding to that node turns to “1”...

  • Page 144: Echoback Test

    Section Commands and Responses for the Support Board Parameters Status flag (response): The overall data link status is returned in one byte of data, as shown in the following diagram. 0 0 0 0 1: Data link table error 1: No data link table Data link mode during operation 0: Manual settings Data link operational status...

  • Page 145: Broadcast Test Results Read

    Section Commands and Responses for the Support Board Command Block 1,998 bytes max. Command Test data code Response Block 1,998 bytes max. Command Response Test data code code Parameters Test data (command, response): For the command, up to 1,998 bytes of data can be specified to be sent to a specified node.

  • Page 146: Error Log Read

    Section Commands and Responses for the Support Board There is no response to this command. The control data must be set as follows when this command is issued: Destination node address: FF (Hex) (for broadcasting the data) Destination unit address: FE (Hex) (for the Controller Link Support Board or Unit) Response required/not required flag: 1 (response not required)

  • Page 147: Error Log Clear

    Section Commands and Responses for the Support Board Date and time: These parameters show the seconds, minutes, hour (0 to 23), date, month, and year (the rightmost two digits) in BCD specifying the time that the error occurred. Note If the PC does not have the specified number of records, all the records that have been stored in the PC up to the point that the command is executed will be returned.
  • Page 148 Section Commands and Responses for the Support Board passed between two Link Units, 2) Data was not passed successfully between a Link Unit and another Unit, such as the PC’s CPU Unit, or 3) The destination of a gateway does not exist. In any case, the Unit that was not able to transfer data will return a response indicating a network relay error.

  • Page 149: Response Codes And Troubleshooting

    Section Commands and Responses for the Support Board Example 2 In this example, the specified destination node or the next relay node does not exist. Computer Computer Controller Link Unit Controller Link Unit Controller Link Unit Controller Link Unit Controller Link Support Board Controller Link Support Board Transmission Transmission...
  • Page 150 Section Commands and Responses for the Support Board Main code Sub- Probable cause Remedy code 02: Destination node Destination node not part of Network Add to Network. error No node with the specified node Check the destination node’s node address address.
  • Page 151 Section 7-44 Commands and Responses for the Support Board Main code Sub- Probable cause Remedy code 11: Parameter error A correct memory area code has not Check the command’s memory area code been used or Extended Data Memory and set the appropriate code. is not available.
  • Page 152 Section Commands and Responses for the Support Board Main code Sub- Probable cause Remedy code 21: Write not possible The specified area is read-only or is If the specified area is read-only, the write write-protected. cannot be performed. If it is write-protected, turn off the write-protect switch and execute the instruction again.
  • Page 153 Section Commands and Responses for the Support Board Main code Sub- Probable cause Remedy code 25: Unit error Parity/checksum error occurred Transfer correct data into memory. because of incorrect data. I/O setting error (The registered I/O Either change the actual configuration to configuration differs from the actual.) match the registered one, or generate the I/O table again.
  • Page 154 Section Commands and Responses for the Support Board Main code Sub- Probable cause Remedy code 26: Command error The specified area is not protected. The program area is not protected, so it This response code will be returned if isn’t necessary to clear protection. an attempt is made to clear protection on an area that is not protected.

  • Page 155: Network Interconnections

    SECTION 8 Network Interconnections This section describes the method used to connect multiple networks through CV-series or CS1-series PCs. What is Network Interconnection? ..........8-1-1 Interconnecting Controller Link Networks .

  • Page 156: What Is Network Interconnection

    Section What is Network Interconnection? What is Network Interconnection? Network interconnection enables commands and responses for the message service to be sent and received across multiple networks. The three networks listed below can be interconnected to achieve this. Controller Link Networks SYSMAC NET Link Networks SYSMAC LINK Networks 8-1-1 Interconnecting Controller Link Networks...

  • Page 157: Creating Routing Tables

    Section Routing Tables Communications across bridges or gateways can include up to three net- works, including the local network (data generating network). Network 1 (local network) Network 2 Network 3 Although 2,012 bytes of data (including the header) can be sent and received with a Controller Link, the maximum amount of data is limited by any network the data passes through, i.e., the network with the the smallest capacity will deter- mine the limit.

  • Page 158: Setting Routing Tables

    Section What is Network Interconnection? Relay Network Table A relay network table provides the node and network addresses corresponding to the initial relay point (first point the data must go to) en route to a target net- work (end network) not directly connected to the local PC. The table traces the route from the relay point to the end network.
  • Page 159 Section Routing Tables Local Network: (Loc Netwk) Address 1 through 127 for the network connected to the Support Board. SIOU Unit No.: (SIOU unit #) Controller Link Support Board unit number (0 to 15) With the Support Board, only one entry can be set in the local network table. The Support Board’s SIOU unit number is the value set for the Controller Link BIOS by CONFIG.SYS (i.e., using the /U option).
  • Page 160 Section What is Network Interconnection? Computer Unit number b Controller Link Network address A Local Network Table SIOU Netwk unit # Example 2 The following example show the settings for a relay network table connecting three networks. Relay Network Tables Relay PC 1 Netwk...
  • Page 161 Section Routing Tables Example 3 The network structure example in the figure below shows routing tables for all nodes. SNT: SYSMAC NET LINK Unit Unit 5 CLK: Controller Link Unit/ Board Node 6 SLK: SYSMAC LINK Unit Network 10 Unit 3 Unit 4 Node 4 Node 5...
  • Page 162 Section What is Network Interconnection? Routing Tables on PC 4 Local Network Table Relay Network Table SIOU Relay Netwk unit# Netwk PC ID Netwk Node Routing Tables on PC 5 Local Network Table Relay Network Table SIOU Relay Netwk unit# Netwk PC ID Netwk...
  • Page 163 SECTION 9 Communications Timing This section explains details on Controller Link Network communications. Refer to this section for network communications that require accurate communications timing. Network Parameters ............9-1-1 Controller Link Communications .

  • Page 164: Network Parameters

    Section Communications Cycle Time Network Parameters This section explains how to use Controller Link Network communications and how to adjust the network parameters to match the system. 9-1-1 Controller Link Communications The token bus method is used for communications in the Controller Link Net- work.

  • Page 165: Specifying Network Parameters

    Section Communications Cycle Time 9-1-3 Network Parameters Network parameters are also used to control network operations. Network parameters are read from the polling node and distributed to all other nodes when the Controller Link Network is started. In this way, all nodes on the network always have the same network parameter settings.

  • Page 166: Active Data Links

    Section Communications Cycle Time 9-2-1 Active Data Links The following equations are used to calculate the communications cycle time when data links are operating. (The communications cycle time will vary some- what depending on the baud rate and the conditions at that particular time.) Wired Systems Baud rate Equation...

  • Page 167: Inactive Data Links

    Section Communications Cycle Time 9-2-2 Inactive Data Links The following equations are used to calculate the communications cycle time when the data links are inactive. (The communications cycle time will vary some- what depending on the baud rate and the conditions at that particular time.) Wired Systems Baud rate Equation...
  • Page 168 Section Communications Cycle Time 9-3-1 Computer to PC In the following diagram illustrating the maximum data link I/O response time, a C200HX/HG/HE is used for the PC (#2) and the PC’s cycle time is greater than or equal to the communications cycle time. Computer at node #1 User application (clkwrite)
  • Page 169 Section Communications Cycle Time 9-3-2 PC to Computer In the following diagram illustrating the maximum data link I/O response time, a C200HX/HG/HE is used for the PC (#2) and the PC’s cycle time is greater than or equal to the communications cycle time. Input Input device I/O refresh...
  • Page 170 Section Communications Cycle Time Message Service Delay Times The following diagram illustrates the maximum message service transmis- sion delay time. In this example, the MEMORY AREA READ FINS command is sent to the PC at node #2 by the user application at the computer at node Computer at User application node #1...

  • Page 171: Troubleshooting And Maintenance

    SECTION 10 Troubleshooting and Maintenance This section provides information on troubleshooting errors that occur during Controller Link Support Board operation, as well as daily inspection, cleaning, and other maintenance procedures. 10-1 Troubleshooting Using Indicators ..........10-1-1 Using the RUN, ERC, ERH and INS Indicators (Wired Boards) .

  • Page 172: Troubleshooting Using Indicators

    Section 10-1 Status Information and Troubleshooting 10-1 Troubleshooting Using Indicators This section describes the errors shown by the Controller Link Support Board indicators and possible remedies. Wired Board Optical Board RUN: Operating RUN: Operating ERC: Communications error ERR: Error ERH: EEPROM error INS: Network participation...
  • Page 173 Section 10-1 Troubleshooting Using Indicators Indicators Probable cause Probable cause Probable remedy Probable remedy Terminating resistance is not set correctly. Turn ON the terminating resistance at the nodes at both ends of the Network and turn it OFF at all other nodes. Cables are not connected correctly.
  • Page 174 Section 10-1 Status Information and Troubleshooting Indicators Probable cause Probable remedy Cables are not connected correctly. Check the cable connections and reconnect correctly. The node address is larger than the maximum Either reset the maximum node address using node address set for the network parameters. the Controller Link Support Software or reset the node address to below the maximum.
  • Page 175 Section 10-1 Troubleshooting Using Indicators Indicators Probable cause Probable remedy Data link operating normally. Flashing When manual setting was used, there is an error in Refer to 6-2-2 Manual Setting and reset the data the data link table. link table. Not lit For manual setting, there are no data link tables set Set data link tables for the local node.
  • Page 176 Section 10-2 Status Information and Troubleshooting 10-2 Status Information and Troubleshooting The Controller Link Support Board contains status information which reflects the current status of communications and the Board. This status information can be read using the STATUS READ or DATA LINK AREA READ FINS command. The cause of the error can be found by reading the status information.

  • Page 177: Error Processing

    Section 10-2 Troubleshooting Using Indicators 10-2-2 Error Processing Data Link Status Bit status Probable cause Probable remedy PC’s CPU Unit error is 1: ON A fatal PC error, non-fatal PC error, Refer to the PC’s operation manual or a watchdog timer error has and correct the error.
  • Page 178 Section 10-2 Status Information and Troubleshooting Other Status Bit status Probable cause Probable remedy Inconsistent network parameters is 1: Indicates that the network parameters Check the network parameters on the recorded in the CPU Unit’s EEPROM Network in use using the Controller differ from the values of the Network Link Support Software, and reset in use.

  • Page 179: Error Log Table

    Section 10-3 Troubleshooting Using Indicators 10-3 Error Log The error log records errors that occur in the Controller Link Support Board and the time they occur. The error log can be read or cleared using the Controller Link Support Software, a PC Programming Device, such as the SYSMAC Support Software, or the message service (FINS commands for the Controller Link Sup- port Board.) 10-3-1 Error Log Table...

  • Page 180: Error Codes

    Section 10-3 Status Information and Troubleshooting 10-3-2 Error Codes The following table lists the error codes (in 4-digit hexadecimal) and the contents of the errors. Detail code Error Contents Correction Recorded code code 1st byte 2nd byte EEPROM Command block 0101 Transmission failed;...
  • Page 181 Section 10-3 Troubleshooting Using Indicators Error Error Contents Contents Detail code Correction Correction Recorded Recorded code code 1st byte 2nd byte EEPROM EEPROM 0203 EEPROM error 01 Hex: 01 Hex: Reset the relevant data. If the Read error Data link error occurs again replace the 02: Hex: tables...

  • Page 182: Reading And Clearing Error Logs

    Section 10-4 Status Information and Troubleshooting 2. Error Status The status of each bit indicates that an error has occurred as given in the diagram below. 1: Token timeout error 1: Polling timeout error 1: Communications controller hardware error 1: Polling node was changed 1: Nodes in Network changed (added or removed) 1: Communications controller send error 1: Duplicate node address setting error...

  • Page 183: Handling Precautions

    Remove any lint or threads left from the cloth, and remount the Board. When returning a faulty Board for repairs, always attach a detailed fault report to the Unit and return to you nearest OMRON outlet as listed at the back of this manual.

  • Page 184: Replacing The Board

    Section 10-5 Status Information and Troubleshooting 10-5-2 Replacing the Board Note 1. When replacing the Board, do not reconnect that node to the Network before carrying out the procedures listed below. In particular, a node with a small address will become the polling node and communicate the initial network parameter status to other nodes, so there is the chance that network param- eters in the entire Network will be damaged.
  • Page 185 Section 10-5 Troubleshooting Using Indicators 3. Detach the communications cables attached to the Controller Link Support Board to be replaced and remove the Board. 4. Set the new Controller Link Support Board’s memory allocation switch, allocation setting circuit pin, and the terminating resistance switch to the same as for the previous Board.
  • Page 186 Appendix Standard Models Controller Link Support Boards Applicable Connection type Model number Remarks computer IBM PC/AT or Wired 3G8F5-CLK21-E Controller Link compatible compatible Support Software Support Software Optical 3G8F5-CLK11-E included. Controller Link Units Applicable PC Connection type Model number Remarks CV-series PCs Wired CVM1-CLK21...

  • Page 187: Standard Models

    Appendix Standard Models Optical Fiber Cables Name Specifications Model H-PCF cables Black 10 m S3200-HCCB101 50 m S3200-HCCB501 100 m S3200-HCCB102 500 m S3200-HCCB502 1,000 m S3200-HCCB103 Orange 10 m S3200-HCCO101 50 m S3200-HCCO501 100 m S3200-HCCO102 500 m S3200-HCCO502 1,000 m S3200-HCCO103 Note The Optical Fiber Cable model numbers are as follows.

  • Page 188: Cpu Units

    S3200-CN-25-25 (Specify length (m) when ordering.) Note Special training is required to assemble Optical Fiber Cables and con- nectors with epoxy adhesive. Contact your OMRON dealer for details on other optical fiber cords and cables. CPU Units and Peripheral Devices...

  • Page 189: Revision History

    Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. Cat. No. W307-E1-3 Revision code The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version.

This manual is also suitable for:

Sysmac 3g8f5-clk21-e

Table of Contents