DFI302 - Part K - English Manual
Contents
1. Device Type DeviceRev o i4 CFRev T Block Type RIO Wireless HART Transducer Black Profile Enhanced D Block Tag Cancel Help Figure 24 14 Adding TBWH block As a general rule for each TBWH block added it is recommended Assign the Long Tag of the HART or WirelessHART field device to the block tag attribute of TBWH Configure the MODE_BLK parameter to Auto Automatic before downloading the configuration on the DF100 Creating a Foundation Fieldbus strategy by using the DF100 Off Line DF100 RIO Wireless HART Transducer Block TI 400W 01 BE elelee ele fe fe Bile i TAG_DESC P STRATEGY ALERT KEY Et MODE _ BLK nat Auto i ACTUAL 3 PERMITTED Po H UFDATE_EWT G BLOCK_ALM TCTRANSDUCERTYPE H TRAN SOUCER_TYPE i TRANSDUCER_TYPE_ WER 1 m m m m m m Clear Close Help Figure 24 15 Configuring the MODE_BLK parameter Configure the HART_EXPD_DEV_INFO parameter with the attributes of the field device that will be mapped by TBWH Refer to Library B Function Blocks Instruction Manual as well as the HART or WirelessHART field device manual to configure correctly this parameter Off Line DF 100 RIO Wireless HART Transducer Block 11 400W 01 ES sel e a i a S MO D_ ERROR n peA oE hani THAT VERSION AU h_OF_PROCESS_VARIABLES HART OD REVISION i HART_DEVICE_REVISION HART_DEVICE_TYPE HART MANUFACTURER_ID HART_DIS2. Strategy New Block Attach Block Delete Control Module Attributes Figure 24 31 Adding new functions blocks to the FBAP The Attach Block dialog box will open as shown below Attach Block Figure 24 32 Attaching blocks to the Control Module The available function blocks for the application are showed in the Attach Block box For the aimed strategy the function blocks that must be inserted will appear in the box So select them one by one and click the OK button When the Attach Block process ends the application will be as shown in the following figure Gi Process Cell 1 Mala E M Process Cell control Module 1 gb WAI TI 400W 01 lg b WiAI TI 400W 02 ARITMETICO eure 24 33 Blocks added to the Control Module Another way to attach the blocks Is left clicking the element and drop it to the window A new tag can be done to the Control Module right clicking it and selecting Attributes For the aimed example will be attributed Temperatura Moinho de Bolas Configuring the Control Strategy Step 10 Now the user is ready to develop the control strategy First right click the Temperatura Moinho de Bolas icon and select Strategy The Strategy window will appear as shown in the following figure 24 17 DFI302 User s Manual AUG 14 K 24 18 i Temperatura Moinho de Bolas Slee i Figure 24 34 Strategy window It is recommended to minimize the strategy window Thus it i
3. User s Manual AUG 14 K I PROJ_DF100 PROJ _DF1O0 E 4 Application Process Cell Figure 24 28 Creating the Control Module To arrange the screen click the Process Cell 1 window So choose Window menu on the Syscon toolbar and then Tile option As following return to the Process Cell1 window Right click the Process Cell1 item and choose New Control Module The figure below shows creating the New Control Module Ii Process Cell 1 Sle PROJ_DF1C Process Ce i Hew Control Module Attributes PRO DF1O0 4 Application me Process Cell 1 etc Fieldbus Networks a HSE Network 2 Ga DE LOO E Recycle Bin Figure 24 29 Creating the New Control Module The New Control Module dialog box will appear Name it with the tag related to the application To continue click OK Control Module Cancel Help Figure 24 30 Attributing tag to the Control Module IMPORTANT Remember that not all characters are valid when naming the elements with tags Inserting Blocks in the Control Module Step 9 Now the user can add function blocks which will participate in the strategy of the mill temperature monitoring in the Logical Plant Right click the Control Module 2 item and choose Attach Block option as shown in the next figure 24 16 Creating a Foundation Fieldbus strategy by using the DF100 fi Process Cell 1 Process Cell 1 Control Module
4. 24 38 Offline characterization in the Strategy window The Off Line Characterization dialog box will appear 24 20 Creating a Foundation Fieldbus strategy by using the DF100 Off Line DF 100 WIO Analog Input WAI TI 400W 01 alle J d lt gt lo E E D boat Handing CF Default TAG_DESC STRATEGY i ALERT_KEY E MODE_BLK BLOCK_ERR P H 0uUT 0o J m oN A to Pa SIMULATE 4 0D_ SCALE GI OUT_SCALE A GRANT_DENY STATUS STATUS OPTS i CHANNEL mi mme Figure 24 39 Offline characterization in the function block Double click at the right side of the parameter to change it Another option is click it once and then in Edit to start editing the parameter value At the ending click End Edit Off Line DF100 WIO anaip WAI Tl 400W 01 CF Default TAG DESC i STRATEGY ALERT_KE Y Et MODE_ BLK E P Gl OLIT SIMULATE AXD_S CALE OUT_ SCALE Cancel Edit End Edit lea Close Help Figure 24 40 Editing the parameter in the Function Block Characterization box The following list shows the parameters that must be set for this area 24 21 DFI302 User s Manual AUG 14 K DEVICE TAG BLOCK PARAMETER TI 400W 01 HART_EXPD_DEV_INFO HART_VERSION 7 NUM_OF_PROCESS_VARIABLES 12 HART_DD_REVISION 0 HART_DEVICE_REVISION 2 HART_DEVICE_TYPE 15881 MANUFACTURER _ID 62 DISTRIBUTOR _ID 62 ANALOG_DISABLE Unused DEVICE_PROFILE 129 TI 40
5. PROJ_DF100 name A new window will appear This window has gt Application Logical Plant To insert control and or monitoring strategies into this part gt Fieldbus Networks Physical Plant To add devices and blocks resources transducers and function blocks to the area into this part PROJ_DF100 FROJ_DF100 4 Application e Fieldbus Networks IET SHE Metwork 2 fi Recycle Bin Figure 24 5 Area divisions Physical Plant Project Step 2 In the main window PROJ_DF100 right click the Fieldbus Networks icon B and choose Communication Settings option or through the toolbar choose Communication gt Settings The communication settings dialog box will open 24 3 DFI302 User s Manual AUG 14 K Communication Settings Server ld Smar HSEOLE Server 0 Server Context C nproces Remote C Local fe All Node Name Cancel Help Figure 24 6 Choosing the Server Confirm if the Smar HSEOLEServer 0 option has already been selected Otherwise the user must select it and then click OK Arranging the Fieldbus windows Step 3 After selecting the Server for the area click the H sign placed at left of the New Fieldbus The HSE network will appear with a tag for example HSE Network 1 Right click this item and choose Expand option The figure below shows the HSE network 6 HSE Network 2 Figure 24 7 Creating an HSE network To arrange th
6. ViAR_ DIARY lt Figure 24 17 Configuring the VAR_NAMES9 parameter of TBWH tagged TI 400W 01 Similarly for the TBWH block tagged as TI 400W 02 the VAR_NAMES9 parameter will be configured with the Tl 400W 02_ Temperatura_do_moinho value Off Line DF100 RIO Wireless HART Transducer Block TI 400W 02 E AUTO nan CAS nos lelalo EW En 5 m Offset Gl HART_VAR_CODI Gl HART_PY HART SV H HART_TY Gl HART_OV BI HART_5 Gl HART_6 Gl HART_i BI HART_ amp GI PRIMARY_ VALUE Gl VAR_UNITSS SeVAR_NAMESS onho Figure 24 18 Configuring the VAR_NAMES9 parameter of TBWH tagged TI 400W 02 Configure the LOCAL_MOD_MAP parameter with the value that the TBWH block should have to be used with Modbus The first TBWH has to be configured with LOCAL_MOD_MAP equals to 0 the second one with 1 and so on up to 99 Refer to Modbus Protocol Support section for further information about Modbus mapping and addressing 24 11 DFI302 User s Manual AUG 14 K 24 12 Off Line DF100 RIO Wireless HART Transducer Block TI 400W 01 EE AUTO n gt oO E 5 als o Difset FO CHECK_PRl FDO_ SIMULATE FD_RECOMMEN_ACT HART_BURST_CTAL_1 H HART BURST CTRL 2 H HART BURST CTRL 3 H HART BURST CTAL_4 SeLOCAL MOG MAP Figure 24 19 Configuring the LOCAL_MOD_MAP parameter From now on we will add to the configuration HSE WIO input function blocks In the DF100 the WIO Analog Input WAI
7. and Multiple Analog Input 16 MAI16 blocks are available These blocks are variations of the HSE WIO for conventional Analog Input Al and Multiple Analog Input MAI blocks respectively Despite having similar algorithms the HSE WIO input function blocks have besides data types specifically designed for the HSE WIO technology parameters named CHANNEL_TAG A HSE WIO input function block such as WAI or MAI16 uses the CHANNEL_TAG parameter instead of CHANNEL parameter to correctly address a HART variable from a TBWH transducer block Knowing that besides the already known parameterization steps for the conventional input function blocks it is necessary to parameterize the CHANNEL_TAG parameters with HART variable names In other words the names parameterized for the CHANNEL_TAG can be any names among those parameters parameterized in the VAR_NAMES9 parameters of the TBWH transducer blocks Refer to the Function Blocks Manual for additional information on the HSE WIO function blocks its parameters and parameterization For the configuration of this example add two WAI blocks The addition of the WAI blocks is similar to addition of TBWH block just described above Each WAI block will address a wireless temperature transmitter and its data via TBWH transducer block For each WAI of the purposed example the CHANNEL _TAG is configured with the VAR_NAME assigned to the HART_PV variable see TBWH block parameterization above of the addressed wirel
8. 0W 02 HART_EXPD_DEV_INFO HART_VERSION 7 NUM_OF_PROCESS_VARIABLES 12 HART_DD_REVISION 0 HART_DEVICE_REVISION 2 HART_DEVICE_TYPE 15881 MANUFACTURER _ID 62 DISTRIBUTOR _ID 62 ANALOG_DISABLE Unused DEVICE_PROFILE 129 WAI TI 400W 01 WAI TI 400W 02 ARITMETICO After the parameter setting the user can start the device communication It is necessary commissioning the DF100 If this procedure is not executed the Syscon will detect the not commissioned controller and the download for this device will be aborted Finishing the commissioning the download process can start The download process can be executed for example returning to the PROJ_DF100 window right clicking the Fieldbus Networks icon and selecting the Download option For further details about the available download types refer to the Syscon manual DF100 conventional function blocks Resource RS2 Diagnostic transducer block DIAG Control and calculation function blocks PID Control PID Enhanced PID control EPID Advanced PID control APID Arithmetic ARTH Splitter SPLT Enhanced signal characterizer ECHAR Integrator INTG Enhanced analog alarm EAALM Input selector ISEL Setpoint ramp generator SPG 24 22 Creating a Foundation Fieldbus strategy by using the DF 100 Enhanced setpoint ramp generator ESPG Timer and logic TIME Lead lag LLAG Output signal selector and dinamic limiter OSDL Constant and cont
9. 404801 405001 405981 S8 General notes about Native Addressing e lf the requested register in Modbus commands involves exclusively or not reserve address the DF100 will respond with a zero value for such register e The Modbus of DF100 is based on version known as Combined Scenario Thus the DF100 allows enabling disabling the swap of variable registers of float tyoe through the RTS_CTS parameter of Modbus MBCF block e The Modbus addresses of any available Modbus point at DF100 may also be consulted through the information page of the DF100 Web Server see next figure After launching it if necessary use the arrows of decreasing or increasing advancement to determine the desired value for the LOCAL MOD_MAP Once you determine the value of LOCAL _MOD_MAP Modbus addresses will be automatically updated 24 27 DFI302 User s Manual DEC 13 K omar MPPs gt Welcome to DF100 Webserver TAG DF100_WHG Serial number 8 BX SHAR LOCAL_MOD_MAP Informative Information x t Ll setup 4 Device Info E s WirelessHART H Lali Network Input Register H La Manager E a Modbus LE Addresses Variable Num of Regs Offset Modbus Address HART_PV Status 1 0 300001 HART_PV Value 2 1 300002 HART_SV Status 1 3 300004 HART_SV Value 2 300005 HART_TV Status 1 6 300007 HART_TV Value 2 7 300008 HART_QV Status 1 9 300010 HART_QV V
10. Section 24 Introduction 24 1 CREATING A FOUNDATION FIELDBUS STRATEGY BY USING THE DF100 This section describes the fieldbus strategy configuration by using the DF100 controller The figure below shows a ball mill rotary whose product temperature must be monitored PROJ_DF100 T4001 Temperature es TI 400VV02 A DFIoOO oeeeeeeeee WirelessHART communication Figure 24 1 Example of temperature monitoring in a ball mill The purpose is to monitor the product temperature at the center of the ball mill The product temperature is measured by two wireless temperature transmitters installed in the hull of the mill in its central part in diametrically opposite positions Measured temperatures will be transmitted from each of the temperature transmitters to the DF100 WirelessHART Gateway via WirelessHART communication In the DF100 positioned near the ball mill and connected to the HSE network control there will be special transducer blocks that will map the temperatures received from the transmitters In addition to the transducers the DF100 has function blocks that are used to calculate the average temperature of the mill from the two measured temperatures DFI302 User s Manual AUG 14 K Starting an Area Step 1 It is possible to create or edit an area from the Studio302 In the Studio302 interface select Areas A window will appear listing all areas of database To create a new area from the Studio302 r
11. TRIBUTOR_ID ANALOG DISABLE PHAR T_ DEVICE PROFILE H H HART_ACTL_DEV_INFO ie FAA T _ CRD i HART_RESF Figure 24 16 Configuring the HART_EXPD_DEV_INFO parameter i In online mode if the desired field device is connected to DF100 and commissioned it is recommended to configure the attributes of HART_EXPD_DEV_INFO parameter with the values of the respective attributes of HART_ACTL_DEV_INFO parameter 24 9 DFI302 User s Manual AUG 14 K The above parameterized attributes are specific to the considered field device in this example the TT400 Smar WirelessHART was used Therefore important to note that the values assigned to the attributes of HART_EXPD_DEV_INFO parameter depend on the type of device pressure temperature density etc and its firmware version The table below summarizes the attributes values of the HART_EXPD_DEV_INFO parameter for some Smar WirelessHART field devices 24 10 Attribute HART_VERSION LD400WH DT400WH TT400WH TT481WH Firmware 3 0 1 Firmware 1 0 0 Firmware 2 0 1 Firmware 1 0 0 NUM_OF_PROCESS_VARIABLES HART_DD_ REVISION HART DEVICE REVISION HART_DEVICE_TYPE HART _MANUFACTURER_ID HART_DISTRIBUTOR_ID ANALOG_ DISABLE HART_DEVICE_PROFILE Knowing that the second temperature transmitter used in this example whose tag is TI 400W 02 it is also a TT400 Smar WirelessHART with identical firmware to the Tl 400W 01 transmitter configure the HART_EXPD_DEV_INFO pa
12. ained RW CTRW Flip flop and edge trigger FFET Analog data transfer ADT Discrete data transfer DDT DF100 specific blocks Listed below are the blocks defined specifically for DF100 For additional information about them see Library B Function Blocks Instruction Manual Transducer Block for HART Gateway TBHG Transducer Block for WirelessHART TBWH ROM Analog Input ROMAI 16 Multiple Analog Input MAI16 24 23 DFI302 User s Manual AUG 14 K Modbus Protocol Support Supported Characteristics e RS 485 port physical level EIA 485 Modbus RTU characteristics configured in the MBCF block o BAUD_RATE up to 19 2 Kbps o STOP_BITS 1 or2 o PARITY Even odd or none o MASTER_SLAVE Master or Slave e ETH1 and ETH2 ports physical level Ethernet TCP IP Modbus TCP IP o Modbus TCP IP multimaster protocol o ETH1 DF100 can perform simultaneously the role of master and slave and it is not necessary configuration o ETH2 DF100 performs only slave role e Bypass bridge functionality conversion of the physical level When the RS 485 port is configured as Master Modbus commands sent via TCP IP to the IP Address of a given controller but whose ID is different from of this DF100 the command is retransmitted on the RS 485 port and the response that comes to this port will be retransmitted to the Ethernet port e The DF100 address on the Modbus network is configured in the MBCF block DEVICE ADDRESS parameter This devi
13. alue 2 10 300011 HART_5V Status 1 12 300013 HART_5V Value 2 13 300014 HART_6V Status 1 15 300016 HART_6V Value 2 16 300017 HART_7V Status 1 18 300019 HART_7V Value 2 19 300020 HART_8V Status 1 21 300022 HART_8V Value 2 22 300023 PRIMARY_VALUE Status 1 24 300025 PRIMARY_VALUE Value 2 25 300026 BLOCK_TAG 16 27 300028 VAR_UNITS9 9 43 300044 Discrete Input Variable Num of Bits Offset Modbus Address FD_SIMULATE 32 o 104001 LIVE_LIST_ST 1 32 104033 Holding Register Variable Num of Regs Offset Modbus Address HART_VAR_CODESS 8 o 404001 Figure 24 41 Web page with Modbus addresses for LOCAL_MOD_MAP equals to zero Modbus Combined Scenario The DF100 supports the Modbus Combined Scenario in which it is able to perform the role as master and slave simultaneously via Modbus TCP IP regardless of any configuration The selection between master and slave would only apply to the RS 485 port which could be communicating simultaneously to the Modbus TCP IP on ETH1 and ETH2 ports 24 28
14. ce identifier ID is the same of the three ports RS 485 ETH1 and ETH2 e tis possible to configure the registers swap through MBCF block RTS_CTS parameter and it is applicable to all ports RS 485 ETH1 and ETH2 Exemplifying the functionality of the registers swap the order of bytes in the Modbus message is the following if the swap was not configured RTS_CTS False 101 325 0x42 MSB 0xCA OxA6 0x66 LSB Register 402 601 OxA6 0x66 Register 402 602 0x42 OxCA In the response message in which the two registers were requested we have OxA6 0x66 0x42 OxCA If configured to perform swap of registers RTS_CTS True we have Register 402 601 0x42 OxCA Register 402 602 OxA6 0x66 In the response message in which the two registers were requested we have 0x42 OxCA OxA6 0x66 e Types of standard commands supported as master and slave FUNCTION CODE DESCRIPTION 03 of a Holding Registers range ing and writing en ee i Reading of an Input Registers range reading variables 06 Writing in a single Holding Register Writing in a Multiple Registers range Native mapping Variables mapped to Modbus regardless of configuration Field devices variables are mapped to Modbus variables in Input Register read only or Holding Register reading and writing See the item Native Mapping for details Configured mapping By configuring the MBCS Modbus block you could map some block parameters of the DF100 aiming at an addresses s
15. dd others conventional function blocks i e non specific HSE WIO ones For that in the New Block dialog box select the desired function block in the Block Type box and then in the Block Tag box give a tag to the block Click OK The next figure shows the addition of the ARTH function block AR Block 24 13 DFI302 User s Manual AUG 14 K 24 14 New Block Manufacturer c Device Type Device Rev fin z lod CF Rev i Block Type AP Block F Profile Standard Block Tag ARITMETICO Figure 24 23 Adding a conventional function block For this example the ARTH block complements the strategy and it will be used in the DF100 to calculate the average temperature in the ball mill Only transducer and function blocks were added in the DF100 WirelessHART Gateway The HART and WirelessHART field devices not support function blocks They are only mapped in the DF100 through TBWH transducer blocks The configuration with all the function and transducers blocks conventional or not is presented in the following figure A HSE Network 2 HSE HOST OF100 DIAG 1 DF100 TBHG 1 TI 400 01 TI 400v 02 wWAI TI 400 w 01 Hp WAI TI 400W 02 h ARITMETICO Figure 24 24 Complete wireless configuration Now the strategy area can be developed Application Logic Plant First is necessary to create a new Process Cell Creating New Process Cells Step 7 The Logical Plant can be di
16. discrete input variables that are mapped to Modbus as well as its respective offsets lengths in bits and Modbus addresses The Modbus addresses were calculated for few LOCAL _MOD_MAP values If you need the Modbus address of any other discrete input variable whose LOCAL _MOD_MAP is not on the table use the above equation to calculate it Discrete Input Number of Offset LOCAL_MOD_MAP VETIEJ Bits 0 1 2 3 4 5 10 20 30 40 50 99 FO_SIMULATE 20 104001 104081 104101 104151 104201 104251 104801 108001 105801 106001 106801 108951 mess i e Towa oa Toae roves T0423 1033 103003 103533 106003 106533 T0003 24 25 Creating a Foundation Fieldbus strategy by using the DF100 Input Register Variables The Modbus address for any input register variable can be calculated by the following equation EnderecoModbusIR 300 001 LOCAL_MOD_MAP 80 Offset Where e EnderecoModbuslR Modbus address of the input register variable e LOCAL _MOD_ MAP value of the same name parameter that was configured by user in the TBWH block e Offset displacement of the variable with respect to the base address The following table presents the DF100 input register variables that are mapped to Modbus as well as its respective offsets lengths in bits and Modbus addresses The Modbus addresses were calculated for few LOCAL MOD_MAP values If you need the Modbus address of any other input register variable whose LOCAL MOD_MAP is no
17. e screen click the area window So choose Window menu on the Syscon toolbar and then Tile option Adding the Controller Step 4 Right clicking the HSE Network 2 it opens a dialog box to add new devices Choosing New option it is possible to select devices such as Bridges Controllers and Devices for the area For the aimed strategy choose Controller option Confirm this choice observing the following figure This number changes if another area was created before When a new HSE area is created this number increases 24 4 Creating a Foundation Fieldbus strategy by using the DF100 i HSE Network 2 F eee HSE Mek JE Device Bridge Controller Device from Template Download Bridge From Template Upload Controller From Template Download Schedule Attributes Figure 24 8 Choosing the Controller After selecting that option it opens a window as shown in the next figure New Controller Bridge Advanced Options Manufacturer 7 Device Type DF100 Device Rew 02 OD Few E CF Rev 0 W Follow the Latest DD and CF Revisions Device Tag Upstream Fort Is Redundant HSE only Cancel Help Figure 24 9 Setting the Controller Select the DF100 device in the Device Type box In the Device Tag box enter DF100 or another tag and click OK IMPORTANT Not all characters are valid when naming the elements so pay attention The valid charac
18. equence and so use the reading or writing commands in registers range as Holding Register Native mapping Mapped variables Several TBWH block parameters of the DF100 are mapped to Modbus In other words as the TBWH maps field devices a variable set of each field device is mapped to Modbus For each instantiated TBWH block whose LOCAL _MOD_MAP parameter is properly parameterized the following parameters variables are available to Modbus The valid values interval for the LOCAL_MOD_ MAP parameter is defined in the Parameters description of the TBWH block 24 24 Creating a Foundation Fieldbus strategy by using the DF 100 TBWH block tag FD SIMULATE LIVE_LIST_ST HART PV HART_SV HART_TV HART QV HART_5V HART_6V HART_7V HART_8V PRIMARY_VALUE VAR_UNITS9 HART VAR_CODES8 1 All bits of Field Diagnostics are mapped See definition of Field Diagnostics for DF 100 2 For HART PV to HART 8V and PRIMARY VALUE variables Status and Value are mapped Discrete Inputs Variables The Modbus address for any discrete input variable can be calculated by the following equation EnderecoModbusDI 104 001 LOCAL_MOD_MAP 50 Offset Where e EnderegoModbusDI Modbus address of the discrete input variable e LOCAL MOD _ MAP value of the same name parameter that was configured by user in the TBWH block e Offset displacement of the variable with respect to the base address The following table presents the DF100
19. ess temperature transmitter The two following figures demonstrate the CHANNEL TAG configuration of the WAI blocks that will address the temperature transmitters Tl 400W 01 and TI 400W 02 respectively Off Line DF 100 WIO Analog Input WAI TIl 400W 01 LO_LO_LIM J HI_HI_ALM HHI ALM H LO_ALM A LO LO_ALM H PRE_OUT_ALM H OUT_ALM OUT_ALM_SUM INVERT_OFTS E HANNEL TAG 41 Cancel Edit End Edit Clear Close Help Figure 24 20 Configuring the CHANNEL_TAG that addresses the HART_PV of TIl 400W 01 Creating a Foundation Fieldbus strategy by using the DF100 Off Line DF100 WIO Analog Input WAI TI 400W 02 AUTO CAS n05 lelalo EY 55l S Fames vate Li e era H HI_HI_ALM HHI ALM LO_ALM H LO_LO_ALM PRE_OUT_ALM H OUT_ALM OUT_ALM_SLM INWERT_OPTS BeCHANNEL_TAG 4 Cancel Edit End E dit Clear Close Help Figure 24 21 Configuring the CHANNEL_TAG that addresses the HART_PV of Tl 400W 02 With the addition of the WAI blocks we have finished adding the HSE WIO transducers and function blocks See the figure below for having a general idea of HSE WIO blocks configured so far ly HSE Network 2 SSB HSE Network 2 d HSE HOST Te i DFIO0 RB 1 DF100 D1AG 1 DF100 TBHS 1 TI 4 00 01 H TI 400W 02 b WAI TI 400W 01 gob WAI TI 400W 02 Figure 24 22 HSE WIO transducers and function blocks Adding Conventional Function Blocks Step 6 The user can also a
20. ight click inside the Areas window then choose New Area File Settings Tools Window Help flee sie MDO 48RFR PEF Qnzeve oy Smar Cl e Areas Site Smar Current Database System302 r l Ela Engineering Database eee Areas i Fy gi Applications Multi user status o YS73 DF100_A1 pee Control Modules Sixes j Logics E a Network Devices Mew area Edit area seven mi Controllers Export for standalone PR se IO Points Remove area Replace area a Net Ifa L GH Field Devices ka A e Documentation Search Po Search by Name Figure 24 2 Creating a new area Eo Another way to create a new area is from Syscon Click the icon in the Studio302 toolbar To create a new area on Syscon choose File gt New or through the toolbar choose New button i The dialog box shows the areas options Select HSE Area as shown in next figure 24 2 Creating a Foundation Fieldbus strategy by using the DF100 HSE Area Predefined area Strategy Template Device Template Bridge Template Controller Template Figure 24 3 Options to create Syscon areas After choosing the area type it opens a window to the user give a name to the new area Setup New Area Area Hame PROJ DF10d o Figure 24 4 New area name Type the name for the area in the Area Name box and click Ok For this example it chooses
21. oes the fast link procedure just right clicking the function block The links necessary for this strategy are Direct Links e OUT WAI TI 400W 01 gt IN_1 ARITMETICO e OUT WAI TI 400W 02 gt IN_2 ARITMETICO After linking the parameters specified above the strategy window will be as shown in the following figure i Temperatura Moinho de Bolas E meg Pi Figure 24 37 Links between the Function Blocks 24 19 DFI302 User s Manual AUG 14 K Function Block Characterization Step 13 The function blocks that are in the strategy must be set according to the application for them So it is necessary to do the block characterization The online and offline modes are possible for the block characterization In the offline mode the parameters are set before starting the communication between the devices The online characterization is executed directly in the devices when the plant is already communicating To change the function block parameters consider the following steps Select the block to characterize Right click it and select the Off Line Characterization option or double click it The following figure shows the block that is being done the offline characterization 6 Temperatura Moinho de Bolas Seles Delete Define Area Link Parameter Edit User Parameter Tags Find Attached Device OFF Line Characterization Show Hidden Links Same Width and Height Show Info Properties Figure
22. rameter exactly as was done for the TBWH of TI 01 400W Configure the each one of the names that will be attributed to the HART_PV HART_SV HART_TV HART_QV HART_5V HART_6V HART_7V HART_8V and PRIMARY_VALUE variables These names have to be configured in the VAR_NAMES9 parameter The names values configured to the attributes 1 to 9 of this parameter refer to the names that will identify in a single way in the DF100 scope that has the TBWH the HART_PV to PRIMARY_VALUE variables respectively This procedure is necessary because the HSE WIO input function blocks will use these names to address the HART variables values The following figure shows the parameterization of the VAR_NAME that will identify the HART_PV variable provided by the Tl 400W 01 transmitter Important to note that depending on the strategy not all VAR_NAMES need to be parameterized See Library B Function Blocks Instruction Manual for additional information on the TBWH transducer block its parameters and parameterization Creating a Foundation Fieldbus strategy by using the DF100 Off Line DF100 RIO Wireless HART Transducer Block TI 400W 01 fel are nan EAs oos elalo ae I S BI a m Parameter lt lt lt lt H HART_VWAR_CODESS HART _PY HART_SY H HAR T_T H HART_OW H HART_Si H HART_EW H HART_ A H HART_ov H PRIMARY WALLE VAR _UNITSS SBVAR_NAMESS Sas on epee Caen ea T 400MW 01_ Temperatura do moinho a
23. s possible to see the whole area The strategy window offers several tools for drawing Refer to the Syscon manual for further details Adding Blocks to the Strategy window Step 11 Now the function blocks can be added to the Temperatura Moinho de Bolas window In order to get this click the first block WAI Tl 400W 01 and drop it into the strategy window A function block will be automatically created The next figure shows the function block added to the strategy window i Temperatura Moinho de Bolas Seles RaehOD eR oO RPdL PPC OR Sdaieeeoek edie pitenee aa oy Figure 24 35 Block inserted into the strategy window Repeat the drag and drop procedure for the other blocks WAI TI 400W 02 and ARITMETICO Linking the Blocks Step 12 There is a specific tool to link the blocks the Link button on the Strategy toolbar Click this button on the toolbar and then in the WAI TI 400W 01 function block The dialog box for linking the input and output parameters will appear Select OUT and then click the OK button as shown in the following figure Creating a Foundation Fieldbus strategy by using the DF100 Output Parameter Selection DF100 WIO Analog Input maf M OUT_ALM Cancel Help Parameter Description The primary analog value calculated as a result of executing the function block Figure 24 36 Linking the Function Blocks Move the mouse cursor up to the block that will be linked The user also d
24. t on the table use the above equation to calculate it Input Register Variable Number of Offset LOCAL_MOD_MAP Registers 0 1 2 3 4 5 10 20 30 40 50 99 pann ovsons f of soon soos sooner stoi tna soos soem A E of E E E E E E EE s7e27 E E 3 soo somo sow soso a soo E E EE 0750 panconrss 3 E E E a E sone soi susie sores suze sve E 24 26 Creating a Foundation Fieldbus Strategy by using the DF 100 Holding Register Variables The Modbus address for any holding register variable can be calculated by the following equation EnderecoModbusHR 404 001 LOCAL_MOD_MAP 20 Offset Where e EnderecoModbusHR Modbus address of the holding register variable e LOCAL MOD_MAP value of the same name parameter that was configured by user in the TBWH block e Offset displacement of the variable with respect to the TBWH base address The following table presents the DF100 holding register variables that are mapped to Modbus as well as its respective offsets lengths in bits and Modbus addresses The Modbus addresses were calculated for few LOCAL _MOD_MAP values If you need the Modbus address of any other holding register variable whose LOCAL_MOD_MAP is not on the table use the above equation to calculate it Holding Register Number of Offset LOCAL_MOD_MAP VE TIE 2 Registers 0 1 2 3 4 5 10 20 30 PT 50 99 HART_VAR CODE C A a 404001 404021 404041 404061 404081 404101 404201 404401 404601
25. ters are A Z a z 0 9 The invalid characters are 1 GER amp 15 lt gt 7 At this moment the following blocks will be created in the configuration Resource block Diagnostic transducer block Transducer block for HART Gateway Transducer Block for HART Gateway TBHG One transducer block for the first HART or WirelessHART field device Transducer Block for WirelessHART TBWH 24 5 DFI302 User s Manual AUG 14 K HSE Network 2 HSE HOST DFIOO RB 1 DFLOO DIAG 1 DF100 TEHG 1 DF100 TEWH 1 Figure 24 10 Blocks created after adding the controller Quite simply we understand that the DF100 WirelessHART Gateway and the WirelessHART and HART field devices will be mapped on SYSTEM302 by the transducer blocks This is possible due to the HSE WIO technology embedded in the DF 100 The DF100 will be mapped by the transducer block single and mandatory called Transducer Block for HART Gateway TBHG Furthermore each HART and WirelessHART field device will be mapped by transducer blocks called Transducer Blocks for WirelessHART TBWH There will be as many TBWH blocks as there are HART and WirelessHART field devices needed in the configuration Adding HSE WIO Transducer and Function Blocks Step 5 The first HSE WIO transducer block TBHG is automatically created when the DF100 controller was added to the Physical Plant Make sure that i
26. ts MODE_BLK parameter is configured to Auto Automatic before downloading the configuration on the DF100 This block as monitored in Online mode shows the list of HART and or WirelessHART field devices currently connected to the DF100 Thus we can understand that the TBHG provides to the system and to the user the Live List of field devices connected to the DF100 via WirelessHART network See Library B Function Blocks Instruction Manual for additional information on the TBHG block The next step is to associate the TBWH block to the first wireless temperature transmitter of this example This TBWH was also automatically created with the DF100 TBWH 1 tag when the DF100 controller was added The transmitter Long Tag has to be attributed suppose TI 400W 017 to the Block Tag of TBWH block The following figures show the association between TBWH and the transmitter 1 The DF100 integrates HART 4 to 20 mA conventional field devices via WirelessHART adapters In online mode the Long Tags of transmitters connected to DF100 can be found in the LIVE_LIST_TAG_x parameters of TBHG block 24 6 Creating a Foundation Fieldbus strategy by using the DF100 fa HSE Network 2 E S HSE Network 2 HSE HOST Peer 19 HSE _NMA_WFE Manannan fa E H5E_F6_VFD OF100 R6 1 H O DFLOO D14G 1 O DFIO0 TBHS 1 DF100 TB ul H 1 OFF Line Characterization Customize Characterization Delete Block On Line Characterization A
27. ttributes Figure 24 11 Changing the attributes of TBWH block Block Attributes Manufacturer Smear Device Type DFO Device Rev D2 OD Rew 03 CF Rew 01 Block Type RIO Wireless HART Transducer Block Profile Enhanced on Block Tag Figure 24 12 Changing the attributes of TBWH block Depending on the strategy you can add as many TBWH blocks as there are HARI and WirelessHART field devices supported by the DF100 see section Technical Specifications For the purposed example just add another TBWH block which will map the second temperature transmitter Its Long Tag will be Tl 400W 02 To add a new Function Block FB click the H sign near to the DF100 controller and right click the Virtual Field Device HSE_FB_VFD icon Choose New Block option 24 7 DFI302 User s Manual AUG 14 K 24 8 Bi HSE Network 2 Seles Jel SR HSE Network 2 HSE HOST E DFIOO PERELE T HE HSE_NMA WFD y Mew Block E DF1O0 l Attach Block H L DF100 _ E DFioo Ic H O Tion Figure 24 13 Adding New Blocks The New Block dialog box will appear In the Block Type option the blocks designed to the controller can be selected Select the block in the Block Type box and name it in the Block Tag box Click OK The following figure shows adding the second TBWH block that will map the transmitter whose Long Tag is TI 400W 02 New Block Manufacturer I ae
28. vided in several process cells according to the plant To create a new process cell right click the Application icon and select New Process Cell item Creating a Foundation Fieldbus strategy by using the DF100 PROJ_DF100 PROJ DFIOO Application i ie Fieldbus i Mew Process Cell 2 HSE Network 2 Gay DFIOO E Recycle Bin Figure 24 25 Inserting a Process Cell The dialog box to name the Process Cell will open Process Cell Figure 24 26 Attributing tag to the Process Cell If the user needs name the Process Cell with a specific tag Enter it in the Tag box and click OK To create more process cells the procedure above can be repeated After inserting the Process Cell the PROJ_DF100 window will be according to the next figure PROJ DF1O0 E PROJ DE1O0 TG Frocess Cell 1 Lue Fieldbus Networks amp HSE Network 2 Gis DFLOO E Recycle Bin Figure 24 27 Area window after inserting the Process Cell The user must remember that Application is a virtual division It only divides a large plant For example if the plant has two networks they can be Process Cells in the Syscon One Application can have several Process Cells but a Process Cell cannot be in more than one Application Creating a Control Module Step 8 Now the user can create a Control Module in the Application section Right click the Process Cell1 icon and choose Expand item 24 15 DFI302
Download Pdf Manuals
Related Search