Scribd
Upload
109 views13 pages

Modbus CIU888

Communication register

Uploaded by

Harita Harita
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
109 views13 pages

Modbus CIU888

Communication register

Uploaded by

Harita Harita
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 13
‘Appendix E - Creation of New Modbus Field Device Configuration File APPENDIX E CREATION OF NEW MODBUS FIELD DEVICE / TRL/2 FIELD DEVICE CONFIGURATION FILE Based on the Modbus field device / TRL2 field device manufacturer's datasheet, the user shall create the Modbus field device / TRL/2 field device configuration file according to the attached Modbus field device configuration template. Refer to the following sections for more information on the Modbus field device / TRL/2 field device configuration template. E.1 Device Type The following table provides more information on the Device Type. XML Tag Description Possible Values: | This isthe Modus fld device | Any sing type. The user shall provide the device type name like ‘SLG700, E+H PraServo ete | This specifcto TRL2 device | TRUE/FALSE and not applicable for Modbus device. The user can provide "TRUE" for Honeywell TRLI2 devices and "FALSE" for tied party devices. E.2 Device engineering units The following table provides information on the various engineering units supported by the Modbus field device. XML Tag, Description Possible Values ~ | This specifies the Device unit_| LEVEL. ‘ype. TEMPERATURE DENSITY PRESSURE: Part No.: 4417584_Rev04 Configuration Manual Honeywell | ives clu 888 Ea ‘Appendix E - Creation of New Modbus Field Device Configuration File E3 E4 ML Tag Description Possible Values - | This specifies the device For LEVEL: m, em, engineering unt. Referto | mm, f, yard, in, in, section E.7 for the supported | is, f/266, in/256, units. 4140 mm (TRU2) For TEMPERATURE "0, °F K, Tenth Fahrenheit (TRL2), Tenth Celsius (TRL2) For DENSITY : kale, “API, Ib, RDEO, bi US gal, kal, gril For PRESSURE : kof! cm?, Pa, kPa, ps, atm, bar, psi_rt09, ps_r1000, mBarG (TRU2), mBard (TRL 2), 17100 psiG (TRL 2), 1/100 psia (TRU2) ‘ This specifies the device engineering units resolution “AIT 10 128 Valid Register Ranges ‘The following table indicates the valid consecutive Modbus register address ranges in the device. can be scanned by CIU. XML Tag, Description Possible Values ~ | This indicates the Modbus | 300001 to 365535 Start address, "400001 t0 485535 | This indicates the Modous End | 300001 to 365535 adsress 400001 to 485535, Modbus Map ‘The following table indicates the Modbus register map of the device that be scanned by CIU. XML Tag, Description’ Possible Values ‘ This indicates the name of | Any Sting ‘ the parameterin the Modbus field device which needs to ‘Configuration Manual IU 888 Part No.: 4417584_Rovod Honeywell | i358 ‘Appendix E - Creation of New Modbus Field Device Configuration File ML Tag Description’ Possible Values ‘ ‘ This indicates the relative Modbus address of a parameter in the Modbus field deviee. ‘Absolute Modbus adores of Parameter = Device Modbus Start Address + Modbus Register Address This is the 6 digit Moabus Register address of the ovice parameter. The fst digit indicates the Modbus function code (3 for Input registers and 4 for Holding registers). Second to Sich digits indicates the Modous register address defined by the devie manufacturer. 0. to 65535 registers can be addressed. For example to address holding register O in device, 400001 would be set here, 300001 to 365535 4400001 to 465535 exposed by the field device so that CIU can interpret the data accordingly and convert itto ts intemal data format. Refer to section E.6 forthe list of supported Modbus data types, This indicates the number of | 1 to 125 Modbus registers defined for _| the selected parameter. “ The data can be exposedin | Not a number different data types by Fixed number ‘ different Modbus fla ASCII string devices. This parameter | Unicode string indicates the Modbus data | 8-bit unsigned type in which data is integer 4b signed integer ‘16-bit unsigned integer ‘seit signed integer 16-1 decimal fost 12bit signed integer 32-bit signed integer 32 bit toa (regular) s2-bt unt 32-4 unvtio 32-bit uinutt00 32-bit unbf1000 32-0t unvt10000 Part No.: 4417584_Rev04 Configuration Manual Honeywell | ives clu 888 ‘Appendix E - Creation of New Modbus Field Device Configuration File ML Tag Description’ Possible Values ‘ “ ‘ - ‘ ‘ This indicates the byte (8- bit) order wihin a 16-bit ‘word in which data is exposed by the field device. There can be 2 formats in which data can be exposed ()LSB first (i) MSB first Based on ths configuration CU interprets the data and converts tots internal data format, ‘Note: This refers the tendianess ofthe received data at byte level. LSB frst refer to Ltle Endian and IMSB first refers to Big Engian, This indicates the word (16- bit) order within a 32-bit ong ‘word in wich data s exposed by the field device. There can be 2 formats in which data can be exposed (0) LSW first (i) MSW frst, Based on ths configuration CU interprets the data and converts tots internal data format, Note: This indicates the tendianess ofthe received data at word level, LSW fist refer to Litle Endian and MSW first refers to Big Engian, ‘Some Modbus feld device scales the data it exposes to the Modbus host. Hence this parameter indicates the scaling factor used in the ‘exposed data from the field device so that CIU can de- scale the retrieved value Scaling and ofset are not ‘applicable then this tag ean be let empty LSB_First MSB_First LSW_ First MSW. First ‘Any float value ‘Configuration Manual IU 888 Part No.: 4417584_Rev0é Honeywell | i sss ‘Appendix E - Creation of New Modbus Field Device Configuration File ML Tag Description Possible Values ‘ ‘Some Modbus feld device | Any 32-bt signed ‘ adds an oft tothe datait_| value exposes to the Modbus host Hence this parameter indicates the offset factor Used in the exposed data from the ld device so that CCU can subtract the ofset from the retrieved value Scaling and offset are not ‘applicaale then this tag ean be let empty “ This indicates the default | FOREGROUND ‘ scanning priority fora device | BACKGROUND parameter. This can be Configured as Foreground / Background. While scanning the eld device, multiple field device parameters are retrieved in one Modbus request, then highest prionty within the scanned field device parameters is set for that request. For example, if Product Level (Foreground prirty), Product Temperature (Background pros), Product Density (Background protty) are Fetrieved from the eld device with a single Modbus request, then the Modbus request would be scheduled to the ela with Foreground protty This can be averrisden through Modous Data Input configuration in C1U 888 service tool “ This indicates the device | LEVEL Lnittype of the parameter | TEMPERATURE configured in the Medous | DENSITY field deviee PRESSURE ANY value for this tag is set as "ANY" then CIU 888 service tool shal splay all the device supported units ints User interface for this Parameter in Modbus Data Input confguration. Part No.: 4417584_Rev04 Configuration Manual Honeywell | ives clu 888 E-5 ‘Appendix E - Creation of New Modbus Field Device Configuration File ML Tag Description Possible Values ‘ This indicates the default | For LEVEL: m, ‘ device unit of the parameter | cm, mm, yard, configured in the device. | in, in/6, is, fi 288, i258, 1/10 ‘Supported Values are based | mm (TRL) ‘on DeviceUnits section, For TEMPERATURE °C,"F,K Tenth Fahrenheit (TRU), Tenth Celsius (TRL) For DENSITY : kg! 1°, "API, bf, RD8O, lb US gal, ait, grim For PRESSURE katfem, Pa, KPa, psi, aim, bar, psi_r100, si_?1000, mBarc. (TRL2), mBard (TRU), 1/100 psiG (TRUZ), 11100 psia (TRL) For ANY: The tag shall be empty ‘Configuration Manual IU 888 Part No.: 4417584_Rev0é Honeywell | i sss ‘Appendix E - Creation of New Modbus Field Device Configuration File ML Tag Description Possible Values ‘ This indicates Modbus feld | Any HEX string as ‘ device parameter failure | per the Modbus value. That is, when field device parameter value retrieved | manufacturer. from Modbus Fld device is equal to this value it indicates the device parameter value is in failure. For example, if OxFFFFFFFF represents Product level measurement fallue fora Modbus field device, then when CIU receives that value it interprets that the Product level measurement has failed and sets the Product Lovel status accordingly. ‘When status register is present inthe device (Status tag information present), status and validity of tne device parameter would be determined by CIU based on ‘Status fag inthe status Section and this fag shall be empty. “ This is the device status | Any sting ‘ parameter name as defined In the Manufacturers product data sheet “ This indicates the Modbus | 300001 to 365535, ‘ register address ofthe 4400001 to 465535 ‘ satus parameter associated with device parameter that needs to be scanned by CIV 888, This isthe 6 digit Mosbus Register address of the device parameter. The frst digit indicates the Macbus function code (3 for Input registers and 4 for Holding registers). Second to Such digits indicates the Modbus register address defined by the device manufacturer. 0 to 85595 registers can be adaressed. For example to address holding register O in ‘device, 400001 would be set here, Part No.: 4417584_Rev04 Configuration Manual Honeywell | ives clu 888 E-7 ‘Appendix E - Creation of New Modbus Field Device Configuration File “ ‘ “ ‘ - cu see, This indicates the Modbus field device's byte order for 18 bit status data. Based on this configuration, CIU 888 inteprets the field device status value with correct byte ordering There can be 2 formats in which data can be exposed (i) LSB first (i) MSB first. Based on ths configuration CU interprets the data and Converts tots internal data format, This indicates the Modbus field device's word ord for 32 bit status data. Based on this configuration, CIU 888, interprets the Feld device status value with correct ‘wore ordering, There can be 2 formats in which data can be exposed (0) LSW first (i) MSW frst Based on ths configuration CCU interprets the data and Converts tto its internal data format, ML Tag Description Possible Values ‘ This indicates the number of | As per Modbus ‘ Modbus registers defined for | field device the Modbus field device | Modbus datasheet status parameter that needs tobe scanned by CIU 888. ‘ This indicates the Modbus | Not a number “ datatype for the Modbus | Fixed number field device satus parameter | 8-bit unsigned that needs to be scanned ay | integer B.bI signed integer s6-bi unsigned integer 16-bit signed integer *20it signed Integer 32-bt signed integer Ls8_First MSB_First LSW_ First MSW. First ES Custom Value Map This configuration defines the value mapping between device parameter value and CIU parameter value. This configuration would be defined only if a direct mapping of device parameter value to CIU ‘Configuration Manual IU 888 Part No.: 4417584_Rev0é Honeywell | i sss ‘Appendix E - Creation of New Modbus Field Device Configuration File parameter value is not possible. For example, Product level value in device can be directly mapped to CIU Product level value but Gauge status / Gauge alarms from the device might not directly map to CIU Gauge status / Gauge alarms and needs a custom value map. Refer to the following table for more information, associate the custom value. XML Tag, Description Possible Values, ~ This is the device parameter | Any value defined as - ame as defined in the part of Manufacturer's product data | < sheet towhich we need to | ModeusMap> - (01) < Modbus ap> ~ - - “This indicates the CIU Parameter Name to which device parameter is mapped, ‘This indicates the value map type. Device parameters ProductLevelstatus| ProductTempStatus WoaterMeasuredStatus DObsHIMSStatus \VapRoomTempSiatus \VapRoomPressStatus AmbientTemperature satus GaugeStatus GaugeLevelAlarms ExternalContacts EnumerationToEnume - - « - - should be the CIU value if EnumerationToEnumerationis selected for VakieMapType and no mapping defined fora particular device parameter value ‘This value incicates the portion of the device value Which needs tobe copied to the CIU parameter. For example, if Bits 15 to 8 of the device parameter needs to be copied then BitM = 8 and BIN = 15, Ifthe ent device value needs to be copied then this tag shall be empty enumeration to CIU parameter's enumeration shall be specified here. ~ Default Value indicates what | Any value as per CU parameter ‘Any value as per Modbus field device Modbus datasheet Part No.: 4417584_Rev04 Configuration Manual Honeywell | ives clu 888 ‘Appendix E - Creation of New Modbus Field Device Configuration File XML Tag Description Possible Values: - ‘This value incicates the ‘Any value as per portion in the CIU parameter | Modbus field device where the device value needs | Modus datasheet | to be copied For example, ifthe device value needs to copied to Bits 12 to Bit8 afer value mapping | is done then it BitM = 8 and BN 2 Inthe the device value (ater value mapping) needs to completely replace C1U parameter value then this tag shall be empty. - Device Value in Modbus data | Any value as per - ‘ype. Modbus field device Modbus datasheet ~ CCU Value in CIU Parameter | Any value as per CIU data ype. parameter E.6 Supported Modbus Data types Modbus Data types are not standard. Based on the analysis of the Modbus field devices, the following Modbus data types would be supported in CIU. Modbus Data Type. Nota number | This data represents 8/16 bit coded information Description Fixed number _| This data represents a 16 bit fxed number, ‘ASCII string | The data represents a string of two ASCII characters per register. Unicode sting | The data represents a string of one UNICODE character per register 16-bitunsigned | The data represents an unsigned integer. Integer Range : 0 to 85535 16bitsigned | The data represents an signed integer (in 2's complement) integer Range : 32768 to 32767 ‘Configuration Manual Part No.: 4417584_Rev0é ciu 888 Honeywell | i sss ‘Appendix E - Creation of New Modbus Field Device Configuration File Wodbus Data he Description 1Sbitdecmal | Bt15 _ : sign float Bit 14.11 : Exponent power of 10 Bit10.0 :Mantissa Value = 4 sign * mantissa * 10 (Exponent -7) Range : -1023°7 to +1023°E7 ‘Pit signed —_| Bit 15.19: Not used integer Bit12 :0-Positve 4 = Negative Bit 11.00: Value 0 to 4095, Ifthe sign is negative, the value is shown in 2's complement Range : 4096 to +4095 S2.btsigned | The data represents an signed integer. integer Range : + 2147483648 lo ~ 2147483647 a {32 BItIEEE floating point in TWO registers. bit float (regular) | All loating point data is coded into 4 Bytes Floating point This fermat allows a representation of ite numbers from negative to positive 3.402823 °E38 Range : 3.402823°E-38 to +3.402823°E38 ‘32-ituinutt | Most significant 16 bits represent integer data and least significant 16 bits is 0 Range Oto 855355 ‘32-5 uinut10 | Most significant 16 bits represent integer data and least significant 16 bits represents 1 fraction digit Range: 0,,65535.95 ‘2p unvTT00 | Most eignfcant 16 bits represent integer data and least significant 16 bits represents 2 fraction digits. Range :0..85535,995 {32-bit uinvf1000 | Most ignifcart 16 bits represent integer data and least significant 16 bits represents 3 fraction digits. Range :0..65535, 8995 32-5 un ‘Most significant 18 bits represent integer data and least #10000 significant 16 bits represents 4 fraction digits, Range :0..65535,99995 Char This data represents an ASCII character. Bit signed —_| This data represents an B-bit signed data integer Range 127 to 128, Part No.: 4417584_Rev04 Configuration Manual Honeywell | ives clu 888 e-1 ‘Appendix E - Creation of New Modbus Field Device Configuration File Car Description ieee Range : 0 to 255 £.7 Supported Device Engineering Units Device engineering unis ae not standard, Based on the analysis ofthe Morus ted devs, te flowing device erinectiig unis would be supported G1 Tas of eee Device unit ye tees Pow mer RL) BWA TRL "70 p TRL 0 pin TRL ciU 888 Honeywell ‘Appendix E - Creation of New Modbus Field Device Configuration File Units of Measurement Type. Densty Kilogram cubic meters Unit Degrees APL Pounds cubic feet RDGO Ibs_us_gallon kilogram liters (Gram / Mile Part No.: 4417584_Rev04 Configuration Manual Honeywell | ives clu 888 E-13

You might also like