BME AHO0412 HART output setup in Control Expert examples

[jamesdlane986]

Hello,

I'm doing a sizable hardware and software migration project for a client. Besides all the configuration and programming to migrate from Proworx32 and Quantum hardware to the X80/M580 and Control Expert, I am adding 5 AHO0412 modules that will be interfaced with flow and pressure control valves with a Flowmaster Beta positioner HART compatible controller. I'm looking for some basic PLC code examples for interfacing the AHO0412 module to any HART compatible controller. I have an M584040 CPU, 5 BMEXBP1200 backplanes, 

[ciupol]

Hello jamesdlane986,

There are few things to consider when using HART modules:

1. Make sure you install HART module in an ethernet slot on the backplane - not all slots on ethernet backplane are ethernet compatible (sic!). The ethernet compatible slot have two connectors vs on connector on non compatible slots.

2. In Control Expert you add HART module as any other module. I would suggest adding the module as Device DDDT and not topological (selection box on the bottom of the window where you select the module).

3. You can change Device DDT name in the module configuration window. I typically use something more descriptive than default name:

4. You have to add the module under the CPU in DTM browser. You can configure HART Device DDT name when you double click the processor, go to Device List, and click HART module. Again I make it more descriptive than default name.

5. After doing the above two Device DDTs are created in Data Editor:

The first one is standard DDT for analog module. That is where you can see 4-20mA channels.

The second one is where you can see HART Dynamic Variable (PV, SV, TV, QV).

6. Finally to make it all work, in DTM browser right click on the CPU and select Device Menu -> Additional functions -> Store Device Conf to FDR. To execute this step you have to be connected to CPU through ethernet port (not USB).

There is really no special logic to make it work. You just grab the value from Device DDT and map it to a variable.

[jamesdlane986]

Do I associate the 2 DDTs by entering the analog output tag names in the "User Defined Label" column?

[ciupol]

jamesdlane986, I am not sure where "User Defined Label" column is. Screenshots are always helpful.

The 2 DDTs are not really associated you can name them however you want. I just showed how I am doing this. 

[jamesdlane9861]

How does the configured module in the rack know that the modules I created in DTM Browser know they are 2 in the same devices? I have 5 HART AHO0412 modules on a rack. Do the rack configuration and the DTM Browser configurations get aligned in the background automatically? Thanks, James

[Trinxs1]

I am unable to view the images as they appear as triangles.

For each HART module two separate data structures are created. 
Firstly the data structure created for the 4..20mA channels will usually have a topological address i.e. it will have a name plus a location of the form "drop.rr.slot"  where the drop number, rack number and slot should relate to the location of the module.
The DTM created for the ethernet IP communications of the module requires a format that identifies the drop number and the slot within the first rack of the module.  Note only the first rack of any CPU or drop can be an ethernet rack where a HART module can be installed.  When naming the data structures keep a similar convention that relates the module to its location and either the 4..20mA or HART communication.

In the configuration of the HART module DTM please enable both the reset and the enable registers so you can disable any HART channels not used.

[ciupol]

jamesdlane9861 I think I know what you are asking now and this is actually important step and I forgot to put in my original post. Once you create DTM for the HART module in DTM browser open whatever is above your module (probably CPU), find your module and go to address setting tab. There is a identifier field that you have to edit according to your physical module position. If you hover above it will give you explanation about formatting - the explanation is not great though so here it is:

- If the module is on remote rack (remote IO drop) it should be Cyyy_xx_AHI0812 or Cyyy_xx_AHO0412 based on what module you have. yyy is drop number. Must be three digits so use leading zero, for example 004 for drop 4. xx is slot number. Again must be two digits, for example 04 for slot 4.

- If the module is on the local (the one with CPU) rack of standalone system (not hot standby) it should be zzz0_xx_AHI0812 or zzz0_xx_AHO0412. Where xx is slot number as previously and zzz is device name prefix for DHCP server. By default zzz is Mx8 but you can change it in Tools->Project Settings->Configuration->Device name prefix for DHCP Address Server. The only reason you would want to change it is fi you have multiple CPUs on the same IO network (flat network). Each CPU needs to be DHCP server for its own HART modules so the prefix is used to group HART module with the CPU they belong to.

- According to the tooltip that shows when you hover over identifier field there are two more possible formats of the identifier , namely zzzA_xx_AHI0812 (zzzA_xx_AHO0412) and zzzB_xx_AHI0812 (zzzB_xx_AHO0412) used for hot standby system where A and B are hot standby CPUs but those, according to my knowledge, would be never used as IO modules can't be installed on local racks of hot standby system. There are some other modules though (NUA module that I am aware of) that use similar format of identifier and can be installed on remote rack of hot standby system. That is why, I assume, they put it in a tooltip.

Hopefully this answers your question.