USER MANUAL - ProSoft Technology
Contents
1. PERFORM T TRANSFER TO DATA FILE TFAL FILE ARITH LOGICAL EN Control R6 0 Length 60 DN Position ol Mode ALL ER Destination EN N7 408 N7 409 Ol Expression N7 412 4 ENCODES BT WRITE BLOCK ID MOV q MOVE Source N7 411 1l Destination N7 310 0 4 USER CFG ENCODES DOWNLOAD BT WRITE SELECT BLOCK ID B3 MOV MOVE 0 Source 255 Destination N7 310 0 4 24 Example Ladder Logic Example PLC Ladder Logic Rung 2 1 WRITES DATA COMMAND LIST OR CONFIGURATION B Sat June 7 1997 Page 3 LOCK TO MODULE This rung is responsible for transferring data to the module This data includes the command blocks 0 and 1 25 and the configuration block 255 DECODE BT READ BT WRITE BT WRITE ENABLE ENABLE BLOCK N7 400 N7 300 QU ase eee EQUAL 15 15 Source A N7 Source B lan Daf anca axis ee PRAIA ANTA Rung 2 3 END OF FILE WRITE TO BT WRITE BUFFER 4 COP COPY FILE 310 Source N7 01 0 Destination N7 311 255 Length 3012. BLOCK TRANSFER READ EN ito 15 Rack 001 Group 0 DN Module 0 Control block N7 400 ER Data file N7 410 Length 64 Continuous N DECODE TRANSFER BT READ BTR BLOCK BLOCK ID ID VALUE LIM MOV LIMIT TEST CIRC MOVE Low limit 0 Source N7 410 EN 1l Test N7 410 Destination N7 409 111 50 High limit Lietta i EI INTEGER T FILE NUMBER MOV MOVE Source 10 Destination N7 408 0 4 DECODE NORMALIZE BT READ TO 0 5 BLOCK ID RANGE LIM SUB LIMIT TEST CIRC SUBTRACT Low limit 12 Source A N7 410 EN 1 Test N7 410 Source B 12 111 High limit 23 Destination N7 409 EN 50 4 INTEGER FILE NUMBER MOV gt MOVE Source 11 Destination N7 408 0 4 vvv vvv Example PLC Ladder Logic Program Listing Report Example Ladder Logic Sat June 7 1997 Page 2 PLC 5 25 File MDA16 Rung 2 DECODE CALC BT READ OFFSET BLOCK ID POINTER TXEIMZ e R TORTE FELIMIT TEST CIRO 4 c rrtlosnocote COMPUTE Low limit 0 Destination N7 409 50 Test N7 410 Expression 1 N7 409 60 High limit 23 4
3. 3100 2 DB25 Female Connectors 3150 2 DB9 Male Connectors 2 1 2 1 1 Writing Data to the Module Writing Data to the Module 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 discussion 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 PLC and SLC ladder logic are included in Appendix A In order for the ProSoft Technology module to function the PLC must be in the RUN mode or in the REM RUN mode If in any other mode Fault PGM the block transfers between the PLC and the module will stop and communications will halt until block transfers resume Block Transferring Data to the Module Data transfer to the module from the processor is executed through the Block Transfer Write function The different t
4. bara aa ae se en NA NI tl t USER CFG DOWNLOAD SELECT B3 E and RR MA CARA U 0 BT WRITE TO MODULE TBTW BLOCK TRANSFER WRITE EN Rack 00 Group 0 DN Module ol Control block N7 300 ER Data file N7 310 Length 64 Continuous N 4 lea Ph aA GIRS A ARG pend daba dO Nb RE d Example Ladder Logic Example PLC Ladder Logic Sat June 7 1997 Data Table Report PLC 5 25 File MDA16 Data Table File N7 0 Address 0 1 2 3 4 5 6 7 8 9 N7 0 5 5 0 0 0 0 0 0 0 0 N7 10 0 0 0 0 0 0 0 0 0 0 N7 20 0 0 0 0 0 0 0 0 0 0 File N10 0 Address 0 1 2 3 4 5 6 7 8 9 N10 0 3864 0 0 0 0 0 1 0 0 0 N10 10 6 2 1997 6 40 28 0 0 0 0 N10 20 1211 516 1 32296 16334 O 24257 1 0 0 N10 30 1 zd 152 V2T 132 135 0 0 0 0 N10 40 20040 13101 18761 129 153 8898 2624 8898 3356 0 N10 50 0 0 0 0 0 0 0 0 0 0 N10 60 20040 13101 18761 129 122 8898 2624 8898 3356 0 N10 70 0 0 0 0 0 0 0 0 0 0 N10 80 20040 13101 18761 129 131 8898 2624 8898 3356 0 N10 90 0 0 0 0 0 0 0 0 0 0 N10 100 20040 13101 18761 129 135 8898 2624 8898 3356 0 N10 110 0 0 0 0 0 0 0 0 0 0 N10 120 0 0 0 0 0 0 0 0 0 0 N10 130 0 0 0 0 0 0 0 0 0 0 N10 140 0 0 0 0 0 0 0 0 0 0 N10 150 0 0 0 0 0 0 0 0 0 0 N10 160 0 0 0 0 0 0 0 0 0 0 N10 170 0 0 0 0 0 0 0 0 0 0 N10 180 0 0 0 0 0 0 0 0 0 0 N10 190 0 0 0 0 0 0 0 0 0 0 N10 200 0 0 0 0 0 0 0 0 0 0 Extend file to 720 words in length N10 7
5. 8 pt mode only 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 See options on module The default from factory is RS 232 but all options are supported by the MDA 16 firmware 3150 for the 1746 Platform Following are the jumper positions for the ProSoft Technology 3150 MDA 16 module 3150 MDA 16 As Needed See Below As Needed See Below N A N A Jumper Configurations JW1 2 RS configuration for port 1 and 2 The default from factory is RS 232 but all options are supported by the MDA 16 firmware Communication Port Jumper Settings for 3150 Modules JW1 amp JW2 Jumper JW1 Settings Odri Daughter Board Daughter Board 3300 Daughter Board Mother Board Daughter Board Daughter JW3 s Board JW4 Jumper JW2 Settings Daughter Board Daughter Board eee Daughter Board TIR Daughter Board mg RS 232 RS 422 4 wire RS 485 2 wire RS 232 RS 422 4 wire RS 485 2 wire 20 SLC Programming Considerations C 21 SLC Programming Considerations The 3150 MDA 16 is also very easy to get operational In order to implement the sample logic the user must make sure that the correct processor and rack size match up Al
6. MDA 16 complete the following steps PLC 5 MDA16 SLC 5 03 MDA16503 See Appendix for SLC programming tips b Edit the ladder logic provided on disk as needed for the application Verify rack and slot location in program Modify ladder instruction addresses as needed c Setup the Communication Configuration parameters Determine each port s communication configuration requirements d Setup the Polling List for each port e Identify the jumper requirements See Appendix f Make up the communication cables g Place processor into the run mode h Monitor the data table for the Data and Error Status values Product Revision History Product Revision History 06 07 97 Revision 1 0 Initial release of product 06 23 97 Revision 1 1 Added support for command 0x54 and expanded the point map to support two analyzers 07 12 97 Revision 1 2 Added support for command 0x50 and 0x52 Table of Contents Table of Contents Implementation Guide i Revision History ii 12 PrOdUCBRSPECIHICATIONS teli ili NAMA DNE MEAN ANA Ae 1 1 4 Operating Specifications iii 1 1 2 Hardware Specifications nana 1 2 Writng Datato the Module 2 inn annual Ne iii 2 2 1 Block Transferring Data to the Module 2 2 1 1 Communications Configuration BTW Block ID 255 2 3 Reading From the Module 5 3 1 Transferring data from the MOdule 5 3 1 1 The Read Da
7. Rate 300 Baud 600 Baud 1200 Baud 2400 Baud 4800 Baud 9600 Baud Polling Timeout This value is used by the module to detect when a timeout condition in the communications from the SYSTEM 16 has occurred By default if a value of O is entered the module will use 30 seconds Valid values range from O to 65535 0 to Reading from the Module 3 Reading From the Module This section provides reference level details on the transfer of data from the PLC SLC processor to the module 3 1 Transferring data from the module When the Master port driver reads data from a slave the resulting data is placed into the ProSoft module s data space This data space is broken down into two 2 720 word data blocks with each 720 word block representing the data from one 1 slave port The following diagram shows this structure Word 0 Port Port 1 2 719 In order to get this data into the PLC SLC the blocks are broken down into 60 word pages and transferred to the ladder logic across the backplane using the standard BTR or M1 instructions The following sections detail the structure of this data and the mechanism by which all of the data is transferred 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 3 1 1 The Read Data Block Structure The BTR buffer definition is BTR Block ID The ladder logic u
8. Reading from the Module Data Offset 670 Month Analyzer 2 Returned from 0x56 671 Day 672 Year 673 Hour Analyzer 2 Returned from 0x56 674 Minute ae Second Analytics High Byte Analyzer 2 Returned from 0x56 Gas Number Low Byte 677 Gas Abbreviation Analyzer 2 Returned from 0x56 678 679 680 jFormatCode Analyzer 2 Returned from 0x56 685 me SEE c ccr Ni 686 Spare __ 687 spare __ 688 spare __ PC 690 Month 691 Day 692 Year 693 Hour 694 Minute 695 Second pes i 69 Fault Number 697 Module Code qo 698 jPointGrup qo 699 SwitehMast __ 705 Spare 706 Spare __ 707 Spare pool A me M 709 Spare Product Information Structure OM dl STO data is only returned for Slave 1 See below for structure 3 2 2 Sequential Results Data Structure Up to 16 Sequential Results Data Blocks Points 0 to Points 15 are returned from each SYSTEM 16 These blocks have been turned into a 10 word structure to allow viewing in the PLC SLC data table to be easier The structure of this data is as follows Note that the structure is shown only for Point 0 This structure repeats itself 32 times on 20 words offsets Reading from the Module Data Addr Description S Date Month Date returned with last sample Date Day Date Year 13 Time Hour Time returned with last sample The Second
9. 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 O ProSoft Technology Inc 1997 Quick Start Guide Quick Start Implementation Guide Integration of the 3100 3150 MDA 16 module into a PLC 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 provided on disk with the module or available off 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 that will impact the long term success of the installation Starting with one of the ladder logic programs provided on disk with the module complete the following steps If hand entering the ladder logic by hand for the SLC remember the following Configure the slot as follows Other ID Code xxxxx Input File Length 8 Output File Length 8 Scanned Input File Length 8 Scanned Output File Length 8 MO File Length 64 M1 File Length 64 a Starting with one of the ladder logic programs provided on disk with the
10. 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 Jumper Configurations B Jumper Configurations Hardware Overview When purchasing the MDA 16 product there are two choices These choices are as follows ProSoft Cat Num Description PLC SLC Module provided by ProSoft 3100 3150 When purchasing the module from ProSoft Technology many of the jumper configurations will have been factory set When purchasing the firmware from ProSoft Technology and the Allen Bradley module from another source particular attention must be paid to hardware configuration 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 MDA 16 module 3100 N A N A N A Not Used 8 Pt Not Used Enabled As Needed As Needed JW5 Backplane 8 16 point 8 Point The module should be operated in the
11. is not latched and will therefore clear to O on the first successful communications The values which can be expected in the field are Value Description All OK TBD TBD Error in Response Timeout Error Module Config Error Checksum Error TX Fail Verify RTS CTS jumper Read Command Done Bits These bits indicate the execution of the particular command The module will clear the bits immediately after the block transfer to assure that they are not held on Value Description Sequential Sample Results 0X30 Current System Status 0x53 Gas Table Data 0x56 Fault 0x61 Point Config 0x54 System Config 0x50 Point Enable Masks 0x52 Unsupported Op Code State Retummedfrom 0x53 4 Month Date returned from 0x53 5 Day 6 Year 7 Hour Time returned from 0x53 8 Minute 9 Second Reading from the Module Data Addr Description Sequential Sample Results See Section 3 2 2 Analyzer 1 Point 0 to Point 15 20 words per unit Sequential Sample Results See Section 3 2 2 Analyzer 2 Point 0 to Point 15 20 words per unit 650 Month Analyzer 1 Returned from 0x56 651 Day 652 Year 653 Hour Analyzer 1 Returned from 0x56 654 Minute 655 Second Gas Number Low Byte 657 Gas Abbreviation Analyzer 1 Returned from 0x56 658 659 660 Format Code Anayzerii RetumedfromOx56 662 663 664 66 Spare 66 Spare __ 667 Spare __ 668 Spare 669 Spare
12. 00 0 0 0 0 0 0 0 0 0 0 N10 710 19780 16692 12590 12336 12594 12338 0 0 0 0 26 Example Ladder Logic File N11 0 Address 0 1 2 3 N11 0 17 53 0 0 1 2 N11 10 6 2 1997 6 N11 20 1211 516 sl 32296 N11 30 1 153 121 N11 40 20040 13101 18761 129 N11 50 0 0 0 0 N11 60 20040 13101 18761 129 N11 70 0 0 0 0 N11 80 20040 13101 18761 129 N11 90 0 0 0 0 N11 100 20040 13101 18761 129 N11 110 0 0 0 0 N11 120 0 0 0 0 N11 130 0 0 0 0 N11 140 0 0 0 0 NILi150 0 0 0 0 N11 160 0 0 0 0 NIIT 0 0 0 0 N11 180 0 0 0 0 N11 190 0 0 0 0 Extend file to 720 words in length N11 700 0 0 0 0 N11 710 0 0 0 0 27 40 16334 132 152 121 131 bh w no SOS O SOCOS DO 200000000 DO 24257 2624 2624 2624 2624 0000000200 00 2 889 889 889 889 oo co 8 8 8 OOOOOOOO O 385 335 335 335 OOOOOOOOORORO dT ae S N a D ae a a ESSES UL DO DO OS CS OS OS OS OS OS
13. 3100 3150 MDA 16 MDA Scientific Sys 16 Interface Module Revision 1 0 USER MANUAL June 1997 ProSoft Technology Inc 9801 Camino Media Suite 105 Bakersfield CA 93311 prosoft prosoft technology com http www prosoft technology com Please Read This Notice Successful application of the MDA 16 module requires a reasonable working knowledge of the Allen Bradley PLC 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 MDA 16 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 product Reproduction of the contents of this manual in whole or in part without written permission from ProSoft Technology Inc is prohibited Information in this manual is subject to change without notice and does not represent
14. Configuration block I 255 is received from the processor ladder logic 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 Normal State When this light is off and the ACT light is blinking quickly the module is actively Block Transferring data with the SLC aa module have failed ERR2 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 MDA 16 slave Recurring error condition on MDA 16 master TxRx1 Green Blink The port is communicating either transmitting or receiving TxRx2 data 13 5 3 Diagnostics and Troubleshooting Troubleshooting 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 BPLN light is on SLC The BPLN light comes on when the module does not think that the SLC
15. EIN 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 one 1 year Warranty Procedure Upon return of the hardware Product ProSoft will at its option repair or replace Product at no additional charge
16. S 422 modes 6 Cable Connections Cable Connections The following diagrams show the connection requirements for the ports on the 3100 and 3150 modules 3100 Module RS 422 4 Wire Connection The jumper on the module must be set in the RS 422 position for all 4 wire applications 3150 Module RS 422 4 Wire Connection The jumper on the module must be set in the RS 422 position for all 4 wire applications 3100 MCM SYSTEM 16 DB 25 Pin Female Device TxD Pin 17 TxD Pin 16 RxD Pin 15 RxD Pin 14 RTS RTS CTS jumper must be installed for CTS card to communicate GND GND Optional 3150 MCM SYSTEM 16 DB 9 Pin Male Device TxD Pin 17 TxD Pin 16 RxD Pin 15 RxD Pin 14 RTS RTS CTS jumper must be installed for CTS card to communicate GND GND Optional RS 422 Ti 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 16 Support Service and Warranty Appendix A 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 326 7066 661 664 7233 fax E mail address prosoft prosoft technology co
17. 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 The 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 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 R
18. ands The ProSoft Technology MDA 16 module Master driver supports several commands from the MDA 16 Command set MDA 16 Commands The MDA 16 module supports a command subset of the Protocol Specification consisting primarily of the commands required to intialize and read data from several units The following sections detail the different commands supported by the module 4 1 1 0x30 Sequential Sample Results This command block contains the sequential sample results for up to 16 points A block of 10 words has been allowed in the data table per point 0x53 Current System State This command delivers the current system state from the SYSTEM 16 0x56 Gas Table Data This command contains the analytical gas information Two spaces have been allowed in the data table one for analyzer 1 and one for analyzer 2 0x61 Fault The command contains the current fault condition This command is only sent when a fault condition occurs 0x54 Point Configuration The command contains the point configuration data for a point The module extracts only the Alarm Level values from this command ie date and time and the other parameters are not extracted 0x50 System Configuration The command contains the system configuration data 0x52 Point Enable Masks The command contains the Point Enable Mask configuration data 5 1 Diagnostics and Troubleshooting Diagnostics amp Troubleshooting Several hardware diagno
19. blocks These individual 60 word blocks are paged across the backplane within the BTR Buffer structure discussed above Using the BTR Block ID number the ladder logic is able to determine where to place the data in the ladder logic memory Word 0 719 Port 1 Block 0 Block 1 Each block represents 60 words Block 1 of the Slave Data structure Block2 Block3 The following diagram shows the Slave amp 1 Data block broken down into its 60 word blocks and the corresponding BTR Block ID number for each of the blocks The following table shows the BTR Block ID numbering for the two slaves BERE 1 0to59 o 12 36010419 6 18 48010539 8 20 54010599 9 21 Reading from the Module 3 2 1 The Slave Data Block Structure The data structure for each slave is predefined and was developed during the development of the module As discussed above the individual slave data is stored in a 240 word data block The structure of the data block is as follows Data Addr Description Offset Communication Counter This value represents a 0 to 32767 rollover counter that increments each time communication with the slave occurs Incrementing is independent of the command executed Communicaton Status Error This register is used to indicate that status of communications between the module and the particular slave A non zero number indicates the type of communicatoin problem which is occuring This value
20. cifications The 3100 3150 MDA 16 MDA Scientific SYSTEM 16 Interface Module product family allows Allen Bradley 1771 and 1746 I O compatible processors to easily interface with MDA Scientific SYSTEM 16 gas monitoring hardware See 3100 3150 MDA 4 for a CM4 solution 1 1 Operating Specifications The MDA 16 product includes the following standard features Two fully configurable serial ports each capable of supporting one SYSTEM 16 unit Supports one SYSTEM 16 unit per serial port Memory mapping will be pre defined in the module to ease implementation in the ladder program RS 422 connection from each port directly to the SYSTEM 16 units Software configuration From processor ladder logic Char Size 8 bits fixed Parity s None fixed Stop Bit 1 fixed Baud Rate 2 400 TO 9 600 RTS to TxD 50 ms fixed Timeout 0 to 65 seconds Response time The protocol drivers are 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 Supported SYSTEM 16 command codes Read Comands 0x30 Sequential Sample Results 0x53 Current System State 0x56 Gas Table Data 0x61 Fault Error Codes returned to the ladder processor 1 2 Hardware Specifications Backplane Current Load 3100 0 65A 3150 0 15Aat5V 0 04 A at 24 V Operating Temperature O to 60 C Storage Temperature 40 to 85 C Connections
21. d 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 Press the 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 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 Example Buffer Data Addr o BTWBlock ID Port Module Configuration Spare Spare 6 N75 Spare 8 N77 Spre 9 N78 Spare The structure of the Port and Module Configuration Data block and the meaning of each of the configuration parameters is outlined in the following table Writing Data to the Module Baud Rate Port 1 The baud rate at which the port is to operate The available Baud Rate Port 2 configurations are as follows Value Baud
22. e processor platforms This logic can be incorporated directly as is or if desired modified as needed for the application Data Files The examples use the same memory map for both of the platforms with the exception of the actual block transfer data and control files The memory map for the example application has been detailed in the attached data table listing In this example application the following configuration and data table layout is used Note that the application programmer may select any PLC data files Integer if the files used in the example are not available Port Port Word L E 9 Block0 Block4 Blockl Block5 Block2 Block6 Block3 Block7 239 N10 N11 Note that the data file listings that are included in this manual do not reflect actual values collected from the SYSTEM 16 instruments 22 Example Ladder Logic Example PLC Ladder Logic Program Listing Report Rung 2 0 BT READ AND REGISTER TRANSFER FROM MODULE DECODING 23 BT READ from module Sat June 7 1997 Page 1 PLC 5 25 File MDA16 Rung 2 0 This rung of logic is responsible for transferring data from the module into the PLC data table The paging is controlled by the BTR Block ID number word 0 in Data file See manual for complete explanation BT READ BT WRITE BT READ FROM ENABLE ENABLE MODULE N7 300 N7 400 BTR tars T
23. ing N 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 If in 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 Error Code 255 in Status This is caused by only one thing a missing CTS input on the port Table 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 Problem Description Steps to take Overwriting data blocks 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 Data swapping is Under several circumstances data swapping in the module has 14 Diagnostics and Troubleshooting 15 occurring 3100 only New configuration values are not being accepted by the module Error Codes being returned in locations with no commands Master Configuration RX1 or RX2 on continuously 3100 only occurred This swapping has
24. is in the run mode i e SLC is in PGM or is Faulted If the SLC is running then verify the following e Verify the SLC Status File to be sure the slot is enabled The Transfer Enable Done Bits I O Bits O 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 CFG light does not clear The 255 BTW Block ID number is not being detected by the after power up no ERR module This could be due to a Block Transfer failure PLC or to LED an error in the ladder logic preventing the 255 value from being moved to the BTW buffer CFG light does not clear If the BPLN light has been cleared then several of the Port and after power up w ERR System configuration values are value checked by the module to LED be sure that legal entries have been entered in the data table Verify the Error Status Table for an indication of a configuration error CFG light toggles 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 condition moving the 255 value is not held true Module is not transmitting Presuming that the processor is in run verify the follow
25. m Web Site http www 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 Block Transfers operation LED patterns An after hours answering system on the Bakersfield number allows pager access to one of our technical and or application support engineers at any time to answer the questions that are important to you Module Service and Repair The MCM 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 necessary to obtain an RMA number from ProSoft Technology Please call the factory for this number and display the number prominently o
26. n 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 Support Service and Warranty 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 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 shipping container or equivalent Contact ProSoft Customer Service for further information Limitation of Liability EXCEPT AS EXPRESSLY PROVIDED HER
27. ransfers between the PLC and the module have failed Not activated in the initial release of the product ERR1 LED1 Amber Normal State When the error LED is off and the related ERR2 LED2 port is actively transferring data there are no communication errors R G er ne communications On This LED will stay on under several conditions CTS input is not being satisfied Port Configuration Error System Configuration Error Unsuccessful comm on MDA 16 slave Recurring error condition on MDA 16 master 12 Diagnostics and Troubleshooting Tx1 PT1X Green Blink The port is transmitting data Tx2 PT2X Rx1 PTIR Green Blink The port is receiving data Rx2 PT2R 5 2 3150 SLC Platform The following table documents the LEDs for the 3150 MDA 16 module 3150 MDA 16 COMMUNICATIONS E ACT sy FAULT EM crc EH BPLN EM PRT ERRI EM PRT2 DO ERR2 DE ue Dtm Name Color Fast successfull Block Transferring with the SLC S NE may be some other problem Blink Indicates the module has somehow entered the Basic 1 Sec Programming Mode Verify jumper JW3 BAS only configuration If all are correct then contact the factor The module is attempting to Block Transfer with the SLC and has failed The SLC may be in the PGM mode or may be faulted Not in initial release SER R ace background diagnostics NI NAME 9 0 c diagnostics s contact factory for technical sup port Wis io a thistime This light blinks every time a Module
28. s field have been left 14 Time Minute off to gain a word register and because it appears that the EIE Gl 16 does not use the second field LB qu High Byte E es Number Low Byte TG Alarm Level 1 Returned from Command 0x54 Alarm Level 2 Returned from Command 0x54 3 2 3 Product Information Data Structure Product revision information which may be useful during debuging and troubleshooting in the future is included in this data structure This data block is only returned with the data from slave 1 Therefore it will be returned at the tail end of BTR Block ID 4 Data Addr Description Offset 710 Product Name These two words represent the product name of the module in 711 an ASCII representation In the case of the 3750 product the letters MDA4 should be displayed when placing the programming software in the ASCII data representation mode Product Revision These two words represent the product revision 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 714 Product Operating System This word represents the module s internal operating system revision level in an ASCII representation 715 Product Run Number This number represents the batch number that your particular chip belongs to in an ASCII representation 10 Protocol Commands 4 1 Protocol Comm
29. ses 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 0 The relationship between the BTR Block ID number and the register table can be put into an equation Starting Register Address Block ID Number 60 Valid codes are between 0 and 23 Each slave will consume 12 blocks 3 2 Continued Word Name Pescription BTW Block ID i Reading from the Module The module returns this value to the processor to be used to enable the movement of Command data to the module The BTW Block ID number is developed by the module Valid codes are BTW Code Description 0 Null 255 Module Configuration This data will contain data received from the slaves 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 Reading Data from the Module BTR Block ID 0 and 23 In order to understand the movement of data from the module to the ladder memory it is important to understand the building of the memory map in the module Shown earlier in the diagram above is that fact that the module stores the Slave Data in individual 240 word blocks The transfer of this data is accomplished by breaking each of the 240 word blocks down into four 4 60 words
30. so should it be necessary to re locate the MDA 16 module the user should be certain to configure the correct slot as a 1746 BAS 5 02 Configuration 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 MDA 16 module It is important that the slot containing the ProSoft module be configured as follows 1746 BAS module 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 ICOM software users should follow similar steps From the Main Menu 1 Select the correct processor program and F3 for Offline programming 2 F1 for Processor Functions 3 F1 for Change Processor Modify the processor here if necessary Note the MDA 16 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 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 Example Ladder Logic D Example Ladder Logic Overview The following ladder logic provides an example for the ladder logic necessary to integrate the 3100 MDA 16 and the 3150 MDA 16 modules into their respectiv
31. stics 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 The following table documents the LEDs for the 3100 MDA 16 module ProSoft CIM Card ACTIVE OO FLT CFG OO BPLN ERR1 OO ERR2 TXD1 OO TXD2 RXD1 OO RXD2 LE com aa esco a CIM DB B Color Fast successfull Block Transferring with the PLC there may be some other problem Blink Indicates the module has somehow entered the Basic 1 Sec Programming Mode Verify jumper JW4 DB B only configuration If all are correct then contact the factor The module is attempting to Block Transfer with the PLC and has failed The PLC may be in the PGM mode or may be faulted CR RE aaa background diagnostics ll diagnostics Please contact factory for technical support LT ES VA Normal state No configuration related activity is occurring at this time OZN Sa RI This light blinks every time a Module Configuration block ID 255 is received from the processor ladder logic On 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 BPLN BTLO Off Normal State When this light is off and the ACT light is blinking guickly the module is actively Block Transferring data with the PLC On Indicates that Block T
32. ta Block Structure 5 3 2 Reading Data from the Module BTR Block ID 0 and 23 6 3 2 1 The Slave Data Block Structure 7 3 2 2 Sequential Results Data Structure nn 9 3 2 3 Product Information Data Structure eee e 10 4 Protocol GOmmlards teniente ete bd sa bete bla canacienalosalangicngiei siate dicon ica 11 4 1 MDA 16 Commands tenerte Era ERR ERE ee aen a Eta LL ikebane etos 11 4 1 1 0x30 Sequential Sample Results 11 4 1 2 0x53 Current System State 11 4 39 0xb6 Gas Table Data erbario 11 coc 19T 11 4 1 5 0x54 Point Configuration i 11 4 1 6 0x50 System Configuration ee 11 4 1 7 0x52 Point Enable MaskS 11 5 Diagnostics amp Troubleshooting eee 12 Sal 29100 PEG Platon cities ener reor t aa dia aaa dica ecciesie va a 12 5 2 29150 SEC Platf O M enal een eret rare Fett setate ta iesu aiaa 13 Did Tro bleshoOtllig soient eee teat venah rne teda tela nila be Pra eL ed 14 6 Gable CONN CONS em Ec T 16 APPEndIX ciet tetti tir rir eret EO TE ER ENE TE VO 17 A Support Service and Warranty 17 B Jumper Configurations eir ett a Lands EA tina cba bete Lalo naana babi aka 19 C SLC Programming ConsiderationS nennen nnne nnne nnns 21 D Example Ladder LOGIC itt rte reet e tab bete de Li tad 22 Product Specifications 1 Product Spe
33. ypes of data which are transferred require slightly different data block structures but the basic data structure is BTW Block ID A block page identifier code This code is used by the ProSoft module to determine what to do with the data block Valid codes are BTW Code Description 0 1 Command Control and Data 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 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 when the parameters must be changed Writing Data to the Module 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 comman
Download Pdf Manuals
Related Search