DeviceNet™ CM059 (SI-N1) OptionTechnical ManualFor Option: CM059 (SI-N1)Models: CIMR-G5*, CIMR-F7*, CIMR-G7*, CIMR-ACA*
10This page intentionally left blank.
11DeviceNet™ Simplified Start-up ProcedureThe following is a quick reference guide to install and configure the drive’s option. For more details, plea
126. Power up the drive and set the number of motor poles in parameter o1-03 to read and set the speed in motor RPMs.7. Set the drive’s run/stop and f
13Unpack and InspectPrior to unpacking, check the package label and verify that the product received matches the product ordered. Unpack the option an
14Installation and WiringThe following describes the installation and configuration of the option. For detailed information about the drive or the Dev
15Connect The Drive To The DeviceNet NetworkWire the DeviceNet communication cable to the terminal block according to the following procedures: Loos
16Baud Rate Setting SwitchMAC ID Setting SwitchTermination ResistorsTerminating resistors must be mounted on the first and last node in a DeviceNet ne
17Verify Option Operation Apply power to the drive. Verify that the diagnostic LEDs on the front of the option are in their correct state. Remove p
18Option Indication LEDsThe table below describes the function of DeviceNet specific LEDs. Table 11: DeviceNet LED FunctionLED NameDisplayOperation St
19Chapter 2Network ConfigurationThis chapter describes how to properly adjust the parameter settings of a DeviceNet slave in a network system.DeviceNe
2This page intentionally blank.
20DeviceNet ConfigurationDeviceNet configuration refers to properly setting the DeviceNet slave in a network system through its parameter settings. Th
21Install EDS FileInstall the drive’s EDS file by selecting EDS Wizard and follow the appropriate steps.In RSNetWorx, select EDS Wizard under Tools. B
22Once the proper EDS file is installed, the drive icon will appear along with the drive model number. Double-click on the drive icon to access the dr
23Set Application ParametersSelect the Parameters tab to access DeviceNet and drive parameters and set the parameters according to the application.The
24Enter appropriate PPA and PCA to use for polled communications. See Chapter 3 for a complete list of available PPA and PCA. Click OK or Apply to sav
25Add Drive to Scanlist and Specify SettingsSelect the Scanlist tab to show available devices for the scanlist.Add the drive to the scanlist by highli
26Select Polled communications and the correct amount of bytes for PCA (Rx) and PPA(Tx). Click OK.Select the Input tab and Unmap any data in the Discr
27Select the M File Memory.Click on the AutoMap button. The selected bytes of polled input data should appear in the scanlist. Click OK.
28Select the Output tab and Unmap any data in the Discrete Memory.Select the M File Memory. Click on the AutoMap button. The selected bytes of polled
29Select the Summary tab to make sure the correct number of I/O bytes are selected and are mapped.Save the changes and download the configuration to t
3Warnings and CautionsThis Section provides warnings and cautions pertinent to this product, that if not heeded, may result in personal injury, fatali
30Data Storage of Option and DriveThe drive with option stores data in four locations: Active RAM memory on the drive Inactive RAM memory on the dri
31Some Parameter Data registers may be written to while the drive is running. These parameters are called run operative parameters. For a list of thes
32Notes:
33Chapter 3Network CommunicationsThis chapter describes how to install and setup the DeviceNet OptionDeviceNet Polled I/O Messaging Communications...
34DeviceNet Polled I/O Messaging CommunicationsDeviceNet Communications between a Master (PLC or PC) and the drive (Slave) uses Polled I/O messaging,
35Basic Speed Control Input Instance 20 (14 Hex)This function is the basic I/O instance of Assembly Object Class (04 Hex) Attribute (03 Hex), which de
36Basic Speed Control Output Instance 70 (46 Hex)This function is the basic I/O instance of Assembly Object Class (04 Hex) Attribute (03 Hex), which d
37Extended Speed Control Input Instance 21 (15 Hex)This function is the basic I/O instance of Assembly Object Class (04 Hex) Attribute (03 Hex), which
38Extended Speed Control Output Instance 71 (47 Hex)This function is the basic I/O instance of Assembly Object Class (04 Hex) Attribute (03 Hex), whic
39Drive Modbus I/O Control Input Instance 100 (64 Hex)This I/O instance allows all drive parameters and monitors to be read/set. This instance is for
4IntroductionThis manual explains the specifications and handling of the Yaskawa DeviceNet™ CM059 (SI-N1) option. The Option connects the drive to a D
40Drive Modbus I/O Control Output Instance 150 (96 Hex)This I/O instance allows all drive parameters and monitors to be read/set. This instance is for
41Standard Drive Control Input Instance 101 (65 Hex)This I/O instance is for the input/output functions as well as the expansion I/O instance function
42*1 Drive products may provide additional inputs and outputs that are not supported through DeviceNet. For example, G7 has 5 digital outputs; however
43Standard Drive Control Output Instance 151 (97 Hex)This I/O instance is for the input/output functions as well as the expansion I/O instance functio
44*1 Drive products may provide additional inputs and outputs that are not supported through DeviceNet. For example, G7 has 5 digital outputs; however
45DeviceNet Explicit Messaging CommunicationsThe DeviceNet communications may also be accomplished by utilizing an “Explicit Message” to communicate w
46Identity Object Class (01 Hex):The Identity object stores DeviceNet product information. Table 23: Supported ServicesService Code (Hex) Service Name
47Table 25: Option Product Name and Product CodesCIMR-F7Uor CIMR-G7U Drive Capacity o2-04F7/SI-N1 G7/SI-N1Product Name Product Code Product Name Produ
48Message Router Object Class (02 Hex): The Message Router object has the function of routing DeviceNet communication information to the correct objec
49Assembly Object Class (04 Hex): The Assembly object is for the polled I/O message functions.Table 30: Supported ServiceService Code (Hex) Service Na
5OverviewThis manual describes the set-up and programming of the option. The option will allow communication between a DeviceNet Communication Network
50DeviceNet Connection Object Class (05 Hex): The DeviceNet Connection object has the function of keeping track of the DeviceNet communication connect
5102Polled Message Only01Instance statusThis instance status is displayed.00: It does not exist in the Network yet, and is being prepared.01: On-line
52Motor Data Object Class (28 Hex): The motor data object is for the information and functions related to the motor connected to the drive. Motor rate
53Table 37: Object ContentInstance (Hex)Attribute (Hex)NameDescriptionSetting RangeInitial Valu e(Hex)Read Write Size00 01Object Software RevisionCont
54AC/DC Drive Object Class (2A Hex): The AC/DC Drive Object is also dedicated to the information and function related to the drive operation. Frequenc
55Table 38: Object Content (continued)0115High Speed LimitDrive Frequency Reference upper limit value is set/read.*2 *3Min. :Unit: [r/min/2SS]where SS
56Drive Parameters Object Class 100 (64 Hex): This DeviceNet Object Class can read and write all of the same parameters and monitors available via dri
57Example 2:Setting the Accel Time 1 Parameter C1-01 Value by Explicit Messaging To set parameter C1-01 (Modbus register 0200 Hex) Acceleration Time 1
58DeviceNet Fault DiagnosticsDrive FaultsTable 44: DeviceNet Fault CodesDeviceNetFault Code No. (Hex)Operator Fault DisplayContent000021202130-GHSCDri
59Fault DiagnosticsThe following is a table of faults caused by the option that will be displayed on the Digital Operator, their causes, and possible
6The list below presents a summary of the Physical/Media specific characteristics of DeviceNet: Trunkline-dropline configuration Support for up to 6
60DeviceNet Communication LED Faults and OperationTable 46: DeviceNet Communication LED Faults and OperationLED DisplayContent Cause SolutionPWR MS NS
61Explicit Message Communication ErrorIf a requested message has an error response from the master when performing Explicit message communication, the
62I/O Message Communication Modbus I/O Instance ErrorsTable 48: Modbus I/O Instance Errors and Their CausesError CodeContent Causes01 Hex Function cod
63Appendix AProduct SpecificationsThis chapter describes the product specifications of a DeviceNet network system.DeviceNet Product Specification ...
64Product Specifications Item SpecificationsI/O Message 4 types of I/O instance are supported:1) Basic I/O instance (Input 4 bytes, output 4 bytes)2)
65Appendix BCable SpecificationsThis chapter describes the cable specifications for a DeviceNet network system.DeviceNet Cable Specifications...
66Cable SpecificationsThick CableThis cable consists of two shielded pairs twisted on a common axis with a drain wire in the center covered with an ov
67DeviceNet Network TopologyThe DeviceNet media has a linear bus topology. Terminating resistors are required on each end of the trunkline. Droplines
68Dropline length is the longest cable distance measured from the tap on the trunkline to each of the transceivers of the nodes on the dropline. The t
69This page intentionally blank.
7Table of ContentsWarnings and Cautions...2Introduction ...
YASKAWA ELECTRIC AMERICA, INC.Chicago-Corporate Headquarters 2121 Norman Drive South, Waukegan, IL 60085, U.S.A.Phone: (800) YASKAWA (800-927-5292)
8Chapter 3- Network Communications......33DeviceNet Polled I/O Messaging Communicati
9Chapter 1InstallationThis chapter describes how to install and setup the DeviceNet OptionDeviceNet™ Simplified Start-up Procedure ......
Commentaires sur ces manuels