Home

3100/3150-ROC User Manual

1. The opcode entered in the table tells the ROC Module what command to execute The different choices are detailed in Section 6 but in an overview they are as follows Opcode Description 8 Set New Time and Date 10 Send Data From Configurable Opcode Tables 120 Send Pointers for Alarm Event and History Logs 128 Send Archived Daily and Hourly Data for the Currently Selected Day and Month 130 Send Archived Hourly and Daily Data for Specified History Point Starting at Specified History Pointer 180 Send Specified Parameters 181 Set Specified Parameters For commands 8 10 120 128 and 130 count is the number of bytes the Fisher ROC command is to read or write For commands 180 and 181 count represents the number of data points See Section 6 for a detailed discussion on the byte lengths to be specified for the different commands Source Address The value represents the register addresses for both read and write commands from which data will be obtained When issuing a command the Source Register Address is the register location in the module where the command will begin getting the command parameters to send to the slave The parameters need to start at this address and be placed in sequential words Destination Address The value represents the register addresses for read commands to which the data received will be written When issuing a command the Destination Address is the register location in the module where the co
2. 5 2 Chapter 5 Heading from the Module Linde Name ccce ed Incomplete Response This error indicates that an incomplete response Detected was received to a master query Often this will indicate that the slave device may be responding too quickly or that there may be excessive noise on the line Module Busy The module busy status code is returned when a write command from the master has not yet been completed when a second write command is received Timeout Error Communications with the addressed slave have been unsuccessful due to a lack of response from the slave The Master port will attempt a command three times before moving onto the next command Buffer Overflow The receive buffer has overflowed and reset the character count to O If this condition occurs try reading fewer parameters at one time Port Configuration If this value is returned from the module one or Error both of the serial ports have been misconfigured To determine the exact source of the problem verify the following Parity Configuration Stop Bit Configuration Baud Rate Configuration Start Input Register Address Start Output Register Address System Configuration If this error is returned from the module one of the system configuration parameters has been detected out of range To determine the source verify the following Read Block Count lt 80 Write Block Count 80 Command Block Count lt 20 Slave Error Pointer lt 3850
3. Yi Block Block Block Via the data transfer sequence outlined in the next section 50 word blocks of data or pages are transferred bi directionally between the module and the PLC SLC processor BTR Buffer BTR Block ID BTW Block ID 50 words of data BTW Buffer BTW Block ID 50 words of data The placement of data in the PLC SLC processor is controlled by the user and the application ladder logic Any available data file in the processor can be used as a source of data for the module and as a destination for data from the module EQU SRC A N7 410 SCR B 4 COP SRC N7 412 DEST N10 200 COUNT 50 The following table provides an overview of the data transfer process between the A B processor and the module This process is effectively controlled by the ladder logic in the processor The following provides some insight into the steps which occur in the module and in the ladder to effect a successful data transfer Reference can be made to the example logic in the Appendix to see an actual implementation Stop Number Step 1 Module generates BTR and BTW Block ID numbers based on the following logic BTW Block ID if BTW Block ID gt Write Block Cnt then BTW Block ID 80 elseif BTW Block ID gt 80 Command Block Cnt then BTW Block ID Write Block Start else BTW block ID BTW block ID 1 BTR Block ID if BTR Block ID gt
4. eene 5 1 The Read Data Block Structure sus sn am 5 1 2 Moving the data from the module to the processor 5 1 3 Ladder Logic to Read Module Data ie st STA Slave Error Code Table ue teca ete eet cana p e OR e austen tae 5 15 Master Brror Code Table eie etie eee ires 5 1 6 Error Status Codes um 52 Decoding Command Done and Command Error Bits Master Mode 52 The Block Structure 5 222 Ladder Logic as iR a 6 Fisher ROC Command Configuration sss eese netten nenne tenente nente te tenente ene 6 1 Fisher ROC Commands nete Ee eee e d n Bede lee 6 1 1 Opcode 180 and 181 Examples 6 1 2 Point Type Support 62 Floating Point Support i e T 63 Store And FOrWAtd eee A IAV X MESE TNR conceusarcacsosutuebecs eee ee Def que 7 Diagnostics and Troubleshooting esses essen entere tnnt tnnt tn tnnt ntn tene tn tete rtn tnnt teintes 7 1 3100 PLC Platform LED Indicators esee entente tenente tnnt tentent Table of Contents ui Bi OO tuo 7 2 3150 SLC Platform LED Indicators 13 Troubleshooting General Cable Connection Diagrams Support Service and Warranty Product Specifications e po Acetate te te seat e E EAE t e yis Jumper Configurations Product Revision History Read Write and Command Block Count Values usage Example Ladder Logic
5. Port 1 Interface Circutry 4 amp JM9 ROC Master RS 232 RS 422 RS 485 DUART 2comm channels Port 2 Interface Circutry 4 amp J9 ROC Master RS 232 RS 422 RS 485 Hardware layout diagram of 3100 3150 modules The primary functional components on the boards are A microcontroller responsible for the overall operation of the board including Backplane communications with Allen Bradley processor Transferring data from module to PLC Accepting data from PLC into the module Servicing DUART communications LED Status Indications An Allen Bradley backplane chipset responsible for servicing the communications between the module and the A B processor The chipset contains proprietary technology licensed from AB designed to Inthe case of the PLC the chipset has been designed to communicate with backplane using the Block Transfer commands transferring 64 words at a time Inthe case of the SLC the chipset has been designed to communicate with the backplane using the MO M1 files As there is no real Block Transfer functionality in the SLC we have implemented a form of block transfer using the I O table to control the handshaking between the module and the processor Up to 64 words may be transferred at a time Shown below presuming the module is in slot 1 are these bits 1 1 0 0 1 0 Transfer Enable This bit is set by the module and used by the ladder logic to enable the
6. Master Error Pointer lt 3880 Error Codes Returned The error code returned from the ROC slave will be From ROC Slave offset by 20 If an error of 2 is returned from the slave then the error will be stored in the module as 22 A transmit timeout condition has occurred indicating that the module was not able to transmit the command Verify that the RTS CTS jumper on the port is still connected Decoding Command Done and Command Error Bits Master Mode The Command Done and Command Error bits are returned for use in the ladder logic program during every data block transfer BTR Block ID 0 to 79 These bits can be used by the ladder logic to keep track of command execution or to disable commands when a command is configured in the Command Control Mode See Section 4 5 Chapter 5 Heading from the Module 5 2 1 The Block Structure The structure of the Done and Error bits as they are returned in the BTR Block Transfer buffer is as follows Word Name BTR Block ID When the BTR Block ID value is between 0 and 79 the BT Buffer contains Command Done and Command Error bits as outlined below BTW Block ID Same as above description poet rd Module data as outlined above Bud 57 MERE Done Bits These registers contain Done Bit flags for each command in the command list up to the first 96 commands The Done Bits are bit mapped into the words depending on their relative position in the Command List The mapping within the Don
7. 1 1 1 1 2 Chapter 1 Functional Overview Functional Overview This section is intended to give the reader an overview of the ROC module operating concepts Details associated with the ladder logic and the data transfer across the backplane is covered in later sections and in the Appendix General The ROC products are single slot rack resident modules which have been designed to provide a tightly integrated Fisher ROC communication interface for the Allen Bradley 1771 and 1746 I O platforms The product will support the following processors 3100 ROC for 1771 Platform PLC 5 family PLC 2 family PLC 3 family 3150 ROC for 1746 Platform SLC 5 02 5 03 5 04 5 05 The module will work in the local rack with the processor or can be installed in a remote rack using Remote I O communications to link the racks in the case of the PLC or can be placed in an extended rack in the case of the SLC The two forms in which the product is available are shown below 3100 Module 3150 Module 1771 Platform 1746 Platform Hardware Overview The design of the ROC module for the two hardware platforms is very similar The following discussion unless identified otherwise will apply to both the 3100 and the 3150 platforms The figure below shows the functional components on the modules Command BTW Command Transfer circuitry Board Processor 80C32 or 80C320 Chapter 1 Functional Overview Isolation Barrier
8. ERR1 2 ERR2 TXD1 TXD2 RXD1 s RXD2 GM Color status indication CIM Color Fast successfully Block Transferring with the PLC DA The module is receiving power from the backplane but f MEN there may be some other problem Of The module is attempting to Block Transfer with the PLC MEN B and has failed The PLC may be in the PGM mode or may be faulted OU D tesgsunddagesies EG background diagnostics _ dagnostis Please contact factor for echnical suppor diagnostics Please contact factory for technical support Normal state No configuration related activity is occurring Blink This light blinks every time a Module Configuration block 055s receives rom he processor ladder gic n Off Normal State When this light is off and the ACT light is blinking quickly the module is actively Block Transferring data with the PLC O The light is on continuously whenever a configuration error is detected The error could be in the Port Configuration data or in the System Configuration data See Section 4 for details On Indicates that Block Transfers between the PLC and the module have failed Not activated in the initial release of the product ERR1 Amber Off Normal State When the error LED is off and the related ERR2 port is actively transferring data there are no communication errors Blink Periodic communication errors are occurring during data communications See Section 4 to determine the
9. entered into the processor Data Table is transferred to the module s memory using BTW Block ID codes 80 99 with each code representing a 50 word block or 5 commands An example of the ladder logic to move the commands to the module is as follows COF SRC N10 150 DEST N7 311 COUNT 50 EQU SRC A N7 310 SCR B 81 COF SRC N10 150 DEST N7 311 COUNT 50 Transfer Command List These two branches located in the BTW rung Rung 1 move two Command List blocks into the module These blocks each contain 5 commands allowing the User to enter up to 10 commands in the module To add additional commands add branches as needed for 82 to 99 BIW Rack 0 Module 0 Group 0 Control N7 300 Data N7 310 Continuous N Length 64 Chapter 4 Writing to the Module 4 4 2 Command List Structure The structure of the block containing the Command List is shown in the diagram below Block ID 80 0 Port Mode Select 1 Slave Unit Command 2 5 Source Address Block ID 82 8 Polling Time Command s 9 Store And Forward Command ist Black of 10 words the information needed for Each Command List Block ROC to construct a command contains 5 commands 2 Slave Group 3 Opcode Block ID 81 command OREN 6 Destination Address Command 3 7 Type Command 5 Source Address Block ID Commands Individual Command Each of the 5 commands is made up
10. 400 Data N7 410 Continuous N Length 64 PLC version COP SRC N7 412 DEST N10 0 COUNT 50 COP SRC N7 412 DEST N10 50 COUNT 50 Example ladder to transfer data from module This logic shows a method for moving data from the module to the PLC data table 5 1 4 Slave Error Code Table The Slave Error Table contains the system information for the ROC module The Slave Error Code Table is initialized to zero on power up and every time the module receives the 255 configuration data block The Slave Error Table is a 20 word block The location of the Error Table is determined by the Slave Error Table Pointer parameter in the Configuration Block The structure of the data block is as follows Port 1 Status Codes wora aaae name Deseripion Word Addr Description 0 Ni0100 NotUsed LLL 1 N10101 NotUsed 2 N10102 NotUsed O 3 No NotUsd LL 4 Ni0104 NotUsed Port 2 Status Codes Example Word Addr Description NTO 105 Not Used ERR RN 6 Ni0306 NoUsed 7 Nor Nisa O O S i 5 a e e 1 CY 9 Ni0309 NotUsed SS Chapter 5 Heading from the Module System Information Example Word moet Description 0 110 Product Name ASCII These two words represent the product name of the um 111 module in an A
11. JW2 Settings ___DauotterBoad RS 232 XE Daughter Board RS 422 Daughter Board 4 wire og Daughter Board RS 485 an s 2 wire Appendix D Product Revision History D Product Revision History 03 08 00 Revision 1 00 1 Initial release of product 08 16 00 Revision 1 04 5 Incorporates changes from byte oriented data to word oriented data The type function was modified to specify stripping of TLP from data or storing raw TLP and data Integers and floating point numbers are automatically swapped in order to be stored correctly in the PLC Changed Store and Forward to use a pointer to the Communication Path header data Appendix E Block Count Value Usage E Read Write and Command Block Count Values usage As part of the configuration process the User is able to configure several parameters in the Communication Configuration Data Block which have a strong impact on how the module transfers data with the PLC SLC processor Overview As shown in Section 4 and 5 of the manual the BTR buffer contains the BTR and the BTW Block ID numbers The BTR Block ID is used to identify the data contents while the BTW Block ID is used by the ladder logic to determine which data to move to the module Diagrammatically the relationship is as follows BTR Buffer BTW Buffer BTW Block ID 50 words 50 words of data of data Configuration Parameters Three parameters which are important to the transfer of data a
12. Not Used Enabled Port 2 RS232 422 485 config Port 1 RS232 422 485 config JW4 Flash Pgm Run Mode Select Run Position The position of this jumper should only be changed if needing to reprogram the ROC FLASH memory This will only need to be done if the module is to be upgraded in the field to a later version of firmware JW5 Backplane 8 16 point 8 Point The module should be operated in the 8 point configuration unless specifically directed otherwise by the factory JW7 Battery Enable Disable Enabled This jumper should be placed in the Enabled position when the module is powered up Although not critical to the operation of the module this will back up some data registers in the module during a power failure or reset JW8 9 RS Configuration for Port 1 and 2 RS 232 422 485 The default from factory is RS 232 but all options are supported by the ROC firmware 3150 for the 1746 Platform Following are the jumper positions for the ProSoft Technology 3150 ROC module 3150 ROC As Needed As Needed N A N A JW1 2 RS configuration for port 1 and 2 RS 232 Position The default from factory is RS 232 but RS 422 and RS 485 are supported by the firmware and hardware See the following diagram Appendix C Jumper Configurations Jumper JW1 Settings ee bis RS 232 Daughter Board eat RS 422 4 wire Daughter Board Daughter Board TREES RS 485 Mother 2 wire Board Daughler Board Daughter w3 E Jumper
13. error condition On This LED will stay on under several conditions CTS input is not being satisfied Port Configuration Error System Configuration Error Unsuccessful comm on ROC slave Recurring error condition on ROC master The port is transmitting data Tx2 Rx2 7 2 7 3 Chapter 7 Diagnostics and Troubleshooting 3150 SLC Platform LED Indicators The following table documents the LEDs on the 3150 ROC hardware and explains the operation of the LEDs COMMUNICATIONS ACT FAULT CFG BPLN PRT1 ERR1 PRT2 ERR2 LED Name cotor status indication ACT Green Blink Normal state The module is operating normally and Fast successfully Block Transferring with the SLC On The module is receiving pow er from the backplane but gt ieremapbesomeotrpebem Off The module is attempting to Block Transfer with the SLC a and has failed The SLC may be in the PGM mode or may be faulted T begrunddagsies Pod background diagnostics On A system problem was detected during background __ dagnestis Please contact factory for technica suppor CFG Green Off Normal state No configuration related activity is occurring Blink This light blinks every time a Module Configuration block to sya tom tne processor acaer ge ia light is on continuously whenever a configuration error is detected The error could be in the Port Configuration data or in the System Configuration data See Section 4 fo
14. logic to send configuration command list and data to the module Transferring data from the module BTR Block ID 0 to 79 When the Master port driver reads data from a slave or when a Host writes to the Slave port driver the resulting data is placed into the ProSoft module s data space Addresses 0 to 3999 This Module Data space is the same block of memory that the PLC SLC can write into per the above discussion The transfer of data from the ProSoft Technology module to the processor is executed through the Block Transfer Read function The following sections detail the handling of the read data Although the full physical 64 words of the data buffer may not be used the BTR and M1 lengths must be configured for a length of 64 words otherwise module operation will be unpredictable The Read Data Block Structure The BTR buffer definition is Name Description Word BTR Block ID The ladder logic uses this value to determine the contents of the data portion of the BTR buffer With some conditional testing in ladder logic the data from the module can be placed into the PLC SLC data table BTR Buffer BTW Buffer al The relationship between the BTR Block ID number and the register table can be put into an equation Starting Register Address Block ID Number 50 Valid codes are between 0 and 79 BTW Block ID The module returns this value to the processor to be used to enable the movement of register data
15. point N10 3 N10 5 contain the TLP values for the second point Noe N07 NOS eee O O O For opcode 180 the received data will have the TLP stripped out and the data will be stored in the module database starting at address 50 DEST ADDR If type is setto 1 then the TLP will be stored with each data value This would take 3 words for the TLP and the data will be stored immediately following For opcode 181 the same TLP will be used as in the previous example because the SRC ADDR is also set to address 0 The data values to write to the ROC must be stored in the module database The data will be fetched starting from the address set by DEST ADDR In this example the starting address is 100 sw oo S O O O O O O O O O The data value of 500 will be written to the first data point and 1000 to the second 6 1 2 Point Type Support The point types supported by the Fisher ROC may contain mixed data types In the ROC module the point data is treated as an array of words Byte data will be placed in the Least Significant byte of a word Word data will be presented as words Floating point data will be presented as two consecutive words ROC Opcode 120 Example Byte 0 is at the destination address Byte 0 Byles INTO INTO zee ee Ale E eec Byte 10 Byte 18 INTO iN 0 BIND o BINO o femo e ere eae eee a aa Byte 20 Byte 21 Byte 22 Byte 23 Byte 24 Byte 25 Byte 26 Byte 27 Byte 28 Byte 29
16. used by the ProSoft module to determine what to do with the data block Valid codes are BTW Code Description 0 79 Module Data Memory 80 99 Command List 255 Module Communication Configuration 1 to 63 Data The data to be written to the module The structure of the data is dependent on the Block ID code The following sections provide details on the different structures Although the full physical 64 words of the data buffer may not be used the BTW and MO lengths must be configured for 64 words otherwise module operation will be unpredictable ROC BTW BlockID Memory Data i i Write Regs Registers 150 to 199 50 wrds blk Write Regs 80 blks total i j 200 to 249 ID 0 79 DOW Write Regs 250 to 299 Command List 10 wrds cmd i i Commands 5 cmds blk E r 1to5 20 blks total i i Commands ID 80 to 99 6 to 10 Configuration Configuration 40 words p 255 Data ID 255 Data transfer from PLC to ROC Data values and Command List entries are paged into the ROC module The data type and location being written into corresponds to the BTW Block ID number The BTW Block ID number is controlled by the ROC module as discussed later in this section 4 2 Chapter 4 Writing to the Module Communications Configuration BTW Block ID 255 The ProSoft Technology firmware communication parameters must be configured at least once when the card is first powered up and any time thereafter
17. when the parameters must be changed Power Up On power up the module enters into a logical loop waiting to receive configuration data from the processor While waiting the module sets the second word of the BTR buffer the BTW Block ID to 255 telling the processor that the module must be configured before anything else will be done The module will continuously perform block transfers until the communications configuration parameters block is received Upon receipt the module will begin execution of the command list if present or begin looking for the command list from the processor Changing parameters during operation Changing values in the configuration table can be done at any time The module does not accept any of the changes until the re configuration process is initiated This can be accomplished in several ways including 1 Cycle power to the rack 2 Pressthe reset pushbutton on the module 3100 only 3 Move 255 into BTW Block ID position See example logic when B3 0 is set During this process the CFG LED will toggle giving a visual indication that the module has received the configuration block Transferring the Communications Configuration Parameters to the module will force a reset of the communication port as well as dropping SS DTR for 200 ms pulses to reset any attached hardware The configuration data block structure which must be transferred from the processor to the module is as follows BTW Data Exa
18. 2 RS 485 compatible for multi drop applications with up to 32 slaves per port Satellite and Packet Radio support with a configurable Inter character Timeout available per port Software configuration From processor ladder logic Slave Addr 0 to 255 Parity None odd or even Stop Bit 10r2 Baud Rate 300 TO 38 400 RTS to TxD 0 65535 ms 1 ms resolution RTS Off 0 65535 ms 1 ms resolution Timeout 0 65535 ms 1 ms resolution Response time The Fisher ROC Master protocol driver is written in Assembly and in a compiled higher level language As such the interrupt capabilities of the hardware are fully utilized to minimize delays and to optimize the product s performance Fisher ROC Master Specifications 2 7 Protocol modes RTU mode with CRC 16 error checking Supported Fisher ROC Function codes 8 Set New Time and Date 10 Send Data From Configurable Opcode Tables 24 Store and Forward 120 Send Pointers for Alarm Event and History Logs 128 Send Archived Daily and Hourly Data for the Currently Selected Day and Month 130 Send Archived Hourly and Daily Data for Specified History Point Starting at Specified History Pointer 180 Send Specified Parameters 181 Set Specified Parameters Supports up to 100 Command List entries each individually configurable with the following parameters Port Mode Selection Slave Unit Slave Group Opcode Number of values to transfer Source data address Destination data addres
19. 26 7066 661 664 7233 fax E mail address prosoft prosoft technology com Web Site http Awww prosoft technology com FTP Site ftp ftp prosoft technology com Before calling for support please prepare yourself for the call In order to provide the best and quickest support possible we will most likely ask for the following information you may wish to fax it to us prior to calling 1 Product Version Number 2 Configuration Information Communication Configuration Master Command List Jumper positions 3 System hierarchy 4 Physical connection information RS 232 422 or 485 Cable configuration 5 Module Operation A Block Transfers operation LED patterns An after hours answering system on the Bakersfield number allows pager access to one of our qualified technical and or application support engineers at any time to answer the questions that are important to you Module Service and Repair The ROC card is an electronic product designed and manufactured to function under somewhat adverse conditions As with any product through age misapplication or any one of many possible problems the card may require repair When purchased from ProSoft Technology the module has a one year parts and labor warranty according to the limits specified in the warranty Replacement and or returns should be directed to the distributor from whom the product was purchased If you need to return the card for repair it is first necess
20. 3100 3150 ROC Fisher ROC Communications Revision 1 2 March 8 2001 USER MANUAL ProSoft Technology Inc 9801 Camino Media Suite 105 Bakersfield CA 93311 661 664 7208 661 664 7233 fax E mail address prosoft prosoft technology com Web Site http www prosoft technology com FTP Site ftp ftp prosoft technology com Please Read This Notice Successful application of the ROC card requires a reasonable working knowledge of the Allen Bradley PLC or SLC hardware and the application in which the combination is to be used For this reason it is important that those responsible for implementing the ROC satisfy themselves that the combination will meet the needs of the application without exposing personnel or equipment to unsafe or inappropriate working conditions This manual is provided to assist the user Every attempt has been made to assure that the information provided is accurate and a true reflection of the product s installation requirements In order to assure a complete understanding of the operation of the product the user should read all applicable Allen Bradley documentation on the operation of the A B hardware Under no conditions will ProSoft Technology Inc be responsible or liable for indirect or consequential damages resulting from the use or application of the ROC product Reproduction of the contents of this manual in whole or in part without written permission from ProSoft Technology Inc is proh
21. C and SLC ladder logic are included in the Appendix In order for the ProSoft Technology module to function the PLC SLC must be in the RUN mode or in the REM RUN mode If in any other mode Fault PGM the module will stop all communications until block transfers resume Operational Overview On power up the module moves a 255 into Word 1 of the BTR data file This is a signal that the module needs to receive configuration data before proceeding any further Once the configuration is received the module will begin transferring data to and from the processor depending upon how many Read and Write block counts have been configured Once these are completed the module will then transfer the command blocks if any have been configured Ladder Logic The flow of the ladder logic is somewhat predefined by the way the module has been programmed The expected flow of the ladder logic should be as follows Read Rung 1 Read Data from the Module In the case of the PLC the module data will be transferred into the BTR Buffer In the case of the SLC the module data will be accessed directly out of the M1 file 2 Decode the BTR Block ID number Depending on the value of the BTR Block ID copy the module data into the correct location in the ladder logic data table 3 Move the BTW Block ID Number from Word 1 of the BTR Buffer into Word 0 of the BTW Buffer In the case of the SLC the transfer will actually be from Word 1 of the M1 file to Word 0 of th
22. Each command consists of See Section 6 for details on configuring Fisher ROC Commands Name _ Bescripion Port Mode Select The Port Mode Select parameter allows the application to select which port the ROC Module will use to execute the command and whether the command will be performed continuously or under direct ladder logic control Control Valid values are Port Mode Description 0 Disable Command 1 Port 1 Continuous Command 2 Port 2 Continuous Command 9 Port 1 Control Command 10 Port 2 Control Command Continuous Opcodes 8 and 181 Write commands enabled as continuous will be executed every time the module s Command List is scanned Control Command Mode In the Control Command Mode the command will only be executed when the Command Enable Bit see Section 4 5 transitions from 0 to 1 The command is executed once per transition i e the module performs some one shot logic to assure that the command only executes one To clear the one shot in the module the Command Enable Bit must change state from 1 back to 0 Slave Unit The slave Unit represents the Fisher ROC slave unit address of the destination slave station Addresses should be entered in the decimal form Slave Group The slave group represents the Fisher ROC slave group address of the destination slave station Addresses should be entered in the decimal form Chapter 4 Writing to the Module Name Descripion amp
23. INTO INTI INTO INT 9 BINO DESEE Pea Pee IDEEN EE Byte 30 Byte31 Byte 32 Byte 33 Byte 34 Byte 35 DE BNo o pm AC ASCII INT 2 INT16 FLP Floating Point BIN Binary 6 2 Floating Point Support The movement of floating point data between the ROC module and other devices is easily accomplished as long as the device supports IEEE 754 Floating Point format This IEEE format is a 32 bit single precision floating point format Chapter 6 Fisher ROC Command Configuration The programming necessary to move the floating point data is to take advantage of the COP command that exists in the PLC and the SLC The COP command is unique in the PLC SLC data movement commands in that itis an untyped function meaning that no data conversion is done when moving data between file types i e itis an image copy not a value copy The structure of the COP command to move data from a Floating Point file into an integer file something you would do to move floating point values to the module is as follows COP SRC F8 0 DEST N7 311 COUNT 2 This command will move one floating point value in two 16 bit integer images to the integer file For multiple floating point values simply increase the count field by a factor of 2 per floating point value The structure of the COP command to move data from an Integer file to a Floating Point file something you would do to receive floating point values from the module is as follo
24. Read Block Cnt then BTR Block ID Read Block Start else BTR block ID BTR block ID 1 Chapter 1 Functional Overview Step Number Description Step 2 Module executes a BTR command with the A B Processor BTR BTW Enable Enable BTR W Yt Rack 0 Module 0 Group 0 Control N7 400 PLC version Data N7 410 Continuous N Length 64 Transfer Transfer Enable Done 11 1 0 O0 1 0 COP FY SRC M1 2 DEST N10 100 COUNT 50 SLC version When the Input bit goes true the module turns this bit on the data is ready to be copied out of the M1 file The structure of the BTR buffer being transferred from the module is BTR Buffer BTR Block ID BTW Block ID 50 wods of data from module words 2 through 51 The ladder logic decodes the BTR Block ID and copies the data from the BTR buffer into the ladder data table based on the value of the BTR Block ID EQU I COP SRC A N7 410 SRC N7 412 SCR B 2 DEST N10 100 COUNT 50 PLC Data Memory i Block ID 0 BTR Buffer i Block ID 1 50 word 4 data block n Block ID 2 Block ID 3 Block ID 4 Chapter 1 Functional Overview Step Number Transfer the BTW Block ID from the BTR Buffer to the BTW buffer MOV SRC A N7 411 SRC B N7 310 BTR Buffer BTW Buffer Copy ladder data memory whether Data Command List or Configuration to the BTW buffer The actual data copied depends on the d
25. S jumper must be installed for CTS card to communicate GND GND DTR RS 232 w Hardware 3150 ROC Modem or other Handshakin DB 9 Pin Male Comm Device Port Connection with a modem or other similar device TxD 3 TxD RxD 2 RxD RTS RTS CTS 8 CTS GND 5 GND DTR 4 DTR RS 485 2 Wire Connection 3150 ROC RS 485 The Jumper on the module must be DB 9 Pin Male Device set in the RS 485 position for all 2 wire applications TxRxD TxRxD TxRxD TxRxD RTS RTS CTS jumper must be installed for CTS card to communicate GND GND Optional RS 422 4 Wire Connection The jumper on the module must be ce Bence in the RS 422 position for all 4 wire applications TxD s _ RxD TxD RxD RxD TxD RxD TxD RTS RTS CTS jumper must be installed for CTS card to communicate GND 5 H GND Optional RS 485 and RS 422 Tip If communication in the RS 422 RS 485 mode does not work at first despite all attempts try switching termination polarities Some manufacturers interpret and A B polarities differently A Appendix A Support Service amp Warranty Support Service and Warranty Technical Support ProSoft Technology survives on its ability to provide meaningful support to its customers Should any questions or problems arise please feel free to contact us at Factory Technical Support ProSoft Technology Inc 9801 Camino Media Suite 105 Bakersfield CA 93311 661 664 7208 800 3
26. SCII representation In the case of the ROC product the letters ROC should be displayed when placing the programming software in the ASCII data representation mode N10 112 Revision ASCII These two words represent the product revision N10 113 level of the firmware in an ASCII representation An example of the data displayed would be 1 00 when placing the programming software in the ASCII data representation mode N10 114 Operating System Rev ASCII These two words represent the module s internal N10 115 operating system revision level in an ASCII representation N10 116 Production Run Number This number represents the batch number that your N10 117 ASCII particular chip belongs to in an ASCII representation 18 19 N10 118 Spare N10 119 All counters in the Slave Error Table will rollover to O after reaching 65535 5 1 5 Master Error Code Table The ROC Module monitors the status of all Master port commands This status is communicated to the processor in the form of a Master Error Code Table the position of which is controlled by the Master Error Table Pointer in the Communication Configuration setup Each Master command will generate an Error Code for use by the user The Master Error Code Table is initialized to zero on power up and every time the module receives the 255 configuration data block The Error Code Table is a 120 word block The relationship between the placement of the error codes withi
27. The allowable range of values is 0 to 65535 Oxffff If a zero value is entered the module will default to a one second timeout value 1000 ms This register is used in situations where the end of message character timeout delay must be extended beyond the normal 3 5 character widths The value entered represents the number of 1 ms intervals of no transmission which will be counted prior to accepting a message This parameter will be useful in satellite or packet radio installation where a data transmission may be split between two packets Increasing this value beyond the system s packet handling time will eliminate timeout errors Valid values range from 0 to 65535 Oxffff System Configuration Chapter 4 Writing to the Module Data Addr Description Read Data Block Count Write Data Block Count Command Block Count This value represents the number of 50 word data blocks which are to be transferred from the ROC Module to the processor The blocks returned from the module start at block 0 and increment from there The maximum block count is 80 As an example a value of 5 will return BTR Block ID data blocks 0 1 2 3 and 4 or module registers 0 to 249 If a value greater than 80 is entered a System Configuration Error is activated This value represents the number of 50 word data blocks which are to be transferred from the processor to the ROC Module The module will use this value to return a BTW Block ID Number
28. This branch located in the BTW rung rung 1 is an example of the logic that must be implemented for each data block to be move to the module See logic in Appendix for implementation example 4 3 2 Block Transfer Data Structure The structure of the block transfer buffer when writing data to the module is shown below Name 9 BDescription BTW Block ID The block identifier number allows the ROC Module to decode which 50 word page in the module s 4000 word data space the data is to be written The data space to be written into can be determined by multiplying the BTW Block ID by 50 The result is the first word of the page As an example BTW Block ID Data Space 0 0 to 49 1 50 to 99 10 500 to 549 20 1000 to 1049 By paging the different data blocks into the module the processor can control the module data memory contents 1 to 50 The data to be written to the module 4 4 4 4 1 Chapter 4 Writing to the Module Command List Configuration Master Mode BTW Block ID Codes 80 99 A ROC Master port establishes communications and performs various communications functions based on the data which the user has placed in the command list The command list consists of up to 100 individually configured command data blocks 10 words reserved per command which are shared between the two available ports in the case when the module is configured with two Master ports Command List Ladder Logic This list
29. a table Using the ladder logic programming software enter the values necessary to setup one or more valid commands Hints to Make Life Easier When first setting up the Command List we recommend that you start out with one command This one command will allow the module to begin transmitting if all else is OK i e ladder logic cable is connected etc Once the module is transmitting then attempt to communicate with the slave then enter any other commands needed An example of a command list is shown below Note that the commands can be entered in rows and that once the column definitions are understood reviewing the Command List is very easy 1 2 3 4 5 8 9 SLV SLV OP SRC POLL STORE UNIT GROUP CODE CNT ADDR TIME FWD 25 2 180 1 0 25 2 10 3 26 2 180 1 0 20 0 26 2 181 4 30 0 Example Command List An example of multiple message configuration data blocks is shown in the following table 4 5 Command Control Mode Master Mode Under some special operating conditions it may be necessary for the ladder logic to be able to closely coordinate and control the execution of commands in the Command List To accommodate this requirement the ROC module supports something called the Command Control Mode When configured in the Command Control Mode the ladder logic is able to provide Command Enable control on a per Command List entry basis In addition when used in conjunction with the Command Done Bits See Section 5 2 the ladder
30. agrams 8 Cable Connection Diagrams The following diagrams show the connection requirements for the ports on the 3100 and 3150 modules 3100 ROC Module RS 232 w No Hardware Handshaking Port Connection with another communication port RS 232 w Hardware Handshaking Port Connection with a modem or other similar device RS 485 2 Wire Connection The jumper on the module must be set in the RS 485 position for all 2 wire applications RS 422 4 Wire Connection The jumper on the module must be in the RS 422 position for all 4 wire applications 3100 ROC DB 25 Pin Female TxD 2 RxD TxD PC or Device RTS CTS jumper must be installed for CTS card to communicate GND 3100 ROC DB 25 Pin Female Modem or other Comm Device TxD 2 TxD RxD 3 RxD RTS n RTS CTS 5 CTS GND GND DTR i20 DTR 3100 ROC RS 485 DB 25 Pin Female Device TxRxD TxRxD TxRxD TxRxD RTS RTS CTS jumper must be installed for CTS card to communicate GND GND Optional 3100 ROC RS 422 DB 25 Pin Female Device TxD RxD w 28 mo RxD TxD RxD TxD RTS CTS 5 GND RTS CTS jumper must be installed for card to communicate GND Optional 3150 ROC Module RS 232 w No Hardware Chapter 8 Cable Connection Diagrams 3150 ROC PC or Device Handshaking DB 9 Pin Male Port Connection with another communication port TxD a RxD RxD TxD RTS RTS CT
31. and command list blocks to the module The BTW Block ID number is developed by the module based on the parameters entered in parameters 21 and 22 of Block 255 This value is intended to only be a suggestion and to ease the ladder logic programming requirements If it is desired to develop a different data transfer series this may be easily accomplished in ladder logic Valid codes are BTW Code Description 0 79 Module Data 80 99 Command List 255 Module Configuration Chapter 5 Reading from the Module Word Name Description 2 to 51 Data The contents of the module s Register Data space 0 3999 This data will contain data received from the slaves data moved from the processor and the Slave and Master Error Tables The values will be 16 bit register values and should be placed into integer files Note that the user application ladder logic controls the placement and use of the data registers 52 to 63 Command Done See Section 5 2 and Error Bits 5 1 2 Moving the data from the module to the processor Data that has been read from the slave devices is deposited into a 4000 word register table in the module This table is addressed starting at 0 and going up to 3999 The data register table is transferred from the module to the ladder logic through a paging mechanism designed to overcome the 64 physical word limit of the BTR instruction The paging mechanism is outlined in the discussion above but the import
32. ant thing to understand is the relationship between the page numbers BTR Block ID numbers and the register addresses in the module The diagram also shows the layout for an example application Note the number of blocks returned from the module to the ladder logic is determined by the value entered in the System Configuration Read Block Cnt register In this example we have assumed a Read Block Count value of 5 R M I PLC Data Memory Renee e PLC Block ID 0 to 79 Address 0 to 3999 pe Block ID 0 Read Data from Slaves to PLC These data registers 0 to 99 will be the destination addresses for the Commands Block ID 1 in the Command List N10 100 Slave Error Table Pointer 100 Master Error Table Pointer 120 Error Table N10 150 Block ID 3 The data registers 100 to 119 will contain the Slave Error Table Data registers 120 to 240 will contain the Master Error Table N10 200 Block ID 4 Block ID 79 Read Data Blocks from ROC Module Note that this diagram assumes a Read Block Count value of 5 therefore returning Registers 0 to 249 from the module This value can be altered as needed depending on the application 5 1 3 Ladder Logic to Read Module Data The ladder logic must be programmed to look at the BTR buffer decode several words and then take action The following is an example of such ladder logic Chapter 5 Reading from the Module BTR BTW Enable Enable BTR Rack 0 Module 0 Group 0 Control N7
33. ary to obtain an RMA number from ProSoft Technology Please call the factory for this number and display the number prominently on the outside of the shipping carton used to return the card General Warranty Policy ProSoft Technology Inc Hereinafter referred to as ProSoft warrants that the Product shall conform to and perform in accordance with published technical specifications and the accompanying written materials and shall be free of defects in materials and workmanship for the period of time herein indicated such warranty period commencing upon receipt of the Product This warranty is limited to the repair and or replacement at ProSoft s election of defective or non conforming Product and ProSoft shall not be responsible for the failure of the Product to perform specified functions or any other non conformance caused by or attributable to a any misapplication of misuse of the Product b failure of Customer to adhere to any of ProSoft s Appendix A Support Service amp Warranty specifications or instructions c neglect of abuse of or accident to the Product or d any associated or complementary equipment or software not furnished by ProSoft Limited warranty service may be obtained by delivering the Product to ProSoft and providing proof of purchase or receipt date Customer agrees to insure the Product or assume the risk of loss or damage in transit to prepay shipping charges to ProSoft and to use the original shipp
34. dresses MO x addresses M1 x addresses space for the module references from N7 and N10 6 Install card in rack Power down rack and Power down and install module E mima Loiemodie needed forappicaion of the module needed for application 9 Apply power to system and place Monitor the status files and PLC in RUN the LEDs on the front of the Once the hardware has been installed and the necessary programming has been downloaded to the processor the system is ready Presuming all other system components are safely ready 3 1 3 2 Chapter 3 Ladder Logic Overview Ladder Logic Overview Data transfers between the processor and the ProSoft Technology module occur using the Block Transfer commands in the case of the PLC and MO M1 data transfer commands in the case of the SLC These commands transfer up to 64 physical registers per transfer The logical data length changes depending on the data transfer function The following discussions and Sections details the data structures used to transfer the different types of data between the ProSoft Technology module and the processor The term Block Transfer is used generically in the following discussion to depict the transfer of data blocks between the processor and the ProSoft Technology module Although a true Block Transfer function does not exist in the SLC we have implemented a pseudo block transfer command in order to assure data integrity at the block level Examples of the PL
35. e 1 year Warranty Procedure Upon return of the hardware Product ProSoft will at its option repair or replace Product at no additional charge freight prepaid except as set forth below Repair parts and replacement Product will be furnished on an exchange basis and will be either reconditioned or new All replaced Product and parts become the property of ProSoft If ProSoft determines that the Product is not under warranty it will at the Customer s option repair the Product using current ProSoft standard rates for parts and labor and return the Product freight collect Appendix B Product Specifications Product Specifications The 3100 3150 ROC Fisher ROC Communication Module product family allows Allen Bradley 1771 and 1746 I O compatible processors to easily interface with other Fisher ROC protocol compatible devices as a Fisher ROC Master The ROC product includes the following standard features General Specifications NON N N C2 C2 N Two fully configurable serial ports each capable of supporting Fisher ROC Master Available configurations include Port Configurations Port 1 Port 2 Master Master Master Master Support for the storage and transfer of up to 4000 registers to the PLC SLC data tables Support movement of binary integer ASCII and floating point data types Memory mapping is completely user definable through data table configuration RS 232C handshaking for SCADA radio modem applications RS 42
36. e Bits is as follows Cmds 1to 16 17 to 32 33 to 48 49 to 64 65 to 80 81 to 96 Example Word 52 bit 0 is Command 1 58 63 Cmd Error Bits These registers contain Error Bit flags for each command in the command list up to the first 96 commands The Error Bits are bit mapped into the words depending on their relative position in the Command List The mapping within the Done Bits is as follows Word Cmds 58 1 to 16 59 17 to 32 60 33 to 48 61 49 to 64 62 65 to 80 63 81 to 96 Example Word 52 bit 0 is Command 1 5 2 2 Ladder Logic A simple rung of logic can be entered to move the Done and Error bits from the BTR buffer to the PLC SLC data table An example follows Copy the Command Done and Error bits from the BTR buffer to the data table 6 1 Chapter 6 Fisher ROC Command Configuration Fisher ROC Command Configuration The ProSoft Technology ROC Fisher ROC Master communication driver supports several data read and write commands When configuring a Master port the decision on which command to use is made depending on the type of data being addressed and the level of Fisher ROC support in the slave equipment Fisher ROC Commands The ROC module supports a command subset of the Fisher ROC Specification The following sections detail the different commands supported by the module Master Driver Opcode Command Comments Set New Time and Date Send Data From Configurable Opcode Tables Send Po
37. e MO file The BTW Block ID number should be manipulated if necessary to assure that data is not overwritten in the module The LIM test branch does this in the example logic 4 Testfor Event Initiated Commands and module configuration Write Rung 1 Decode the BTW Block ID number and depending on the value move either data values Command List values or Configuration values to the BTW buffer MO file in the SLC 2 Ifthe configuration transfer is enabled then clear the configuration enable bit 3 Inan Event Initiated Command is enabled then clear the enable bit 4 Execute the BTW transfer In the PLC this will be done by enabling the BTW instruction In the SLC this will be done by setting the Transfer Done bit an Output bit has been assigned to this function in the design of the module Chapter 4 Writing to the Module 4 Writing to the Module This section provides reference level details on the transfer of data from the PLC SLC processor to the ROC module This type of transfer allows the ladder logic to send configuration command list and data to the module 4 1 Block Transferring to the Module Data transfer to the module from the processor is executed through the Block Transfer Write function The different types of data which are transferred require slightly different data block structures but the basic data structure is Name Description Word BIW Block ID A block page identifier code This code is
38. e value must be determined empirically bL c RANDE I Read Block ID Start This value determines the starting BTR Block ID number which will be returned from the module As an example if the ladder logic needs to receive Blocks 2 through 5 from the module the parameter should be configured w ith a 2 and the Read Block Count should be set to 4 Valid values range from 0 to 79 Write Block ID Start This value determines the starting BTW Block ID number which the module will return to the ladder logic As an example if the ladder logic needs to write into Blocks 4 through 5 in the module this parameter should be set to 4 and the Write Block Count should be set to 2 Valid values range from 0 to 79 4 3 Writing Into Module Data Memory BTW Block ID Codes 0 79 Writing into the ROC register data space is accomplished using a Block Transfer Write with BTW Block ID codes from 0 to 79 followed by 50 words of data Care must be exercised with memory layout to assure that ROC read and write commands do not overwrite data being moved in from the processor ladder logic Fisher ROC data cannot be moved into a 50 word block that is also updated by the processor The ladder logic examples in the Appendix address this concern 4 3 1 Ladder Logic to Write Data to Module The ladder logic required to move data to the module is a simple series of EQU COP branches or it can be implemented using indirect addressing The wa
39. ecoding of the BTW Block ID number EQU A I COP SRC A N7 310 SRC N10 150 SCR B 3 DEST N7 311 COUNT 50 PLC Data Memory Block ID 0 Block ID 4 BTW Buffer Block ID 2 T data block Block ID 3 Block ID 4 BTR BIW Enable Enable BTW Wi Rack 0 Module 0 Group 0 Control N7 300 Data N7 310 Continuous N Length 64 PLC version Transfer Transfer Enable Done 11 1 0 O0 1 0 COP IM SRC N10 100 DEST M0 1 1 COUNT 50 Transfer Done 00 1 0 SLC version When the ladder logic has transferred the ladder data into the MO file the Transfer Done bit is set by the ladder This bit is used by the module to determine when the transfer process is complete 1 3 5 Chapter 1 Functional Overview Stop Number Step 7 Interlocking the Block Transfers The module receives the BTW data After decoding the BTW Block ID number the module will transfer the BTW buffer data into the correct location in the modules memory One of the fundamental assumptions that the module makes is that there will be one BTR per one BTW command In the module upon completing the BTR instruction the module jumps immediately to the BTW instruction To the programmer who follows our example logic this has rather minor implications Problems arise however when a ladder logic implementation is attempted which does not meet the module s block transfer exp
40. ectations Specifically the following must be adhered to when programming the ladder logic for the module PLC Program using BTR BTW Instructions In the 1771 types of processors PLC 2 PLC 3 and PLC 5 the BTR and BTW Enable bits must be used to enable the Block Transfer Instructions With this type of programming the PLC is guaranteed not to execute two block transfers at the same time and the BTR and BTW instructions are guaranteed to alternate Ample examples of this type of block transfer programming are available in A B documentation as well as in the example ladder logic program in the Appendix BTW Enable BTR vi BTW Enable vi Rack 0 Module 0 Group 0 Control N7 400 Data N7 410 Continuous N Length 64 Data transfer instructions to move data from module to ladder memory Data transfer instructions to move data from ladder memory to module BTW Rack 0 0 Group 0 Control N7 300 Data N7 310 Continuous N Length 64 Module Chapter 1 Functional Overview SLC Program using MO M1 Instructions In the SLC processors there is no true mechanism for guaranteeing the integrity of data block transfers as there is in the PLC platform For this reason we have developed a handshaking mechanism which is designed to assure that all the words in the MO and M1 files are transferred in unison Following this mechanism is the only wa
41. ed the module will begin to block transfer with the ladder logic The first block transfer sent from the module will initiate the configuration process causing the ladder logic to move a 255 configuration block to the module Once the module is configured it will begin the Main Logic Loop Main Loop Logic Upon completing the power up configuration process the module jumps into an infinite loop which includes the following functions 1 Port 1 and Port 2 handlers Detect end of message condition Call message handlers Initiate commands 2 Block Transfer Test CTS pin to assure module is not in transmit mode Test Block Transfer Delay counter If all OK then block transfer From Power Up Logic Execute Port 1 Control Logic Execute Port 2 Control Logic transmit active BT Delay Cntr Done Yes Call BT Logic 1 3 3 The Data Space in the module Chapter 1 Functional Overview if port in RX mode then test for message received if port in TX mode then test if message transmit has completed If ready for new command then create new command Port 2 Control Logic if port in RX mode then test for message received if port in TX mode then test if message transmit has completed If ready for new command then create new command Test Transmit Status If either port is in process of transmitting then do not execute BT logic The module uses the CTS pin status to detect the tra
42. emory in which the received data should be placed starting with word 0 Chapter 6 Fisher ROC Command Configuration Master Driver Opcode Command Comments Send Count Number of bytes to be sent Valid Archived count value is 4 Hourly and Daily Data Source Addr Starting word address in the for Specified module where the write data is stored The History Point data starting at this address will be sent to the Starting at slave when an opcode 128 is written Enter a Specified 0 to output parameter data from internal History database address 0 Pointer Dest Addr Starting word address in the module s Register Memory in which the received data should be placed starting with word 0 Send Count Number of data points to be read Specified Count must be greater than 0 Parameters Source Addr Starting word address in the module from which the TLP data to be sent to the slave should be read The first word is Point type the second is Point Logic number and the third is Parameter number Enter a 0 to output parameter data from internal database address 0 Dest Addr Starting word address in the module s Register Memory in which the received data should be placed starting with word 0 Type Controls TLP stripping See Section 4 for details Set to 0 for stripping and 1 for no stripping Set Specified Count Number of points to be written Count Parameters must be greater than 0 Source Addr Starting word add
43. fers 13 6 SLC Processor Configuration 14 Data Flow ss s 14 1 General concepts 14 22 Reading data from the module esee eene tenente nentn nete 143 Writing data to the module sese tetentnnenenetne 144 Master Port Driver gu s 1 5 ROC Support of Fisher ROC Functionality essere 2 Getting Going A Step by Step Approach teten tenentes 3 Ladder Logic Overview esse 3 1 Operational Overview 32 Ladder Logic 4 Writing to the Module sese 41 Block Transferring to the Module 42 Communications Configuration BTW Block ID 255 43 Writing Into Module Data Memory BTW Block ID Codes 0 79 43 1 Ladder Logic to Write Data to Module serene 4 3 2 Block Transfer Data Structure 44 Command List Configuration Master Mode BTW Block ID Codes 80 99 44 1 Command List Ladder Logic seseneeeenentete tnter trennen 442 Command List Structure 44 3 Editing the Command List 4 5 Command Control Mode Master Mode sn am 45 1 The BTW Block OO E a a a Ea ee entente tnnt tn tnnt tn tn Ea entes 45 2 Controlling the Commands essent tenerte ttnten 4 5 3 Example Command List B sh 3 5 Reading fromthe Modile AR p ER RUPEE HH 5 1 Transferring data from the module BTR Block ID 0 to 79
44. for module code 5 F9 for SPIO Config when the correct slot is highlighted 6 F5 Advanced Setup 7 F5 for MO file length type in 64 and Enter 8 F6 for M1 file length type in 64 and Enter Esc out and save configuration Data Flow General concepts In developing a solid understanding of the module s operation it is important to understand the movement of data in between the ladder logic the module and the Master drivers 1 4 2 1 4 3 1 4 4 Chapter 1 Functional Overview PLC Memory PLC Ladder ROC Memory ROC Logic Field Device i T Slave 2f Device The following discussion covers the flow of data in the different stages Further discussion is available in later sections on the flow of data under the different operating modes of the ports Reading data from the module The module maintains a 4000 block of data memory This memory contains The results of Master port transactions Slave port Status data Module Revision information Master port Status data mess die During the transfer of data from the module to the PLC the ladder logic is able to gain access to this information Writing data to the module The module depending on the configuration of the ports requires three basic types of data in order to operate correctly The three types of memory which can be transferred to the module are as follows 1 Configuration Data This data contains all of the parameters necessary for the module
45. gisters Error Status Table Example Master Error Table Pointer 120 Wrd Wrd Wrd Wrd z a a a a N10 120 N10 130 N10 140 N10 150 N10 160 N10 170 N10 180 N10 190 N10 200 N10 210 N10 220 N10 230 These registers correspond to the registers used in the sample program for PLC 5 in the back of this manual Your application may require your own specific program In this case an error code of 8 was generated for command 2 all other commands were executed without any errors Column 0 is used to identify that a master port has reached the end of the command list and is starting at the top of the Command List OOoooo0o0oooo0oc o Oooooooooooo l2 ooocooooooooewS OOooo0o0o0o0o0o0000 lo OoOoooooooooo OoOooooooooooocl an OoOooooooooooc o OoOooooo0o0ooo0o00l4 OOoo0o0o00000001o oOocooooooooookog e eo eo eo 5 1 6 Error Status Codes The Error Codes returned in the Master Error Code Table reflect the outcome of the commands executed by the module Note that in all cases if a zero is returned there was not an error Valid Error Status Codes are as follows Code Name Description o a All OK The module is operating as desired Illegal Function An illegal function code request is being attempted Bad Data Address The address or the range of addresses covered by a request from the master are not within allowed limits 3 Bad Data Value The value in the data field of the command is not allowed
46. he User Config Bit in the example logic accomplishes this In the example logic the bit must either be set in the data table manually or the module must be powered down reset In order to download the configuration upon transitioning from PGM to RUN simply add a run to set the User Config Bit based on the First Scan Status Bit S1 1 15 Chapter 7 Diagnostics and Troubleshooting Problem Description Steps to take Error Codes being returned in locations with no commands Master Configuration RX1 or RX2 on continuously 3100 only Be sure that the Command Block Count configuration value is setup correctly There should be one branch of logic in the Write Rung corresponding to each Command Block to be written i e a Command Block Count of 2 should have two branches of logic to handle BTW Block IDs 80 and 81 If the Command Block Count configuration value exceeds the number of branches in logic the Command List is inadvertently being duplicated To resolve the issue either add more branches of logic or reduce the Command Block Count value to match the number of BTW logic branches The TX and RX LEDs on the module are tied to the hardware state of the ports i e are not controlled directly by firmware When the RX LED is on continuously is normally indicates that the polarity of the cable connection to the port is swapped This is particularly true in RS 485 and RS 422 modes Chapter 8 Cable Connection Di
47. ibited Information in this manual is subject to change without notice and does not represent a commitment on the part of ProSoft Technology Inc Improvements and or changes in this manual or the product may be made at any time These changes will be made periodically to correct technical inaccuracies or typographical errors ProSoft Technology Inc 1995 2001 Quick Start Implementation Guide Integration of the ROC module into a PLC or SLC application is easier if a series of steps are followed In order to assist the first time users of our products in getting operational quickly we have come up with this step by step implementation guide First Time Users Although the following steps are to assist you in implementing the module we recommend that you attempt to experiment with the example logic available off of our FTP site before laying out your application This step will allow you to gain insight into how the module works prior to making decisions which will impact the long term success of the installation Starting with one of the ladder logic programs available for the ROC complete the following steps If hand entering the ladder logic by hand for the SLC remember the following Configure the slot as a 1746 BAS module in 5 02 mode Be sure to enter the Transfer Enable and Done bits as shown in the example logic Edit the ladder logic provided on disk as needed for the application See Section 3 0 Verify rack and
48. ing container or equivalent Contact ProSoft Customer Service for further information Limitation of Liability EXCEPT AS EXPRESSLY PROVIDED HEREIN PROSOFT MAKES NO WARRANT OF ANY KIND EXPRESSED OR IMPLIED WITH RESPECT TO ANY EQUIPMENT PARTS OR SERVICES PROVIDED PURSUANT TO THIS AGREEMENT INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE NEITHER PROSOFT OR ITS DEALER SHALL BE LIABLE FOR ANY OTHER DAMAGES INCLUDING BUT NOT LIMITED TO DIRECT INDIRECT INCIDENTAL SPECIAL OR CONSEQUENTIAL DAMAGES WHETHER IN AN ACTION IN CONTRACT OR TORT INCLUDING NEGLIGENCE AND STRICT LIABILITY SUCH AS BUT NOT LIMITED TO LOSS OF ANTICIPATED PROFITS OR BENEFITS RESULTING FROM OR ARISING OUT OF OR IN CONNECTION WITH THE USE OR FURNISHING OF EQUIPMENT PARTS OR SERVICES HEREUNDER OR THE PERFORMANCE USE OR INABILITY TO USE THE SAME EVEN IF PROSOFT OR ITS DEALER S TOTAL LIABILITY EXCEED THE PRICE PAID FOR THE PRODUCT Where directed by State Law some of the above exclusions or limitations may not be applicable in some states This warranty provides specific legal rights other rights that vary from state to state may also exist This warranty shall not be applicable to the extent that any provisions of this warranty is prohibited by any Federal State or Municipal Law that cannot be preempted Hardware Product Warranty Details Warranty Period ProSoft warranties hardware product for a period of on
49. inters for Alarm Event and History Logs Send Archived Daily and Hourly Data for the Currently Selected Day and Month Count Number of bytes to be sent Valid count values are 6 9 Source Addr Starting word address in the module where the write data is stored The data starting at this address will be sent to the slave when an opcode 8 is written Enter a 0 to output parameter data from internal database address 0 Count Number of bytes to be sent Valid count value is 3 Source Addr Starting word address in the module where the write data is stored The data starting at this address will be sent to the slave when an opcode 10 is written Enter a 0 to output parameter data from internal database address 0 Dest Addr Starting word address in the module s Register Memory in which the received data should be placed starting with word 0 Count Number of bytes to be sent Valid count value is 0 Source Addr N A Dest Addr Starting word address in the module s Register Memory in which the received data should be placed starting with word 0 Count Number of bytes to be sent Valid count value is 3 Source Addr Starting word address in the module where the write data is stored The data starting at this address will be sent to the slave when an opcode 128 is written Enter a 0 to output parameter data from internal database address 0 Dest Addr Starting word address in the module s Register M
50. logic is able to effectively one shot each command if desired 4 5 1 The BTW Block Structure The structure of the Enable bits as they are written to the module in the BTW Block Transfer buffer is as follows Word Name Description BTW Block ID The Command Enable bits are moved to the module during every BTW transaction Therefore all valid BTW Block ID numbers can be used here Module data and Command List as outlined above Chapter 4 Writing to the Module Word Name Description amp Cmd Enable Bits These registers contain Command Enable Bits for each command in the command list up to the first 96 commands The Enable Bits are bit mapped into the words depending on their relative position in the Command List The mapping within the words is as follows Cmds 1to 16 17 to 32 33 to 48 49 to 64 65 to 80 81 to 96 Example Word 51 bit 0 is Command 1 Enable 4 5 2 Controlling the Commands When a command is configured in the Command Control Mode and when the module detects the Command Enable bit changing state from 0 to 1 the module will attempt to execute the command Three attempts will be made to execute the command If the command is successfully sent the Command Done bit will be set If an error occurs during the sending process the Command Error bit will be set As example of the ladder logic which might be implemented to control a command would appear i
51. mmand will begin placing the data from the slave The data will be placed in the data table one value per integer See section 6 1 1 for a detailed explanation The Type field is relevant only during the 180 read command The Stripping of the TLP from the data is available In order to use the stripping feature all data types requested in one command must be of the same size i e all floating point all integers or all bytes Type Description 0 Default value Strips TLP from data and stores data only 1 Stores TLP and data as received Polling Time Preset The Polling Time Preset value allows each command to have a configurable execution frequency In the module a timer is maintained for each command Once per second the timer is decremented until it reaches zero When the timer reaches zero the command is enabled for execution and the timer is reset to the Polling Timer Preset value The resolution of the polling timer is 1 second Valid values are 0 to 65535 Oxffff Store And Forward Source The value represents the register addresses for both read and write Address commands from which the Store and Forward Communication Path header will be obtained The contents of the 10 words starting at this address will be used as the Communication Path for ROC to ROC Communications Chapter 4 Writing to the Module 4 4 3 Editing the Command List Entering the Command List is a matter of entering the correct values into the PLC dat
52. movement of data over the backplane Transfer Done This bit is set by the ladder logic to communicate to the module that the ladder has completed the data transfer The port interface circuitry providing the physical interface to the real world The ports and the interface circuitry are optically isolated from the rest of the card and therefore the backplane providing a high level of protection to the A B processor Both ports are capable of supporting RS 232 RS 422 also called a 4 wire connection RS 485 also called a 2 wire connection 1 3 General Concepts The following discussion covers several concepts which are key to understanding the operation of the ProSoft module 1 3 1 1 3 2 Chapter 1 Functional Overview Module Power Up and Reset On power up or after pressing the reset pushbutton 3100 only the module begins performing its logical functions These functions shown in the flow chart Power Up Initialize module registers Initialize hardware Setup the interrupts Perform Power Up Logic Call BT Logic Get Module Init Call BTLogic until get 255 block Block Recvd Yves Proceed to Main Loop Logic included here include 1 Initialize hardware Initialize the backplane Initialize the DUART 2 Initialize Module registers Clear the Module Data Block Clear Command List Clear Error Status Tables Preset constants Once the register space has been initializ
53. mple Buffer Addr Value 0 _ BIWBlocID Pert Config pes N S Por Configuration Word Port Unit Addr Baud Rate Port Configuration Word Port Unit Addr Chapter 4 Writing to the Module System Configuration NOE N N 24 NL126 N 27 This register contains several communication configuration parameters encoded into the word These are as follows Protocol Mode The port s protocol mode is selected by these bits Bits 210 000 Fisher ROC Master Unused Bits All unused bits must be set to 0 Stop Bits The number of stop bits to be used is defined as follows Bits 13 12 0 0 One stop bit 0 1 Two stop bits 1x Invalid Port Configuration Parity The parity mode to be used by the module is defined by this word as follows No parity Odd parity Even parity Invalid Port Configuration N 1 Master Unit Address The value entered in this register is used as the Fisher ROC N 11 Master Unit address Valid values range from 0 to 255 Baud Rate The baud rate at which the port is to operate The available configurations are as follows Value Baud Rate 300 Baud 600 Baud 1200 Baud 2400 Baud 4800 Baud 9600 Baud 19200 Baud 38400 Baud The module s two ports are limited to an upper baud rate of either 19200 or 38400 baud The module cannot be configured with one port at 19200 and the other at 38400 If an attempt is made to configure the module in this fashion a Por
54. n structure as follows Ladder Logic Command Command Enable Trigger Bit 4 Command Command Enable Done Bit Bit 4 The simplest implementation would be to maintain a Binary table of Command Enable Bits which is copied to the BTW Buffer every transaction The following branch of logic can be added to the BTW rung transfer data to module COP 7 SRC B9 0 DEST N7 361 Copy the Command Enable COUNT 6 Table of bits to the BTW Block Transfer Buffer The Command Done and Error bits could then be copied into the same Binary File and referenced in ladder logic after being transferred The following instruction can be added to the BTR rung read data from module accomplish this Copy the Command Done and Error bits from the BTR buffer to the data table 4 5 3 Example Command List Commands can be controlled through configuration of the Command Enable Chapter 4 Writing to the Module 1 2 3 4 8 9 SLV SLV OP POLL STORE UNIT GROUP CODE CNT TIME FWD 25 2 180 1 25 2 181 4 Example Command List An example where the command in N7 50 is configured as a Control Command Mode for Port 1 while the N7 60 command is configured for Port 2 0 0 0 0 5 1 5 1 1 Chapter 5 Heading from the Module Reading from the Module This section provides reference level details on the transfer of data from the PLC SLC processor to the ROC module This type of transfer allows the ladder
55. n the Error Table and the commands is according to the command s relative position in the command list The simplest method for obtaining the Master Error Status Table is to locate it at the end of the application s data map and then read it back into the PLC SLC data table as part of the regular data The structure of the Master Error Table is as follows Word Description 0 Command List End of Poll Status 1 Command 1 Error Status 2 Command 2 Error Status 98 Command 98 Error Status 99 Command 99 Error Status 100 120 Future Where Command List End Of Poll Status This register provides an indication of when the Master has completed one cycle through the Command List A bit in the word will be toggled each time the command list has been completed The status is indicated for each master port as follows Bit 0 Master Port 1 1 Master Port 2 Chapter 5 Heading from the Module End of Poll Toggle Bit The theoretical operation of the End of Poll Toggle Bit is that all of the commands which are to be executed for a port are execute within each state change of the bit Command Error Status The Error Status Codes either received from the slaves or generated by the module are placed in the table See the next section for the meaning of the error codes The values will be 16 bit values and should be placed into an integer file Note that the user application ladder logic controls the placement and use of these re
56. ndition moving the 255 value is not held true Presuming that the processor is in run verify the following CTS input is not satisfied check RTS CTS jumper Check Error Status codes for 255 code If so see next problem If in slave mode verify the slave address being requested from the Host Ifin master mode verify the command list configuration and that the Command List is being moved into the module i e check the Command Block Cnt and associated ladder logic This is caused by only one thing a missing CTS input on the port If a cable is connected to the port then verify that a jumper has been installed between the RTS and CTS pins If so then there may be a hardware problem This condition normally occurs when it is forgotten that the BTW Block ID value is being manipulated by the module and that it always starts at 0 Please verify that the configuration of the module Read and Write Block Counts is not causing data from the PLC SLC to overwrite data being returned from the module A simple method for verifying this is to perform a histogram on the BTW Block ID register Under several circumstances data swapping in the module has occurred This swapping has always been associated with the 8 16 pt jumper on the back of the card Please verify that the jumper is in the 8pt position In order for new values to be moved to the module a Block Transfer Write with a Block ID of 255 must be transmitted to the module T
57. nsmit status Test the Block Transfer Delay Counter If the Block Transfer Delay counter has incremented beyond the counter preset set in config then go ahead and perform block transfer Execute Block Transfer Logic Calls BT Logic which executes the BTR and BTW logic One of the concepts which are important to develop an understanding of is the relationship between the data space in the module and how this data can be moved between the module and the PLC SLC processor The following discussion explains the data structure in the module and how this data can be moved between the module and the ladder program Some key points to understand Key Point Size of data register space in the module The module maintains a 4000 word data space which can be used as needed by the application for data storage Module Memory 4000 word block of 16 bit registers Addresses 0 to 3999 0 m 1 3 4 Chapter 1 Functional Overview Key Point How 4000 word module data space is broken down in blocks How data is paged between the module and processor How data page is placed in the processor s data table The Backplane Data Transfer Process This 4000 words block of data is logically broken down into 80 fifty 50 word blocks 80 blks x 50 wrds blk24000 words Module Memory 4000 word block of 16 bit registers Block ID 0 to 79 Addresses 0 to 3999 O Block IDO Block ID 1 Block ID 2
58. r ROC Functionality The ROC module supports several Fisher ROC Function Codes used for data transfer The following table documents the Function Codes and the point types that are supported See Section 6 for more details Function Read Write 8 SetNewTmeandDae wie Opcode Tables 24 120 Send Pointers for Alarm Event and Read History Logs 128 Send Archived Daily and Hourly Read Data for the Currently Selected Day DEN and Month 130 Send Archived Hourly and Daily Read Data for Specified History Point Starting at Specified History Pointer 180 181 2 Chapter 2 Getting Going A Step by Step Approach Getting Going A Step by Step Approach Installation of the 3100 3150 ROC module is easily accomplished Installation into a system requires only a few steps Following is a step by step procedure for getting an application operational Step Example User Application 1 Identify Rack position 2 Identify PLC Data Files usage BT Buffers N7 BT Buffers N BT Control N7 BT Control N Config File N7 Config File N Data File N10 Data File N 3 Ladder Logic Example on disk and in Select the example closest to Appendix Several your application and modify as examples to choose from needed 4 Modify Logic for rack position PLC Modify these instructions as BTR Rung 2 0 needed based on the required BTW Rung 2 1 rack position Be sure to SLC configure the slot in the SLC l x 0 addresses O x 0 ad
59. r details Normal State When this light is off and the ACT light is blinking quickly the module is actively Block Transferring data with the SLC Indicates that Block Transfers between the Eco M LM RE and the Eco M LM RE have failed Normal State When the error LED is off and the related port port is actively transferring data there are no communication errors Periodic communication errors are occurring during data communications See Section 4 to determine the error condition This LED will stay on under several conditions CTS input is not being satisfied Port Configuration Error System Configuration Error Unsuccessful comm on ROC slave Recurring error condition on ROC master PRT1 Green Blink The port is communicating either transmitting or receiving PRT2 data Troubleshooting General In order to assist in the troubleshooting of the module the following tables have been put together to assist you Please use the following to help in using the module but if you have additional questions or problems please do not hesitate to contact us The entries in this section have been placed in the order in which the problems would most likely occur after powering up the module Chapter 7 Diagnostics and Troubleshooting Problem Description Steps to take BPLN light is on SLC CFG light does not clear after power up no ERR LED CFG light does not clear after power up w ERR LED CFG light toggles Module is not t
60. ransmitting Error Code 255 in Status Table Overwriting data blocks Data swapping is occurring 3100 only New configuration values are not being accepted by the module The BPLN light comes on when the module does not think that the SLC is in the run mode i e SLC is in PGM or is Faulted If the SLC is running then verify the following Verify the SLC Status File to be sure the slot is enabled The Transfer Enable Done Bits I O Bits 0 for the slot with the module must be controlled by the ladder logic See Section 2 x for details or the example ladder logic in the Appendix If the ladder logic for the module is in a subroutine file verify that there is a JSR command calling the SBR The 255 BTW Block ID number is not being detected by the module This could be due to a Block Transfer failure PLC or to an error in the ladder logic preventing the 255 value from being moved to the BTW buffer If the BPLN light has been cleared then several of the Port and System configuration values are value checked by the module to be sure that legal entries have been entered in the data table Verify the Error Status Table for an indication of a configuration error Under normal conditions the CFG LED will clear immediately after receipt If the CFG light toggles this usually indicates that the logic condition which places the 255 Block ID value in the BTW buffer is not being cleared Check the ladder logic to be sure that the co
61. re Read Block Count This value represents the number of 50 word data blocks which are to be transferred from the ROC Module to the processor The blocks returned from the module start at the value entered in the Read Block Start register and increments from there Write Block Count This value represents the number of 50 word data blocks which are to be transferred from the processor to the ROC Module Command Block Count This value represents the number of 50 word Command Blocks which are to be transferred from the processor to the ROC Module These values are used by the module in order to determine how the BTW and BTR Block ID Codes are to be manipulated Part of the functionality that the module provides is to control the incrementing and resetting of the BTR and BTW Block ID codes This was done in the interest of limiting the amount of ladder logic required to support the module Module Operation As are result of the configuration parameters entered the module will cycle through the range of BTW and BTR Blocks The cycle is based on the following equations BTW Block ID if BTW Block ID gt Write Block Cnt then BTW Block ID 80 elseif BTW Block ID gt 80 Command Block Ont then BTW Block ID Write Block Start else BTW block ID BTW block ID 1 BTR Block ID if BTR Block ID gt Read Block Cnt then BTR Block ID Read Block Start else BTR block ID BTR block ID 1 As an example assume that we are configured wi
62. ress in the module from which the TLP data to be sent to the slave should be read The first word is Point type the second is Point Logic number and the third is Parameter number Enter a 0 to output parameter data from internal database address 0 Dest Addr Starting word address in the module from which the data to be written to the module is obtained The first word corresponds to the TLP in the first location of Source Addr Type Type represents the number of byte in the data type All of the data written with one command must be of the same type Valid values are 4 floating point 2 integer and 1 byte 6 1 1 Opcode 180 and 181 Examples The first command example is using an opcode 180 to read 2 data points The second writes data to the same two data points The commands are shown below Chapter 6 Fisher ROC Command Configuration 1 2 3 4 5 8 9 SLV SLV OP SRC POLL STORE UNIT GROUP CODE CNT ADDR TIME FWD 25 2 180 2 25 2 181 2 0 0 0 0 0 0 The TLP for the 2 points are stored the module starting at address 0 set by the SRC ADDR of the command In this example we will assume that N10 0 maps to address 0 of the module database This example is set up for reading and writing to Point type 3 Analog Input logical numbers 0 and 1 and parameter 2 Scan Period The value in N10 0 is the point type for the first data point N10 1 holds the logical number and N10 2 contains the parameter number for the first data
63. s Swap type Polling Time Command Control Mode d Appendix B Product Specifications Allows individual command execution control to be done in ladder logic enabling a list of commands to be executed based on events in the PLC SLC Individual command Done and Error bits available Individual Command Error Statue codes returned to the ladder processor Hardware Specifications 7 Backplane Current Load 3100 0 65A 3150 0 15Aat5V 0 04 A at 24 V Operating Temperature 0 to 60 C Storage Temperature 40 to 85 C Connections 3100 2 DB25 Female Connectors 3150 2 DB9 Male Connectors C Appendix C Jumper Configurations Jumper Configurations Hardware Overview When purchasing the ROC product there are two available configurations These choices are as follows ProSoft Cat Num Description PLC SLC Module provided by ProSoft 3100 3150 When purchasing the module from ProSoft Technology the jumper configurations will have been factory set to default positions for testing prior to shipment Module Jumper Configurations The following section details the available jumper configurations for the 1771 and 1746 platform solutions As needed differences between the module based solutions and the firmware based solutions are highlighted 3100 for the 1771 Platform Following are the jumper positions for the ProSoft Technology 3100 ROC module 3100 N A N A N A Flash Pgm Run Mode 8 Pt
64. slot location in program Modify ladder instruction addresses as needed Setup the Communication Configuration parameters See Section 4 2 Determine each port s communication configuration requirements Master or Slave Parity Stop Bits Baud Rate RTS delay requirements Identify memory mapping requirements Set the Read Data Write Data and the Command Block Count parameters Set the Slave and Master Error Table pointers are needed for the application Setup the Command List if configuring a Master See Section 4 4 Be sure to review register map of slave device to build most effective memory map Identify the module jumper requirements See Appendix C Make up the communication cables See Section 8 Make sure that no matter what type of connection is being made up that a jumper is in place to satisfy the CTS signal Normally this signal will be jumpered to RTS Place processor into the run mode Monitor the data table for the Master and Slave Error Status values See Section 5 1 4 Table of Contents Table of Contents 1 Princ tioma lt OVELVIS Wei co rre cate ED REN e UR bete mpra 1 1 Generale Ras 12 Hardware Overview 13 General Concepts sss weit ais m 13 1 Module Power Up and Reset sse eterne tnter 1 332 Main Lo0p DOgl6 s sette RR ER D E E UTER 13 3 The Data Space in the module ies zx 134 The Backplane Data Transfer Process serere 13 5 Interlocking the Block Trans
65. t Configuration Error will be returned Chapter 4 Writing to the Module Data Addr Description RTS to TXD Delay RIS Off Delay Message Response Timeout Inter character Timeout This value represents the time in 1 ms increments to be inserted between asserting RTS and the actual transmission of data The delay if greater in duration than the hardware time delay associated with CTS will override the CTS line until the time out is complete This configurable parameter is useful w hen interfacing with modem based devices anytime line noise must be allowed to subside before data is transmitted or if data transmissions must be slowed down Valid values range from 0 to 65535 Oxffff The value in this word represents the number of 1 ms time delay increments inserted after the last character is transmitted and before RTS is dropped The module automatically inserts a one character width Off Delay assuring that RTS does not drop until after the last character has been completely sent Unless working under unusual conditions this value will normally be configured with a value of 0 Valid value range from 0 to 65535 Oxffff This register represents the message response timeout period in 1 ms increments This is the time which a port configured as a Master will wait before re transmitting a command if no response is received from the addressed slave The value is set depending on the expected slave response times
66. th the following values Read Block Cnt 4 Write Block Cnt 1 Command Block Cnt 2 Read Block Start 1 Write Block Start 0 These configuration values would lead to the following cycle of Block ID codes BTW BTR Block ID Block ID 0 1 80 2 81 3 0 4 80 1 81 2 0 3 Note that there is no implicit relationship between the absolute value in the BTW and the BTR Block ID F Appendix F Example Ladder Logic Example Ladder Logic The following example logic has been provided to assist you in developing applications more effectively These examples are provided on our FTP site ftp ftp prosoft technology com Master Mode Examples Example 1 Master Mode Basic Application ROC5EX1M PLC 5 ROC3EX1M SLC 5 03 Example 2 Master Mode w Command Control ROC5EX2M PLC 5 ROC3EX2M SLC 5 03
67. to configure the serial ports and to set up the data transfers between the module and the ladder logic 2 CommandList This set of data contains all of the parameters the module required to encode valid commands which will be transmitted out the Master port to Fisher ROC slave devices Up to 20 Command List blocks can be sent to the module for a total of 100 commands 3 Data Memory This type of memory is moved to the module to provide the data values necessary for the Master port to service write requests i e the data written to the slaves Master Port Driver Under normal applications the Master port is used primarily to issue read commands to slave devices thereby acting as a data gatherer and then transferring the data which has been read to the ladder logic The module uses the Command List entries to encode valid Fisher ROC commands As each command is executed the module scans for the next entry in the Command List If the Master port is issuing a read command the results of the read are deposited in the Data Memory If the Master port is issuing a write command data from the Data Memory is written to the slave device For every command which the module executes the status of the command can be found in the Master Error Table This table can be located anywhere in the Data Memory block and is read back into the ladder logic as part of the regular data transfer process Chapter 1 Functional Overview 1 5 ROC Support of Fishe
68. to the processor The ladder logic can use this value to determine which data to move to the ROC via the Block Transfer Write The maximum block count is 80 As an example if a value of 5 is entered the ROC will return BTW Block ID numbers 0 1 2 3 and 4 to the ladder logic See Section 4 2 If a value E MN than 80 is entered a E MN Configuration Error is activated This value represents the number of 50 word Command Blocks which are to be transferred from the processor to the ROC Module This value will be 0 if the module will not be configured with a Master port See the discussion in Section 4 1 for details on the number of Command Blocks needed The maximum block count is 20 If a value greater than 20 is entered a System Configuration Error is activated Chapter 4 Writing to the Module Data Addr Description Slave Error Block Pointer Master Error Block Pointer This value represents the relative starting position in the module s data table within which the Fisher ROC Slave Error Data Block is placed The Slave Error Table is a 20 word block containing Slave port status and several communication counters The error data can be placed anywhere in the module s data space 0 to 3999 The contents of the Error Table can then be obtained as part of the regular Register Data If a value greater than 3980 is entered a System Configuration Error is activated ROC Module Memory to 79 0 3999 Block ID 1 99 Sla
69. ve Error Table Pointer 100 Block ID 2 Slave Error Table The data regsters 100 to 119 will contain the Slave Error Table Block ID 3 Block ID 4 This value represents the relative starting position in the module s data register table within which the Master Error Data Block is placed The error block 120 words in length can be placed anywhere in the module s data space 0 to 3999 The contents of the Error Table can then be obtained as part of the regular Register Data If a value greater than 3880 is entered a System Configuration Error is activated BOC Module Memory Block ID 0 to 79 Q 999 Addre Q Block ID 0 Block ID 1 Master Error Table Block ID 3 Data registers 120 to 240 will contain the Master Error Table Block ID 4 Master Error Table Pointer 120 Chapter 4 Writing to the Module Data Addr Description Block Transfer Delay Counter This is an empirical value used by the module to balance the amount of time the module spends block transferring and the amount spent handling port communications The value entered is used as a loop counter in the module where each time through the loop the count is incremented When the count equals the Block Transfer Delay Counter a Block Transfer sequence is initiated The range on this value is 0 to 255 Example In Master Mode applications with the module in a remote rack the frequency of command execution can be improved by entering a value of 75 150 Th
70. ws COP SRC N7 412 DEST F8 10 COUNT 1 This command will move two 16 bit integer registers containing one floating point value image to the floating point file For multiple values simply increase the count field Store And Forward The Store and Forward function is achieved by setting an address value of greater than 0 in location 9 of a command This address is the starting word of the communication path for ROC to ROC communications A value of 0 disables Store and Forward When Store and Forward is used the module wraps the opcode 24 and communication path information around the command before it is sent out of the communication port Example The Store and Forward Source Address of a command is N11 40 Communication Path data is stored as the following N11 40 N11 41 N11 42 N11 43 N11 44 N11 45 N11 46 N11 47 N11 48 N11 49 7 1 Chapter 7 Diagnostics and Troubleshooting Diagnostics and Troubleshooting Several hardware diagnostics capabilities have been implemented using the LED indicator lights on the front of the module The following sections explain the meaning of the individual LEDs for both the PLC and the SLC platforms 3100 PLC Platform LED Indicators The PLC platform ROC product is based on the ProSoft CIM hardware platform The following table documents the LEDs on the 3100 ROC hardware and explains the operation of the LEDs ProSoft CIM Card ACTIVE FLT CFG BPLN
71. y that we can assure that the data in a block corresponds to the Block ID being transferred The basic ladder programming which must be implemented in an SLC application is as follows Transfer Transfer Enable Done 11 1 0 OO0 1 0 Data transfer instructions LA Cd 4 to move data from module to ladder memory Transfer Transfer Enable Done H 3 0 O0 1 0 ul Data transfer instructions to move data from ladder memory to module Transfer Done 00 1 0 0 1 3 6 SLC Processor Configuration 1 4 1 4 1 When initially setting up the SLC program file or when moving the module from one slot to another the user must configure the slot to accept the ROC module It is important that the slot containing the ProSoft module be configured as follows 1746 BAS module with 5 02 or greater configuration or enter 13106 for the module ID code Configure the MO M1 files for 64 words Configure I O for 8 words The following is a step by step on how to configure these files using Allen Bradley APS software Other software packages users should follow similar steps From the Main Menu 1 Select the correct processor program and F3 for Off line programming 2 F1 for Processor Functions 3 F1 for Change Processor Modify the processor here if necessary Note the ROC will only work with 5 02 or greater processors 4 F5 for Configure I O Select 1746 BAS module for SLC 5 02 or greater or enter 13106
72. y that we have implemented the transfer to the module in all of our example ladder logic See Appendix and Application Notes is through a two step process where Step 1 During the BTR process the module will feed the ladder logic a BTW Block ID Number in the second word of the BTR Data Buffer Ladder logic is implemented to accept this value condition it if needed and then to move the value to the actual BTW Block ID location The ladder logic to do this is shown below Chapter 4 Writing to the Module Setting up the BTW Block ID Number Located at the bottom of the BTR rung Rung 0 this logic moves the BTW Block ID Number being received from the module and offsets it by the Read Block Count N7 20 in order to assure that PLC data does not overwrite the data being returned from the module to the PLC See logic in Appendix for implementation details Step 2 During the processing of the BTW rung the ladder logic will test for the value in the BTW Block ID register and based on the value copy data from the data table into the BTW Block Transfer buffer This process requires that every BTW Block ID which will be processes be accounted for with a branch of logic An example of the ladder logic required follows EQ COP SRC N10 150 DEST N7 311 COUNT 50 U 4 SRC A N7 310 SCR B 3 Test BTW Block ID and move data to BTW Buffer

3100/3150-ROC User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents