Endress Hauser CM442

A real beginner here as far as knowing what i'm doing. Have a new Endress Hauser CM442. Added it to the Devices using OPC UA. Brought into tags through the OPC and can see active tags. The problem i cannot figure out is how to get the pH and temp values from the CM442 to Ignition. Wondering if anyone can guide me through this step.

This isn't a clear description of what you've done.

Did you make a direct OPC UA connection to this device, or did you choose one of Ignition's drivers and make a device connection using a driver?

Sorry, been away for several days. Thanks for replying.
In Ignition Configuration, under OPC UA - Device Connections, selected Create New Device and added the CM442 using the TCP Driver. It connects fine and then going the Ignition Designer, going to the Tag Browser - Connected Devices - OPC Driver it shows there along with only "Diagnostics" available for tags. I need to be able to see the Input and Outputs of the CM442, specifically the pH Probe readings.
Endress technician i talked with said they are unfamiliar with Ignition and not much help beyond that.

Don't use the TCP driver. A quick google suggests that it supports Modbus TCP. Create a driver connection with that driver, and either google for or request the list of Modbus registers from E+H.

Note the tags will not appear themselves with Modbus, you need to create them yourself. The manual describes the syntax:

https://docs.inductiveautomation.com/display/DOC81/Modbus+Addressing

Thanks Matrix_Engineering. I followed the directions and creating the tags i get error_configuration. If i put the port number down in the OPC Item Path i get the value correct at 44818 so i know the connections are good, it's just i'm missing the correct path ns=1;s=[WasteWater_Controller][Diagnostics]/Port. I also tried creating a new Folder looking at their EDS file called Params and then tried to create a tag for Param46, should have gotten me the AI1Value but still getting error-configuration. Can i somehow use the EDS file for the CM442 to get the paths correct?

If you're dealing with an EDS file it's not Modbus, it's EtherNet/IP, and we don't have a first party driver for that.

@pturmel does, though. At this point you need to take a hard look at the documentation and figure out exactly what hardware and comms modules/options you have.

The OP contacted me directly and supplied the information I needed to produce a configuration for the CM44x family:

<Controller>
  <DataTypes>
    <DataType Name="CM44x_Alg_t" Alignment="2" Handle="8fd5">
      Value=REAL
      Status=INT
      Unit=INT
    </DataType>
    <DataType Name="CM44x_Config_t" Alignment="2" Handle="f9f6">
      Reserved0=DWORD
      Reserved1=SINT
      WebEnable=SINT
      Reserved2=SINT
      Reserved3=SINT
    </DataType>
    <DataType Name="CM44x_Dig_t" Alignment="2" Handle="f854">
      Value=INT
      Status=INT
    </DataType>
    <DataType Name="CM44x_Inputs_t" Alignment="2" Handle="a29a">
      Reserved0=DWORD
      DiagnoseCode=INT
      StatusSignal=SINT
      Channel=SINT
      AI=CM44x_Alg_t[1..16]
      DI=CM44x_Dig_t[1..8]
    </DataType>
    <DataType Name="CM44x_Outputs_t" Alignment="2" Handle="8e3c">
      AO=CM44x_Alg_t[1..4]
      DO=CM44x_Dig_t[1..8]
    </DataType>
  </DataTypes>
  <Tags>
    <Tag Name="Liquiline1_C" Definition="CM44x_Config_t">
      <Data>
        00 00 00 00 00 01 00 00
      </Data>
    </Tag>
    <Tag Name="Liquiline1_I" Definition="CM44x_Inputs_t"/>
    <Tag Name="Liquiline1_O" Definition="CM44x_Outputs_t"/>
  </Tags>
  <Assemblies>
  </Assemblies>
  <Modules>
    <Module Name="Liquiline1" CatalogNumber="Liquiline_CM44x" Inhibited="false" Direction="Client"
    Vendor="1182" ProductType="43" ProductCode="4252" Major="3" Minor="1"
    InRPI="200000" UnicastIn="true" InRTMF="0" OutRPI="200000" UnicastOut="true" OutRTMF="4">
      <Route>port 2 10.20.30.40</Route>
      <Application>2004 2466 2c65 2c64</Application>
      <InputTag>Liquiline1_I</InputTag>
      <OutputTag>Liquiline1_O</OutputTag>
      <ConfigTag>Liquiline1_C</ConfigTag>
    </Module>
  </Modules>
</Controller>

Nice device, fwiw. The analog and digital I/O channels shown in this configuration are assignable to many different data items within the unit, with a variety of built-in unit conversions. (Apparently. I don't have one myself.)

1 Like

Would you mind describing or pointing me to how the use and/or build this configuration file?

I am looking to test this out on the MC44x family, and then see what can be done to pull tags directly from the E+H Promag Ethernet Flow meters into Ignition.

Since there's a sample above, the simplest way to get started is to load it into a test "EtherNet/IP Host Device" and then use the live editing dialogs in the gateway web interface to rework it to fit your needs. You will certainly need to familiarize yourself with the module's user manual. If you get stuck, I don't mind providing a modest amount of pre-sales support (via email).

Downloads and further information are available on my Module Sales page.

{This is a third-party module that needs to be installed in your gateway, in case you hadn't realized.}