Configurations

Incorrect configurations can interrupt data flow and cause errors in values and ranges. Use this section to review and verify the correct configurations for the data source, data selection and egress endpoints.

Data Source

Use the following list to troubleshoot Data source parameters:

• MasterStationBehaviors

  • masterAddress - The DNP address on the TCP Channel that the adapter is communicating on is unique. The adapter identifies itself using this address. If there is a conflict, the adapter may have trouble sending/receiving DNP messages to outstations.

  • dataLinkLayerTimeout - The timeout is appropriate for your network. If the value is too small, communications may timeout before completing. If the value is too large, it will take longer to notice communication failures. The default is sufficient in most cases.

• OutstationBehaviors

  • ApplicationLayerTimeout - The timeout is appropriate for your network. If the value is too small, communications may timeout before completing. If the value is too large, it takes longer to notice communication failures. The default is sufficient in most cases.

  • EnableUnsolicited - The outstations support unsolicited data. If outstations support unsolicited data, there may be no need to configure static or event scans. If your outstations do not support unsolicited data, then the value of this parameter is largely inconsequential.

  • EnableTimeSync - The adapter machine has an accurate time sync. When enabled, the adapter provides the current time to an outstation when requested. If you do not want the outstations to sync with the adapter machine time, mark this as false.

  • IntegrityScanOnStartup - The outstation can handle the burden of an integrity scan on startup. This scan places additional load on the outstation whenever the adapter or outstation is restarted.

  • IntegrityScanOnEventBufferOverflow - The outstation can handle the burden of an integrity scan when the outstation's event buffer overflows. This scan places additional load on the outstation whenever outstation's event buffer overflows.

  • IntegrityScanPeriod - The outstation can handle the burden of an integrity scan at this interval. This scan places additional load on the outstation whenever this interval passes.

  • EventClasses - The points you want to collect event data for are in one of the event classes listed here. If your point is not in any event class, you may need to configure a static scan.

  • EventScanPeriod - The interval is appropriate for your data collection needs. A too short interval may put unnecessary load on the network, adapter, and outstations. An interval that is too long may allow the outstation's event buffer to overflow.

• TCPChannel

  • HostNameOrIpAddress - The hostname is resolvable from the adapter machine, the IP address is reachable, or both. Also, the outstation is listening at this hostname/address. Otherwise, the adapter cannot connect to the outstation.

  • Port - The firewalls between the adapter and outstation allow connections on this port. Also, the outstation is listening on this port. Otherwise, the adapter cannot connect to the outstation.

  • MasterStationBehaviorId - This parameter matches the Id of one of the configurations in the MasterStationBehaviors list.

• Outstations

  • DNPAddress - This parameter matches the DNP Address of your outstation. This is used as an identifier on the DNP network. The adapter only accepts data from an outstation at an address specified here in the configuration.

  • OutstationBehaviorId - This parameter matches the Id of one of the configurations in the OutstationBehaviors list.

Data selection

Use the following list to troubleshoot Data selection parameters:

• OutstationId - This parameter must match the Id of one of the Outstation configurations.

• Group - This parameter matches the DNP3 object group number of the point that you want to collect data from.

• Variation - This variation is supported by your outstation. Behavior is outstation dependent if you specify a variation that is not supported.

• Index - This parameter matches the point index of the DNP3 point that you want to collect data from.

• StaticScanScheduleId - This parameter matches the Id of a schedule in the Schedules configuration. This is the interval at which a static scan is requested, but it is not required if no static scan is desired.

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

Egress endpoints

Navigate to Egress endpoints. For each configured endpoint, verify that the Endpoint and authentication properties are correct.

• For an AVEVA PI Server, verify UserName and Password.

• For an CONNECT data services endpoint, verify ClientId and ClientSecret.