Series 90-30 FIP Bus Controller User`s Manual, GFK-1213
Contents
1. 1 2 8 a R0 05 FBC IN1 Sg IO128 I 2 5 7 a R0 05 FBC IN1 lt 3 I0128 10257 0384 Second input area RO 05 FBC IN2 lt S EE UNASSIGNED olo eT ENT R0 05 FBC IN2 lt 9 3 2 ENT R0 05 FBC IN2 lt S J AI0032 AI 7 ENT R0 05 FBC IN2 lt S 9 J AI0032 AI0097 0128 At each acguisition the PLC will place the Boolean inputs consumed in the FIP network by the FIP Bus Controller FBC at addresses 901257 to 1384 and the analog inputs at address AI97 to AI128 the data is distributed in these input areas as per the configuration defined by the network interface configuration Output areas Press the key again to access selections for output areas Proceed as for input areas described above At each output the PLC will place the data produced in the FIP network by the FIP Bus Controller FBC in the same way as for acguisitions Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Configuration of Each COMV Mode 11 Only GFK 1213 This operation is only possible if the network interface was configured with the Hand Held Programmer HHP external configuration version number 0 Press the key to select the COMV type The default COMV type is empty no COMYV If this is appropriate press the key to go directly to the next COMV Otherwise press the key to display the other COMV types prod cons then to validate Press th2. 0000 2 3 Observing the LEDS 0 ce ee ee a ee wees 2 4 Upgrading the Bus Controller Firmware VVV V eee eee 2 5 Chapter 3 Hand held ProgrammerConfiguration v v 3 1 Setting the PLC to Stop Mode 6 FY FF eee eee 3 2 FIP Bus Controller FBC Slot Number VVYY Y YF Yu eee 3 3 Yl PLC Memory Addresses V Y YF Y Yu 3 4 Configuration Mode die iae eee eens 3 5 Communication Protocol and Tslot VVYYYFFFFF Y eee 3 6 Subscriber Number and Medium Number V rr iiu 3 7 Maximum Time Between Two CPU Module Input Scans 3 8 Bus Arbiter and External Configuration Version Numbers Mode 11 Only 3 9 Size and Addresses in the PLC Memory YVYYFF eee eee ee 3 10 Configuration of Each COMV Mode 11 Only 006 3 13 Building each COMV Mode 11 Only VVYFY YY eee 3 15 Configuration of the STATFBC COMV Mode 11 Only 3 19 Validation of Configuration 6 cece eee eee 3 20 Hand held Programmer HHP Error Messages 00000 2000 3 21 Chapter 4 Configuration and Operating Modes 4 1 Configuration Mode 10 2 6 LL REF uu 4 2 Configuration Mode 11 2 nce eee ees 4 9 Chapter 5 Diagnostics ee secs etree swe arn weed daw kee Rd Y eaten 5 1 Appendix A Description of COMVS cece cece cece e cece Ynn A 1 Appendix B Examples ces i was Wd i GN
3. H HHP Error Messages Idle mode in mode 10 4 3 4 5 in mode 11 4 10 Init mode in mode 11 Installation p 2 L LEDs 1 2 2 4 M Media number of Medium number B 7 Memory Address Mode 10 configuration parameters Mode 11 configuration parameters Modes 4 1 Mode 10 GFK 1213 Series 90 30 FIP Bus Controller User s Manual March 1996 Index 1 Index Index 2 mode 11 4 9 Module location O Operation in Mode 10 4 3 Operation in Mode 10 4 2 P Performance in mode 10 in mode 11 4 14 Pin assignments for the bus connectors PLC memory address for FBC 3 4 PLC memory usage in mode 10 in mode 11 8 11 PLC Stop mode setting with HHP 3 2 Port Protocol in mode 10 in mode 11 4 14 R Ready mode in mode 10 4 5 in mode 11 4 10 4 11 Registers number transferred in mode 10 4 7 Remote Drops 1 1 Removing the Module 2 2 Return time in mode 11 4 14 Running mode in mode 11 4 10 4 11 Series 90 30 FIP Bus Controller User s Manual March 1996 Running lock ed mode in mode 10 4 3 ME lock ed mode in mode 10 S Scan time Serial port Shock Silence time in mode 11 4 14 Slot number Specifications 1 3 Standby mode in mode 11 4 13 Statfbc COMV A 3 In mode 10 4 2 in mode 11 3 19 4 9 Stop mode setting with HHP b Subscriber number R in mode 10 4 7 in mode 11 a Trans
4. 10 USING MODE 11 The Configuration mode cannot be changed if any area input or output has been assigned In this case you must delete the assignments of each area one by one or else cancel the entire configuration the key then start module configuration over again GFK 1213 Chapter 3 Hand held Programmer Configuration 3 5 Communication Protocol and Tslot To select the communication protocol press the key The default protocol is WorldFIP If this is the protocol you want press the key to go directly to the next parameter Otherwise press the key to display the other protocols FIP slowFIP Then press the key to validate The next parameter is Tslot Press the key The default Tslot is 62 nsec If this is appropriate press the key to go directly to the next parameter Otherwise press the key to display the other values 250 nsec 625 nsec 2500 nsec Then press the key to validate The recommended value is 250 nsec all other values are reserved for special requirements Example For a WorldFIP protocol with a Tslot of 250 nsec proceed as follows Key Strokes Display gt R0 05 FBC lt S PROTOCOL WORLD RO 05 FBC lt S TSLOT 62 S RO 05 FBC lt S TSLOT 250 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Subscriber Number and Medium Number Press the key to select the subscribernumber Enter the subscriber nu
5. GFK 1213 For these results proceed as follows Configuration of 1st TVA x El e E gt ENT ENT 2 ENT J A 8 Chapter 3 Hand held Programmer Configuration ENT R0 05 FBC C1 T1 EMPTY R0 05 FBC C1 T1 BOOL OFF R0 05 FBC lt S C1 T1 LEN 1 R0 05 FBC lt S C1 T1 LEN 8 R0 05 FBC lt 9 C1 T1 POS 0 R0 05 FBC lt 9 C1 T1 AREA 1 R0 05 FBC lt 9 C1 T1 AREA 12 R0 05 FBC lt 9 C1 T1 OFF 0 R0 05 FBC lt S C1 T1 OFF 8 Configuration of 2nd TVA AIALA ai JEE 2 JIE gt JAG E e HE R0 05 FBC C1 T2 EMPTY R0 05 FBC C1 T2 NUM OFF R0 05 FBC lt S C1 T2 LEN 1 R0 05 FBC lt S C1 T2 LEN 16 R0 05 FBC lt S C1 T2 POS O R0 05 FBC lt S C1 T2 POS 16 R0 05 FBC lt S C1 T2 AREA 1 R0 05 FBC lt S C1 T2 AREA 14 R0 05 FBC lt S C1 T2 OFF 0 R0 05 FBC lt S C1 T2 OFF 24 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 GFK 1213 Configuration of the STATFBC COMV Mode 11 Only This operation is only possible if the network interface was configured with the Hand Held Programmer HHP external configuration version number 0 Press the key to select the Statfbc COMV The default selection is no COMV not produced If this is ap
6. lt S USING MODE GO R0 05 FBC lt S USING MODE 10 m Mode 11 Key Strokes Display RO 05 FBC lt S USING MODE 11 y 3 R0 05 FBC lt S USING MODE GO RO 05 FBC lt S USING MODE 11 3 20 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 GFK 1213 Hand held Programmer HHP Error Messages The Hand Held Programmer HHP displays error messages to inform you of configuration errors if the FIP Bus Controller FBC is absent or if it is not communicating with the PLC Message Meaning REFER The reference address is outside the range of this PLC model REFADJ Indicates one of the following situations A References have been adjusted to the lowest byte B Logical references have been adjusted to the highest byte I OERR You have assigned reference addresses which overlap with references already assigned DAT ERR A parameter is outside permissiblelimits CFG ERR Configurationerror Chapter 3 Hand held Programmer Configuration 3 21 Chapter Configurationand Operating Modes GFK 1213 4 This chapter describes the characteristics of Configuration modes 10 and 11 m Configuration Mode 10 Control of Network Interface Operating Modes Exchange of Application Data Between the CPU and the Network Mode 10 Characteristics and Performance of Mode 10 m Configuration Mode 11 Control of Network Interface Operating Mo
7. press these keys Key Strokes Display RO 05 FBC OUT1 lt S gt UNASSIGNED ENT R ll R0 05 FBC OUT1 lt S R 3 2 Ei RO 05 FBC OUT1 lt S R0032 R 1 BYT R0 05 FBC OUT1 lt S R0050 R0001 0032 At each output the PLC will place the data produced on the FIP network by the FIP Bus Controller FBC in the registers R1 to R32 the data is distributed in these registers as per the configuration defined in the config COMV Configuration mode 11 In Configuration mode 11 each input and output area must be associated with the PLC memory Input areas Press the key to select the variable type in each input area Enter the variable type and press to validate To select the input area size enter the size of the area 0 to 2040 Boolean variables representing 0 to 255 bytes or else 0 to 127 words and press or to validate to validate To select the input area location enter the start address and press Chapter 3 Hand held Programmer Configuration 3 11 Example If you want to use 128 I addresses that is 16 bytes starting from address I257 in the first input area in 1 and 32 AI addresses starting from address AI97 in the second input area in 2 proceed as follows Key Strokes Display First input area R0 05 FBC IN1 lt S UNASSIGNED cu ENT A ci 7D J ee FBC IN1 lt
8. 10 only if the configuration specifies in running mode 11 The FIP identifier of the Statfbc COMV is 0000 hexadecimal subscriber number The Statfbc COMV contains 8 bytes specific to it described below plus a refresh byte Word Description 1 Type 1 subscriber 03 in hexadecimal This parameter indicates that the subscriber is a Series 90 30 or an Alspa C80 35PLC 2 Type2subscriber This parameter contains the Configuration mode 10 or 11 in hexadecimal 3 4 Version number of m the network interface configuration indicated in the first two bytes of the Config COMV for mode 10 m the external configuration for mode 11 Version number 0 means there is no configuration The configuration number is between 1 and FFFF hexadecimal 5 Operating mode of the FIP Bus Controller FBC network interface hex In Configuration mode 10 00 error 01 idle 02 ready 03 running lock ed 04 running unlock ed In Configuration mode 11 00 error 02 ready 03 running 6 Contains the following bits mbit 0 FIP statusbit This parameter is set to 1 as soon as a consumed COMV becomes invalid invalid refresh or promptness bits 1 to 6 reserved m bit 7 in using mode 10 indicates the standby status it is set to 1 as soon as the network is disconnected and reset by a Command COMV Not used in mode 11 7 Contains the following bits m bit 0 host status This parameter is set to 1 as soon as the
9. RQ with the PLC memory Although R memory is recommended other types are also permitted Boolean variables must be a multiple of 16 In all cases data is read and written in the COMV s as per the MSB LSB method Input area RI Press the key to select the variable type in input area Enter the variable type and press to validate To select the input area size enter the size of the area 0 to 127 words or else 0 to 2032 Boolean variables representing 0 to 254 bytes and press to validate To select the input area location enter the start address and press to validate Example If you want 50 RI addresses starting from the PLC address R40 press these keys Key Strokes Display R0 05 FBC IN1 lt S e UNASSIGNED R 5 R0 05 FBC IN1 lt S R 5 0 Ei R0 05 FBC IN1 lt S R0050 R 4 0 Ei RO 05 FBC IN1 lt S R0050 R0040 0089 At each acguisition the PLC will place the data consumed in the FIP network by the FIP Bus Controller FBC in the registers R40 to R89 data will be distributed in these registers as per the configuration defined by the config COMV Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 GFK 1213 Output area RQ Press the key again to call the output variable type selection screen Proceed as for the input area Example If you want to have 32 RQ addresses starting from the PLC address R1
10. Utility and follow its instructions to update the firm ware Chapter 2 Installation Chapter 3 Hand held Programmer Configuration This chapter describes configuration steps for the Bus Controller using a Hand held Programmer HHP The module must be physically present to be configured by the HHP The HHP may be used to enter change or remove a configuration The Hand Held Programmer must be connected to the power supply module and be connected to the PLC The PLC power must be ON and the PLC in STOP mode The FIP Bus Controller FBC must be installed in the desired slot Configuration of the FIP Bus Controller FBC includes choosing the Configuration mode and setting its parameters Mode 10 Mode 11 FIP Bus Controller FBC slot number in the PLC rack Configuration mode 10 Configuration mode 11 Communicationprotocol FIP WorldFIP and Tslot Subscriber number and medium number Maximum time between input scans by the CPU module Notapplicable Bus arbiter BA version numbers and external configurationnumbers Addresses in I PLC memory of 16 validity bits of consumed COMV s 1 invalid and of the module status register Addresses in I PLC memory of 16 validity bits of input areas 1 invalid and of the module status register Size and addresses in R PLC memory of the input area RI updated based on COMV s consumed by the module Size and addresses in PLC memory
11. Yd dw Md dd tas eh aie yes B 1 GFK 1213 Series 90 30 FIP Bus Controller User s Manual March 1996 v Chapter GFK 1213 1 Introduction The Series 90 30 PLC FIP Bus Controller catalog number IC693BEM340 is used to inter face a FIP I O network to a Series 90 30 PLC Series 90 70 PLC a46566 Series 90 30 PLC a lt g C o lo fe o VIO J on 2 g Optional Redundant FIP Bus FIP I O B Field Control O Bua I O Station FIP Bus ld FIP Inter Interface Unit o face Module rs Generic Up to 8 li Device Field Control Series 90 30 modules Remote I O Scanner 4 shown Optional Expansion Rack AFIP bus is used to connect different types of devices on the FIP network Series 90 70 PLC interfaced to a FIP bus by a Fip Bus Controller Field Control Stations Field Control I O modules that are interfaced to the bus via a FIP Bus Interface Unit BIU m Remote Drops Series 90 30 I O racks that are interfaced to the bus via FIP Remote I O Scanner Modules Each remote drop can have one 5 or 10 slot main rack one 5 or 10 slot expansion rack and any mix of discrete and analog I O modules m Generic Devices such as genera
12. modes 10 and 11 Related Publications For more information refer to these publications Series 90 30 FIP Remote I O Scanner User s Manual GFK 1038 This book is a reference for installing configuring and using a GE Fanuc Series 90 30 FIP Remote I O Scanner Series 90 70 FIP Bus ControllerUser s Manual GFK 1038 Reference manual for the Bus Controller which interfaces a FIP bus to a Series 90 70 PLC This book describes the installation and operation of the Bus Controller It also contains the programming information needed to interface FIP devices to a Series 90 70 PLC FIP Bus Interface Unit User s Manual GFK 1175 This manual describes the Field Control FIP Bus Interface Unit It explains operation of the Bus Interface Unit as a FIP bus device GFK 1213 Series 90 30 FIP Bus Controller User s Manual March 1996 iii Preface iv Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Contents Chapter 1 Introduction ss ia eu ose dita Yf beri BAY Tw eee age AGA GR 1 1 FIP Bus Controller Description Y YY eee eee 1 2 Module Specifications essei ie eee eens 1 3 Compatibility eners reer boei Wie eran Wh winds WI dn ee na aa eles 1 3 Chapter 2 Installation ee wd Y oars hae t een Uo 2 1 Module Installation ues y hb eel be ee here Fy NA 2 2 Module Removal p sed sits Satine Suc y RY Meg eS dwU 2 2 Connecting the FIP Bus to the Bus Controller
13. transfer time v 5 msec exchange_time time_if_error exchange_time 1 msec n_bytes total number of bytes exchanged with CPU module time_if_error 10 nsec n_TVA This time is only involved when a medium is lost n_TVA total number of TVAs making up the consumed COMVs or when there is a refresh error of a consumed COMV n_TVA number of TVAs making up the COMV concerned transmit rate of I O bus used during dialog with the CPU CPU 331 23 nsec per word CPU 341 20 nsec per word CPU 351 18 nsec per word m dynamic characteristics of network interface Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 time for acknowledgment of an avalanche of N consumed COMVs N COMVs transmitted successively at maximum network speed v 3 msec 1 msec N exchange_time time_if_error assuming there is no more than one PLC sweep during the avalanche maximum time to refresh a COMV after write by the CPU depends on priority level P attributed during configuration a COMV is transmitted every P internal sweeps the maximum duration of a sweep is 5 msec 1 msec n_COMV exchange_time time_if_error where n_COMV is the total number of COMVs consumed and produced during the sweep 1 if the configuration requires production of the Staffbc COMV it is assumed that there is at least one exchange with the CPU during the sweep GFK 1213 Chapter 4 Configur
14. 3 parameters bytes m bits 0 to 2 type of TVA 000 no TVA 011 RI the COMV is produced therefore the TVA contains the input registers 110 RQ the COMV is consumed therefore the TVA contains the output registers Other values are non representative m bit 3 default mode of TVA inputs when the statusbits of the consumed COMVsare invalid 0 reset 1 frozen at last valid status m bits 4 to 7 rank of frequency 0000 rank 0 0001 rank 1 0010 rank 2 0011 rank3 0100 rank4 0101 rank5 The 2nd byte indicates the position in the COMV 0 to 122 bytes where the TVA is written for a consumed COMV or read for a produced COMV Byte 3 indicates the offset in the data area where the TVA is written for input data or read for output data This is expressed as a number of bytes 0 to 254 The 4th byte indicates the length of the TVA 0 to 124 bytes This must be an evennumber If it is zero the TVA does not exist The 5th byte contains the length of the COMV 0 to 124 bytes not including the refresh bit If this byte is 0 the COMV does not exist Bytes 6 and 7 contain the identifier of the associated COMV 0 to FFFF hex 62 checksum of the first 122 bytes of the COMV 0 to FFFF in hexadecimal A 2 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Statfbc COMV The Statfbc COMV is transmitted periodically by the FBC software always in running mode
15. A program through the serial port If that is appropriate press the key to go directly to the next parameter Otherwise enter the version number between 1 and 255 and press am to validate In this case you must load a bus arbiter program with the same version number as the number configured Example 1 Proceed as follows to choose a FIP Bus Controller FBC which is a bus arbiter with BA program number 3 Key Strokes Display R0 05 FBC lt S BA CONF 0 J R0 05 FBC lt S BA CONF 3 The external configuration version number is the next parameter Press the key to select it The default version number is 0 This means the network interface will be introduced by the HHP and you do not have to load the external configuration through the serial port If this is appropriate press the key to go directly to the next parameter Otherwise enter the version number between 1 and 255 and press to validate You will have to load an external configuration with the same version number as the number configured Example 2 Proceed as follows to select an external configuration with version number 27 Key Strokes Display R0 05 FBC lt S EXT CONF 0 2 7 J RO 05 FBC lt S EXT CONF 27 GFK 1213 Chapter 3 Hand held Programmer Configuration 3 9 Size and Addresses in the PLC Memory Configuration mode 10 In Configuration mode 10 you must associate the input area RI and the output area
16. FANUC GE Fanuc Automation Programmable Control Products Series 90 30 FIP Bus Controller User s Manual GFK1213 March 1996 GFL 002 Warnings Cautions and Notes as Used in this Publication 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 notices are used where equipment might be damaged if care is not taken Note Notes merely call attention to information that is especially significant to understanding and operating the equipment This document is based on information available at the time of its publication While efforts have been made to be accurate the information contained herein does not purport to cover all details or variations in hardware or software nor to provide for every possible contingency in connection with installation operation or maintenance 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 GE Fanuc Automation makes no representation or warranty expressed implied or statutory with respect to and assumes no responsibility for the accur
17. FBC detects a CPU communicationfault m bit 1 applicationrunning This parameter is set to 1 as soon as the application stops running mbit 2 redundantmedia This bit is set to 1 as soon as one of the two media is disconnected when redundancy has been selected m bits 3 to 7 not applicable 8 Reserved for software version 0 to FF in hexadecimal GFK 1213 Appendix A Description of COMVs A 3 Appendix B Examples The two examples below are common to Configuration modes 10 and 11 Example 1 In this example not much data is exchanged between the FBC module and the CPU This means dialog over the FIP bus is fast The configuration is as follows 2 consumed COMVs of 4 bytes each including a 4 byte TVA 2 produced COMVs of 4 bytes at priority 1 highest possible rate each with a 4 byte TVA plus the Statfbc COMV The refresh and promptness freguencies of the COMVs are each 10 msec The network validity must be tested in the worst case every 10 msec The bus arbiter program provides transport of the 5 COMVs alone at the highest rate no BA_WAIT over the FIP bus The FBC and the CPU module exchange 22 bytes in each direction plus the 32 validity bits 68 bytes in all The application program defined for a 331 CPU is minimum it only copies the 8 bytes consumed on the FIP bus in the 8 bytes produced Under these conditions a measurement made over 100 seconds shows the following characteris
18. MV 1 PER 2500 R0 05 FBC lt S COMV 1 PRIOR 1 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Building each COMV Mode 11 Only This operation is only possible if the network interface was configured with the Hand Held Programmer HHP external configuration number 0 Press the key to configure the first TVA of the first COMV C1T1 the first time it is pressed or the next TVA for the current COMV thereafter The first parameter is the TVA type empty no TVA is the default type If this is appropriate press the key to go directly to the next TVA of the same COMV C1T2 Otherwise press the key to display the other types m bool off Boolean variable with value 0 TVA at 0 in the case of a consumed COMV reception fault m bool frz Boolean variable whose value is frozen TVA frozen in the case of a consumed COMV reception fault num off numerical variable words coded as per FIP standard from MSB to LSB with value 0 TVA at 0 in the case of a consumed COMV reception fault m num frz numerical variable words coded as per FIP standard from MSB to LSB in the case of a consumed COMV reception fault After selecting the TVA type press to validate Then press the key to go to the next parameter TVA length len Enter the length 1 to 125 bytes for Boolean variables or else an even value between 2 and 124 b
19. acy completeness sufficiency or usefulness of the information contained herein No warranties of merchantability or fitness for purpose shall apply The following are trademarks of GE Fanuc Automation North America Inc Alarm Master GEnet PowerMotion Series One CIMPLICITY Genius ProLoop Series Six CIMPLICITY PowerTRAC Genius PowerTRAC PROMACRO Series Three CIMPLICITY 90 ADS Helpmate Series Five VuMaster CIMSTAR Logicmaster Series 90 Workmaster Field Control Modelmaster Copyright 1995 1996 GE Fanuc Automation North America Inc All Rights Reserved Preface Content of this Manual Chapter 1 Introduction This chapter describes the Series 90 30 PLC FIP Bus Controller FBC Chapter 2 Installation This chapter explains how to install and remove the Bus Controller connect the FIP bus observe the LEDs and upgrade the Bus Controller firmware Chapter 3 Hand held Programmer Configuration This chapter explains the Hand held Programmer configuration steps for a FIP Bus Controller Chapter 4 Configuration and Operating Modes This chapter describes the characteristics of Configuration modes 10 and 11 Chapter 5 Diagnostics This chapter describes the contents of the Staffbc COMV Appendix A Description of COMVs This appendix contains detailed description of the COMVs used in the various functions of the FIP Bus Controller FBC Appendix B Examples This appendix includes two examples which are common to Configuration
20. annel 1 O O Connector for Channel 2 B O Note If only one FIP bus is used cover the unused FIP bus connector with an anti static cap The unused connector must be protected in this manner to meet IEFE specification 801 2 Pin Assignments for the FIP Bus Connectors The diagram below shows pin assignments for both FIP bus connectors on the front of the Bus Controller a46556 D co o 2 7 o 3 D 8 o 4 91 OF 5 GFK 1213 Chapter 2 Installation 2 3 Observing the LEDs When power is applied the LEDs on the Bus Controller indicate operating status a46557 Module OK Run Carrier Detect Ch 1 LEDs gt Transmit Enable Ch 1 9 Carrier Detect Ch 2 Transmit Enable Ch 2 O The top LED indicates module health The bottom five LEDs indicate communications activity on the FIP bus Two LEDs are dedicated to each of the two FIP channels MODULE OK Shows the status of the FIP Bus Controller This LED blinks during power up diagnostics and should remain on as long as power is applied to the Bus Controller RUN Shows the operational status of the FIP Bus Controller This LED turns ON when the module status is being scanned by the CPU CARRIER DETECT A Carrier Detect LED is ON when the Bus Controller is detecting a carrier signal on the FIP bus attached to that channel TRANSMIT ENABLE A Transmit Enable LED is ON when the Bus Controller trans m
21. ation and Operating Modes 4 15 Chapter GFK 1213 5 Configurationand Operating Modes Diagnostics concerning the network are made possible by the contents of the Statfbc COMV see Appendix A Updating of this variable is part of control of network interface operating modes Configuration mode 10 or 11 and of exchange of application data between the CPU and the network Configuration mode 10 only Diagnostics concerning the CPU are made possible by the status of the following input bits Address Meaning Context I1 to I16 Inputarea validity bits Exchange of application data between CPU and network Configuration mode 11 only 117 Bus arbiter BA active if I17 is set to 1 Control of bus arbiter Configuration mode 11only 125 Network active if I25 is set to 0 Control of network interfaceoperating modes Configuration modes 10 and 11 126 Noredundancy error if I26 is set to 0 Control of network interfaceoperating modes Configurationmodes10and11 5 1 Appendix _ Descriptionof COMVs A This appendix contains detailed description of the COMVs used in the various functions of the FIP Bus Controller FBC Command COMV The Command COMV Configuration mode 10 only contains the transition necessary for changing operating modes idle ready running lock ed or running unlock ed The FIP identifier of the Command COMV is 0100
22. d the external configuration have been installed The module remains in or returns to this state until the CPU module has run a scan STOP state In this mode if the configuration requests it the Statfbc COMV is produced running The FBC is in this mode while the CPU is scanning RUN state In this mode if the configuration requires the Statfbc COMV is produced The following figure shows the changes in network interface operating modes running mode 11 power on reconfiguration configuration stop run Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Application Data Exchange between the CPU and Network Mode 11 The exchange of application data between the CPU and the network depends entirely on the network interface operating mode Network interface gt Modeni operating mode Exchange of COMVs consumed application data COMVs produced on the network between the CPU on the network and the network Output areas updated p gt Input areas by the CPU read by the CPU Data Exchange Depending on the operating mode the following operations are run on application data idle No application COMV is either produced or consumed ready No application COMV is refreshed The application COMVs configured to be consumed by the device are processed in the same way as in running mode running The application COMVs produced are representative of output data updat
23. ded Chapter 4 Configuration and Operating Modes 4 13 Characteristics and Performance Configuration mode 11 has the following main characteristics and performance m The FIP configuration is as follows number of media 1 or 2 transmit rate 1 Mbit sec Tslot configurable to 62 ns 250 ns 625 ns 2500 ns return time 42 nsec slowFIP 10 nsec FIP WorldFIP silence time out 240 nsec slowFIP 100 nsec FIP WorldFIP physical layer protocol slowFIP FIP NFC WorldFIP IEC All produced COMVs contain the FIP status byte which indicates refreshment All consumed COMVs must be sent by their producer with the FIP status byte containing the refresh indication m Total number of application COMVs 1 to 32 1 to 9 if configured by the HHP m Total number of TVAs per application COMV 1 to 125 1 to 3 if configured by the HHP m Total number of TVAs 1 to 1000 m Maximum size of data exchanged between the FBC module and the PLC 16 input areas each containing 1 to 255 bytes 16 output areas each containing 1 to 255 bytes m Duration of elementary operations read of a consumed COMV lt 1 msec write of a produced COMV including Statfbc lt 1 msec detection of loss of a medium lt 3 msec m dynamic characteristics of CPU interface module access time read command write command by PLC sweep not including application data
24. des Application Data Exchange between the CPU and Network Mode 11 Control of Bus Arbiter Characteristics and Performance Appendix B gives two examples common to Configuration modes 10 and 11 Configuration Mode 10 Control of Network Interface Operating Modes In Mode 10 the FIP Bus Controller FBC is a slave module The operating modes of its network interface are linked to the contents of the Command and Config COMVs consumed by the Bus Controller on the FIP network The FBC software periodically produces the Statfbc COMV which indicates to the other devices the current operating mode of its network interface Mode 10 Statfbc COMV Command COMV produced on consumed on the networK Control of network the network Config COMV interface consumed on the network OPerating modes Command COMV In Mode 10 the Command COMV is received periodically by the network Its transmitter must only refresh its contents when the current network interface operating mode is changed That is the only time the command is acknowledged by the FBC software The FIP identifier of the Command COMV is 0100 hexadecimal subscriber number The Command COMV contains two bytes specific to it plus a refresh byte See Appendix A for further information Config COMV The FIP identifier of the Config COMV is 0200 hexadecimal subscriber number The Config COMV contains 124 bytes specific to it plus a ref
25. e key to select the next parameter the COMV identifier Enter the COMV number between 0 and FFFF and press to validate Press the key and enter the COMV length between 1 and 125 bytes Press to validate Press the key to select the next parameter either the refresh period if the COMV is produced or the promptness period if the COMV is consumed Enter the factor of this period between 1 and 65535 times 0 1 msec and press to validate For produced COMV s press the key to select the COMV priority The default priority is 1 top priority If this is appropriate press the key to go directly to building the COMV Otherwise press the key to display the other priorities 2 Ua 4 and to validate The next step in configuration is the building of the COMV defined as described above Chapter 3 Hand held Programmer Configuration 3 13 3 14 Example Proceed as follows to configure a produced COMV with identifier 80A5 hexadecimal length 48 bytes refresh period 250 msec and top priority 1 Key Strokes gt iz JORGE B J JE gt eJ AE gt Display R0 05 FBC COMV 1 EMPTY R0 05 FBC COMV 1 PROD R0 05 FBC COMV 1 ID 0000H R0 05 FBC COMV 1 ID 80A5H R0 05 FBC lt S COMV 1 LEN 1 R0 05 FBC lt S COMV 1 LEN 48 R0 05 FBC lt S COMV 1 PER 0 R0 05 FBC lt S CO
26. ed by the CPU module The application COMVs configured to be consumed by the device are read by the FBC module Rank n associated with each I validity bit corresponds to the rank of each input area The lI validity bits associated with unused areas are set to 0 A I validity bit is declared valid when all input data TVAs making up the associated input area is valid that is when the status bits refresh and promptness associated with the COMVs that own these TVAs are valid In this case the input data is provided for the CPU in the input areas l validity bits COMV OK a l 0 valid ooo TVA No 1 T AREA COMV OK TVANo 1 TVANo 3 q COMV OK TVA No 3 GFK 1213 Chapter 4 Configuration and Operating Modes 4 11 Series 90 30 FIP Bus Controller User s Manual March 1996 A I validity bit is declared invalid whenever one of the input data items TVA making up the associated input area is invalid that is when the status bits refresh or promptness associated with the COMV which owns the TVA are invalid In this case the input area including this data is provided for the CPU with the configured fall back values 0 or frozen Dialog occurs cyclically as follows The following operations are executed in order of decreasing priority 1 dialog with the CPU module 2 read of COMVs as of reception 3 write of COMVs depe
27. errupted or the bus arbiter shut down while the operating mode was running lock ed or running unlock ed running lock ed The FBC is in the running lock ed mode after it has received a start up command via the Command COMV If network service is interrupted or the bus arbiter shut down while in this mode the FBC automatically goes to ready mode running unlock ed The FBC is in running unlock ed mode after it receives a debug command via the Command COMV If network service is interrupted or the bus arbiter shut down while in this mode the FBC automatically goes to ready mode GFK 1213 Chapter 4 Configuration and Operating Modes 4 3 Implementation for Mode 10 The Config COMV indicates to the module which COMVs it must produce or consume This COMV is only read and acknowledged when it has received a configuration order via the Command COMV while the current Configuration mode is idle It is therefore pointless to refresh the Config COMV in other cases Proceed as follows to be sure the Config and Command COMVs are correctly refreshed when there is a configuration command Build the Config and Command COMVs the Command COMV contains a configuration order both bytes equal 0 Refresh the Config COMV Wait until the Config COMV identifier has passed Refresh the Command COMV Refresh the Config COMV If after a period of time equal to 200 msec the Statfbc COMV period the operating mode indicated in this COMV
28. ess the 4 Kbytes exchanged between the FBC module and the CPU Under these conditions a measurement over 100 seconds shows the following characteristics m 5295 internal sweeps each producing the 16 COMVs Statfbc an application COMV is therefore produced on average every 1 2 msec m 41345 COMV reads A COMV is therefore consumed on average every 2 4 msec m The FBC module therefore processed over 1300 COMVs per second m The average module access time is 2 msec Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 A Active mode in mode 11 B Bus connectors Bus Arbiter Control in mode 11 Bus Arbuter version in mode 11 B 9 Bus Connectors 1 2 Bus Controller description number in system C Catalog Number Characteristics in mode 10 in mode 11 4 14 Command COMV A 1 In mode 10 Communication protocol b 4 Compatibility COMVs Command COMV Command COMV in mode 10 12 Config COMV A 2 Config COMV in mode 10 4 2 configuration in mode 11 3 13 total number in mode 11 Config COMV In mode 10 saa nion instructions for using HHP 3 1 Configuration mode Statfbc COMV in mode na 4 14 D Data exchange in mode 10 Data maximum in mode 11 Index Diagnostics 5 1 E Environmental specifications Error Messages Examples External Configuration version in mode F Field Control 1 1 Firmware upgrading G Generic devices
29. he PLC is now in STOP mode 3 2 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 FIP Bus Controller FBC Slot Number In the Program Data screen select module configuration by pressing the key then the key Press the key to call the configuration corresponding to the FIP Bus Controller FBC rack and slot m If the FIP Bus Controller FBC is already configured it appears in the slot For example R0 05 FBC lt S I32 10033 10064 The top line indicates the baseplate RO and the slot 05 selected The bottom line shows the I memory addresses attributed to the status bits When you press the key the Hand Held Programmer HHP displays R0 05 FBC lt S USING MODE 10 m If the module is present in the slot and the rack without being configured it does not appear on the screen The HHP indicates that the slot is empty EMPTY RO 05 EMPTY lt S READ EN Press the key then the key GFK 1213 Chapter 3 Hand held Programmer Configuration 3 3 l PLC Memory Addresses Selection of I addresses is the first operation to carry out Just choose the location of the first I and press In Configuration mode 10 the I bits represent the COMV validity bits and the status bits In Configuration mode 11 they represent the input area validity bits and the status bits Example The module is not yet part of the configuration stored by the PLC It is inserted in slot 5 You wish t
30. hexadecimal subscriber number The Command COMV contains two bytes specific to it described below plus a refresh byte m st byte coded command hexadecimal 00 configuration 01 deconfiguration 02 run Running lock ed 03 stop 04 adjust Running unlock ed m 2nd byte reserved contains 0 GFK 1213 A 1 Config COMV The FIP identifier of the Config COMV is 0200 hexadecimal subscriber number The Config COMV using mode 10 only contains 124 bytes specific to it described below plus a refresh byte Word Description 1 Configurationversion number 1 to FFFF in hexadecimal Thisnumberis placed in the Statfbc COMV 2 Reserved 3 Refresh frequency of the StatfbcCOMV factor of 0 to FFFF in hexadecimal times 0 1 msec 4 Reserved 5 Promptness frequency of the Command COMV factor of 0 to FFFF in hexadeci mal times 0 1 msec 6 Reserved 7 Promptness frequency of the Config COMV factor of 0 to FFFF in hexadecimal times 0 1 msec 8 to 19 Frequency of application COMVs each group contains 6groupsof2 1stword transmission frequency if the COMV is produced factor of 0 to FFFF words in hexadecimal times0 1 msec 2nd word refresh frequency if the COMV is produce or promptness frequency if the COMV is consumed factor of 0 to FFFF in hexadecimal times0 1 msec 20 to 61 Configuration of application COMVs Each group contains the following 12 groups of7 The 1st byte includes
31. ice are not read and the validity bits corresponding to these COMVs are set to 1 The others are set to 0 Furthermore m when the module is in this operating mode following a configuration or shutdown command the RI input area or other type used to store the data from the FIP bus is set to 0 m when this operating mode is due to an interruption of network service or bus arbiter shutdown the RI input area is either set to 0 or frozen no value change depending on the configuration received in the Config COMV running lock ed In this mode the COMVs produced are built from the RQ output area or other type when the application is active If the application is stopped the COMVs produced are no longer refreshed for consumers of these COMVs the FIP status bytes will become invalid In this mode the COMVs configured to be consumed by the device are read each time a valid COMV is read the corresponding RI input area or other type is GFK 1213 Chapter 4 Configuration and Operating Modes 4 5 updated based on the contents of the COMV and its configuration as well as the corresponding lI validity bit set to 0 Each time an invalid COMV is read the corresponding RI input area is frozen or set to 0 depending on its configuration as well as the corresponding lI validity bit set to 1 The I validity bits which do not correspond to consumed COMVs are set to 0 Dialog occurs cyclically as follows The following operat
32. ime between passage of the Command COMV containing a configuration order and refreshment of the Statfbc COMV after passing to the ready operating mode 200 msec m Total number of application COMVs 1 to 12 Number of application COMVs consumed 0 to 12 Number of application COMVs produced 0 to 12 m Number of R exchanges between the FBC and the C80 35 PLC 0 to 127 in each direction Number of K transported in an application COMV 0 to 62 m Duration of elementary operations read of consumed COMV lt 1 msec write of produced COMV including Statfbc lt 1 msec detection of loss of medium lt 3 msec m dynamic characteristics of interface with the CPU access time to module read command write command per PLC sweep application data transfer time not included v 5 msec exchange_time time_if_error exchange_time 1 msec n_bytes total number of bytes exchanged with the CPU module time_if_error 10 nsec n_TVA This only occurs if there is a loss of medium n_TVA total number of TVAs making up consumed COMVs or a refresh error of a consumed COMV n_TVA number of TVA making up the COMV in question transmit rate of I O buses used in dialog with the CPU CPU 331 23 nsec per word GFK 1213 Chapter 4 Configuration and Operating Modes 4 7 CPU 341 20 nsec per word CPU 351 18 nsec per word m dynamic characteristics of the network interface m acknow
33. indicates the current network operating mode to the other devices Mode 11 Control of network interface CPU module gt operating Statfbc COMV produced operating mode modes on the network as per configuration Operating Mode Once configured the FBC module adopts its operating mode as per the CPU module Statfbc COMV If the configuration requires it the Statfoc COMV is sent periodically by the FBC software when it has received and acknowledged the configuration provided by the PLC The FIP identifier of the Statfbc COMV is configurable as is the refresh period The Statfbc COMV contains 8 bytes which are specific to it plus a byte indicating refreshment See Appendix A for further information GFK 1213 Chapter 4 Configuration and Operating Modes 4 9 4 10 FIP Bus Controller FBC Network Interface Operating Modes Mode 11 The FBC has the following network interface operating modes idle The FBC is in this mode after power is applied as soon as the internal initializations are complete but the configuration generated by the Hand Held Programmer or the programmer the bus arbiter and the external configuration have not yet been installed The module returns to this state after a new configuration received in ready mode In this mode no COMVs are produced or consumed ready The FBC is in this mode once the configuration generated by the HHP or the programmer the bus arbiter an
34. ions are executed in order of decreasing priority 1 dialog with the CPU module 2 read of COMVs as of reception 3 write of COMVs depending on their frequency In addition the FBC module tests the media with a frequency less than the shortest refresh and promptness period running unlock ed COMVs are produced and consumed similarly to the running lock ed operating mode except that when an invalid COMV is read the corresponding RI input area has to be frozen Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Characteristics and Performance of Mode 10 The main characteristics of Configuration mode 10 are as follows m The FIP configuration is as follows number of media 1 or 2 transmit rate 1 Mbit sec Tslot configurable to 62 nsec 250 msec 625 msec 2500 nsec return time 42 nsec slowFIP 10 msec FIP WorldFIP silence time out 240 nsec slowFIP 100 nsec FIP WorldFIP physical layer protocol slowFIP FIP NFC WorldFIP IEC All produced COMVs contain the FIP status byte which indicates refreshment All consumed COMVs must be sent by their producer with the FIP status byte containing the refreshment indication m Maximum time between passage of the Command COMV identifier different from a configuration order which changes the operating mode and refreshment of the Statfbc COMV which indicates the new mode 20 msec Maximum t
35. is not ready then the configuration is wrong it is assumed that the module s operating mode was idle that network service was not interrupted etc Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Exchange of Application Data Between the CPU and the Network Mode 10 Exchange of application data between the CPU and the network is completely dependent on the network interface operating mode Mode 10 Network interface operating mode Exchange of COMVs consumed _ p application data COMVs produced on the network between CPU on the network RQ output area p and network Rl input area ys updated by CPU read by the CPU Exchange of application data The following operations are executed for application data depending on the network interface operating mode idle In this mode only the Statfbc COMV is sent only the Command COMV and if necessary the Config COMV are consumed Application COMVs are neither sent nor received The entire RI input area or other type is initialized to 0 and the 16 I validity bits are initialized to 1 ready In this mode the COMVs produced are built from the 9oRO output area or other type when the application is active If the application stops the COMVs produced are no longer refreshed for the consumers of these COMVs the FIP status bytes will become invalid In this mode the COMVs configured to be consumed by the dev
36. its data on the FIP bus attached to that channel The intensity of this LED indicates the level of transmission activity in the bus A dimly lit Transmit Enable LED indicates low activity a brightly lit Transmit En able LED indicates high activity GFK 1213 2 4 Series 90 30 FIP Bus Controller User s Manual March 1996 Status Indications of the MODULE OK and RUN LEDs Status Meaning MODULE OK on The FBC module is correctly configured in the CPU RUN on The module does not exist in the CPU configuration MODULE OK on or RUN off The CPU configuration is incorrect or Configuration by the HHP is under way MODULE OK on The FBC module is waiting for configuration or an external RUN blinking slowly bus arbiter either because they have not been sent or because one or both are incorrect MODULE OK on The FBC module is loading a configuration or an external RUN blinking rapidly bus arbiter MODULE OK blinking Memory tests are under way RUN off MODULE OK The firmware checksum is incorrect and RUN or blinking together The firmware is being loaded MODULE OK Fatal error error in FULLFIP configuration or insufficient and RUN memory blinking alternately Upgrading the Bus Controller Firmware To upgrade the Bus Controller firmware connect the loading computer PC with the new firmware to the 15 pin serial port on the front of the Bus Controller From the loading PC invoke the Loading
37. l purpose computers that are interfaced to the bus via a FIP Interface Module m Variable speed drives 1 1 FIP Bus Controller Description The FIP Bus Controller is a standard rack mounted Series 90 30 PLC module It plugs easily into the PLC s backplane The latch on the bottom of the module secures it in position a46560 Module OK Run Carrier Detect Ch 1 gt O Transmit Enable Ch 1 Carrier Detect Ch 2 Transmit Enable Ch 2 7 15 Pin Serial Connector RS 485 gt O O 9 Pin FIP Fieldbus Connector channel 1 O O 9 Pin FIP Fieldbus Connector gt channel 2 O There are no DIP switches or jumpers to set on the module The Series 90 30 FIP Bus Controller has six status LEDs an RS 485 serial port and two identical FIP bus connectors Status LEDs The 6 LEDs on the front of the FIP Bus Controller display module status and commu nications activity Serial Port The 15 pin serial port is used to connect a programmer or computer for upgrading the operating firmware of the Bus Controller FIP Bus Connectors The two 9 pin connectors on the FIP Bus Controller provide for attachment of one or two FIP busses The two busses provide a redundant bus capability Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Module Specifications Compatibility GFK 1213 Ordering information Moduletype Qua
38. ledgment time of an avalanche of N consumed COMVs N COMVs transmitted successively at network maximum speed v 3 msec 1 msec N exchange_time time_if_error it is assumed that there is no more than one PLC sweep during the avalanche m maximum time to refresh a COMV after writing by the CPU depends on the priority P attributed during configuration a COMV is sent every P internal sweeps the maximum sweep time is 5 msec 1 msec n_COMV exchange_time time_if_error where n_COMV is the total number of COMVs consumed and produced during this sweep 1 if the configuration requests production of the Statfbc COMV one assumes there has been at most one exchange with the CPU during the sweep It should be noted that the FBC module automatically generates internally the priority of produced COMVs in order to determine the configuration transmission freguency Appendix B includes two examples common to Configuration modes 10 and 11 4 8 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Configuration Mode 11 Control of Network Interface Operating Modes In Mode 11 the FIP Bus Controller FBC is a self governing module The operating modes of its network interface are automatically controlled by the FBC module itself They also depend on the configuration the FBC has received from the PLC after initialization If the configuration so specifies the Statfbc COMV is produced periodically This
39. lling or removing the module To install the Bus Controller in the Series 90 30 PLC backplate 1 Grasp the module with the terminal board toward you and the rear hook facing away from you Align the module with the desired base slot and connector Tilt the module upward so that the top rear hook on the module engages the slot on the baseplate Swing the module downward until the connectors mate and the locking lever on the bottom of the module snaps into place engaging the baseplate notch a43055 Module Removal Locate the release lever on the bottom of the module Firmly press it up toward the module While holding the module firmly at the top continue fully depressing the release lever and swing the module upward Disengage the hook at the top of the module by raising the module up and moving it away from the baseplate a43056 4 PRESS Masel RELEASELEVER 2 2 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Connecting the FIP Bus to the Bus Controller Attach FIP bus cable s to the connectors on the front of the Bus Controller When installed in a single media or simplex configuration either connector may be used When installed in a dual media or redundant configuration both the Channel 1 and 2 connectors must be used Both connectors accept a standard 9 pin D type male connec tor a46567 O O O Connector for ch
40. mber between 0 and 255 and press to validate The next parameter to select is the medium number Press the key By default the network is simplex single medium If this is appropriate press the key to go directly to the next parameter Otherwise press the key to choose a redundant dual medium network then J to validate Example Proceed as follows to choose FIP subscriber number 3 and a dual medium architecture Key Strokes Display R0 05 FBC lt S SUBSCRIBER 0 3 15 R0 05 FBC lt S SUBSCRIBER 3 R0 05 FBC lt S LJ MEDIUM MONO 4 ST R0 05 FBC lt S MEDIUM BI GFK 1213 Chapter 3 Hand held Programmer Configuration 3 7 Maximum Time Between Two CPU Module Input Scans Press the key to select the maximum cycle time Enter the time factor between 1 and 255 times 100 msec and press to validate Example For a FIP Bus Controller FBC associated with a CPU module that has a sweep time of less than second enter the following Key Strokes Display RO 05 FBC lt S MAX TIME 1 1 0 Ei R0 05 FBC lt S MAX TIME 10 3 8 Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Bus Arbiter and External Configuration Version Numbers Mode 11 Only Press the key to select the bus arbiter version number The default version number is 0 which means the FBC module is not the bus arbiter you can simply load the B
41. mit rate in mode 10 4 7 in mode 11 Tslot configuration in mode 10 4 7 configuration characteristics in mode 11 TVAs number of in mode 11 V Vibration GFK 1213
42. nding on their priority level 1 to 4 In addition the FBC module tests the media with a frequency less than the shortest refresh and promptness period GFK 1213 GFK 1213 Control of Bus Arbiter The FBC module may be the bus arbiter depending on whether or not it has a version of the bus arbiter and whether or not the network bus arbiter is active R Bus Version of bus arbiter Status of bus p i program in FBC ah arbiter in FBC Network rbiter active or not Bus Arbiter Control The bus arbiter has the following operating modes Init The FBC module has no bus arbiter whose version number corresponds to the BA conf parameter The bus arbiter is absent or unusable Standby The FBC module has a bus arbiter whose version number corresponds to the BA conf parameter The bus arbiter is ready and waiting to be chosen Active The FBC module has a bus arbiter whose version number corresponds to the BA conf parameter The bus arbiter is active power on STANDBY 3 Transitions between operating modes are 1 Abus arbiter has just been loaded with a correct version number but another bus arbiter is active 2 Abus arbiter has just been loaded with a correct version number and no other bus arbiter is active 3 The FBC module detects that the previous bus arbiter has stopped and therefore activates its bus arbiter 4 Anew bus arbiter or a new configuration is being loa
43. ntity per PLC Currentconsumption FIP data Softwarediagnostics Environmental Operating temperature Storage temperature Humidity Vibration and shock Series 90 30 PLC memory types for IC693BEM340 Series 90 30 PLC module providing FIP communications with other devices As power supply willallow 1 2Ampsmaximum 800mA typical G 901 Q 96AI WAQ R 96M T Status bits Fault Reporting to Series 90 30 PLC 0 C to 55 C 4 32 F to 131 F 25 C to 70 C 139F to 158 F 5 to 95 non condensing 0 2 inch displacement 5Hz to 10Hz 1G10Hz to 200Hz 5G10Ms duration Minimum hardware configuration m Series 90 30 PLC baseplate m Power supply CPU Specific equipment or software versions required for compatibility with the FIP Bus Controller module are listed below CPU The FIP Bus Controller can be used with all CPU models 311 351 The CPU firmware must be rel 5 0 or later Control 90 Software rel 1 5 or later Chapter 1 Introduction 1 3 Chapter Installation GFK 1213 2 This chapter describes m Module Installation m Module Removal m Connecting the FIP Bus to the Bus Controller m Observing the LEDs m Upgrading the Bus Controller Firmware Module Installation The FIP Bus Controller module can be located in any I O slot in a Series 90 30 CPU rack or I O rack including remote racks For best performance the main rack is required Power must be OFF when insta
44. o locate the 9ol bits as of 9oll After switching to configuration mode and selecting the right location press these keys Key Strokes Display RO 05 EMPTY lt S RO 05 FBC lt S SREY I32 I R0 05 FBC lt S 132 10001 0032 This example gives the following configuration for Configuration mode 10 I1 will be the validity bit of the first COMV defined in the COMV config which only makes sense if the configured COMV is consumed 12 will be the validity bit of the second COMV etc 125 will be the bit indicating whether the network is active 0 OK 126 will be the bit indicating whether there is a redundancy fault 0 OK m for Configuration mode 11 I1 will be the validity bit of the first configured input area 12 will be the validity bit of the second input area etc 125 will be the bit indicating whether the network is active 0 OK 126 will be the bit indicating whether there is a redundancy fault 0 OK Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 Configuration Mode Press the key to be able to set the Configuration mode parameter The default Configuration mode is mode 10 If this mode has been selected press the key to go directly to the next parameter To choose Configuration mode 11 press the key to display the other Configuration modes Then press the key to validate Example for mode 11 Key Strokes Display R0 05 FBC lt S USING MODE
45. of each of the 16 input areas updated based on COMV s consumed by the module Size and addresses in PLC memory R of the output area RQ used to build the COMV s produced by the module Size and addresses in PLC memory of each of the 16 output areas used to build the COMV s produced by the module Notapplicable Configuration of COMV 9 maximum type of COMV absent produced or consumed COMV identifier refresh or promptness period associated with the COMV constitution of the COMY including for each TVA 3 max type of TVA length of TVA position of TVA number of area containing TVA o _ offsetin area from which TVA is stored 0000 Notapplicable Configuration of COMV Statfbc m presence of COMV absent or produced COMV identifier m refresh period associated with the COMV Configuration data is stored in the PLC The configuration is static It cannot be changed while the PLC is operating GFK 1213 3 1 Setting the PLC to Stop Mode If necessary press the key of the Hand Held Programmer HHP to set the PLC PRESS lt gt KEY lt R to STOP mode The lt Rcharacters in the top right indicate that the PLC is in RUN mode Press the key RUN MODE lt R Press the key again to change mode STOP MODE lt R Press the B key The HHP screen displays 1 PROGRAM lt S 2 DATA The lt S characters in the top right indicate that t
46. propriate configuration is over Otherwise press the key to display yes Then press to validate Press the key to select the identifier Enter the number of the Statfbc COMV 0 to FFFF and press to validate Press the key to select the next parameter the refresh period refr refresh Enter the factor for the period 1 to 65535 times 0 1 msec and press to validate Example To configure the produced Statfbc COMV with identifier 0030 hexadecimal and refresh period 500 msec Key Strokes Display R0 05 FBC lt S STATFBC PROD NO P D RO 05 FBC lt S STATFBC PROD YES gt R0 05 FBC lt S lt STATFBC ID 0000H R0 05 FBC lt S STATFBC ID 0030H R0 05 FBC lt S STATFBC REFR 0 Lo e o JUS o ej 2 Lo ENT 37 oi R0 05 FBC lt S STATFBC REFR 5000 Chapter 3 Hand held Programmer Configuration 3 19 Validation of Configuration Note The module must be reconfigured every time the PLC is reconfigured To validate the HHP configuration display the Configuration mode press the Key to display the GO message and press to validate The GO message flashes during configuration then the selected Configuration mode mode 10 or mode 11 is displayed Example Mode 10 Key Strokes Display RO 05 FBC lt S USING MODE 10 T T a RO 05 FBC
47. resh byte See Appendix A for further information Statfbc COMV The Statfbc COMV is periodically transmitted by the FBC software when it has received and acknowledged the configuration provided by the PLC The FIP identifier of the Statfbc COMV is 0000 hexadecimal subscriber number The Statfbc COMV contains 8 bytes which are specific to it plus a refresh byte See Appendix A for further information Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213 FIP Bus Controller FBC Network Interface Operating Modes in Mode 10 The following diagram shows changes in the FIP Bus Controller FBC network interface operating modes in Configuration mode 10 i power on deconfiguration mn reconfiguration debug run shutdown network interruption RUNNING mf debug RUNNING UNLOCKED LOCKED run The FBC network interface operating modes are idle The FBC is in dle mode after power is applied and it has received the configuration from the PLC or after it has received a configuration change command received in ready mode In this mode only the Statfbc COMV is transmitted The only COMVs consumed are the Command COMV and if necessary the Config COMV ready The FBC is in ready mode after it has received a configuration command via the Command COMV and has consumed the Config COMV containing valid information The module automatically adopts this mode when network service is int
48. tics GFK 1213 91650 internal sweeps producing each time the 2 COMVs Statfbc an application COMV is therefore produced on average every 550 mec 146232 COMV reads a COMV is therefore consumed on average every 700 nsec The FBC module has processed on average over 4200 COMVs per second The average application sweep time all sweep components included is 10 msec The average module access time is 2 msec Example 2 In this example a very large amount of data is exchanged between the FBC and the CPU over the FIP bus The configuration is as follows m 16 consumed COMVs of 125 bytes each including 31 2 byte TVAs the format selected is numerical implying return of bytes m 16 produced COMVs of 125 priority 1 bytes highest possible rate each including 31 2 byte TVAs in numerical format plus the Statfbc COMV m The total is 992 TVAs m The refresh and promptness frequencies of the COMVs are each 100 msec Network validity must be tested in the worst case every 100 msec m The bus arbiter program provides transport of the 33 COMVs only at maximum rate no BA_WAIT over the FIP bus m The FBC module and the CPU exchange 2 Kbytes in each direction m The application program defined for a 331 CPU is the same as previously In this environment the PLC sweep time is approximately 70 msec For the experiment to be conclusive the sweep time is forced to 100 msec i e only 30 msec is considered enough time to proc
49. ytes for numerical variables Press to validate Press the key to select TVA position in COMV Enter the position pos between 0 and 124 bytes then press to validate Press the key to go to the next parameter area selection of the input area for a consumed COMV or the output area for a produced COMV Enter the area number between 1 and 16 and press to validate Press the key to select TVA position in the area offset Enter the offset off between 0 and 254 bytes for Boolean variables or an even value between 0 and 252 bytes for numerical variables Press to validate GFK 1213 Chapter 3 Hand held Programmer Configuration 3 15 Building a COMV mode 11 only The next step in configuration is definition of the next TVA for the current COMV or when all TVAs of the current COMV have been defined definition of the next COMV COMV type etc or when all COMV s have been defined by definition of the Statfbc COMV Example To complete the configuration steps of produced COMV as described above and have the following results m 1 TVA 8 Boolean bytes from area 12 starting with offset 8 will be stored at COMV position 0 m 2nd TVA 16 numerical bytes from area 14 starting with offset 24 will be stored at COMV position 16 AREA 12 1 a 8 bytes o 1st TVA COMV 0 2nd TVA 16 AREA 14 0 24 16 bytes Series 90 30 FIP Bus Controller User s Manual March 1996 GFK 1213
Download Pdf Manuals
Related Search