GE Fanuc Automation Programmable Control Products Series 90™-30 CPU with Embedded PROFIBUS Interface User's Manual GFK-2334A November 2004
GFL-002 Warnings, Cautions, and Notes as Used in this Publication Warning Warning notices are used in this publication to emphasize that hazardous voltages, currents, temperatures, or other conditions that could cause personal injury exist in this equipment or may be associated with its use. In situations where inattention could cause either personal injury or damage to equipment, a Warning notice is used. Caution Caution notices are used where equipment might be damaged if care is not taken.
Contents Overview and Specifications........................................................................................ 1-1 Finding Information in this Manual ............................................................................... 1-1 For Detailed Information about PROFIBUS ...................................................................... 1-2 For Series 90-30 Installation and Operation ..................................................................... 1-2 Embedded PROFIBUS Master.......
Contents PROFIBUS Slave CPU Configuration .......................................................................... 4-1 Adding a PROFIBUS Slave CPU to the Hardware Configuration ............................... 4-1 Configuring PROFIBUS Parameters for the PROFIBUS Slave CPU .......................... 4-2 PROFIBUS Tab................................................................................................................. 4-2 Input Data Area Tab.........................................................
Chapter Overview and Specifications 1 Finding Information in this Manual Chapter 1, Overview and Specifications: Provides basic information about the Series 90-30 CPUs with embedded PROFIBUS: IC693CPU366, CPU with Embedded PROFIBUS Master IC693CPU367, CPU with Embedded PROFIBUS Slave Chapter 2, Installation: Discusses power requirements, cable specifications, grounding, and module installation. Chapter 3, PROFIBUS Master Configuration: Explains how to configure PROFIBUS master communications.
1 For Detailed Information about PROFIBUS The PROFIBUS logo is a registered trademark of the PROFIBUS International Organization. More information about the organization and the protocol is available at http://www.profibus.com.
1 Embedded PROFIBUS Master The IC693CPU366 contains an embedded PROFIBUS master that allows the CPU to send and receive I/O data from a PROFIBUS-DP network. This manual describes the operation of the PROFIBUS daughterboard. For details on CPU operation, refer to the Series 90-30 CPU Reference Manual, GFK-0467. 1 2 1 LEDs System (SYS) and Communications (COM) indicators. 2 Service Port RS232 Port , 9-pin, male. Used for firmware upgrades. 3 PROFIBUS Port RS485 Port, 9-pin, female.
1 PROFIBUS Master Communications Features The CPU366 provides the following PROFIBUS communications features: Supports all standard data rates Supports a maximum of 1024 bytes of input data and 1024 bytes of output data Supports a maximum of 125 DP slaves Supports a maximum of 244 bytes of input and 244 bytes of output data per slave Supports Sync and Freeze modes Supports DP-V1 Read, Write and Alarm messages Has PROFIBUS-compliant Module and Network Status LEDs Provides an R
1 Embedded PROFIBUS Slave The CPU367 contains an embedded PROFIBUS slave that allows the CPU to operate as a slave on a PROFIBUS DP network and to communicate with a PROFIBUS DP master. The slave module automatically exchanges data with a master device, but has no bus access rights. It can only acknowledge received messages or transmit messages to a master upon request. This manual describes the operation of the PROFIBUS daughterboard.
1 PROFIBUS Slave Communications Features The CPU367 provides the following PROFIBUS communications features: Ability to read up to 244 bytes of input data from the network, and send up to 244 bytes of output data Support for all standard PROFIBUS data rates Support for DP-V1 Read, Write and Alarm messages PROFIBUS-compliant Module and Network Status LEDs An RS-232 serial port (the Service port) for upgrading the firmware IC693CPU367 Slave CPU Specifications 1-6 Catalog number IC693CP
1 PROFIBUS Basics PROFIBUS Network Overview • PROFIBUS is an open, vendor independent fieldbus standard for a wide range of applications in industrial automation, including motion control. • PROFIBUS is a dynamic technology that grows functionally while complying with IEC 61158.
1 Data Bandwidth Demands on PROFIBUS Communications Systems Amount of Data Transmission Duration Transmission Frequency Management level MBytes Hours/Minutes Day/Shift Cell level KBytes Seconds Hours/Minutes Field Level Bytes Several 100 microseconds to 100 milliseconds 10 to 100 Milliseconds Actuator sensor level Bits Microseconds to milliseconds Milliseconds Network Topology PROFIBUS uses linear bus architecture with active bus termination at both ends.
1 Repeater Connecting Segments Participant Participant Participant Remote Repeater Link Segment (No Participants) Termination Branch Segment Participant Participant Participant Remote Repeater Termination To additional participants Repeaters and Bus Termination Network Connectors PROFIBUS connections are typically created with a 9-pin sub-D connector. Other connectors are used for IP67 devices.
Chapter Installation 2 This chapter contains information on the following procedures: Reviewing system power requirements Installing the PROFIBUS CPU module in the PLC rack Installing PROFIBUS wiring Connecting the CPU module to the PROFIBUS network Selecting the proper line type PROFIBUS cable types Installing bus termination Reviewing System Power Requirements Review the power requirements of your system to ensure that your power supply has sufficient capacity to support the PROFIBUS CPU.
2 Installing the PROFIBUS CPU Module in the PLC Rack 1. Remove power from Series 90-30 rack. 2. Turn off power to rack. 3. Place the module into the CPU slot in the main rack by hooking the top of the module on the notch above the slot and slowly lowering the module until it snaps into place. 4. Attach the PROFIBUS cable and terminate as required. Note: For details about installing Series 90-30 rack systems and modules, refer to the Series 90-30 Installation Manual and Hardware Manual, GFK-0356.
2 Connecting the CPU Module to the PROFIBUS Network The module contains a standard female DB9 connector, labeled “PROFIBUS,” that can be connected to a PROFIBUS bus terminal. PROFIBUS DB-9 connector recommendation: Siemens 6ES7-972-OBB50-OXAO (12MB) Pin Assignments for PROFIBUS Connector Pin # Pin Description 1 Shield 2 M24 3 RxD/TxD-P DB9 Line * Termination Connect this pin to pin 8 (data -) with 220 Ohms resistor.
2 Line Types Baud Rate 1 Line A 1, 2 Distance (Max) Line B 1, 2 Distance (Max) Glass Fiber 9.6 kBit/s, 19.2 kBit/s and 93.75kBit/s 1200 m 1200 m 6 km 187.5 kBit/s 1000 m 600 m 6 km 500 kBit/s 400 m 200 m 6 km 1.5 MBit/s 200 m NA 6 km 3 MBit/s, 6 MBit/s and 12 MBit/s 100 m NA 6 km If using a combination of both line types, divide the lengths shown by two. 2 Values shown are the sum of all bus segments and drop cable lengths.
2 Network Termination Termination resistors are needed, as defined in DIN 19245 Part 1 section 3.1.2.5. M aster Slave Slave Slave Slave Slave Term ination Required (Segm ent 1) One terminator must be applied at each end of a network segment. M aster Slave S lave T erm ination Required (Segm ent 1) R epeater Slave S lave S lave Term ination R equired (Segm ent 2) Generally, termination is provided in commercially-available PROFIBUS standard network connectors.
2 VP (6) Ru = 390 Ohms RxD/TxD-P (3) Rt = 220 Ohms RxD/TxD-N (8) Rd = 390 Ohms DGND (5) Bus Termination for Type A Cable in Accordance to PROFIBUS Specifications In addition to the termination shown above, the following compensation should be added for 12 MBit/s bus technology: To/from another node 110nH 9 8 7 110nH 6 5 4 110nH 3 2 1 110nH To/from another node 12 MBit/s Bus Compensation Network Baud Rate The master configures the appropriate network baud rate for each station on the networ
Chapter PROFIBUS Master CPU Configuration 3 These configuration procedures are written for users with at least a basic knowledge of the Machine Edition Logic Developer software and the Series 90-30 PLC. For help with using the software, please see the software’s built-in help system. Note: The PROFIBUS Master CPU does not support redundant masters. Software configuration of the PROFIBUS master CPU consists of the following steps: Adding the PROFIBUS master CPU to the configuration.
3 Configuring PROFIBUS Parameters for the PROFIBUS Master CPU The parameters on the PROFIBUS tab are used to configure the operation of the embedded PROFIBUS master. For details on the Series 90-30 CPU parameters, refer to the software online help. PROFIBUS Tab Slave Status Bit Array Address Starting address for the consumed range used to receive the slave status bits. This array of bits indicates the health of each node on the PROFIBUS network.
3 DPV1 Status The starting reference address of a 32-bit (2-word) produced range used at the beginning of a scan to receive the station address of a slave that has a DPV1 message to send. If another slave has a DPV1 message, it is ignored until the first one has been serviced, and will then appear in a subsequent scan. To acknowledge the DPV1 message and obtain the alarm information it contains, use a DPV1 Alarm Request (task 9) COMMREQ. For details, refer to chapter 5.
3 Download GSD Files Note: 3-4 Determines whether a Full Upload or Generic Upload can be performed from the downloaded configuration. If you set this parameter to False (default), GSD files are not downloaded to the PLC. Subsequent upload operations are Generic. If set to True, the GSD files required by the network configuration are sent to the PLC. Subsequent upload operations are Full uploads.
3 Using Sync/Freeze Control Sync and Freeze are global control functions used to synchronize remote I/O stations. You can use these functions to cause a group of slaves to operate at the same time in your system. ■ The Sync command is used to control a slave’s outputs. When a slave receives a Sync command, it holds the last output data from the master until the slave receives another sync command from the master. ■ Freeze is used to control a slave’s inputs.
3 Configuring Network Settings for PROFIBUS Master To configure network settings for the master, double-click the Network Settings field in the Parameter Editor Settings tab. The Master Properties dialog box opens. Note: You can also open this dialog box by selecting the Project tab of the Navigator and expanding the Hardware configuration folder and the rack that contains the module. Right click the slot containing the IC693CPU366 module, and choose Network Settings.
3 Network Tab of the Master Properties Dialog Box Figure 3-2. Network Tab of MASTER Properties Dialog Box Network parameters are automatically set. This tab provides additional configuration for advanced users. Baud rate The baud rate of the PROFIBUS network. The choices are 9.6 KBps, 19.2 KBps, 93.75 KBps, 187.5 KBps, 500 KBps, 1.5 MBps, 3 MBps, 6 MBps, 12 MBps. Default is 1.5 MBps. Highest Station The highest possible station address for any active station on the network.
3 Parameters Sub-Tab of Network Tab 3-8 Token Retry The number of times the PROFIBUS master tries to pass the token before deciding that a station is not there. Token Error The maximum number of errors in 256 token cycles. Response Error The maximum number of message failures in 16 successive messages. Gap Update Factor The number of token rotations between solicitations for a new PROFIBUS master card.
3 Parameters Tab of the Master Properties Dialog Box Scan Cycle Times Typical This field displays the estimated time (µs) required for one scan of the PROFIBUS network. This is a read-only field. Minimum The minimum I/O scan time in 100 microsecond increments. This may be required if the I/O modules are restricted in how often they can be scanned. To use this parameter, click the Minimum check-box to activate it. Then enter the value in the field next to it.
3 Adding Slave Devices to the IC693CPU366 Master Adding Slaves and Modules 1. In the Navigator window, right click the IC693CPU366 and choose Add Slave. The Slave Catalog dialog box appears. 2. Select a slave device and click OK. The Slave Properties dialog box opens. Note: 3-10 If the slave module is not in the list but you have a GSD file for it, click the “Have Disk” button.
3 Note: The following figures use the Series 90-30 367 PROFIBUS Slave module as an example. Name The name assigned to the slave. You can edit the name or use the default name. The name appears in the title bar of the dialog box (in the figure above, the default name is Station 1 (SERIES 90-30 PROFIBUS SLAVE). Station The address of the slave on a PROFIBUS DP network. The slave is defaulted to the next highest available address. Description An optional description for the slave device.
3 4. To add modules to the slave, select the Modules tab and click Add. The Select New Module dialog box appears. Note: To add the slave to the configuration, you must configure at least one module. Note: The Select New Module list of items to choose from depends on the slave. Each type of slave is likely to have a different list of modules. 5. Select a module and click OK. The module is added to the Modules list in the slave Properties dialog box. Add additional modules as required for your system.
3 Note: To change the order (position) of a module, select it and click Properties. The module Properties dialog box opens. Enter the numerical value of the new position the module is to have. The position numbering starts at 0. 6. When you have finished adding modules, click OK. The modules appear under the slave node in the Hardware Configuration.
3 Configuring Module Data Areas To configure module data areas, right click the module node in the Hardware Configuration, and choose Configure. The Parameter Editor window for the module appears. The values for read-only parameters are supplied from the GSD text file that defines the Profibus module's characteristics. Most devices have one data area with inputs, outputs or both. Some devices have multiple data areas that are shown as additional rows.
3 Configuring DP-V1 Settings for a Slave Whether or not a slave device supports DP-V1 functions is indicated in the GSD file provided by the vendor of that device. For devices that do provide DP-V1 functions, support is disabled by default. To enable DP-V1: 1. In the project Navigator, right click the slave and select Properties. 2. In the Properties window, click the button in the DPV1 Settings field. The PROFIBUS DPV1 Setup dialog box appears.
3 PROFIBUS DPV1 Setup Parameters The default values in this dialog box are populated by the device’s GS? file. Enable DPV1 Support Check this box to enable DPV1 settings for the selected PROFIBUS device. The device's GS? file determines which settings are editable and which are read-only. Clear this check box to disable DPV1 settings. The values of all parameters are retained until the DPV1 settings are enabled again for the selected device.
3 Slave Functions Extra Alarm Service Access Point The service access point (SAP) through which the master quits alarms. Choices: Master Alarmacknowledge SAP51: Master quits alarms via SAP51. Master Alarmacknowledge SAP50: Master quits alarms via SAP50. Configuration Data Convention The DPV1 data types. Choices: Configuration Data of EN 50170 Configuration Data of DPV1 Enabled Alarms Pull Plug Alarm (Editable or read-only, depending on the GS? file.
Chapter PROFIBUS Slave CPU Configuration 4 These configuration procedures are intended for users with at least a basic knowledge of the Machine Edition Logic Developer software and the Series 90-30 PLC. For help with using the software, please see the software’s built-in help system. Software configuration of the PROFIBUS slave CPU consists of the following steps: Adding the PROFIBUS slave CPU to the configuration.
4 Configuring PROFIBUS Parameters for the PROFIBUS Slave CPU The CPU367 has three tabs that contain parameters for the embedded PROFIBUS slave: PROFIBUS, Input Data Area, and Output Data Area. For details on the Series 90-30 CPU parameters, refer to the software online help. Note: The PROFIBUS card used in the CPU367 autodetects the data transmission baud rate. PROFIBUS Tab Station The Slave module’s station number that is used on the PROFIBUS network. Can be in the range from 1 to 125.
4 DP-V1 Class 1 Buffer Length The length of the data buffer in the PROFIBUS chip for Class 1 DP-V1 messages. This includes the length of the header buffer, which is set to 4 bytes. Note: This value impacts the available data width for the cyclic I/O data. Valid range: 0 through 244 bytes.
4 Input Data Area Tab The input data area describes data received over the network by the CPU367 PROFIBUS Slave module from the network Master. These inputs are mapped, using the Input Data Area tab, into specific memory locations in the PLC where the Slave module resides. Area A read-only identifier for the row. Valid range: 1 to 32. Type Data type of area being defined. Valid types are Digital In, Analog In, and Empty. The default value is Empty.
Chapter PROFIBUS Master Status and Diagnostics 5 There are four methods for obtaining status and diagnostic data for the PROFIBUS Master CPU: GFK-2334A Observing and interpreting the LED indicators on the PROFIBUS CPU366, page 5-2 Using the Slave Status Bit Array, page 5-3 Observing the PLC Fault Table, page 5-4 Using Communications Request (COMMREQ) ladder logic instructions to instruct the PROFIBUS Master to gather diagnostic or status data and report it to the PLC CPU, page 5-5 5-1
5 PROFIBUS CPU366 LEDs LED Patterns Before and During PROFIBUS CPU366 Configuration LED Pattern Meaning SYS off and COM blinking green PROFIBUS Master and connected slaves are not configured The following blinking sequence repeats continually: SYS off, COM blinking green SYS off, COM blinking red SYS red, COM off PROFIBUS Master configured in PLC but no slaves added SYS red, COM green PROFIBUS Master configured and slaves added.
5 Slave Status Bit Array The Slave Status bit array contains a bit for each slave. If communication with a slave has no errors, the bit corresponding to the slave (determined by its network address) is set. If the communication has errors or is not occurring for any reason, the bit is cleared. The Master also maintains its own status in the bit corresponding to its network address. The starting reference address for the Slave Status bit array is set in the PROFIBUS Master software configuration.
5 PLC Fault Table Entries Communications errors are displayed in the PLC fault table. For information on using fault tables, refer to the programming software’s online help. For details on the effects of the different types of faults on PLC behavior, refer to the Series 90-30 Reference Manual, GFK-0467. Note: Slave communications status events (loss and re-establish) are reported to the PLC fault table by default.
5 Communication Requests The Communication Request function (COMMREQ) allows the program to communicate with a GE Fanuc intelligent module, such as a PROFIBUS Master. For details on the operation of the COMMREQ function block, refer to appendix A. The figure below illustrates the flow of information between the PLC CPU and the PROFIBUS master. Communications Request Operation for PROFIBUS Master The PROFIBUS Master CPU supports the following COMMREQ tasks and responses.
5 Get Device Status (1) The Get Device Status Command retrieves detailed status information for the specified device. Get Device Status Command Block – Basic Example The following command block accomplishes the following: Get Device Status for Device 1. Return the COMMREQ Status Words to %R10—%R13. Return the Device Status to %R251-%R259.
5 Get Device Status Reply Data Format – Response written to location specified by Words 8 & 9 Word Name Description 1 Command Code Echo of Command Code that this data block is replying to (0x0001). 2 Device Status 1 Code indicating the status of the slave device. See tables below. 3 Device Status 2 Code indicating the status of the slave device. See tables below. 4 Device Status 3 Code indicating the status of the slave device. See tables below.
5 Device Status 2 – Word 3 Bit Name Description 0 Prm_Req Slave must be parameterized. 1 Stat_Diag This bit remains active until all diagnostic data has been retrieved from the slave. 2 1 Always a value of one. 3 WD_On Slave watchdog is activated. 4 Freeze_Mode Freeze command active. 5 Sync_Mode Sync command active 6 Reserved Reserved. 7 Deactivated Slave not active.
5 Get Master Status (2) The Get Master Status Command provides detailed status information about the Master CPU366. Get Master Status Command Block – Basic Example The following command block accomplishes the following: Get Master Status. Return the COMMREQ Status Word to %R10—%R13. Return the Device Status to %R251—%R259.
5 Get Master Status Reply Data Format – Response written to location specified by Words 8 & 9 Word Name Description 1 Command Code Echo of Command code that this data block is replying to. (0x0002) 2 Global State Bits Bits indicating the global state of the master. See “Global State Bits.” 3 DPM State Control state of the Dual Port Memory in the master. See “DPM State” on page 5-11. 4L Error Remote Address Remote address of device with error. See “Error Remote Address” on page 5-11.
5 DPM State This byte indicates the current control state of the Dual Port Memory in the master. DPM State is reported in Word 3 of the Get Master Status reply data and the high byte of Word 4 of the Read Module Header reply data (described on page 5-17). The following table provides definitions of the possible values. Value DPM Master State Description 0x00 OFFLINE The master system has been switched on, but there is no data transfer on the bus.
5 Error Event Codes for PROFIBUS Master (Error Remote Address of 255) Code 5-12 Indication Source Corrective Action 0 No errors are present. None None. 50 USR_INTF-Task not found. Master Firmware is invalid. Module must be updated. 51 No global data-field. Master Firmware is invalid. Module must be updated. 52 FDL-Task not found. Master Firmware is invalid. Module must be updated. 53 PLC-Task not found. Master Firmware is invalid. Module must be updated.
5 Error Event Codes for Slave Devices (Error Remote Address Not Equal to 255) Code Indication Source Corrective Action 0 No errors 2 Slave station reports data overflow. Master Telegram Check length of configured slave parameter or configuration data. 3 Master is requesting a function that is not supported in the slave. Master Telegram Check if slave is PROFIBUS-DP norm compatible. 9 No answering data, although the slave must respond with data.
5 Get Device Diagnostics (4) The Get Device Diagnostic command retrieves detailed status information for the specified device. Get Device Diagnostics Command Block – Basic Example The following command block accomplishes the following: Get Device Diagnostics for Device 1 (a PBS201Release 1). Return the COMMREQ Status Word to %R10—%R13. Return the Device Status to %R251—%R259.
5 Note: A GE Fanuc 90-30 PROFIBUS Slave (PBS201) returns 13 bytes (7 words) of data. Word 10 needs to be 9 or larger. (Word 11) Slave Number: Word 11 specifies the address of the slave to which COMMREQ is directed. If the address of the master or a slave that is not on the bus is entered, a Status response of 4 is returned. Get Device Diagnostics Reply Data Format – Response written to location specified by Words 8 & 9 Word Description Command Code Echo of the Command Code = 4.
5 Read Module Header (5) The Read Module Header command retrieves Network Diagnostic Information and statistics from the device Read Module Header Command Block – Basic Example The following command block accomplishes the following: Read Module Header Data. Return the COMMREQ Status Word to %R10—%R13. Return the Device Status to %R251—%R270.
5 Read Module Header Reply Data Format for Master Word GFK-2334A Name Description 1 Command Code Echo of the Command Code = 5. 2 Interface Type 2 if the interface is a master. 1 if the interface is a slave. 3 Firmware Revision Indicates the current firmware revision: high byte is major version number; low byte is minor version number. 4L Global State Bits (Low Byte) Indicates the global state of the master. See “ Global State Bits” on page 5-10.
5 Clear Counters (6) This command sets the counters in the PROFIBUS Master CPU366 to zero. Clear Counters Command Block – Basic Example In the following command block, Status is returned in %R251—%R252 (words 8 and 9).
5 DP-V1 Read Request (7) The DPV1 Read Request Block is used by the master to perform a DP-V1 Read Request to a slave device. The Command/Response format of this block is as follows. DP-V1 Read Request Command Block – Basic Example The following command block accomplishes the following: Send DP-V1 Read Request to Station Address 1, Slot 2, Index 1: Return the COMMREQ Status Word to %R10—%R13. Return the Device Status to %R251—%R257+x.
5 DP-V1 Read Request Reply Data Format – Response written to location specified by Words 8 & 9 Word Name Description 1 Command Code Echo of the Command Code = 7. 2 Slave Address Echo of Slave address from command. 3 Slot Number Echo of Slot number from command. 4 Index Echo of Index from command. 5 Length Actual length of received data. 6 ReadReqStat The DPV1 status of the read request. This status word indicates success or failure of the DPV1 request.
5 DP-V1 Write Request (8) The DP-V1 Write Request Block is used by the master to perform a DP-V1 Write Request to a slave device. The Command/Response format of this block is as follows. DP-V1 Write Request Command Block – Basic Example The following command block accomplishes the following: Send DP-V1 Write Request to Station Address 1, Slot 2, Index 1. Return the COMMREQ Status Word to %R10—%R13. Return the Device Status to %R251—%R257.
5 DP-V1 Write Request Reply Data Format – Response written to location specified by Words 8 & 9 Word Name Description 1 Command Code Echo of the Command Code = 8. 2 Slave Address Echo of Slave address from command. 3 Slot Number Echo of Slot number from command. 4 Index Echo of Index from command. 5 Length Actual length of received data. 6 WriteReqStat The DPV1 status of the read request. This status word indicates success or failure of the DPV1 request. See status table below.
5 Error Code 1 The bits that make up the Error Code 1 byte are defined below.
5 DP-V1 Alarm Acknowledge (9) The master uses the DP-V1 Alarm Request Block to perform a DP-V1 Alarm acknowledgement to a slave device. This message is sent to acknowledge and receive information about an alarm when the alarm information appears in the DP-V1 status words of the PLC. The information mapped to these words must be used in the DP-V1 Alarm Response command to process the alarm properly. The mapping of these words is as follows.
5 (Word 9) Local PLC - Memory Starting Address: Word 9 is a 0-based offset that determines the starting address in the local PLC in which the response is to be written. The value entered is the offset (0-based) from the beginning of PLC memory for the memory type and mode specified in Word 8. This offset will be either in bits, bytes, or words depending on the mode specified (for example, if Word 8=16 and Word 9=2, then the starting address will be %I17).
Chapter PROFIBUS Slave Status and Diagnostics 6 There are three methods for obtaining status and diagnostic data: Observing and interpreting the LED indicators on the PROFIBUS CPU367, page 6-2 Monitoring the Status/Firmware ID Array, page 6-3 Using Communications Request (COMMREQ) ladder logic instructions to instruct the PROFIBUS slave to gather diagnostic or status data and report it to the PLC CPU, page 6-4 Note: GFK-2334A The PROFIBUS slave does not generate faults for the Fault Table.
6 PROFIBUS CPU367 LEDs LED Patterns Before and During PROFIBUS CPU367 Configuration SYS LED Color Indication Flashing Green This LED flashes green for two seconds at system startup Off PROFIBUS slave is not configured COM LED Off The PROFIBUS slave does not use the COM LED, except when loading firmware and to indicate it is not configured. This LED is normally off. Flashing Green PROFIBUS slave is not configured Note: When loading firmware, the module is placed in the System Configuration mode.
6 Status/Firmware ID Array The starting reference address for this two-word array is set in the PROFIBUS slave software configuration. For details, see “PROFIBUS Slave Parameters” in chapter 4. Word Name Description 1 Slave Status This word contains the slave status code. The status can be read using the Get Slave Status COMMREQ (task 3), described on page 6-4. . 2 Firmware ID Current firmware version running on the slave module.
6 Communication Requests The Communication Request function (COMMREQ) allows the program to communicate with a GE Fanuc intelligent module, such as a PROFIBUS slave. For details on the operation of the COMMREQ function block, refer to appendix A. The figure below illustrates the flow of information between the PLC CPU and the PROFIBUS slave. Communications Request Operation for PROFIBUS Master The PROFIBUS slave supports the following COMMREQ tasks and responses.
6 Get Slave Status COMMREQ (Command Code 3) The Get Slave Status COMMREQ retrieves detailed status information for the slave device from the 16-bit slave status word. The starting address of this word is configured as Status/Firmware ID Address in the PROFIBUS slave software configuration. For details, refer to “PROFIBUS Slave Parameters” in chapter 4. Get Slave Status Command Block – Basic Example Get Slave status for Device Return the COMMREQ status words to %R10—%R13.
6 Get Slave Status - Reply Data Format Word Name Word 1 CommandCode Word 2 Last Error See “Slave Last Error Codes” on page 6-6. Word 3 Running State Word values: xxx1 – Slave in initialization state. If slave remains in this state the slave hardware configuration has an error. xx1x – Slave initialized without error. x1xx – Slave diagnostics information is being sent. 1xxx – Data exchange is active with master.
6 Value Dec (Hex) GFK-2334A Meaning 75 (0051) DPS_ERR_INIT_SPC3_LESS_MEM Not enough memory in SPC3 for all buffers. 76 (0052) DPS_ERR_INIT_DIN_DOUT_BUF_LEN Illegal I/O data buffer length. 77 (0053) DPS_ERR_INIT_DIAG_BUF_LEN Illegal diagnostic buffer length. 78 (0054) DPS_ERR_INIT_PRM_BUF_LEN Illegal parameter buffer length. 79 (0055) DPS_ERR_INIT_CFG_BUF_LEN Illegal configuration buffer length. 80 (0056) DPS_ERR_INIT_SSA_BUF_LEN Illegal SSA buffer length.
6 Read Module Header (5) The Read Module Header command retrieves Network Diagnostic Information for the device. Read Module Header Command Block – Basic Example The following command block accomplishes the following: Get Module Header Data Return the COMMREQ Status Word to %R10—%R13. Return the Device Status to %R251—%R275.
6 Read Module Header Reply Data Format for Slave Word GFK-2334A Name Description 1 Command Code Echo of the Command Code = 5. 2 Interface Type 2 if the interface is a master. 1 if the interface is a slave. 3 Firmware Revision Indicates the current firmware revision. High Byte is major version number. Low Byte is minor version number. 4 Slave Bus Address Address of slave in active bus. 5 Ident Number PROFIBUS identification number. 6 Last Error Last Error reported from slave.
6 Clear Counters (6) The Clear Counters Command sets the counters in the PROFIBUS module to zero. Clear Counters Command Block – Basic Example In the following command block, Status is returned in %R251—%R252 (words 8 and 9).
6 DP-V1 Read Response (7) Read Response Command Block – Basic Example When a DP-V1 master executes a Read Request to a slave, an indication will appear in the DP-V1 status register of the PLC. The application program must use this information in order to formulate the appropriate COMMREQ response to the master’s request. The response format for this COMMREQ is as follows. Word 1 Dec (Hex) 8+x Definition Length of command block (0008+x) 2 0 (0000) Always zero - no wait mode request.
6 Read Response Reply Data Format Word 1 6-12 Name Command Code Description Echo of Command code = 7 2 Master Address Echo of master address from command 3 Slot Number Echo of Slot Number from command 4 Index Echo of Index from command 5 Length Actual length of data sent 6 ReadResStat (Read Response Status) 0 = Successful 1 = Unsuccessful 7—12 Reserved Reserved Series 90™-30 CPU with Embedded PROFIBUS Interface – November 2004 GFK-2334A
6 DP-V1 Write Response (8) Write Response Command Block – Basic Example When a DP-V1 master executes a Write Request to a slave, an indication will appear in the DP-V1 status register of the PLC. The application program must use this information in order to formulate the appropriate COMMREQ response to the master’s request. The response format for this COMMREQ is as follows. Word Dec (Hex) Definition 1 7 (0007) Length of command block 2 0 (0000) Always zero - no wait mode request.
6 Write Response Reply Data Format Word 1 6-14 Name Command Code Description Echo of Command code = 8 2 Master Address Echo of master address from command 3 Slot Number Echo of Slot Number from command 4 Index Echo of Index from command 5 Length Actual length of data received 6 WriteResStat (Read Response Status) 0 = Successful 1 = Unsuccessful 6+x Data Data received (0 to 65535 (0 to FFFF)) … … Data received (0 to 65535 (0 to FFFF)) Series 90™-30 CPU with Embedded PROFIBUS Interfac
6 DP-V1 Alarm Request (9) The slave can send DP-V1 alarm indications to a master. The format of this COMMREQ is as follows. Alarm Request Command Block – Basic Example Word Dec 1 9+x (Hex) Definition Length of command block (0009+x) 2 0 (0000) Always zero - no wait mode request.
6 (Word 13) Alarm Type: The Alarm Type is application specific and is in the range of 0254. (Word 15) Alarm Size: The Size field holds the number of words of data in this COMMREQ. It holds 0 (zero) if no data needs to be transmitted to the master. (Word 16…) Alarm Data: This is an optional field and can be used to transmit additional alarm relevant data to the master. The length of the data must be entered in the Size field.
Appendix COMMREQ Operation A The Communication Request function (COMMREQ) allows the program to communicate with a GE Fanuc intelligent module, such as a PROFIBUS master or slave. The COMMREQ function uses a command block that contains the data to be communicated to the device, plus information related to the execution of the COMMREQ. The command block must be placed in the designated memory area using data move instructions, such as MOVE or BLKMOV (Block Move).
A COMMREQ Ladder Instruction A Communications Request is initiated when a COMMREQ ladder instruction is activated during the PLC scan. At this time, a command from the PLC via the Communications Request is sent to the PROFIBUS device. At the conclusion of every request, the CPU reports the status of the request to the Status Word, which is a location in PLC memory that is designated by the Status Word Pointer in the Command Block.
A COMMREQ Programming Requirements and Recommendations GFK-2334A COMMREQ instructions should be enabled by a contact from a transition coil. If using more than one COMMREQ in a ladder program, verify that a previous COMMREQ executed successfully before executing another one. This can be done by checking the Status Word and the FT (Fault) output. The FT output is held False if the Enable Input is not active.
A Error Detection and Handling As shown in “COMMREQ Status Word”, a value of 1 is returned to the Status Word if communications proceed normally, but if any error condition is detected, a value greater than 1 is returned. If you require error detection in your ladder program, you can use a Greater Than (GT) compare instruction to determine if the value in the Status Word is negative (less than zero). If an error occurs, the GT instruction’s output (Q) will go high.
A COMMREQ Status Word The following table defines the state codes that can be returned in the COMMREQ status word. Value Dec (Hex) 0 (0000) 1 (0001) Description Device has not yet processed the COMMREQ. Command Complete Note: This status does not necessarily mean success. Some commands have reply data that must also be checked.
Index A Get Device Status, 5-6 Get Master Status, 5-9 Get Slave Status, 6-5 Adding slave devices, 3-10 C Cable specifications, 2-4 Clear Counters (6), 5-18, 6-10 COMMREQs Clear Counters (6), 5-18, 6-10 DP-V1 Alarm Acknowledge (9), 5-24 DP-V1 Alarm Request (9), 6-15 DP-V1 Read Request (7), 5-19 DP-V1 Read Response (7), 6-11 DP-V1 Write Request (8), 5-21 DP-V1 Write Response (8), 6-13 Get Device Diagnostics (4), 5-14 Get Device Status (1), 5-6 Get Master Status (2), 5-9 Get Slave Status, 6-5 Read Module He
Index R Read Module Header, 5-16, 6-8 Redundant masters, 3-1 Removing the module from the rack, 2-2 S Selecting the proper line type, 2-3 Series 90-30 additional information, 1-2 Slave diagnostics/firmware ID array, 5-3 Slave status bit array, 5-3 Specifications cable, 2-4 master module, 1-4 slave module, 1-6 Status DP-V1, 4-3 slave status/firmware ID arrray, 6-3 Status and diagnostic methods, 6-1 master, 5-1 Status Word codes, COMMREQ, A-5 T Task ID COMMREQ, A-2 Index-2 Series 90™-30 CPU with Embed
