M0310 MODBUS To HART Module User Manual

http://www.microcyber.cncurrent working status.Table 1.3 HART Module Working Status Indication ListInitial Power-upContinuousWork1.5LED1LED2Status DescriptionLight onLight onModule initialization, not enter working statusNormallyNormallyononTwinkle——Indicate there‟s HART communication at present——TwinkleIndicate there‟s Modbus communication at presentLight offLight offIndicate there‟s no any communication or fault statusAfter module initialization, no any HART and Modbus communicationSoftware User InterfaceMODBUS link and application layer standard is used between HART moduleand user board. HART module is master station, user board is slave station.HART fieldbus interface of HART module executes HART 7.0 protocol, andsupports BURST mode operation. Common and general commands areshown in Table 1.4.Table 1.4 Command List Supported by HART Bus InterfaceCommonGeneralCommand NameCommand No.Command NameCommand No.0Read Unique Identifier33Read Device Variables1Read Primary Variable34Write Primary Variable Damping Value35Write Primary Variable Range Values36Set Primary Variable Upper Range Value23Read Loop Current and Percent ofRangeRead Dynamic Variables and LoopCurrent6Write Polling Address37Set Primary Variable Lower Range Value7Read Loop Configuration40Enter/Exit Fixed Current Mode8Read Dynamic Variable Classifications41Perform Self Test9Read Device Variables with Status42Perform Device Reset43Set Primary Variable Zero11Read Unique Identifier Associated withTag12Read Message44Write Primary Variable Units13Read Tag, Descriptor, Date45Trim Loop Current Zero (4.000mA)46Trim Loop Current Gain (20.000mA)Write Primary Variable Transfer 15Read Device Information4716Read Final Assembly Number4917Write Message50Read Dynamic Variable Assignments18Write Tag, Descriptor, Date51Write Dynamic Variable Assignments19Write Final Assembly Number53Write Device Variable Units20Read Long Tag59Write Number of Response Preambles6Write Primary Variable Transducer SerialNumber

http://www.microcyber.cnRead Unique Identifier Associated with21Long Tag105Read Burst Mode Configuration22Write Long Tag107Write Burst Device Variables38Reset Configuration Changed Flag108Write Burst Mode Command Number48Read Additional Device Status109Burst Mode ControlFactory default polling address (short address) of HART module is „0‟.Serial transmission mode supported by HART module is Modbus RTU mode.Serial communication interface feature supported is shown in Table 1.5.Table 1.5 Feature List of Modbus Communication InterfaceSlave addressDefault parameterOptional range11-247Baut rate96001200,2400,4800,9600, 9200,35700,38400,57600Data bits87, 8 (this version only supports ModbusRTU, so 8-bit is valid)Stop bits11, 2EVENODD，EVEN，NONELower-High OrderLow-High Order，High-Low OrderParityCRC verificationMODBUS communication interface of HART module supports the followingMODBUS commands.Table 1.6 Command List Supported by Modbus Communication InterfaceCommand No.1.6Command NameNo.Command Name1Read coil status4Read input register value2Read discrete input status5Write coil3Read holding register value16Write multi register valuesDimensionsHART module PCB depth is 1.6mm, rectangular. Front (shown in Figure 1-4),the highest component is 5mm from board surface; Back, the highest is 9mmfrom board surface. Others all are surface mount components, lower than4mm. Length, width, fixed hole‟s location, etc. of HART module are shown infigure below.7

2.52.62.665.02.5Figure 1.4 Front Dimensions of HART ModuleUnit: mm单位：mm5.01.69.0Figure 1.5 Front Back Height Dimensions of HART ModuleIDC16(2x8) standard socket of 2.54mm spacing is used on backside, to pluginto user board; HART module has another 3 fixed holes of Dia.3.0mm, usedto fix HART module onto user board.8

http://www.microcyber.cn2. Quick Configuration2.1Configuration Tool IntroductionAs previously mentioned, Microcyber can provide PC configuration softwarefor HART module configuration. Or provide HART module DD files for HARTmaster station (PC, communicator) which owns DD file analytical ability. Heretake PC configuration software as an example, hardware connection is shownin Figure1-2, connection description is shown in Section 1.4.About usage and status description of HART modem, refer to “HART ModemDatasheet” of Microcyber.About installation and general operation of PC configuration software, refer to“HART PC Configuration Tool” of Microcyber.Here only introduce HART module configuration and simple general operation.After wiring according to Figure1-2, and electrifying field device with HARTmodule, double-click shortcut iconHARTconfigurationsoftwareon PC which has been icrocyber\HartMPT\HartMPT.exe"), enter initial interface of HART PCconfiguration software, see figure below:9

http://www.microcyber.cnFigure 2.1 Configuration Software Icon and Intial Interface„COM3‟ in Figure 2.1 is Windows system‟ virtual serial port used for USBinterface HART modem. If driver of HART Modem (virtual serial port chip) iscorrectly installed, green light will be on when HART modem is inserted intoPC; otherwise, check wiring and driver‟s installation result. After module iselectrified, check status of HART module‟s LED1 and LED2, if both arenormally on, that means HART module is on standby.In webview of intial interface, right-click serial port node (COM3), select „singlenode‟ „node 0‟. Configuration software sends „universal command 0‟ toquery if HART device with short address „0‟ is online.10

http://www.microcyber.cnFigure 2.2 Poll Online HART ModuleFactory default short address of HART module is „0‟, without error for wiringand power supply, HART configuration software will list query result, shown inFigure 2.2. The device with short address „0‟ in Figure 2.2 (Hereinafter called 0device) is online, click 0 device, after continuous communication betweenconfiguration software and HART module, change of TAB webview is shown inthe following figure.Figure 2.3 TAB of HART Module11

http://www.microcyber.cnHART module, compared with other type of HART device, its TAB 'ModBus toHart Setting‟ and ManufactureInfoConf are unique, and other 4TABs shown inthe figure above are shared by all HART devices. Here only emphasizes 'Modbus to HART Setting‟ of HART module, as shown below:Figure 2.4 TAB of Gateway ConfigurationTo configure HART module, firstly modify ' ModBus to Hart Setting \ DetailedSetup \ Normal Operation‟ option groupt to 'Configuration Mode‟. Under thismode, the user can operate other functions of „Detailed Setup‟; underconfiguration mode, HART module won‟t send Modbus data to user board ininitiative and cycle mode.To configure HART module, there are three steps:1. Configure Modbus interface; 2. Configure device variable; 3. Configuredynamic variable.1. Configure Modbus interface, that is to use 'ModBus to Hart Setting \ Detailed12

http://www.microcyber.cnSetup \ Modbus Variables‟, configure Modbus interface based on differentModbus device interface features.2. Configure device variable, that‟s to use 'ModBus to Hart Setting \ DetailedSetup \ Device Variable‟, configure device variable based on different Modbusdevice data storage mode, i.e.data register is mapped to device variable.3. Configure dynamic variable, that‟s to use 'ModBus to Hart Setting \ DetailedSetup \ Device Variable Assignments‟, configure dynamic variable based onrequirements to HART dynamic variables from different end users, i.e.devicevariable is mapped to dynamic variable.As mentioned earlier, configuration function of the software can also berealized by HART master station (such as PC, communicator) with DD fileanalysis capability. The functions decribed by HART module DD files arebasically same with HartMPT configuration software. The figure below isfunction menu tree of DD files, and the user can quickly find the parameters toconfigure in 475 communicator, etc. by the function menu tree.13

http://www.microcyber.cnStatus2-1Test Device2-1-11 Status2 Test self3 Device TestProcess Variables12341PVPV % rngePV LoopCurrentPv Range12345678Device 0Status group 0Status group 1Status group 2Status group 3Status group 4Status group 5Ext dev statusOperate mode 14-2-13 USL4 LSL5 Min span6 URV7 LRVRe-range2-4-11 Range ValuesDevice 12 Apply Values4-2-2Anolog output2-4-2Diag/Service1 Test Device22 CalibrationCalibrationBasic Setup312345672-4TagLong TagPv UnitPV xfer fncntPV DampRange valuesDevice information1 Re-range2 Anolog output3 Sensor trim4 Coils trim5 Registers trim6 Recall factory trim2-4-32-4-4Coils trimRegisters trimDevice 31 Registers trim2-4-61 Manufacturer2 Model3 Dev id4 Cfg chng count5 Tag6 Long Tag7 Date8 Write project9 Descriptor10 Message11 Final asmbly num12 Revision #’s1 Classe2 Unit3 USL4 LSL5 Min span6 URV7 LRV1 Coils trim3-7On lineDevice 24-2-3Sensor trim2-4-51 Classe2 Unit3 USL4 LSL5 Min span6 URV7 LRVPV Loop currentPV Alrm typPV Channel flagsPV Xfer fnctnLoop current modeLoop testD/A trim1 Zero trimDevice information1 Process Variables2 Diag/Service3 Basic Setup4 Detailed Setup5 Review12345671 Classe2 Unit4-2-4Recall factory trim1 Classe2 Unit3 USL4 LSL5 Min span6 URV7 LRV1 Restore to default factory2 Save as factory3 Restore to factoryDevice 44-2-53-7-12Revision #’s1 Classe2 Unit3 USL4 LSL5 Min span6 URV7 LRV1 Universal rev2 Fld dev rev3 Software revDevice 54-2-63 USL4 LSL5 Min span6 URV7 LRVDevice Variable AssignmentsDetailed Setup41 Device Variable Assignments2 Sensors3 MODBUS4 Signal condition5 Output condition6 Device information7 Configuration Mode4-15MODBUS VariablesSensorsReview1 Model2 Manufaturer3 Write project4 Device id5 Cfg chng count6 Max dev vars7 Tag8 Long tag9 Descriptor10 Message11 Date12 Final asmbly num13 Universal rev14 Fld dev rev15 Software rev16 Poll addr17 Loop current mode18 Num req preams19 Num resp preams1 PV is2 SV is3 TV is4 QV is4-3-14-212345674-34-3-24-3-3MODBUS VariablesDevice statusPV RangeDevice variable 0Device variable 1Device variable 2Device variable 3Device variable 4Device variable 54-51234PV LRVPV URVPV % rngePV Damp4-5-1Output condition1 Analog outputDevice information1 Manufacturer2 Model3 Dev id4 Cfg chng count5 Tag6 Long Tag7 Date8 Write project9 Descriptor10 Message11 Final asmbly num12 Revision #’sPV Range1 PV Range Source2 PV Range OptionDevice variable 04-3-4Analog output1 PV Loop current2 PV alrm typ3 PV Channel flags4 PV Xfer fnctn5 Loop current mode6 Loop test7 D/A trim4-5-2Hart output1 Poll addr2 Num req preams3 Num resp preams1 Default Unit2 Modbus function Code3 Register address4 Register Date Type5 Scaling Factor6 Uper Register Address7 Lower Register AddressDevice variable 24-3-64-6-121 Default Unit2 Modbus function Code3 Register address4 Register Date Type5 Scaling Factor6 Uper Register Address7 Lower Register AddressDevice variable 14-3-52 HART output4-6Device Status1 Device Status register address2 Device Status Bit parttren3 Register Data TypeSignal Condition4-41 Address2 Baud Rate3 Data Bits4 Parity5 Stop Bits6 CRC OrderDevice 0Device 1Device 2Device 3Device 4Device 5Max dev varsModbus1234567891 Classe2 UnitRevision #’s1 Universal rev2 Fld dev rev3 Software rev1 Default Unit2 Modbus function Code3 Register address4 Register Date Type5 Scaling Factor6 Uper Register Address7 Lower Register AddressDevice variable 34-3-71 Default Unit2 Modbus function Code3 Register address4 Register Date Type5 Scaling Factor6 Uper Register Address7 Lower Register AddressDevice variable 44-3-81 Default Unit2 Modbus function Code3 Register address4 Register Date Type5 Scaling Factor6 Uper Register Address7 Lower Register AddressDevice variable 54-3-9Figure 2.5 Function Menu Tree141 Default Unit2 Modbus function Code3 Register address4 Register Date Type5 Scaling Factor6 Uper Register Address7 Lower Register Address

http://www.microcyber.cn2.2To Configure Modbus IntefaceTo unify communication parameter is the keypoint that HART module is able tocorrectly communicate with user board, the communication between them isModbus-RTU protocol. To use 'ModBus to Hart Setting \ Detailed Setup \Modbus Variables‟ of configuration software, the user can configure Modbusinterface according to interface features of Modbus device (user board), asshown in Figure 2.6:Figure 2.6 Modbus Communication ParametersParameter Meaning:Table 2.1 Modbus Communication ParametersFunction NameAddressBaud RateData BitsParityStop BitsCRC OrderFaultUsageParametersModbus slave device addressThebaudrateusedwhen1HARTmodulecommunicate with user boardLength of data bits when HART module communicatewith user boardBytes use parity mode: odd parity, even parity, noparityNumber of stop bits9600bps8EVEN1The last two-byte CRC sending order of Modbusprotocol data packetLow-High OrderOnly when all communication parameters in Table 2.1 are fully tallied withModbus device interface features, normal communication can be ensured.After setting parameters, click „Apply‟ button to save configuration data intoHART module. To communicate with the communication parametersdescribed in Table 2.1 when HART module exchanges data with user board.15

http://www.microcyber.cn2.3To Configure Device VariablesTo configure device variable, that means to configure Modbus device data(such as instantaneous flow, cumulative flow, velocity, medium indensity,medium temperature, etc. of flow meter) information into the device variable ofHART module. HART module can support 6 device variables‟ configuration.Using „ModBus to Hart Setting \ Detailed Setup \ Device Variable‟ to configure,detailed configured information is shown in Figure 2.7:Figure 2.7 Device Variable ConfigurationUnder quick configuration, meaning of each item is shown in Table 2.2.Table 2.2 Device Variable ConfigurationDevice Variable n (n 0 5)Function NameUsageData type of user Modbus device, according to theClassdifferent type, select the corresponding item (such asvolume flow rate, temperature, pressure, density, etc.) inthe 'Type' drop-down list.UnitUSLLSLDevice data current used and displayed unit (unit of PV)Maximum limit of device variable n acquired by user‟sModbus deviceMinimum limit of device variable n acquired by user‟s16

http://www.microcyber.cnModbus deviceMin SpanRange span, usually set as sensor range upper limitdivied by 100URVBetween upper and lower limit of sensor rangeLRVBetween upper and lower limit of sensor rangeDefault UnitVariable value unit read from Modbus deviceModbus Function CodeFunction code sent out when reading device variable nRegister AddressRegister Data TypeData register address in Modbus device of devicevariable nByte order in Modbus data register of device variable nAmong them, range upper and lower limit can be modified only when currentdevice variable mapping is primary variable; Here, range upper/lower limit ofdevice variable are the same parameters with that of HART device.According the number and important degree, device data of Modbus device isassigned to 6 device variables respectively. After configuration, click on 'Apply'button to save the data into HART

MODBUS input device (measure instruments, like flow, level etc.), and then MODBUS application layer protocol is run by TTL level signal. HART module as MODBUS master and HART slave, converts data registers (such as input register, holding register) of MODBUS device into all the dynamic variables of HART commands.