Device Attributes Supported by DNP3 Slave Outstations
This section applies to DNP3 slave outstations—outstations that allow ClearSCADA to operate as a DNP3 Slave. When ClearSCADA is configured as a DNP3 Slave, it appears as a DNP3 outstation to a DNP3 master, such as a third-party server. When ClearSCADA is configured as a DNP3 Slave, it supports a number of DNP3 Device Attributes and can transmit the values of those attributes to its DNP3 Master(s). These attributes are listed in section 4 of the ClearSCADA DNP3 Slave Device Profile. The rest of this topic indicates the values that a DNP3 slave outstation will report in response to a request for those Device Attributes.
ID | Device Attribute | Value Returned by a DNP3 Slave Outstation |
---|---|---|
197 | Configuration Version |
The slave reports its configuration version number. This is the value of the DNP3 slave outstation's ConfigVersion field (one of the configuration fields that is located in the CDBObject database table). In the slave outstation's Status display, the Configuration Version is included in the Last Modified status attribute. |
199 | Configuration Last Change Date |
The slave reports the most recent last modified time of the slave outstation itself and all of its Value Maps. The last modified time is the value of each database item's ConfigTime field (one of the configuration fields that is located in the CDBObject database table). In the slave outstation's and Value Maps' Status displays, the last modified time is included in the Last Modified status attribute. |
200 | Configuration Signature |
The slave reports its configuration signature. This is calculated using a CRC32 algorithm, and is computed from the slave outstation and all of its Value Maps' configuration. The Configuration Signature attribute appears in the slave outstation's Status display. |
201 | Configuration Signature Algorithm | CRC32 |
203 | Device Altitude | The slave reports its Location altitude, if one is configured for the DNP3 slave outstation in ClearSCADA (see Use the Location Tab to Specify an Item's Geographic Coordinates). The altitude comprises the slave outstation's elevation in meters above mean sea level. |
204 | Device Longitude | The slave reports its Location longitude, if one is configured for the DNP3 slave outstation in ClearSCADA (see Use the Location Tab to Specify an Item's Geographic Coordinates). |
205 | Device Latitude | The slave reports its Location latitude, if one is configured for the DNP3 slave outstation in ClearSCADA (see Use the Location Tab to Specify an Item's Geographic Coordinates). |
209 | Secure Authentication Version | 2 |
210 | Security Statistics per Association |
0 (As the slave does not support security statistics.) |
212 | Master-Defined Data Set Prototypes |
0 (As the slave does not support data sets.) |
213 | Outstation-Defined Data Set Prototypes |
0 (As the slave does not support data sets.) |
214 | Master-Defined Data Sets |
0 (As the slave does not support data sets.) |
215 | Outstation-Defined Data Sets |
0 (As the slave does not support data sets.) |
216 | Maximum Binary Controls per Request | 170 |
217 | Local Timing Accuracy | 16000 milliseconds |
218 | Duration of Time Accuracy | The slave reports its Clock Set Request Interval, in seconds. |
219 | Analog Output Events Supported | The slave reports 1 if it has an analog output Value Map configured and generates analog output or float output events (otherwise it reports 0). |
220 | Maximum Analog Output Index |
The slave reports the highest index in its analog output Value Map. It reports 0 if it does not have such a Value Map, or the Value Map is empty. |
221 | Number of Analog Output Points | The slave reports the size of its analog output Value Map (or 0 if it does not have such a Value Map). |
222 | Binary Output Events Supported | The slave reports 1 if it has a binary output Value Map configured and generates binary output events (otherwise it reports 0). |
223 | Maximum Binary Output Index |
The slave reports the highest index in its binary output Value Map. It reports 0 if it does not have such a Value Map, or the Value Map is empty. |
224 | Number of Binary Output Points | The slave reports the size of its binary output Value Map (or 0 if it does not have such a Value Map). |
225 | Frozen Counter Events Supported | The slave reports 1 if it has a frozen counter Value Map configured and generates frozen counter events (otherwise it reports 0). |
226 | Frozen Counters Supported | The slave reports 1 if it has a frozen counter Value Map configured (otherwise it reports 0). |
227 | Counter Events Supported | The slave reports 1 if it has a running counter Value Map configured and generates running counter events (otherwise it reports 0). |
228 | Maximum Counter Index |
The slave reports the highest index in its running counter Value Map. It reports 0 if it does not have such a Value Map, or the Value Map is empty. |
229 | Number of Counter Points | The slave reports the size of its running counter Value Map (or 0 if it does not have such a Value Map). |
230 | Frozen Analog Inputs Supported |
0 (As the slave does not support frozen analog input points.) |
231 | Analog Input Events Supported | The slave reports 1 if it has an analog input Value Map configured and generates analog input or float input events (otherwise it reports 0). |
232 | Maximum Analog Input Index |
The slave reports the highest index in its analog input Value Map. It reports 0 if it does not have such a Value Map, or the Value Map is empty. |
233 | Number of Analog Input Points | The slave reports the size of its analog input Value Map (or 0 if it does not have such a Value Map). |
234 | Double-Bit Binary Input Events Supported | The slave reports 1 if it has a double-bit binary input Value Map configured and generates double-bit binary input events (otherwise it reports 0). |
235 | Maximum Double-Bit Binary Input Index |
The slave reports the highest index in its double-bit binary input Value Map. It reports 0 if it does not have such a Value Map, or the Value Map is empty. |
236 | Number of Double-Bit Binary Input Points | The slave reports the size of its double-bit binary input Value Map (or 0 if it does not have such a Value Map). |
237 | Binary Input Events Supported | The slave reports 1 if it has a binary input Value Map configured and generates binary input events (otherwise it reports 0). |
238 | Maximum Binary Input Point Index |
The slave reports the highest index in its binary input Value Map. It reports 0 if it does not have such a Value Map, or the Value Map is empty. |
239 | Number of Binary Input Points | The slave reports the size of its binary input Value Map (or 0 if it does not have such a Value Map). |
240 | Maximum Transmit Fragment Size | The slave reports the value of the Maximum Size of Application Fragment property. This property is defined in the DNP3 Slave section of the ClearSCADA Server Configuration Tool (see Configuring DNP3 Server Settings). |
241 | Maximum Receive Fragment Size | 2048 bytes |
242 | Software Version | The slave reports the ClearSCADA version number (such as 6.80.6724.1) |
243 | Hardware Version | The slave reports the CPU identification and Windows operating system version of the machine on which it is running. (This information also appears in the Information section, within the General branch of the ClearSCADA Server Status Tool.) |
246 | User-Assigned ID Code/Number |
The slave reports the object ID that is associated with the DNP3 Slave Outstation in the ClearSCADA database. This is the value of the Id field (one of the configuration fields that is located in the CDBObject database table). In the slave outstation's Status display, the Id status attribute displays this information. |
247 | User-Assigned Device Name |
The slave reports the full name that is assigned to the DNP3 Slave Outstation in the ClearSCADA database. This is the value of the FullName field (one of the configuration fields that is located in the CDBObject database table). In the slave outstation's Status display, the Full Name status attribute displays this information. |
248 | Device Serial Number |
The slave reports the ClearSCADA product code. This is a Globally Unique Identifier that uniquely identifies the ClearSCADA installer. For example: {E03FC52B-3CE0-49BB-AF05-E4AFF33E4F3F} |
249 | DNP3 Subset and Conformance |
2: (indicating subset level 2, no conformance) |
250 | Device Manufacturer's Product Name and Model | The slave reports the product name and version. For example, ClearSCADA 2017 R3. |
252 | Device Manufacturer's Name | Schneider Electric |