. Driver Download GE Fanuc Automation Series 90-30/70 SNP-X driver Please acknowledge the following terms of use before you use our download service. Download of any file signifies your agreement to the terms of use. Terms of Use. Schneider Electric Japan Holdings Ltd. ('SEJH') shall retain all intellectual property rights to the files that SEJH provides for this service. Who, uses or plans to use SEJH's products, may download and use any file.
We have the Manuals needed to support your GE Fanuc Series 90-30 PLC. Find just the right tool to answer your Series 90-30 question.
Reproduction, disclosure, re-publication, assignment, lease, decompilation, modification, falsification or reuse of any file that SEJH provides for this service shall be prohibited. However, for manuals, samples, BMP images and CAD files, you may reprint, duplicate, quote a part of the content or the whole on your company's specification sheets, or instruction manuals for built-in products.
Also you may change the layout of the content. This download service is provided through the Internet.
Please acknowledge that SEJH provides no guarantee of the condition at the time of provision, the availability of access and the condition of use concerning this service before you use this service. Please use this service at your own risk. If any additional conditions such as service usage conditions are attached to the downloaded files, please comply with such conditions as well. Notices:. Files are subject to deletion, or modification of the contents or specifications without notice.
Please confirm that the downloading file size completely accords with the download file size shown. If the file sizes do not match, delete the file without decompressing and then download the same file once again. Download Note: → Title GE Fanuc Automation Series 90-30/70 SNP-X Driver Version Ver. 1.11.02 File Name File Size 605KB Applicable Software GP-Pro EX Ver. 1.10.000 or later Pro-Server EX Ver.
1.10.000 or later To check your version, go to the ” Help ” menu → ” Version Info ”. Related Devices. Series 90-30. Series 90-70 Related Units. AGP3000 Series.
IPC Series for WinGP (GP-Pro EX Ver. 2.00.000 or later) Manual For details, please read the following PDF: ( 495KB ) Updated Contents Ver. 1.11.02 (Apr. 10, 2009) The following issue was corrected:. When writing specific data, an illegal communication response error could be reported incorrectly. Installation (This file is self-extracting.). Please confirm that the supported software is installed in your computer.
Prior to installing the driver, close all your personal computer applications, including any resident programs such as virus detection program, etc. Click on the above file name to download the data to desired folder.
After the download to your PC is finished, double-click on the file's icon to start the installer program. After the installer starts, follow the instructions given on each screen.
After installation, execute GP-Pro EX. After installation, click on the Device/PLC area's GE Fanuc Automation selection and select Series 90-30/70 SNP-X. When using the driver, be sure to refer to the Device Connection Manual PDF (Shown above).
Also, for general information regarding Device connection and documentation conventions please refer to your own Device/PLC Connection Manual. Update History: Ver. 1.11.02 (Apr. 10, 2009)The following issue was corrected:. When writing specific data, an illegal communication response error could be reported incorrectly. Last Updated: Apr. 10, 2009 Posted: Nov 22, 2006.
. GE Fanuc Automation Programmable Control Products Series 90®-30 Programmable Controller DeviceNet™ Modules GFK-2196 November 2002. Features may be described herein which are not present in all hardware and software systems. GE Fanuc Automation assumes no obligation of notice to holders of this document with respect to changes subsequently made. Operation of a Series 90-30 Slave (Server) DeviceNet Module.5-4 Fault Table Entries for a Series 90-30 DeviceNet Module.5-5 PLC Status References for a Series 90-30 DeviceNet Module. 5-6 Device Status Bits for the Series 90-30 DeviceNet Master Module.
5-7 Chapter 6 Programmed Communications.6-1 COMMREQs for the Series 90-30 DeviceNet Modules. Command Code 9: Reading Identification, Status, and Error Information.
6-8 Command Code 4: Getting the Status of a Network Device. 6-12 Command Code 5: Getting Status Information of a Series 90-30 DeviceNet Slave Module or the Server Function of a Master Module.6-14 Command Code 6: Getting Input Status from a Device. LED indications. Chapter 3: PLC Configuration for the DeviceNet Master, explains how to add a DeviceNet Master Module to the configuration of the Series 90-30 PLC.
It also explains how to configure communications connections, the module, and the DeviceNet network. Both of these modules can be installed in any rack in the Series 90-30 PLC.
Each module counts as a single node on the DeviceNet network. However, the server function of each module is easily configured for up to two DeviceNet I/O Messaging connections and for Explicit Messaging. Series 90-30 DeviceNet Master Module The Series 90-30 DeviceNet Master Module (IC693DNM200) allows a Series 90-30 CPU to send and receive data over a DeviceNet network.
It can act as master for up to 63 slaves on the DeviceNet network. It can also be configured to simultaneously function as a slave to another master on the bus. Requires CIMPLICITY Machine Edition Logic Developer PLC version 3.0 with Service Pack for DeviceNet, or later. Not compatible with the VersaPro™, Control, or Logicmaster™ programming software.
The Series 90-30 Hand-Held Programmer (IC693PRG300) cannot be used to configure this module. Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002. Series 90-30 DeviceNet Slave Module The Series 90-30 DeviceNet Slave Module (IC693DNS201) interfaces a Series 90-30 PLC to a DeviceNet bus that is controlled by another master device. DeviceNet Slave Module Module NET POWER Status MOD STATUS LEDs NET STATUS.
Requires CIMPLICITY Machine Edition Logic Developer PLC version 3.0 with Service Pack for DeviceNet, or later. Not compatible with the VersaPro™, Control, or Logicmaster™ programming software. The Series 90-30 Hand-Held Programmer (IC693PRG300) cannot be used to configure this module. Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002. The DeviceNet network has a linear structure.
There is a main trunk line with drop lines routed to the networked devices. Power and signals are carried on the same network cable.
A Series 90-30 DeviceNet module can be connected directly to the trunk cable or installed as an individual drop or as part of a daisy-chain drop. There are four basic types of I/O messages: Polled, Strobed, Cyclic, and Change-of-State (COS).
The Series 90-30 DeviceNet Master Module can be configured for up to two different types of I/O messaging connections to each slave (for example, one Cyclic I/O messaging connection and one Change-of-State I/O messaging connection). Conformance to Standards Before installing GE Fanuc products in situations where compliance to standards or directives from the Federal Communications Commission, the Canadian Department of Communications, or the European Union is necessary please refer to GE Fanuc’s Installation Requirements for Conformance to Standards, GFK-1179. Power Supplies When using a Series 90-30 DeviceNet module, there are two separate power supplies to consider: the PLC power supply and the DeviceNet network power supply. PLC Power A Series 90-30 DeviceNet module consumes 450mA at 5VDC (typical) from the PLC backplane. DeviceNet Cable for the Series 90-30 Modules Series 90-30 DeviceNet modules can be used with the either DeviceNet thick cable or thin cable.
Thick cable permits greater cable lengths and higher current levels. Generally, thick cable is used for the trunk cable. Thin cable is normally used for shorter distances and is suitable for drop cables and for installations where more cable flexibility is needed. Bus Length The maximum length of the trunk cable and drops both depend on the cable type and data rate.
Individual drops may not exceed 6 meters and are limited to one network node per drop. However, the node may have multiple ports. Data Rates 125kbps 250kbps. Drop Lines Node Node Node Wiring to the Series 90-30 DeviceNet Master module depends on its location on the network: If the Series 90-30 DeviceNet If the module is installed at the If the module is installed module is located at either end. CANH SHIELD CANL Ground Wire Size The minimum size ground conductor for the DeviceNet screw-clamp terminals on a Series 90-30 DeviceNet module is a 2.5mm (14 AWG) wire. For other network devices, larger wire diameters may be necessary.
Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002. Installing the DeviceNet Module in the PLC Rack A Series 90-30 DeviceNet module can be installed in the main (CPU) rack in slot 2 or higher, or in slot 1 or higher of any expansion rack. Turn off power to the rack. Module LEDs The module's three LEDs show its operating and communications status: NET POWER MOD STATUS NET STATUS Network Power LED Indicates There is no power detected on the network. Green Power detected on the network. Module Status LED Indicates There is no backplane power to the module. When it finishes successfully storing the new firmware, the module automatically resets and attempts to start the new firmware.
If the firmware transfer was not successful, the greeting screen reappears. Retry the transfer. On success, disconnect the serial cable and cycle power to the Series 90-30 PLC rack. GFK-2196 Chapter 2 Installation. PLC Configuration for the DeviceNet Master Chapter This chapter explains how to add a Series 90-30 DeviceNet Master Module (IC693DNM200) to the configuration of the Series 90-30 PLC.
It also explains how to configure communications connections between a Series 90-30 DeviceNet Master Module and the DeviceNet network. Configuration Steps There are three basic steps to configuring a Series 90-30 DeviceNet Master Module: Adding the module to the PLC rack and configuring its operating parameters. Telling the DeviceNet Master about slaves by adding the network slaves to the Master and configuring their network settings. Adding a DeviceNet Master Module to the PLC Configuration First, add the Series 90-30 DeviceNet Master Module (IC693DNM200) to the PLC rack configuration. The module is compatible with any Series 90-30 CPU except IC693CPU321 or IC693CPU340. It requires release 8.0 CPU firmware as a minimum.
Release 10.6 or later is recommended, if available for your particular CPU. Configuring the Parameters of a DeviceNet Master Module The DeviceNet Master Module is added to the PLC configuration in the Navigator window, and the module’s Parameter Editor window appears in the InfoViewer window space. Parameters of a DeviceNet Master Module Settings tab Mac ID The Mac ID (medium access control identification) of the master on the DeviceNet network. Settings tab Fault State When the DeviceNet Master Module detects a PLC fault (because the PLC has not Transmission requested its regular I/O update from the module), the module can either send idle packets or set data to zero. The default is to send idle packets. Inputs on Loss If the DeviceNet Master loses communications with a slave, it can hold the module's input of Slave. Data Areas Tab This tab shows the PLC program references assigned to the DeviceNet Master Module's Network Settings when it is used as a slave: This TAB is optional and should only be used when the DeviceNet Master Module is also a slave to another Devicenet master device.
Note: Do not enter values on this tab if the DeviceNet Master Module is not also used as a slave. Configuration Parameter screen; they can be set in either place. The rest of the tabs are only used if the Series 90-30 DeviceNet Master Module will operate as a server (slave) to another master on the network. If the DeviceNet Master is not a slave to another DeviceNet master these three tabs should be left blank. Select the slave type from the list that appears. Click OK to select the slave.
For example, to add a Series 90-30 DeviceNet Slave Module (IC693DNS201) as a slave on the network, you would select: You can also drag and drop a device from the Toolchest to the DeviceNet master. Open the Toolchest by clicking the Toolchest button on the Tools toolbar. Configuring Network Settings for Slaves Added to the Master The Network Settings include MAC IDs, baud rates, and the messaging connections between devices on the network. Assigning the MAC IDs and Baud Rate Be sure the MAC IDs entered for slaves in the Machine Edition configuration match the MAC IDs set up for the devices themselves. I/O Messaging communications occur automatically during system operation. Each Series 90-30 device in a DeviceNet system can be set up for up to two different I/O Messaging connections. Each connection can be disabled (the default), or set up for Polled, Strobed, Change-of-State, or Cyclic operation.
To configure polling for slave connection 1 or connection 2, select Polled on the Slave Properties menu. Polled I/O Messaging Screen for a DeviceNet Slave in the Series 90-30 DeviceNet Master configuration For input resources, specify the number of data bytes the slave will send to the master. Configuring a Strobed I/O Messaging Connection In Strobed I/O mode, the master produces a single Strobe request message that is consumed by all devices with a connection configured for strobing, requesting their current status. This occurs at the rate selected using the Scan Interval parameter of the DeviceNet Master Module. Each strobed device then responds with its input data.
Configuring a Change-of-State (COS) I/O Messaging Connection A connection configured for Change-of-State (COS) I/O Messaging is activated only when the device sends a message to the master, reporting a change of status. The master then sends an output message to the device and the device responds with its input data.
Device Produces Change of State Message Master Sends Outputs, Device Replies DeviceNet. If Acknowledge Suppress flag is selected, the DeviceNet master does not wait for an acknowledge message from the device. For Update, specify the interval in milliseconds at which the Series 90-30 DeviceNet master will update data for a network device. To select the fastest update rate possible, enter zero. If Explicit Messaging should be enabled, click on Enable Explicit Connection on the Explicit Messages tab. In addition, for a Series 90-30 DeviceNet Slave Module, or Series 90-30 DeviceNet Master module operating as a slave, specify the message request and message response size.
Make sure the size specified is large enough. I/O Messaging communications occur automatically during system operation. Each Series 90-30 device in a DeviceNet system can be set up for up to two different I/O Messaging connections. Each connection can be disabled (the default), or set up for Polled, Strobed, Change-of-State, or Cyclic operation. To configure polling for slave connection 1 or connection 2, select Polled on the Slave Properties menu.
Polled I/O Messaging Screen for a Series 90-30 DeviceNet Master Module For input resources, specify the number of data bytes the slave will send to the master. To configure Strobed I/O Messaging for a slave connection, select Strobed on the Slave Properties menu. Strobed I/O Messaging Screen for a Series 90-30 DeviceNet Master Module For input resources, specify the number of data bytes the device will send to the master. To configure Change-of-State I/O Messaging for a connection, select COS on the slave properties menu. COS I/O Messaging Screen for a Series 90-30 DeviceNet Master Module For input resources, specify the number of data bytes the device will send to the master. If Acknowledge Suppress flag is selected, the DeviceNet master does not wait for an acknowledge message from the device. For Update, specify the interval in milliseconds at which the Series 90-30 DeviceNet master will update data for a network device.
To select the fastest update rate possible, enter zero. If Explicit Messaging should be enabled, click on Enable Explicit Connection on the Explicit Messages tab. In addition, for a Series 90-30 DeviceNet Slave Module, or Series 90-30 DeviceNet Master module operating as a slave, specify the message request and message response size. Make sure the size specified is large enough. PLC Configuration for the DeviceNet Slave Chapter This chapter explains how to add a Series 90-30 DeviceNet Slave Module (IC693DNS201) to the configuration of the Series 90-30 PLC. It also explains how to configure communications connections between a Series 90-30 DeviceNet Slave Module and the DeviceNet network. Configuring the module as a slave on the network of a master module.
Instructions for configuring the network of a Series 90-30 DeviceNet Master Module are given in chapter 3. Instructions for configuring other master types are not described in this manual. Adding a DeviceNet Slave Module to the PLC Configuration First, add the Series 90-30 DeviceNet Slave Module (IC693DNS201) to the PLC rack configuration.
The IC693DNS201 is compatible with any Series 90-30 CPU except IC693CPU321 and IC693CPU340. It requires release 8.0 CPU firmware as a minimum. Release 10.6 or later is recommended, if available for your particular CPU. Configuring the Parameters of a DeviceNet Slave Module After selecting the module, its Parameter Editor window appears in the InfoViewer window space.
Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196. Parameters of a DeviceNet Slave Module Settings tab Mac ID The Mac ID (medium access control identification) of the slave on the DeviceNet network. Valid range: 0 - 63. To set this parameter in the DeviceNet Slave Properties dialog box, go to the Navigator, right-click the DeviceNet slave and choose Network Settings.
Data Areas Tabs These tabs show the PLC program references assigned to the selected module: These reference assignments can be edited, or left at their defaults. Note that the input data area tab shows master inputs, which are module outputs. The output data area tab shows master outputs, which are module inputs. Configuring the Network Settings of a DeviceNet Slave Module To configure the Network Settings for a DeviceNet Slave Module, right-click the DeviceNet Slave in the PLC configuration, and choose Network Settings. The Network Settings dialog box appears. The General tab allows setting a name and description for the module. On this tab, you can also select the MACID and Baud Rate.
Configuring I/O Messaging Connections I/O Messaging is the term used for the routine and automatic exchange of data between the master and slaves in a DeviceNet system. Each configured I/O Message defines a dedicated communication path between a producing device and one or more consuming devices. Once these connections have been established, I/O Messaging communications occur automatically during system operation. To configure polling for slave connection 1 or connection 2, select Polled on the Slave Properties menu.
Polled I/O Messaging Screen for a Series 90-30 DeviceNet Slave Module For input resources, specify the number of data bytes the DeviceNet Slave Module will send to the master. To configure Strobed I/O Messaging for a connection, select Strobed on the Slave Properties menu.
Strobed I/O Messaging Screen for a Series 90-30 DeviceNet Slave Module For input resources, specify the number of data bytes the module will send to the master. To configure Change-of-State I/O Messaging for a connection, select COS on the Connection tab menu. COS I/O Messaging Screen for a Series 90-30 DeviceNet Slave Module For input resources, specify the number of data bytes the module will send to the master. To configure Cyclic I/O Messaging for a connection, select Cyclic on the Slave Properties menu. Cyclic I/O Messaging Screen for a Series 90-30 DeviceNet Slave Module For input resources, specify the number of data bytes the module will send to the master. Also specify the message request and message response size. Make sure the size specified is large enough.
The Series 90-30 DeviceNet module implements Explicit Messaging through the use of COMMREQ instructions in the application program. These COMMREQ messages are described in chapter 6, 'Programmed Communications'. Module Operation Chapter This chapter describes how the Series 90-30 DeviceNet Master Module and the Series 90-30 DeviceNet Slave Module function in a Series 90-30 PLC system. Operation of the Series 90-30 DeviceNet Master Module Operation while the PLC is in Stop Mode. Operation of a Series 90-30 DeviceNet Master Module A Series 90-30 DeviceNet Master Module automatically exchanges data with devices on the network once connections are established. However, the content of the data it sends to network devices depends on the operating mode of the PLC. Fatal Errors If a Series 90-30 DeviceNet Module has a fatal error, it takes the following actions if possible: It sets its Module Status LED to solid RED and its Network Status LED to OFF.
It informs the PLC CPU. Operation of a Series 90-30 Slave (Server) DeviceNet Module A Series 90-30 DeviceNet Slave Module operates as a server (slave) to a master device on a DeviceNet network. The Series 90-30 DeviceNet Master Module can be also be configured for server operation, and can perform the same functions as the Series 90-30 DeviceNet Slave Module. For details on the effects of different types of faults on PLC behavior, refer to the Series 90-30 System Manual, GFK-1411 or the Series 90-30 Reference Manual, GFK-0467.
PLC Status References for a Series 90-30 DeviceNet Module A Series 90-30 DeviceNet module automatically reports the three words of status information shown below to its configured PLC references (Network Status/Firmware ID). The application logic can monitor these references and take appropriate actions in response to specific changes. The example status bits shown below represent a network with 25 devices assigned MAC IDs 0 to 24.
The Series 90-30 DeviceNet Master Module is assigned MAC ID #0 and the device with MAC ID #8 is faulted, so there are 0s in status bits%I00001,%I00009, and%I00026 through%I00064. DeviceNet serial number. CAN Network status. Getting the Status of a Network Slave (for Series 90-30 DeviceNet Master Module only) whether it is included in the master's list of configured devices whether it is being scanned its configuration error status.
COMMREQs for the Series 90-30 DeviceNet Modules The Series 90-30 DeviceNet Master Module and Slave Module can use the COMMREQs listed below. COMMREQs are described in detail on the following pages. Command Feature Command Description Support Code Name Master Send Device. The CPU sends the COMMREQ to an intelligent module in the PLC system, in this case, a Series 90-30 DeviceNet Master or Slave module. The module receives the command and performs the requested function. Some COMMREQs for the DeviceNet Master or Slave are used to read or write module data.
Command Block is%R00100. The length of the Command Block depends on which command is being executed.
Command Blocks for all the Series 90-30 DeviceNet module commands are shown in this chapter. COMMREQ Programming Requirements and Recommendations Data must be placed in the Command Block before executing the COMMREQ instruction. For some commands, additional data areas must also be set up. Since the normal PLC sweep order is from top to bottom, this should be done ahead of the rung that contains the COMMREQ.
If you use MOVE instructions to load values into Command Block registers, use a Word-type MOVE to load a hexadecimal number, and an Integer-type MOVE to load a decimal number. Corrective Actions for COMMREQ Errors The type of corrective action to take in response to a COMMREQ error depends upon the application. If an error occurs during the startup or debugging stage of ladder development, you should check the COMMREQ parameters.
The COMMREQ parameters should also be checked if an error occurs right after a program is modified. The COMMREQ Status Block for Series 90-30 DeviceNet Modules The COMMREQ Status Block is four words long. Each status word is data type UINT.
The status block can be located in any of the supported PLC memory areas. The PLC application must set the Status Block contents to 0 before each COMMREQ. Command Code 9: Reading Identification, Status, and Error Information To read the following information from a Series 90-30 DeviceNet Master or Slave module, use COMMREQ #9, Read Module Header: Module Type, Module ID, Module revision. CAN Kernel identification and revision. 0 = 16K, 1 = 32K, 2 = 64K, 3=128K Reserved Kernel identification. 0x0001 = CAN 2.0A kernel Kernel revision Module ID, 0x0017 (Series 90-30 DeviceNet module) Module revision in binary coded decimal (BCD), 4 hex digits XX.XX (i.e.
Rev 1.0 = 0x0100, rev 1.10 = 0x0110) 9,10. Runtime Error Codes in the Module Header After a runtime error word 2 of the Read module header, reply data = 'DN' (0x444E), the Main Error Code word 25 and Additional Code word 33 fields of the reply data describe the runtime error. Fatal Error Codes in the Module Header If the module is capable of executing and reporting an error after a fatal error, the Module Type field of the Module Header data contains the value “ER” (0x4552). All DeviceNet network activity, if active, stops. Proper DeviceNet shutdown messages are not guaranteed. (invalid vendor id, device type, product code, I/O connections, etc) its connection 1 and connection 2 input states This function is internal to the Series 90-30 PLC; it does not generate a DeviceNet network message.
Get Detailed Device Status, Example COMMREQ This example COMMREQ does the following: Gets the Device Status of the slave with MAC ID #4 from the DeviceNet Master Module. Get Detailed Device Status, Reply Data Format Upon receiving COMMREQ 4 from the PLC CPU, the Series 90-30 DeviceNet Master Module generates a reply containing the status data it currently has stored for the specified MAC ID. Word # Description Command number that this data block is replying to. DeviceNet explicit message (previously commanded by a Send Server Response COMMREQ). How the module's I/O messaging settings are configured. This function is internal to the Series 90-30 PLC; it does not generate a DeviceNet network message.
Series 90-30 PLC. Explicit message, for transmission on the network. Bits 1 - 7: Reserved Bits showing the configured features of the module. For this example, the Series 90-30 high DeviceNet module slave server is set up for explicit messaging and polled I/O operation. Command Code 6: Getting Input Status from a Device To read the information normally mapped to a Series 90-30 DeviceNet Module's 3 status words, plus all the information normally mapped to the DeviceNet Master Module's 64 device status bits, use COMMREQ #6, Get Status Information.
COMMREQ #6 is alternate way to access this information. Get Status Information, Reply Data Format Word # Description Command code that this data block is replying to. (6) 2 - 5 Device Status. Each bit corresponds to an individual device MAC ID. The state of that bit indicates the device's status: 0 = Device is not active (not configured, faulted, etc) 1 = Device is active, being scanned For the master's own MAC ID, the status bit is always 0. The addressed device must be configured for an explicit message connection in the Series 90-30 configuration of the DeviceNet Master Module and sufficient buffer memory must be configured to contain the largest message produced by the COMMREQ or the largest reply produced by the device.
The difference between Send Device Explicit and Send Device Explicit Extended is how they store the data that will be sent in PLC memory. For Send Device Explicit, the data to be sent is located in the same memory area as the COMMREQ command block. Series 90-30 PLC COMMREQ Command Block. Word # (Hex) Description (000C) 00012 Length of command: Length of the command block for this COMMREQ. For the Send Device Explicit (command 1) the command length is 10 words plus the number of words of Service Data. The COMMREQ header (words 1–6) is not counted in the command length. Note: Service Data is in bytes, divide by 2 and round up for words.
This command is only valid to a Master Module. This example COMMREQ does the following: Sends an explicit message to Mac ID 4 (a GE Fanuc S2K DeviceNet Motion Controller) Returns the COMMREQ Status Words to%R10-%R13 Sets (writes) an array of data (32 DINT) variables to the S2K integer memory (VI registers). Send Device Explicit Extended, Data Block Format The following data must be placed in the PLC memory location specifed in the command by the data memory offset. One use of the data byte offset (see below) would be to “point “ to a start location within a large array of data in the PLC memory. Send Device Explicit (& Extended), Reply Data Format The Series 90-30 DeviceNet Master Module replies to a Send Device Explicit or Send Device Explicit Extended COMMREQ.
The reply data has the following format: Word # Description Command code that this data block is replying to. (1 for Send Device Explicit, or 7 for Send Device Explicit Extended) Status of the explicit message. For example, the PLC Data Object allows a device like a personal computer or another PLC to read or write an array of PLC data memory where the Series 90-30 DeviceNet module is installed. This could be used to send a recipe to PLC%R memory or to retrieve an array of status data on demand. DeviceNet module to reply to “custom” explicit messages. One use of custom-explicit messaging is to allow the Series 90-30 DeviceNet module to respond to existing client messages, or to emulate the response of a particular DeviceNet device template. For example, the Series 90-30 DeviceNet module could emulate the response expected from a DeviceNet motor control center or position controller device.
SERRA bit / Network Command Reply A Series 90-30 DeviceNet module can receive multiple explicit request messages from a network master before the first response message is generated. Command code 2: Receive Server Explicit, Example COMMREQ Format This example Receive Server Explicit COMMREQ specifies the command number (2), and sets up in the PLC CPU a memory type, starting address and length for the reply data that will be returned by the module.
Receive Server Explicit, Reply Data Format When it receives a Receive Server Explicit COMMREQ, the DeviceNet module returns a reply containing either the next explicit request in its internal memory, or an indication that there is no explicit request in the queue to process. The reply contains information about the device that sent the explicit request, and a description of the service requested.
After retrieving a DeviceNet explicit message from a Series 90-30 DeviceNet Slave Module or Series 90-30 Master Module in slave mode, the application program can respond to the network master using COMMREQ #3, Send Server Explicit. If the content of the response is more than 238 explicit data bytes, use COMMREQ #8, Send Server Explicit Extended instead. Command Code 3: Send Server Explicit, COMMREQ Description For the Send Server Explicit COMMREQ there is no reply to the command.
Ge 90 30 Plc Obsolete
Care should be taken to verify the success of the command via the COMMREQ status word. You must have the appropriate connection ID from command 2 prior to executing this command. Command Code 8: Send Server Explicit Extended, COMMREQ Word # Description Command Length: Always 4 words for command 8 Always 0 (no-wait mode request) Status segment select: Memory type of COMMREQ status word (%R for this example).
(8 = R, 10 = AI, 12 = AQ, 16 = I, 18 = Q, 20 = T, 22 = M) Status memory offset: COMMREQ status word address minus 1 (%R10 for this example) Reserved Reserved. DeviceNet Objects for Series 90-30 Modules Chapter This chapter describes the DeviceNet Objects that are defined for the Series 90-30 DeviceNet Master Module, IC693DNM200 and the Series 90-30 DeviceNet Slave Module, IC693DNS201. These modules use the following types of Objects in DeviceNet information exchanges. Identity Object Object Class 0x01 The Identity Object contains the module's identifying information.
There is only one instance of this object. Class Attributes Description Limits Revision Max Instance Max ID of class attributes Max ID of instance attributes Supported Not supported Class Services Service Param. Not supported Instance Attributes Description Limits Object List Maximum connections supported Number of active connections Active connections list Supported Not supported Instance Services Service Param. Options GetAttributesAll GetAttributeSingle Supported Not supported GFK-2196 Chapter 7 DeviceNet Objects for Series 90-30 Modules. DeviceNet Object Object Class 0x03 The DeviceNet Object contains the parameters for DeviceNet operations.
There is only 1 instance of this object. Class Attributes Description Limits Revision Supported Not supported Class Services Service Param.
Options GetAttributeSingle Supported Not supported Instance Attributes Description Limits MAC ID. Number of Members in List Member List Data Supported Not supported. Only for non-Established output connections Instance Services Service Param. Options GetAttributeSingle SetAttributeSingle Supported Not supported.
Only for non-Established output connections GFK-2196 Chapter 7 DeviceNet Objects for Series 90-30 Modules. Connection Object Object Class 0x05 The Connection Object handles the module connection. Each Connection Object represents the end points of a connection. In an I/O message, all the information about what to do with the data in the message is contained in the Connection Object for that I/O message.
There can be a maximum of 255 instances of the Connection Object in any combination of connection types. COS/Cyclic Server Connection Attribute Limits (acknowledged) 9.
COS/Cyclic Client Connection Attribute Limits (unacknowledged) 10. COS/Cyclic Server Connection Attribute Limits (unacknowledged) Instance Services Service Param.
Options Reset Delete ApplyAttributes GetAttributeSingle SetAttributeSingle Supported Not supported GFK-2196 Chapter 7 DeviceNet Objects for Series 90-30 Modules. 0x32 GETPLCDATA 0x33 SETPLCDATA Specific Instances The Series 90-30 DeviceNet modules support access to PLC memory using the following segment selectors. The segment selectors are set in the Instance ID of the Explicit request. Selector Code / Name Description Instance ID (dec). Sum of register base and quantity are out of range for this CPU 0x20 0x06 Error communicating with PLC on GETPLCRGS service 0x20 0x07 Error communicating with PLC on SETPLCRGS service GFK-2196 Chapter 7 DeviceNet Objects for Series 90-30 Modules. IC693DNS201. These files are included only for reference; an electronic version of the most up-to- date EDS file is provided as part of the GE Fanuc programming software CIMPLICITY Machine Edition Logic Developer.
The EDS files (and any updates) are also on the GE Fanuc WEB Site www.gefanuc.com/support/plc/. Electronic Datasheet File for the DeviceNet Slave Module $ DeviceNet Electronic Data Sheet $ Copyright (C) 2002 GE Fanuc Automation North America File DescText = '90-30 DeviceNet Slave'; CreateDate =; CreateTime = 12:59:12; ModDate =; ModTime = 12:34:56.
Index Configuring a DeviceNet Slave Module, 4-2 Configuring DeviceNet Master Module, 3-2 Configuring network devices, 3-8 Configuring network settings, 3-2, 3-9, 3-16 ACK timeout, 3-5, 4-5 Connection Object, 6-24, 7-6 Add Device errors, 6-10 Connectors, 2-3 Assembly Object, 6-24, 7-5 CPU fails to read inputs, 5-3 CPU firmware, 1-4 Current limits for cable, 2-2. Index PLC power supply load, 2-2 PLC status references, 5-6 Polled I/O mode, 3-10, 3-11, 3-16, 3-17, 4-8, Hand-Held Programmer, 1-4, 1-6 Power Consumption, 1-4, 1-6, 3-6, 4-6 Program mode transmission, 3-4, 4-5 I/O Messaging, 1-8 I/O Messaging configuration, 3-10, 3-16, 4-8 Identity Object, 6-24, 7-2 Read Module Header, 6-2 Idle packets, 3-4.