Automated measurement classifications

CampbellCloud now supports automated measurement classifications, which allow measurement metadata (such as classification, units, and aggregation type) to be defined at the asset level and automatically applied when data is received into CampbellCloud.

When measurement classifications are defined on the device, manual configuration in Measurement Properties is no longer required.

What is a measurement classification?

A measurement classification defines how CampbellCloud understands a data stream, including:

• Measurement classification and sub-classification

• Units of measurement

• Aggregate type (for example, average, total, or maximum)

These classifications are defined using standardized Campbell Scientific classification codes.

How automated classification works

When an asset sends data toCampbellCloud:

• If measurement classifications are included in the data payload, CampbellCloud automatically applies them to the incoming data streams.

• If no classifications are provided, the data streams remain unclassified, and Measurement Properties must be configured manually. (See Configure Measurement Properties.)

Aspen 10 devices

Aspen 10 devices support automated measurement classifications through their sensor programs.

Requirements

• The Aspen 10 must be running a sensor program that includes predefined measurement classifications.

• Automatic Updates must be enabled on the Aspen 10 device to download updated programs that support automated measurement classifications.

As updated sensor programs are released, Aspen 10 devices with automatic updates enabled will automatically receive these programs and begin sending classified measurements to CampbellCloud.

What happens in CampbellCloud

When a classified Aspen 10 device connects to CampbellCloud:

• Measurement Properties are populated automatically.

• Units and classifications are applied correctly.

• No manual configuration is required.

CR data loggers (CRBasic programs)

For CR data loggers, automated measurement classifications must be added directly to the CRBasic program.

This is done using the FieldClassify() instruction when sending data to CampbellCloud via MQTT.

Key points

• FieldClassify() assigns a classification code to each output field.

• Classification codes define the measurement type, units, and aggregation.

• The instruction must be placed inside the DataTable(), immediately after the output instruction.

• If no classification is provided, the measurement remains unclassified.

CRBasic example

DataTable(Hourly,True,-1) Sample(2,TempC,IEEE4) FieldNames("AirTemp,SoilTemp") FieldClassify("&H01010101,&H01040101") EndTable

In this example:

• 01010101 classifies the datastreams as Temperature >> Air Temperature >> (°C) >> Sample

• 01040101 classifies Temperature >> Soil Temperature >> (°C) >> Sample

Once the program is loaded onto the data logger and compiled and running, all data sent toCampbellCloud with classifications defined will be automatically classified.

Finding classification codes

Measurement classification codes are defined by Campbell Scientific and are standardized across CampbellCloud.

To view available classification codes:

Select Measurement Classifications from the CampbellCloud Help menu. This will display an up-to-date filterable list of supported measurement classifications (https://campbell-cloud.com/classifications ).

What happens after classification

Once measurements are automatically classified:

• Measurement Properties are populated automatically.

• Units are displayed consistently throughout CampbellCloud.

• User and organization unit preferences continue to control display units. (See Displaying and customizing units of measurement.)

• Manual configuration of Measurement Properties is no longer required.

Important notes

• If a classification code is not recognized, it is ignored and defaults to unclassified.

• A classification of all zeros indicates an unclassified measurement.

• Only Campbell Scientific classification codes are supported; custom classifications are not allowed.