Home

3100/3150-CBM User Manual

1. Command Enable ENCODES 3 BLOCK GRT MOV Greater Than A gt B Move Source A N7 120 Source 102 0 gt 102 gt Source B 0 Dest MO 1 0 0 gt 9 gt USER CFG DOWNLOAD ENCODES SELECT BLOCK B3 0 MOV 4 H Move 0 Source 255 255 lt Dest MO 1 0 9 gt WRITE DATA TO MODULE This logic moves the Device Definition Files the Command Lists the Write Commands and the module configuration data to the module for handling TRANSFER TRANSFER ENABLE DONE must be must be BT WRITE BUILD PTR in logic in logic TO MODULE FOR COP 1 1 0 1 LIM CPT 0002 4h A Limit Test Compute 0 0 Low Lim 80 Dest N7 30 1746 BAS 5 02 1746 BAS 5 02 80 lt 50 lt Test MO0 1 0 Expression M0 1 0 80 50 9 gt High Lim 99 99 lt TRANSFER TO MODULE COP Copy File Source N11 N7 30 Dest M0 1 1 Length 50 BT WRITE BUILD PTR TO MODULE FOR COP LIM CPT Limit Test Compute Low Lim 100 Dest N7 30 100 lt 50 lt Test M0 1 0 Expression M0 1 0 100 0 lt High Lim 119 119 lt TRANSFER TO MODULE COP Copy File Source N12 N7 30 Dest M0 1 1 Length 10 Page 2 Monday June 28 1999 13 54 42 CBM503 LAD 2 CBM 503 Total Rungs in File 4 0003 MOV Move Source 0 0 gt Dest N7 N7 31 0 gt BT WRITE TRANSFER TO MODULE TO MODULE LIM COP Li
2. 006 020 BoilerMedium 1 Steam 2 Hot Water 001 108 BurnerStatus 001 115 BurnerStatusExt 001 132 SequenceTimer 001 009 OperPressure 001 010 OperTemperatur 001 125 FireRate 001 008 ControlSource 001 139 FuelSelection 001 057 GasPressure 001 062 OilPressure 001 067 OilTemperature 001 018 PercentInput 001 123 FireRateMode 001 004 StackTemp 001 005 KeyboardMode 001 072 MaxFire 001 024 LoFire Group 002 Diagnostic DIGITAL 002 155 GasFuelSelect 002 156 OilFuelSelect 002 157 Term51 002 158 PrelgnInterlock 002 159 RecycleLimit 002 160 LockoutInterlock 002 161 PilotValve 002 162 GasMainValve 002 163 OilMainValve 002 164 AtomizingAirPrSw 002 165 BurnerSwitch DMD 002 166 Term50 Group 003 Diagnostic ANALOG Honeywell Point Maps 003 003 003 003 003 003 003 Group 019 148 149 150 151 152 154 WaterTempTerm32 FlameSignal GasPressureTerm46 OilPressureTerm43 OilTempTerm34 StmPressTerm37 DampMotorTerm40 004 Control Setpoints 004 004 004 004 004 004 004 004 004 Group 027 030 033 036 039 042 055 056 071 BoilerOff BoilerOn OperSetpoint SetbkBoileroff SetbkBoilerOn SetbackSetPt Setback Capable Setback Mode Response 005 Limits Alarms 005 005 005 005 005 005 016 017 058 059 060 063 StackTempHiAlarm PercentHiAlarm NomGasPress oGasLimit HiGasLimi
3. Fault Faul Faul Faul Burn Burn Fire SequenceTimer Fuel t Hours t Code erStatus Rate Selectio t Cycle t Hours t Code erStatus Rate Selectio DDNDDDDDHDAUMUNUUNHHHHHFP PEP PPP ds ds BPWWWWWWWWWNNNNNNNNNFRRPRPRR RP Fault Faul Faul Faul Burn Burn Fire SequenceTimer Fuel Fault Faul Faul Faul Burn Burn Fire SequenceTimer Fuel Fault Faul Faul Faul Burn Burn Fire SequenceTimer Fuel Fault Faul Faul Faul Burn Burn Fire t Cycle t Hours t Code erStatus Rate Selectio t Cycle t Hours t Code erStatus erStatus l Rate Selectio t Cycle t Hours t Code erStatus erStatus Rate Selectio t Cycle t Hours t Code erStatus ersStatus Rate Message erStatusExt n Message erStatusExt n t Message erStatusExt n Message Ext n Message Ext n t Message EXt SequenceTimer FuelSelection Honeywell Point Maps ERR E HE FE FE FE E E FE TE FE FE HE HE HEE HEH H HE 07700 POINT CATEGORIES FEE HE HETE FE FE EE E AE HE FE FE FE E E AE TE FE FE HE HE HEE HEH H HE Group 006 Configuration 009 o o PBROBNYINWOAWUOWUO oooooooo a NF RO 039 008 007 032 004 001 002 033 003 040 006 005 026 027 028 029 030 031 006 006
4. 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 006 Answe Comml Dial Dial Dial Dial Dial Dial Dial rRings ntNetworkAddr DialMethod utBaudRatel utBaudRate2 utBaudRate3 utCeasel utCease2 utCease3 Delayl Dial Dial Delay2 Delay3 Dial Dial Dial Dial Dial Dial Inact OC O O OO O OO OD O O 00 Ce TE sce CE ETE cr Ce T Local Major Minor DeviceTypel DeviceType2 DeviceType3 Phonel Phone2 utPhone3 ivityTimeout LocalBaudRate DeviceType LocalNetworkAddr LocalOnlyReporting Revision Revision ModemNetworkAddr Progr Respo amident nseTimeout SiteName SitePassword 51 lot2NetworkAddr lot3NetworkAddr lot4NetworkAddr lot5NetworkAddr lot 6NetworkAddr NNNNN otiNetworkAddr Honeywell Point Maps FEAE FE E HE HE FE FE FE FE HE E FE FE FE FE FE E FE FE FE FE E HE HHHH HE RM78xx POINT CATEGORIES FEAE FE E HE HE FE FE FE FE HE E FE FE FE FE HE E HE FE FE FE E 8 48 50 Group 001 Operating Status 001 009 BurnerAvailability 001 010 Remote Command 001 037 Sequence Status 001 038 Sequence Extension 001 039 Sequence Timer Group 002 Diagnostic DIGITAL 002 012 Run Test Switch 002 013 PilotValveHold T16 002 014 Manual Open Sw T17 002 015 LowFire Switch T18 002 016 HighFireS
5. 190 N10 200 N10 210 Note that registers N10 140 149 must be viewed in ASCII mode to determine revision information In this case an error code of 8 was generated for Poll Command 2 all other commands were executed without any errors 2 2 3 Error Status Codes The Error Codes returned in the low byte of each word in the Error Table reflects the outcome of the commands and responses 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 0 All ok The module is operating as desired 1 A Line Feed character which was expected was not detected while parsing the data from the slave 2 An ASCII error response was returned as a result of the command 3 No Response A No Response message was received from the 057850 indicating that the addressed slave did not respond to the requested command 4 Bad Response Parsing of the response from the slave generated an unexpected error condition If the ERR LED is on solid with this code then reset the Q7700 as messages may be out of sync 5 An unsupported command was attempted 6 Wrong Cmd Byte Cnt A Wrong Command Byte Count message was Poe received from the QS7850 indicating that the command was not structured correcil 7 A Write command was attempted to a read only point 8 Timeout Error Communications with the addressed QS7850 have been unsuccessful and have timed out Assure that the
6. 400 BTR gt __ Block Transfer Read CEN gt 15 15 Module Type Generic Block Transfer Rack 001 CDN gt Group 1 Module 0 CER Control Block N7 400 Data File N7 410 Length 64 Continuous No DECODE BT READ GENERATE BLOCK ID FILE PTR LIM CPT Limit Test Compute Low Lim 0 Dest N7 409 0 gt 150 gt Test N7 410 Expression N7 410 50 3 lt High Lim 19 19 lt READ DATA FROM UNITS COP Copy File Source N7 412 Dest N10 N7 409 Length 50 ENCODES BT WRITE BLOCK ID MOV Move Source N7 411 83 lt Dest N7 310 83 lt ENCODES BT WRITE BLOCK ID N7 100 MOV Move 0 Source 100 100 lt Dest N7 310 83 lt Page 1 Monday June 28 1999 13 51 24 CBMS RSP LAD 2 Total Rungs in File 3 0001 BT READ BT WRITE ENABLE ENABLE N7 400 N7 300 15 15 ENCODES BT WRITE BLOCK ID N7 101 MOV 4 E Move 0 Source 101 101 gt Dest N7 310 83 lt ENCODES BT WRITE BLOCK ID N7 102 MOV 4 E Move 0 Source 102 102 lt Dest N7 310 83 lt USER CFG ENCODES DOWNLOAD BT WRITE SELECT BLOCK ID B3 0 MOV 4 E Move 0 Source 255 255 lt Dest N7 310 83 lt LIM CPT Limit Test Compute Low Lim 80 Dest N7 308 80 lt 150 lt Test N7 310 Expression N7 310 80 50 83 lt High Lim 99 99 lt WRITE TO BT WRITE BUFFER COP Copy File Source N11 N7 308 Dest N7 311 Length 50 LIM C
7. Fault Code Fault Message Sequence Sequence Sequence Status EXt Timer Fault Cycle Fault Hour Fault Code Fault Message Sequence Sequence Sequence Status EXE Timer Fault Cycle Fault Hour Fault Code Fault Message Sequence Sequence Sequence Status Ext Timer Fault Cycle Fault Hour Honeywell Point Maps FERE HEETE HRT HHH RET ET HH HHH S7830 POINT CATEGORIES FERE HEIE FE FE EE HE E HE FE FE H E E E AE TE HE HE HE HEEE H Group 001 Operating Status 001 008 Current Status Group 002 Diagnostic DIGITAL 002 010 Valve Closure T4 002 011 Burner Switch T5 002 012 Oper Control T6 002 013 Aux Limit 1 T7 002 014 Aux Limit 2 T8 002 015 LWCO T9 002 016 High Limit T10 002 017 Aux Limit 3 T11 002 018 Oil Select T12 002 019 Hi OilPressure T13 002 020 LowOilPressure T14 002 021 High Oil Temp T15 002 022 Low Oil Temp T16 002 023 Atomizing Sw T19 002 024 Gas Select T17 002 025 Hi GasPressure T18 002 026 LowGasPressure T19 002 027 Airflow Switch T20 002 028 Aux ILK 4 T21 002 029 Aux ILK 5 T22 Group 006 Configuration 006 004 Software Revision Group 007 History 007 007 Fault First Out 007 009 Fault ValveClosure Honeywell Point Maps Example PLC and SLC Ladder Logic Overview The following ladder logic provides an example for the ladder logic necessary to integrate
8. 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 1996 1997 1998 Product Revision History 10 01 96 Revision 1 0 Initial release of product 02 04 98 Updated manual to include the point lists from Honeywell for each of the products Implementation Guide Integration of the CBM module into a PLC or SLC application is easier the first time if a series of steps are followed In order to assist the first time users of our products in getting the CBM operational quickly we have come up with this step by step implementation guide a Starting with one of the ladder logic programs provided on disk with the CBM complete the following steps PLC 5 CBM5 SLC 5 03 CBM503 See Appendix for SLC programming tips 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 Setup the Communication Configuration parameters See Section 2 Determine each port s communication configuration requirements Setup the Polling List for each port See Section 2 Be sure to review register map of slave device to build most effective memory map Setup the Device Definition Files for each of the devices to be addressed See Section 2 This is where the user is able to determine the Point Num
9. 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 freight prepaid
10. been detected by the module Review the Error Status Codes to determine the source of the error 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 The connection between the 3100 3150 CBM module and the Honeywell QS7850 unit is by an RS 485 to the DB connections on the front of the module The cable connections for both the 3100 and the 3150 units are shown below Two Wire Mode RS 485 Please be sure the jumper on the module is in the RS 485 mode ProSoft Module 3100 3150 25 Pin 9 Pin 4 RTS 7 5 CTS 8 14 TxRxDA 9 QS7850 Jumper RTS to CTS 15 25 TxRxDB 4 7 GND 5 iii 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
11. com 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 Jumper positions System hierarchy Physical connection information RS 232 422 or 485 Cable configuration 5 Module Operation Block Transfers operation LED patterns 20 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 CBM 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 on the outside of the
12. 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 Issuing a 255 Configuration command will cause the module to act as if it has been powered down The Polling Command List the Write Commands and the Device Definition Files will be cleared The configuration data block structure which must be transferred from the processor to the module is as follows BTW Block ID 255 Word Description 0 BTW Block ID 255 1 10 Port 1 Configuration parameters 11 20 Port 2 Configuration parameters 21 30 System Configuration parameters BTW Example Buffer Address Description 0 Block ID Header 255 Port 1 Configuration 1 N7 0 Baud Rate 2 N7 1 Response Timeout 3 10 N7 2 9 Spare Port 2 Configuration 11 N7 10 Baud Rate 12 N7 11 Response Timeout 13 20 N7 12 19 Spare System Configuration 21 N7 20 Read Block Count 22 N7 21 Write Block Count 23 N7 22 Command Block Count 24 N7 23 Error Pointer 25 N7 24 Spare 26 N7 25 Spare 27 N7 26 Device Definition File Count Response Baud Rate Timesi Port 1Configuration Port 2 Configuration System Configuration Read Blk Cnt Device Definition File Cnt Command BIk Cnt Error Pointer Example Configuration Block Where Baud Rate The baud rate at which the module is to operate The baud rate is configured as follows Value Baud Rate 300 Baud 600 Baud 1200 Baud 2400 Bau
13. the 3100 CBM and the 3150 CBM modules into their respective 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 Response Baud Rate Timeout 0 1 2 3 4 5 6 7 8 9 N7 0 0 Port lConfiguration N7 10 5 2000 0 0 0 0 0 0 0 O Port 2 Configuration N7 20 5 0 4 130 0 0 5 0 0 0 System Configuration Command Device Definition Node Slot File number Port Select Addr Number Destination Address Comand 1 Comand 2 Comand 3 Comand 4 N11 40 0 0 0 0 0 0 0 0 0 0 Comand 5 Point Number Enter the point numbers for the points to be read from the slave up to 20 Device Address N120 0 N120 10 0 0 0 0 0 0 0 0 0 0 N120 20 Example Ladder Logic CBMS RSP LAD 2 Total Rungs in File 3 0000 BT READ AND REGISTER TRANSFER FROM MODULE DECODING BT READ from module If BT READ Block ID is 1 then transfers the module s registers 50 99 into the PLC data table starting at N10 50 To add additional data blocks simply add additional decoding logic BT READ BT WRITE BT READ FROM ENABLE ENABLE MODULE N7 300 N7
14. time Fill with O Command Device Definition Slot File number Number Destination Address Node Port Select Addr Comand 1 Comand 2 Comand 3 Comand 4 Comand 5 Example Command List Block N11 0 2 8 1 5 0 0 0 0 0 0 RPA Command issued out port 2 to slave 8 The command references the Point Definition File O and places the results in Word 0 of the module N11 10 2 8 2 5 0 4 34 10 224 0 RPQA Command issued out port 2 to slave 8 The command is issued to an S7830 to read Point Num 10 with a qualifier 224 The results are placed in register 4 in the module 2 1 3 Executing Write Commands BTW Block ID 100 to 119 A CBM Master port is capable of executing single register write commands to slave devices on the ControlBus network The write commands are executed and one shoted by the module on a priority basis over commands in the Poll Command List Only one write command can be initiated per Block Transfer The write command is initiated by writing a data block from the processor containing the information necessary for the module to encode a valid command message including the data to be transferred The structure of the write message block transfer data is BTW Buf Example Name Description Address Address BTW Block ID This value is used by the ladder logic and by the 100 to 9 module to determine which command is executing The module will return the error status value in the relative position in the
15. 3100 3150 CBM Honeywell ControlBus Master Module Revision 1 0 USER MANUAL February 1998 ProSoft Technology Inc 9801 Camino Media Suite 105 Bakersfield CA 93311 prosoft prosoft technology com Please Read This Notice Successful application of the CBM 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 CBM 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 CBM 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 a commitment on the part of ProSoft
16. Error Table based on the Block ID number i e the Command executed by Block ID 100 will have a status value returned in position 112 in the table See Error Table section 1 N12 0 The Port Select parameter allows the application to select which port the CBM Module will use to execute the command Valid values are Port Description 1 Port 1 Command 2 Port 2 Command 2 N12 1 Node Address This value represents the Node address assigned to the QS7850A module to which the command is to be directed Valid values are between 8 and 255 Used to instruct the module which of the supported 3 N12 2 the valid entries are commands to execute In the Command List table 10 Cmd Description 3 wpa Write Point 4 wpqa Write Point Qualified 5 sn Set Node Address Ref Appendix for sn Cmd Slot Number This value represents the SN Slot Number for Network Number wpa commands the NN Network Number for QS7850 Node Adr wpqa commands and the Node Address for sn commands Device Address This value is used to select the particular device and type of device which is on a slot Valid values at this time are 17 QM40XX 18 Trapscan 19 Pulseatrol 20 for the BCS7700 32 for the RM78XX 34 for the S7830 N12 5 The Point Number in the slave in which the write Number command is to place a value N12 6 Pt Qualifier A value which must be sent when performing a wpaq command The value is defined by Honeywell on a per point basis See App
17. ID 1 BTW Block ID 2 62 Data BTR Block ID Number 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 BTW Block ID Number The module returns this value to the processor to be used to enable the movement of Poll Command List blocks and Device Definition File Blocks to the module The BTW Block ID number is developed by the module based on the value entered in parameter 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 through ladder logic BTR Buffer BTW Buffer Data The contents of the module s Register Data space containing the status and results of the polling of the slaves The values will be 16 bit register values and floating point values and should be placed into integer files Note that the user application ladder logic controls the placement and use of the data registers 2 2 1 2 2 2 Reading Slave Data Data which has been read from the slave devices is deposited into a 4000 word register table in the module This table is addressed starting at O 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 wo
18. PT Limit Test Compute Low Lim 100 Dest N7 308 100 lt 150 lt Test N7 310 Expression N7 310 100 10 83 lt High Lim 119 119 lt Page 2 Monday June 28 1999 13 51 27 CBMS RSP LAD 2 Total Rungs in File 3 0002 WRITE TO BT WRITE BUFFER COP Copy File Source N12 N7 308 Dest N7 311 Length 10 N7 N7 3 10 CUD 0 WRITE TO BT WRITE BUFFER LIM COP Limit Test Copy File Low Lim 120 Source N N7 310 0 120 lt Dest N7 311 Test N7 310 Length 21 83 lt High Lim 139 139 lt DECODE WRITE TO BT WRITE BT WRITE BLOCK BUFFER EQU COP Equal Copy File Source A N7 310 Source N7 0 83 lt Dest N7 311 Source B 255 Length 30 255 lt USER CFG DOWNLOAD SELECT B3 0 CU 0 BT WRITE TO MODULE BTW Block Transfer Write CEN gt Module Type Generic Block Transfer Rack 001 CDN gt Group 1 Module 0 CER Control Block N7 300 Data File N7 310 Length 64 Continuous No Page 3 Monday June 28 1999 13 51 27 CEND gt CBM503 LAD 2 CBM 503 Total Rungs in File 4 READ DATA FROM MODULE This rung of logic transfers data from the module to the ladder data t
19. Response Timeout value is large enough for the application if the error code is intermittent 9 ASCII Error An error response has been received from the QS7850 as a result of the command that was sent Verify that valid points are being requested 10 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 16 Port Configuration Error If this error is returned it is because the module has detected an invalid port configuration request Verify the baud rate settings if this error occurs 18 System Configuration If this error is returned from the module one of the Error system configuration parameters has been detected out of range To determine the source verify the following Read Block Count lt 80 Command Block Count lt 20 Error Pointer lt 3850 Dev Def File Cnt lt 40 255 TX Hardware Timeout 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 3 Protocol Commands 11 The ProSoft Technology CBM module Master driver supports several commands from the CBM Command set 3 1 CBM Commands The CBM module supports a command subset of the Protocol Specification consisting primarily of the commands required to initialize and read data from several units The following sections detail the different command
20. able depending on the BTR Block ID number In addition the logic transfers the BTW Block ID number for the write logic to use TRANSFER TRANSFER ENABLE DONE must be must be BUILD PTR in logic in logic FOR COP 1 1 0 1 LIM MUL 0000 3 E Limit Test Multiply 0 0 Low Lim 0 Source A M1 1 0 1746 BAS 5 02 1746 BAS 5 02 0 gt 9 gt Test M1 1 0 Source B 50 9 gt 50 lt High Lim N7 20 Dest N7 30 5 lt 50 lt COP Copy File Source M1 1 2 Dest N10 N7 30 Length 50 ENCODES BLOCK MOV Move Source M1 1 1 9 gt Dest MO 1 0 9 gt MOV BTW BLOCK ID FOR USE IN WRITE LOGIC MOV Move Source MO 1 0 9 gt Dest N7 31 81 gt TEST FOR WRITE COMMANDS This logic enables any write commands which are enabled In addition the configuration data block is transferred to the module if the User Cfg bit is set TRANSFER TRANSFER ENABLE DONE Command must be must be Enable ENCODES in logic in logic 1 BLOCK 1 1 0 1 GRT MOV 0001 3 e Greater Than A gt B Move 0 0 Source A N7 100 Source 100 1746 BAS 5 02 1746 BAS 5 02 0 gt 100 gt Source B 0 Dest MO 1 0 0 gt 9 gt Command Enable ENCODES 2 BLOCK GRT MOV Greater Than A gt B Move Source A N7 110 Source 101 0 gt 101 gt Source 8 0 Dest MO 1 0 0 gt 9 gt Page 1 Monday June 28 1999 13 54 37 CBM503 LAD 2 CBM 503 Total Rungs in File 4
21. bers in each of the devices which are to be brought back to the ladder logic Up to 20 points can be defined per Point Definition File Identify the jumper requirements See Appendix Make up the communication cables See Section 5 Place processor into the run mode Monitor the data table for the Error Status values See Section 2 Table of Contents Revision History i Implementation Guide ii T Product Specifications ccissc seteieasyctaccaiye ia 1 2 CBM Theoretical Operations ssns ie keie aaa a aaa a ra a aeai naaa e aia a erR aE aaao 1 2 1 Block Transferring Data to the Module 2 2 1 1 Communications Configuration BTW Block ID 255 000666600000 2 2 1 2 Writing Poll Command Lists to Module BTW Block ID 80 to 99 1 4 2 1 3 Executing Write Commands BTW Block ID 100 to 119 1 6 2 1 4 Writing Device Definition Files BTW Block ID 120 to 159 7 2 2 Block Transferring data from the module e 8 2 21 Reading Slave Dal 9 2 2 2 Reading Diagnostic Status Data 000066600000066 6 9 2 2 3 Error Status COS cm id 11 3 P
22. by the Error Table Pointer in the Communication Configuration setup Each Poll Command entry will generate an Error Code for use by the user The Error Table is initialized to zero on power up and every time the module receives the 255 configuration data block The Error Table is a total of 131 words in length The simplest method for obtaining the Error 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 position of the Error Table in the module s memory is user determined by the Error Table Pointer in the Module Configuration Block See Section 2 1 The structure of the Error Table is as follows Word Description System Information 0 1 Product Name ASCII 2 3 Revision ASCII 4 5 Operating System Rev ASCII 6 7 Production Run Number ASCII 8 9 Spare Poll Command Status 10 Command List End of Poll Status 11 Command 1 Error Status 12 Command 2 Error Status 109 Command 299 Error Status 110 Command 100 Error Status 111 130 Write Command Status Where Product Name These two words represent the product name of the module in an ASCII representation In the case of the CBM product the letters CBM should be displayed when placing the programming software in the ASCII data representation mode Revision These two words represent the product revision level of the firmware in an ASCII representation An example of the data
23. commands In the following example we will show how to write an integer value and a floating point value using the wpa command 1 Enter the values in the appropriate data table location to setup the command structure In the example logic this would be in the N12 file with each line of 10 words dedicated to one command Example Command amp 1 This command shown below performs the following Write Floating poin value 13 0 Point Address 27 Boiler Off in a BCS7700 Uses a wpa command to perform the write Command Device Address 3 is wpa Point Node Si Address Value Format ot Port Select Addr Nimba Scaling Example Command 2 This command shown below performs the following Writes integer vaue 5 Point Address 171 Cold Start Alarm in a BCS7700 Uses wpa command to perform the write Command Device Address 3 is wpa Point Node Address Value Format Slot Port Select Addr Number Scaling Writing Values to a Slave 3100 3150 CBM Honeywell 78XX Master Module Device Definition File Device Type Word Value Description 1 lt COIN lh lh Device Definition File Form Format CCC PPP Honeywell Point Maps CCC PPP DDDDDDDDDDDDDDDDDD Category Code Point DDDDDDDDDDDDDDDDDD DeviceTypeldentifier He RTH HERR AE EHH HRT EE HH RRR EEE BCS7700 POINT CATEGORIES aT EHH ERT ETH HH RTE EHH HR REE H Group 001 Operating Status
24. ct Specifications The 3100 3150 CBM Honeywell ControlBusTM Module CBM Master product family allows Allen Bradley 1771 and 1746 I O compatible processors to interface easily with Honeywell 7800 Series controls and BCS 7700 systems The CBM product includes the following standard features e Two fully configurable serial ports each capable of supporting the CBM Master functionality using the ASCII mode of communications e RS 485 connection from each port directly to Honeywell QS7850A interface modules e Supports up to 32 Honeywell nodes per serial port e Supports polling of rpa command accessible data using the integer data type e Floating point values are scaled x 10 by module e ASCII text strings are not supported e Supports one shoted writes using to wpa wpga accessible data from ladder logic e to 40 device config files are available for user configuration e Communication configuration From processor ladder logic Node Addr 0 8to 255 Baud Rate 300 TO 38 400 9600 baud only supported by Honeywell Response Timeout Parity None fixed Stop Bit 1 fixed Mode i ASCII fixed e Supported CBM command codes rpa Read Point rpga Read Point Qualified wpa Write Point wpqa Write Point Qualified sn Set Address e Error Codes returned to the ladder processor along with a poll execute toggle bit e Response time The protocol drivers are written in Assembly and in a compiled higher level language As such t
25. d 4800 Baud 9600 Baud Honeywell default 19200 Baud 38400 Baud 0 00 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 Port Configuration Error will be returned Message Response Timeout 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 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 3000 ms System Configuration Read Data Block Count This value represents the number of 50 word data blocks which are to be transferred from the module to the processor The blocks returned from the module start at block O and increment from there The maximum block count is 80 As an example a value of 5 will return 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 Command Block Count This value represents the number of 50 word Command Blocks which are to be transferred from the processor to the module This value will b
26. d 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 E in module have failed ERR1 Amber Normal State When the error LED is off and the related port 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 CBM slave Recurring error condition on CBM master The port is communicating either transmitting or receiving PRT2 data 4 3 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 14 Problem Description BPLN light is on SLC CFG light does not clear after power up Module is
27. different types of data which are transferred require slightly different data block structures but the basic data structure is Where Word Description 0 BTW Block ID code 1 63 Data 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 BTW Block ID Code A block identifier code between 0 and 255 in value This code is used by the ProSoft module to determine what to do with the data block Valid codes are BTW Code Description 80 99 Polling Command List 100 119 Write Commands 120 160 Device Definition Lists 255 Module Configuration 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 2 1 1 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 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 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
28. displayed would be 1 00 when placing the programming software in the ASCII data representation mode Operating System Revision These two words represent the module s internal operating system revision level in an ASCII representation Production Run Number This number represents the batch number that your particular chip belongs to in an ASCII representation 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 Port 1 1 Port 2 Command Error Status The Error Status Codes either received from the slaves or generated by the module are placed in the table The Error and Status information is split into a High and Low byte format as follows High Byte Command Execute Toggle Low Byte Error Status Code 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 The relationship between the placement of the error codes within the Error Table and the commands is according to the command s relative position in the command list Error Status Table Example Error Table Pointer 140 Wrd Wrd Wrd Wrd Wrd Wrd Wrd Wrd Wrd Wrd l 0 1 2 3 4 5 6 7 8 9 N10 140 CB M 1 00 08 01 0 0 0 0 10 N18 188 8 N10 170 N10 180 N10
29. e O if the module will not be configured with a Master port See the discussion in Section 2 1 2 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 Error Block Pointer This value represents the relative starting position in the module s data table within which the Error Data Block is placed The Error Table is a 131 word block containing module revision level information as well as slave polling status 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 3850 is entered a System Configuration Error is activated Device Definition File Count This value represents the number of Device Definition Files which will be defined by the ladder logic application This value is used by the module to determine which how many definition files to request during a power up or re configuration sequence If a value greater than 40 is entered a System Configuration Error is activated Writing Poll Command Lists to Module BTW Block ID 80 to 99 A CBM Master port establishes communications and performs various communications functions based on the data which the user has placed in the Poll Command List The command list consists of up to 100 individually configured command data blocks 10 words reserved pe
30. endix point listing or Honeywell Reference 206610 Q7850 diskette N12 7 Data Value The value which will be written into the slave Point Note that floating point values should be entered as integers x 10 N12 8 The format value as defined by Honeywell for the appropriate command N12 9 Scaling The scaling value as defined by Honeywell for the appropriate command N12 3 N12 4 2 1 4 Writing Device Definition Files BTW Block ID 120 to 159 The Device Definition Lists are used by the CBM module when building a Read Point Command to determine which points to read Up to 40 Device Definition Lists may be entered in the processor data table Devices with the same Device Address and the same list of points to read can reference an individual Device Definition File multiple times i e if there are 6 of the same devices on a network and all of the same points are to read out of each device then only one Device Definition File needs to be created although 6 entries will still need to be made in the Poll Command List Movement of the Device Definition Files occurs automatically only on power up or anytime a module reconfiguration Block ID 255 is issued to the module The example ladder logic in the Appendix references a method for setting up the Device Definition Files and for moving them in ladder logic into the Block Transfer Write buffer The structure of the Device Definition File is as follows BTW Buf Example Name Descripti
31. 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 tor parts and labor and return the Product freight collect Support Service and Warranty Jumper Configurations Hardware Overview When purchasing the CBM 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 tor the 1771 Platform Following are the jumper positions for the ProSoft Technology 3100 CBM module 3100 N A N A N A Flash Pgm Run Mode 8 Pt 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 CBM FLASH me
32. he interrupt capabilities of the hardware are fully utilized to minimize delays and to optimize the product s performance CBM Theoretical Operation 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 2 1 Block Transferring Data to the Module Data transfer to the module from the processor is executed through the Block Transfer Write function The
33. ions SLC Programming Considerations The 3150 CBM is also very easy to get operational After the ICBM cover and firmware are installed and the jumpers have been configured the module is ready to be configured In order to implement the sample logic the user must make sure that the correct processor and rack size match up Also should it be necessary to re locate the CBM 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 CBM module It is important that the slot containing the ProSoft module be configured as follows 1746 BAS module or enter 13106 for the module 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 CBM 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 t
34. itions when the QS7850 first is received from the factory it will not be assigned an address requiring that the unit be addressed using 255 Using the procedure documented in the Appendix the node address can be set The structure of the command as supported by the CBM module is Node sn V1CR LF 4 Hardware Diagnostics 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 4 1 3100 PLC Platform The PLC platform CBM product is based on the ProSoft CIM hardware platform The following table documents the LEDs on the 3100 CBM hardware and explains the operation of the LEDs ProSoft CIM ACTIVE CFG ERR1 TXD1 RXD1 Pom color stats Fast successfully Block Transferring with the PLC E may be some other problem 5 off 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 background diagnostics diagnostics Please contact factory for technical support this time This light blinks every time a Module Configuration block ID 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
35. mit Test Copy File Low Lim 120 Source N N7 31 0 120 lt Dest MO 1 1 Test MO 1 0 Length 21 9 gt High Lim 159 159 lt DECODES BT WRITE TRANSFER BLOCK ID TO MODULE EQU COP Equal Copy File Source A MO0 1 0 Source N7 0 2 lt Dest MO0 1 1 Source B 255 Length 30 255 lt USER CFG DOWNLOAD SELECT B3 0 0 WRITE DONE O 1 0 1746 BAS 5 02 END gt Page 3 Monday June 28 1999 13 54 43
36. mory This will only need to be done if the module is to be upgraded in the field to a leter 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 The default from factory is RS 232 but all options are supported by the CBM firmware 3150 for the 1746 Platform Following are the jumper positions for the ProSoft Technology 3150 CBM module 3150 CBM As Needed As Needed N A N A Jumper Configurations 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 foll Communication Port Jumper Settings for 3150 Modules JW1 8 JW2 Jumper JW1 Settings cor ee posta RS 232 Daughter Board A anos RS 422 4 wire Daughter Board Daughter Board 5 0 02 Rs 485 Mother 2 wire Board Daughter Board wo Bas JW4 Jumper JW2 Settings Daughter Board R S 232 TREN Daughter Board RS 422 Daughter Board 4 wire PTE Daughter Board RS 485 oof se 2 wire Jumper Configurat
37. not transmitting Error Code 255 in Status Table ERR light flashing periodically New configuration values are not being accepted by the module Cable Connection Steps to take The BPLN light comes on when the module does not think that the SLC is in the run mode ie 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 enabed e 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 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 Presuming that the processor is in run verify the following e Check Error Status codes for 255 code If so see next problem If all the ladder logic is block transferring with the module Active LED is toggles 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 An error response or condition has
38. off and the ACT light is blinking quickly the module is actively Block Transferring data with the PLC 0 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 port ERR2 is actively transferring data there are no communication errors Blink Periodic communication errors are occurring during data communications See Section 4 to determine the 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 CBM slave Recurring error condition on CBM master 1x1 Green Blink The port is transmitting data 1x2 Rx2 13 4 2 3150 SLC Platform The following table documents the LEDs on the 3150 CBM hardware and explains the operation of the LEDs COMMUNICATIONS EM ACT EE FAULT EM crc EM BPLN EM PRT DS ERRI EM PRT2 DS ERR2 i eoe e Name Color Fast successfull Block Transferring with the SLC may be some other problem 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 ee background diagnostics O EE a diagnostics Please contact factory for technical sup port ee ee this time 0 This light blinks every time a Module Configuration block I 255 is receive
39. on Address Address BTW Block ID This value is used by the ladder logic and by the 120 to 159 module to determine where to place the File data The Poll Command List entries will reference the File numbers starting at O such that the entry placed in the module with Block ID 120 will be referenced as 0 N120 0 Device Address This value is used to select the particular device 2 2 and type of device which is on a slot Valid values at this time are 17 QM40XX 18 Trapscan 19 Pulseatrol 20 for the BCS7700 32 for the RM78XX 34 for the S7830 2 N120 1 Point Number List A list of the Point Numbers which are to be read to 121 from the slave devices Block 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 Module Data space is then transferred to the PLC SLC The transfer of data from the ProSoft Technology module to the processor is executed through the Block Transfer Read function The data structure for the block transfer is predefined and detailed below 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 ladder logic must be programmed to look at the BTR buffer decode several words and then take action The BTR buffer definition is Word Description 0 BTR Block
40. r command which are shared between the two available ports This list entered into the processor Data Table is transferred to the module s memory using Block ID codes 80 99 with each code representing a 50 word block or 5 commands BTW Buffer Word Description 0 BTW Block ID Code 80 99 1 10 Command Config Pos 1 11 20 Command Config Pos 2 21 30 Command Config Pos 3 31 40 Command Config Pos 4 41 50 Command Config Pos 5 BTW Block ID The block identifier number allows the CBM Module to decode which portion of the command configuration table is being written Valid numbers for the BTW Block ID are between 80 and 99 inclusive with 80 representing the beginning of the command list commands 1 to 5 and 99 representing commands 95 to 99 Command Config Data The Command Configuration Data consists of the command list data outlined in the above discussion A command configuration block consists of the data necessary for the module to encode a valid command to transfer data from a slave to the master s memory The structure of the command configuration data block is as follows Block Example Address Address 0 N11 0 N11 1 N11 2 N11 3 N11 4 N11 5 N11 6 N11 7 N11 8 N11 9 Name Port Select Node Address Command Slot Number Network Number Device Definition File Destination Address rpqa DA Device Address rpqa PP Point Number rpqa PQ Point Qualifier Spa
41. rd limit of the BTR instruction The paging mechanism is outlined in the discussion above but the important thing to understand is the relationship between the page numbers BTR Block ID numbers and the register addresses in the module 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 The following 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 See Section 2 1 CBM Module Memory PLC Block ID 0 to 79 Address 0 to 3999 PLC Data Memory Addr N10 0 Block ID O Read Data from Slaves to PLC These data registers 0 to 139 will be the destination addresses for the Commands in the Poll Command List Block ID 1 0000 Block ID 2 Error Table Pointer 140 N10 150 Block ID 3 Error Table These data registers 140 to 270 will contain the Block ID 4 Error Table presuming an Error Table Pointer of 140 N10 200 N10 250 Block ID 5 N10 300 Block ID 6 Block ID 79 Read Data Blocks from CBM Module example only Reading Diagnostic Status Data The module monitors the status of all commands This status is communicated to the processor as part of an Error Table the position of which is controlled
42. re Description The Port Select parameter allows the application to select which port the CBM Module will use to execute the command Valid values are Port Description 1 Port 1 Command 2 Port 2 Command This value represents the Node address assigned to the QS7850A module to which the command is to be directed Valid values are between 8 and 255 Used to instruct the module which of the supported commands to execute In the Poll Command List table the valid entries are Cmd Description 1 rpa Read Point 2 rpga Read Point Qualified This value represents the SN Slot Number for rpa commands and the NN Network Number for rpga commands This value is used by the module to reference the point list configured in the Device Definition File The relationship between the value entered here and the Files themselves is as follows Value Block Transfer 0 120 File Number O 2 121 File Number 1 39 159 File Number 39 The CBM module register address in which the data being read from the slaves will be returned As an example a value of 50 would place the slave data block starting at register 50 in the CBM module and return the data to the processor when Block ID 1 is read Used only for the RPQA command to identify the Device Address of the unit to read from The RPQA Point Number to be read The RPQA Point Qualifier which must be sent to reference the point This value is available from Honeywell point tables Not used at this
43. rotocol Commands iii 11 321 CBM Commands i 2 4 00 12 3 1 1 Cmd 1 rpa Read Point Command 12 3 1 2 Cmd 2 rpga Read Point Qualified 00131383 666 12 3 1 3 Cmd 3 wpa Write Point Command 00 12 3 1 4 Cmd 4 wpga Write Point Qualified Command 12 3 1 5 Cmd 5 sn Set Node Number o oo 12 4 Hardware Diagnostiese iesene 12 4 1 3100 PLG 01112 EA E e E A A A 13 4 2 31 50 SEC a EIES LAN E E E o A ed ae ot E E 14 00 1 0000 14 5 Cable Connection 1 00 15 Appendix Support Service and Warranty Jumper Configurations SLC Programming Considerations Setting a Slave Node Address Writing values to a slave Device Definition File Form Honeywell Point List Example Ladder Logic PLC 5 SLC 5 03 Produ
44. s supported by the module 3 1 1 Cmd 1 rpa Read Point Command This command allows read access to most of the points in the Honeywell units This will be the most commonly used command The structure of the command as supported by the CBM module is Node rpa SN DA PP PP CR LF The module will support up to 20 points per request Note that if one invalid point is entered in the point list then the entire command will fail 3 1 2 Cmd 2 rpqa Read Point Qualified Command This command allows access to points which are not accessible via the rpa command The structure of the command as supported by the CBM module is Node NN DA PP PQ CR LF The module will support up to 1 point of data per request 3 1 3 Cmd 3 wpa Write Point Command This command allows write access to most of the points which are contained in the Honeywell hardware The structure of the command as supported by the CBM module is Node wpa SN DA PP V1 FF SC CR LF The module will support up to 1 point of data per request 3 1 4 Cmd 4 wpqa Write Point Qualified Command This command allows write access to the points which are not accessible via the wpa command The structure of the command as supported by the CBM module is Node wpqa SN DA PP V1 PQ Q1 Q2 CR LF The module will support up to 1 point of data per request 3 1 5 Cmd 5 sn Set Node Number This command allows a QS7850 unit to be re addressed Under normal cond
45. 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 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 Support Service and Warranty 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 HEREIN PROSOFT MAKES NO
46. t Nom0il Press 005 005 064 065 o0ilPress imit iOilPress Amit 005 005 005 005 005 Group 068 069 070 153 171 NomOi 1Temp 00ilTemplLimit HiOilTempLimit PercentLoAlarm ColdStartAlarm 006 Configuration 006 006 006 006 006 006 006 006 001 002 003 012 013 014 015 020 MajorRevision MinorRevision Programident ConfigTerm FlameAmplifier BoilerType FuelSeries BoilerMedium 006 006 006 006 006 006 006 Group 021 022 023 061 066 073 074 SteamSensRange WaterSensRange GasSensRange OilPressSensRange OilTempSensRange PrepurgeExtend PostpurgeExtend 007 History 007 076 007 083 007 077 H Total Cycl H Total Hours H1 Fault Cycle es Honeywell Point Maps 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 084 095 102 109 116 126 133 140 078 085 096 103 110 117 127 134 141 079 086 097 104 111 118 128 135 142 080 087 098 105 112 119 129 136 143 081 088 099 106 113 120 130 137 144 082 089 100 107 114 121 131 138 145 Faul Faul Faul Burn Burn Fire SequenceTimer Fuel
47. witch T19 002 017 Valve 2 Start T21 002 018 Prelgn ILK T20 002 019 Oper Control T6 002 020 Ignition T10 002 021 Main Valve T9 002 022 Pilot Valve T8 002 023 Interlock T7 Group 003 Diagnostic ANALOG 003 011 Flame Signal Group 006 Configuration 006 004 Software Revision 006 025 Purge Time 006 026 Amplifier Type 006 027 Jumper 1 006 028 Jumper 2 006 029 Jumper 3 006 030 Flame Response 006 032 Device 006 033 Manufacturing Code 006 087 Line Frequency Group 007 History 007 040 Total Cycles 007 041 Total Hours 007 042 H1 Fault Code 007 043 H1 Fault Message 007 044 H1 Sequence Status 007 045 H1 Sequence Ext 007 046 H1 Sequence Timer 007 047 H1 Fault Cycle 007 048 H1 Fault Hour 007 049 H2 Fault Code 007 050 H2 Fault Message 007 051 H2 Sequence Status Honeywell Point Maps 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 DDNDDDNDADUVUUNUUHHUHOP ds ds ds ds ds BPWWWWWWWNDN DN Sequence Sequence EXt Timer Fault Cycle Fault Hour Fault Code Fault Message Sequence Sequence Sequence Status EXE Timer Fault Cycle Fault Hour
48. ype in 64 and Enter 8 F6 for M1 file length type in 64 and Enter Esc out and save configuration SLC Programming Considerations Setting a Slave Node Address When a QS7850 is received from the factory and installed in on network it must be configured with a unique node address In a multi drop configuration each QS7850 has a number stored in a EEPROM that uniquely identifies it in the range of 8 to 254 When first powering up a card perform the following procedure 1 Connect the QS7850 to the network and power up the 7700 rack containing the module Be sure that all pre existing cards on the RS 485 network have unique addresses between 8 and 254 2 Enter a Set Node Address command in the ladder logic data table as follows Command 5 is Set Node Port Select Addr Set Node Address N12 0 Command Note that the Set Node Address command is actually addressed to generic node number 255 If a QS7850 card does not have a pre assigned node address stored in it s EEPROM then the unit will respond to the 255 address 1 Initiate the command so that the new slave address is written to the QS7850 card 2 Enter polling commands in the Poll Command list to address the new slave device 3 Monitor the Error Table to verify that configuration has been successful Setting a Slave Node Address Writing Values to a Slave Writing values to a slave Honeywell device is accomplished using the methods outlined in Section 2 1 3 to write

3100/3150-CBM User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents