Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Create Data Payload Processor (DPP) configuration for a string payload

Create Data Payload Processor (DPP) configuration for a string payload

  • Last UpdatedApr 24, 2025
  • 4 minute read

The following example illustrates how to create a Data Payload Processor (DPP) configuration for a payload consisting of a delimited string.

Assumption: We are receiving Hourly Meter Data and AGA Parameter changes from a text file:

Meter1, 2014-02-01 09:00:00, 150, 150, 75, 75, 25, 30, 14.73, 0

Object Name

Time

Vol.

Energy

Pres.

Temp.

Elev.

Base Temp.

Atmos. Pres.

Latitude

Meter1

2014-02-01

09:00:00

150

150

75

75

25

30

14.73

0

To create DPP configuration for a string payload

  1. On the DPP Config Tool window, we select New > New Decode Template.

    The New Decode Template dialog box opens.

  2. We configure the New Decode Template dialog box as shown and save the record.

    The Decode Method Template dialog box opens.

  3. The first value of our incoming data, as seen in the table above, is "Object Name" (Meter1). Therefore, we want to use the Obj Name parameter:

    1. Since we know the incoming data is a comma-delimited string, we leave Action and Input Data Type as the default string2string and String, respectively.

    2. Likewise, the default String Delimiter value (Comma) is used.

    3. We skip Byte Count, as we're dealing with strings.

    4. For Delimiter/Byte Offset we know that Object Name is the very first value of our incoming string (Meter1, 2014-02-01 09:00:00, ...). Therefore, since no commas come prior to the value, we enter 0.

    5. Finally, since the Source is coming from the Payload column of the rdm_readingRaw table, we enter Payload.

  4. The next value in the incoming string is "Time" (2014-02-01 09:00:00). Therefore, we want to use the Local Time parameter in our list:

    1. We leave Action, Input Data Type, Type, and String Delimiter as the default values.

    2. We skip Byte Count, as we're dealing with strings.

    3. For Delimiter/Byte Offset, we see that, in our incoming string (Meter1, 2014-02-01 09:00:00, ...), the time comes after the first comma. Therefore, we enter 1.

  5. On the DPP Config Tool window, we select New > New Decode Template to create the AGA Parameter Decode Template for Elevation and, after that, Base Temperature, Atmospheric Pressure, and Latitude.

    The New Decode Template dialog box opens.

  6. We configure the New Decode Template dialog box as shown and save the record.

    The Decode Method Template dialog box opens.

    Embedded Image (65% Scaling) (LIVE)

  7. First, we configure the Decode Method Template dialog box for Elevation and select Save.

    Note: For information on determining the Sub Group Name and Item Name, refer to Determine item name and subgroup name.

  8. To create the Decode Template for Base Temperature, we change the fields on the Decode Method Template dialog box as required and select Save as New Template (refer to Create a Decode Template from an existing Decode Template).

  9. We repeat Step 8 for Atmospheric Pressure and Latitude.

    We have now created five Decode Templates for our data. Next, we create a new Decode Define.

  10. On the DPP Config Tool window, we select New > New Decode Define.

    The New Decode Define dialog box opens.

    Embedded Image (65% Scaling) (LIVE)

  11. We configure the New Decode Define dialog box as outlined in Create a Decode Define.

    The Decode Definition must match the incoming record stringKey. In the decodeDefine table, DPP compares the Definition column to the incoming rdm_readingRaw Record's stringKey column.

  12. We add the five new Decode Templates created above to the Decode Define and select Save.