Configure schedules
- Last UpdatedSep 12, 2025
- 2 minute read
- PI System
- Adapter for DNP3 1.2
- Adapters
You can configure the adapter to run scans based on a schedule. Each data item can be assigned to a schedule in the data selection configuration. The adapter samples data for those data items at the scheduled time.
If you start an ingress component without a schedule configuration, a default schedule configuration is added to use as an example.
Note: When the adapter framework scheduler misses or skips a scan for any reason, either one of the following messages is printed: Scan skipped for schedule id <Id> or Scan missed for schedule <id>.
Configure schedules
Complete the following steps to change the schedules configuration:
-
Using any text editor, create a file that contains the schedules configuration in the JSON format.
-
For content structure, see the Example schedule configuration section below.
-
For all available parameters, see the Schedules parameters table below.
-
-
Save the file. For example, ConfigureSchedules.json.
-
Use any of the Configuration tools capable of making HTTP requests to run a PUT command with the contents of the file to the following endpoint:
http://localhost:5590/api/v1/configuration/<ComponentId>/Schedules.
Note: Replace <ComponentId> with the ComponentId of the adapter.
5590 is the default port number. If you selected a different port number, replace it with that value.
Example using edgecmd:
edgecmd -cid <ComponentId> set schedules -file ./ConfigureSchedules.json
On successful execution, the schedules change takes effect immediately during runtime.
Schedules parameters
The following parameters are available for configuring schedules:
|
Parameter |
Required |
Type |
Description |
|---|---|---|---|
|
id |
Required |
string |
Unique identifier for the schedule Allowed value: any string identifier |
|
period |
Required |
string |
The data sampling rate of the schedule. The expected format is HH:MM:SS.###. Invalid inputs: null, negative timespan, or zero A default value must be specified. |
|
offset |
Optional |
string |
The offset from the midnight when the schedule starts. The expected format is HH:MM:SS.### Invalid input: negative timespan A default value must be specified. |
Note: Time spans can be specified as numeric values in seconds, with no upper limit. For example, "period": 25 represents 25 seconds, while "period": 125 corresponds to 2 minutes and 5 seconds. The system accepts any positive integer value to define the duration.
Example schedule configuration
The following is an example of a complete schedule configuration:
[
{
"id": "schedule1",
"period": "00:00:01.500",
"offset": "00:02:03"
}
]
Default schedule configuration
If no schedule is configured, the adapter uses the following default schedule configuration:
[
{
"id": "1",
"period": "0:00:05",
"offset": "0:00:00"
}
]
REST URLs
|
Relative URL |
HTTP verb |
Action |
|---|---|---|
|
api/v1/configuration/ComponentId/Schedules |
GET |
Gets all configured schedules |
|
api/v1/configuration/ComponentId/Schedules |
DELETE |
Deletes all configured schedules |
|
api/v1/configuration/ComponentId/Schedules |
POST |
Adds an array of schedules or a single schedule. Fails if any schedule already exists. |
|
api/v1/configuration/ComponentId/Schedules |
PUT |
Replaces all schedules |
|
api/v1/configuration/ComponentId/Schedules/<id> |
GET |
Gets configured schedule by id |
|
api/v1/configuration/ComponentId/Schedules/<id> |
DELETE |
Deletes configured schedule by id |
|
api/v1/configuration/ComponentId/Schedules/<id> |
PUT |
Replaces schedule by id. Fails if schedule does not exist |
|
api/v1/configuration/ComponentId/Schedules/<id> |
PATCH |
Allows partial updating of configured schedule by <id> |
Note: Replace ComponentId with the Id of your adapter component.