Data filters
- Last UpdatedSep 26, 2025
- 3 minute read
AVEVA adapters can be configured to perform data filtering to save network bandwidth. Every data item in the data selection configuration can be assigned the Id of a data filter. The adapter will then filter data for those data items based on the data filter configuration.
Note: If data filters are enabled and data quality changes, both the old and current data quality values are passed on.
Configure data filters
Complete the following steps to configure data filters. Use the PUT method in conjunction with the http://localhost:5590/api/v1/configuration/<ComponentId>/DataFilters REST endpoint to initialize the configuration.
-
Using a text editor, create an empty text file.
-
Copy and paste an example configuration for data filters into the file.
For sample JSON, see Data filters.
-
Update the example JSON parameters for your environment.
For a table of all available parameters, see Data filters.
-
Save the file. For example, as ConfigureDataFilters.json.
-
Open a command line session. Change directory to the location of ConfigureDataFilters.json.
-
Enter the following cURL command (which uses the PUT method) to initialize the data filters configuration.
curl -d "@ConfigureDataFilters.json" -H "Content-Type: application/json" -X PUT "http://localhost:5590/api/v1/configuration/<ComponentId>/DataFilters"
Alternatively, using edgecmd:
edgecmd -cid <ComponentId> set datafilters -file ./ConfigureDatafilters.json
Note: If you installed the adapter to listen on a non-default port, update 5590 to the port number in use.
For a list of other REST operations you can perform, like updating or deleting a data filters configuration, see Data filters.
On successful execution, the change that you have made to data filters takes effect immediately during runtime.
Data filters schema
The full schema definition for the data filters configuration is in the AdapterName_DataFilters_schema.json file located in one of the following folders:
Windows: %ProgramFiles%\OSIsoft\Adapters\Modbus TCP\Schemas
Linux: /opt/OSIsoft/Adapters/Modbus TCP/Schemas
Data filters parameters
The following parameters are available for configuring data filters:
|
Parameter |
Required |
Type |
Description |
|---|---|---|---|
|
Id |
Required |
string |
Unique identifier for the data filter. |
|
AbsoluteDeadband |
Optional |
double |
Specifies the absolute change in data value that should cause the current value to
pass the filter test. |
|
PercentChange |
Optional |
double |
Specifies the percent change from previous value that should cause the current value
to pass the filter test. |
|
ExpirationPeriod |
Optional |
timespan |
The length in time that can elapse after an event before automatically sending the
next event, regardless of whether the next event passes the filter or not. The expected
format is HH:MM:SS.### or SSS.* |
* Note: For example, "ExpirationPeriod": 5:00 and "ExpirationPeriod": 300 both specify an expiration period of 5 minutes and 0 seconds.
Data filters example
[
{
"Id": "DuplicateData",
"AbsoluteDeadband": 0,
"PercentChange": null,
"ExpirationPeriod": "01:00:00"
}
]
REST URLs
|
Relative URL |
HTTP verb |
Action |
|---|---|---|
|
api/v1/configuration/ComponentId/DataFilters |
GET |
Gets all configured data filters. |
|
api/v1/configuration/ComponentId/DataFilters |
DELETE |
Deletes all configured data filters. |
|
api/v1/configuration/ComponentId/DataFilters |
POST |
Adds an array of data filters or a single data filter. Fails if any data filter already exists. |
|
api/v1/configuration/ComponentId/DataFilters |
PUT |
Replaces all data. |
|
api/v1/configuration/ComponentId/DataFilters |
PATCH |
Allows partial updating of configured data filter. |
|
api/v1/configuration/ComponentId/DataFilters/id |
GET |
Gets configured data filter by id. |
|
api/v1/configuration/ComponentId/DataFilters/id |
DELETE |
Deletes configured data filter by id. |
|
api/v1/configuration/ComponentId/DataFilters/id |
PUT |
Replaces data filter by id. Fails if data filter does not exist. |
Note: Replace ComponentId with the Id of your adapter component.