DNP3 Library Documentation ¶ Company : CODESYS Title : DNP3 Version : 1.0.0.0 Categories : Communication Protocols Namespace : DNP3 Author : CODESYS Development GmbH Placeholder : DNP3 Description [ 1 ] ¶ DNP3 library is the library to work with DNP3 on application level. Introduction ¶ The CODESYS DNP3 library is intended to support the application development using the DNP3 protocol according to IEEE Std 1815-2012. It provides function blocks for: Outstation Outstation Outstation configuration OutstationConfiguration Outstation data model OutstationDataModel Outstation data points Point and specific AnalogInput , BinaryInput etc. Outstation data point groups GroupAnalogInputs , GroupBinaryInputs etc. Outstation data model and data points ¶ The following outstation data point types are supported: Analog Input AnalogInput Analog Output AnalogOutput Binary Counter BinaryCounter Binary Input BinaryInput Binary Output BinaryOutput Double Bit Input DoubleBitInput An application can setup an OutstationDataModel describing a number of data points of the supported types. Outstation data point - inputs / outputs versa configuration ¶ Outstation data points do work with two types of input variables: configuration (for example BinaryInput.description) input / output (for example BinaryInput.pValue or AnalogInput.lowLimit) Data point configuration is fixed (sampled) at Outstation startup (xEnable FALSE –> TRUE) - so changes to data point configuration after Outstation startup are ignored. Data point inputs / outputs are intended to expose application data to the DNP3 protocol - so they are processed after Outstation startup accordingly. Outstation data point inputs / outputs of type AnyNumber ¶ Some data point inputs / outputs are implemented as VAR_INPUT / VAR_IN_OUT (data) using AnyNumber , to support easy use of certain data types - for example AnalogInput . AnyNumber requires to use support functions for compare, arithmetic etc. - see documentation of AnyNumber . Outstation data flow ¶ Outstation data points of same type are grouped in a data point group. Data point groups needed for a specific Outstation do specify the OutstationDataModel which is connected to Outstation input dataModel. A specific OutstationConfiguration (actually either OutstationConfigurationIP or OutstationConfigurationCOM ) is also connected to Outstation input configuration. If the Outstation is enabled, the dataModel and the configuration is checked for consistency. Example ¶ The CODESYS DNP3 package includes an example how to work with Outstation in ST and CFC. The example gets installed at your local hard drive during package installation - default is C:\\Users\\your-username\\CODESYS DNP3\\x.x.x.x\\Projects. Outlook ¶ Future versions of CODESYS DNP3 will provide function blocks for: Outstation data point event generation Master Contents: ¶ DNP3 Doc Enums Function Blocks Functions GlobalConstants Interfaces Parameter Types Library Information GetLibVersion (Function) GetLibVersionNumber (Function) IsLibReleased (Function) Indices and tables ¶ [ 1 ] Based on DNP3.library, last modified 04.10.2023, 10:20:41. LibDoc 4.4.0.0-b.37 The content file DNP3.clean.json was generated with CODESYS V3.5 SP16 Patch 3 on 04.10.2023, 10:20:43.
DNP3 ¶ Doc Example Introduction Outstation data model and data points Outstation data point - inputs / outputs versa configuration Outstation data point inputs / outputs of type AnyNumber Outstation data flow Outlook Enums DoubleBitState (Enum) Error (Enum) PointType (Enum) Function Blocks Groups GroupAnalogInputDeadbands (FunctionBlock) GroupAnalogInputs (FunctionBlock) GroupAnalogOutputs (FunctionBlock) GroupBinaryCounters (FunctionBlock) GroupBinaryInputs (FunctionBlock) GroupBinaryOutputs (FunctionBlock) GroupDoubleBitInputs (FunctionBlock) GroupFrozenCounters (FunctionBlock) Outstation ETHdeviceHelper (FunctionBlock) Outstation (FunctionBlock) IdToString (Method) Name (Property) OutstationConfiguration (FunctionBlock) GetEnableUnsolicitedResponses (Method) OutstationConfigurationCOM (FunctionBlock) OutstationConfigurationIP (FunctionBlock) OutstationDataModel (FunctionBlock) Points AnalogInput (FunctionBlock) AnalogInputDeadband (FunctionBlock) AnalogOutput (FunctionBlock) BinaryCounter (FunctionBlock) BinaryInput (FunctionBlock) BinaryOutput (FunctionBlock) DoubleBitInput (FunctionBlock) Point (FunctionBlock) PointWithFlags (FunctionBlock) Functions AnyNumber AnyNumberArithmetic (Function) AnyNumberAssign (Function) AnyNumberAssignIfNotEqual (Function) AnyNumberCheck (Function) AnyNumberCompare (Function) AnyNumberMaximum (Function) AnyNumberMinimum (Function) AnyNumberToString (Function) AnyNumberTypeEquals (Function) AnyNumberTypeToString (Function) IEC_TMWTYPES_ANALOG_TYPE_ToString (Function) GlobalConstants ConstantsInternal (GVL) Interfaces IGroupAnalogInputDeadbands (Interface) GetPointData (Method) IGroupAnalogInputs (Interface) GetPointData (Method) IGroupAnalogOutputs (Interface) GetPointData (Method) IGroupBinaryCounters (Interface) GetPointData (Method) IGroupBinaryInputs (Interface) GetPointData (Method) IGroupBinaryOutputs (Interface) GetPointData (Method) IGroupDoubleBitInputs (Interface) GetPointData (Method) IGroupFrozenCounters (Interface) GetPointData (Method) IOutstation (Interface) IdToString (Method) LogOptions (Property) Name (Property) IOutstationConfiguration (Interface) GetEnableUnsolicitedResponses (Method) IOutstationConfigurationCOM (Interface) IOutstationConfigurationIP (Interface) IOutstationDataModel (Interface) GetGroupAnalogInputDeadbands (Method) GetGroupAnalogInputs (Method) GetGroupAnalogOutputs (Method) GetGroupBinaryCounters (Method) GetGroupBinaryInputs (Method) GetGroupBinaryOutputs (Method) GetGroupDoubleBitInputs (Method) Parameter Parameter (ParamList) Types AnyNumber AnyNumber (Struct) AnyNumberPointerUnion (Union) AnyNumberTypes (Enum) AnyNumberUnion (Union) AnyNumberValueUnion (Union) COMParity (Enum) COMStopBits (Enum) DNP3_String (Alias) LoggingOptions (Enum)
Doc ¶ Example Introduction Outstation data model and data points Outstation data point - inputs / outputs versa configuration Outstation data point inputs / outputs of type AnyNumber Outstation data flow Outlook
Example ¶ The CODESYS DNP3 package includes an example how to work with |Outstation| in ST and CFC. The example gets installed at your local hard drive during package installation - default is C:\\Users\\your-username\\CODESYS DNP3\\x.x.x.x\\Projects.
Introduction ¶ The CODESYS DNP3 library is intended to support the application development using the DNP3 protocol according to IEEE Std 1815-2012. It provides function blocks for: Outstation Outstation Outstation configuration OutstationConfiguration Outstation data model OutstationDataModel Outstation data points Point and specific AnalogInput , BinaryInput etc. Outstation data point groups GroupAnalogInputs , GroupBinaryInputs etc. Outstation data model and data points ¶ The following outstation data point types are supported: Analog Input AnalogInput Analog Output AnalogOutput Binary Counter BinaryCounter Binary Input BinaryInput Binary Output BinaryOutput Double Bit Input DoubleBitInput An application can setup an OutstationDataModel describing a number of data points of the supported types. Outstation data point - inputs / outputs versa configuration ¶ Outstation data points do work with two types of input variables: configuration (for example BinaryInput.description) input / output (for example BinaryInput.pValue or AnalogInput.lowLimit) Data point configuration is fixed (sampled) at Outstation startup (xEnable FALSE –> TRUE) - so changes to data point configuration after Outstation startup are ignored. Data point inputs / outputs are intended to expose application data to the DNP3 protocol - so they are processed after Outstation startup accordingly. Outstation data point inputs / outputs of type AnyNumber ¶ Some data point inputs / outputs are implemented as VAR_INPUT / VAR_IN_OUT (data) using AnyNumber , to support easy use of certain data types - for example AnalogInput . AnyNumber requires to use support functions for compare, arithmetic etc. - see documentation of AnyNumber . Outstation data flow ¶ Outstation data points of same type are grouped in a data point group. Data point groups needed for a specific Outstation do specify the OutstationDataModel which is connected to Outstation input dataModel. A specific OutstationConfiguration (actually either OutstationConfigurationIP or OutstationConfigurationCOM ) is also connected to Outstation input configuration. If the Outstation is enabled, the dataModel and the configuration is checked for consistency.
IEC_TMWTYPES_SCALED_FLOAT (STRUCT) ¶ TYPE IEC_TMWTYPES_SCALED_FLOAT : STRUCT This allows for a scaled integer representation of floating point value as well as the floating point value itself. This also allows the database to determine how the floating point value would be rounded if an integer value is to be sent in a response. fval will be used if a floating point value is required, lval will be used if an integer value is required. InOut: Name Type fval IEC_TMWTYPES_SFLOAT lval IEC_TMWTYPES_LONG
IEC_TMWTYPES_SFLOAT (ALIAS) ¶ TYPE IEC_TMWTYPES_SFLOAT : REAL
IEC_TMWTYPES_SHORT (ALIAS) ¶ TYPE IEC_TMWTYPES_SHORT : INT
IEC_TMWTYPES_UCHAR (ALIAS) ¶ TYPE IEC_TMWTYPES_UCHAR : USINT
IEC_TMWTYPES_ULONG (ALIAS) ¶ TYPE IEC_TMWTYPES_ULONG : UDINT
