Configuration

Check configurations

Incorrect configurations can interrupt data flow and cause errors in values and ranges. Perform the following steps confirm correct configuration for your adapter.

1. Navigate to Configure data source and verify that each configured device IP address and port are correct.

2. Navigate to Configure data selection and verify the following for each configured data selection item below:

• DeviceId - The referenced device exists in the data source configuration.
  A non-existent or incorrect DeviceId causes the adapter to not find the data source device.

• UnitId - The correct UnitId number is referenced.
  An incorrect UnitId number can cause the adapter to request data from a different or non-existent device.

• RegisterType - The correct RegisterType number or string is referenced.
  An incorrect RegisterType number or string can cause the adapter to not read the correct register groups.

• RegisterOffset - The correct RegisterOffset number is referenced.
  An incorrect RegisterOffset number can cause the adapter to request or incorrectly interpret data locations, which results in unexpected values or out-of-range errors.

• DataTypeCode - The correct DataTypeCode number is referenced.
  An incorrect DataTypeCode number can cause unexpected values or out-of-range errors.

• ScheduleId - The referenced schedule exists.
  A non-existent referenced schedule uses a default schedule instead.

• DataFilterId - If configured, verify the referenced data filter exists.
  A non-existent or incorrect DataFilterId means that data filtering is not active.

• BitMap - If configured, verify the BitMap is correct.
  An incorrect bitmap can cause unexpected values.

3. Navigate to Configure egress endpoints and verify each configured endpoint's Endpoint property and credentials are correct.

• For a AVEVA PI Server endpoint, verify UserName and Password.

• For an AVEVA Data Hub endpoint, verify ClientId and ClientSecret.