YOKOGAWA FA-M3 Instruction Manual
  1. Manuals
  2. Brands
  3. YOKOGAWA Manuals
  4. Control Unit
  5. FA-M3 Vitesse
  6. Instruction manual
YOKOGAWA FA-M3 Instruction Manual

YOKOGAWA FA-M3 Instruction Manual

Devicenet scanner module
Hide thumbs Also See for FA-M3:
Table of Contents

Advertisement

Quick Links

Download this manual
Instruction
Manual
DeviceNet Scanner Module
IM 34M6H28-01E
Addendum
See at the end of this manual.
IM 34M6H28-01E
1st Edition
Y okogawa Electric Corporation

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FA-M3 and is the answer not in the manual?

Questions and answers

Related Manuals for YOKOGAWA FA-M3

Summary of Contents for YOKOGAWA FA-M3

  • Page 1 Instruction Manual DeviceNet Scanner Module IM 34M6H28-01E Addendum See at the end of this manual. IM 34M6H28-01E 1st Edition Y okogawa Electric Corporation...
  • Page 2 Blank Page...
  • Page 3 Refer to the document number in all communications; also refer to the document number or the document model code when purchasing additional manuals. Media No. IM 34M6H28-01E (CD) 1st Edition : Feb. 1999 (YK) IM 34M6H28-01E 1st Edition : Feb.01,1999-00 All Rights Reserved Copyright © 1999, Yokogawa Electric Corporation...

  • Page 4: Important

    (6) Every effort has been made to ensure accuracy in the preparation of this manual. However, should any errors or omissions come to the attention of the user, please contact the nearest Yokogawa Electric representative or sales office. IM 34M6H28-01E...
  • Page 5 <Toc> <Ind> <Rev> <Preface> Safety Precautions when Using/Maintaining the Product The following safety symbols are used on the product as well as in this manual. CAUTION This symbol indicates that the operator must follow the instructions laid out in this manual in order to avoid the risk of personnel injuries or fatalities or damage to the instrument.
  • Page 6 WARRANTY that is provided separately. (2) Yokogawa Electric assumes no liability to any party for any loss or damage, direct or indirect, caused by the user or any unpredictable defect of the product.
  • Page 7 Never use solvents such as paint thinner for cleaning: • Gently clean the surfaces of the FA-M3 controllers with a piece of soft cloth soaked in water or a neutral detergent. • Do not use solvents such as paint thinner for cleaning, as they may cause deforma- tion, discoloration, or malfunctioning.
  • Page 8 <Toc> <Ind> <Rev> <Preface> Avoid storing the FA-M3 controllers in places with high temperature or humidity: • Since the CPU module has a built-in battery, avoid storing it in places with high tem- perature or humidity. • Since the service life of the battery is drastically reduced by exposure to high tem- peratures, so take special care (storage temperature can be from -20 to 75 C).
  • Page 9 With reference to the equipment types in the WEEE directive Annex 1, this product is classified as a “Monitoring and Control instrumentation” product. Do not dispose in domestic household waste. When disposing products in the EU, contact your local Yokogawa Europe B. V. office. IM 34M6H28-01E 1st Edition : Feb.01,1999-00...

  • Page 10: N Introduction

    <Toc> <Ind> <Rev> <Preface> Introduction I Overview of the Manual This is the instruction manual of the DeviceNet Scanner Module of the FA-M3 Multi-control- ler. I Other Instruction Manuals Consult the following FA-M3 manuals as necessary when using this module: •...

  • Page 11: Table Of Contents

    Toc-1 <Int> <Ind> <Rev> FA-M3 DeviceNet Scanner Module IM 34M6H28-01E 1st Edition CONTENTS Important ...................... ii Introduction....................viii Overview ....................1-1 Overview of DeviceNet................2-1 Network Configuration..................2-1 I/O Communications (I/O Slave Message) ............2-3 Message Communications (Explicit Peer-to-Peer Message) ......2-4 Preparations for Operation ................
  • Page 12 Toc-2 <Int> <Ind> <Rev> Start/Stop Operation and Status Management (Example of Programming) ................7-12 I/O Data Access (Example of Programming) ........... 7-16 Message Communications................ 8-1 Module Operation ..................... 8-1 Interface ......................8-4 8.2.1 Request and Response Formats ............8-4 8.2.2 Exit Codes ..................

  • Page 13: Overview

    Each equipment type is defined by a device profile (specifications which define the opera- tion of the equipment). Equipment is built according to these profiles, thus resulting in the compatibility and interchangeability of the equipment. Personal computer/Workstation Higher-level network FA-M3 FA-M3 Display Special purpose...
  • Page 14 • Operation in a multi-master environment with decentralized control is also possible. • 16 modules of this kind can be installed in a single FA-M3. It is easy to manage mul- tiple-point I/O data and to add new lines.

  • Page 15: Overview Of Devicenet

    <Toc> <Ind> <2. Overview of DeviceNet > Overview of DeviceNet An explanation of the functions which are supported by this module and which are related to the DeviceNet specifications is given here. SEE ALSO 1) For details on the DeviceNet specifications, see also to the DeviceNet Specifications Manual, published by ODVA (Open Device Net Vendor Association, Inc.).
  • Page 16 <Toc> <Ind> <2. Overview of DeviceNet > • Cable Five special purpose cables (2 signal lines, 2 power supply lines, and 1 SHIELD cable) are used. There are 2 types of cables, namely, thick cables and thin cables . • Trunk Line Terminating resistors are attached at both ends of this cable.

  • Page 17: I/O Communications (I/O Slave Message)

    <Toc> <Ind> <2. Overview of DeviceNet > I/O Communications (I/O Slave Message) This is a communication function which allows the exchange of control information (I/O data) between the master and a slave in real time. This module supports the following two types of I/O communications protocols of DeviceNet.

  • Page 18: Message Communications (Explicit Peer-To-Peer Message)

    This is a function for setting and reading parameters, controlling and managing operations and exchanging information between nodes (1: 1) when necessary. In this module, it is possible to send a service request to other nodes (master and slaves) using the explicit messages defined in DeviceNet. FA-M3 Other masters Response DeviceNet...

  • Page 19: Preparations For Operation

    <Toc> <Ind> <3. Preparations for Operation > Preparations for Operation The preparations required before starting the operation are shown in Figure 3.1. <Sections referred to:> <Process flow> <Process Details> Section 2 Overview of DeviceNet Section 4.1 Function Specifications Design DeviceNet system Section 7 I/O Communications Section 8 Message Communications (1) Node address...
  • Page 20 <Toc> <Ind> <3. Preparations for Operation > SEE ALSO (1) For details on the interface of the CPU module and this module related to operation preparations, see also the following sections of this manual: • Section 6.1 I/O Relay • Section 6.2 I/O Data Register •...

  • Page 21: Module Specifications

    <Toc> <Ind> <4. Module Specifications > Module Specifications The specifications of this module are explained herein. Function Specifications The range of DeviceNet functions supported by this module is shown in the following table. Table 4.1 Supported DeviceNet Functions DeviceNet functions Device Communication adaptor Master/Scanner Explicit peer-to-peer message...
  • Page 22 <Toc> <Ind> <4. Module Specifications > The function specifications are shown in Table 4.2. Table 4.2 General Specifications Items Specifications Interface Conforms to DeviceNet. Data rate 125/250/500 kbps (selected by switch positions) Transmission medium 5 special cables (2 for signals, 1 SHIELD, 2 for power supply) Transmission distance Data rate Maximum length of trunk line...

  • Page 23: Operating Environment

    <Toc> <Ind> <4. Module Specifications > Operating Environment There are no restrictions on the CPU modules that can be used with this module. Model and Suffix Codes Model Suffix Code Style Code Option Code Description DeviceNet F3LD01 1 port T0403-1.EPS Components Front view Indicators...

  • Page 24: Display Panel

    "Node absent" means that no response has been received from the target node. During scanning, if an FA-M3 system failure occurs, scanning stops regardless of the value of the scan operation mode.

  • Page 25: Setting Switches

    <Toc> <Ind> <4. Module Specifications > Setting Switches An explanation about the switch settings of this module is given in this section. 4.6.1 Node Address Setting Switch Node addresses can be set using 2 decimal rotary switches which are on the front side of this module.

  • Page 26: Terminating Resistor Setting Switch

    <Toc> <Ind> <4. Module Specifications > 4.6.3 Terminating Resistor Setting Switch Using the knife switch on the front face of module, the built-in resistors can be used as terminating resistors of a trunk line. The built-in resistors are used only when connecting to the trunk line using daisy chain method when they are installed at both ends of a trunk line.

  • Page 27: External Dimensions

    <Toc> <Ind> <4. Module Specifications > External Dimensions Unit: mm 83.2 28.9 (*) When connecting the base module, the DeviceNet connector and cable leave enough space for the cable to bend properly. (See Section 5.1, “Attaching and Detaching a Module.”) F0405.EPS Figure 4.5 External Dimensions IM 34M6H28-01E...
  • Page 28 Blank Page...

  • Page 29: Attaching And Wiring

    <Toc> <Ind> <5. Attaching and Wiring > Attaching and Wiring The explanation about attaching/ detaching a module and wiring is given in this section. Attaching and Detaching a Module (1) Attaching Module Figure 5.1 shows how to attach this module to the base module. First hook the anchor slot at the bottom of the module to be attached onto the anchor pin on the bottom of the base module.
  • Page 30 <Toc> <Ind> <5. Attaching and Wiring > CAUTION Do not overtighten the module fixing screw. Recommended screws M4 12- to 14-mm long bind screws F0502.EPS Figure 5.2 Tightening Module Using Screws (4) The Depth for Attachment The depth between the rear surface of the base module and the front surface of this mod- ule should be 89.9 mm.

  • Page 31: External Wiring

    F0504.EPS Figure 5.4 Wiring to the Connector CAUTION • Switch OFF the power supply to the FA-M3 and network and then connect the com- munication cables. • Use crimp-on terminals for wiring. The following products can be used as crimp-on terminals of the cables.
  • Page 32 <Toc> <Ind> <5. Attaching and Wiring > • Attaching the connector to this module Insert the connector in the module as shown below. Proper torque for tightening the screw of the cable is 0.3 N.m. Screw slot Screw slot F0505.EPS Figure 5.5 Attaching Connector to This Module IM 34M6H28-01E 1st Edition : Feb.01,1999-00...

  • Page 33: Module Access

    Scan list ot set On if there is no registration in the device list. Same as above System failure On if a system failure occurs in the FA-M3. Same as above Scan status On during scanning; Off if not scanning.

  • Page 34: I/O Data Register

    <Toc> <Ind> <6. Module Access > I/O Data Register The list of I/O data registers is shown in Table 6.3. The I/O data registers that are not defined in Table 6.3 cannot be used. Table 6.3 I/O Data Register List Data Position Number Data Name Description...
  • Page 35 <Toc> <Ind> <6. Module Access > Control Flag A control flag is used to control the message communications and I/O communications of each node . The list is given in Table 6.5. Table 6.5 Control Flag Data Position Type*1 Content Explanation Default Value Number...

  • Page 36: Access From The Cpu Module

    <Toc> <Ind> <6. Module Access > Access from the CPU Module The method for accessing from the CPU module is explained in this section. See the sample programs in Sections 7 to 9 for more details. 6.3.1 Access Using Ladder Sequence When using the ladder sequence, use the following instructions to access from the CPU module.

  • Page 37: Access Using Basic

    <Toc> <Ind> <6. Module Access > 6.3.2 Access Using BASIC In BASIC, the following instructions are used to access from the CPU module. For the details on each instruction, see “BASIC CPU, BASIC Programming Tool M3” (IM34M6Q22- 01E). The following BASIC statements can be used for this module. If statements other than the following are used, the operation cannot be guaranteed.
  • Page 38 <Toc> <Ind> <6. Module Access > Input relays are allocated to 2 words in bits as shown below: 15 14 13 12 11 10 9 Not in use Not in use Not in use Not in use Not in use Not in use Not in use Not in use...
  • Page 39 <Toc> <Ind> <6. Module Access > Output relays are allocated to 2 words in bits as shown below: 15 14 13 12 11 10 9 Not in use Not in use Not in use Not in use Not in use Not in use Not in use Not in use...
  • Page 40 Blank Page...

  • Page 41: I/O Communications

    <Toc> <Ind> <7. I/O Communications > I/O Communications The operation of this module related to scanning and I/O communications is explained here. Scan List The scan list of this module is explained here. What is a scan list? Node identification information, the communication type, I/O data size and I/O data storage location are stored in the scan list for each node that communicates with this module.
  • Page 42 <Toc> <Ind> <7. I/O Communications > Register and Save The scan list and transmission time interval (see Section 7.5, “Transmission Time Interval”) are registered in the memory using the Register Device/Register Transmission Time Inter- val commands of the Tool commands (see Section 9.1.4 of this manual for details on the commands) using a Ladder/BASIC program in the CPU module.
  • Page 43 <Toc> <Ind> <7. I/O Communications > Allocation of I/O data storage location The storage location for I/O data is allocated in the I/O data buffer (see Section 6.2, “I/O Data Register,” in this Manual) according to the following rules. • Select the type (polling/bit strobe/none) of the I/O communications method. (When using message communications, select separately from I/O Communications).

  • Page 44: Module Operation

    <Toc> <Ind> <7. I/O Communications > Module Operation Normal Operation Perform the operations following the steps below. The operation of this module is shown in Figure 7.3. Start operation *1 If scanning is started without storing output data, system outputs '0' or the data at the time when the previous scanning is stopped.
  • Page 45 <Toc> <Ind> <7. I/O Communications > CPU module This module Operation from program Interface Action Store output data Request to start/stop scanning Scanning starts Request to start scan Scan status Status of other Confirm that scanning is in progress nodes Scan (I/O communications)
  • Page 46 <Toc> <Ind> <7. I/O Communications > Operation from Ladder/BASIC program of CPU module When you wish to read the data, turn on the "request to prohibit input data update flag" of the target node. Wait until the update status flag turns on. When it does, read the data and turn off the prohibit update flag.
  • Page 47 <Toc> <Ind> <7. I/O Communications > • Output Data Flags • Request to Prohibit Output Data Access flag in control flag of each node. • Output Data Access Status flag in status flag of each node. Operation from Ladder/BASIC program of CPU module When you wish to output new data, turn on the request to prohibit output data access flag of the target node.
  • Page 48 <Toc> <Ind> <7. I/O Communications > CPU module This module User program Interface I/O communication Concurrent I/O communications access to data of target node During request to accessing prohibit stopped? access? Request to prohibit output data access Request Control flag of the node to prohibit Request to access on...
  • Page 49 High order/ low order byte swapping of multiple byte data The encoding rules are different for data on the FA-M3 and DeviceNet. Hence in multiple- byte data it is necessary to swap the high order/low order bytes every 2 bytes.

  • Page 50: Transmission Time Intervals

    7-10 <Toc> <Ind> <7. I/O Communications > Transmission Time Intervals The transmission time interval is the period in which I/O communications are performed cyclically. The interval can be specified in the range of 0 to 5000 ms in units of 5 ms using the tool commands.

  • Page 51: I/O Response Time

    7-11 <Toc> <Ind> <7. I/O Communications > I/O Response Time The I/O response time is the time from the start of input to the slave, followed by ladder program processing, until output from the slave. From a ladder program, read the input data from this module using the special module read command READ.

  • Page 52: Start/Stop Operation And Status Management (Example Of Programming)

    7-12 <Toc> <Ind> <7. I/O Communications > Start/Stop Operation and Status Management (Example of Programming) This sample program shows how to start/stop an operation and how to manage the status. This sample program is based on the following conditions: • This module is installed in the 4th slot. •...
  • Page 53 7-13 <Toc> <Ind> <7. I/O Communications > Example of Ladder Programming (0001) ******** Initialization/Clear error ******** (0002) M0035 Request to clear error flag on 00001 Y00449 (0003) X00417 Confirm clear error has completed, then 00003 Y00449 turn OFF the Error Request flag. (0004) ******** Set scan operation mode ******** (0005)
  • Page 54 7-14 <Toc> <Ind> <7. I/O Communications > Example of BASIC Programming 10 ! ********************************************************** 20 ! * F3LD01-ON SAMPLE PROGRAM 30 ! * Start/Stop Operation and Status Management 40 ! ********************************************************** 50 ! ****Initial setup**** 60 DEFINT A-Z 70 DIM DLIST (3), DSTS (3) 80 LDSLOT = 4 90 ASSIGN LD01 = LDSLOT 100 !
  • Page 55 7-15 <Toc> <Ind> <7. I/O Communications > ENTER LDSLOT,25+I NOFORMAT;DSTS (I) 510 IF DLIST (I) <> DSTS (I) THEN LOOP1@ : ! Compare with scan list (Wait till it matches) 520 NEXT I 530 ! 540 ! 600 ! ****Valid data**** 610 OFF TIMER #1 : ! 20 second timer interrupt off 620 !

  • Page 56: I/O Data Access (Example Of Programming)

    7-16 <Toc> <Ind> <7. I/O Communications > I/O Data Access (Example of Programming) A programming example of I/O data access is shown below. In this program, the scan list is registered in the input and output data areas and normal communication is performed. Input data Data type Data position...
  • Page 57 7-17 <Toc> <Ind> <7. I/O Communications > Example of Ladder Programming (0017) ********Operation******** ********Read data******** (0018) I00001 Confirm that scan data is valid (I00001ON) 00039 READ D0001 and read input data. (0019) Data format conversion RROT D0001 (0020) RROT D0002 (0021) RROT D0003...
  • Page 58 7-18 <Toc> <Ind> <7. I/O Communications > Example of BASIC Programming This program is only a subroutine and is called from the program described in Section 7.5, “Start/Stop Operation and Status Management.” 1000 ! **** Read input data **** 1010 DREAD@ 1020 ENTER LDSLOT ,511 NOFORMAT ;IN1 : ! Read input data...

  • Page 59: Message Communications

    <Toc> <Ind> <8. Message Communications > Message Communications In this section, operation of message communications in this module and the interface is explained. Module Operation Operation during message communications in this module are explained here. Conditions for request to receive communication When the following conditions are satisfied, a request to receive communication is transmit- ted.
  • Page 60 <Toc> <Ind> <8. Message Communications > Message transmission Are both message communication request and completion flags turned off? Create a request message. (write to message communication transmission buffer.) Message communication request flag is turned on. Is the message communication completion flag on? Read the response message (read it from message communication...
  • Page 61 <Toc> <Ind> <8. Message Communications > CPU module This module Ladder/BASIC program Interface Operation of this module Write request Checks Message Other transmission request message communication nodes transmission buffer Transmission Transmission request Message communication execution flag Response Reception reception check Message communication completion flag...

  • Page 62: Interface

    • High order / low order byte swapping of multiple-byte data in service data The encoding rules are different for data on FA-M3 and DeviceNet. Hence, in multi-byte data, it is necessary to swap the byte high order/ low order byte every 2 bytes.

  • Page 63: Exit Codes

    <Toc> <Ind> <8. Message Communications > 8.2.2 Exit Codes The exit codes used for message communications are described herein. Error code Description Troubleshooting $0100 Target node may be absent or message communications are Connection for message not registered as communication type in scan list. Confirm the communications is unavailable.

  • Page 64: Sample Programs

    <Toc> <Ind> <8. Message Communications > Sample Programs Remote setting of operation (output cut-off/maintain) during abnormal communications of a discrete output device is given as a sample program of message communications. The target device supports the following services and attributes. •...
  • Page 65 <Toc> <Ind> <8. Message Communications > Example of Ladder Programming Only message communications are given in this program. Use it with the program given in Section 7.5, “Start/Stop Operation and Status Management.” I00200, Message communication start relay I00001, confirm communication status. (0034) (Refer to 7.5 “start/stop Operation ********Message communication********...
  • Page 66 <Toc> <Ind> <8. Message Communications > Example of BASIC Programming This program is only a subroutine and can be called from the program described in Section 7.5, “Start/Stop Operation and Status Management.” 2000 ! ****Message communication**** 2010 MESSEGE@ 2020 OUTPUT LDSLOT ,1501 NOFORMAT ;0 : ! Reserved 2030 OUTPUT LDSLOT ,1502 NOFORMAT ;1...

  • Page 67: Configuration

    <Toc> <Ind> <9. Configuration > Configuration Configuration includes the following: • Creating a scan list • Registering the transmission time interval • Storing in flash memory • Remote setting of other nodes (see Section 8.3, “Sample Programs,” in this manual) Configuration is performed by starting the Ladder/BASIC program for setting configuration on the CPU module which is defined when this module is used.

  • Page 68: Request Procedure

    <Toc> <Ind> <9. Configuration > 9.1.2 Request Procedure The request procedure for the tool commands is given below. Tool command execution Are both tool request to execute command flag and completion flag off? Creating the requested command (writing command to tool command buffer) Turns on tool request to execute command flag...
  • Page 69 <Toc> <Ind> <9. Configuration > CPU module This module Ladder/BASIC program Interface Action within this module Writing Tool request to execute Checks request requested command command flag Y Tool command execution Execute request completion flag X Command execution Completion check Completion Reading response Tool command buffer...

  • Page 70: Basic Command Formats

    <Toc> <Ind> <9. Configuration > 9.1.3 Basic Command Formats The format for a request/response (normal exit/error exit) is given below. • Request Data position no. Content Command number 401 to 449 Parameters T090103-1.EPS • Response (normal exit) Data position no. Content Command number 401 to 449...

  • Page 71: Details Of Commands

    <Toc> <Ind> <9. Configuration > 9.1.4 Details of Commands 1) Register device Registers device information for each node in the scan list. Nodes already registered cannot be registered again. Perform registration after deleting the devices and emptying the information in the scan list. •...
  • Page 72 <Toc> <Ind> <9. Configuration > System reserved Message communications I/O communications: Polling I/O communications : Bit strobe • The I/O data offset is the relative position from the beginning of every I/O data buffer. The unit for the I/O data offset/size is bytes. •...
  • Page 73 <Toc> <Ind> <9. Configuration > • Supplement • For information on communications type/offset, refer to the description of device registration. 3) Delete device Deletes the device information of a node from the scan list. • Request Data position no. Content Command = $05 Node number T090104-7.EPS...
  • Page 74 <Toc> <Ind> <9. Configuration > • Response (error exit) Data position no. Content $8071 Exit code T090104-12.EPS • Supplement • Writing is not possible during scanning. 5) Register transmission time interval Registers transmission time intervals. • Request Data position no. Content Command = $72 401-402...
  • Page 75 Product name of device T0902.EPS The revision starts from 1.1 ($0101) in the DeviceNet manual. The status codes given in the DeviceNet manual are used. Each device is given a unique number. FA-M3 LD01 Scanner Module IM 34M6H28-01E 1st Edition : Feb.01,1999-00...

  • Page 76: Exit Codes

    9-10 <Toc> <Ind> <9. Configuration > 9.1.5 Exit Codes The unique exit codes used in response to tool commands are given in Table 9.3. In the case of an incorrect response to a request, either confirm the command number/parameter or delete device/stop scanning before the request, according to the exit code. Table 9.3 Summary of Exit Codes Item...

  • Page 77: Configuration Procedure

    9-11 <Toc> <Ind> <9. Configuration > Configuration Procedure Configuration involves the following steps: Create a scan list and set the transmission time interval. Register the nodes with which communication is to be established (create a scan list) and set the transmission time interval using the tool command. Set the transmission time interval to either 0 msec.

  • Page 78: Sample Program

    9-12 <Toc> <Ind> <9. Configuration > Sample Program A sample program for configuration is given here. Configuration is carried out as follows: Configuration Clears the error flags of this module. Clear error Sets up transmission time interval. Setup transmission time interval Deletes all the registered devices from the scan list.
  • Page 79 9-13 <Toc> <Ind> <9. Configuration > • Clear Error The clear error command is carried out as follows: Clear error Request to clear error relay (Y 49) on Clear error completed confirmation relay(X 17) on Release request to clear error relay (X 49) off Release request to clear error confirmation relay (X...
  • Page 80 9-14 <Toc> <Ind> <9. Configuration > Setting transmission time 400 Command $72 403 Set Transmission Time Interval Write a request to command buffer Request to execute command relay (Y 58) on Execute command completed confirmation relay (X 26) on Read response Any errors? (command codes of request/response do not match)
  • Page 81 9-15 <Toc> <Ind> <9. Configuration > • Initalizing Scan list If there are registered devices, they are deleted from the scan list. Deletion from the scan list is carried out in the following manner. Initialising scan List Scan information not set relay (X 07) ON? Node address N=0 400 Command $05...
  • Page 82 9-16 <Toc> <Ind> <9. Configuration > • Registering Devices The procedure for device registration is given below. In the sample program, the following two devices are being registered. Item Data Data Node no Vendor ID 47 (Omron Corporation) 47 (Omron Corporation) Device type Product code 100 (Type DRT1-ID08)
  • Page 83 9-17 <Toc> <Ind> <9. Configuration > Registering devices Reads the data of registered slave one by one. Read device registration data Is data available? 400 Command $03 401 or greater - Registration Write a request to command buffer information Request to execute command relay (Y 58) on Execute command completed...
  • Page 84 9-18 <Toc> <Ind> <9. Configuration > • Storing in flash memory The steps for storing in flash memory are given below. Storing in flash memory 400 Command $71 Write a request to command buffer Request to execute command relay (Y 58) on Execute command completed confirmation relay (X...
  • Page 85 9-19 <Toc> <Ind> <9. Configuration > Sample Program Using Ladder Program A sample program using ladder programs is shown here. The sample program is created based on the following conditions. • This module is installed in slot 4. • The contents for device registration should be set in advance as given below. D0051 ~ information for first item D0101 ~...
  • Page 86 9-20 <Toc> <Ind> <9. Configuration > (0001) ********Initialisation ******** (0002) M0035 Clear data register. 00001 BSET D0001 2048 (0003) BSET D2049 1200 (0004) Clear Y relay of this module. Y00433 (0005) Clear relay. I00001 (0006) Specify the slot number of this module. D0007 (0007) ********Clear error********...
  • Page 87 9-21 <Toc> <Ind> <9. Configuration > (0014) X00426 Confirm that command execution has 00025 READ D0007 D0003 completed, and then read response. (0015) Request to execute command off. Y00458 (0016) I00002 (0017) ********Setting transmission time interval******** (0018) I00002 Clear tool command buffer. D0001 00032 WRITE...
  • Page 88 9-22 <Toc> <Ind> <9. Configuration > (0037) Proceed to the next process if node number is 64. D0002 D0001 (0038) I00002 (0039) ********Register Device ******** (0040) Clear D2 register (N-th item). D0001 00093 D0002 (0041) I00002 Specify data position of N-th item. D0005 D0002 (0042)
  • Page 89 9-23 <Toc> <Ind> <9. Configuration > (0060) ********END******** (0061) Normal exit D0001 00156 D0001 (0062) ********ERR******** (0063) I00006 Number for error handling 00158 D0001 D0011 (0064) D0001 Error (0065) Node address (during device deletion) D0002 D0012 Data number (during device registration) (0066) Command response ($8000+command number) D0003...
  • Page 90 9-24 <Toc> <Ind> <9. Configuration > (0079) ********Address 2******** (0080) M0035 Node address 00188 D0101 (0081) Vendor ID D0102 (0082) Device type D0103 (0083) Produce code D0104 (0084) Communication type D0108 (0085) Size of output data D0112 (0086) Offset of output data D0113 (0087) Size of input data...
  • Page 91 9-25 <Toc> <Ind> <9. Configuration > Sample BASIC Program An example of a BASIC program is given here. • This module is installed in slot 4. • The contents to be registered in the scan list are set using a DATA statement. •...
  • Page 92 9-26 <Toc> <Ind> <9. Configuration > 430 IF BIT (STS, 6) = 1 THEN GOTO SSET@ : ! Skip if scan list is not registered 440 FOR NA = 0 TO 63 450 GOSUB TBCLEAR@ 460 OUTPUT LDSLOT, 400 NOFORMAT; $05 : ! Command $05 470 OUTPUT LDSLOT, 401 NOFORMAT;...
  • Page 93 9-27 <Toc> <Ind> <9. Configuration > 960 RETURN 970 ! 1000 ! **** Subroutine – Execute command **** 1010 COMMAND@ 1020 CONTROL LDSLOT, 102; $0200, $FFFF : ! Request to Execute Command relay(Y 58) ON 1030 STS = 0 1040 WHILE BIT (STS, 9) = 0 : ! Clear Error Confirmation (Wait for Clear Error Confirmation 26) ON)
  • Page 94 Blank Page...

  • Page 95: Errors And Troubleshooting

    10-1 <Toc> <Ind> <10. Errors and Troubleshooting > 10. Errors and Troubleshooting Troubleshooting of this module is shown in the following flowcharts. Error Is RDY LED on? Go to 9.1 Flowchart Is MS LED blinking? when RDY LED is not on Go to 9.2 flowchart when MS LED is blinking Remedy the cause...

  • Page 96: Flowchart When Rdy Led Is Not On

    10-2 <Toc> <Ind> <10. Errors and Troubleshooting > 10.1 Flowchart When RDY LED Is Not ON RDY LED is not on Is the required voltage applied to the power Apply the correct voltage module? Replace the power module or Are the other modules RDY? the base module Is module properly Fitting is correct...

  • Page 97: Flowchart When Ms Led Is Flashing

    10-3 <Toc> <Ind> <10. Errors and Troubleshooting > 10.2 Flowchart When MS LED Is Flashing MS LED is flashing Is the setting of node address Correct the setting of the switch setting switch correct? (See 5.2.1, “Node Number Set Switch”) Is the setting of action mode Correct the setting of the switch setting switch correct?

  • Page 98: Flowchart When Ns Led Is Not On

    10-4 <Toc> <Ind> <10. Errors and Troubleshooting > 10.3 Flowchart When NS LED Is Not ON NS LED is not on Error Code = $E112 Is the power supply for communication correct? Reset the wiring and power Is the network power supply correctly set? supply of network Is the network power...

  • Page 99: Flowchart When Red Ns Led Is On

    10-5 <Toc> <Ind> <10. Errors and Troubleshooting > 10.4 Flowchart When Red NS LED Is ON Red NS LEd is on Error code= $E121 Is the node address duplicated? Correct the node address Error code= $E122 Are the data rates Make the transmission speeds of all nodes the same? of all nodes the same...

  • Page 100: Flowchart When Red Ns Led Is Flashing

    10-6 <Toc> <Ind> <10. Errors and Troubleshooting > 10.5 Flowchart When Red NS LED Is Flashing Red NS LED is flashing and ‘NS’ LED is not on after request to start scanning Error code= $E143 Is the scan list registered? Register scan list Error code= $E142...

  • Page 101: Error Codes

    10-7 <Toc> <Ind> <10. Errors and Troubleshooting > 10.6 Error Codes This module conveys error status not only by LED but also by input relay (X 01 to 16), error codes and other node error information. The error codes within the module information of the input/output data register and the node error information is of latched type.
  • Page 102 10-8 <Toc> <Ind> <10. Errors and Troubleshooting > SEE ALSO 1) See also Section 8.2.2, “Exit Codes,” in this manual for the exit codes of message communications. 2) See also Section 9.1.5, “Exit Codes,” in this manual for the exit codes of tool commands. IM 34M6H28-01E 1st Edition : Feb.01,1999-00...

  • Page 103: Devicenet Glossary

    11-1 <Toc> <Ind> <11. DeviceNet Glossary > 11. DeviceNet Glossary Bus-off: Indicates that the error rate in the network is very high. CAN: CAN is short for Controller Area Network. It is a communications protocol developed as a LAN for use in an automobile. DeviceNet employs CAN technology. I/O communications: This is a communications function which allows the exchange of control information (I/O data) between masters and slaves in real time.
  • Page 104 11-2 <Toc> <Ind> <11. DeviceNet Glossary > Master/Slave: A node can be either a master which collects and distributes data or a slave which outputs and inputs data according to the instructions received from the master. Message communications: These are functions for parameter setting/reading, operation control/management, informa- tion exchange, etc.

  • Page 105: Appendix 1. Details On Network Configuration

    Appx.1-1 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Appendix 1. Details on Network Configuration The network configuration of a DeviceNet is given below. For configuration components, refer to Section 2.1, “Network Configuration.” Network power supply Terminating resistor Terminating resistor Node Node Node...
  • Page 106 Appx.1-2 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Maximum cable length The maximum allowable node distance is called the maximum cable length. Maximum cable lengths according to the type of cable used are given in Table 1.1. Table 1.1 Maximum Cable Length Data rate Thick cable Thin cable...

  • Page 107: Appendix 1.2 Connection Methods

    Appx.1-3 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Table 1.2 Maximum Drop-line Length and Data Rate Transmission speed Length of drop line Maximum Cumulative 125 kbps 156 m 250 kbps 78 m 500 kbps 39 m TA0102.EPS Appendix 1.2 Connection Methods There are two types of connection methods for DeviceNet;...
  • Page 108 Appx.1-4 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Daisy Chain method Both trunk lines and drop lines can be connected using the daisy chain method. Drop or trunk line Drop or trunk line FAP0105.EPS Figure 1.5 Daisy Chain CAUTION The DeviceNet connector provided cannot be used for Daisy Chain type connection using thick cables as the cables are too thick.

  • Page 109: Appendix 1.3 Terminating Resistor

    Appx.1-5 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Appendix 1.3 Terminating Resistor Installing terminating resistors (121 ) at both ends of a trunk line reduces reflection and stabilizes communications. The terminating resistor should satisfy the following specifications. • 121 •...

  • Page 110: Appendix 1.4 Configuration Of Network Power Supply

    Appx.1-6 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Appendix 1.4 Configuration of Network Power Supply Two lines out of the five special cables are 24 V DC power supply lines used for communi- cation. It is necessary to provide power supply to the connectors of all nodes through these cables.
  • Page 111 Appx.1-7 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Special Purpose Power Supply Tap Special purpose power supply taps are configured as shown in Figure1.6. Always use it when there are more than two-power supply sources on a single network. Fuse CAN_H SHIELD...
  • Page 112 Appx.1-8 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Table 1.5 Maximum Current (amps) Available Based on Network Thin Cable Length Cable length (m) Max. current (amps) 3.00 3.00 3.00 2.06 1.57 1.26 1.06 0.91 0.80 0.71 0.64 TA0105.EPS Length of network (m) FAP0108.EPS Figure 1.8...
  • Page 113 Appx.1-9 <Toc> <Ind> <Appendix 1. Details on Network Configuration > • Configuration example 2 Network power supply Terminating resistor Terminating resistor Node Node Node Node Node 0.1A 0.1A 0.1A 0.05A 0.1A 100 m thick cable 150 m thick cable FAP0110.EPS Figure 1.10 Network Power Supply Configuration (Example 2) Total length of network on right side = 150 m...

  • Page 114: Appendix 1.5 Network Grounding

    Appx.1-10 <Toc> <Ind> <Appendix 1. Details on Network Configuration > Appendix 1.5 Network Grounding DeviceNet uses one-point grounding. As far as possible, ground it in the vicinity of the center of the network through the SHIELD terminal of the power supply tap. If the tap is not used, ground the GND cable directly.

  • Page 115: Appendix 2. Information On Third-Party Products

    Appx.2-1 <Toc> <Ind> <Appendix 2. Information on Third-party Products > Appendix 2. Information on Third-party Products Obtaining Information on Third-party Products DeviceNet is a multi-vendor network, and devices conforming to DeviceNet specifications are supplied by many vendors. A list of devices that conform to the DeviceNet specifications and the relevant contacts are given in the "Product Catalog (Catalog of devices conforming to DeviceNet)"...
  • Page 116 Blank Page...

  • Page 117: Revision History

    New publication Written by Product Marketing Section, PLC Center Industrial Automation Business Head Quarter. Yokogawa Electric Corporation Published by Yokogawa Electric Corporation 2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN Printed by Yokogawa Graphic Arts Co., Ltd. IM 34M6H28-01E 1st Edition : Feb.01,1999-00...
  • Page 118 Blank Page...
  • Page 119 FG clamps to the shields to secure and ground them. Peel off insulation and apply an FG clamp to the exposed shield. Shielded cable Screw the FG clamp to the metal plate of the panel enclosure for grounding. IM 34M06H28-01E-003 Jun. 2017 Yokogawa Electric Corporation...
  • Page 120  Appx. 1-2, “Maximum cable length” Replace with the following text. ■ Maximum cable length The maximum allowable node distance is called the maximum cable length. Maximum cable lengths according to the type of cable used are given in Table 1.1. To comply with the standard, the outdoor cable shall be less than 10 m, the indoor cable shall be less than 30 m.

Table of Contents